@dc42 Thank you so much for clearing that up for me. I just want to ensure I have all the information needed to fill out the configurator correctly. Thank you.

@phaedrux awesome look forward to the new version.

If you can I would write

" the intention has always been that it gets you a starting point for syntax and command layout and then you would go through the customization process"

at the start of the configurator for other new users like me who assume that it is 100% all you need

@manjoel where is it preventing you from entering those values? Most likely, one of the other values you have entered is not compatible with those values.

4af66478-4635-45d9-affd-12f91b456af8-image.png

I'm also in need of this, thanks

@All

Is there someone with a solution for this issue?

Good question. Will see about that. In the meantime you can choose io1 and then edit the config.g after you've got it in place using the web interface to use io0.

There is some planned work for the config tool coming yes.

@chuser said in correctly Config for my Fan:

@fcwilt @Phaedrux Thank you very much for the help.

I have measured the power current of the fan and found that it is too much. The current of the fan rised above 1A after a short time.

I have replaced the fan and now everything works.

So it turned out to be the fan that was causing the reset as we suspected.

Glad to hear you got it all sorted.

Frederick

It's a simple switch at heart. Perhaps that could be made clearer on the config tool. I'll bring that up.

Yes the limitation for assigning multiple drivers to a single axis will eventually be going away once the config tool switches over to using the object model.

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.

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)

Achsen Motoren.png
a7045a9d-7e82-4774-a90d-28814c8db929-grafik.png

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

@agf998 said in Z axis homing problem:

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.

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/Duet2and3Firmware-3.2.zip
That will get your firmware and DWC up to date.

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

I have now figured everything out thanks to all of your support and help.

Thank you very much for replying quickly and for your time
Have a good day

Sincerely George

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

Thanks for the note, this has been fixed in version 3.2.2.

@chrishamm Merci beaucoup. Ca fonctionne.👍 👍 👍

Thanks, I've got a fix ready which I will apply in approx 30 minutes. For now, either clear your browser cache or turn off the "Get RRF" and "Get DWC" options on the last page.

The new heater tuning algorithm in 3.2 can take a long time. Just let it finish.

https://forum.duet3d.com/topic/19761/new-heater-tuning-algorithm