Jump to content

Different gcode files [CuraEngine/Cura]


chintanjoshi1

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', '127.0.0.1:49674', '-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

 

Thanks

  • 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]

    Hi,

    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.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 26 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...