@droftarts You rock!! Thank you.

When calibrating my Z probe (BLTouch), I accidentally sent a G30 command without ensuring that the head was high enough for the probe. Doing this causes the probe to go into a blinking failed state. I'm wondering if there is a g-code that I can send to reset the probe so I can raise the head and try again. I try sending M999 and that doesn't do anything. The only way I have found to reset the probe's error state is to power down the machine and power it back up.

I'm hoping there is a command that I can send without doing a power-cycle.

Thanks,
Preston

@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
"

@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.

@bearer said in Received Duet2 WiFi with DOA WiFi:

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

Not just "mostly dead?"

@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

@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

@bearer said in Received Duet2 WiFi with DOA WiFi:

thank you so much for your response and help. When I send M122 I don't see anything that indicates wifi firmware version (printout below). I also tried to send the commands that you suggested and when I send the M588 command I get "M588: Failed to reset the WiFi module to factory settings". I then tried M552 and it still gives "WiFi module is being started"

M122 response:

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 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: 256
Never used ram: 11676
Tasks: NETWORK(ready,1876) HEAT(blocked,1232) MAIN(running,3824) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:04:13 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 42.9, current 48.7, max 49.0
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 392271515
Slowest loop: 100.44ms; 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 assembling a command 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.17ms; 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 starting
WiFi module is disabled
Failed messages: pending 0, notready 1, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok

@prestonthayne

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-12-13b1
                                 ok
                                   WiFi module is being started
                                                               ok
                                                                 WiFi module is being started
             ok
               WiFi module is being started
                                           ok
                                             WiFi module is being started
                                                                         ok
                                                                           WiFi module is being started
                       ok
                         WiFi module is being started
                                                     ok
                                                       WiFi module is being started
   ok```

I'm so sorry. I didn't mean to mislead. These are screenshots of what I got before I upgraded. After upgrading I get the same results (except it does show "...FIRMWARE_VERSION: 2.05...).