Wifi 2.1beta6 from 3.5.0-rc.2/3 still disconnecting
-
@Chriss Can you connect via USB and run M122 when DWC is in the disconnected state? If so please post the M122 output here.
-
@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.
-
i ran the printer most of the day with the USB lead connected and not one disconnect
-
@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 S1To 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 withM929 S0. This doesn't log debug messages that have been turned on with M111, though.Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts ive been running printer for 3 days now with the usb lead connected and not one disconnect ... typical
-
@moth4017 I was doing that yesterday. As soon as I disconnected the serial terminal, DWC lost connection!
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@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
-
@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
-
@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
-
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<
-
@moth4017 I don't see any M111 output from the WiFi module...
-
@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
<
-
@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?
-
@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.
-
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.
-
@gloomyandy DWC stopped responding no data being updated in the DWC window ,
connection "octo.local"
to get reconnected i use the reload button in chrome
-
@gloomyandy please explain " UART connection to the WiFi board in place."
im connected via USB to hercules , sent the M111 P14 S1 $0D and M111 P1 S1 $0D -
@moth4017 I'm not sure which WiFi module you are using, but on the skrpro there will be a separate set of wires that connects the module UART interface (used for flashing new versions of the WiFi firmware and for debug output) to the main board. That is the connection you need in place to see debug output from the board. If it is working and you run M552 s-1 followed by M522 S1 you should see a lot of debug output from the board.
If a refresh of the web page allows it to work again, I'd say that probably means it it not a problem with the WiFi module, check the Web browser developer console for errors, it may be that DWC has crashed for some reason.
-
@gloomyandy
M111The oldest data was removed. Continue... conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes Damon running Debugging On Fan & Heater Off 12896 5 New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 360 bytes New conn on socket 0 for local port 80 Found responder Received 361 bytes New conn on socket 0 for local port 80 Found responder Received 337 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 359 bytes New conn on socket 0 for local port 80 Found responder Received 360 bytes New conn on socket 0 for local port 80 Found responder Received 336 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes Serial port COM3 closed Serial port COM3 opened Serial port COM3 closed Serial port COM3 opened Serial port COM3 closed Serial port COM3 opened Serial port COM3 closed Serial port COM3 opened Serial port COM3 closed Serial port COM3 opened M552 s1 ok New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes M552 s1 ok New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes Damon running Debugging On Fan & Heater Off 12917 5 New conn on socket 0 for local port 80 Found responder Received 350 bytes New conn on socket 0 for local port 80 Found responder Received 360 bytes New conn on socket 0 for local port 80 Found responder Received 361 bytes New conn on socket 0 for local port 80 Found responder Received 337 bytes New conn on socket 0 for local port 80 Found responder Received 349 bytes M552 s-1 WiFi module stopped ok M552 s1 WiFi: WiFi: ets Jan 8 2013,rst cause:2, boot mode:(3,6) WiFi: WiFi: load 0x4010f000, len 1392, room 16 WiFi: tail 0 WiFi: chksum 0xd0 WiFi: csum 0xd0 WiFi: v00000000 WiFi: ~ld ok WiFi: phy buf[107] is ff adc mode is ff WiFi: boot not set WiFi: ota1 not set WiFi: ota2 not set WiFi: V2 WiFi: Mo WiFi: irf cal sector: 1019 WiFi: freq trace enable 0 WiFi: rf[112]Â WiFi: SDK:3.0.2(824dc80)/Core:unspecified=0/lwIP:STABLE-2_1_2_RELEASE/glue:1.2-17-g354887a/BearSSL:89454af WiFi: SocketServer.cpp(1576): Init completed WiFi: SocketServer.cpp(1577): WiFi: WiFi: DuetWiFiSocketServer version 1.27-04S-D ready WiFi: WiFi module started ESP reported status change ESP reported status change WiFi: SocketServer.cpp(1222): Set hostname to octo WiFi: mode : sta(e8:68:e7:d9:f9:a3) WiFi: add if0 Damon running Debugging On Fan & Heater Off 12927 5 Serial port COM3 closed -
@moth4017 I would have expected to see details of the WiFi server connecting to your access point in that output, did you remove that from what you posted?
But anyway I don't see any signs of a problem with the WiFi module in that output.
-
undefined T3P3Tony moved this topic from Beta Firmware
