Is my DuetWifiServer.bin properly updated?
-
Hello,
trying to troubleshoot another problem I discovered a possible cause to a recurring annoyance of mine: the connection to the webinterface tends to reset itself every so often. Haven't bothered so far as more pressing things, but here's what I have: at random intervals I see this in the logs:
Digging in, I find that the while everything else is at RRP 3.5.0-rc3, the Wifi system is listed DuetWiFiServer 2.1beta6. I can't find what the exact last version needs to be, but I downloaded the Duetwifiserver.bin listed in RRP 3.5.0-rc3 and uploaded it (using webinterface): when restarting it stays at v2.1beta6
Can you tell me what version there should be?
Thanks!
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3 (2024-01-24 17:56:24) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MS8-6J9FL-3SN6N-TVVR9 Used output buffers: 9 of 26 (26 max) === RTOS === Static ram: 23224 Dynamic ram: 77664 of which 0 recycled Never used RAM 12256, free system stack 182 words Tasks: NETWORK(1,ready,13.4%,221) ACCEL(6,nWait 5,0.0%,346) HEAT(3,nWait 5,0.1%,327) Move(4,nWait 5,0.0%,360) DUEX(5,nWait 5,0.0%,24) MAIN(1,running,86.0%,742) IDLE(0,ready,0.5%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:02:58 ago, cause: power up Last software reset at 2024-02-11 15:48, reason: User, Gcodes spinning, available RAM 8392, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU temperature: min 20.3, current 27.0, max 27.2 Supply voltage: min 24.1, current 24.3, 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: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2024-03-27 08:02:25 Cache data hit count 4294967295 Slowest loop: 15.30ms; fastest: 0.19ms 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 2.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === 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 === Movement locks 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 idle 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 Q0 segments left 0 Code queue 0 is empty === DueX === Read count 1, 0.34 reads/min === Network === Slowest loop: 15.13ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta6 MAC address ec:fa:bc:2d:df:4f Module reset reason: Turned on by main processor, Vcc 3.39, flash size 2097152, free heap 43068 WiFi IP address 192.168.178.30 Signal strength -44dBm, channel 1, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
-
@phoenix the WiFi server version isn’t aligned to the RRF/DWC version. 3.5.0-rc3 was released with DuetWifiServer 2.1beta6, but as @jay_s_uk points out, there is a newer 2.1beta7 version that’s resolves some connection issues. I’ve been using this and haven’t had a connection failure (apart from poor WiFi signal, but that’s my WiFi location’s problem). So please try that, and report back if your connection problem persists.
Ian
-
@droftarts Thank you for the pointer - I have updated it but can't see a difference.
-
@phoenix said in Is my DuetWifiServer.bin properly updated?:
I have updated it but can't see a difference.
Can't see a difference in the version number, or can't see a difference in operation i.e. you're still getting the error messages?
Ian
-
@droftarts Version is now showing 2.1beta7.
No change in the behavior. It's mostly annoying when doing config work, as randomly the interfaces loses connection (and reconnects within a second), but it closes the edited config file wihtout saving obviously. -
@phoenix said in Is my DuetWifiServer.bin properly updated?:
Signal strength -44dBm, channel 1, mode 802.11n, reconnections 0
I notice it says it's on channel 1. This can cause problems if you're using a Duet 2 WiFi with an aerial that's built into the WiFi module PCB rather than an external one. From https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshooting
Try changing the channel on your WiFi router. Most routers default to Auto, but can be set to use a fixed channel instead. The channels overlap, so it is common to use channel 1, 6 or 11. This may also help if another device is causing interference.
Particularly if using channel 1, change the router WiFi channel. Duets with onboard WiFi antennas may be more susceptible to interference from the Duet itself at this frequency. Try channel 6 or 11.Ian
-
Can you try the older 1.27 release to see if the behaviour remains?
https://github.com/Duet3D/DuetWiFiSocketServer/releases/download/1.27/DuetWiFiServer.bin
-
@Phaedrux Version 1.27 does not bring any relief unfortunately.
I understand @droftarts point - I'll change the channel to 6 or 11 on the home wifi. Crossing my fingers !
-
@Phaedrux @droftarts on Channel 13 now (Europe, and much less congested than 11 or 6).
I believe it's gotten slightly better, but I still see disconnects at random (frequent) intervals. If i understand you right, this is caused by EMF? Is my last resort an external antenna?
-
@phoenix Interference can certainly be an issue. Microwave ovens, cordless phones, baby monitors, or noisy electric motors (eg old fridge), so have a look a look around the immediate area to see if there's anything that could be causing it.
It's also worth looking at the LED on (or next to, depending on Duet 2 version) the WiFi module when it disconnects, to see if it is actually disconnecting; the LED should be on constantly when connected, but will flash when it loses connection and tries to reconnect. If it is staying on constantly while you have the error, then it may be a firmware issue.
To test the Duet's WiFi itself, change it to AP (Access Point) mode. You can connect directly via WiFi, and see if you get dropouts then. See https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#configuring-duet-in-wifi-access-point-mode
Lastly, have a look at the router. Do any other devices drop out? Some routers try and move the Duet WiFi to 5GHz, rather than 2.4GHZ, but then fall back to 2.4GHz, which might cause a disconnection/reconnection. There may be an option in the router to fix the Duet to 2.4GHz.
Ian