Along these lines I wondered if it was possible to echo to the DWC console any commands sent by the user so that there is a log of what was sent? I appreciate you don't want the full gcode file of a print scrolling down the console.

When I change temperature I see the G10 xx xxx command appear in the console, but it would be nice if all manual commands were listed, such as move axis, or run macro etc.. Even if they are sent from a host like pronterface.

Just a thought.

Also any progress on having the last few commands stored for recall in DWC on the console, like pronterface does or DOS or whatever so you can press up/down arrows and resend a command you typed previously, I only ask as this is a standard feature of nearly all console interfaces, its absence from DWC is noticeable.

Sweet. Thanks 🙂

1 board at 1.18 and the other 2 at 1.19beta8. That did the trick. Thank you!!!

This is one for chrishamm.

See the note at the end of this section: https://duet3d.com/wiki/Connecting_and_configuring_fans#G-code_controlled_fans.

I don't know mate, seems like 6 to one half a dozen to the other.

Mine heats both bed and extruder to full temp before printing, and yes it does go to the center twice…once after initial homing and then again after mesh bed leveling to reset the nozzle height, but I see no real harm in it.

I don't use any pressure advance, do you have a bowden extruder?

I do like how to use 170 degC extruder temp before print start to avoid oozing (which is a pain in the arse), but I want my bed at full temp before probing.

Just goes to show how many options are available for us to use, and I'm thinking some of your script blended with mine might be good for my application.

ty so much. ill check it out hopefully get it going good soon

@npm1:

hiya, how would i use octoprint on a raspberry pi instead of the the duetwifi web interface, when attempted to use it the, it worked well but i couldn't send any files to the printer, would i need to remove the duetwifi password

I don't know why it doesn't just work, It may be that Octoprint is expecting some Marlin-specific response that RRF doesn't emulate perfectly. I read that someone modified Octoprint so you can configure it not to wait for OK after each command, but I don't know whether that has made it into the mainstream release yet.

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?