Error gcode file too long

jay_s_uk

@daoust what do you class as the newest firmware?
what mainboard are you running?

infiniteloop

@daoust said in Error gcode file too long:

I got this message: error, gcode file too long.

It’s not the file is too long, the error message states: GCode command too long. Reading the complete message tells us that in line 995655 of the file "CFFFP_700w heater2.gcode", the G1 command fails at character position 256. Now, please look up that line in the file and show what it contains. In addition, tell us the Cura version you are using.

daoust

@infiniteloop I use cura 5.0 with reprap firmware.

It almost stop in mid print but when I open with notepad++ it only have 941463 line of command for the complet gcode so I don t understand how it can be a probleme with the line 995655

infiniteloop

@daoust said in Error gcode file too long:

with notepad++ it only have 941463 line

Hm, where have the remaining 55+k lines gone? Can you hint me into the right direction by estimating how much of the print was actually done when the error showed up?

daoust

@infiniteloop it stop after 6h30 min in a 10 to 11h print

infiniteloop

@daoust OK, let's have a look at the file as you see it in notepad: If it is complete, it should end with a bunch of commented lines similar to this:

; wipe = 0
; z_offset = 0
; clip_multipart_objects = 1
; dont_support_bridges = 1
; extrusion_width = 0.45
; first_layer_height = 0.25
; infill_only_where_needed = 0
; interface_shells = 0
; layer_height = 0.15
; raft_layers = 0
; seam_position = nearest
; support_material = 0
; support_material_angle = 0
; support_material_buildplate_only = 0
; support_material_contact_distance = 0.15
; support_material_enforce_layers = 0
; support_material_extruder = 1
; support_material_extrusion_width = 0.35
; support_material_interface_contact_loops = 0
; support_material_interface_extruder = 1
; support_material_interface_layers = 2
; support_material_interface_spacing = 0.2
; support_material_interface_speed = 100%
; support_material_pattern = rectilinear
; support_material_spacing = 2
; support_material_speed = 50
; support_material_synchronize_layers = 0
; support_material_threshold = 35
; support_material_with_sheath = 0
; support_material_xy_spacing = 60%
; xy_size_compensation = 0
; bottom_solid_layers = 4
; bridge_flow_ratio = 0.8
; bridge_speed = 20
; ensure_vertical_shell_thickness = 1
; external_fill_pattern = concentric
; external_perimeter_extrusion_width = 0.45
; external_perimeter_speed = 25
; external_perimeters_first = 0
; extra_perimeters = 0
; fill_angle = 45
; fill_density = 25%
; fill_pattern = honeycomb
; gap_fill_speed = 40
; infill_every_layers = 2
; infill_extruder = 1
; infill_extrusion_width = 0.45
; infill_overlap = 25%
; infill_speed = 80
; overhangs = 0
; perimeter_extruder = 1
; perimeter_extrusion_width = 0.45
; perimeter_speed = 60
; perimeters = 3
; small_perimeter_speed = 20
; solid_infill_below_area = 0
; solid_infill_every_layers = 65
; solid_infill_extruder = 1
; solid_infill_extrusion_width = 0.45
; solid_infill_speed = 40
; thin_walls = 0
; top_infill_extrusion_width = 0.45
; top_solid_infill_speed = 30
; top_solid_layers = 4

All these lines start with a colon, the are appended by Cura to the GCodes making up the print. If you don't see anything like this, the file "CFFFP_700w heater2.gcode" is truncated by notepad. In that case, use LibreOffice instead.

As I'm on the Mac, I use Xcode which give me line-numbering - not sure which app you could use on a PC to offer this capability. Nevertheless: When you have ensured to get the whole file, just scroll around in the area short after half of the file. You will notice that most of the lines consist of G1 commands - the other ones are mostly layer changes etc.

These G1-lines all are of (approximately) the same length - just look for a line which extends prominently to the right: that's our culprit!

daoust

@infiniteloop I tested 3 differents gcode viewer, all 3 have the same line count of 941 463. All 2 mark ; end of gcode at line 941 443. After looking for a long gcode line, I don t find anything longer near the midle of the print. Should I try again the same gcode to see if the probleme still there?

daoust

@daoust ![alt text]

Phaedrux

Can you please share the actual file?

Also please share the results of M122.

dc42

@daoust said in Error gcode file too long:

@infiniteloop I use cura 5.0 with reprap firmware.

It almost stop in mid print but when I open with notepad++ it only have 941463 line of command for the complet gcode so I don t understand how it can be a probleme with the line 995655

Current versions of RRF double count line numbers when the line ending is CRLF. So try looking at line 497828.

infiniteloop

@dc42 said in Error gcode file too long:

Current versions of RRF double count line numbers when the line ending is CRLF.

Thanks for the missing link!

infiniteloop

@daoust said in Error gcode file too long:

Should I try again the same gcode to see if the probleme still there?

You can try a simulation run, so no waste of filament. But the original problem has to be found in the file, and @dc42 told us where to look:

Current versions of RRF double count line numbers when the line ending is CRLF. So try looking at line 497828

Be it a line more or less - if you can share the file as @Phaedrux proposes, we can throw our editors with line numbering at it

daoust

so here is the m122 , for the gcode, it say my file size is too big too share, so how to ? file size is
29 921kb

console.txt

daoust

Here is the line that should have fail

infiniteloop

@daoust

for the gcode, it say my file size is too big too share, so how to?

Dropbox, Google Drive? As I don't use any of these, I can't give a recommendation. Maybe @Phaedrux has an idea?

Thanks for the screenshot - all lines look pretty common, so I wonder what's going on there. I really want to examine the binary, and if nothing else helps, run the file in simulation mode on my printer.

The M122 report would be more telling if you made it in the event of the error, that is when you actually print (or simulate) the file.

daoust

@infiniteloop the m122 was done after the error hapen, the printer was never close after the event.

I will look at dropbox to send the file. Now I m suspecting a bad sd card maybe

daoust

@infiniteloop here is the file. it is available for 7 days https://www.transfernow.net/dl/20230120EGawtxia

Thank you

dc42

@daoust thanks, I am running your file in simulation mode now.

infiniteloop

@daoust, @dc42 said in Error gcode file too long:

thanks, I am running your file in simulation mode now.

Mee too. Simulation shows no problems. I've also looked at the file: no hidden characters, no line even near to the limit of 255 chars. So your file is OK. Maybe you're right suspecting the sd card.

dc42

@daoust my simulation ran OK too.

I am wondering whether the file might have become corrupted. How did you upload the file to the Duet? If you uploaded it from DWC, do you have "Use CRC32 checksums for uploads" enabled on the Settings/Machine Specific tab?

You could download the file from the Duet and check whether the downloaded one matches the original.