PanelDue M409 polling and G1 sequence return

middles

I have an Ooznest CNC WiFi Duet 2, with a connected pendant, running dc42 software and a small display reading axis information through the paneldue port. It was working fine on v2 firmware but since upgrading to V3.3 - some issues. The display polls with M408 but the JSON response now seems much larger and is causing memory size issues. To improve this I'm now using M409 but have to make six calls, six reads and six deserial to read the user and machine axis, it's clumsy and slow. Is there a way to query the object module once to read all six axis as with M408. I have looked at "coords" in the type 1 response but do not know how it relates to M409 and its commands.

Also when I send G1 command I now get this response down the paneldue {"seq":26,"resp":"\n"} which I don't think was there before. I assume its sequencing information but I can't find any references in the documentation. I would like to turn it off as its interfering with the M409 polling.

Any information would be gratefully received.

Regards
Steve Middleton

dc42

@middles you can query the OM to read all 6 axis using M409 K"move.axes". To get just the values that change frequently (the machine position and user position) use M409 K"move.axes" F"f".

There isn't a way to remove the reporting of empty responses to G1 commands in RRF 3.3, but I can change RRF 3.4 not to report empty responses to an attached PanelDue or something that is emulating one.

middles

@dc42 Thank you for this. Unfortunately, I broke my laptop so was not able to do this from the console, only an Arduino connected to the panelDue port. I now have a laptop connected and it's making some sense. Yes I can read the user and machine positions with M09K"move.axes"F"f" so all should be okay. Needed fewer fingers and more spelling lessons.

The G1 response I can block so it doesn't get deserialised as an axis position.

Many thanks again, response much appreciated.

dc42

@middles the RRF 3.4 stable release, or next RC of there is one, will no longer return empty responses to PanelDue.

I recommend that you parse all responses as JSON and look at the file names, just as PanelDue does, in order to ensure that you pick up the values that you want and nothing else.

middles

@dc42 Yes now I've got the data down to a reasonable size I can parse and select what I want.

Thanks again.