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....

Hi * and happy x-mas,

I can remember that we had the discussion about the colours in the DWC and the temp chart, I remember from the top of my head that this colours are not configurable, aren't they?

I do not feel very satisfied with some colours here:

Brown seams a bit low in contrast, the difference between Tool1 and tool3 is hard to tell. And the black on that nice gray looks very ruff to me.

It would be very, very nice if we could make that configurable or if some colours would not be used, specially in some combinations liek this red and orange.

Cheers, Chriss

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

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

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...

Hi * and happy x-mas,

I can remember that we had the discussion about the colours in the DWC and the temp chart, I remember from the top of my head that this colours are not configurable, aren't they?

I do not feel very satisfied with some colours here:

Brown seams a bit low in contrast, the difference between Tool1 and tool3 is hard to tell. And the black on that nice gray looks very ruff to me.

It would be very, very nice if we could make that configurable or if some colours would not be used, specially in some combinations liek this red and orange.

Cheers, Chriss

@droftarts Thanks... That helped indeed a lot to get a better/full understanding about the concept.

@dc42 Thanks for the further explanation David! I understand it now and I switched over to the G53 concept in the meantime. Going "my way" was not very successful.

I have a other questions about the tool change itself. The Prusa slicer, which I use here, acts a bit stupid in my understanding, It sets the tool with G10 to the standby filament temp instead using M568 and the R option. I do that manually via the start code now, like this:

M568 P0 R{global.tool0_standby}
M568 P1 R{global.tool1_standby}
M568 P2 R{global.tool2_standby}
M568 P3 R{global.tool3_standby}

That works so far and I'm happy. But now comes Prusa into the game. The slicer change the temperate of the tool to standby temp now. That should not be a problem because I changed the standby in the start code. You see the "T1" than which does the tool change drill. Next is a G10 with P1 which is OKish. And the next M116 is my problem.

[...]
G1 E-1 F7200
; Filament-specific end gcode
G10 S100 P0 ; set temperature ;cooldown
T1
; Filament gcode
G10 S215 P1 ; set temperature
M116 ; wait for temperature to be reached
[...]

The M116 makes the printer to wait till the previous tool has reached its designated temperature which is the standby temp than (100°C in this case). That confuses me a bit. I understood M116 that it does not wait for "parked" tools since 3.5 anymore:

Note that in v3.5, the scope of tool heaters to wait for is limited to the heaters of the currently selected tool of the selected motion system.

I'm not sure how to overcome that to be honest. The only thing I can think of is to change the main temperature back to the printing temp via the tfree script. But not sure to what will lead me that.

Any ideas?

Cheers, Chriss

@gloomyandy Yes, I saw Davids configs indeed. I use many of his plastic parts for my Hemeras and did some modding on them. But thanks for bring them back up.

I always struggle a bit with using other peoples configs to be honest. I like to understand how things work in detail. And this printer is not a new build, I convert a RR VCore into a toolchanger, so I have a working config and need to add the toolchanging "only". Anyway, I used Davids settings for the coupler and some more ideas. But you are right, I have overlooked the G53 in his tools related files.

Cheers, Chriss

@engikeneer Thanks for the tip with G53, that is indeed what I was looking for. I id implemented "my way" in the meantime which simply sets the offset to x0y0 in the tool files. But that is a ugly hack indeed.
I had a look at the e3d's git repo to get some ideas how they did it. And they do not use they do not use the G53 there, which is a bit surprising. The command may be to new for their retired product.

Anyway, I will work on the calibration for now and will play with the G53 later.

@droftarts I'm a bit confused about the concept behind that offset to be honest. My tools get picked up and dropped off correctly as long as I have no offset configured.
It turns into a nightmare if I have offsets configured for obvious reasons.
So I tend to change the offset now in the tpost file and turn it back to X0 Y0 in the tfree file but that seams to me like a ugly hack. It would be far more convenient if the offset would be removed automatically removed when the tfree gets executed.

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...