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!

  • charmed_electronEnglish
    4·
    11 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.worldEnglish
      2·
      11 months ago

      Look at the start G-code of your configured printer. Copy over the one from the old version into the new version.

    • FuglyDuck@lemmy.worldEnglish
      31·
      11 months ago

      The gcode command should be either

      m104 e0 160

      Sets the first extrider to 160, doesn’t wait

      Or
      M109 e0 190

      sets 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.

    • threelonmusketeers@sh.itjust.worksOPEnglish
      1·
      11 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.worldEnglish
        1·
        11 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.

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

        • threelonmusketeers@sh.itjust.worksOPEnglish
          1·
          11 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?

          • anguo@lemmy.caEnglish
            1·
            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?