3.5.1 "forgetting" the assigned WiFi connection
-
I updated to 3,5,1 on one of my Duet-2 (1.04) boards yesterday, and I am encountered an issue where after the update in that I couldn't reconnect to DWC via Wi-Fi
I connected via a USB cable, and instantly I started receiving Wi-Fi connection errors stating no known networks were available
I disabled the Wi-Fi Adapter to suppress the error, then re-initialized it, putting it into an idle state.
Sending M587 shows no networks were saved,
I then Re-Added my Wi-Fi connection and got re-connected via DWC (the printer prints normally on the new firmware after I got connected) I initially just put it down to the update not doing its thing properly.
Went to connect to the printer this morning and couldn't, connecting via USB started the cycle i encountered during the upgrade, if I carried out the rectification procedure again I could connect until I shut down then the cycle begins again.
If I roll back to earlier firmware (on the same board with no changes to the config.g) the problem disappears.
-
Can you share an M122 report?
What is the reported wifi server version?The wifi module forgetting the networks after the initial upgrade isn't totally unheard of, but it shouldn't be forgetting it every reboot.
-
@Phaedrux said in 3.5.1 "forgetting" the assigned WiFi connection:
Can you share an M122 report?
What is the reported wifi server version?The wifi module forgetting the networks after the initial upgrade isn't totally unheard of, but it shouldn't be forgetting it every reboot.
I have permanently rolled back to Release 3.5.0-rc.4
WiFi Sever is 2.1 Beta 8
Results of M122 (board ID & MAC Address removed)
(Edit) I did remove all saved networks using M588 S"*" before re-adding my SSID/Password
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet WiFi 1.0 or 1.01 Board ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Used output buffers: 14 of 26 (14 max) === RTOS === Static ram: 23256 Dynamic ram: 72848 of which 12 recycled Never used RAM 17028, free system stack 170 words Tasks: NETWORK(2,nWait 6,13.1%,220) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,86.2%,745) IDLE(0,ready,0.7%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:02:31 ago, cause: power up Last software reset at 2024-04-20 16:29, reason: User, Gcodes spinning, available RAM 12972, 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 MCU temperature: min 34.8, current 37.6, max 38.7 Supply voltage: min 24.1, current 24.2, max 24.5, 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: 2024-04-21 11:53:07 Cache data hit count 4294967295 Slowest loop: 11.05ms; 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 4.8ms, 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, min interval 0, bad calcs 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 Heater 1 is on, I-accum = 0.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 === Network === Slowest loop: 8.32ms; 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.1beta8 MAC address xxxxxxxxxxxxxxxx Module reset reason: Turned on by main processor, Vcc 3.39, flash size 4194304, free heap 39236 WiFi IP address 192.168.88.222 Signal strength -55dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@Mr-Crispin said in 3.5.1 "forgetting" the assigned WiFi connection:
I have permanently rolled back to Release 3.5.0-rc.4
WiFi Sever is 2.1 Beta 8
And the problem doesn't occur there anymore?
-
@Phaedrux said in 3.5.1 "forgetting" the assigned WiFi connection:
And the problem doesn't occur there anymore?
Correct, As soon as I roll back the firmware, the problem disappears
-
undefined Phaedrux marked this topic as a question
-
@Mr-Crispin said in 3.5.1 "forgetting" the assigned WiFi connection:
Firmware version 2.1beta8
It looks like the wifi firmware wasn't actually updated? Or the M122 was collected after reverting?
Can you try updating using the full release zip file and confirming that the wifi server firmware is actually getting updated to the full non-beta release?
-
That's the package I originally downloaded.
It's working fine on the older firmware, so I will leave well alone until i have to update
-
If it's a bug we can reproduce we can try to fix it.
-
undefined Phaedrux moved this topic from Firmware installation
-
undefined Mr.Crispin referenced this topic