@T3P3Tony said in Command to turn heaters active/standby/off?:
@fcwilt may I ask why you need to turn off (as opposed to set to zero) tools?
One use case that I would need it for would be a pause in printing.
Since you are not always on site I would like to switch off T0 and T1, but without changing or losing the set active and standby temperature.
So that when you continue printing, the correct temperatures are available without having to make this setting.
Ok, thanks for your answers.
You made it easy for me, I will stick to standard extrusion.
I've been wondering what is the better for a long time?
About my story:
At the beginning I printed with my UM2 with volumetric extrusion and found it nice. Due to the conversion to dual, the "UltiGCode" volumetric printing was more complicated because Cura had some restrictions (Ultimaker 2 printer profile).
In a one-to-one comparison, I found the expressions with volumetric extrusion ever better (optically).
Now I've been on Duet for some time and today I'm wondering whether volumetric extrusion brings more advantages than I know.
Of so many reading, I am already quite confused.
I would be happy to hear from you about your answers.
It doesn't look right to me:
G10 S1; retract
I think the problem is the same!
This variant, M500 P31, helped me
Before that, I also used a simple M500
Had posted it here before
https://forum.duet3d.com/topic/15317/reprapfirmware-3-01-rc6-released/147?_=1589506715771
Hi there,
Can it be that the G30 S-3. is no longer working properly?
With RRF2.05 this was saved automatically, max. an M500 was necessary.
Now it only works again with M500 P31
DWC shows the following message:
But config-override.g was not saved
greetings
Many thanks to you, I'm a little smarter now.
So it would go to the fan output? Have Duet2 V1.03.
Would 5V also go to the expansion header since there is more choice with 5V?
To be on the safe side, I would need a second opinion before I spend more thought on it!
Can a "Linear Solenoids Cylinder Solenoids" (e.g. https://www.red-magnetics.com/en/product-groups/linear-solenoids/cylinder-solenoids/its-lz-1335-z/) be controlled with the Duet?
By using "exp.heater3 and exp.heater4" from Expansion header directly without using an expansion board.
With RF3 this should be possible, right?
Thank you for your answers and advice!
Would have another question
Should you invert the pin on M950 or with M581 S1?
What happens to the following constellation:
M950 J1 C"!e0stop"
M581 P1 T0 S1 C0
For me, two sensor inputs are created?
Where does the numbering start?
An example on Gcode Wiki shows J1, so I thought it started at one.
Shouldn't "M581 T3 S0" make a change?
There is only one message
A question of understanding
What is the expected behavior if this macro is called by trigger when printing / filament change
; trigger6.g
; M400
abort "TEST abort"
; M400
I just get a message otherwise no reaction
With this macro:
; trigger6.g
; M400
abort "TEST abort"
The print head stops and when pressed again (trigger) the printer status changes to idel.
Restarting the printout has no reaction, first requires an emergency stop to start a new print job
Has anyone already successfully used the abort function?
For me, this doesn't work as expected at all.
Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC1+1 (2020-02-09b1)
Wouldn't it be time for RF3 to open a new Gcode site?
That would be much clearer.
I was just looking at the upcoming change of M581, and it's getting a bit confusing for me.
@dc42 said in RepRapFirmware 3.01-beta 3 released:
Please check whether you still have these 2 issues using the new binary at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.
All endstop inputs are visible, including the hidden ones 
"abort / while" I could not find any change
Print movements are stopped, but the printer status remains printing
And "while" only works as expected with M400
Status tool is not yet correct
After once on active/standby
The tool status (tools[0].state) appears to no longer be updated to off.
When starting, off is displayed, but once active, off is no longer displayed.
Only with me or can someone reproduce that
@Danal
That didn't catch my eye!
And exactly with M581 there is no information about it.
Thank goodness someone made me aware of it
(in my defense, I have to translate everything with Google translator because my english is unfortunately not good)
Thanks alot
This information was missing to me, it is nowhere to be found.
Perhaps this should be written down for others.
It's different with me, Duet2 Wiffi. This time also called from a print file.
Your mentioned variant does not happen to me, printing is successfully completed. The macro file is only canceled.
With "abort" at the end of the file, the printing movements are stopped, but the printer status remains "Printing/Processing"
Sometimes only an emergency stop helps, sometimes I can use "Pause Print" and then "Cancel Print" to escape the "Printing/Processing" status
Signature is up to date (firmware version, etc.)
@Danal
In what file do you have this.
I have it in tpost #, the following M116 P1 S3
What I just remembered are all axes referenced?
All visible axes must be referenced, otherwise the tool change macros will not be executed.
greeting
@deckingman said in Retract from specific tool if not selected:
No. (but in any case, you don't need RRF3 to use the tool change macros which, IMO Iis the easiest way to achieve what you want to do).
No tool change macros are executed during the pause
@CJ-BRAVO said in Retract from specific tool if not selected:
Can I select specific tool to retract while in PAUSE?
Somehow I came across strange things, here are my examples
Trigger 2 is triggered permanently
Trigger 1 is confirmed with a finger
Loop does not work:
G28 X Y
G0 X10 Y200 F1000
M400
M18 X Y
M400
while sensors.endstops[2].triggered ; == false
;echo "sensor wakü", sensors.endstops[2].triggered
; M291 P"TEST1234" R"TEST" S2
if sensors.endstops[1].triggered
abort "TEST abort"
echo "ENDE"
The loop works with the following code:
G28 X Y
G0 X10 Y200 F1000
M400
M18 X Y
M400
while sensors.endstops[2].triggered ; == false
;echo "sensor wakü", sensors.endstops[2].triggered
; M291 P"TEST1234" R"TEST" S2
if sensors.endstops[1].triggered
abort "TEST abort"
M400
echo "ENDE"
But the abort function does not work, the printing is not canceled
With this code the abort function works
G28 X Y
G0 X10 Y200 F1000
M400
M18 X Y
M400
while sensors.endstops[2].triggered ; == false
;echo "sensor wakü", sensors.endstops[2].triggered
; M291 P"TEST1234" R"TEST" S2
if sensors.endstops[1].triggered
break
M400
if sensors.endstops[1].triggered
abort "TEST abort"
The abort function only seems to work if it is at the very end of the file.
(Also works in a macro as soon as it is at the end of the macro)
Could someone test this on their Duet?