Automations line pause

[_Michael]

I’m surprised that M3 and M5 don’t work in the Automation section of gSender.

I have an IOT relay and use M8 on start and resume and M9 on pause and end. This is with a LongMill and a Router. I’ve never used a spindle with a VFD so maybe that complicates things.

[Pelibob]

It’s starting to get complicated for me to understand all this

[KGN]

They do, but pause works a little differently.

Since you can’t send non-realtime commands in a hold state, pause automations have the following effect:

1. Stop sending on the sender side (workflow pause)
2. Empty buffer (firmware handles all planned movements)
3. On empty buffer, send pause automation - so the pause code will actually run
4. Actually hold the firmware using !

The side effect of this is that pauses are no longer instant (as if we held instantly we’d have no way to send the pause automation code)

The issue that OP might be seeing is hitting pause and not seeing anything happen - because planned movements need to finish before the automation is sent.

[_Michael]

Thanks for the explanation.

@KGN

The issue that OP might be seeing is hitting pause and not seeing anything happen - because planned movements need to finish before the automation is sent.

Good point. I’m used to that behavior because I developed a bad habit of preferring the pause over the physical stop button. That was because with the original LongBoard the stop button stopped the machine but not the Arduino. Now I have the SLB but the bad habit remains.

[KGN]

Something similar to this is coming in 1.6.2 - You’ll be able to add [\xNN] format to macros/console to send the realtime command.

For example, Flood Coolant off would look like the following and be interpreted correctly as the Hex value: