Duet 3 mini 5+ network problems

j3dk

undefined Why is my printer suddenly disapeared from my LAN? One night I turned it off and the next day when I turned it on it was disapeared from the IP-adress it had the day before and the control led for the web server was on.
I scanned my LAN but could not find it. Now I have tried everything described in the documentation, several times. The only thing that happens is the web server led turns om but can't connect to it from the IP, YAT says it have. When I try to connect to it I can't thoug the control Led was on and when I scan my LAN, I get this message

what is going on?

jay_s_uk

@j3dk can you get an output of M122 through YAT with the webserver (M552 S1) enabled?

j3dk

@jay_s_uk Yes and I get hte following result:
M552 S1
ok
WiFi module is connected to access point SecureNest, IP address 192.168.87.110
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: RAKRW-A196U-D65J0-40KMW-LU03Z-7FDQQ
Used output buffers: 1 of 40 (2 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 105696 of which 60 recycled
Never used RAM 35224, free system stack 168 words
Tasks: NETWORK(ready,15.0%,385) HEAT(notifyWait,0.0%,366) Move(notifyWait,0.1%,334) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.0%,124) MAIN(running,84.0%,426) IDLE(ready,0.1%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:05:29 ago, cause: reset button
Last software reset at 2021-09-28 16:31, reason: User, GCodes spinning, available RAM 35224, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 329682, completed 329681, timed out 0, errs 0
Step timer max interval 737
MCU temperature: min 28.2, current 29.7, max 29.7
Supply voltage: min 0.5, current 0.6, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 63954, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 1: position 63954, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 2: position 63954, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 632817408
Slowest loop: 4.95ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 2965, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 1648/0/0
Tx timeouts 0,0,1647,0,0,1316 last cancelled message type 4514 dest 127

=== Network ===
Slowest loop: 20.99ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
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.25
WiFi MAC address f0:08:d1:02:eb:6b
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 25464
WiFi IP address 192.168.87.110
WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

jay_s_uk

@j3dk can you update to DuetWifiServer 1.26?
You can find it here https://github.com/Duet3D/DuetWiFiSocketServer/releases/download/1.26/DuetWiFiServer.bin

j3dk

@jay_s_uk Yes, but I still can't find it on the given IP from YAT

dc42

@j3dk does it respond to ping requests to that IP address?

j3dk

@dc42 Yes and now it's online again I don't know what and why but now I have found it on a totally different IP that not existed yesterday.
Thanks a lot for your help and fast respond time.

Jens Kej

oliof

@j3dk you may want to look into how to "reserve" an IP address for a given device on your WiFi router. That will give you more stability.

j3dk

@oliof Yes ,you are right, I just had this thought last night....