Cannot connect to DWC Simple fix??
-
This is not my strongest area to be working in, so it is very frustrating when I get it to
work and now it doesn't. I unplugged the duet from the USB ate lunch came back to reconnect
and back to square one. Now no YAT. Saying com5 is closed, and no wifi of course.
Device manager see's it plugged into com 5??? What am I missing.I do understand handing out IP address above a certain range, but shouldn't the device always
have the same IP, once it is set. -
@AMPMAKER said in Cannot connect to DWC Simple fix??:
I unplugged the duet from the USB ate lunch came back to reconnect
and back to square one. Now no YAT. Saying com5 is closed, and no wifi of course.
Device manager see's it plugged into com 5That is odd. When I first started with a Duet WiFi I had the odd problem with WiFi but I never had a problem using the USB connection. Perhaps you already have another instance of YAT running and connnected to COM5? Windows only allows one connection at a time to a COM port.
I do understand handing out IP address above a certain range, but shouldn't the device always
have the same IP, once it is set.If a device like a Duet is setup to use DHCP every time it powers up/resets and asks for an IP address it may get a different one.
The only way to insure that it ALWAYS gets the same one is with a IP reservation. If you can find a link to the manual for your router I will be glad to take a look and see if and how IP reservations can be done.
Frederick
-
Frederick thank you for the offer, I will keep that offer a bit, but if I don't work this through I may never learn
how it's done. I have been able to get back to a YAT connection with the Duet. Still no internet Although.M552
WiFi module is connected to access point ORBI, IP address 192.168.1.4<LF>ok<LF>
M587
Remembered networks:<LF>TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0<LF>ORBI65 IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0<LF>ORBI IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0<LF>ok<LF>I did find this on instructables.com Whats your thought on trying it.
https://www.instructables.com/id/Duet-WiFi-Activate-and-Connect-the-WiFi-When-It-Do/
I did contact the company that sold the Duet to us and he suggested a different router 2.4 of course just
for the duet. But I think that isolating the IP is the most Logical. -
I found this post from
dc42 ADMINISTRATORS 8 Mar 2018, 12:54
Either:- Send M552 S0, then send M552 P192.168.1.xx, then send M552 S1. You should then be able to connect DWC. In DWC go to the System editor and edit the M552 command in config.g to have that IP address.
Or:
- Move the SD card to a PC and use a text editor to make the same change to the M552 command in config.g.
So I was able to get connected to the DWC again, I just don't know if I turn this off if it will reconnect.
We shall see. The IP recorded in the config.g was different than the IP that came up when entering the
M552 command.Do I always have to go thru YAT to get to DWC or should it come up when the Duet is powered on??
-
Hi,
Read about M552 a little more closely.
Notice:
"On the Duet 2 WiFi running firmware 1.19 and later, the IP address is set in the M587 command when you configure the access point details."
Once you get the WiFi configured correctly it is saved in the WiFi hardware "flash" memory and you can connect any time you power/reset the Duet.
Frederick
-
@fcwilt Concerning YAT not connecting, what was described above is what happened to me. I opened a second instance of YAT and got connection errors. I also closed all connections and had some issues connecting back again.
-
I am having this same issue:
Duet 2 WIFI running 2.03 suite of firmware and drivers from github
Made it through Step 8 in the "Getting Connected to your Duet" guide
Connection to YAT works great
Connection to Pronterface works great
M552 returns:
ok
WiFi module is connected to access point SkyNet Guest, IP address 192.168.0.192
My tp-link router shows a wireless client at the 192.168.0.192 address but cannot identify it. (shows a "*" )I am clearly set up and connected, but I get the "can't reach this page" error every time. (I've tried both the IP address and the duettest.local routes)
-
@spudaddict said in Cannot connect to DWC Simple fix??:
WiFi module is connected to access point SkyNet Guest, IP address 192.168.0.192
The "Guest" part suggests to me that it is configured for client isolation. Which means a WiFi device connected using that SSID can see the Internet but nothing else on the local network. And nothing else on the local network can see the device.
Frederick
-
@spudaddict said in Cannot connect to DWC Simple fix??:
WiFi module is connected to access point SkyNet Guest, IP address 192.168.0.192
Can you ping 192.168.0.192 from the PC where you are attempting to connect a browser?
-
You could try setting the Duet WiFi up in access point mode to check that it's definitely your network. I agree through it sounds like the Guest segment of your network could be restricting access.
-
Thanks to all that helped get us connected. Configuring the access was the final answer to
getting connected. Now I can turn on the Duet board and it will find our wifi.
Now on to the next hurdle, to actually configure the setting to this printer.
When I re-load the config.g to the board with the new setting will this stage of connection be lost.Maybe this should go to a new discussion.
I have hard wired all the motors, five in all two extruder motors. Optical limit switches and heaters ect.
I also have a Panel Duet 5i. I get no response from the panel, but I guess that is because I have not configured
and uploaded the new parameters. Still new to setting this up so should the old Config.g file be saved before
loading a new one? Does any on have a config file for a JGAurora A8 printer?Mark
-
@AMPMAKER said in Cannot connect to DWC Simple fix??:
Configuring the access was the final answer to getting connected.
Hi,
What exactly do you mean by that?
Thanks.
Frederick
-
@AMPMAKER said in Cannot connect to DWC Simple fix??:
Send M552 S0, then send M552 P192.168.1.xx, then send M552 S1. You should then be able to connect DWC. In DWC go to the System editor and edit the M552 command in config.g to have that IP address.
Send M552 S0, then send M552 P192.168.1.xx, then send M552 S1. You should then be able to connect DWC. In DWC go to the System editor and edit the M552 command in config.g to have that IP address.
Maybe the lingo was not correct..sorry