Jump to content

Different gcode files [CuraEngine/Cura]


Recommended Posts

Posted · Different gcode files [CuraEngine/Cura]

Hello everyone, I am facing an issue when I generate a gcode from GUI and then from command line the output file is different. (I am new to this so pardon the formatting if its not correct.)

Ultimaker2 Printer is selected in my Cura GUI

from the log I found this command being passed


2017-06-06 16:31:40,883 - DEBUG - .../UM/Backend/Backend.py (_backendLog [88]): [backend] Calling engine with: ['/opt/cura/bin/CuraEngine', 'connect', '', '-j', '/opt/cura/share/cura/resources/definitions/fdmprinter.def.json', '']


Which is followed by a various settings.

If I run the following command from the command line


./CuraEngine slice -v -j /opt/cura/share/cura/resources/definitions/fdmprinter.def.json -o /home/xyz/Desktop/gcodes/command_line_pause-start_100.gcode -l /home/xyz/Downloads/pigrrl-2-raspberry-pi-game-console-by-adafruit/pause-start.stl


I get very different results...

but if I pass this command


./CuraEngine slice -v -j /opt/cura/share/cura/resources/definitions/ultimaker2.def.json -o /home/xyz/Desktop/gcodes/command_line_pause-start_100.gcode -l /home/xyz/Downloads/pigrrl-2-raspberry-pi-game-console-by-adafruit/pause-start.stl


the gcode files are quite same, although there are minor variations (2k-3k lines of gcode)

So what could be causing the issue ?

Also am I doing it correctly ?

I also plan to pass custom settings from command line but I don't know how, is that done by appending

-s to the command or do I need another json file ?


  • CuraEngine Version : 2.3.1
  • OS : Ubuntu 14.04
  • Cura Version: 2.3.1



  • Link to post
    Share on other sites

    Posted · Different gcode files [CuraEngine/Cura]

    The definition file is not the only place with settings.

    The files are different because you give the engine different settings.

  • Link to post
    Share on other sites

    Posted · Different gcode files [CuraEngine/Cura]

    The definition file is not the only place with settings.

    The files are different because you give the engine different settings.

    Thanks, it was as you said, different settings were indeed given, but I didn't knew from where they were going, now its all clear.

    Thank you for the help.

  • Link to post
    Share on other sites

    • 1 month later...
    Posted · Different gcode files [CuraEngine/Cura]


    I did not succeed so far in retrieving identical information from the Cura windows application and CuraEngine and would appreciate some help.

    I using CuraEngine 2.4.0 (git clone https://github.com/Ultimaker/CuraEngine.git && git checkout 2.4.0).

    And the windows version 2.4.0 from Cura.

    I use the CuraEngine to retrieve slicing information like print time and amount of filament used for .stl files.

    I copied the definition files from C:\Program Files\Cura 2.4\resources\definitions and C:\Program Files\Cura 2.4\resources\extruders to the directory /var/tmp/curadef to be used by CuraEngine.

    I copied the settings from the cura.log file (...\AppData\Local\cura).

    I used the printer definition fdmprinter.def.json (as in the connect line in cura.log)

    In the Cura windows application I selected a custom FDM printer with default values

    Are all settings in the cura.log and the printer files?

    What settings am I missing?

    How can I find those settings from the Cura windows app?

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.3 stable released
        In this stable release, Cura 5.3 achieves yet another huge leap forward in 3D printing thanks to material interlocking! As well as introducing an expanded recommended print settings menu and lots of print quality improvements. Not to mention, a whole bunch of new printer profiles for non-UltiMaker printers!
          • Thanks
          • Like
        • 56 replies
      • Here it is. The new UltiMaker S7
        The UltiMaker S7 is built on the success of the UltiMaker S5 and its design decisions were heavily based on feedback from customers.
        So what’s new?
        The obvious change is the S7’s height. It now includes an integrated Air Manager. This filters the exhaust air of every print and also improves build temperature stability. To further enclose the build chamber the S7 only has one magnetically latched door.
        The build stack has also been completely redesigned. A PEI-coated flexible steel build plate makes a big difference to productivity. Not only do you not need tools to pop a printed part off. But we also don’t recommend using or adhesion structures for UltiMaker materials (except PC, because...it’s PC). Along with that, 4 pins and 25 magnets make it easy to replace the flex plate perfectly – even with one hand.
        The re-engineered print head has an inductive sensor which reduces noise when probing the build plate. This effectively makes it much harder to not achieve a perfect first layer, improving overall print success. We also reversed the front fan direction (fewer plastic hairs, less maintenance), made the print core door magnets stronger, and add a sensor that helps avoid flooding.

        The UltiMaker S7 also includes quality of life improvements:
        Reliable bed tilt compensation (no more thumbscrews) 2.4 and 5 GHz Wi-Fi A 1080p camera (mounted higher for a better view) Compatibility with 280+ Marketplace materials Compatibility with S5 project files (no reslicing needed) And a whole lot more  
        Curious to see the S7 in action?
        We’re hosting a free tech demo on February 7.
        It will be live and you can ask any questions to our CTO, Miguel Calvo.
        Register here for the Webinar
          • Like
        • 18 replies
      • UltiMaker Cura Alpha 🎄 Tree Support Spotlight 🎄
        Are you a fan of tree support, but dislike the removal process and the amount of filament it uses? Then we would like to invite you to try this special release of UltiMaker Cura. Brought to you by our special community contributor @thomasrahm
        We generated a special version of Cura 5.2 called 5.3.0 Alpha + Xmas. The only changes we introduced compared to UltiMaker Cura 5.2.1 are those which are needed for the new supports. So keep in mind, this is not a sneak peek for Cura 5.3 (there are some really cool new features coming up) but a spotlight release highlighting this new version of tree supports.  
          • Like
        • 29 replies
    • Create New...