@Phaedrux said in ERROR: 409 / BAD COMMAND / WARNINGS:
When connected via USB and Bossa, you should be able to gather some information on what chip is in there.
But the fact the errors are persisting I would think it's more likely the wiring.
Does it run next to endstops or motors?
What baud rate do you have set?
I install 3.1.1 Firmware, PanelDue 1.24, printer is working but error still exist.. 
@Phaedrux said in ERROR: 409 / BAD COMMAND / WARNINGS:
ou can try paneldue fw 1.24
I update to 1.24, but with 3.2rc2 the problem still persist.
Now i'll try to downgrade to 3.1.1, Do I have to follow a particular procedure to do that?
@Dougal1957 How can I check the processor?
If the problem is the 3.2.6, i'll install an other one older.
But the older, it's comparible 
with Duet Firmware 3.2?
@Phaedrux said in ERROR: 409 / BAD COMMAND / WARNINGS:
versions are you running on the Duet and the PanelDue?
Sorry.. PanelDue 5'' v2
PanelDue firmare reupdate and connection checked, but the problem still exist.
@Phaedrux said in ERROR: 409 / BAD COMMAND / WARNINGS:
e been some similar reports of bad commands showing up after updating the firmware and sometime
PanelDue3.2.6
Firmware 3.2RC2
Those type of errors cause also the Pause during prints .. now I'll check the connection
It's about some days that my duet 2 wifi continue to show these errors.
I can't see nothing on the DWC, i can see these only on the pannel.
Same GCODE (prusa slicer 2.3rc2) run on other printer also with Duet 2 WiFi m.b. don't show errors.
I don't think it's caused by Config.g or other sys scripts because a weeks ago there it wasn't problems.
Here my config.g
@Dad003 said in Mechanical filament sensor config:
@Dad003 said in Mechanical filament sensor config:
; filament monitor connected to E0_stop
THank you , i printed my part put the switch and inserted the Gcode line and it work , both extruder need to have filaments in them .
IT there a way that one could had a line of code that would only check the switch of the current extruder in the job ? so that if extruder 2 is not used and has no filament that nothing pop up ? can duet do that or it asking too much .
anyway it work so i dont have to keep watching when the spool it getting low !
Hi, what do you add on config.g? I Use
M591 D0 P1 C"e0stop" S1
M591 D1 P1 C"e1stop" S1
But during print there are some notifications ''bad command .... '' How can I resolve?
