Duet 2 Wifi issue. Wont connect after high voltage warning
-
Hello, any advice would be welcomed here. I was working on setting up a BLTouch on my printer (Ender 3 style cartesian). I was looking at the Duet web interface and saw a high voltage warning (31.4v, should be 24v) and immediately powered off the machine. I want to turn it back on and the wifi module has no LED that is powering on and there is no connection to the wifi (verified with the router to ensure there was no IP address change). I connect the board to a computer via USB. I attempt to turn on the wifi and this is what I am getting:
m552 WiFi module is disabled ok m552 S0 ok WiFi module started m552 WiFi module is idle ok m552 S0 ok m552 WiFi module is idle ok M587 S"Redacted" P"Redacted" Error: M587: Failed to add SSID to remembered list: SPI timeout ok Error retrieving WiFi status message: another SPI transfer is pending Error retrieving WiFi status message: another SPI transfer is pending Error retrieving WiFi status message: another SPI transfer is pendingHere is the M122 command recommended in the troubleshooting guide (fresh after USB connection):
=== 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: 08DLM-996RU-N85S4-7J9F8-3S46K-9VBVP Used output buffers: 1 of 24 (1 max) === RTOS === Static ram: 23876 Dynamic ram: 73544 of which 12 recycled Never used RAM 16984, free system stack 193 words Tasks: NETWORK(ready,6.3%,517) HEAT(delaying,0.0%,386) Move(notifyWait,0.1%,364) MAIN(running,85.9%,639) IDLE(ready,7.8%,29), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 00:01:24 ago, cause: power up Last software reset at 2021-08-19 18:34, reason: User, GCodes spinning, available RAM 11448, slot 2 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 214.0, current 220.6, max 221.2 Supply voltage: min 0.7, current 0.8, max 0.9, 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 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 3570437365 Slowest loop: 0.19ms; 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: 0.2MBytes/sec SD card longest read time 0.0ms, 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 disabled WiFi module is disabled Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485 Socket states: 0 0 0 0 0 0 0 0 okI'd appreciate any help people can provide. Im not sure if its an SD card issue or a burnt out module.
-
Please try sending this
M552 S0 ; disable module
M997 S1 ; flash wifi firmware
M552 S1 ; enable module@justin-0 said in Duet 2 Wifi issue. Wont connect after high voltage warning:
Im not sure if its an SD card issue or a burnt out module.
Does the SD card show it's contents when you put it in a PC?
@justin-0 said in Duet 2 Wifi issue. Wont connect after high voltage warning:
MCU temperature: min 214.0, current 220.6, max 221.2
Is the big CPU chip on the board getting very hot? Does anything else get very hot?
Any idea what might have caused such a voltage spike?
-
@phaedrux I just tried that and the results are below. I think this means that there is an issue with the SD card then, correct? Might just need a reformat and install.
M552 S0 ok WiFi module started M997 S1 Error: M997: File 0:/firmware/DuetWiFiServer.bin not found ok M552 S1 ok WiFi module is idle WiFi reported error: no known networks found WiFi module is idle WiFi reported error: network scan failed WiFi module is idle WiFi reported error: network scan failed Error retrieving WiFi status message: SPI timeout Failed to change WiFi mode: bad reply format version -
What files show up when checking in a PC? The files just might not be in the firmware folder or it can't read the card.
Your m122 also shows an odd speed for the SD card.
interface speed: 0.2MBytes/secThat may mean the voltage spike has damaged the SD card slot. And perhaps more. Is anything else hot?
-
@phaedrux @phaedrux Plugging in the SD Card, I see no issue with reading any files at a first glance. What is the best way to verify the files are correct?
The board has 2 fans on it so I wasn't worried about heat but I probably should have. I touched the "big CPU chip" and it was slightly warm about 10 mins after the high voltage warning. I do remember that the BLTouch board got very hot that was in my hand. Hopefully it didn't fry more things, but it could of.
-
Does the SD card slot get hot? I think it took a hit. Sounds like the SD card is ok.
-
@phaedrux The SD card slot does not get hot. So something about getting the SD card connected to a PC changed something (I did not do anything to the card such as scanning or repairing it). The board will now connect to my wifi (confirmed via router and USB connection). It does not respond to connections to its IP address (via chrome and command prompt ping requests). I'm not really certain what is going on here with the board.
M122 return this now:
=== 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: 08DLM-996RU-N85S4-7J9F8-3S46K-9VBVP Used output buffers: 1 of 24 (1 max) === RTOS === Static ram: 23876 Dynamic ram: 79080 of which 12 recycled Never used RAM 11448, free system stack 191 words Tasks: NETWORK(ready,14.6%,416) HEAT(suspended,0.0%,336) MAIN(running,83.1%,467) IDLE(ready,2.3%,29), total 99.9% Owned mutexes: WiFi(NETWORK) USB(MAIN) === Platform === Last reset 00:01:37 ago, cause: power up Last software reset at 2021-08-19 18:34, reason: User, GCodes spinning, available RAM 11448, slot 2 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 148.3, current 186.6, max 191.8 Supply voltage: min 0.1, current 0.8, max 1.2, 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 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 4056468584 Slowest loop: 300.18ms; 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 52.4ms, 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 = 0 -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: 15.42ms; 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 active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address f4:cf:a2:6e:81:89 WiFi Vcc 2.22, reset reason Turned on by main processor WiFi flash size 4194304, free heap 25968 WiFi IP address 192.168.86.33 WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 ok -
@justin-0 I stand corrected. After powering off and on again, it no longer connects or has the wifi module turn on.
-
Can you try going through these steps?
https://duet3d.dozuki.com/Wiki/SD_Card#Section_Troubleshooting_SD_Card_issues
And these
https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respondThe MCU temp being reported must be way off then if it's not warm to the touch.
This is with only USB connected? Have you tried connecting with VIN from the PSU? Have you checked the PSU VIN output with a multimeter?
-
@phaedrux I ran through the two links you had. The duet was good on the https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond up to the diag LED. It is constantly lit when connected to the board is powered by the PSU.
I tested this by putting an old know cood config file, no change. I removed the SD card and no change. Reset button is not stuck on the board.
The board shows up on the PC and communicates with the PC.
It seems that the DIAG LED is an indicator that something got fried.
Running through the https://duet3d.dozuki.com/Wiki/SD_Card#Section_Troubleshooting_SD_Card_issues
M122 yields a .2 MB/s. This indicates a bad processor or SD card slot according to the link.
Running a file transfer test yields:M122 P104 s10 Error: Failed to create folder 0:/gcodes in path 0:/gcodes/test.tst Error: M122: Failed to create fileJust to rule out any SD card issue, I bought a new SD card with 10MB/s write and 100MB/s read, the same issue occurs. There is no visible damage to the SD card pins.
One thing that none of the guides mention that I think maybe another clue is the LED on the wifi module never lights.
From here, it seems those articles are pointing to a SD card and/or a processor issue on the board.
Do you know if there is anything else I can do?
Is there anything that Duet is able to help me with on the board if it is an SD card reader or processor issue?I really appreciate your expertise and help!!
-
Do you see any damaged components on the board? Can you post some photos? Do you have any idea what the high voltage event could have been? Did the PSU fail? Did something get shorted?
-
@phaedrux I dont see any damaged comonets on the boar. I'll attach some images.
The high voltage warning came from the duet at 31.4V. It could have come from the power supply. It came from an ender 3. I don't think the PSU has failed. I will have a multimeter later today and check output voltages.
I don't think any items got shorted and there was no sounds of shorting.
-
I'd suggest taking it out completely, disconnecting everything, and checking with just usb connected again. Get some well lit close up shots.
-
@phaedrux Okay will do. Just checked PSU voltage, its 24v. Measured it 10 times, 1 a min. range was 23.8-24v
-
@phaedrux Connecting the board via USB with not connections has it working like it was new out of the box
-
@justin-0 when RRF reports that the VIN voltage is abnormally high, it usually means that the 3.3V rail voltage is low because the ADC uses the 3.3V rail as the reference. Typically this means that the 3.3V rail is overloaded, either by an external device or by an on-board device. So check whether any components are getting hot, in particular the 3.3V regulator, the SD card, the WiFi module, and the main processor.
If nothing is getting hot, reconnect VIN power and see whether VIN is still reported as being abnormally high.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 @Phaedrux Nothing gets hot when connected over USB. I'm connected to the PSU and the board is working with not issues (I have power cycled everything a few time to make sure). Vin is reported at 24.3 by the board and 23.8 by multimeter. I don't have time to reassemble printer today, but will do that tomorrow port by port to make sure the board will still function. I appreciate your help!
-
Something may be shorting out then. Slowly add back things one at a time to see if you can find what it was. Hopefully nothing got fried.
-
@phaedrux said in Duet 2 Wifi issue. Wont connect after high voltage warning:
Slowly add back things one at a time to see if you can find what it was.
^This. Best practice is to plug in each connector with power off, turn it on briefly and read the voltage or watch for the error message, quickly shutting it off if there's a problem. It's now been isolated to whatever cable was plugged in last, so unplug the far of that cable, and power up the board again. If the problem reoccurs, it's in the cable, and if not, it's in whatever that cable connects to.
-
Also, let your eyes do some testing first. Look for signs of scorching or browning on connectors and components and wires.
