We are having an error connecting to our robot using wireless. It works perfectly fine when we are tethered in. But when we try to connect using wireless we get an error saying “Windows was unable to connect to 5175.” I have looked everywhere and I cannot find an explanation why only the computer with code cannot connect wirelessly. Another thing to note is that the D’Link is listed as “Unidentified network” when we are tethered in if that is an issue.
Are you using a static IP address or dynamic? If dynamic, try changing to a static address of 10.51.75.5 (this will need to be done individually for Ethernet and wifi). It should come up as Unitdentified Network over the tether.
All I know thus far is that I used the Bridge Configuration Utility tool in the most recent update suite. I’m not sure where to tell if it is static or dynamic or what the tool configured the d’link to.
The question is - how is the driver station computer getting an IP address? It will be in your network setup on that box. If you can’t find it, let us know what OS you’re using there.
Sorry for the late reply I didn’t have access to the computer. I’m not exactly sure what i’m looking for or where to find it but I am on Windows 7.
Look here for instructions to change your IP address. It should be a static IP address of “10.51.75.5”. (a.k.a. select “Use this IP address”) If it already was something like that (10.51.75.*), try changing it to DHCP and see if that works (a.k.a. select “Obtain an IP address automatically”).
Personally I have found the simplest setup to be using the RoboRIO setup to provide DHCP (which I think it is the default setting) and then making sure that your wireless connection on your laptop is configured to use DHCP as well.
The roboRIO webdashboard (accessible through the USB connection) will show you this:
The laptop wireless config should look like this:
The most important part is that they match… either both set for DHCP or both set for a fixed IP address.
I just checked and they both match but my computer isn’t even showing the robot as an obtainable address. I can’t try and connect to test if it works because I cannot see the network.
Do you mean that you do not see your network (5175) listed when you look for wireless networks to connect to from your laptop?
Does the list of wireless networks shown by your PC list “dlink” as a possible connection?
(That’s the default SSID for the DLink and it will be this if the DLink was reset but not FRC programmed.)
Is the switch on the back of the dlink set to AP 2.4GHz or AP 5Ghz rather than bridge?
(Needs to be on one of the AP settings AND match what your PC wireless supports. All PC’s support 2.4GHz, but some do not support 5GHz.)
Are two blue lights showing on the front of the dlink?
(There are three LEDs on the front of the DLink. For normal operation there will be a blue power light-on the left, and a blue AP-in the center.
The right blue Bridge light is usually only for competition field use, so it normally should be off for home use.)
Correct when I try to search for the dlink network all I find is my school’s network. There is no other network listed.
There is no other connection listed other than my school’s network. The Dlink is set to 2.4GHz same as we always set it to. Both the normal operation lights are on. I previously reset the router and imaged it using the Imaging tool included with labVIEW so it should appear as 5175
Did you make sure the Router is set to AP (not Bridge) mode?
There are ways to hide the SSID, but you’d have to do it on purpose by changing a setting on the DLink.
I’d suggest:
- Moving the switch to 5GHz and waiting for it to reboot to see if it shows up
- Checking with other computers/phones to see if they can see it (for both 2.4GHz & 5GHz settings)
- Taking just the DLink home to see if it can be seen away from the school environment (some can suppress unrecognized APs).
- Resetting once again to the factory defaults, but not using the FRC tool on it right away. See if the default “dlink” shows up in your list of available networks.
If it still doesn’t show then the DLink wireless may be broken.