CONSTANT AJAX disconnect errors

dc42

Glad you got it working! I'm sorry I was short with you earlier on.

TimVukman

3 hours at idle. Did not disconnect

TimVukman

I'm sorry I expressed my frustrations out loud. Normally I'm much more patient.

At some point I am going to reconnect the IR Sensor. I was getting the 4 red flashes shortly after power up, and then at about 10 mm it would register 408/409. At 3 - 5 it would register 440 - 441, but it never went over 500. I did try a completely different cable with the same results, so if you could give that some thought, I'd appreciate it. The green light on the edge of the board means my 3.3v is ok, right?

I'm using limit switches on all axis now, but I would use the probe on the hot end for bed leveling, as soon as I can print up a bracket for it!.

Thanks,
Tim

dc42

I am fairly certain that either you have the OUT pin from the sensor connected to the wrong pin on the Duet (it should go to the pin marked IN on the underside of the Duet, which is the end one next to the PanelDue connector), or you have a bad crimp connection in that wire.

TimVukman

I will check the pins. I did not build either of the two cables that I am using. There is no doubt that I was careful to make sure that the orientation of both ends of the connects matched between what I took out and what I put it, so it the original was backwards, it's replacement would also be backwards.

I should ask a more important question. Is the cable three wires at both ends? I ask because if signal out from the sensor should go to the in port on the wifi board probe connector, I will not have a 4th pin on my cable to pick up 3.3v from the other end of that probe connector. Which every way I go, I have 3 lines from the sensor going to 4 lines on the board. I thought one end on the wifi board was not used,.

I will look it up to be sure. I'm trying to reset my movement settings since all the gcode files were replaced when I deleted /sys and installed fresh with the firmware. Yes, you're right! It would have been wise of me to have written my gcode files out somewhere when I could get at them and they were working. You can bet I will when I get them fixed.

KeeganB

@Dougal1957:

I have started to run into the dreaded AJAX Disconnect prob but have tracked it down to the router (Netgear D6400).

It would disconnect after anything from 2-5 hours or so not actually timed it but seems like that Router is only 8 feet max away from the Duet and only Chipboard/plasterboard between them.

Have plugged in my TP-Link TL720N in as an AP Extender and all is now good S I am now suspecting that some of the issues may well be the AP's in use but can't categorically confirm this.

Duet is on 1.20A7

Incidentally spent a few hours yesterday and Friday evening trying to get a friend of mine's Replikeo supplied Duet0.6 working and it came out the his Virgin Hub would not communicate with it at all plug it thru a TP-Link router that he had lying around and it came straight up again telling me that there are some flaky network routers out there.

Just thoughts

Doug

Your thought on the APs is interesting. Currently I am running 1 Airport Extreme Base Station and 3 Airport expresses. 2 are set to extend the network, and the 3rd is just set to join the network (it handles a POE switch in my attic for security system).

Tomorrow my new router will be here (Tenda AC18) and I will do away with all of the previous network hardware (except the attic stuff) and start the network from scratch.

Jarery

I continue to have wifi connection issues.
Disconnects mid print
Disconnects when sitting idle
Disconnects part way through a G32 calibrate routine.

On a possibly related note. I happened to be watching the print screen right at the time prior to a disconnect.
The temperature/time graph, which has a very straight line for temp, was suddenly going very jittery, such that the right side 1/4 of the line was suddenly 1/4" high of very compact squiggles as temp was read high/low.
I was about to take a screenshot when it disconnected, and of course the histogram disappears…....

I'm using a PT100 on a smart effector system. The temp line, when I'm actually connected and can see it, is typically very straight, maybe a minor bump every now and then. This was a solid couple of min (1/4 of the time line) where it was extremely erratic temp readings. Then a disconnect.

May be related, maybe not, as it also disconnects in a calibration or idle when there is no temp.

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