Jump to content

Running CuraEngine from command line, returns empty GCode file


BiLeVi

Recommended Posts

Posted · Running CuraEngine from command line, returns empty GCode file

I have been attempting to get CuraEngine running from the command line in order to use an interactive python script with it through the subprocess import that python has. I call the directory that Ultimaker Cura is in, then type in the argument:

 

CuraEngine slice -v -p -j C:/Users/blv/Cura/resources/definitions/ultimaker2.def.json -o C:\Users\blv\Desktop\200_stars.gcode -l C:\Users\blv\Desktop\stl files\200_stars.stl

 

I get the output file 200_stars.gcode, but when I open it, its completely empty!

 

There are errors/warnings that pop up within the command prompt, which state:


[WARNING] JSON setting zig_zaggify_support has no default_value!
[ERROR] Couldn't find definition file with ID: ultimaker2_extruder_0
[ERROR] Couldn't open JSON file:
[WARNING] JSON setting machine_end_gcode has no default_value!
[WARNING] Unrecognized data type in JSON setting machine_head_with_fans_polygon

[WARNING] Unable to recognize the extension of the file. Currently only .stl and .STL are supported.[ERROR] Failed to load model: C:\Users\blv\Desktop\stl. (error number 0)

 

I believe that the empty GCode output is a result of the JSON file not being read properly, but I do not know how to get it to open and read correctly.

 

Any help would be greatly appreciated!

 

 

  • Link to post
    Share on other sites

    Posted · Running CuraEngine from command line, returns empty GCode file

    Hey @BiLeVi,

     

    Welcome to the Ultimaker Community 🎉


    Personallly I'm not very skilled with running from the engine command line, and most of the Cura Developers can be found on the Github https://github.com/Ultimaker/Cura

    But I can ask someone from the team to take a look for you. 🤞

  • Link to post
    Share on other sites

    Posted · Running CuraEngine from command line, returns empty GCode file

    The best way to overcome these problems is to create a folder that includes all files needed including the .stl file and a little batch file for running the slicer engine.

     

    Looking on your errors there are missing:

    ultimaker2_extruder_0.def.json,

    in addition you need:

    ultimaker.def.json,

    fdmextruder.def.json

     

    Here is an litte example, extract the folder Test to your Desktop and run batch file SliceUM2.bat in cmd window:

    Test.zip

    • Like 1
    Link to post
    Share on other sites

    Posted (edited) · Running CuraEngine from command line, returns empty GCode file

    I might be wrong, but shouldn't you have quotation marks around the STL file path? There's a space in it

     

    C:\Users\blv\Desktop\stl files\200_stars.stl

                                               ^

                                       right here

    Edited by Nosybottle
    • Like 1
    Link to post
    Share on other sites

    • 2 months later...

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