True wifi printing
-
No way to work with them so it uploads over wifi then S3D can monitor and control (estop etc) via serial over ethernet?
-
What's the benefit to that over simply using Duet Web Control for monitor/control?
It seems like a lot of work to duplicate functionality that exists already?
-
No way to work with them so it uploads over wifi then S3D can monitor and control (estop etc) via serial over ethernet?
-
Well to me its not duplicating functionality…. Simplify3D already supports this on printers that have built in wifi printing.
To me i find it more of a pain to save sliced file, open browser tab upload file oopse first layer failed rinse repeat when instead i could just push the print button from Simplify3D. that and its far easier to send prints to multiple printers from simplify3d then to repeat this process for each printer.
The web panel serves a great purpose for managing the controller/firmware but for prints especially with many machines using simplify3d is just quicker.
-
You could automate it by writing a script and run it as a post-processing script in Simplify3D.
I wrote a Mac app, launched from an S3D post-processing script, that lets me pick a directory on the Duet to upload to, and presents an option to print after upload.
-
Tomasf… I would love to use that app. I have 3 factory files saved that each represent a printer. The post processing script in each one uploads to the correct queue on Repetier Server and automatically starts the print. I have been looking for a way to duplicate that functionality with the Duet.
-
Tomasf… I would love to use that app. I have 3 factory files saved that each represent a printer. The post processing script in each one uploads to the correct queue on Repetier Server and automatically starts the print. I have been looking for a way to duplicate that functionality with the Duet.
I uploaded it to GitHub: https://github.com/tomasf/DuetUploader
It's very much unfinished, but it should work. You can use it like this in your post-processing script in Simplify3D:
[c]open -a "/Applications/Duet Uploader.app" "[output_filepath]"[/c]
-
Super cool. Is there a way via parameters I can tell it which printer to upload to? Maybe I should just open the project
-
thanks for sharing
-
Super cool. Is there a way via parameters I can tell it which printer to upload to? Maybe I should just open the project
Yeah, you set the hostname in Preferences
-
That looks very useful!
-
Once we start using firmware 1.19 and get FTP support again, perhaps scripting Transmit or something similar will be a better idea than using a dedicated app for uploading.
-
Bear in mind that direct wifi printing comes with security implications. What facilities does S3D provide for authenticating access to the printer over WiFi?
-
I like the idea of some sort of file transfer script to the duet as a S3D post process, mainly to reduce the steps required…
I've come from smoothieboard, which at the time had problems with S3D.. so I'm used to annoying steps in the process, the smoothie/s3d issues is now comipletely fixed by the way, but what I used to have to do was:
-
Slice in S3D, save to temp folder
-
alt-tab to web site for S3D move cleanup process
-
upload gcode file from temp folder
-
Save processed file back to temp folder
-
alt-tab to octoprint page
-
upload gcode file from temp folder
-
Hit print & watch
So I'm pretty used to multiple steps. but its better now, with my DUET my process is:
-
Slice in S3D, save to temp folder
-
alt-tab to DWC page
-
upload gcode file from temp folder
-
Hit print & watch
If I could have a S3D post process script that saved the file directly to the DUET, probably via FTP I assume would be easiest.. then it would save having to have a temp folder and the upload step.. it would end up:..
-
Slice in S3D, (Post process script saves directly to DUET.. with option on what folder it saves to? )
-
alt-tab to DWC page
-
Hit print & watch
-
-
DC42… I have in mind more like the Octo/Repetier method. HTTP upload and control. There is an API key generated to keep it secure
-
I like the idea of some sort of file transfer script to the duet as a S3D post process, mainly to reduce the steps required…
I've come from smoothieboard, which at the time had problems with S3D.. so I'm used to annoying steps in the process, the smoothie/s3d issues is now comipletely fixed by the way, but what I used to have to do was:
-
Slice in S3D, save to temp folder
-
alt-tab to web site for S3D move cleanup process
-
upload gcode file from temp folder
-
Save processed file back to temp folder
-
alt-tab to octoprint page
-
upload gcode file from temp folder
-
Hit print & watch
So I'm pretty used to multiple steps. but its better now, with my DUET my process is:
-
Slice in S3D, save to temp folder
-
alt-tab to DWC page
-
upload gcode file from temp folder
-
Hit print & watch
If I could have a S3D post process script that saved the file directly to the DUET, probably via FTP I assume would be easiest.. then it would save having to have a temp folder and the upload step.. it would end up:..
-
Slice in S3D, (Post process script saves directly to DUET.. with option on what folder it saves to? )
-
alt-tab to DWC page
-
Hit print & watch
In S3D scripts > Post processing
curl -d "@[output_filepath]" -X POST [http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes](http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes)[output_filename].gcodeIt will upload the file upon saving gcode
-
-
In S3D scripts > Post processing
curl -d "@[output_filepath]" -X POST [http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes](http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes)[output_filename].gcodeIt will upload the file upon saving gcode
Is there a way to start it automatically?
-
In S3D scripts > Post processing
curl -d "@[output_filepath]" -X POST [http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes](http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes)[output_filename].gcodeIt will upload the file upon saving gcode
Is there a way to start it automatically?
You mean start printing?
I believe it can be done with the same manner. Will try when I get home. -
DC42… I have in mind more like the Octo/Repetier method. HTTP upload and control. There is an API key generated to keep it secure
Upvote. I put a feature request on the Slic3r Github to have a more generic 'send to printer' option like a command line, but emulating OctoPrint to receive gcode for printing might be a faster way to fitting in with more existing systems.
-
You mean start printing?
I believe it can be done with the same manner. Will try when I get home.Looking forward to this!
