@phaedrux

Deleted, rebooted, and still get the error messages.

@phaedrux

I think I now recall not wiping all saved SSIDs. I think I just removed the extra one that was showing up. Before upgrading the firmware (since I just upgraded to 3.3 the other day), I decided to see if just erasing the SSIDs would fix it. And it did!

I no longer get any of the error message spam, no more timeouts or blank AP connections and after boot it connects right away to my regular AP. I did this about 10 times in a row with success.

Thanks for your help!

@dc42 Standalone mode.

@phaedrux Any other ideas?

@phaedrux

Deleted, rebooted, and still get the error messages.

I can confirm I'm getting this same behavior. The homez.g file is really simple. I'm running RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode).

; homez.g

M291 P"Click OK when touch probe is ready to home Z" R"Home Z" S3 X1Y1
G90      ; absolute coordinates
G30      ; probe z

My Z probe is setup like this in config.g:

M558 K0 P5 C"^!io4.in" H5 F100 T6000     ; set Z probe 0 to digital switch type, invert and enable pullup resistor
G31 P900 X0 Y0 Z0.5                      ; set Z probe trigger value, offset and trigger height

After pressing HOME Z on the web interface, the G30 command executes and probes my metal touch probe properly and HOME Z turns blue. After it turns blue, two messages pop up with

M292
Error: Homing failed

and

G28 Z
Error: Homing failed

@phaedrux

I think I now recall not wiping all saved SSIDs. I think I just removed the extra one that was showing up. Before upgrading the firmware (since I just upgraded to 3.3 the other day), I decided to see if just erasing the SSIDs would fix it. And it did!

I no longer get any of the error message spam, no more timeouts or blank AP connections and after boot it connects right away to my regular AP. I did this about 10 times in a row with success.

Thanks for your help!

@phaedrux About 30 ft. But when I was putting this together, I was in the same room as the AP and this still occurred.

@phaedrux

I already cleared out the saved list of APs since my board came with one enabled already. Here is my current M587:

17:13:35.161 -> Remembered networks:
17:13:35.161 -> mynetwork IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
17:13:35.161 -> ok

Here is the result of M112 while connected to the blank AP:

