New Install - Cannot Reach Web Interface
-
@dc42 just got my Duet Ethernet out of the box and I am having the same issue as RetiredinNC. I have been following the guide here. Please see attached screenshots from YAT and the command line. When I send the M552 S1 command after an M552 command, nothing happens (I waited for a few minutes after sending that command) When I send a M552 S0 command, followed by an M552 S1 command, it indicates that the network is running, but I cannot ping the device and cannot reach the web interface by typing the IP address into the my web browser. I know next to nothing about networking and am out of ideas. Thanks for your help.
-
It looks like your config.g file still contains the commands to set the network parameters that were used when your Duet was tested at the factory. I suggest you remove the M540, M552, M553 and M554 commands from config.g and put just M552 S1 in their place. After starting the Duet, run M552 from YAT to find what IP address your router has allocated to the Duet.
-
Thanks for the quick reply. Removing these commands from the config.g file would need to be done by plugging the SD card in and modifying the config.g file in notepad, right?
-
@benwilde said in New Install - Cannot Reach Web Interface:
Thanks for the quick reply. Removing these commands from the config.g file would need to be done by plugging the SD card in and modifying the config.g file in notepad, right?
Yes, until you have the network connection working. So instead you could try sending M552 S0, then M552 P0.0.0.0 and finally M552 S1.
-
Ok. Great. After entering those commands, It did send back a new IP address. I can now ping that IP address. However, when I enter that IP into the web browser, a blank screen is all I see (chrome). It does seem to reach that address, but there is not web control there. http://duettest.local/ does not work either.
-
Here's a bit more information from using the M111 commands mentioned earlier in the thread.
-
The duettest.local address doesn't work on the Duet Ethernet, only on the Duet WiFi. So use the IP address instead.
The 404 response suggests that the /www folder on the SD card or its contents is missing.
-
Great. I’ll look into this tomorrow. I need to go buy an adapter so that I can get the micro sd to load into the sd card slot on my laptop. Theres not a better way to access the files, right? It can’t be done through usb, with the card still in the board, right?
-
@benwilde said in New Install - Cannot Reach Web Interface:
Great. I’ll look into this tomorrow. I need to go buy an adapter so that I can get the micro sd to load into the sd card slot on my laptop. Theres not a better way to access the files, right? It can’t be done through usb, with the card still in the board, right?
There is limited access to the files on the SD card via USB, but it isn't easy to use.
Does your laptop have a full-size SD card slot? If so, have you bought an SD card recently? These days, when you buy an SD card, what you usually get is a micro SDHC card plus an adapter to turn it into a full size card. So if you have a digital camera, you may already have an adapter inside it.
Assuming you bought the Duet as a Duet Ethernet and didn't convert it from a Duet WiFi, it seems odd that it is behaving as if the /www files are missing. Perhaps there is an issue reading the SD card. If you run M503 from YAT, does it list config.g? If you run M122, does it say the SD card is present and the interface speed is 20Mbytes/sec?
-
I did indeed buy the Duet Ethernet. It is not a conversion. I found a micro sd card reader. I forgot that I had one. The /www folder looks to be in order. I have attached screenshots of the files. I also sent the M122 command, and have attached the screenshot. It seems that the SD card is working fine based on the M122 command. However, when I first started up the board, it went to run config.g and threw and "daemon length overflow" error. Could that be causing the issue?
-
Update- Web control did indeed come up this time after I reset the IP address. Not sure why it didn’t work before. I will continue working through the quick start guide by editing the config.g file. I haven’t had a chance to mess with this as I had to run out the door right after the web control came up.
