Wifi 2.1beta6 from 3.5.0-rc.2/3 still disconnecting

Phaedrux

Do you get the same issue with the 1.27 release?

https://github.com/Duet3D/DuetWiFiSocketServer/releases/download/1.27/DuetWiFiServer.bin

chimaeragh

@Phaedrux Will the just released RRF 3.5rc3 work with WiFi Server 1.27?
I had issues with connection being dropped on WiFiserver 2.1 on 3.5rc2 so I rolled back to RRF3.4.6

moth4017

@chimaeragh im still getting disconnect too with Duet Web Control 3.5.0-rc.2,Duet WiFi Server n/a 1.27-04S-D

Chriss

@Phaedrux I guess that this is the version pre 2.1beta6? I saw the disconnects and the reconnects there too. But with a lover cadence and the board was reachable after the reconnect. So I never complained.

I can downgrade the wifi module if you want me to confirm that with 3.5rcX. Is it only me having that issue? I have 5 duet boards running here in my wifi and all 3.5rc boards have that hard problem. The others are fine.

Cheers, Chriss

Chriss

Do not get me wrong, I do not complain about the disconnects. I complain that the board is not reachable after the reconnect.

gloomyandy

@Chriss Can you connect via USB and run M122 when DWC is in the disconnected state? If so please post the M122 output here.

Chriss

@gloomyandy Hard to archive to be honest... I hope that I can do that via the console on the display and get you a picture. Let me do that when it happens the next time.

moth4017

i ran the printer most of the day with the USB lead connected and not one disconnect

droftarts

@moth4017 @Chriss I'm also having the WiFi connection drop and then be unresponsive, running a Mini 5+ with RRF/DWC 3.5.0-rc.3 and Duet WiFi Server 2.1beta6. We're trying to catch this bug and fix it! Any help with this would be greatly appreciated.

I've just had another disconnection. I was manually sending Gcodes in the DWC console when DWC disconnected, and then sat trying to reconnect. There was no message that it had disconnected on the PanelDue. I couldn't ping the Duet using the local host name or IP address. Unfortunately I didn't notice if the WiFi LED was still on next to the WiFi module on the Duet.

I turned off the WiFi module module with M552 S-1 and back on again with M552 S1 via the connected PanelDue. I have a macro to do this now!

; 1_WiFi off on
M552 S-1
G4 S5
M552 S1

To be able to track this bug down, the suggestion from the developer of the WiFi firmware is to turn on logging with M111 for the WiFi module and networking, eg:

M111 P1 S1
Debugging enabled for modules: Network(1 - 0xffffffff)
Debugging disabled for modules: Platform(0) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unused2(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) SbcInterface(16) CAN(17) Expansion(18)
M111 P14 S1
Debugging enabled for modules: Network(1 - 0xffffffff) WiFi(14 - 0xffffffff)
Debugging disabled for modules: Platform(0) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unused2(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Expansion(18)

This will mean a serial terminal needs to be connected via USB, so as not to miss messages.

You can also enable logging to SD card with M929, eg M929 P"eventlog.txt" S3, turn off with M929 S0. This doesn't log debug messages that have been turned on with M111, though.

Ian

moth4017

@droftarts ive been running printer for 3 days now with the usb lead connected and not one disconnect ... typical

droftarts

@moth4017 I was doing that yesterday. As soon as I disconnected the serial terminal, DWC lost connection!

Ian

moth4017

@droftarts i know this is a long shot and i carnt see any logic why the connection to the USB would make any difference, but only seems to disconect when the usb is not connected, unless its somehow suppling more power to the wifi module

oliof

@moth4017 you can try to tape off the VIN pin on the USB cable to see if its really a back power issue https://community.octoprint.org/t/put-tape-on-the-5v-pin-why-and-how/13574

moth4017

@oliof ran printer for a couple of hours today with USB connected , no issue , will add tape to USB lead and try again

that was a bit tricky to do

moth4017

ok DWC lost connection

M122 === Diagnostics ===
RepRapFirmware for STM32F4 based Boards (biqoctopuspro_1.0) version 3.5.0-rc.2+101 (2023-12-19 16:32:23) running on STM32F4 (standalone mode)
Board ID: 32063-002JU-NJ38P-6T18S-HFUN7-70000
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 19696
Dynamic ram: 90300 of which 20 recycled
Never used RAM 20028, free system stack 91 words
CCMRam static ram: 24276 dynamic ram: 34724 free ram 6532
Tasks: NETWORK(1,ready,16.8%,168) HEAT(3,nWait,0s 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Movement locks held by null, null
HTTP 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0004007
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 13820565 clear 32718022
Extruder 0 sensor: ok
=== CAN ===
Disabled
Longest wait 0ms for reply type 0, peak Tx sync delay 0 free buffers 0 (min 0), ts 0/0/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 668.81ms; fastest: 0.07ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0)
HTTP sessions: 2 of 8
Uploads/Errors: 4/0
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Bad header: 0/0
Firmware version 1.27-04S-D
MAC address 00:23:cd:20:84:e6
Module reset reason: Turned on by main processor, Vcc 3.39, flash size 4194304, free heap 37176
WiFi IP address 192.168.0.13
Signal strength -60dBm, channel 5, mode 802.11n, reconnections 0
Clock register 00004002
Socket states: 0 0 0 0 0 0 0 0
ok
Damon running
Debugging On
Fan & Heater Off
9564
5
Damon running
Debugging On
Fan & Heater Off
9574
5

gloomyandy

@moth4017 I don't see any M111 output from the WiFi module...

moth4017

@gloomyandy hopefully o SD card but im printing at the moment so cant stop, funny how it lost connection shortly after doing the tape on the USB lead

gloomyandy

@moth4017 Also what exactly do you mean by "lost connection"? Does the connection get re-established? Are you connecting to the IP address or to the <board>.local dns name? If the connection does not get re-established can you ping the board when it is in this state, can you connect to it from a different device?

gloomyandy

@moth4017 The M111 output only goes to the USB terminal and you will only see it if you have the UART connection to the WiFi board in place.

Chriss

I learned yesterday that I had a loop in my includes. So the FW opened the same 3 files over and over again, till a counter was reached. It seems to me that this made the WiFi module too disconnect and reconnect without being reachable in the LAN. But it is a guess only. I need observe the behaviour a bit more.