WiFi disconnect errors
-
Sure, I'll collect more data and post it here
In the meanwhile – I can build the firmware myself, so if you need me to build it with maybe some additional debug flags, or quickly test some changes without releasing the new beta version – feel free to ask.
-
Thanks. Those debug messages come from the firmware on the wifi module, so it's that firmware that is likely to contain the fault.
-
Please can anyone else who is still getting WiFi disconnections even though the RSSI is good do the following:
1. Upgrade to the just-released DuetWiFiFirmware 1.20beta8 and DuetWiFiServer 1.20beta9.
2. Connect a PC via USB and send M111 S1 P14 to enable the new WiFi debugging feature. If you have already started wifi, send M552 S-1 and then M552 S1 to restart it. You will get some WiFi debug messages during startup and connection to your router, similar to the following:
WiFi:
WiFi: ets Jan 8 2013,rst cause:2, boot mode:(3,6)
WiFi:
WiFi: load 0x4010f000, len 1384, room 16
WiFi: tail 8
WiFi: chksum 0x2d
WiFi: csum 0x2d
WiFi: v00007fff
WiFi: ~ld
WiFi module started
WiFi: mode : sta(a0:20:a6:19:28:23)
WiFi: add if0
WiFi: scandone
WiFi: sleep enable,type: 2
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 2
WiFi: cnt
WiFi:
WiFi: connected with ********, channel 6
WiFi: dhcp client start…
Wifi module is connected to access point ********* IP address 192.168.1.123
WiFi: ip:192.168.1.123,mask:255.255.255.0,gw:192.168.1.254
WiFi: pm open,type:2 03. Load DuetWebControl in your browser.
4. If/when the wifi disconnects unexpectedly, look at the console on the PC to see whether any more debug messages have been displayed, and report what you find.
-
Hi David,
So I was able to reproduce few more times. Here are my observations:
- (obvious one) I didn't see any debug messages including p->buf==1 while DWC page is not opened
- these p->buf==1 messages always (or most of the time) come out in pairs
- there are no regular intervals between these messages, sometimes I see few per second, sometimes I don't any for 10-15 minutes
- they are not getting more often before the disconnect
- I feel that messages are coming much more often when printer is printing (compared to the idle) - suspect it may be related to some timings, e.g. CPU is busy with something and can't send some command or data to the WiFi module in time. Or maybe noise in power line due to heaters PWM. My power supply is able to provide enough current, so it's not under-voltage, but maybe some noise…
I'll post here if I get more data
-
Thanks. Please can you install this DuetWiFiServer.bin file twice (the second time you can just send M997 S1 to install it again from the existing SD card file). It will provide a slightly more detailed debug message.
-
Sure, will do. I wonder if there is anything of interest to you in the debug message showing when I do M552 S0 after such disconnect:
WiFi: state: 5 -> 0 (0) WiFi: rm 0 WiFi: pm close 7 WiFi: tcp_pcb_purge: pcb->state == SYN_RCVD but tcp_listen_pcbs is NULL Wifi module is idle WiFi: tcp_pcb_purge: pcb->state == SYN_RCVD but tcp_listen_pcbs is NULL WiFi: tcp_pcb_purge: pcb->state == SYN_RCVD but tcp_listen_pcbs is NULL WiFi: del if0 WiFi: usl WiFi: mode : nullNot sure if these pcb->state checks are ok
-
Yes, those are interesting too, in particular the tcp_pcb_purge messages.
-
I did additional M997 S1 and then reproduced disconnect once again, but it didn't result in any additional messages in the log.
-
There shouldn't be additional messages, but some of the messages should have additional detail.
-
I had to revert to 1.20beta6 for now because starting from 1.20beta7 it resets every now and then and I have lots of failed prints because of that. I'm still running the latest 1.20beta9 WiFi firmware though.
-
Please can anyone else who is still getting WiFi disconnections even though the RSSI is good do the following:
1. Upgrade to the just-released DuetWiFiFirmware 1.20beta8 and DuetWiFiServer 1.20beta9…
I'll upgrade tomorrow morning (US Central time) and start testing.
John
-
OK - Firmware updated, WiFi debugging turned on. We'll see what happens. Here's the startup debug so far:
[[language]] Connecting... RepRapFirmware for Duet WiFi Version 1.20beta8+1 dated 2017-11-18 Executing config.g...Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 594C. HTTP is enabled on port 80 FTP is disabled TELNET is disabled Done! RepRapFirmware for Duet WiFi is up and running.T:20.7 /0.0 B:20.1 /0.0 Printer is now online. >>>M111 S1 P14 SENDING:M111 S1 P14 Debugging enabled for modules: WiFi(14) Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) >>>M552 S-1 SENDING:M552 S-1 WiFi module stopped >>>M552 S1 SENDING:M552 S1 WiFi: WiFi: ets Jan 8 2013,rst cause:2, boot mode:(3,7) WiFi: WiFi: load 0x4010f000, len 1384, room 16 WiFi: tail 8 WiFi: chksum 0x2d WiFi: csum 0x2d WiFi: v00007fff WiFi: ~ld WiFi module started WiFi: mode : sta(a0:20:a6:16:eb:66) WiFi: add if0 WiFi: scandone WiFi: sleep enable,type: 2 WiFi: scandone WiFi: state: 0 -> 2 (b0) WiFi: state: 2 -> 3 (0) WiFi: state: 3 -> 5 (10) WiFi: add 0 WiFi: aid 7 WiFi: cnt WiFi: WiFi: connected with Aloha, channel 7 WiFi: dhcp client start... Wifi module is connected to access point Aloha, IP address 192.168.62.118 WiFi: ip:192.168.62.118,mask:255.255.255.0,gw:192.168.62.1 WiFi: pm open,type:2 0 WiFi: p->ref == 1 WiFi: p->ref == 1 -
Ok - just finished a two hour print without disconnects. I am seeing many of the WiFi: p->ref == 1 messages. I also added an M122 diagnostic at the end.
Here's the full log so far. I'll keep the machine on.
[[language]] Connecting... RepRapFirmware for Duet WiFi Version 1.20beta8+1 dated 2017-11-18 Executing config.g...Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 594C. HTTP is enabled on port 80 FTP is disabled TELNET is disabled Done! RepRapFirmware for Duet WiFi is up and running.T:20.7 /0.0 B:20.1 /0.0 Printer is now online. >>>M111 S1 P14 SENDING:M111 S1 P14 Debugging enabled for modules: WiFi(14) Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) >>>M552 S-1 SENDING:M552 S-1 WiFi module stopped >>>M552 S1 SENDING:M552 S1 WiFi: WiFi: ets Jan 8 2013,rst cause:2, boot mode:(3,7) WiFi: WiFi: load 0x4010f000, len 1384, room 16 WiFi: tail 8 WiFi: chksum 0x2d WiFi: csum 0x2d WiFi: v00007fff WiFi: ~ld WiFi module started WiFi: mode : sta(a0:20:a6:16:eb:66) WiFi: add if0 WiFi: scandone WiFi: sleep enable,type: 2 WiFi: scandone WiFi: state: 0 -> 2 (b0) WiFi: state: 2 -> 3 (0) WiFi: state: 3 -> 5 (10) WiFi: add 0 WiFi: aid 7 WiFi: cnt WiFi: WiFi: connected with Aloha, channel 7 WiFi: dhcp client start... Wifi module is connected to access point Aloha, IP address 192.168.62.118 WiFi: ip:192.168.62.118,mask:255.255.255.0,gw:192.168.62.1 WiFi: pm open,type:2 0 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 Calibrated 6 factors using 10 points, deviation before 0.213 after 0.036 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 Done printing fileFinished printing file Models/JoelBot_Repaired_70p_KMR3.gcode, print time was 2h 18m WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 >>>M122 SENDING:M122 === Diagnostics === Used output buffers: 3 of 32 (9 max) === Platform === RepRapFirmware for Duet WiFi version 1.20beta8+1 running on Duet WiFi 1.0 Board ID: 08DAM-999TL-MQ4S8-6JKDJ-3SJ6K-16BVW Static ram used: 15488 Dynamic ram used: 99336 Recycled dynamiWiFi: c ram: 3960 Stack ram used: 4328 current, 9428 maximum Never used ram: 2860 Last reset 02:39:14 ago, cause: power up Last software reset reason: User, spinning module GCodes, available RAM 3192 bytes (slot 1) Software reset code 0x0003, HFSR 0x00000000, CFWiFi: LINK SR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0WiFi: xmit: 0 xffffffff Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 543.3ms MCU temperature: min 29.3, current 38.3, max 41.0 Supply voltWiFi: recv: 0 age: min 0.6, current 12.3, max 12.5, under voltage events: 0, over voltage events: 0 DWiFi: fw: 0 river 0: standstill Driver 1: standstill Driver 2: standstill Driver 3: standstill Driver 4: standstill Date/time: 2017-11-19 11:59:58 Cache data hit count 4294967295 SlWiFi: drop: 0 owest main loop (seconds): 0.544757; fastest: 0.000033 === Move === MaxReps: 6, StepErrors: 0, FreeDm: 240, MinFreeDm 120, WiFi: chkerr: 0 MaxWait: 1524274909ms, Underruns: 0, 0 Scheduled moves: 0, completed moves: 0 Bed compensation in use: none Bed probe heights: 0.300 WiFi: lenerr: 0 0.175 0.153 0.075 0.295 === Heat === Bed heater = 0, chamber heater = -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.7 === GCodes === SegmeWiFi: memerr: 0 nts left: 0 Stack records: 1 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 WiFi: rterr: 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is ready with "M122" in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autWiFi: proterr: 0 opause is idle in state(s) 0 Code queue is empty. Network state is runniWiFi: opterr: 0 ng WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.20b9 WiFi MAC address a0:20:a6:16:eb:66 WiFi Vcc 3.37, reset reason Turned on by main processorWiFi: err: 0 WiFi flash size 4194304, free heap 27640 WWiFi: cachehit: 0 iFi IP address 192.168.62.118 WiFi signal strength -58dBm, reconnections 0, sleep mode modem HTTP sessions: 2 of 8 Socket states: 0 0 0 0 0 0 0 0 Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) WiFi: WiFi: ETHARP WiFi: xmit: 4 WiFi: recv: 1203 WiFi: fw: 0 WiFi: drop: 6803 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: rterr: 0 WiFi: proterr: 6803 WiFi: opterr: 0 WiFi: err: 0 WiFi: cachehit: 40018 WiFi: WiFi: IP WiFi: xmit: 40128 WiFi: recv: 6877 WiFi: fw: 0 WiFi: drop: 0 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: rterr: 0 WiFi: proterr: 0 WiFi: opterr: 0 WiFi: err: 0 WiFi: cachehit: 0 WiFi: WiFi: IGMP WiFi: xmit: 2 WiFi: recv: 94 WiFi: drop: 0 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: proterr: 0 WiFi: rx_v1: 0 WiFi: rx_group: 0 WiFi: rx_genert 62171 WiFi: recv: 62198 WiFi: fw: 0 WiFi: drop: 0 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: rterr: 0 WiFi: proterr: 0 WiFi: opterr: 0 WiFi: err: 0 WiFi: cachehit: 0 -
The printer has been sitting idle since the last post (about 43 minutes).
-
I just had a disconnect.
-
I was not able to re-connect from DWC.
-
I am not able to ping the printer
-
Router is an ASUS RT-N66R running the Asus-Merlin firmware 380_68.4
Latest log from the still USB connected computer is below:
[[language]] WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 WiFi: p->ref == 1 >>>M122 SENDING:M122 === Diagnostics === Used output buffers: 3 of 32 (11 max) === Platform === RepRapFirmware for Duet WiFi version 1.20beta8+1 running on Duet WiFi 1.0 Board ID: 08DAM-999TL-MQ4S8-6JKDJ-3SJ6K-16BVW Static ram used: 15488 Dynamic ram used: 99336 Recycled dynamWiFi: ic ram: 3960 Stack ram used: 4328 current, 9428 maximum NWiFi: LINK ever used ram: 2860 Last reset 03:22:04 ago, cause: power up Last software reset reason: User, spinning module GCodes, available RAM 3192 bytes (slot 1) Software reset code 0x0003, HFSR 0x00000000, CWiFi: xmit: 0 FSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff Error status: 0 Free file entriWiFi: recv: 0 es: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 34.2, current 34.4, max 38.7 Supply voltaWiFi: fw: 0 ge: min 12.2, current 12.3, max 12.5, under voltage events: 0, over voltage events: 0 Driver 0: standstill Driver 1: standstill DriWiFi: drop: 0 ver 2: standstill Driver 3: standstill Driver 4: standstill Date/time: 2017-11-19 12:42:48 Cache data hit count 4294967295 SlWiFi: chkerr: 0 owest main loop (seconds): 0.116336; fastest: 0.000112 === Move === MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0 Scheduled WiFi: lenerr: 0 moves: 0, completed moves: 0 Bed compensation in use: none Bed probe heights: 0.300 0.175 0.1WiFi: memerr: 0 53 0.075 0.295 === Heat === Bed heater = 0, chamber heater = -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.7 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet isWiFi: rterr: 0 idle in state(s) 0 file is idle in state(s) 0 sWiFi: proterr: 0 erial is ready with "M122" in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. Network state is running WiFi mWiFi: opterr: 0 odule is connected to access point Failed messages: pending 0, notready 0, nWiFi: err: 0 oresp 0 WiFi firmware version 1.20b9 WiFi MAC address a0:20:a6:16:eb:66 WiFi Vcc 3.38, reset reason Turned on by main processor WiFi flash size 4194304, free heap 28584 WiFi IP adWiFi: cachehit: 0 dress 192.168.62.118 WiFi signal strength -59dBm, reconnections 0, sleep mode modem HTTP sessions: 2 of 8 SoWiFi: cket states: 0 0 0 0 0 0 0 0 Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) WiFi: ETHARP WiFi: xmit: 4 WiFi: recv: 2331 WiFi: fw: 0 WiFi: drop: 8472 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: rterr: 0 WiFi: proterr: 8472 WiFi: opterr: 0 WiFi: err: 0 WiFi: cachehit: 61640 WiFi: WiFi: IP WiFi: xmit: 61750 WiFi: recv: 36768 WiFi: fw: 0 WiFi: drop: 0 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: rterr: 0 WiFi: proterr: 0 WiFi: opterr: 0 WiFi: err: 0 WiFi: cachehit: 0 WiFi: WiFi: IGMP WiFi: xmit: 2 WiFi: recv: 106 WiFi: drop: 0 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: proterr: 0 WiFi: rx_v1: 0 WiFi: rx_group: 0 WiFi: rx_gent: 10141 WiFi: recv: 23497 WiFi: fw: 0 WiFi: drop: 0 WiFi: chkerr: 0 WiFi: lenerr: 0 WiFi: memerr: 0 WiFi: rterr: 0 WiFi: proterr: 0 WiFi: opterr: 0 WiFi: err: 0 WiFi: cachehit: 0 -
-
Interestingly, after posting the entry above, the following happened in the still running log, which did allow me to reconnect from DWC:
[[language]] WiFi: state: 5 -> 2 (10c0) WiFi: rm 0 WiFi: pm close 7 WiFi reported error: Lost connection, auto reconnecting WiFi: reconnect WiFi: state: 2 -> 0 (0) WiFi: scandone WiFi: state: 0 -> 2 (b0) WiFi: state: 2 -> 3 (0) WiFi: state: 3 -> 5 (10) WiFi: add 0 WiFi: aid 7 WiFi: cnt WiFi: WiFi: connected with Aloha, channel 7 WiFi: dhcp client start... WiFi reported error: Auto reconnect succeeded WiFi: ip:192.168.62.118,mask:255.255.255.0,gw:192.168.62.1 WiFi: pm open,type:2 0 -
Thanks for that. The p->ref==1 definitely indicates an error. I've spotted a patch that someone made to lwip 1.4 for the ESP8266, and that patch isn't in any of the official sources, so I'm beginning to suspect it. It's strange that I never see those messages.
The latest log entry you posted indicates the WiFi connection was lost but the auto reconnection done by the WiFi SDK succeeded. That's the first time I've seen evidence of that working.
-
I don't have any log data for you but I have some interesting other data.
I had been having numerous Ajax time outs and most of the time I couldn't reconnect but occasionally I could. I had a strong signal with RSSI values from -38 to -40. My network was made up of two Apple Airport Extreme (the latest version) access points. One as my router and the 2nd extending the network to my basement where my printer is. Sometimes the printer would connect to the access point two floors away instead of the one 6 feet from the printer. Also, since the Airport Extremes don't have a dedicated radio to extend the network the performance wasn't as good as it could be with some of the new tri-band routers.
Yesterday, I replaced the Airport Extremes with a 3 node Netgear Orbi setup. The Orbi remote closest to the printer is in the same location as that the 2nd Airport Express was. There is also an additional Orbi remote one floor up and the primary Orbi Router is two floors up from where the printer is. The connection has been rock solid with this setup for about 24 hours now. I've had a few disconnects related to the laptop going to sleep or such, but that is to be expected. I can always immediately reconnect when I need to. I have had no disconnects when I wouldn't expect them.
I'm also finding the my wireless performance better overall.
I think at least one other person has mentioned that they use an Apple router. It would be interesting to see if there is any correlation between what routers people use and the disconnects.
Of course, if this patch you just found fixes it, I guess it won't matter.
-
I have good WiFi connectivity, RSSI -43dBm, Broadcom chipset based router. Have upgraded to latest firmware and beta9 server, could do two small prints of 30 minutes without issue, this morning I could not reconnect. Unfortunately i accidentally turned off the pc i used for usb logging, will retry tonight.
-
I think at least one other person has mentioned that they use an Apple router. It would be interesting to see if there is any correlation between what routers people use and the disconnects.
I've had various problems with Duets and WiFi for a long time, and I'm also using an AirPort Extreme. It mostly works fine nowadays, but I'm still having problems from time to time. I recently updated to 1.20b, but it's too early to determine whether that has made a difference.
-
I've replaced my Apple router with Google WiFi today, and it still disconnects, so I don't think it is related to particular router model.
