17
Upgrading from Cura 4.12 to 5.6 no longer heats extruders or bed
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jan 2024
17 points (100.0% liked)
3DPrinting
15525 readers
123 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
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
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 
Moderation policy: Light, mostly invisible
founded 1 year ago
MODERATORS
The way that the heaters turn on and off is by using a gcode command. So my first thought is that somehow the new slicing profile is not spitting out those commands. Try comparing the generated gcode from slicing the same model in both versions and see what’s different. The temperature commands have to be at the start so should be easy to find. The gcode commands themselves are very googleable.
Look at the start G-code of your configured printer. Copy over the one from the old version into the new version.
The start gcode of the old version and new version are identical.
The gcode command should be either
m104 e0 160Sets the first extrider to 160, doesn’t wait
Or
M109 e0 190sets the first extruder to 190, waits to reach temp before moving on,
I would consider checking with a usb connection and setting the hot end temp manually that way, if that works, it’s something in the gcode, and you can pull up a gcode reader (or text file,) and search for them.
Is there an easy way to compare .x3g gcode files? It seems to be in binary format, rather than plaintext. Alternatively, is there a way to capture the slicer output gcode before it is translated to x3g?
Wtf is that format and why would anyone use it. I guess it's compressed. That would be the only reason to have a binary format for this.
Also the who writes the x3g file? Is it cura directly?
I think x3g is the required format for all printers running Sailfish firmware, such as my FlashForge printer. I'd be hesitant to change the firmware, as I don't want to risk bricking my printer if I do the wrong thing.
Cura writes the files using the X3GWriter plugin by Ghostkeeper. Perhaps there is a way to turn off this plugin and compare the gcode?
I'm sure there must be a way to temporarily change Cura's settings to export G-code instead of x3g. Did you figure this out yet?