Wifi not working after a while
-
Hello,
i have some trouble with my Duet 2 Wifi.
I am able to access my printer via web, wifi and via usb, YAT.After a while the wifi connection gets interrupted and i cannot access the printer via web anymore. If this happens i can use USB and YAT to send M552 S0 and M552 S1, to reconnect via wifi. Any ideas why this may be happening?
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.6 (2023-07-21)
Duet WiFi Server Version: 1.27M122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S8-6J1FA-3S86M-9BKBF
Used output buffers: 1 of 26 (13 max)
=== RTOS ===
Static ram: 23896
Dynamic ram: 75212 of which 36 recycled
Never used RAM 9408, free system stack 110 words
Tasks: NETWORK(ready,64.3%,215) HEAT(notifyWait,0.1%,277) Move(notifyWait,3.0%,284) MAIN(running,32.3%,408) IDLE(ready,0.3%,30), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 03:22:52 ago, cause: power up
Last software reset at 2023-11-21 21:39, reason: User, GCodes spinning, available RAM 9932, 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 31.1, current 32.2, max 47.0
Supply voltage: min 10.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/40/40, gc cycles 0
Events: 4 queued, 4 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-11-22 21:07:45
Cache data hit count 4294967295
Slowest loop: 300.20ms; fastest: 0.15ms
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 7.8ms, write time 37.3ms, max retries 0
=== Move ===
DMs created 83, segments created 28, maxWait 2187008ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 560, completed 560, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 6], 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 0 -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: 254.08ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Interface state: active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 4
WiFi firmware version 1.27
WiFi MAC address cc:50:e3:15:60:78
WiFi Vcc 3.32, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25952
WiFi IP address 192.168.0.8
WiFi signal strength -63dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
@huge
Is your wifi 2.4 gigs. The diet 2 only supports 2.4 not 5.0. Or bonded wifi. It will drop the signal. I have many cameras and other devices that do this so I had to create a 2.4 network.
Might look into that -
@ecnsupplies
It actually is 2.4/5.0 will give it a try to use only 2.4.
Thanks -
It seems that sometimes routers with 2.4/5ghz networks if they are unified as one it will try and push some clients to the 5ghz band when they should not. It's called band steering. It may think the Duet should be on the 5ghz when it actually doesn't support it at all. Creating a separate 2.4ghz network and have the Duet use that may help.
