Hello Guest it is May 14, 2021, 02:57:48 AM

Author Topic: M codes and mach4, is there still a hesitation same as m3? (Except m10/m11)  (Read 1254 times)

0 Members and 1 Guest are viewing this topic.

As per title, when using m codes to toggle outputs is there still a hesitation with mach4, the same as there was with mach3, hence the reason why the m10/m11 codes were used as they were suppose not to have the delay / hesitation?

Was this not to do with the loop speed in mach3

(Question is to do with THC on and off control where a divot was created with the torch pause / hesitation during the m code processing)

Thanks

Rob
Rob

Albert Einstein ― “If you can't explain it to a six year old, you don't understand it yourself.”

Offline Tweakie.CNC

*
  • *
  •  8,706 8,706
  • Super Kitty
    • View Profile
    • Tweakie.CNC
Hi Rob,

If it's any help, the Mach4 equivalent to the Mach3 M11Px/M10Px commands are...

M62Px turns Output# x ON
M63Px turns Output# x OFF

There are no delays associated with these commands as they take effect coincident with axis movement.

Tweakie.
KEEP SAFE !
Tweakie, thanks very much, I'll give them a go

(Running a smooth stepper so that has its own challenges to see what's implemented and what's not, in mach3 only one output could be toggled with an m10/m11 regardless of the "Px" bit as the output is defined in the motion controllers config page)

Rob
Rob

Albert Einstein ― “If you can't explain it to a six year old, you don't understand it yourself.”