Solved DUET2 does not connect

[amimafe]

Hi,

I have a machine running DUET2 and I connect to it via a TPLINK router. This router takes almost 2 minutes to start the wifi every time I start the machine.
I think my duet board makes a couple of attempts to connect to the wifi and as it does not detect it, it stays without connecting.
Is there any way to force the DUET2 board to keep trying to connect until it detects the wifi?

Thanks!

[Phaedrux]

What is the signal strength?
Can you send M122 and share the results?

Ideally we'd want to solve the problem connecting and then if that isn't possible you could likely use conditional gcode and the daemon.g file to try reconnecting.

[amimafe]

@Phaedrux

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.4 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2022-10-20 16:17:41
ok
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S4-6JKF4-3SD6L-9U1AL
Used output buffers: 1 of 26 (1 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 74624 of which 0 recycled
Never used RAM 13596, free system stack 166 words
Tasks: NETWORK(ready,12.4%,363) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,86.1%,438) IDLE(ready,1.5%,30), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:01:01 ago, cause: power up
Last software reset at 2023-08-07 10:22, reason: User, GCodes spinning, available RAM 13596, slot 0
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 25.5, current 30.0, max 30.2
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 2160390490
Slowest loop: 4.03ms; fastest: 0.18ms
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, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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: 11.45ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
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.27
WiFi MAC address 48:3f:da:a6:ed:aa
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 26704
WiFi IP address 255.255.255.255
WiFi signal strength 31dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

[amimafe]

This is the result of sending the m122 code to the duet board.
It appears connected as an access point. Is this normal?

[amimafe]

@Phaedrux

I think I have been able to solve it by forcing it to connect to the network I want, adding the command M552 S1 "My network".
Before I only had the M552 S1 command, without the network.
Thanks for your time and help. I hope this can help others who have the same problem.

[dc42]

@amimafe I'm glad you solved it.

If you don't specify the name of the access point that you want to connect to, then RRF will perform a scan looking for access points in its list. If there is more than one in its list that is available, it will connect to the one with the strongest signal. So it appears that there is another access point in the list that sometimes has a stronger signal than the one you want it to connect to. Use M587 with no parameters to display the list. You can use M588 to delete any unwanted entries.