18

Hi folks,

I've used Cura as my main slicer with my Flashforge Creator Pro for several years with no major issues. It was a while since I had upgraded (4.12) and I decided to try out the latest version (5.6).

My printer and slicing profiles seemed to transfer over automatically, but when I tried to slice and print, I encountered a strange issue: It no longer heats the extruders or the bed.

It just starts "printing" immediately with stone-cold extruders and bed. The temperature settings in my slicing profiles seem unchanged from 4.12, so I'm a bit at a loss as to what is happening.

I can verify that this is not a hardware issue with the printer, as I can run print jobs generated in Cura 4.12, and the heaters work just fine.

Anyone else encounter this or a similar issue? Any known fixes or recommended troubleshooting advice?

Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments
[-] sawecw@lemmy.world 2 points 8 months ago* (last edited 8 months ago)

For me, this problem started with Cura 5.6. 5.5 was OK. It stems from lines in the start.gcode that have patterns with two values inside the curly braces such as:

M104 S{material_print_temperature_layer_0, initial_extruder_nr} T{initial_extruder_nr} ; set left or right extruder temperature

For a temperature of 200 and extruder 0, this should produce the gcode "M104 S200 T0", but instead produces "M104 S(200,0) T0". The latter causes the nozzle heater to shut off.

It looks like this bug will be fixed in Cura 5.7. (https://github.com/Ultimaker/Cura/issues/17501)

So the solution is to either go to a Cura version older than 5.6, wait for 5.7 or edit the start.gcode. For me, if I remove ", initial_extruder_nr" from each two value pattern, it works OK. In my Flashforge Creator Pro start template, this pattern appears 4 times. My nozzle temperature line looks like:

M104 S{material_print_temperature_layer_0} T{initial_extruder_nr}

If you have a configuration where the individual nozzles temperature/settings are different from the global ones, then things may not work as expected. For example, I am not sure if replacing {nozzle_wipe_gcode, initial_extruder_nr} by {nozzle_wipe_gcode} does the right thing, particularly with the left extruder. But I am printing fine with the right extruder.

[-] threelonmusketeers@sh.itjust.works 1 points 6 months ago

Thanks for your comment! Not sure how I missed it.

I did some experimentation and came to similar conclusions. I've upgraded to 5.7 and can confirm that this bug is fixed. Thanks again for your comment!

this post was submitted on 05 Jan 2024
18 points (100.0% liked)

3DPrinting

15462 readers
199 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io

There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago
MODERATORS