Mac with S3D… put this in your Scripts/Additional terminal commands for post processing section.

You will need to update the IP address to your Duet. When you save the gcode (it doesnt matter where), it will at the same time upload to the duet and start printing right away. Be sure you check your printer before printing, Its easy to forget a print or maybe even just a skirt is still there. You can turn off your computer after it finishes uploading. The gcode is completely on the Duet. You will not be able to control the printer from S3D at this point, you will need to use the web interface.

curl --data-binary "@[output_filepath]" -X POST [http://192.168.5.26/rr_upload?name=gcodes](http://192.168.5.26/rr_upload?name=gcodes)[output_filename].gcode
curl -G http://192.168.5.26/rr_gcode –data-urlencode "gcode=M32 [output_filename].gcode"

EDIT: This might have problems with certain characters in the filenames. I had a failed upload with a space in the filename. I havent had time to play with that yet.

Just coming at this the other way if you want the extruder to retract at 2000 mm/min set this as your e jerk value. I appreciate this might cause a stall depending on the extruder/gearing and you might have to use a lower value but at least you have control over it. I'm using a cable driven extruder on one machine and have to use low jerk and acceleration to get the motor to reverse and turn at high rpm (40:1 gearing) so I expect it never reaches the intended retract speed. It's irrelevant as it retracts enough to prevent blobs and strings.

Thanks Dave! I look forward to the new release!

I just do the homing while the bed is heating up - I have to wait for that in any case. So, M140 - G28 - M190. Of course, if you print onto a cold bed, then it won't work.

I think I'll go with the Arduino option for now then. Thank you all for your responses.

Glad to hear you got it working!

I added my config-override.g to the same folder on Drive. It only includes the results of the PID autotuning so nothing very interesting.
I see your other problem was already answered in the other thread, you just need to set some tool as active. I have it in my Slic3r start code, but I guess it could just as well be in the end of config.g.

If you have only 1 extruder you can add T0 to the end of your config.g to select it when the machine powers up. This avoids a "no tool selected" problem. If you have multiple tools then it's a bit more complicated.

One thing to consider is if a 4 head axis IDEX type design was developed then XUVW would all be used by individual axis. A solution which used a XYZ to move the currently selected tool axis, while allowing UWV? to represent the actual drives makes sense.

Extending this logic further it could be conceivable that someone would want to build an IdeY (independent Y axis) or similar, or even have multiple Z axis for different tools in a tool changer type situation (OK I admit this is getting far fetched and I can't see how the mechanical design would work but bear with me).

With that in mind should IdeX type machines not be required to map "special" drive designations (U,V,W,?,?,?….) to the actual drives and then use XYZ only for the currently selected drives. If a tool specifies that multiple drives are mapped to X, Y or Z then this would of course not be a problem.

Thanks for clarification David, I started to think I was mad!

should i create tfree0 files?

No worries 🙂

Yeah I might get a sheet just to try with the piezo sensor, but so far I'm sticking with printbite.

Which interestingly although its fairly tough a 250 deg C nozzle driven hard into it during a headcrash, which I had a few of during developing the piezo sensor, will leave a hole in it, I have about 3 or 4 holes, tried filling them with abs juice, which works but gets pulled out with a print.

Also I believe it is being removed from slic3r, it already has been in in the Prusa editions, as the hardware version works better.

A 0 byte file length sounds like the file was new!y created, perhaps to upload a new one or save some edits, but the rest of the upload failed.

I'll add a work item to make uploads create and write a temporary file, and only rename to the correct file name (after deleting the old one if it exists) when the upload is complete.

@saffi:

the Duet is definitely my go to board now for printer builds.

I'm with you there.

My long term goal is to install Diamond 5 color hotends - as part of that process I just added Duex5 boards to my printers.

I have another printer kit on order (larger non-delta) and I already have the Duet boards in house ready to go.

Great stuff.

Frederick

Just love a happy ending.

Frederick

Also you can adjust Z on the fly, it is called babystepping (a search on the forum will turn up results).

ok, partialy i have found the issue. in the article by deckingman there is a paragraph that refers to extruder numbering. i suggest to extend it by following

[[language]] slic3r on object -> settings it is offered to choose extruder from the "default" (that is prompted to be 0), "1", "2", "3" and "4". In fact, slic3r treats "default" as "1". Later in generated gcode this "default"="1" is treated as "T0". "2" is treated as "T1" etc.

another issue that i look into now - even for very simple things (circle) it generates 5 tool changes, that can be difficult with manual filament change.

And just as a footnote for the new guys (like me).

When I entered M143 H0 S140 via the DWC, all was good until I used the emergency stop or updated the firmware. Then I was back to the default 125 degC limit for the bed.

To make it permanent, you need to enter the line in the config file.

This may be obvious to some but not to others, so I thought I'd mention it.

I am running 1.18.1 but have not removed the card while it is on. I removed the card and scanned for errors on the PC and it was clean. I replaced the card and will test again and see if I have any issues. I am hoping it is just a flakey card.

thanks,
Brendin