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.
Well I already did that before even thinking to post something here..
My problem is that I don't find exact information about the used current, microstepping etc. for the axes motors or the extruder motors.
The models are:
Extruder 0: 17PM-K342BG03CN
Extruder 1: 17PM-K142BN07CN
X Motor: KV4239-T2B011 (KV4239-T2BX047)
Even though the Model name is a bit similar I'm not quite sure if these data are the right and would like to compare the settings with someone who already did the upgrade (read some posts about others but unfortunately didn't find anything useful).
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet Ethernet 1.02 or later + DueX2
That firmware is quite out of date at this point. Just about 3 years.
I would suggest that our first step is updating the firmware to at least 2.05.1. This would get you at least on the most recent V2 firmware and won't require any config changes like the update to V3 would. Though I would suggest that since this is a new build it's probably a good idea to update to V3 and start with a fresh config from the config tool, and then manually updating the config to suit your printer. This would also resolve the errors with your tools.
After entering the command the SD card can be selected but the connection is not permanent. if I print something on the es card and the connection is interrupted, the board restarts. but it doesn't matter, I use the upload & start function