So the f-code "bug" is a cosmetic misbehavior only.
Puh - then there is lot of outstanding work which is quite more important like
active g- and mcodes.
cheers Reinhard
Active Gcode and Mcode is the same problem as fcode.
Chris
___
Hi,
On Mittwoch, 1. April 2020, 22:05:01 CEST andy pugh wrote:
> On Wed, 1 Apr 2020 at 05:48, Reinhard
wrote:
> > I added a F-word with a slow value (like F100) to the beginning and a
> > faster one (like F400) to the end. Without changing the feed overwrite,
> > the machine starts to run with
On Wed, 1 Apr 2020 at 05:48, Reinhard wrote:
> I added a F-word with a slow value (like F100) to the beginning and a faster
> one (like F400) to the end. Without changing the feed overwrite, the machine
> starts to run with F400 as feed limit - which is aparently wrong.
Are you sure about this?
On Wed, 1 Apr 2020 at 04:11, Reinhard wrote:
> But this modification should be allowed to lower speed only. Not to rise it
> up.
I strongly disagree, being able to crank up the feed rate is very
important when trying to optimise the cutting parameters.
--
atp
"A motorcycle is a bicycle with
Hi Rod,
On Mittwoch, 1. April 2020, 06:55:14 CEST Rod Webster wrote:
> Really should not be using the eyeometer here
Nice word :)
I use the combination axis/gremlin together with my app to test my app. The
testcase from Chris was new experience for me.
Reinhard
What happens if you plot motion.current-vel and Chris's Fcode pin in
halscope?
Really should not be using the eyeometer here
And yes, the feed values are tokenised and thrown away before it gets to
motion.
Rod Webster
*1300 896 832*
+61 435 765 611
VMN®
www.vmn.com.au
On Wed, 1 Apr 2020
Hi Rob,
On Mittwoch, 1. April 2020, 05:42:08 CEST Rod Webster wrote:
> I'm a bit confused by Reinhard's views.
> We spent a fair bit of time working though this with plasma machines (where
> knowing the commanded velocity is critical) and I don't recall seeing an
> instance where commanded
I'm a bit confused by Reinhard's views.
If you Use an F command F100 and you apply a feed override of +10%, surely
then the machine is allowed to travel at F110?
In that instance the F code is overridden and the velocity may be higher
than the F command by up to 10 units.
I thought the trajectory
Hi,
I'm thrilled that improving synchronization has become so much interest :)
On Dienstag, 31. März 2020, 18:10:37 CEST andy pugh wrote:
> On Tue, 31 Mar 2020 at 06:46, Reinhard
> wrote:
> > The testcase (3Dchips.ngc with different f-words) shows, that f-word is
> > not bound to the motion
On Tue, 31 Mar 2020 at 06:46, Reinhard
wrote:
>
> The testcase (3Dchips.ngc with different f-words) shows, that f-word is
> not
> bound to the motion segments. So I wonder, how the max. velocity of
> segments
> is calculated?
The actual velocity and acceleration limits are set in the INI file
To: EMC developers
Subject: [Emc-developers] feedcode-message branch
Hi Chris,
I had the time to get a closer look to your work.
I was very astonished on executing the testcase for the failure.
Looking at your work, it seems to me, as if the newly introduced fcode-
variable is unrelated
Hi Chris,
I had the time to get a closer look to your work.
I was very astonished on executing the testcase for the failure.
Looking at your work, it seems to me, as if the newly introduced fcode-
variable is unrelated to the rest of motion stuff and I doubt, whether this is
the right way.
12 matches
Mail list logo
