@droftarts Thanks for grounding me again. I may have misunderstood the docu of G10.
I may have overlooked that:
In your G10 tool offset setting commands (these G10 commands have axis letter parameters and a P parameter but no L parameter), specify the offsets of the nozzle or cutting head relative to the HRP.
I will drop the L parameter than and see how it behaves than.
Cheers, Chreers
I use G10 L2 now to define the offsets from the HRP:
G10 L2 P0 X0 Y0 Z2
I tested a bit, the tip of the nozzle is ruffly 2mm deeper than the z-probe. I expected to see a jump of the z high when I select T0 than but nothing happens when I select T0. Z is still at 2mm when the nozzle barely touching the bed. Did I miss understand something?
Cheers, Chriss
I have the feeling that I should use Z according to:
https://docs.duet3d.com/en/User_manual/Tuning/Defining_tool_and_Z_probe_offsets
Hi *,
My toolchanger setup goes forward slowly, the hardware is mostly done now and I think about the configuration.
I wounder now where I should expect x0 y0. I see it at the moment at the z-endstop on the coupler.
My idea was to use that as the startpoint and set the offset than per tool. Or would it make more sense to use T0's nozzle as y0 x0 and configure the offset of the endstop and the three 0ther tools from there?
I'm not sure what would make more sense. My uneducated guess is variant 1, with 0 at the microswitch, that would make it more generic, would need to calculate one one offset when I replace the tool.
How have you done it? Or how would you do it and why.
Cheers, Chriss
@Argo Argo is back in town... 
@Hernicz Well, duet, as you know, is g-code only, so scripting is the only way too implement anything in RRF. You can add any kind of interaction code wherever you want, in the start.g, in some filament specific g-code what so ever. I just wanted to show you HOW you can implement a interaction with the operator and how I did it. It is fine for me if you think that it is irrelevant in your case and you are not going to use it.
Good luck,
Chriss
@Phaedrux Thanks for the confirmation... I have expected that but you know.....
@Hernicz said in Better filament Load and Unload handling:
There's no way to cancel and I have to wait until unload.g finishes before I'm able to select another filament. I'm also unable to put any script into unload.g, because as soon as unload.g finishes running I have no filament assigned.
I have no idea how the unload.g actually works but I had a similar problem with a trigger and I used M291 to interact with the user and you can simply store values in a global variable if you need it later.
Here how I did it with a trigger to head up my hotend, retract, bla bla and the operator can select a new temp for the hotend just because you can not flush the nozzle with ABS when your toolhead is at pla temp etc
;echo "Filament Change triggered"
M291 R"Tool" P"Change Filament?" K{"OK","Cancel"} S4
if (input == 0)
G1 Y1 F20000
;echo "Heating up"
M109 S190 ; Set temp and wait for it
G1 E-86 F600 ; Retract filament
echo "Change Filament"
M291 R"Tool" P"Filament Changed?" K{"Yes","Cancel"} S4
; Yes
if (input == 0)
G1 E84 F600 ; Extrude filament till nozzle
M291 R"Tool" P"Filament temp for nozzle purge" K{"210","230", "260"} S4
if (input == 0)
M109 S210 ; Set temp and wait for it
if (input == 1)
M109 S230 ; Set temp and wait for it
if (input == 2)
M109 S260 ; Set temp and wait for it
G1 E60 F400 ; Extrude to clean the nozzle
M400 ; Wait for the end of extrude
G1 E-18 F800 ; retracht filament from meltzone (revo)
M400
M104 S0 ; Extruder temp to 0
M568 P0 A0 ; Extruder heater off
M106 P5 S0 ; Turn the LEDs off
echo "Done"
; Cancel
if (input == 1)
M106 P5 S0 ; Turn the LEDs off
; No
if (input == 1)
echo "Chancel chosen"
M106 P5 S0 ; Turn the LEDs off
I found it very convenient to use whether I use the DWC or the display.
Cheers, Chriss
@Phaedrux Hmmmm.... I'm still not sure what I should expect. (And I do not do that for pause either to be honest). I never ganged in the pause.g from absolute to relative movement for example. My idea would be to move the toolead to the center front retract the filament, wait for confirmation and extrude a lot of filament to flush the nozzle. Retract a tiny bit and continue the print after a interaction with the operator.
So the move to the front must be a absolute move so I need to change that because reasons. Do I need to change that back before I resume the print than? Or does the FW takes care of that? I guess so because the head needs to go back to the saved position....
Cheers, Chriss
@oliof This is clear to me and what is clear from the docu of M600. But what is with the rest? Will the printer than in the "Pause" state? How will it resume regarding G91/90?
Cheers, Chriss
Hi *,
I have a question regarding the inter print filament change drill.
I realized that the SuperSlicer likes to add a "filament change" code to the generated g code when it detects a logo etc.
I had a quick look at it and it seams to me that it generates a M600 at the needed layer to change the filament. I understood M600 that it executes filament-change.g or pause.g if the first one does not exist.
So what can I expect here? The M600 executes the filament-change.g and goes in "pause" than? And I can continue the print than with a "resume" via the DWC or the display? Does the firmware resume than at the same location and with the same G91/G90 as it was?
Cheers, Chriss
@dc42 Many thanks for the hint. That looks exactly like the solution I was looking for!
Cheers, Chriss
Hi *,
I have the idea to extend my 6HC based printer with some features. One idea includes the need to execute a external shell script on the PI, do make some tasks happening. Is there any way to do that? something like "M??? -P"/path/to/shell_script.sh".?
If not: Can we make it a feature request?
Cheers, Chriss
@jay_s_uk It seems like I instantly felt in love with BtnCmd. 
Cheers....
That is a bit strange, I have found this in one of my older configs:
;; Bed Corner temp sensor (2=Orange, 3=Brown, 4=Green, 5=Yellow, 6=Purple 7=Black, )
; Configure Bed corner temp sensor as thermistor on pin temp2
M308 S5 P"0.temp1" Y"thermistor" A"Bed-Corner" T100000 B4138
So at least the colours of the sensors have/had that feature. I can remember that I created the list of colours in the past.
I guess that we all agree that we want to change the colours here, don't we?
"BtnCmd"?
Cheers, Chriss
Hi *,
I can remember that there is/was a possibility to specify the tool colour in the DWC somehow in the config but I can not find it anymore. Could somebody give me a hint please?
The docu from M563 or M308 did not help me.
Cheers, Chriss
@dc42
Let me point out one more thing here: The printer I see this problem does not have this problem since some weeks anymore. But all of the print which the printer performed are below 100mm in Z. I'm not sure whether that is time ore high related. I just wanted to let you know my observation.
@chrishamm said in duetpluginservice(-root) not starting....:
@Chriss said in duetpluginservice(-root) not starting....:
Is there a am64 repo for that? I would like to play with that in a VM.
No. You could build it from the sources for different architectures but since it requires an SPI link to work I guess that's rather pointless.
OK, so no VM than, I will grep a other PI than for testing that.
@Chriss said in duetpluginservice(-root) not starting....:
I'm confused that I'm the only person reporting that, I used the most recent raspberry image from the duet homepage and I did not altered anything.
If anything went wrong during start-up, the journal should tell you. No idea why they were empty on your machine, though. They should be enabled by default. What variant are you using, 32 or 64-bit, with or without GUI?
64 and without GUI.
Cheers, Chriss
@chrishamm Strange, most strange.... Is there a am64 repo for that? I would like to play with that in a VM.
Am I right when I assume that we need to have the process running twice, one as uid 0 and one as the dsf? I will create two supervisord script to manage the processes till I found the reason for that behavior via the systemd.
I'm confused that I'm the only person reporting that, I used the most recent raspberry image from the duet homepage and I did not altered anything.
Needless to say that I want my init system back.
Cheers, Chriss