CNC Pendant Disconnecting Duet

[middles]

I am a member of the Workbee users group on Facebook where there are a number of continuing reports of the Ardunino pendant causing the Duet to disconnect. I have started using the wireless controller in the attached photo and have had the same problem, on a couple of occasions the WiFi has disconnected. I have tried two different Arduinos (pro micro) with the same result. Looking at the pendant output with a terminal emulator the pendant is producing an occasional abnormal output, shown in the attached screenshot. The previous line number is being added to the G0 command causing incorrect line sequencing. I have seen this where several line numbers have been added to multiple lines completely filling the screen with characters flooding the PanelDue port. Unfortunately, I cannot get the pendant to do this when I want to take a screenshot. It seems that the GcodeSerial library is not adding lines numbers correctly on occasion and this may be causing the Duet to disconnect. I don't think it's a hardware problem, unless generic to the ATmega32U4 chip, but I will change the Ardunino to an ATmega328 and see what happens.

[Phaedrux]

Firmware versions?

[middles]

@phaedrux

Its an Ooznest Duet with their latest firmware, 2.02 I think

[Phaedrux]

I'm really not sure. That firmware version is about 2 years old at this point.

Can you give us more details about the pendant?

[dc42]

@middles is the pendant running exactly the firmware from https://github.com/Duet3D/CNC-Pendant-Firmware ? If so then I will review the code.

PS - also, which version of Arduino software did you built it with; and are you using the PanelDue pass-through facility?

[middles]

@dc42

Yes it is the code you posted on Github, downloaded and used without change or modification, Arduino IDE 1.8.13. The micro-controller is a pro micro, I have tried two with the same result.

[middles]

@dc42

Sorry missed the PanelDue off, no I am not it or the passthrough.

[dc42]

@middles please try the new version I have just committed to https://github.com/Duet3D/CNC-Pendant-Firmware.

[middles]

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

[Zakm0n]

@dc42 Just built my pendant controller, and the most recent code causes the pendant to not work at all. I used the previous commit and it works fine. Whatever you did, broke it in a big way. I noticed it would not respond to movements, but after enough movements were commanded, my Duet 2 wifi had to be completely restarted

[dc42]

@zakm0n that's strange because it works on my pendant, which uses the Arduino Pro Micro. I didn't test it on an Arduino Nano.

[Zakm0n]

@dc42 I'm using pro micro and Duet 2 wifi on the latest RRF2 build for it. Thought I had it wired wrong, but flashing the older sketch made it work. I am getting some wifi issues with it though.

[middles]

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

[middles]

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

[madedi123]

Hello

My problem is that my pendant (the same as david's, with an arduino micro) only sends the M112 command, but does not perform any movement via the encoder. My hardware is a DUET3 6HC with SBC and without Panel DUE, Configuration CNC. The arduino sketch was uploaded with firmware 1.8.1 thank you for your help

[dc42]

@Zakm0n @middles @madedi123 you can trace what the Duet is receiving. Connect a PC running a terminal emulator (e.g. YAT) to the Duet USB port and send M111 S1 P3. Commands received by RRF will then be echoed to the terminal. Lines starting with "aux:" are commands received rom the PanelDue port.

@Zakm0n @middles do you also find that the emergency stop button on the pendant works, even though the other commands don't?

[madedi123]

i will test it tomorrow, yes i know that the emergency stop works but nothing else.

[madedi123]

Aux(bad-csum): G91 G0 F6000 X10.0<LF>Aux(bad-csum): G91 G0 F6000 X-10.0<LF>Aux(bad-csum): G91 G0 F6000 X10.0<LF>Aux(bad-csum): G91 G0 F6000 X-10.0<LF>Aux(bad-csum): G91 G0 F6000 X0.1<LF>Aux(bad-csum): G91 G0 F6000 X-0.1<LF>Aux(bad-csum): G91 G0 F6000 Y0.1<LF>Aux(bad-csum): G91 G0 F6000 Y-0.1<LF>Aux(bad-csum): G91 G0 F600 Z0.1<LF>Aux(bad-csum): G91 G0 F600 Z-0.1<LF>Aux(bad-csum): G91 G0 F600 Z0.1<LF>

Looks like the Duet3 and reprap get the commands from the ardiono correct, but why is there no movement ? and what is (bad-csum) after the command ?

[madedi123]

i think that the emergency stop on pendant can´t reset duet3, is that whyle the config etc. is saved on the pi ?

[dc42]

@madedi123 thanks, the problem is that RRF thinks the checksums are invalid. That tells me where to look.

The pendant will halt and I think reset the Duet if you press the red emergency stop button.