CONSTANT AJAX disconnect errors
-
I really wish there was some way I could reproduce the problem you are experiencing. AFAIK you are the only user who finds 1.19.2 less reliable than 1.18.
Downgrading to 1.18 you will need to do a simultaneous install of both DuetWiFiFirmware and DuetWiFiServer. If the board was shipped with 1.19 firmware originally then you will also need to install DuetWiFiFirmware.bin on the WiFi module.
Then you will need to follow the connection instructions for 1.18 and earlier.
-
i also find 1.19.2 less reliable than 1.8 with regard to the wireless/ajax issue. (sorry I'm not really helping with the debugging at the moment, house for sell, can't use my printer as often as I wish)
-
Thanks David.
My board was shipped with 1.18.
I understand that network issues are near impossible to replicate. I wish there was more detailed log info or something I could get to you. I am able to force a reconnect via USB with M552 S-1/S1
The real frustration comes when doing calibration prints and etc. It disconnects so quickly I can't make any adjustments easily; baby stepping, extrusion, temp etc to do on-the-fly adjustments. That, and every time I want to start a new test print I have to go through the reconnect process every time.
I feel pretty confident my network is not the issue, but I have been toying with the idea of upgrading my router and other network equipment, so maybe I will do that now just in case. I've also considered taking on my my extra routers and setting up a clean dummy network to test.
David, is there any possible advantage in doing a "clean" install of 1.19.2. Meaning, could/should I format the SD card and do a completely clean install of everything, and then just paste in my config values as needed?
-
Thanks David.
David, is there any possible advantage in doing a "clean" install of 1.19.2. Meaning, could/should I format the SD card and do a completely clean install of everything, and then just paste in my config values as needed?My thoughts also.
I'm also not happy with 1.19 in regards to 1.18.
All the additions are awesome, and I always use volumetric extrusion and other features not in 1.18. But if i have no method of connecting to the system the features it has are a moot point. -
I Did have an issue to start with which was almost instant disconnects I fitted an AP Extender and got round it but then when I moved the printer back to it rightful location the issue re-appeared turns out my WiFi AP Credentials for the original AP was corrupt deleting them and re-applying fixed the problem not saying it will fix you issues but may be worth a try?
FWIW I am using a netgear WiFi router (D6400)
-
Sorry Dougal,
I am not following what you are suggesting? Are you saying the credentials saved to the DUET for connecting to your AP were bad?
-
yes indeed
-
Thanks, I will certainly try that. It won't hurt anything and if it resolves this issue, Ill be ecstatic!
-
Use the M588 to remove it from the list first before trying to re-instate it
-
I didn't have much time last night, but I tested your idea Dougal. Nope
-
I didn't think it would TBH your symptoms are different to what mine were but it was worth a try.
-
Yeah, I wasn't holding much hope, but it was easy enough to give it a shot! Thanks
-
Hi
I am jumping in here too as I had written my own post on this issue between last night and today. I will collect some data based on the gcodes posted here that will provide the data. I have not been able to connect today because I upgraded to 1.20.7 and something must have gone wrong because now I can't get the Wifi to initialize.I can say that I never had the connection to the printer drop when I was running 1.18.2. That says the connection from the printer to the network and from the DWC to the printer both had enough signal strength. I will get the numbers if I can.
-
Hi
I am going to try to downgrade to 1.18.2 since that is when everything was working properly. I currently can't initialize the Wifi module. Any way to test if it is ok? -
Hi
I am jumping in here too as I had written my own post on this issue between last night and today. I will collect some data based on the gcodes posted here that will provide the data. I have not been able to connect today because I upgraded to 1.20.7 and something must have gone wrong because now I can't get the Wifi to initialize.Did you follow the upgrade instructions at https://duet3d.com/wiki/Upgrading_to_DuetWiFiFirmware_1.19 ? In particular, the but about using M587 to enter your WIFI access point ssid and password.
-
Send M552 S-1
wait for it to complete
Send M552 S1
Try that?
-
Hi dc42
Yes, to the letter.
I'm stuck trying to downgrade back to 1.18.2
Erased the board
tried bossac with the drivers installed.
listcomports returns COM5 - Escher 3D - USB\lots of characters
bossac.exe –p=COM5 -e -w -v -b DuetWifiFirmware returns
No board found on COM5Frustrated beyond belief
-
Why do people insist on erasing the firmware, when it is almost never necessary?
-
Hi dc42
To be very clear, I did not choose to erase my firmware and never would have.
I am trying to recover from my firmware quitting on it's own. I was trying to setup the IR Probe. The board went from connecting reliably and functioning very nicely to not connecting at all and indicating USB errors.
From there I followed the troubleshooting documentation on the Wiki.
Suggesting that I chose to erase the firmware on my own is not going to help me set the board up so that I can use it.
Perhaps the documentation should be revisited so that it is consistent, located in a single place with suggestions on what to look for to aid in understanding what has gone wrong and flow-charted with a path to follow.
Even better would be a software tool that could be started on the board if not remotely (or set as the temporary boot path on the memory card) that could look at the board / firmware and tell the user if it was ok - ie don't erase me, I'm fine! Even a statement in the installation instructions to the effect of "Don't erase the firmware - it is almost never necessary" would help.
In my other thread last night you indicated that there was a bug in windows that shut down the USB ports if they switched too quickly which would render them looking like they were gone.
Maybe the troubleshooting documentation should have proposed a way to make sure that the ports were properly reset before it suggested the erase / reset course of action. Windows users would never find themselves coming across this bug in the normal usage of windows where USB connects are not frequently even disconnected or changed.
There are a large number of posts on this forum indicating that people are experiencing issues with connections and the 1.19 release of firmware. If the process was functioning properly and properly documented, there would not be so many posts.
The documentation states that the process implemented in this has changed, and upgrading needs to be handled carefully. That would be a good place to include some of the information and suggestions that have come to light - before people like me start troubleshooting the situation based on the physical evidence they are looking at.
I am very understanding and I know well how things do not always go according to plan. I also know that there are frequently unforeseen issues that could not have been predicted that crop up and cause issues. I also would only post as a last resort, which in this case was too late.
I appreciate your assistance and I wish to work through the issue to recover my board.
I am moving slowly in my other thread and documenting everything that is happening, trusting that we will recover the board, so I will not be off trying things on my own that might make sense to me based on what I am seeing.
Tim
-
The process to recover a non-working board is documented at https://duet3d.com/wiki/What_to_do_if_your_Duet_or_Duet_WiFi_won%27t_respond. I've just added a couple of steps.
HTH David
