@dc42 Looking at your Duet 3D DWC it seems not to have machine and tool position indications like the Ooznest DWC. Maybe this is an issue for Ooznest!!

@dc42 Sorry I should have been more specific. It's an Ooznest Workbee CNC with WiFi Duet2 and v3.3 firmware. I have a number of programable macros commanded from a wireless pendant with a touch screen. The macros use chained G1 commands to cut a number of differing shapes. Everything works as it should except the tool (workplace) indication on the DWC does not show the intermediate positions at the end of each G1 command, the machine position does. Not sure if this is normal or if I have something wrong. I would like to be able to run an "air cut" to check the positions before machining but without the tool position indication, it's a bit awkward.
Thank you for your prompt reply.

I have a simple test macro G1 X50 F1000 G1 X-50 F1000. When run the machine position updates to +50 and then returns to zero but not the tool position, it stays at 0. Is there a way for the tool position to update. Not a deal breaker but as I am using offsets in a coordinate system I would like to see the tool position.

Regards
Steve Middleton

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

Thanks again.

@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.

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

Does anyone know if the coordinate system in use, 1-9, is reported by the Duet through the PanelDue port in any way, I can't see anything in the documentation

@dc42

I have just tested both versions of the software, the original works the modified does not. I have repeated this several times with the same results. Attached are screenshots from both which are identical. The Ardunino seems to be outputting correctly but the duet is not responding to the modified software. This is a pro-micro connected to an Ooznest WiFi Duet running the latest firmware. Is there a possibility the new software is picking old include files, I assume the IDE by default uses the include files located in the same directory as the .ino file.

@zakm0n

I have just returned from being away so I haven't tried the modified software. I will do it later today and reply to the forum.

@dc42

Thank you for this. Unfortunately, I am not at home and away until the end of next week. I will try this when I return.