3DPrinting

15605 readers

249 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: [email protected] or [email protected]

There are CAD communities available at: [email protected] or [email protected]

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 ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago

MODERATORS

Upgrading from Cura 4.12 to 5.6 no longer heats extruders or bed (sh.itjust.works)

submitted 10 months ago by [email protected] to c/3dprinting

13 comments fedilink hide all child comments

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

[–] [email protected] 1 points 10 months ago (1 children)

Try comparing the generated gcode from slicing the same model in both versions and see what’s different

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?

[–] callcc 1 points 10 months ago* (last edited 10 months ago) (1 children)

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?

[–] [email protected] 1 points 10 months ago (1 children)

Wtf is that format and why would anyone use it

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.

Also the who writes the x3g file? Is it cura directly?

Cura writes the files using the X3GWriter plugin by Ghostkeeper. Perhaps there is a way to turn off this plugin and compare the gcode?

[–] [email protected] 1 points 10 months ago

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?