Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Personal Information

  • Field of Work
    R&D / Exploration
  • Country
  1. Thanks @Nikolinux ,it seems the final header is coming in the stderr instead of the stdout, and I was trying to capture it through the stdout.
  2. Hi @nallath, I am trying to use the auto-orient plugin in my CuraEngine source, executing from the command line. Not sure how could I integrate the plugin functionality in the engine.
  3. If I try capturing the output from the command-line with -v parameter, the valid header *after* slicing is not caught. Although the valid header is displayed on the screen, the captured output contains output only till the "END of Gcode". How could I get the valid header details after running the command.
  4. Hi NicoLinux, I have been trying to capture the filament length and time from the, "Gcode header after slicing". But apparently, the updated header does not show up in the output for the command `CuraEngine slice -v -p -j fdmprinter.def.json -l #{model_url}` Seems the header is generated after the gcode, which is not captured in the output. How could I get the final, filament and time parameters.
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!