17:07:51.722 -> WiFi reported error: network scan failed
17:07:51.722 -> WiFi module is idle
17:07:51.722 -> WiFi reported error: network scan failed
17:07:51.722 -> WiFi module is idle
17:07:54.148 -> WiFi module is connected to access point , IP address 255.255.255.255
17:08:01.132 -> === Diagnostics ===
17:08:01.132 -> RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
17:08:01.132 -> Board ID: DDHUY-P296U-D65J0-40KM8-LF03Z-7NL3U
17:08:01.132 -> Used output buffers: 1 of 40 (40 max)
17:08:01.132 -> === RTOS ===
17:08:01.132 -> Static ram: 102724
17:08:01.132 -> Dynamic ram: 104928 of which 136 recycled
17:08:01.132 -> Never used RAM 35916, free system stack 160 words
17:08:01.132 -> Tasks: NETWORK(ready,12.6%,368) HEAT(delaying,0.0%,420) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.6%,115) MAIN(running,84.4%,578) IDLE(ready,1.5%,29) AIN(delaying,0.8%,273), total 100.0%
17:08:01.132 -> Owned mutexes: USB(MAIN)
17:08:01.132 -> === Platform ===
17:08:01.132 -> Last reset 00:00:14 ago, cause: power up
17:08:01.132 -> Last software reset at 2021-07-07 15:08, reason: User, GCodes spinning, available RAM 35916, slot 0
17:08:01.132 -> Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
17:08:01.132 -> Error status: 0x04
17:08:01.132 -> MCU revision 3, ADC conversions started 14945, completed 14944, timed out 0, errs 0
17:08:01.132 -> Step timer max interval 738
17:08:01.132 -> MCU temperature: min 23.9, current 27.2, max 27.2
17:08:01.132 -> Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
17:08:01.132 -> Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
17:08:01.132 -> Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 753, writes 9, timeouts 0, DMA errors 0
17:08:01.132 -> Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 753, writes 9, timeouts 0, DMA errors 0
17:08:01.132 -> Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 753, writes 9, timeouts 0, DMA errors 0
17:08:01.132 -> Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 752, writes 9, timeouts 0, DMA errors 0
17:08:01.132 -> Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 753, writes 9, timeouts 0, DMA errors 0
17:08:01.132 -> Driver 5: position 0, assumed not present
17:08:01.132 -> Driver 6: position 0, assumed not present
17:08:01.132 -> Date/time: 1970-01-01 00:00:00
17:08:01.132 -> Cache data hit count 29034098
17:08:01.132 -> Slowest loop: 4.39ms; fastest: 0.11ms
17:08:01.132 -> === Storage ===
17:08:01.132 -> Free file entries: 10
17:08:01.132 -> SD card 0 detected, interface speed: 22.5MBytes/sec
17:08:01.132 -> SD card longest read time 3.2ms, write time 0.0ms, max retries 0
17:08:01.132 -> === Move ===
17:08:01.132 -> DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
17:08:01.132 -> === MainDDARing ===
17:08:01.132 -> Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
17:08:01.132 -> === AuxDDARing ===
17:08:01.132 -> Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
17:08:01.132 -> === Heat ===
17:08:01.132 -> Bed heaters = -1 -1, chamberHeaters = -1 -1
17:08:01.132 -> === GCodes ===
17:08:01.132 -> Segments left: 0
17:08:01.132 -> Movement lock held by null
17:08:01.132 -> HTTP is idle in state(s) 0
17:08:01.132 -> Telnet is idle in state(s) 0
17:08:01.132 -> File is idle in state(s) 0
17:08:01.132 -> USB is ready with "M122" in state(s) 0
17:08:01.132 -> Aux is idle in state(s) 0
17:08:01.132 -> Trigger is idle in state(s) 0
17:08:01.132 -> Queue is idle in state(s) 0
17:08:01.132 -> LCD is idle in state(s) 0
17:08:01.132 -> SBC is idle in state(s) 0
17:08:01.132 -> Daemon is idle in state(s) 0
17:08:01.132 -> Aux2 is idle in state(s) 0
17:08:01.132 -> Autopause is idle in state(s) 0
17:08:01.132 -> Code queue is empty.
17:08:01.132 -> === CAN ===
17:08:01.132 -> Messages queued 74, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 74/0/0
17:08:01.132 -> Tx timeouts 0,0,73,0,0,0 last cancelled message type 30 dest 127
17:08:01.132 -> 
17:08:01.132 -> === Network ===
17:08:01.132 -> Slowest loop: 9.28ms; fastest: 0.00ms
17:08:01.132 -> Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
17:08:01.132 -> HTTP sessions: 0 of 8
17:08:01.132 -> - WiFi -
17:08:01.132 -> Network state is active
17:08:01.132 -> WiFi module is connected to access point 
17:08:01.132 -> Failed messages: pending 0, notready 0, noresp 0
17:08:01.132 -> WiFi firmware version 1.26
17:08:01.132 -> WiFi MAC address f0:08:d1:02:b5:d1
17:08:01.132 -> WiFi Vcc 3.32, reset reason Power up
17:08:01.132 -> WiFi flash size 2097152, free heap 25688
17:08:01.132 -> WiFi IP address 255.255.255.255
17:08:01.132 -> WiFi signal strength 31dBm, mode 802.11n, reconnections 0, sleep mode modem
17:08:01.132 -> Clock register 00002002
17:08:01.132 -> Socket states: 0 0 0 0 0 0 0 0
17:08:01.132 -> ok

and same for M98 P"config.g":

17:09:10.052 -> HTTP is enabled on port 80
17:09:10.052 -> FTP is disabled
17:09:10.052 -> TELNET is disabled
17:09:10.052 -> ok

Here is my config.g:

; General
G90                                     ; send absolute coordinates...
M550 P"MPCNC"                           ; set printer name

; Network
M552 S1                                 ; enable network
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet
M453                                    ; Enable CNC mode

; Drives
M569 P0 S1 ; X0
M569 P1 S0 ; X1
M569 P2 S0 ; Y0
M569 P3 S1 ; Y1
M569 P4 S0 ; Z
M584 X0:1 Y2:3 Z4 U0 V1 A2 B3 R0 P3               ; R0 = assume linear, P3 = 3 axes visible
M350 X256 Y256 Z256 U256 V256 A256 B256 I0        ; configure microstepping with interpolation
; calculator: https://blog.prusaprinters.org/calculator_3416
; belt pitch 2 mm / pulley teeth 16
; 256x: 6.25*256=1600 for belts (X and Y)
; Lead screw T8 4 start 2mm pitch, 8mm/rev -- 25*256=6400
M92  X1600 Y1600 Z6400 U1600 V1600 A1600 B1600     ; set steps per mm
M566  X900  Y900   Z60  U900  V900  A900  B900     ; set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000  Z180 U6000 V6000 A6000 B6000     ; set maximum speeds (mm/min)
M201  X500  Y500   Z20  U500  V500  A500  B500     ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z1500 U1500 V1500 A1500 B1500 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; set idle timeout

; Setup dimensions are 24 in x 18 x 3.25 in, but actual dimensions are measured below
; Axis Limits
M208   X0   Y0  Z0 S1                   ; set axis minima
M208 X600 Y440 Z82 S0                   ; set axis maxima

