CONSTANT AJAX disconnect errors

dc42

I'm sorry to hear that you are still having problems. See https://duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors.

The fluctuating temperature readings could indicate interference, or a power supply issue. Check that the VIN terminal block screws are tight (check the bed heater output terminals too).

Jarery

I have done everything in the wiki page linked
My RSS is at -38, its not a wifi strength issue.
I have now commissioned two printers, each with duet wifi. This issue is the same on both.

Right now i would not recommend this board to anyone as its disconnection issue makes its use beyond frustrating and many of the "features" are missing if you only have connection through the PanelDue and not the browser.

I would exchange them both for ethernet versions where I could hook them up to a router acting as a bridge, or a $20 travel router which is actually able to keep a connection.

dc42

I'm sorry to hear that you are still having problems with staying connected. Are you running the latest stable version (1.19.2) of both DuetWiFiFirmware and DuetWiFiServer? Look on the Settings/General tabe of DWC to check.

If you are running the latest versions, then it would be helpful for me to know the following:

1. Does it disconnect when the printer is idle, or only when printing?

2. When connection from the browser is lost, are you able to reconnect by pressing the Connect button?

3. If you are not able to reconnect by pressing the Connect button, please send M552 or M122 from USB and let us know whether it says the wifi module is connected to the access point, or is idle.

4. If it disconnects only during printing, please run M122 after a print and report the MaxReps value it prints. Note that MaxReps is cleared every time you run M122, so only the first time you run it after completing a print has any meaning.

5. What do you have the Max Retries set to in DWC?

Jarery

Firmware Version: 1.19 (2017-08-14)
WiFi Server Version: 1.19
Web Interface Version: 1.19

I've gone through all these with you previously in this or other threads..

Disconnects when idle also
Reconnect via "connect" button happens is 50/50. Never reconnects if pressed immediately. Sometimes if i let it print 5-10 min it will reconnect vie connect button. Majority of time it does not
Will check this next time i try a print . (unable to currently due to odd probing behaviour, separate thread in smart effector section)
I've posted the maxreps previously, i recall it was single digits, 5 or so.

50 max retries is set to 3. Ive also tried 5 and 10.

dc42

Please upgrade to firmware 1.19.2 (both DuetWiFiFirmware and DuetWiFiServer). The WiFi module should have reconnected automatically if connection to the access point it lost, because that's what the manufacturer's firmware is configured to do. But during testing, I found it unreliable. So our own firmware now does a separate reconnect if that one fails.

The M122 report includes the number of reconnections done.

Jarery

Downloaded files from here :
https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Stable
Location is from the wiki page..

Uploaded. Both report the exact same as before…
Firmware Version: 1.19 (2017-08-14)
WiFi Server Version: 1.19
Web Interface Version: 1.19

Are these 1.19.2 files hidden somewhere ?

Found them after searching the forum for the link
https://github.com/dc42/RepRapFirmware/releases/tag/v1.19.2

Maybe update the wiki page to the link, right now it goes to 1.19

dc42

Latest stable releases are now always at https://github.com/dc42/RepRapFirmware/releases. Which wiki page links to 1.19 ?

Jarery

https://duet3d.com/wiki/Updating_main_firmware

Check you have [downloaded the correct firmware](downloaded the correct firmware) before installing it. The DuetWiFiFirmware.bin file should be the same size as shown on the github (currently about 300 KB in size).

–----------------

Installed 19.2
ran a print, 5 min in it disconnected:
Didn't reconnect on its own but did with a repress of "connect button"

=== Move ===
MaxReps: 5, StepErrors: 0, FreeDm: 123, MinFreeDm 120, MaxWait: 9ms, Underruns: 0, 0
Scheduled moves: 25067, completed moves: 25037
Bed compensation in use: mesh

Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19.2
WiFi MAC address a0:20:a6:10:55:89
WiFi Vcc 3.17, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39000
WiFi IP address 192.168.2.32
WiFi signal strength -52dBm
Reconnections 0
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

Jarery

3. If you are not able to reconnect by pressing the Connect button, please send M552 or M122 from USB and let us know whether it says the wifi module is connected to the access point, or is idle.

Mid print, system has disconnected for second time.

M155 from PanelDue states:
"WIFI module is connected to access point xxxxxx, ip address 192.168.2.32"

dc42

Thanks.

Are you still able to ping the IP address of the Duet? If not, are you able to confirm on the status page of your router that the router agrees that the Duet is still connected?

Jarery

PING 192.168.2.32 (192.168.2.32): 56 data bytes

–- 192.168.2.32 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

M552 on panel shows as still connected to access point.
So it disconnects from router but thinks its still connected

dc42

Thanks. Does your router still think it is connected, or not? You will need to login to the admin page of your router from your browser to find out.

Jarery

Router believes its dropped and no longer shows it on the client list.
M552 shows it still connected

KeeganB

This looks like good info Jarery. Thanks!

I just finished configuring my new router, so now I am testing the first print on a completely new network. (I started from scratch)

KeeganB

Dare I say it?

24mins into a print and no disconnects, this is a record for me.

Ill be kicking myself if it was some network quirk on my network.

JohnOCFII

@KeeganB:

Dare I say it?

24mins into a print and no disconnects, this is a record for me.

Ill be kicking myself if it was some network quirk on my network.

Hopefully it'll fix things for you. If it does, though, that begs the question of what is different about the WiFi board on the Duet Wifi (or it's firmware) in comparison to the other devices on your WiFi network that (I assume) continued to work well when the DuetWiFi was having issues.

I haven't yet upgraded past 1.18.2 yet. I used to have regular timeouts when I connected to the printer via it's DNS entry. Someone here suggested I connect to it via IP address, and it has been much more stable for me that way. I do still get the occasional disconnect, usually after a print has been completed and the system has been idle for 10 or more minutes.

John

KeeganB

Yeah, that will be the odd part. All my other devices have been perfectly fine. This includes several devices set up for remote access, via ports and etc, wireless printers, mobile devices, airplay stuff, etc…

My network hardware was getting pretty old, and I had been considering an upgrade so this was as good a time as any.

Print finished in 50 mins and I'm still connected. 2 hours of connection: 50mins print, and 70 mins idle. This is feeling pretty good.

dc42

@Jarery:

Router believes its dropped and no longer shows it on the client list.
M552 shows it still connected

Thanks, that's very useful information. It sounds like we can't trust the status call of the ESP8266 SDK to tell us whether the WiFi is still connected to the AP. This is going to be a problem for us because the SDK is closed source. We may need to ping the router regularly to determine whether the connection is still alive.

Please confirm that you are running version 1.19.2 of both DuetWiFiFirmware and DuetWiFiServer, by looking at the Settings/General tab in DWC.

Jarery

I’m at work and not in front of my printer to screenshot the data, but I can confirm both are displaying 1.19.2

callil

Feel bad piling on here, but same timeout issues in 1.19.2 for me. I've checked everything with M122. Slightly poor connection (-58db) but otherwise there is nothing outstanding I can find. My experience sounds very similar to Keegan's.

Some other details:
• Disconnects when not printing
• Always a timeout error
• Stays connected for about 30 seconds on average
• Uploading or sending commands often causes it to disconnect (CPU issue?)
• Cannot re-connect after (requires hard reset on board)

I was already getting a bunch of disconnects in 1.18 but I chalked that up to signal strength, but its gotten worse.
Let me know if there is any way I can help.