On Wed, 17 Apr 2024, Chris Albertson wrote:
Date: Wed, 17 Apr 2024 17:50:46 -0700
From: Chris Albertson
To: "Enhanced Machine Controller (EMC)"
Cc: Peter Wallace
Subject: Re: [Emc-users] Big Tree Tech Re: Mesa Card Stepgens?
No it does not fail, we can always send new commands in real time
No it does not fail, we can always send new commands in real time to be
executed “right away” (at the current time) and make the queued execution
system look and act as if there were no queue. A command taged with the
current time will jump to the front of the queue.
The system also allows
On Wed, 2024-04-17 at 09:13 -0700, Peter Wallace wrote:
>
> > LCNC really should be doing this. If the Measa cards would
> > maintain a queue
> > and a synchronized clock we would not care at all about latency.
> > Klipper
> > proves the idea works.
>
> This is basically what Mach 3/4 do
>
Nothing wrong with asynchronous processing in control of machinery, as long as
there are checks built in to ensure that events that must happen in a specific
order cannot be executed out of order due to things like race conditions or
operators inputting parameters and hitting the go button too
On 4/17/24 13:02, Todd Zuercher via Emc-users wrote:
Sorry to hijack the thread, but I've had to live with this on a machine that
I'm using cascaded double PID loops on. I have the velocity loop PIDs running
in a fast floating point base thread to help with the tuning of some
cantankerous
>
>>LCNC really should be doing this. If the Measa cards would maintain a
>> queue
>>and a synchronized clock we would not care at all about latency. Klipper
>>proves the idea works.
>
> This is basically what Mach 3/4 do
>
> This fails as soon as you need the control to repond to
> feedback in
On Wed, 17 Apr 2024, Todd Zuercher wrote:
Date: Wed, 17 Apr 2024 18:14:10 +
From: Todd Zuercher
To: Peter Wallace ,
Todd Zuercher via Emc-users
Subject: RE: [Emc-users] Home to index triggers following error
The machine is currently running Linuxcnc 2.7, but the Mesa cards, are
The machine is currently running Linuxcnc 2.7, but the Mesa cards, are
significantly older, dating back to the Linuxcnc 2.5 era.
I'm not sure how comfortable a feel about updating this machine to current at
the moment. It is running 32-bit RTAI, and I'm not confident I'll be able to
achieve
On Wed, 17 Apr 2024, Todd Zuercher via Emc-users wrote:
Date: Wed, 17 Apr 2024 17:00:31 +
From: Todd Zuercher via Emc-users
To: "Enhanced Machine Controller (EMC)"
Cc: Todd Zuercher
Subject: Re: [Emc-users] Home to index triggers following error
Sorry to hijack the thread, but I've had
Sorry to hijack the thread, but I've had to live with this on a machine that
I'm using cascaded double PID loops on. I have the velocity loop PIDs running
in a fast floating point base thread to help with the tuning of some
cantankerous torque mode servos. The position loops are still in the
LCNC really should be doing this. If the Measa cards would maintain a queue
and a synchronized clock we would not care at all about latency. Klipper
proves the idea works.
This is basically what Mach 3/4 do
This fails as soon as you need the control to repond to
feedback in real time
For those on this LCNC list who have not seen Klipper, Klipper’s architecture
is very much like Linux CNC’s. Like LCNC, the g-code interpreter, kinematics,
and motion planning live in a “real computer” like a Raspberry Pi. Or I was
running it on a virtual machine running Linux on my Mac
On 4/17/24 07:40, Tomaz T. wrote:
There is an arbitrarily large position jump when the index
pulse is detected. The position counter is set from
whatever has accumulated during the home move to zero. My
PPMC driver detects index_enable going from 1 to 0 and
suppresses any velocity on the next
On Wed, 17 Apr 2024 at 12:45, Tomaz T. wrote:
now it doesn't trigger following error any more (homing completes
> successfully), interesting thing is, that on first attempt of homing after
> fresh starting LinuxCNC I see quite large spike on f-error when hitting
> index pulse, this large spike
>There is an arbitrarily large position jump when the index
>pulse is detected. The position counter is set from
>whatever has accumulated during the home move to zero. My
>PPMC driver detects index_enable going from 1 to 0 and
>suppresses any velocity on the next servo cycle. It still
15 matches
Mail list logo
