CONSTANT AJAX disconnect errors
-
Not sure if this is helpful or something totally different:
I can now create the Ajax Errors whenever I want. Turns out that it is good enough to remove G32 and G28 from my GCode file (I reconnected the steppers), then I only need to change temperature when the printer is heating up for the 2nd layer and I get the disconnect (most likely because Duet crashes, the whole gcode behaves a little strange without the homing command)
Do you have a watchdog process running that restarts duet? In that case I am perhaps onto something, if not then what I am seeing is simply a crash that kills duet plus wifi, no more, no less.
Just in case I have uploaded the gcode here:http://temp.michael-ring.org/D_Delta2LowerPulleys.gcode
Michael
-
Michael,
In my situation, I get the disconnects even when the heaters are off. I haven't been able to figure out any pattern with mine lately. It happens when the heaters are off, or on, the steppers are off, idle, or moving, when the printer is printing or not, etc…
Where is you duet mounted in proximity to your PSU? after I figure out my stepper issues I posted above, my next step is to move the duet as far away as possible from the rest of the printer to test for disconnects that way.
-
I also have random disconnects, sometimes a few seconds after startup, sometimes shortly after starting a print. The only pattern I see is the pattern on what I see with station Info provided by my router. Besides that everything feels random, crashes after a few seconds, no problems to connect after several hours of idle after a print, I have it all
-
Once again you have the WiFi antenna inside a metal reflector along with several sources of interference. We designed the Duet WiFi with the antenna right at the edge of the board and no vertical connectors etc. in the last 20mm of the board along that edge, specifically so that you can mount the Duet with the antenna outside the printer metalwork.
-
David, can you please check my comments a little higher than this last comment, I‘d like your idea if what I saw is something worth following up or just a crash. At least the sympthons look exactly the same as a random crash, at keast from what I see in the logs of the router
-
David
As to your suggestion that maybe its the way you have yours mounted vs those of us with issues, i tried the following.
On my delta, with only board and motors in the top triangle, i moved my board so its standing on end instead of flat, in the center of the triangle such that the wifi module is near no motor or motor wires and is as far away from all 3 motors as possible, without moving it completely out of the printer.
Disconnected after about an hour of idling and using autocorrect a few times.
-
Looking back I think everyone with issues reported using routers with Merlins firmware? Perhaps anyone with Ajax disconnect issues who is running stock firmware on their router could confirm/deny.
Researching Asus routers that drop wireless clients, one thread had success turning off beamforming. In Merlins firmware there are two beamforming settings under "Professional" tab, Explicit and Universal.
Another thread reported wireless client issues dropping with both Merlins and stock firmware but problem cleared when they used DD-WRT firmware.Last night I turned off both beamforming options. My system has stayed connected overnight. I wont be able to run it through any prints till tomorrow, but perhaps some others with the issue capable of printing sooner could also test and let us know prior to that.
If this route fails I'll start messing with other router firmware. If anyone with issues is using dd-wrt firmware please let me know so i don't go down that path unnecessarily.
-
I'm running an OpenWRT firmware on an APU2 board, and I have these errors. On the other hand, my signal is really weak: -67dB
-
I was running the stock firmware on my Apple Airport Extreme router, and now I am running the stock firmware on my Tenda AC18 router.
I am about 99% sure the Apple router didn't have beam forming.
The Tenda does have beam forming, so I will see if I can turn it off.
Having had the same issues over two different routers and two different network setups I don't think it is a router issue in my case.
I've had a hell of a time with it over the past few days, and my frustration level reached a max last night. I have some new stuff to type up, but I am just not in the frame of mind to do it.
-
If anyone is interested in joining a Slack channel where we can have more instant (and mobile) conversations about this I have created one here:
If you have never used Slack, it is a FANTASTIC messaging system that works on nearly every platform and is loaded with wonderful features for file sharing, images, pics, chat, etc…
EDIT: If this slack channel is well received, we should probably still post to this post to keep everyone that may be following along updated on progress and findings.
-
@KeeganB - According to google the apple airport extreme has beamforming. Ive never used their router, perhaps its not able to be turned on/off by the user. No mention if its explicit only or if they implicit also. In my test I've currently turned off both. I also share your pain with the frustration part
@fma, Thanks that helps to know.
-
Jarery,
I'll google it, but my Airport Extreme was from 2008, so it was the older N version, not the newer AC. I'm not sure which one you were looking at.
-
dc42, can we get confirmation about the wifi sleep on/off function.
I believe in one thread you said the newest beta firmware turned the sleep option off.
I am using the newest firmware and it responds with "sleep state modem" which from my limited research is still a low powered sleep mode.Does the newest firmware turn off the sleep ability completely? If not can we get a firmware where it does turn it off ?
*You can use wifi_set_sleep_type to set sleep type for power saving and set NONE_SLEEP_T to disable power saving.
*power saving modes can only be enabled in station mode, since ESP8266 do not sleep when working in softap mode.
*Wake up of sleep:
Deep Sleep: ESP8266 need be waked up by xpd_dcdc(Pin8) or by other gpio of external MCU. Thus, xpd_dcdc(Pin8) or external GPIO should be connected to ext_rstb(Pin32).
Light Sleep and Modem sleep:Both are automatically added by underlying, which can sleep and be waked up automatically. There is no need of any processing in hardware. -
It looks like that change failed to make it into 1.20beta2. I am currently working on a new version that uses a later SDK and fixes the KRACK vulnerability, so I'll issue an update when that is finished.
-
My beamforming off experimented was a no go. It eventually disconnected.
will wait for the "sleep off" firmware. -
My beamforming off experimented was a no go. It eventually disconnected.
will wait for the "sleep off" firmware.Bummer, I guess one of us should try the firmware downgrade and see if that works. It may at least help narrow down where the issue lies. I don't know if I will have time to get to that tonight, but ill try it after I test a few other things.
One of the things that has been bothering me about this is that sometimes it disconnects and a single click of "Connect" in DWC works fine. Other times it disconnects and locks me out entirely, this is the more common issue. When it does lock me out entirely I can get it to reconnect using one of three different methods. Method three is the most confusing to me.
1. Power the printer/board off and then back on.
2. Send M552 S-1 followed by M552 S1 via Pronterface over USB.
3. Wait. If I click "connect" and it doesn't connect and then I do nothing and just let the printer continue to print or sit idle for "X" amount of minutes I can just click "connect" and it will suddenly connect again. The "X" amount of minutes is generally 30 or more minutes I think.The common theme among those is that "restarting" the wifi module seems to temporarily fix it, BUT what is happening in scenario #3, where it resolves itself?
-
1. Power the printer/board off and then back on.
2. Send M552 S-1 followed by M552 S1 via Pronterface over USB.
3. Wait. If I click "connect" and it doesn't connect and then I do nothing and just let the printer continue to print or sit idle for "X" amount of minutes I can just click "connect" and it will suddenly connect again. The "X" amount of minutes is generally 30 or more minutes I think.The common theme among those is that "restarting" the wifi module seems to temporarily fix it, BUT what is happening in scenario #3, where it resolves itself?
Interesting, I have the same 3 scenarios.
I either turn wifi on/off or wait 30min+. -
This afternoon when i got home from work, I powered up the printed (NO USB Connected) and figured I would fight with this disconnect issue some more. Here are the steps I took.
1. Power on printer
2. Load DWC in Google Chrome via the hostname.
3. Sigh heavily
4. Walk away, lets get some dinner.
2 MINUTES AND 3 SECONDS is all it stayed connected for. I did nothing but turn it on and load DWC. The heaters were OFF, the steppers were OFF, nothing got homed, no files were uploaded, etc…
I was completely locked out too, This would have required either a power cycle of the printer, or running 552 commands from usb/pronterface.
-
I yesterday isolated the Duet from interference by first putting two alumnium plates on top of the printer and then placing the Duet above this metal shield, see attached picture.
Later, during a print last night I lost connectivity and could not reconnect. I tried another trick by rebooting my router to check if the Duet reconnects after the WiFi signal is back, it did not. All my other devices reconnected as usual and duet also reconnects when it is not in this 'broken' state.
-
Keegan, I'd like to send you a Duet WiFi with external antenna to test, to see if it resolves the problem. The antenna will need to be mounted on the outside of your printer, and the cable to the wifi module on the Duet is 13cm long. Will that be workable for you? If so, please PM me with your mailing address.
Also, do you have a 3.3V-compatible USB-to-serial converter? If so then we might be able to get some diagnostics out of the wifi module.