; Endstops
M574 X1 S1 P"io0.in+io1.in"
M574 Y1 S1 P"io2.in+io3.in"

; Z-Probe
M558 K0 P5 C"^!io4.in" H5 F100 T6000     ; set Z probe 0 to digital switch type, invert and enable pullup resistor
G31 P900 X0 Y0 Z0.5                      ; set Z probe trigger value, offset and trigger height
;M557 X15:215 Y15:195 S20                ; define mesh grid

; Heaters
M140 H-1                                ; disable heated bed (overrides default heater mapping)

Here is M122 when connected to my access point:

17:12:15.939 -> WiFi module is connected to access point mynetwork, IP address 192.168.1.87
17:12:27.077 -> === Diagnostics ===
17:12:27.077 -> RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
17:12:27.077 -> Board ID: DDHUY-P296U-D65J0-40KM8-LF03Z-7NL3U
17:12:27.077 -> Used output buffers: 1 of 40 (11 max)
17:12:27.077 -> === RTOS ===
17:12:27.077 -> Static ram: 102724
17:12:27.077 -> Dynamic ram: 104928 of which 136 recycled
17:12:27.077 -> Never used RAM 35916, free system stack 150 words
17:12:27.077 -> Tasks: NETWORK(ready,11.9%,264) HEAT(delaying,0.0%,420) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.7%,115) MAIN(running,85.9%,592) IDLE(ready,0.7%,29) AIN(delaying,0.8%,273), total 100.0%
17:12:27.077 -> Owned mutexes: USB(MAIN)
17:12:27.077 -> === Platform ===
17:12:27.077 -> Last reset 00:00:31 ago, cause: software
17:12:27.077 -> Last software reset time unknown, reason: HardFault invState, GCodes spinning, available RAM 35916, slot 2
17:12:27.077 -> Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041e803 BFAR 0xe000ed38 SP 0x20011e50 Task TMC Freestk 127 ok
17:12:27.077 -> Stack: 200190b0 20011bfc 20001064 e000e000 00000060 00089625 00000000 60000000 00000001 00000000 200117b0 0002cab3 00000004 00000003 200117b0 20011bf4 00000004 41008000 a5a5a5a5 0002cbdb a5a5a5a5 00087e75 a5a5a5a5 00000000 846f0005 c06fff05 9b00000e
17:12:27.077 -> Error status: 0x00
17:12:27.077 -> MCU revision 3, ADC conversions started 31391, completed 31390, timed out 0, errs 0
17:12:27.077 -> Step timer max interval 751
17:12:27.077 -> MCU temperature: min 31.6, current 32.6, max 32.6
17:12:27.077 -> Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
17:12:27.077 -> Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
17:12:27.077 -> Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 31, reads 1613, writes 9, timeouts 0, DMA errors 0
17:12:27.077 -> Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 31, reads 1613, writes 9, timeouts 0, DMA errors 0
17:12:27.077 -> Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 31, reads 1613, writes 9, timeouts 0, DMA errors 0
17:12:27.077 -> Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 31, reads 1612, writes 9, timeouts 0, DMA errors 0
17:12:27.077 -> Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 31, reads 1613, writes 9, timeouts 0, DMA errors 0
17:12:27.077 -> Driver 5: position 0, assumed not present
17:12:27.077 -> Driver 6: position 0, assumed not present
17:12:27.077 -> Date/time: 2021-07-07 17:12:25
17:12:27.077 -> Cache data hit count 60684450
17:12:27.077 -> Slowest loop: 4.35ms; fastest: 0.11ms
17:12:27.077 -> === Storage ===
17:12:27.077 -> Free file entries: 10
17:12:27.077 -> SD card 0 detected, interface speed: 22.5MBytes/sec
17:12:27.077 -> SD card longest read time 3.2ms, write time 0.0ms, max retries 0
17:12:27.077 -> === Move ===
17:12:27.077 -> DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
17:12:27.077 -> === MainDDARing ===
17:12:27.077 -> Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
17:12:27.077 -> === AuxDDARing ===
17:12:27.077 -> Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
17:12:27.077 -> === Heat ===
17:12:27.077 -> Bed heaters = -1 -1, chamberHeaters = -1 -1
17:12:27.077 -> === GCodes ===
17:12:27.077 -> Segments left: 0
17:12:27.077 -> Movement lock held by null
17:12:27.077 -> HTTP is idle in state(s) 0
17:12:27.077 -> Telnet is idle in state(s) 0
17:12:27.077 -> File is idle in state(s) 0
17:12:27.077 -> USB is ready with "M122" in state(s) 0
17:12:27.077 -> Aux is idle in state(s) 0
17:12:27.077 -> Trigger is idle in state(s) 0
17:12:27.077 -> Queue is idle in state(s) 0
17:12:27.077 -> LCD is idle in state(s) 0
17:12:27.077 -> SBC is idle in state(s) 0
17:12:27.077 -> Daemon is idle in state(s) 0
17:12:27.077 -> Aux2 is idle in state(s) 0
17:12:27.077 -> Autopause is idle in state(s) 0
17:12:27.077 -> Code queue is empty.
17:12:27.077 -> === CAN ===
17:12:27.077 -> Messages queued 156, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 156/0/0
17:12:27.077 -> Tx timeouts 0,0,155,0,0,0 last cancelled message type 30 dest 127
17:12:27.077 -> 
17:12:27.077 -> === Network ===
17:12:27.077 -> Slowest loop: 11.39ms; fastest: 0.00ms
17:12:27.077 -> Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
17:12:27.077 -> HTTP sessions: 1 of 8
17:12:27.077 -> - WiFi -
17:12:27.077 -> Network state is active
17:12:27.077 -> WiFi module is connected to access point 
17:12:27.077 -> Failed messages: pending 0, notready 0, noresp 0
17:12:27.077 -> WiFi firmware version 1.26
17:12:27.077 -> WiFi MAC address f0:08:d1:02:b5:d1
17:12:27.077 -> WiFi Vcc 3.31, reset reason Power up
17:12:27.077 -> WiFi flash size 2097152, free heap 25016
17:12:27.077 -> WiFi IP address 192.168.1.87
17:12:27.077 -> WiFi signal strength -75dBm, mode 802.11n, reconnections 0, sleep mode modem
17:12:27.077 -> Clock register 00002002
17:12:27.077 -> Socket states: 0 0 0 0 0 0 0 0
17:12:27.077 -> ok

