Thanks a lot for your answers.

I found a very good solution from a nice Company, they have a nice system where you can by the pliers and add inserts for various connectors.
https://www.rennsteig.com/en/products/crimping/200-crimp-system-tool-pew-12

I talked a bit with the support and they told me that there insert "624 1324 3 0" should work with the WE connectors.

I will send them some connectors and some wires for testing now. Let's see what they say after there tests.

That may sounds a bit over the top but I love good tools and I'm sure that it makes sense to support good engineering. I think that this is the case with duet, isn't it?

Cheers, Chriss

@jay_s_uk It seems like I instantly felt in love with BtnCmd.

Cheers....

I use Cura and I hate it... the very last version needs a restart after every print and it is crashing all the time. (on my linux workstation)
But the tree support is a gamechanger for me.

I will test PrusaSlicer 2.3.0-alpha2 after I saw that here in the thread.

This is how a real slicer should look like:

+1 This would be nice. And I ask for a Endstop status too!

@oliof said in Error messages improvement?:

@Chriss you aren't the first to ask for this, see https://forum.duet3d.com/post/325796

Not a surprise to be honest.... It is more a surprise that it took so long that people ask for that feature....

https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Wiring_Diagram

Yes, we can close the topic now..... It was my bad! The tool 0 was selected for homez and not deselected anymore. I changed that and it is working as expected now.

Thanks for your support guys!

Cheers, Chriss

I rebuild the toolhead including the extruder and it seems to me like the problem is gone now. I will do some more test prints but I think that we can close the problem now.

Cheers, Chriss

@Argo Argo is back in town...

@bearer Thanks.. that did it. I'm a bit confused, it my first reflex was the mode 8 but it did not work. Well, I played a bit with the config in the meantime, that ańd your confirmation did the trick.
At least one success today.

Cheers, Chriss

@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