Looking at the G Code console I’ver noticed a number of checksum errors reported even though the printer is just sitting there idle with no print job loaded.
Is this normal and, if so, what causes them?
Which Duet do you have, and which firmware version is it running?
It's a Duet WiFi:
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20 (2017-12-23)
WiFi Server Version: 1.20
Web Interface Version: 1.20
No messages so far this morning otherwise I'd include a couple of examples.
From memory It's something along the lines of "G Code checksum error at line 1114" or thereabouts if that makes sense
Checksum errors normally indicate that the data received by the Duet from PanelDue is corrupt. Possible causes include overrun in the UART on the Duet, or interference pickup by the cable connecting PanelDue to the Duet. I used to see these errors quite often, but in more recent firmware revisions the UART interrupt priority is higher than anything else to avoid this happening, and I haven't seen any checksum errors since that change.
Reducing the baud rate may avoid them.
I was having WiFi issues at the time so that may have a bearing.
Since the errors are being detected and don’t seem to be affecting normal operation I think I’ll just keep an eye on it for now and maybe take a couple of standard anti-interferance precautions (screening the interface cable, checking its routing etc.)
Thanks for the swift response (as always)