@JayT said in RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error:
; Network
;M552 S1
M552 S-1
I notice you are not enabling networking. Are you running the simulation from a PanelDue?
M929 S3 P"/macros/log/DEBUG.txt"
Is there a reason you're running debug logging? This will impact performance, and means a lot of writes to the SD card. It could be that the level of logging has increased in 3.5.1, and is causing what was a marginal problem on the SD card to become a real one.
I set up a bench test, with a Duet 2 WiFi on RRF 3.5.1 and PanelDue, powered by USB, with your config.g. I enabled networking. I simulated all three files, which all completed fine.
08/05/2024, 16:24:30 M37 P"0:/gcodes/1714799702668-30mmtestcube_44min.gcode"
Simulating print of file 0:/gcodes/1714799702668-30mmtestcube_44min.gcode
08/05/2024, 16:24:35 File 0:/gcodes/1714799702668-30mmtestcube_44min.gcode will print in 0h 45m plus heating time
08/05/2024, 16:24:50 M37 P"0:/gcodes/1714799702737-cfffp_flex_dino_keychain.gcode"
Simulating print of file 0:/gcodes/1714799702737-cfffp_flex_dino_keychain.gcode
08/05/2024, 16:26:36 File 0:/gcodes/1714799702737-cfffp_flex_dino_keychain.gcode will print in 1h 31m plus heating time
08/05/2024, 16:26:48 M37 P"0:/gcodes/1714799702831-pcb-cover_500_5_15h.gcode"
Simulating print of file 0:/gcodes/1714799702831-pcb-cover_500_5_15h.gcode
08/05/2024, 16:29:41 File 0:/gcodes/1714799702831-pcb-cover_500_5_15h.gcode will print in 5h 44m plus heating time
Looking at the DEBUG.txt file the logging created, there's a lot of writes during simulation. I think this is causing a degraded SD card problems. Please try with a new SD card.
Ian