Look at the start G-code of your configured printer. Copy over the one from the old version into the new version.
Comment on Upgrading from Cura 4.12 to 5.6 no longer heats extruders or bed
charmed_electron@programming.dev 10 months ago
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.
callcc@lemmy.world 10 months ago
threelonmusketeers@sh.itjust.works 10 months ago
The start gcode of the old version and new version are identical.
threelonmusketeers@sh.itjust.works 10 months ago
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@lemmy.world 10 months ago
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.
threelonmusketeers@sh.itjust.works 10 months ago
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?
FuglyDuck@lemmy.world 10 months ago
The gcode command should be
m104 e0 160Sets the first extrider to 160, doesn’t waitM109 e0 190sets the first extruder to 190, waits to reach temp before moving on