Duet 2 Ethernet Firmware failure
-
I am currently on firmware version 2.0.4 and am trying to upgrade to version 3.4. I have tried a couple different ways, starting with the web application. I uploaded the .zip I downloaded from the repo and it started updating the board but I think it timed out or something as it lost connection and now I cannot reconnect to the web app. It just sits there saying "Connecting".
My USB still works and I can connect via the terminal. So i tried the fallback method number 1, downloaded the firmware files to the sys folder on the SD card, then I ran the M997 S0 followed by M997 S1. The USB port recycles, i reconnect and check the firmware version but it is still 2.0.4. Shouldn't it be 3.4.0? Those are the files I added to the SD card, but I dont think it is actually flashing the controller. I still cant access the webapp, even though I can ping the device. Any thoughts?
-
You can't go there directly. You need to make a few stops along the way.
If you still have access to DWC. Upload these 3 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.0/Duet2and3Firmware-3.4.0.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.xFor your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/StartBackup 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 -
@phaedrux I no longer have access to DWC. But I can still access the terminal port. Can I manually extract those folders and put them in the sys folder and run the M997 command?
-
@mcbrown90 Yes. But if you can connect via USB, you can skip all of the above by erasing the firmware and installing 3.4 directly using Bossa. See https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts Ok, I was able to update successfully. I just did one at a time manually via the usb. Thanks for the help. Also i am looking to use uart 0 (PanelDue port) and control the motors from there. Is there any documentation on how to do this? Meaning configuration reequipments and if Gcode commands are not supported then what is the protocol?
-
@mcbrown90 said in Duet 2 Ethernet Firmware failure:
Also i am looking to use uart 0 (PanelDue port) and control the motors from there. Is there any documentation on how to do this? Meaning configuration reequipments and if Gcode commands are not supported then what is the protocol?
I'm not exactly sure what you're asking.
-
@phaedrux Is there a way I can utilize UART 0 to control the printer motors
-
I'm not sure. Could you use the USB terminal instead to send gcode commands?
What is your application?
-
@phaedrux Sorry did not see your response. I am trying to use a micro to send commands to the motor controller directly with a uart. I did manage to get the PanelDue port to work with command line commands, just changed protocol parameter. Just curios, why doesn't it provide acknowledgements to commands? M84 for example returns "ok" when received on the other port, where as the PanelDue port does not. Is there a way to enable command ack or nacks there?
-
@mcbrown90 said in Duet 2 Ethernet Firmware failure:
@phaedrux Sorry did not see your response. I am trying to use a micro to send commands to the motor controller directly with a uart. I did manage to get the PanelDue port to work with command line commands, just changed protocol parameter. Just curios, why doesn't it provide acknowledgements to commands? M84 for example returns "ok" when received on the other port, where as the PanelDue port does not. Is there a way to enable command ack or nacks there?
It may be best to start a new thread for your questions on that topic. Will get more eyes and since it's not related to your current topic title/issue.
