frankie
Posts: 4
Joined: Thu Mar 13, 2014 1:34 pm

Feature Request - Output to other destinations

I would like the ability to use different ways to print than a printer directly connected to my PC.

When I run a preview and close it, I get the question:
"If you're happy with the preview, would you like to begin building it on your machine?"

Directly after that, the following options would be great:
- Output the .gcode to an OctoPrint instance and trigger the print command ( http://octoprint.org/ )
- Transfer the .gcode file via FTP (to a remote instance of a print daemon or to a hacked Transcend Wifi SD Card)
- Run a script to do one of the above myself ;-)
kdpainter
Posts: 10
Joined: Mon Sep 01, 2014 6:24 pm

Re: Feature Request - Output to other destinations

+1 on that! I would like an ftp output so I can upload it directly to my raspberry pi. A web interface to Octoprint would be great too but I would just like to ftp it somewhere.
montressor
Posts: 20
Joined: Sat Dec 20, 2014 3:54 pm

Re: Feature Request - Output to other destinations

+1 for option to integrate with Octoprint. Even more awesome to add printer control via Octoprint. Awesomest would be full integration including preview, where Octoprint becomes just another printer.
S3D-Jason
Posts: 1608
Joined: Sun May 31, 2015 6:01 am

Re: Feature Request - Output to other destinations

The "commands for post-processing" section on the Scripts tab runs right after your file is exported. So you could easily execute a script to upload a file to a specific location each time a file is exported.

For example, place this in the "commands for post-processing" section to run upload.bat right after you export the file with an argument for the gcode filepath. We assume -u is the flag used to say what file you want to upload.

Code: Select all

"C:\Users\username\Desktop\upload.bat" -u "[output_filepath]"

Return to “Feature Requests”