Topics created by jjude

@jjude how are you configuring the filament changer motors? if you are configuring them as axes rather than extruders then those will be the unhomed axes that are causing the issues.

If you need to keep them as axes rather than extruders then either home them, or send G92 A0 B0 C0

or whatever the axes are to se them to a known position (does not need to be 0).

See M290 in the gcode reference

I don't think there is any inherent problem with updating for a CNC. There's a few improvements actually.

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.3/Duet2and3Firmware-3.4.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.4/Duet2and3Firmware-3.4.4.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

@jjude https://github.com/Duet3D/Duet3-Tool-Distribution-Board

Maybe a table of features may help you decide.

https://docs.duet3d.com/en/Duet3D_hardware/Hardware_overview

@jjude

https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests

rr_gcode should work for you

@jjude
Yes it does have to be defined in config.g
See the release notes and docs
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m80-atx-power-on