We followed the networking instructions in the FRC manual to setup the Robot Bridge and Router. After changing the settings on both devices and a laptop, we are able to connect to the router, but not the bridge.
Our laptop doesn’t have an N-adapter, so are connected to the router (via DS) by a wired connection. We’ve also tried connecting the laptop directly to the router.
When we tried reconnecting an ethernet cable between bridge and router, we get an IP address conflict notice on the computer. We think this is because the bridge is connecting through wireless and wired with same IP address.
Any thoughts? There is some ambiguity in the manual about where the router should start allocating dynamic addresses, (the screenshot says 10.XX.YY.1, but the text says 10.XX.YY.10). We tried both, and think 10 is correct, but not sure if this has anything to do with the problem
For IP conflict, we restarted our computers and it was fine.
Remember to turn off all the network security settings on your PC, router, and bridge.
I think the text is correct since that is working for most teams including our team.
10 is correct. That prevents the router from automatically assigning addresses in the range that FIRST is reserving and using for our static addresses (.1-.6).
I’d examine the static addresses of each device (laptop, router, bridge) to verify the IP addresses and other settings. You can connect your laptop directly to the bridge with a standard ethernet cable to check out it’s settings.
Thanks for the replies.
The system is working now, just a couple notes in case they might be helpful to someone else:
After having mucked up the set-up, we were trying to start over by using the Factory Reset button on the wireless bridge, changing the IP address of the router back to the original value in the setup, and starting the FIRST instructions again from the beginning.
This approach didn’t work until I changed the SSID name on the router to something other than my team number before setting up the bridge. Leaving the correct name would cause a conflict as soon as I changed the SSID on the bridge. After doing this, and following the instructions correctly from the beginning, everything worked.