CONSTANT AJAX disconnect errors
-
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?
-
Hey David,
To start, I did your previously requested test in relation to the motor idle current and didn't get any disconnects. This was done during that really long stretch of good connection.
Yes, the disconnect last night happened probably 30 seconds or so after the print started. I do a G32 as part of the print, and after that completed, while working on the first layer it disconnected.
I have been keeping an eye on the MCU temp via DWC and it stays in the mid 30s Celsius.
I could add another small cooling fan to blow direction onto the wifi module if you think the is the problem. I can test that tonight. honestly though, if that is the problem I would have to question the quality of the module, or its ability to withstand heat. I don't think it is working under any extreme conditions at all.No, no high power transmission sources nearby.
-
Keegan, please try firmware 1.20beta2 and the DuetWiFiServer that goes with it. It stops the WiFi module going into sleep mode and the M122 report includes additional network diagnostics.
I'm discussing with my colleagues the possibility of loaning you another Duet WiFi to test, in case the WiFi module on your Duet is faulty. Meanwhile, if you can temporarily add a fan to cool the WiFi module, that would test the temperature theory.
When you did that test with the motors energised but idle, what idle current factor were you using? Please re-test it at 100% idle current if you haven't already.
-
Hey David,
I will test with a fan on the module tonight as well as upload the newest firmwares.
For the idle test, i tested with a print paused with both a factor of 60 and 100.
Thank You
-
Thanks. Can you confirm that you set the idle current to 100% before the motors went into idle hold? I'm not sure whether using M906 to adjust the idle current affects motors that have already been switched to idle.
-
Ive installed the new firmware.
confused by this statement :- Duet WiFi user can use either DuetWiFiServer 1.20beta2 (which disables WiFi module sleep) or 1.20alpha1 (which uses the default "modem sleep" mode)
My M122 has the following, but I'm using 1.20beta2, where above states modem sleep is only available with 1.20alpha1
WiFi signal strength -47dBm, reconnections 0, sleep mode modem