When I boot my Duet 3 Mini 5+ WiFi, it typically never connects to my network immediately. It will spam

16:24:49.156 -> WiFi reported error: network scan failed
16:24:49.156 -> WiFi module is idle

lots of times and then do either one of two things. The first thing it might do is have an SPI timeout:

16:26:00.168 -> Error retrieving WiFi status message: SPI timeout
16:26:00.168 -> WiFi module is idle
16:26:00.349 -> Failed to change WiFi mode: SPI timeout
16:26:08.217 -> WiFi module is disabled

This requires me to enable the WiFi module again. Or, the second thing it will do (more frequently) is connect to a blank AP and have ip address 255.255.255.255:

16:26:18.009 -> WiFi module is connected to access point , IP address 255.255.255.255

From there, I put the WiFi module into S0 and then back into S1 to start the process all over again.

When a network scan succeeds, I will see my network in the list, but there is sometimes these lines:

16:27:38.753 -> WiFi reported error: Unexpected WiFi state 'idle' while trying to connect to
16:27:38.753 -> WiFi module is idle
16:27:38.788 -> WiFi: ../src/SocketServer.cpp(357): found network
16:27:38.788 -> WiFi reported error: no known networks found

and it continues on and on. Then it does eventually connect to my network if on the current session it hasn't hit the SPI timeout or blank AP problem. On success I get it:

16:28:29.298 -> WiFi: sleep enable,type: 2
16:28:29.756 -> WiFi: wifi evt: 2
16:28:31.469 -> WiFi: scandone
16:28:32.368 -> WiFi: state: 0 -> 2 (b0)
16:28:33.345 -> WiFi: state: 2 -> 0 (2)
16:28:33.345 -> WiFi: reconnect
16:28:33.345 -> WiFi: wifi evt: 1
16:28:33.345 -> WiFi: STA disconnect: 2
16:28:35.563 -> WiFi: scandone
16:28:35.563 -> WiFi: state: 0 -> 2 (b0)
16:28:35.563 -> WiFi: state: 2 -> 3 (0)
16:28:35.563 -> WiFi: state: 3 -> 5 (10)
16:28:35.563 -> WiFi: add 0
16:28:35.563 -> WiFi: aid 7
16:28:35.563 -> WiFi: cnt
16:28:35.563 -> WiFi:
16:28:35.597 -> WiFi: connected with mynetwork, channel 6
16:28:35.597 -> WiFi: dhcp client start...
16:28:35.597 -> WiFi: wifi evt: 0
16:28:35.633 -> WiFi module is connected to access point mynetwork, IP address 192.168.1.87
16:28:35.633 -> WiFi: ip:192.168.1.87,mask:255.255.255.0,gw:192.168.1.1
16:28:35.633 -> WiFi: wifi evt: 3

I've attached a session that shows all of the above (my AP is listed as mynetwork. Any ideas why this is happening?

scan.txt

Edit: FYI my board came with 3.2 and this was happening, I've since upgraded to 3.3 and it is still happening.