Trying to figure out what is giving the Bad Command error

dc42

What firmware version are you using? Most firmware versions usually report what the bad command was.

Phaedrux

Can you post your homeall.g as well? Perhaps your bad command is in there.

Dragon

Firmware 2.05.1
Here is the code from Cura a bit more of it in case that helps:

;FLAVOR:RepRap
;TIME:1841
;Filament used: 1.10598m
;Layer height: 0.2
;MINX:96.5
;MINY:96.5
;MINZ:0.2
;MAXX:138.5
;MAXY:138.5
;MAXZ:20.2
;POSTPROCESSED
;LINEARADVANCEPROCESSED
;Generated with Cura_SteamEngine 4.6.1
T0
M83 ;absolute extrusion mode
;M201 X500.00 Y500.00 Z140.00 E5000.00 ;Setup machine max acceleration
;M203 X9000.00 Y9000.00 Z6000.00 E6000.00 ;Setup machine max feedrate
;M204 P500.00 R1000.00 T500.00 ;Setup Print/Retract/Travel acceleration
;M205 X8.00 Y8.00 Z0.40 E5.00 ;Setup Jerk
M220 S100 ;Reset Feedrate
M221 S100 ;Reset Flowrate

G28 ;Home

M140 S65 ; start preheating the bed
M104 S215 T0 ; start preheating hotend
G28 ; home
G32

M190 S65 ; heat to Cura Bed setting
M109 S215 T0 ; heat to Cura Hotend

G32 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up
G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position
G1 X10.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line
G1 X10.4 Y200.0 Z0.28 F5000.0 ;Move to side a little
G1 X10.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line
G1 Z2.0 F3000 ;Move Z Axis up
M83 ;relative extrusion mode
G1 F2700 E-5
;LAYER_COUNT:100
M572 S0.000000 D0 ;added by LinearAdvanceSettingPlugin
;LAYER:0
M107
G1 F300 Z0.4
G0 F6000 X127.637 Y97.311 Z0.4
;TYPE:SKIRT
G1 F300 Z0.2
G1 F2700 E5
G1 F1200 X128.539 Y97.364 E0.03005
G1 X129.432 Y97.496 E0.03002
G1 X130.31 Y97.707 E0.03003
G1 X131.166 Y97.995 E0.03004
G1 X131.993 Y98.357 E0.03003
G1 X132.785 Y98.792 E0.03005
G1 X133.536 Y99.294 E0.03004

And the home all:

; 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

But this only happens with files from Cura.

Thanks.

dc42

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

G32 E0 ;Reset Extruder

That looks wrong. I presume it should be: G92 E0

Edit: @Phaedrux already pointed that out.

Can you post your bed.g file too?

Dragon

Thanks, will try that change now.

Dragon

Nope that wasn't it

Dragon

Here is the end Gcode if it could be there:

G0 F9000 X114.795 Y108.649
G1 F1500 X111.208 Y112.237 E0.16875
G1 X110.926 Y112.519
;TIME_ELAPSED:1841.048257
G1 F2700 E-5
M140 S0
M83 ;absolute extrusion mode
M107
G91 ;Relative positionning
G1 E-2 F2700 ;Retract a bit
G1 E-2 Z0.2 F2400 ;Retract and raise Z
G1 X5 Y5 F3000 ;Wipe out
G1 Z10 ;Raise Z more
G90 ;Absolute positionning

G1 X0 Y235 ;Present print
M106 S0 ;Turn-off fan
M104 S0 ;Turn-off hotend
M140 S0 ;Turn-off bed

M84 X Y E ;Disable all steppers but Z
M83 ;relative extrusion mode
M104 S0
;End of Gcode
;SETTING_3 {"global_quality": "[general]\nversion = 4\nname = Standard Quality
;SETTING_3 #3\ndefinition = creality_ender3\n\n[metadata]\nquality_type = s
;SETTING_3 tandard\ntype = quality_changes\n\n[values]\nadhesion_type = skir
;SETTING_3 t\nmaterial_bed_temperature = 65\n\n", "extruder_quality": ["[gene
;SETTING_3 ral]\nversion = 4\nname = Standard Quality #3\ndefinition = creali
;SETTING_3 ty_ender3\n\n[metadata]\nquality_type = standard\nposition = 0\n
;SETTING_3 type = quality_changes\n\n[values]\ninfill_overlap = 10.0\ninfill
;SETTING_3 _pattern = gyroid\ninfill_sparse_density = 10\ninfill_wipe_dist = 0
;SETTING_3 .4\nmaterial_flow = 100\nmaterial_flow_layer_0 = 100\nmaterial_pri
;SETTING_3 nt_temperature = 215\nretraction_hop_enabled = True\nretraction_hop
;SETTING_3 _only_when_collides = True\nskirt_gap = 10\nspeed_wall_0 = 30.0\ns
;SETTING_3 peed_wall_x = 30.0\ntop_bottom_thickness = =layer_height_0+layer_hei
;SETTING_3 ght*3\nwall_0_material_flow = 100\n\n"]}

Phaedrux

Can you upload the file itself so we could check it in a text editor?

Another thing you can try is to send each command copy and pasted from the file in the gcode console and see if any give an error.

M572 S0.000000

Maybe try fewer zeroes?

Dragon

Here:

30min Benchy.gcode

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

Dragon

Bed file:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue May 26 2020 00:51:15 GMT-0700 (Pacific Daylight Time)
;M561 ; clear any bed transform
G30 X20 Y20
G29 S1 ; probe the bed and enable compensation

; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 115, probe offset (-42, -12)
;M98 Pdeployprobe.g
;G30 P0 X0.00 Y115.00 Z-99999 H0
;G30 P1 X57.50 Y99.59 Z-99999 H0
;G30 P2 X99.59 Y57.50 Z-99999 H0
;G30 P3 X115.00 Y0.00 Z-99999 H0
;G30 P4 X99.59 Y-57.50 Z-99999 H0
;G30 P5 X57.50 Y-99.59 Z-99999 H0
;G30 P6 X0.00 Y-98.87 Z-99999 H0
;G30 P7 X-44.23 Y-76.60 Z-99999 H0
;G30 P8 X-72.61 Y-41.92 Z-99999 H0
;G30 P9 X-83.99 Y-0.00 Z-99999 H0
;G30 P10 X-77.01 Y44.46 Z-99999 H0
;G30 P11 X-49.88 Y86.40 Z-99999 H0
;G30 P12 X0.00 Y53.39 Z-99999 H0
;G30 P13 X49.80 Y-28.75 Z-99999 H0
;G30 P14 X-28.51 Y-16.46 Z-99999 H0
;G30 P15 X0 Y0 Z-99999 S6
;M98 Pretractprobe.g

Again this only happens with files from Cura files from Prusa Slicer don't give the error.

Dragon

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

Can you upload the file itself so we could check it in a text editor?

Another thing you can try is to send each command copy and pasted from the file in the gcode console and see if any give an error.

M572 S0.000000

Maybe try fewer zeroes?

I have tried commenting that line out and it did not fix the error.

Phaedrux

Upload the homeall. and bed.g as well.

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.