Lost my connection to my Duet
-
Reflashing the WiFi firmware might solve it if that has become corrupted. Otherwise i suspect a hardware fault on the ESP. A possibility might be some sort of issue with the 3.3V level causing the ESP to misbehave but just high enough not to bother the SAM4E8E (but that's unlikely).
-
The WiFi firmware was My thought Tony at least it should prove it one way or another and shouldn't stop the printer from working?
-
I'll give that a go when this large print has finished in a few hours time.
-
I agree, try reloading DuetWiFiServer.bin.
-
Wonderful. Pronteface decided to disconnect after nearly 6 hours so that print is scrap plastic. No idea what caused that as I can reconnect via Pronteface no problem.
Never mind, at least it gave me chance to reload DuetWifiServer.bin which I have done. After doing M997 S1 the installation progress all seemed to go as it should. About 30 seconds later I got a message to the effect that the duet was running as an access point. Managed to connect to it with my 'phone but when I enter 192.168.1.1 all I get is blank page. I've tried about a dozen times. Because my 'phone won't stay connected for long, I've saved the tab with 192.168.1.1. so that I can enter it really quickly after logging on but no joy - just a blank page.
What next please? (Can't trust Pronteface so I'm a bit stuck).
-
I came to the forum today to see if there was anyone else having a similar issue to me, and it seems this might be it, although I'm not using a DuetWifi.
I updated 2 of the 4 RepRapPro Fishers I have here (that use Duet v0.6 boards) to version 1.17e yesterday. Previously, one was running 1.17b and the other was running 1.17d and have been printing without issue almost non-stop until the update. After updating neither unit managed to complete a print - they just just stopped randomly and the Duet reset. Each did this a number of times but I could still log back into the web interface.However, mid-print I opened the web interface to check the estimated time and as soon as the page began to load the printer crashed again, except this time I could not log back in properly even after power cycling. I could occasionally get come of the page to load, but never all of it and it never managed to get to the password prompt. I could tell from listening to the fan and watching the LEDs on the board that it was in a boot cycle. I manually downgraded the firmware back to 1.17d and I have done a number of prints now without issue. I managed to get the same boot cycle brick on the second printer by repeatedly opening the web interface. Again, rolling back to 1.17d seems to have stopped the problem. FWIW, the original upgrades to 1.17e were done differently on each machine - one via USB/bossac and one via the WebInterface.
-
Possibly your wifi module has developed a fault. Other than that, I'm wondering whether your phone is giving up on the Duet access point too soon because it knows you have another access point with an Internet connection. You could try temporarily telling your phone to forget the connection to your wifi router, maybe then it will stay connected to the Duet for longer. Although my Android phone seems to stay connected to the Duet access point for long enough without me having to do that.
I am getting close to starting the work on the wifi module code rewrite. I've done the design work already.
-
Possibly your wifi module has developed a fault. Other than that, I'm wondering whether your phone is giving up on the Duet access point too soon because it knows you have another access point with an Internet connection. You could try temporarily telling your phone to forget the connection to your wifi router, maybe then it will stay connected to the Duet for longer. Although my Android phone seems to stay connected to the Duet access point for long enough without me having to do that.
I am getting close to starting the work on the wifi module code rewrite. I've done the design work already.
David,
I don't think it's the 'phone because when it gives up on the connection and I try to connect, I get an error message to say that it could not connect. When the phone successfully connects, I get no error message, just a blank page when I try 198.168.1.1.
But of course it begs the question why did DWC suddenly lose connection while waiting for the hot end to heat and why did the Duet suddenly reverted to becoming an access point, when it's been running fine for months?
-
It does rather suggest a hardware fault. Tony, can you take Ian's board back for testing, with a view to replacing it?
-
For info, I tried logging into duetwifi again with my wife's laptop but just get a message to the effect that windows was unable to connect.
