CONSTANT AJAX disconnect errors
-
Did the "wifi module stopped" message happen because you sent a M552 command to stop it, or spontaneously?
-
Did the "wifi module stopped" message happen because you sent a M552 command to stop it, or spontaneously?
Probably b/c I sent the command to stop/start it, but honestly the disconnects were so bad and so frequent last night, I can't remember.
To even use the printer last night I was running M552 S-1/S1 pretty much any time I needed to access DWC because even if it had only be a couple of minutes it would have already disconnected.
If you have an exact set of steps you'd like me to walk through, I'm happy to try ANYTHING.
Also, even during the times that it is connected, it is not showing up as a connected client in my routers admin utility.
-
If it is connected but not showing up in your router's admin page, that is a problem with your router. You may need to refresh your router's admin page.
I'll be releasing a new firmware version soon that displays the wifi module sleep mode, along with a patched wifi module that doesn't sleep at all.
-
I don't think it is a problem with my router. All other devices on the network show connected. I can even power my phone off then on and watch it disappear and reappear on the connected clients list.
I guess it could be that the Duet disconnects so quickly after reconnecting that the client list doesn't update fast enough, but I am not sure.
-
Got a brand new Duet WIFI last week.
(had another previously which work fine - for a while)Had constant Ajax timeouts with the new one.
Could not stay connected for more than 30 seconds.
Could not always reconnect.
Restarted browser; hit reset button etc.
Had reported WiFi signal strength -62dBm.
Printer in basement, wifi router upstairs.Went to bestbuy, bought a NETGEAR - AC1200 Dual-Band Gigabit Wi-Fi Range Extender. $99
this is mounted in an outlet near the printer.Have not had a single disconnect since.
Pete
btw my previous Duet wifi which appears to have a broken wifi hardware issue (which I need to get resolved)
never had this timeout issue with everything in the same locations as pre-Wi-Fi Range Extender. -
I am glad that worked for you Pete.
I've got my Duet in the same room as my router, reporting mid -30dBm.
I've tried multiple different channels, moving the router around and to different rooms, and even replaced the router with a brand new one and created a from scratch network. I don't think the router or location is part of my problem.I'd like to set up a DHCP reservation for the Duet, but I can't seem to get that done since the router rarely sees the Duet as a connected client.
-
I am not saying you should fork out $99 for the wifi extender I got,
they have much cheaper versions.But what this extender did (after the configuration) do was allow me to connect
the DUET to a different SSID than everything else in my house
(NETGEAR20_2GEXT instead of NETGEAR20).
I don't necessarily know what difference this would make,
but it may be part of the issue.My original signal strength of -62dBm should have been perfectly ok
(and my previous Duet was OK with it),
Anything below 70 is considered very good.
Your 30 value SHOULD be beyond OK. And yet it is not.Is it worth a $20 try - TP-LINK - Wireless N300 Wi-Fi Range Extender with Ethernet Port - White
at bestbuy -
I've got a few extenders laying around, ill add one to my network and let the Duet be its only client with a different SSID as you suggest. It's worth a shot!
Thanks
-
Just tested the separate extender with dedicated SSID, and it only took 8 mins of sitting idle to disconnect.
-
I have two duet wifi's, both exhibit same behaviour, so it pretty much has to be a setting in the router.
these are my settings
-
I was able to reconnect and it actually showed up in my router admin as a connected device. This allowed me to bind a DHCP reservation to it. It has been sitting idle now CONNECTED for 44 mins. I am far from convinced that this will work, but so far it has. I will start a print next and see how that goes.
-
aaaaaaand about 30 seconds into a print…. DISCONNECT!
-
Jarery, I'd roll one of the Duets back to 1.18.2 and see if you still have issues.
-
KeeganB, please can you try a couple of things:
1. Start a print, wait until the motors are moving, then pause it. If it has disconnected already, reconnect. See whether it stays connected.
2. If it does stay connected, set the motor idle current to 100%, resume the print and pause it again, and once again see if it stays connected.
What I am wondering is whether the current to the stepper motors is causing interference.
-
KeeganB, please can you try a couple of things:
1. Start a print, wait until the motors are moving, then pause it. If it has disconnected already, reconnect. See whether it stays connected.
2. If it does stay connected, set the motor idle current to 100%, resume the print and pause it again, and once again see if it stays connected.
What I am wondering is whether the current to the stepper motors is causing interference.
I can try this. Are you thinking that the stepper motor wires are creating some level of EMI and interrupting the wifi signal? Should I consider wrapping them in some sort of shielding, and/or re-routing them as far away from the wifi card as possible?
I do have another update. Last night I reinstalled all the latest alpha/beta firmwares and uploaded all new configs generated from the online RRF Configuration tool. I wanted to "start from scratch" with everything that I could think of.
Doing this it stayed connected while printing from 10:28pm until 11:14pm. At this point my computer had gone to sleep, so I woke it back up and DWC had reported "disconnected - timeout". I was able to click "Connect" twice and it reconnected. It then stayed connected until 1am. I'm not sure at that point what may have happened, because I was asleep. I powered off the printer before leaving for work this morning. I am fine with that behavior, as it didn't require pronterface to send M552's to the board. I don't want to have to be constantly tethered to my computer.
-
Yes, I am thinking that EMI from the stepper cables, or the PSU, or the Duet itself could be generating interference.
I haven't ruled out the possibility that the WiFi modules on your Duet is faulty. But as I believe you reported that the connection is much less reliable when you are printing, I don't think that is very likely - unless for some reason the 3.3V power to the WiFi module is dropping for some reason when you are printing.
Interference generated by the Duet or the PSU might also explain why some WiFi channels seem to be more reliable than others.
-
David,
Aside from maybe the the stepper idle currents, is there ANYTHING in the config.g that could be related to my issues?
-
David,
Aside from maybe the the stepper idle currents, is there ANYTHING in the config.g that could be related to my issues?
As long as M122 shows a low MaxReps value after printing, nothing that I can think of.
-
Well,
I had a really good run yesterday afternoon. I was printing, sitting at idle with and without the steppers powers, and editing configs and etc though DWC for hours and hours yesterday with not issues. I was even able to move all of my network hardware back to its rightful place in my office and move my printer back to its normal spot as well. I powered it all up and it all connected just fine, no usb needed!
and then…. as I'm going to start a print before bed DISCONNECT, and it would not reconnect. I didn't want to mess with pronterface, so I just let it print. As usual about an hour later or so I was able to access DWC again.
-
Did the disconnection happen soon after the stepper motors were powered up?
Could the behaviour be related to temperature? i.e. it works OK when the ambient temperature is low and the machine is not printing, but the connection fails when the wifi module gets a bit warmer due to higher ambient temperature or heating due to the stepper drivers passing current?
I don't suppose you have a radio taxi station, ATC beacon or other high-power transmission source in your vicinity?
