Topics created by customPrint

@sebkritikel: yeah changing the X to U made all the difference . D'oh! seems stupidly obvious now.

@o_lampe: Made the changes and added the second tool screen grab below.
Config o_L.png

All is working as I expect, on to the next steps of my custom testing.

Again thanks for the time to look at my code.

-Peter

@customprint
For the RRF configuration tool a 'custom printer' begins by adding a second extruder on an independent axis. It's not able (yet) to sort out the best logic way to put the M-codes in the right order.
"M584 before M669" is mentioned somewhere in the gcode-dictionary.

@fcwilt Right and understand what you are saying.

I built my sensors and mounts, so obviously, was following the wires closely. I ended up using ribbon cable that I had, so there's no color code, just notes stating what they are.

I would have done the same thing that you did otherwise.

That all sounds normal!

The default homing files (homex.g, homey.g etc) usually have a command in them to raise Z a little bit (5mm I think) so that it will clear anything on the bed (e.g. a print!). Have a look in your homing files and you'll see what it ius actually doing when you click the button in DWC 🙂

RE the drive mapping, the '0.x' thing is something new to the Duet3 hardware. The '0.' is the CAN address, so if you also had an expansion board set at address '2' you would map the drives on that with an M569 P2.1 etc. The older Duet2's (Duet Wifi & Ethernet) don't have the CAN expansion so don't use this notation. Also, I think if you miss out the '0.', it just assumes your addressing the main board, so in your case it probably won't make any difference.

I am.

Thanks again