WiFi Flapping / unable to connect to DWC
-
@dc42 said in WiFi Flapping / unable to connect to DWC:
Have you acquired a new cordless phone system, baby alarm, or other device that uses the 2.4GHz wifi band recently?
It could also be a neighbour, not even next door.
Many newer "high speed" 11n 2.4GHz WiFi systems use 2/3 of the band rather than the 1/3 that used to be common (11g etc), meaning it's just about one-device-at-a-time if there are any of those in range.
Plus other 2.4GHz non-wifi gear, as dc42 says.
Robert J.
Printers: Overlord pro, Kossel XL+ with Duet 6HC and "Frankentron", TronXY X5SA Pro converted to E3D toolchange with Duet 6HC and 1LC toolboards.
-
@dc42 No new RF devices and the printer is less than 10ft away from the access point. Homes in my area are fairly far apart so its unlikely that its RF interference from a neighbor. I also have the signal strength cranked way up to get coverage through the entire house with a single access point rather then adding repeaters.
I can look at the scanner built into it and see if anything shows up but what I'm trying to say it that its unlikely RF interference has anything to do with this.
I was running 3.4b to address issues with the MFM and had upgraded to b7+ to try and address a problem I'm having with printing PLA.
I will also roll back the firmware to 3.3 but I think I will need the appropriate DWC version as well if someone could point me to both.
I'm thinking this is probably a hardware issue and would like to know how to go about replacement. we're right up against the end of the 1 year warranty period.
Thank you!
-
-
@wouldstain said in WiFi Flapping / unable to connect to DWC:
I will also roll back the firmware to 3.3 but I think I will need the appropriate DWC version as well if someone could point me to both.
You should be able to upload the full zip file and take care of everything.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
-
@rjenkinsgb Ran RF scan and there's nothing even close enough with overlapping channels that could be interfering.
-
Would you be able to test in access point mode to eliminated the router from the connection chain?
-
@wouldstain said in WiFi Flapping / unable to connect to DWC:
Ran RF scan and there's nothing even close enough with overlapping channels that could be interfering.
If that was with a computer / WiFi device, note that it will not register different types of signals such as video senders and suchlike, even on identical frequencies.
You would need a spectrum analyser or panoramic receiver to see what is actually present.
Also note the WiFi channel numbers are from earlier systems; 11g takes a block four of those old channel wide and 11n up to eight channels wide.
-
For whatever bizarre reason, it started working again.
This concerns me as I did not really do anything to it this evening other than turn back on again with the same SD card that was in it originally.
If it happens again I'll pick up this thread.
-
-
do you have stall detection configured?
-
A few days ago I faced the same problem. Tried many ways. Changed the wi-fi channel. Turned on and off DHCP. Rebooted the router. I changed the firmware from 3.4 b 7 to 3.4 rc1. This did not improve the situation in any way. When pinging via cmd, packets were constantly lost and there was a big ping.
Packet exchange from 192.168.1.10 to 32 bytes of data: The waiting interval for the request has been exceeded. Response from 192.168.1.10: number of bytes=32 time=316ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=207ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=122ms TTL=255 Ping statistics for 192.168.1.10: Packets: sent = 4, received = 3, lost = 1 (25% loss) Approximate receive-transmit time in ms: Minimum = 122 m sec, Maximum = 316 m sec, Average = 215 m secI had a spare router. After replacing the router, the problem went away. The ping is minimal. The connection is not lost. Maybe this will help you.
Packet exchange from 192.168.1.10 to 32 bytes of data: Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Response from 192.168.1.10: number of bytes=32 time=1ms TTL=255 Ping statistics for 192.168.1.10: Packets: sent = 4, received = 4, Lost = 0 (0% loss) Approximate receive-transmit time in ms: Minimum = 1msec, Maximum = 1msec, Average = 1msec
