Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gcode IOError: [Errno 2] No such file or directory #779

Closed
Duality4Y opened this issue Oct 21, 2016 · 6 comments
Closed

Gcode IOError: [Errno 2] No such file or directory #779

Duality4Y opened this issue Oct 21, 2016 · 6 comments

Comments

@Duality4Y
Copy link

Duality4Y commented Oct 21, 2016

I cloned the repo, and installed.
I get the error that pronterface can't find the exported gcode file.
it seems that the file is renamed but not loaded under it's new name.
loading by hand works.

full output:

Slicing /home/duality/Downloads/20mm-box.stl
Slicing /home/duality/Downloads/20mm-box.stl
Running slic3r /home/duality/Downloads/20mm-box.stl --load /home/duality/.Slic3r/print/ABS.ini --load /home/duality/.Slic3r/printer/ABS.ini --load /home/duality/.Slic3r/filament/ABS.ini
Running slic3r /home/duality/Downloads/20mm-box.stl --load /home/duality/.Slic3r/print/ABS.ini --load /home/duality/.Slic3r/printer/ABS.ini --load /home/duality/.Slic3r/filament/ABS.ini
=> Processing triangulated mesh
=> Generating perimeters
=> Preparing infill
=> Infilling layers
=> Generating skirt
=> Exporting G-code to /home/duality/Downloads/20mm-box.gcode
Done. Process took 0 minutes and 0.501 seconds
Filament required: 908.2mm (2.2cm3)
Loading file: /home/duality/Downloads/20mm-box_export.gcode
Loading file: /home/duality/Downloads/20mm-box_export.gcode
Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/duality/.pyvenvs/py2venv/lib/python2.7/site-packages/printrun/pronterface.py", line 1393, in load_gcode_async_thread
    gcode = gcode)
  File "/home/duality/.pyvenvs/py2venv/lib/python2.7/site-packages/printrun/pronsole.py", line 891, in load_gcode
    self.fgcode.prepare(open(filename, "rU"),
IOError: [Errno 2] No such file or directory: u'/home/duality/Downloads/20mm-box_export.gcode'
@rockstorm101
Copy link
Collaborator

Hi @Duality4Y,

Thanks for reporting this, and good OP by the way. This seems pretty easy to fix but...

@kliment, is there a reason why printrun expects a sliced file with the suffix "_export"? Slic3r does not add that by default, does Skeinforge?

Regards,
Rock

@hroncok
Copy link
Collaborator

hroncok commented Oct 23, 2016

Skeinforge does.

@rockstorm101
Copy link
Collaborator

Dear @Duality4Y,

Could you try adding -o $o to your slicing command (Settings > Options > External Commands > Slice Command). Mine is slic3r $s -o $o and it works as expected.

By the way, the README.md says:

See the Slic3r readme for more details on integration.

But I can't find where exactly this integration is explained, could this section be missing by any chance?

Regards,
Rock

@Duality4Y
Copy link
Author

Duality4Y commented Oct 24, 2016

yes that works!
pretty cool,
maybe it could be mentioned in the readme to note that you have to use -o $o to generate the right output file for slic3r.

though i wonder if it would be easier to by default just use thing.stl -> thing.gcode and load it that way.

@kliment
Copy link
Owner

kliment commented Oct 25, 2016

Skeinforge does, yes, and it's not configurable there.

On 10/23/2016 10:04 AM, Rock Storm wrote:

Hi @Duality4Y,

Thanks for reporting this, and good OP by the way. This seems pretty easy to fix but...

@kliment, is there a reason why printrun expects a sliced file with the suffix "_export"? Slic3r does not add that by default, does Skeinforge?

Regards,
Rock

@MitchBradley
Copy link

To make it work, I had to open the Slicing settings, then switch to Expert Mode (File>Preferences Mode:Expert) then OK, then kill Slic3r, then re-open the Slicing settings to start in Expert mode, then Output options / Output filename format: [input_filename_base]_export.gcode - i.e. I had to add the "_export" part.

It is sort of amazing that I had the patience to dig deep enough to figure that out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants