@jay_s_uk if the board is not talking to CAN then the bootloader can only be updated using a Atmel ICE, or another SWD debugging tool that supports the SAMC21. We don't expect our users to possess such a tool.

If you do decide to update the firmware...

If you still have access to DWC. Upload these zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console 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.3/Duet2and3Firmware-3.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip

That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

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

Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3
https://docs.duet3d.com/en/User_manual/Reference/Gcodes

@T3P3Tony Yea I had a stack of orings in there temporarily until I could get a mount drawn up. There was plenty of clearance between the contacts on the board and the hemera.

@dc42 Thank you for the great service. The duet was replaced and works perfectly

@Phaedrux I do eventually want to use the duet in conjunction with a raspberry pi, but they are hard to find right now and if you can find them they are ridiculously overpriced.

@achrn @RogerPodacter There are component son the boards that are rated to 85C so that is an absolute maximum. I suggest an ambient above 50C may require some cooling to the toolboard (e.g. airflow) depending on what stepper currents you are running and the heater current.

@Sindarius now we're talking!

@jay_s_uk thanks - I ordered one today so will see how it goes.

If you're running RRF3.0 or later then you should use M308, not M305.
Those dips look like they may be noise due to a bad crimp or something.
Probably best to check that and to come back wit what firmware version you're using and full config.g

@OwenD awesome! Thanks, l will try tomorrow.

@dc42
Ok got comms sorted. I got this initially
ec6c989e-6c7d-453e-839b-fb3f6f868106-image.png
Looks like the MISO line isnt pulled up locally on the the BTT board. I guess this makes sense as the board is meant to plug into 'step stick port' on a BTT driver board. In all the literature I read from BTT/Biqu makes no mention of pullups or active line jumpering. Any way pulled the MISO line up to 3V via 10k and now I get the following;
24ba278d-01bd-4ecb-87ed-d3a69fce39a0-image.png
DWC is also reporting semi resonable values so now just some tuning and firmer wiring to get the ball rolling. I have a Duet PT100 dtr board coming from filastruda and I dont think ill have it for a week. I also ordered an Adafruit MAX31865 bob that should be here tomorrow so Ill follow up this thread on how that gos.

Huge thanks for this Forum and support, the best 🙂

@Phaedrux Yes, I already have the Duet wifi for a few years on a large format 3D printer with nema 17 and 23 motors, but unfortunately they lose steps due to lack of power, so I'm thinking of using servo motors with the duet wifi. I have not bought any servo yet and by the way I would like you to recommend some servo models that are compatible to do this installation.

@jay_s_uk

Thanks
Now everything works fine.

Thanks for the help.

Best regards

Anders

@dc42 Thank you for the confirmation. This prevents me from having to redo the wiring and firmware moving forward on a hope, lol.

@TRATOON I'm running a cpap blower, so I'm not using a part cooling fan on the toolboard. Port your config and I can take a look at it and see if I think there is anything odd about it.

It may also be your slicer settings. Not sure what slicer you are using, but maybe you have 'cooling fan always on' enabled?

That solution also assumes the endstops are moveable so that they can be positioned to eliminated any skew. If you can't move them, then you would need to split the X axis into two independent axis, home them, and them apply a movement offset to cure any skew, and then recombine to X.

Both methods are shown here: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling

It focuses on the Z axis, but the concept is the same for other axis.

This is exactly what happens when I slice for Marlin instead of RepRap in CURA.

Make sure your slicer is set to RepRap and it should automatically fix the issues as explained by everyone above.

Then yes, you need to switch the - wire to the pin labeled "out1" on the wiring diagram, which is the pwm capable pin.

Attaching the negative wire to ground will just be always on.

@Phaedrux yes there is no seperate network names or channels

@dc42 Yes it slowly creeps down to 223-225 ish