Tool changer commands
-
@t3p3tony and @whosrdaddy
Thank you for your input! I'll try to figure this out with a new cup of coffee
-
@rajaakahel : I don't know if you read this one too: https://duet3d.dozuki.com/Wiki/Gcode#Section_T_Select_Tool?
This is the most informative doc about tools and the sequence followed on tool changes. -
@whosrdaddy
Thank you, I started to make progress finally, after some painful crashes especially with the interference from S3D.. -
Ok, so I removed any parking or picking commands from Simplify3D, and did the following:
; tfree0.g
; called when tool 0 is freed
M98 P/macros/parkT0; tfree1.g
; called when tool 1 is freed
M98 P/macros/parkT1; tpre0.g
; called before tool 0 is selected
M98 P/macros/selectT0; tpre1.g
; called before tool 1 is selected
M98 P/macros/selectT1It works fine during a print, but at the beginning it doesn't pick any tool, and at the end it doesn't park any tool. Is there a way to fix this?
I noticed that I don't have files such as start.g or end.g in the files section, anyway is there such a start file for T0 and another one for T1? (same for the end?) -
@rajaakahel glad you got it working on tool change!
start and end gcodes are normally configured in you slicer so you can add the relevant macro calls to your slicer.
One thing I note it that if you don't always start with tool 0 for every print then its probably better to have the "default state " of your printer with the tool changer with tool 1 selected.
-
@t3p3tony Thank you!
Unfortunately Starting Script and Ending Script in Simplify3D don't allow IF commands such as {IF NEWTOOL=0}
It's only allowed in Tool Change Script section.
And as you know each print is different, one time you start with a tool and another time you start with another tool (same for finishing). So I would love to make it automatic.. -
@rajaakahel in that case you are going to have to have a default state of the printer with always having T0 (or T1) selected. So your end script always selects T0 so you know at the start that T0 is selected. That way when the printer changes to T1 it will park T0 and then pickup T1. That should work even if the printer start with T1, as long as S3d explicitly chooses the tool every time.
-
@t3p3tony Thank you very much for your time! I'll look into this closely. I also submitted a request to S3D to allow IF commands in start and end scripts. I hope it can be added later in the Duet firmware as well.
Please can you check my other post whenever you have time?
https://forum.duet3d.com/topic/6517/setting-z-offset-for-t1 -
@rajaakahel, make sure you start with no tool selected. You probably have T0 at the end of config.g, if so then remove that. Also include T-1 in your slicer end script to deselect and park the active tool.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Thank you! I'm still trying to work it out to be full automatic. Will get back to you with the results
-
@dc42 Hello again, I managed to
park any nozzle at the end of a print by putting the following Ending Script in my slicer:G1 E-15 F4000
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
T0
M98 P/macros/parkT0
G28 X ; home x and y axes
G28 Y ; home x and y axes
M84 ; disable motors
M107
M1In Duet firmware I have the following:
; tfree0.g
; called when tool 0 is freed
M98 P/macros/parkT0; tfree1.g
; called when tool 1 is freed
M98 P/macros/parkT1; tpost0.g
; called after tool 0 is selected
M98 P/macros/selectT0; tpost1.g
; called after tool 1 is selected
M98 P/macros/selectT1But the problem is when I start a print, Duet is always activating T0 (even if the first tool to run is T1) when starting to heat up, but it does not actually go and pick T0 tool (so it thinks T0 is already picked up).
I can work this around by picking T0 at the end of each print without parking it. But I want both nozzles to be parked to prevent oozing and stuff.
So the question is: how can I tell the duet to start a print (heat up) without activating any tool until the print gcode tells it to activate (thus pick up) the right tool?
*I don't have T0 or T1 at the end of config.g
*I tried to include T-1 or M1 at the Starting Script of my slicer, but it didn't work. (Duet is always activating T0 regardless of what tool gonna start).
*I tried sending M1 manually before I start a print (to deactivate tools) but same thing happens when a print is started by heating up (activating T0). -
@rajaakahel Make sure that all axes are referenced before the tool command!
Only then will the tool script be triggered!@rajaakahel said in Tool changer commands:
But the problem is when I start a print, Duet is always activating T0 (even if the first tool to run is T1) when starting to heat up, but it does not actually go and pick T0 tool (so it thinks T0 is already picked up).
Do you have a start.g file? With me the duet does not select a tool at the print start, so you have somewhere a tool command.
@rajaakahel said in Tool changer commands:
I can work this around by picking T0 at the end of each print without parking it. But I want both nozzles to be parked to prevent oozing and stuff.
Does not T-1 work? There must be no M84, M18, M1 before.
G1 E-15 F4000 M104 S0; Extruder M140 S0 ausschalten; Bett ausschalten T-1 G28 X; home x und y Achsen G28 Y; home x und y Achsen M84; Deaktivieren Sie die Motoren M107 M1@rajaakahel said in Tool changer commands:
So the question is: how can I tell the duet to start a print (heat up) without activating any tool until the print gcode tells it to activate (thus pick up) the right tool?
You can activate tools with
T# P0(# = Tool Number) without changing the toolhttps://duet3d.dozuki.com/Wiki/Multiple_tools_and_Tool_change_macros
-
@zerspaner_gerd
"Make sure that all axes are referenced before the tool command!
Only then will the tool script be triggered!"
You mean by "referenced" homed? if so, then yes they are homed."Do you have a start.g file? With me the duet does not select a tool at the print start, so you have somewhere a tool command."
No I don't have a start.g file in the Duet. And in my slicer only G28 is included in the Start Script. I don't find any tool command.."Does not T-1 work? There must be no M84, M18, M1 before."
I tried T-1 and M1 in the Start Script of my slicer, they do nothing. After I upload a print to the Duet, it immediately choose T0 (but doesn't activate the tpost1.g (same if I manually send T-1 or M1 before I start a print).You can activate tools with T# P0 (# = Tool Number) without changing the tool
Where should I put T# P0?
Again, Duet is always activating T0 (even if the first tool to run is T1) when starting to heat up, but it does not activate the tpost1.g. -
Here are all my settings if that helps..
Macros:
https://drive.google.com/open?id=1Nwte-EtKEzL_ogCqJp7PMQ2qsLK7RBkMConfigurations:
https://drive.google.com/open?id=1q-h8eojJ91CQwK2p5YhWKuQaQph0sQ_T -
@rajaakahel said in Tool changer commands:
But the problem is when I start a print, Duet is always activating T0 (even if the first tool to run is T1) when starting to heat up, but it does not actually go and pick T0 tool (so it thinks T0 is already picked up).
That probably means you have either a T0 command or a M109 command near the start of your GCode file before the printer has been homed. M109 or M109 T0 will select T0 implicitly if no tool is selected, and if the printer hasn't been homed than the tool change macros won't be run.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in Tool changer commands:
M109
This is my Start and Ending Scripts in Simplify3D, nothing else is there in between:
Start Script:
G1 E15 F3000
G28 ; home all axes
G1 Y37
Ending Script
G1 E-15 F4000
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
T0
;M98 P/macros/parkT0
G28 X ; home x and y axes
G28 Y ; home x and y axes
M84 ; disable motors
M107
M1I can't find any M109. Where in the Duet I can look for what is causing this? You see I attached all the files in my last post, I can't either find anything in them, please check them yourself too. Maybe my firmware is bad somehow? especially that I have another problem that I have to fix in order for my printer to function! (G10 Z offset for T1 simply doesn't work) as you see here:
https://forum.duet3d.com/topic/6517/setting-z-offset-for-t1/15Any suggestions please? (at least I have to fix the T1 Z offset issue).
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 1.21 (2018-03-21)
WiFi Server Version: 1.21RC4(08b3)
Web Interface Version: 1.21-RC4 -
Please post the first 50 or so lines (not counting comment lines) of the GCode file generated by your slicer. You may find that it has inserted a M109 command before your start GCode.
-
A file starts with T0:
G90
M82
M106 S255
M140 S0
M104 S180 T0
M104 S180 T1
M109 S180 T0
M109 S180 T1
G1 E15 F3000
G28 ; home all axes
G1 Y37
G92 E0
G1 E-3.0000 F2400
G1 Z0.600 F1800
; process Process1-1-1-1-1
; layer 1, Z = 0.200
T0
; tool H0.200 W0.720
; inner perimeter
G1 X194.300 Y161.800 F18000
G1 Z0.200 F1800
G1 E0.0000 F720
G92 E0
G1 X194.944 Y161.800 E0.0409 F1125
G1 X194.821 Y162.257 E0.0709
G1 X194.324 Y162.390 E0.1036
G1 X194.300 Y162.404 E0.1053
G1 X194.300 Y161.800 E0.1436A file starts with T1:
G90
M82
M106 S255
M140 S0
M104 S180 T0
M104 S180 T1
M109 S180 T0
M109 S180 T1
G1 E15 F3000
G28 ; home all axes
G1 Y37
G1 Z0.600 F1800
; process Process1
; layer 1, Z = 0.200
T1
; tool H0.200 W0.480
; inner perimeter
G1 X220.180 Y161.680 F18000
G1 Z0.200 F1800
G92 E0
G1 X221.135 Y161.680 E0.0404 F1125
G1 X221.085 Y161.759 E0.0443
G1 X220.921 Y162.368 E0.0710
G1 X220.405 Y162.482 E0.0934
G1 X220.180 Y162.611 E0.1044
G1 X220.180 Y161.680 E0.1438
G1 X220.180 Y177.346 F18000True, there is M109 before G28! How can I fix this please although as you see nothing in my Start Script is there!
Start Script:
G1 E15 F3000
G28 ; home all axes
G1 Y37 -
In most slicers, if you put tool heating commands in your start GCode then the slicer won't generate them itself. So you use something like this in your start GCode:
G28 ; ensure homed before selecting tool
G10 P0 S[first_layer_temperature] ; set tool 0 temperature
T0 ; select tool
M116 ; wait for all temperatures - not needed if you already do it in your tpost filesThe details will depend on your slicer.
-
Thank you for your time DC42. I'll try to fix this. Now I know it's because of the slicer.
