Unable to start WIFI Module

Handiwork7

Following the upgrade tutorial from Ooznest firmware update. The WIFI Module has stopped working.

Duet 2 Wifi (PCB Version 1.04c)
Wifi Module ESP 07S

It claims to be "starting" but never does.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok





M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JKF4-3SN6L-9U4AK
Used output buffers: 1 of 24 (12 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 74172 of which 176 recycled
Never used RAM 13336, free system stack 185 words
Tasks: NETWORK(ready,8.0%,517) HEAT(delaying,0.0%,386) Move(notifyWait,0.1%,364) MAIN(running,91.9%,431) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:07:57 ago, cause: software
Last software reset at 2025-01-07 13:23, reason: User, GCodes spinning, available RAM 13512, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 29.7, current 30.2, max 30.4
Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/24/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 6.90ms; fastest: 0.13ms
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, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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.
=== Network ===
Slowest loop: 0.18ms; 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 0, noresp 1
Socket states: 0 0 0 0 0 0 0 0
ok

jay_s_uk

@Handiwork7 can you try reflashing the wifi firmware?

M552 S0
M997 S1

Handiwork7

@jay_s_uk said in Unable to start WIFI Module:

M552 S0

M552 S0

ok

M997 S1

Trying to connect at 230400 baud:  failed
Trying to connect at 115200 baud:  failed
Trying to connect at 74880 baud:  failed
Trying to connect at 9600 baud:  failed
Error: Installation failed due to comm write error
ok

M997 S0
Shutting down USB interface to update main firmware. Try reconnecting after 30 seconds.

This did not fix the issue.

jay_s_uk

@Handiwork7 that doesn't look good.
when and where did you purchase the board?
one for @Phaedrux or @droftarts

Handiwork7

@jay_s_uk

This is a Workbee CNC, purchased from a private seller. The unit was working following an upgrade directly from workbee then reboot and all is dead.

droftarts

@Handiwork7 If it was working before, an RRF firmware update should kill the WiFi module, and neither should a WiFi module update.

Do you have a PanelDue connected? If so, please either switch it to the 'Setup' page or disconnect it while updating the WiFi firmware (the serial communications from the PanelDue can interrupt the update process).

Ian

Handiwork7

@droftarts

Sadly, I do not have the PanelDue.

droftarts

@Handiwork7 Try this:

Turn off the Duet, remove the SD card.
Turn on the Duet and connect via USB. This will mean the WiFi never gets initialised.
Put the SD card back in, and send M21 to mount the SD card.
Then try either:
- sending M997 S1, or
- start again, but send M552 S0 to turn the WiFi on in idle mode, then send M997 S1

This was probably caused by a failed WiFi firmware flash during the main firmware update, so the WiFi firmware is only partially there. Possibly the WiFi firmware flash took longer than expected, and the Duet reset before it had finished.

When you turn the Duet on, I think the WiFi module gets hung up trying to enable networking with the M552 S1 command in config.g, so removing the SD card means this doesn't happen. Hopefully then the Duet can flash the WiFi module, as it should be off, or idle.

Ian

Handiwork7

@droftarts Thank you!

Earlier today I replaced the WIFI Module with the Ethernet module from a faulty board I had years ago (drivers died, I kept the board for spares). (Save make/version etc).

The Ethernet module was recognized, I can set the IP etc. Sadly, It's still showing "Link Down" with the Ethernet cable connected.

I can only assume at this point one of the traces are damaged on the PCB and the signal is not making it back to the atmel chip.

I do have a full re-flow station and microscope. Just not sure if its worth the dive vs go just buy a new one.

T3P3Tony

@Handiwork7

The schematic for your Duet 2 board is here so you could probe the connections back to the MCU and see if there are any issues there.

https://github.com/Duet3D/Duet-2-Hardware/blob/371c656c226417c3ee1e4c78887d536f61ac9edc/Duet2/Duet2v1.04/Duet2_1.04c_Schematic.pdf