Duet2 WiFi problem after update to RRFv3.4.1

bramerrf

I had my E3D Toolchanger running nicely on RRF v3.0 and (stupidly) decided to upgrade to RRFv3.4.1 As far as I can tell the upgrade ran with no issues but after a restart the DWC interface does not open and I do not have a WiFi connection.

At start up I get :-

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1
Executing config.g… HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Macro file config-override.g not found
Done!
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.

Then running M114, M115 and M122 I get the output below.

M114
X:0.000 Y:0.000 Z:0.000 C:0.000 E:0.000 E0:-0.0 E1:-0.0 E2:-0.0 E3:-0.0 Count 0 0 0 0 Machine 0.000 0.000 0.000 0.000 Bed comp 0.000
Ok

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.1 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2022-06-01 21:05:38
Ok

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MSD-6J9DD-3SN6Q-1STH9
Used output buffers: 1 of 26 (1 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 77720 of which 0 recycled
Never used RAM 10500, free system stack 193 words
Tasks: NETWORK(ready,7.0%,521) HEAT(notifyWait,0.1%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,92.8%,437) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:21:41 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 0
MCU temperature: min 31.6, current 36.8, max 37.1
Supply voltage: min 0.5, current 0.5, max 1.5, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5: ok, SG min n/a
Driver 6: ok, SG min n/a
Driver 7: ok, SG min n/a
Driver 8: ok, SG min n/a
Driver 9: ok, SG min n/a
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 101.24ms; fastest: 0.15ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== DueX ===
Read count 1, 0.05 reads/min
=== Network ===
Slowest loop: 0.41ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

WiFi -
Network state is starting2
WiFi module is disabled
Failed messages: pending 0, notready 1, noresp 0
Socket states: 0 0 0 0 0 0 0 0
Ok

M587
Failed to retrieve network list: another SPI transfer is pending
ok

The WiFi module has its blue lit up but the module is not talking.
If I do network scan it is not there.

Any ideas on how to proceed from here will be much appreciated.

jay_s_uk

@bramerrf said in Duet2 WiFi problem after update to RRFv3.4.1:

Supply voltage: min 0.5, current 0.5, max 1.5, under voltage events: 0, over voltage events: 0, power good: no

you seem to have little to no voltage?

but anyway, run

M552 S0
M997 S1
M552 S1

Phaedrux

How did you do the update?

bramerrf

@jay_s_uk
Since I cannot connect using the DWC I used a terminal emulation program. The results are:-
M552 S0
ok
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok
M552 S1
Turn off the current WiFi mode before selecting a new one
ok

bramerrf

@phaedrux
with the 3.0 firmware loaded the DWC was working. So I uploaded Duet2and3Firmware-3.4.1.zip using that. As each item was being loaded to registered 100% and did not report any issues.

Phaedrux

@bramerrf said in Duet2 WiFi problem after update to RRFv3.4.1:

Error: M997: File 0:/firmware/DuetWiFiServer.bin not found

You'll have to pull the SD card and place the missing wifi server bin file into the firmware folder and then try sending M997 S1 again to complete the flash of the wifi module.

bramerrf

@phaedrux
Many thanks. I did as you advised and now I have a working printer again.
Your help is very much appreciated.

bramerrf

@phaedrux
I spoke too soon. DWC is working fine now. Theprinter connects and everything looks OK but when I do a 'home all' the Z probe is not working, in that is would prefer to drive itself through the bed.
I did a complete reinstall of Duet2and3Firmware-3.4.1.zip and it completed successfully, no errors reported. Upon restarting the Z probe is still not being cooperative, it does not seem to be activating even though it is flat on the bed.
Can you, please, suggest anything I can try? Previously to all these issues with firmware upgrading the printer was working well with no issues.

bramerrf

@phaedrux
Granpa Pig solution worked. Disconnect printer, shut down completely, have a cup of coffee, turn power back on, restart printer. Z probe now working correctly. Printing a test job right now.
Thanks again.