Duet wifi S3D
-
I really recommend using the web interface rather than printing over USB. If you do control over USB then make sure you upload the file to the SD card and print from there.
I print only over the web interface and have a 2200VA 4 battery sine wave backup. Printing off a PC would be my last choice, so I agree.
-
I've just been experimenting with sending the S3D output to the Duet Web Control using the rr_upload api. Its a work in progress and what I'd love to be able to do is upload to job to the SDcard via DWC from S3D, then see the job in the live preview, but not sure it will work that way.
I'm on windows so I installed CURL, then you added the following to the additional terminal post processing section of the S3D profile.
curl -d "@[output_filepath]" -X POST http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes\S3D
I've just got it to work so may not be the final script. Ideally I'd like to store the upload with the model name, but I've not found the S3D attribute to send instead of "\S3D"
-
Interesting!
Keep it up and perfect it. Wish I could do this stuff.
(simple mechanical guy here) -
I've just been experimenting with sending the S3D output to the Duet Web Control using the rr_upload api. Its a work in progress and what I'd love to be able to do is upload to job to the SDcard via DWC from S3D, then see the job in the live preview, but not sure it will work that way.
I'm on windows so I installed CURL, then you added the following to the additional terminal post processing section of the S3D profile.
curl -d "@[output_filepath]" -X POST http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes\S3D
I've just got it to work so may not be the final script. Ideally I'd like to store the upload with the model name, but I've not found the S3D attribute to send instead of "\S3D"
i believe you can get the file name using:
[output_filepath] = the full path to the file being saved, including extension
[output_dir] = full path to the folder that you're saving the file in (excluding the actual file itself)
[otuput_filename] = filename without extension or path -
here is a script that works for me:
[[language]] path=[output_filepath] file=${path##*/} curl -# -d "@[output_filepath]" -X POST http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes/$file -
On OSX i have a folder action using a bash script
[[language]] for f in "$@" do path="$f" file=${path##*/} curl -# -d "@$f" -X POST http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes/$file doneAny gcode file I save to this folder with the action gets uploaded. I like this better than the s3d terminal option because the upload happens on save, not preview on print. In this way i only upload once when i know the print looks right.
-
Just my 2 cents and might be off topic but if using usb, you might want to modify a cable and cut out the 5V supply especially if you have a dedicated 5v in to the board already.
-
Thank you for this. I have fine tuned the code for Simplify3D a little, and it works great!
curl -d "@[output_filepath]" -X POST http://hypercube.local/rr_upload?name=gcodes/[output_filename].gcode -
OK. While the above code does upload a file to duet, it does something to the file that leaves it unprintable. I have experimented with it and discovered the following works. This may not be the optimal method still, but it does yield a printable GCode file.
curl -F "file=@[output_filepath]" "http://hypercube.local/rr_upload?name=gcodes/[output_filename].gcode"The reason I say it is not optimal is that is places some HTTP data at the top of the file. But, Duet appears to ignore this code and happily prints anyway. So, for now it will do.
--------------------------16eea21da68ae83e Content-Disposition: form-data; name="file"; filename="curl_test.gcode" Content-Type: application/octet-stream -
This is great! thumbsup Thanks for sharing…
-
Hi,
I used a similar command with Octoprint succesfully so I was quite happy when I found this thread.
The command Im using is
curl -# -d "@[output_filepath]" -X POST http://xxx.xxx.xxx.xxx/rr_upload?name=gcodes/[output_filename].gcode"
which uploads the code correctly, however when I want to print the autouploaded code, it starts the print, does nothing and then returns the message "print finished in 0h 1m".The same code works normally when I upload it via the webinterface.
Whats the trick to get that working?
Cheers
-
Please download the "uploaded" GCode via WebInterface and take a look into the file. Maybe there it will be clearer what happens.
-
I ran the original and the autouploaded file through notepad++s compare tool and they matched 100%
-
I ran the original and the autouploaded file through notepad++s compare tool and they matched 100%
Uhm, thats interesting.
Can you try this one, i'm using and change the IP to your DuetWifi/Ethernet IP?
[[language]] curl -F "file=@[output_filepath]" "http://192.168.178.144/rr_upload?name=gcodes/[output_filename].gcode"That is working even if the Printer is currently busy.
Regards
MoS-tekknix -
Great, that seems to work. Thanks
-
Great, that seems to work. Thanks
You're welcome. That's what's a forum for
Regards
MoS-tekknix -
I ran the original and the autouploaded file through notepad++s compare tool and they matched 100%
Uhm, thats interesting.
Can you try this one, i'm using and change the IP to your DuetWifi/Ethernet IP?
[[language]] curl -F "file=@[output_filepath]" "http://192.168.178.144/rr_upload?name=gcodes/[output_filename].gcode"That is working even if the Printer is currently busy.
Regards
MoS-tekknixThis script
curl -F "file=@[output_filepath]" "http://192.168.x.x/rr_upload?name=gcodes/[output_filename].gcode"
uploads the file correctly, but the print doesn't start…Am I missing something?
-
You need to send a separate command to print the file.
-
Yes, I figured that could be the issue, however, I couldn't find anything here https://github.com/chrishamm/DuetWebControl…
Is there a command to print? Where can I look for it?
I can see
[[language]] function startUpload(type, files, fromCallback) { ```in the javascript, but am clueless how to specify 'print' as the type to upload gcode & start the print -
Use the rr_gcode command to send M32 "filename.gcode".
