Lost my connection to my Duet
-
Started my machine as normal this morning. Executed home all as normal, then part way through heating the nozzle (my home all and home z files have a command to heat the hot end to 140 to soften any plastic before probing the bed), DWC froze and then I got a disconnect error message. Since then, I am unable to connect to the board via wifi. I can connect using Pronteface. I can send M503 and it reads back my config.g. All the LEDs on the board look normal. I've sent M552 S1 via Pronteface but that hasn't helped.
On the list of WiFi networks on my 'phone I can see "DuetWiFi" Then underneath that "No internet access detected, won't automatically connect". So I guess that's normal?
When I try to connect from my PC I get an error to the effect that the connection has timed out because the server is taking too long to respond.
What to check or do next please.
-
If you can see the DuetWifi access point that means your board has lost connection with your wifi router
You need to connect to that access point and go to 192.168.1.1 and input the wifi login info again
https://duet3d.com/wiki/Getting_connected_to_the_Duet_WiFi -
Tried that. From Pronteface I just did M552 S0 followed by M552 S1 to restart the WiFi server. This is what came back.
SENDING:M552 S0
WiFi server stoppedM552 S1
SENDING:M552 S1
WiFi server starting up
DuetWiFiServer version 1.03 (ch fork)
Flash size 4194304, free RAM 32376 bytes, WiFi Vcc 3.10V, host name: duetwifi, reset reason: Turned on by main processor
WiFi is running as an access point with name DuetWiFiNo IP address given. Tried logging in to 192.168.1.1 - no connection timeout. Checked my home hub and it shows the Duet wifi as present but disconnected. The IP address (DHCP) has always been 192.168.1.100. and that hasn;'t chnaged. I can't connect using that IP address either.
-
Just want to make sure that you have connected to the 'DuetWifi' access point before trying 192.168.1.1?
-
Well I thought I was (connected to the access point that is) but my 'phone is a bit flaky. Just tried it on my wife's laptop but that just fails to connect to duet wifi. It shows up as an available network but won't connect. Looking at my 'phone again, it tries to connect, looks like it's connected, but then after about 15 seconds it tries to connect again. Seems to do this 3 times then reverts to connecting to connecting to my router.
-
Just tried again using my 'phone. Fairly sure that after many attempts I managed to connect to the access point long enough to enter 192.168.1.1 but all I get is a blank page. Nowhere to select any wifi network or enter any password. I've managed to start a print using Pronteface and as near as I can tell, everything else is working as it should. Just can't connect or use DWC. What do I do now?
-
Have you tried pressing the erase button and re-flashing the firmware from SAM-BA?
-
How about putting the Wifi FW File on the SD Card in the SYS Folder rename it to how it should be and do the M997 S1 from Pronterface I think it is this should reload the firmware to the Wifi Module may also be worth doing DWC the same way just in case they have been corrupted
Doug
-
Dont think it will be the Firmware Simon has he can use the board thru the usb so that to me prooves the main system
-
Everything is working fine apart from the fact that I can't access it via wifi. I'm reluctant to start messing around erasing and reinstalling firmware as who knows what else I might bu**er up in the process. It was working fine then DWC froze while I was heating the hot end and since then, I haven't been able to connect. Difficult to see how the software could have got corrupted while the system was just waiting for the hot end to get up to temperature.
-
My suggestion above wont take the main firmware out but may recover the Wifi remember that is a separate CPU itself and IIRC the DWC sits on it as well
-
Really need David or Tony's input to know for sure?
-
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?
