3.2 final execonmcode warning issue

oozeBot

I am not sure which category this needs to go in, so please move it accordingly.

With 3.2 final (on a Duet 3 / RPi) mcodes that have custom scripts associated through execonmcode now result in a warning. This was not happening previously.

m9999
Warning: M9999: Command is not supported

Phaedrux

@wilriker may have some input?

wilriker

@oozeBot No idea right away but I don't see it on my system. Is it maybe because you used lower-case m?

oozeBot

Same result, but I tested a few other custom mCodes and it appears that this is only happening with M9999.. weird.

M9999
Warning: M9999: Command is not supported

PCR

@oozeBot always happend to me. DWC dont know the Mcode. So it will say it

PCR

what you can do is making a macro names M9999.g and put nothing inside or only a M117 "Command"

PCR

https://www.youtube.com/watch?v=WxcLDUF9zMs&t

here you can see it at the end of the video

Phaedrux

What is M9999 supposed to be anyway?

Did you mean M999?

oozeBot

@Phaedrux it’s a custom mCode through execonmcode to safely shutdown the raspberry pi..

Phaedrux

thanks. I assumed but wasn't certain.

oozeBot

@PCR it's odd that it only happens on M9999.. none of my other custom mCodes.

wilriker

@oozeBot How do you issue this command? I checked RRF source code and if the command reaches the Duet via PanelDue it will show this warning regardless which custom code you send. All paths that run through DCS should be handled.

oozeBot

For posterior's sake, I figured this out. My custom mCode (M9999 in this case) to reboot the RPi is immediately shutting it down. DWC is still online long enough to process it as an unknown command since execonmcode doesn't return the call and reports unsupported.

It appears a method to reboot the RPi is being introduced in 3.3 (M999 B-1), so this will no longer be necessary.