Cannot Connect to Duet 3 Web Control
I was able to connect to the web control once, but the next day, I couldn't seem to connect to it again. I followed the instructions from this page: https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7. Right now, it seems like the emulator is not behaving the same way as it was last time. The configured IP address displays as what I set it fixed to, but the actual IP address is just displayed as 0.0.0.0. I believe last time, this was flipped the other way. Is anyone able to walk me through this process?
fcwilt last edited by
Please post the contents of your config.g file using the </> tag.
@fcwilt How can I find the config.g file? I am very new to this so I apologize about being unknowledgeable. When I had access to the duet 3 Web control, I saw the config.g file, but now I cannot even get connected to the web control.
If you have access to the Duet over USB terminal send M552 to get a read back of the current IP address. What does it report? Still 0.0.0.0?
Send M552 S1, what does it report back then?
@phaedrux I will check this right now. Could you confirm my connections? I currently have a USB connection to my laptop with the micro USB on the board. I then have an ethernet running from the board to my router. I also tried with the ethernet from my board to my computer.
If you connect ethernet between your computer and Duet you must configure a static IP address on both. If you're connecting to the router, the router can issue a DHCP IP address to both as long as the Duet is configured to request one.
You can retrieve your config.g from the SD card in the Duet by putting the SD card in your PC and looking for it in the /sys/ folder.
@phaedrux My config.g file has been untouched and when I had access to the web control, it was extremely empty.
@phaedrux When I type in M552, it reports "Ethernet is enabled, configured IP address: 192.168.2.2, actual IP address: 0.0.0.0 <LF>ok<LF>". I set my computer IP address to 192.168.2.1. Also when I type in M552 S0 and then M552 S1 P192.168.2.2 (to set the IP address), I only get ok <LF> as a response. Not sure if this is normal.
Bolded portions are taken off the guide/documentation linked in my original post (Step 10).
DHCP: Most home routers are setup to assign IP addresses by DHCP. Send M552 S0 to disable networking, then M552 S1 P0.0.0.0 to enable networking and have your router assign an IP address.
- When I type in M552 S1 P0.0.0.0, I simply get ok<LF> as a response. It doesn't reply with Network running and the IP address the duet is using. Typing in M552 after to check, it just says "Ethernet is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0 <LF>ok<LF>".
Fixed Address: You can set the Duet to use a fixed IP address. Note that if you use a fixed address, care should be taken that it does not conflict with other devices on the network. Send M552 S0 to disable networking, then M552 S1 Px.x.x.x to enable networking, where "x.x.x.x" is the IP address you want to use, eg 192.168.1.15.
- When I type M552 S1 P192.168.2.2, I get the same response of ok<LF>. Then when I type M552, I get "Ethernet is enabled, configured IP address: 192.168.2.2, actual IP address: 0.0.0.0 <LF>ok<LF>".
In both cases, after 10-30 seconds the board should reply with Network running and the IP address the Duet is using. Send M552 to check the settings.
-This does not happen for me. I never get the network running response.
Do you see the link light on the ethernet port on the Duet light up at all?
@phaedrux Where is that? Right under the ethernet port? I do not see a light on.
Do you have the ethernet cable connected to your router or your computer?
Can you please post your config.g from the SD card? I'd like to see what it's set to do at startup.
Can you also send M122 in the terminal and copy and paste the results?
@phaedrux Right now I have it connected to my computer and I am trying to configure/set an IP address. I also set an IP address on my computer. I also tried connecting it to the router, but that did not work either.
M122 command: === Diagnostics ===<LF>RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)<LF>Board ID: 08DJM-9P63L-DJMSS-6J9DD-3S06Q-TBFR8<LF>Used output buffers: 1 of 40 (1 max)<LF>=== RTOS ===<LF>Static ram: 149788<LF>Dynamic ram: 92564 of which 120 recycled<LF>Never used RAM 116360, free system stack 164 words<LF>Tasks: NETWORK(ready,545) ETHERNET(blocked,211) HEAT(blocked,297) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1130) IDLE(ready,19)<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:44:08 ago, cause: power up<LF>Last software reset at 2021-06-30 14:15, reason: User, GCodes spinning, available RAM 117132, slot 0<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Aux0 errors 0,0,0<LF>Aux1 errors 0,0,0<LF>MCU temperature: min 39.1, current 49.6, max 49.7<LF>Supply voltage: min 0.2, current 23.6, max 23.7, under voltage event[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]
I cannot upload a screenshot of my config file because it is over 4096 kb... It is EXTREMELY blank. This is all it has (I typed it out).
;Default config.g template for DuetPi
;Replace this with a proper configuration file (e.g. from https://configtool.reprapfirmware.org)
;Display initial welcome message
M552 P192.168.2.1 S1.
I can't see anything in your photo. What am I looking at?
Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]
Please configure YAT to use the correct line break format so we can see the fulll report.
@phaedrux I realized the image was impossible to read. Sorry. It was meant to be the config.g file.
When I was on the web control, I changed the 0.0.0.0 to 192.168.2.1
@phaedrux My version of YAT does not have these settings. It looks different.
@frank-0 Is the "ETHERNET(blocked,211)" section of this text a concern?
Are you using a single board computer like a raspberry Pi with your duet3 right now?
@phaedrux No I am not. I realized the error with the network commands was because the SD card got loose. I am trying to get a wired network connection (ethernet) and access the web control page.
https://duet3d.dozuki.com/Wiki/Setting_up_networking_on_Duet I have read and looked at this page as well.
So with the SD card back in place are you having better luck?
@phaedrux Better, but still not completely working. Is it possible to connect via just USB instead of using the ethernet/networking?
How does it behave now? Are you able to connect to the web interface or not?
Does the SD card have the correct files in the /www folder?
You can stream gcode over USB from a sender program like octoprint or simplify3d or pronterface, but you lose a lot of features including speed and quality.
@phaedrux When I try to set up the networking, I get this on YAT: . Visiting this address on a browser does not work. I just want to connect to the Web Control
fcwilt last edited by
You have to have on the SD card a basic config.g and the files for the web interface.
Do you have those on the SD card?
Visiting this address on a browser does not work.
What do you actually see in the browser when you try to go to that address?
Are you able to ping that address from your computer?
What IP address does your computer have?
This will help us confirm if you're able to communicate with the Duet over the network.
Can you show us a screenshot of the contents of your SD card?
At minimum it should have a folder structure similar to what is shown here: https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure
If the /www folder is missing or empty, you won't be able to connect to the web control even if the network connection is good. If it's missing or empty, you can replace the files using this zip file.
Extract the contents of that zip file into the /www folder.