Received Duet2 WiFi with DOA WiFi

Phaedrux

Download these two files and place them on the SD card in the /sys folder with your PC.

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2CombinedFirmware.bin

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWiFiServer-1.23.bin

Rename DuetWiFiServer-1.23.bin to DuetWiFiServer.bin

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWebControl-SD-2.0.7.zip

Extract this zip file to the /www folder.

Now put the SD card back in the duet and power up via USB and send M997 S0:1 in the console to install the main and wifi firmwares.

Then send M122 again after it reboots and post the result.

prestonthayne

@Phaedrux Thanks for your suggestion. I followed your directions and it looks like the sub-version did change from 2.05 to 2.05.1. I however still get the same results.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93428 of which 0 recycled
Exception stack ram used: 304
Never used ram: 11628
Tasks: NETWORK(ready,1876) HEAT(blocked,1232) MAIN(running,3824) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:01:02 ago, cause: power up
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11612 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 40.1, current 47.1, max 47.1
Supply voltage: min 1.4, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 93718842
Slowest loop: 0.16ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.16ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
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
ok
M552 S-1
ok
M552 S0
ok
M588 S"*"
M588: Failed to reset the WiFi module to factory settings
ok

A Former User

edit: seems to be normal output of M122 after M552 S-1. So first try M552 S0 then M122

if still the same, then go with:

could you run M552 S-1 then M111 P14 S1 followed by another attempt at M997 S1 and post what happens?

prestonthayne

@bearer

M552 S-1
ok
M111 P14 S1
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15)
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

A Former User

to quote Monty Python "its dead, thats whats wrong with it"

prestonthayne

@bearer said in Received Duet2 WiFi with DOA WiFi:

to quote Monty Python "its dead, thats whats wrong with it"

Not just "mostly dead?"

A Former User

I'll defer to the Duet people for the final word, but seems the wifi module has ceased to be; its not even connecting to the bootloader. (If the wifi module is okay then the uart on the main processor is toast, either way, RMA methinks)

prestonthayne

@bearer Thanks for your time and expertise (and trip down Python memory lane). I will wait to hear what the Duet people have to say.

Phaedrux

When and where did you purchase the Duet Wifi?

prestonthayne

@Phaedrux I purchased my board from MatterHackers on March 31, 2020. It took me a while to carve out the time to put it in my 3d printer and when I started to get ready to install it, I found that I couldn't get it to connect to my network. On May 4th I reached out to support @ matterhackers and wen't back and forth with them, trying several things to get it working to no avail. They then asked me to post on this forum because the CEO and Chief Designer needed to see a post here about defective boards.

Thanks,
Preston

Here is the first email that I sent to support about this issue on May 4th:
"I purchased a Duet 2 WiFi last month (Order #101-0000102-1607002) and am trying to set it up. I can’t get the WiFi to start up. When I sent the M552 S1 command in terminal it says ok, then when I send M552 it responds with “WiFi module is being started”. It keeps showing that forever (ok, actually I waited 30 min, but in computer 30 min might as well be forever) and the blue light on the wifi module never even blinks on. Incidentally, the WiFi module is quite hot to the touch.

I’m not sure what to try to get the WiFi working. Please advise.

Regards,
Preston
"

dc42

@prestonthayne said in Received Duet2 WiFi with DOA WiFi:

@bearer

M552 S-1
ok
M111 P14 S1
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15)
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

Thanks for that report, it shows that uploading firmware to the WiFi module is not working. I am happy to approve a warranty replacement.