CuraEngine CLI Slicing Gives an "Empty" GCODE File

[Elkelthen 0]

I'm trying to get a raspberry pi to slice stl files using CuraEngine through the command line. I've done this before in the past on a (much) older version of raspbian, and it may have been before they changed the structure of CuraEngine (something to do with the JSONs? I don't follow this closely, this is just from my recent research).

 

Anyway, the command I'm using is:

 

CuraEngine slice -v -p -j fdmprinter.def.json -j fdmextruder.def.json -s material_shrinkage_percentage=0 -s adhesion_extruder_nr=0 -o test.gcode -l /path/to/usb/test.stl

 

and this creates an output gcode file without spitting out any errors. The gcode file output, however, is clearly not correct. I suspect this is to do with the fact that the mins and maxes for the axes are weird numbers, but I don't know for certain. I will also mention that the two -s parameters I put in are necessary; the command errors out if I don't have those in there. I've tried with stl files on and off USBs, they aren't complex files (just a test cylinder) and these fdm jsons are the most recent as far as I know. I got them from the resources repo yesterday, and I was under the impression that those are the standard "let's get an example working" files.

 

Any help is appreciated and I'm happy to share any information necessary. I'm sure I forgot to mention something in here...

cura_forum_log.log test.gcode

[ahoeben 1,763]

16 hours ago, Elkelthen said:

I got them from the resources repo yesterday

What resources repo exactly?

 

The CuraEngine you are using seems to be version 4.8. You would need to use a version of fdmprinter.def.json and fdmextruder.def.json that matches this version.

https://github.com/Ultimaker/Cura/blob/4.8/resources/definitions/fdmprinter.def.json

https://github.com/Ultimaker/Cura/blob/4.8/resources/definitions/fdmextruder.def.json

[Elkelthen 0]

Worked like a charm, thanks so much!

 

I had been following the same gist I followed for the old version at https://gist.github.com/BenRoe/f166e8b65fe62edda4427fd419059695

 

but tried skipping all the manual build steps since I could just apt-get curaengine. Then I used the wget lines from the gist, which it turns out were very outdated but still download something.

[ahoeben 1,763]

1 hour ago, Elkelthen said:

Then I used the wget lines from the gist, which it turns out were very outdated but still download something.

Actually, those links would have downloaded the correct versions of the files, if you would not have skipped all the manual build steps. But I am glad you got something working now. Just know that what you have working now is (apparently) >2 years old.