How does FluidNC/Jackpot handle motor disable/enable?

Software / Firmware Jackpot Board / FluidNC
1

Does the V1 version of the Jackpot firmware have an automatic “timeout” at which point the motors are disabled?

The Marlin version (for the SKR boards, for example) had this feature. This resulted in the motors being movable rather than locked into position after 30 minutes or something. It was useful to be able to change this, either by extending the time or disabling it entirely so that the motors remained enabled during long pauses or slow tool changes, for example. The timeout could then be re-enabled at the end of the project.

I have inspected the MPCNC config.yaml and don’t see any obvious indication of such a timeout, but I’ll the first to admit that my understanding of all the parameters in FluidNC is weak at best.

So, does this exist? Or, if not, can it exist? (I know there is a “motor disable” command available, but, I guess I need the opposite…)

2

It’s the idle_ms setting which is typically set to 255 so the motors always stay enabled.

  • idle_ms:
    • Type: Integer
    • Range: 0-4294967295
    • Default: 250
    • Details: A value of 255 will keep the motors enabled at all times (preferred for most projects). Any other value, either between 0-254 or from 256- 4294967295, will disable all the motors that many milliseconds after the last step on any motor. Note: Motors can be manually disabled at any time with the $MD command.

The use of the value 255 to mean “always enabled” is for Grbl compatibility. Grbl used an 8-bit number for this parameter so only values of 0-266 were possible. FluidNC uses a 32-bit number to permit larger values.

1 Like
3

Thanks!

1 Like