Trying to figure out what is giving the Bad Command error

[Phaedrux]

M104 S215 T0 ; start preheating hotend

I don't think M104 takes a T parameter, but I don't think it would complain about it...

[Dragon]

Bed is above here is home:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue May 26 2020 00:51:15 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-240 Y-240 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-240 Y-240 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X117 Y117 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
G29 S1

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

[Phaedrux]

I meant the actual file so we can check for bogus characters.

[Dragon]

OK,
But as I said it only gives an error with files from Cura.

bed.g
homeall.g

Thanks for your help!

[Phaedrux]

@Phaedrux said in Trying to figure out what is giving the Bad Command error:

M104 S215 T0 ; start preheating hotend

I don't think M104 takes a T parameter, but I don't think it would complain about it...

Were you able to test this one?

[dc42]

Do you get the Bad Command error just once, or multiple times during the print? If it's multiple times then we probably need to see the whole file.

[Phaedrux]

@Dragon said in Trying to figure out what is giving the Bad Command error:

Here:

30min Benchy.gcode

It doesn't seem to cause any problems other than driving me nuts not knowing what's causing it.

@dc42 There's the whole file.

[dc42]

HxD revealed that yout GCode file has some non-printing characters in it at the start of what appears to be a blank line when viewed in a standard text editor. It's the line after "M109 S205 T0 ; heat to Cura Hotend". Possibly this was in your slicer start script?

PS - there are some more earlier in the file, the EF BB BF sequence. Neither of them is a valid UTF-8 character sequence.

[Phaedrux]

Are you using the Cura plugin to upload the gcode file directly to the printer or are you uploading via the DWC?

What version of DWC are you using?

[Dragon]

@dc42

OK, Thanks! I believe that was it. It would only pop up once when starting but didn't affect the print.

Thanks everyone for the help!

Cheers.