HTTP connection over wifi gets dropped
-
I have TWO RailCore printers driven by DuetWifi controllers. BOTH started this issue where I can conNECT just fine to DWC. But if i upload a gcode file tp print, it will get part way through and the connection drops. It's apparently my home wifi. Embarrassingly, I'm an IT guy and I see nothing wrong with it. No recent changes either.
As a troubleshooting step, i wanted to change the Wifi to a different access point, using the M587 command. It takes the command and does do anything. How do I change the wifi, and and any ideas on the HTTP drop? -
@StevenL Which versions of RRF and DWC do you have installed? Also, please run M122 and share the result here.
In a first step, follow this WiFi troubleshooting guide. You also should be familiar with this doc: Setting up networking on Duet.
The syntax and usage of gCodes is listed in the GCode dictionary. See M587 and M588. -
@StevenL said in HTTP connection over wifi gets dropped:
How do I change the wifi
Adding another network to the remembered list won't automatically make it switch to that network by default. Instead it will connect to whichever network has the best signal strength. To force it to connect to a network you can include the network name in the
M552 P
command. Or use M588 to clear all the networks and re-add only one with M587.The Duet is only capable of 2.4ghz wifi. Perhaps your APs are trying to use band steering to 5ghz when it starts a file transfer.
-
@infiniteloop I am running 3.4.3 on both.
Results of M122:M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.3 (2022-10-05 09:01:07) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JKD6-3SN6L-KUW7G
Used output buffers: 1 of 26 (21 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 76052 of which 0 recycled
Never used RAM 12168, free system stack 184 words
Tasks: NETWORK(ready,13.0%,237) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,86.8%,438) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:18:57 ago, cause: power up
Last software reset at 2023-08-27 12:19, reason: User, GCodes spinning, available RAM 8984, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00417000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 28.3, current 41.1, max 41.7
Supply voltage: min 24.3, current 24.4, 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: 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: 2023-08-28 19:45:46
Cache data hit count 4294967295
Slowest loop: 14.24ms; 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 0.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 ===
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 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
Code queue is empty
=== DueX ===
Read count 1, 0.05 reads/min
=== Network ===
Slowest loop: 129.09ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 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 84:f3:eb:83:47:2a
WiFi Vcc 3.30, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24400
WiFi IP address 192.168.200.197
WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
Please try updating your firmware to 3.4.6
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.6/Duet2and3Firmware-3.4.6.zip
There is a new wifi firmware included in there as well.
Do you know if your AP has band steering?