Wireless Communication Setup (Home & Competition)

[SaMSoNhs]

Thank you for the answers!

Unfortunately I have tried resetting router a few times(pressing the reset button for 10-15 seconds) and still kept having the same problem.

I am using a windows 7 laptop if that matters.(I have tried connecting router to the different computers and got No Network Access error for the ethernet connection in each of them)

[adammiller3122]

On the computer that you are using, try running the troubleshooting wizard by right clicking on the network indicator in the task bar, and selecting the troubleshooting option. See if that turns anything interesting up.

[timytamy]

Try the following procedure, I've never actually used the bridge configuration utility, I prefer to set it up manualy (and show students how to do so) because it both works better, and give a better understanding of how the network works.

1) Start with a completely clean/reset router. (ie Do a reset using a paperclip into the button near the power connector), and connect to PC via Ethernet.
2) Set computer ethernet IP to 192.168.0.40*
3) Using a browser, log into DLink (192.168.0.50). Go to network settings and change IP to 10.TE.AM.1 After saving, the DLink will log you out.
4) Set computer IP to 10.TE.AM.40*.
5) Log back into DLink, go to advanced settings -> DHCP settings. Set the IP range to be 10.TE.AM.100 - 199*, netmask 255.255.255.0, default gateway 10.TE.AM.1
6) Go back to wireless setup (ensure you go to manual, not automatic) and set the SSID to TEAM*, etc.
7) After you disconnect your computer, make sure you go change the PC IP settings back to DHCP

Hopefully that will work for you.

* all these need to be in a specific range to work, and can take on other values. I just picked a number that I know works.

As general info, a big thing to watch out for is a conflict between static and DHCP IP addresses. If, on one network, you have the DLink giving out ips in the range of 10.TE.AM.100-199, you CAN NOT set a static IP on your computer in that range (so 10.TE.AM.123 would be illegal) however, IPs out of that range (and on the same subnet) are allowed (for example, the cRIO at 10.TE.AM.2 would function fine with a DHCP server giving out 10.TE.AM.100-199)

Secondly, do all this with the roboRIO off. From the roboRIO manual:

The first time you power up the chassis, it attempts to initiate a DHCP network connection. If the chassis is unable to initiate a DHCP connection, it connects to the network with a link-local IP address with the form 169.254.x.x .

I'm not sure if the roboRIO keeps the IP, or for how many power cycles. Nonetheless I've made sure that I only power on a roboRIO with a network which has DHCP running, and haven't had any problems.

[Mark McLeod]

Normal operation at home would be to connect wirelessly for ease of driving freely. It can be handy to have the DLink serve DHCP for both the roboRIO and the PC, but even without that the DLink will usually work with just about any settings, even the default factory settings.

Try this for wireless robot operation:

• On your PC, wireless needs to be Enabled and set to DHCP.
• The Ethernet adapter can be Disabled to simplify this testing or at least set to DHCP if you want to tether directly to the robot DLink.
• On the PC there is a list of AP's the PC wireless has found. Do you see your team number listed as one of the available networks?
• Does your PC label any other network access point as "Connected"? If so then you need to Disconnect from it and Connect to your team number AP.
• After Connecting your PC to your team number network, the message should be "No Internet Access" or "Limited network access." That would be normal, since the robot's AP isn't normally connected to the Internet.
• Start the Driver Station app and on the Diagnostics tab (second one down on the left) you will see a list under "Pinging..." See what gets a green light in that list. It should be green for Bridge and Robot.

[SaMSoNhs]

I want to thank all of you for the answers. Thanks to you I was able to setup wireless communication successfully today.

@adammiller3122
Troubleshoot suggested me to reset the access point, but resetting did not help.

@timytamy
I followed your suggestions and it worked!

@Mark McLeod
After following instructions at the previous post, I was able to connect AP(which is named as my team number)