Firmware Upgrade Complete Fail
-
I purchased a new Duet 2 Wifi (my 2nd) for a new CoreXY that I am building. When trying to enable sensor less homing I discovered that I needed to upgrade from Firmware 2.03 to at least 3.1. However, I also discovered that I couldn't do this in one go and would have to step to V 3.0 first and then go to 3.2.
During the first step to V3.0 i met up with the missing iap4e.bin problem. After successfully managing this problem I finally got V3.o installed. However, along the way I was constantly having problems with the onboard Wifi module switching off and would have to use my Panel Due and M552 S1 to get it restarted.
So next step was to upgrade to V3.2. This appeared to be going swimmingly my Panel Due showed update complete but my wifi connected PC was still showing updating files.
I noticed that the wifi module blue led was again extinguished so tried sending another M522 S1 but then found the Panel Due was now showing disconnected.Net result I now cannot connect to my board either via the Panel Due or via my PC.
To say that this upgrade process is a complete cluster would be an understatement. I love these boards when they are working but at the moment not so much.
How do I get out of this situation?
-
In FW 3.1+ you need to enable the paneldue in your config.g with
M575 P1 B57600 S1. This is because in RRF3 there are no default pin assignments and settings for anything. It's all generalized. So the PanelDue must be configured.At this point it might be easiest to pull the SD card, add that command to config.g and power up again.
I think the iap problem you originally encountered was from not uploading the complete firmware zip file, so some things were missing.
The best way to update firmware if you still have access to DWC.
If on an older firmware, upload these 3 zip files, one at a time. Don't extract them. Reboot after each.
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.Going forward, you only need the single zip file from the latest stable release. It's a bit messier if you are using beta releases since they don't get a combined zip file.
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 -
Thanks Phaedrux. I copied M575 and M552 into Config G. The board at least now lights up the wifi LED and the Panel Due is now communicating again. Can't get the DWC working yet but I shall work through the configurator and generate a fresh set. Will let you know how I get on.
-
You may need to replace the DWC files in the /www folder to match the version of firmware currently flashed. Use M115 to check the currently flashed firmware version.
If 3.2 is flashed, use: https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/DuetWebControl-SD.zip
Also, your paneldue should be using at least firmware 1.24
https://duet3d.dozuki.com/Wiki/PanelDue_Firmware_update -
I am now going round in circles with this. I have started again from scratch but am halted at Step 7 of the Getting Started Dozuki with this error message:
Error:M587: Failed to add SSID to remembered list: another SPI transfer is pendingI suspect the SD Card is corrupted somehow but don't want to try rebooting it in case I end up wasting hours of work on this.
-
try sending:
M552 S0 ; Disable network module M588 S"*" ; Clear all saved wifi networksFollowed by
M587 S"NETWORKNAME" P"PASSWORD" ; Add duet wifi SSID to remembered networks list M552 S1 ; re-enable wifi moduleAnd if none of that works, send M997 S1 to reflash the wifi module.
If it still complains about SPI transfer, reboot the board.
If you have another SD card you can make a backup now and copy your folders and files over. -
Thanks again Phaedrux. After several more hours of chasing my tail and using two computers and the Panel Due, I think (fingers crossed) I have got my Wifi board and Panel Due back running on the latest firmware versions.
One of the biggest problems was the Wifi module remaining idle every time the machine was re-started. I was using M552 S1 at the start of Config G but then finally changed that to M552 S2 after reading the details of that command.What did surprise me that this board is less than 1 year old but shipped with the 2.03 firmware. The two step process to upgrade was a nightmare for someone not doing this on a regular basis.
It would be nice to think that these boards could have a menu option for checking for firmware updates and then link directly to the latest firmware upgrade via the internet. Again, Github maybe easypeasy for regular users but I found it complex and less than intuitive at best.
Now at least I can get back to setting up this new home made Core XY.
Thanks again for your help.
-
@Pierre52 said in Firmware Upgrade Complete Fail:
finally changed that to M552 S2
..just to clarify are you wanting to use the Duet as the Access point or wanting to connect the Duet to an Access Point?
S2 is for creating the access point, and you need to use M589 instead of M587 to configure the SSID and passphrase for that; that hasn't changed afaik.
-
Glad you're back on track. Maybe post your config.g and the results of M122 just so we can make sure it's all good to go.
-
@bearer Good spotting thanks. Have changed it back to S1 and appears to be working OK
@Phaedrux here is the relevant section of Config .g as it stands at the moment
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Fri Jan 22 2021 13:39:52 GMT+1300 (New Zealand Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Pierre's Core XY" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
M552 S1 ; enable WiFi; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z3400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z300 S0 ; set axis maxima; Endstops
M574 X1 S3 ; configure sensorless endstop for low end on X
M574 Y1 S3 ; configure sensorless endstop for low end on Y
M574 Z1 S2 ; configure Z-probe endstop for low end on ZM122 returns: Reprap firmware for Duet 2 Wifi version 3.2 running on Duet wifi 1.02 or later
Now on to endstop set up and getting it to accept a 220v bed heater with a Thermistor that measures 138k Ohm
