Bridge and roboRio cannot connect to eachother

[JacobD]

Hello,

I cannot receive a bridge signal to the roboRIO no matter what I try. I currently have the bridge configured using the tool and wired via ethernet to the roboRIO. But, when turning on the robot, the only status lights that comes on are the power and RSL indicators. Also, when trying to connect the computer to the bridge, it is unable to authenticate. It will connect but say "No internet Access" with an X on it. Keep in mind that I am using 2.4ghz wireless.

A side note: when trying to tether the robot, I still cannot get connection. Last year we used a batch file to edit the internet settings. Do we need one this year? If yes can someone direct me to where to get one or what to write inside of one.

[Joey1939]

Have you tethered via usb and imaged the roboRIO? If not the rio won't be assigning its self an ip and that is no fun.

Can you connect to the roboRIO webdashboard when tethered via usb?

When connected to the bridge is your computer assigned an ip via DHCP? (aka are you using this years utility)

Have you tried pinging the bridge at 10.xx.xx.2? Have you tried pinging the roboRIO at roborRIO-xxxx.local? Have you identified the roboRIO's ip and pinged it?

I am just throwing out ideas because I don't know what you mean by they "cannot connect to eachother". This year the radio should be configured to auto-assign the correct ip address to connected computers. When connected to bridge you will always see "No internet Access" because you aren't connected to the internet, but it will still work.

EDIT: I reread your post, and it occured to me that you might mean the radio light on the roboRIO. Contrary to the roboRIO manual, the radio light on the roboRIO hasn't been implemented.

[JacobD]

Originally Posted by Joey1939

Have you tethered via usb and imaged the roboRIO? If not the rio won't be assigning its self an ip and that is no fun.

Can you connect to the roboRIO webdashboard when tethered via usb?

When connected to the bridge is your computer assigned an ip via DHCP? (aka are you using this years utility)

Have you tried pinging the bridge at 10.xx.xx.2? Have you tried pinging the roboRIO at roborRIO-xxxx.local? Have you identified the roboRIO's ip and pinged it?

I am just throwing out ideas because I don't know what you mean by they "cannot connect to eachother". This year the radio should be configured to auto-assign the correct ip address to connected computers. When connected to bridge you will always see "No internet Access" because you aren't connected to the internet, but it will still work.

EDIT: I reread your post, and it occured to me that you might mean the radio light on the roboRIO. Contrary to the roboRIO manual, the radio light on the roboRIO hasn't been implemented.

Thanks for the help.

I indeed was talking about the radio light on the roboRIO. Thanks for clarifying that it has not been implemented. Also, by USB, I can connect to the roboRIO. But, when tethering from the laptop directly to the roboRIO, there is no connection made. By that, I mean that the driver station does not see the roboRIO at all. Also, as far as the utility you mentioned for this year, I am using last year's bridge configuration tool with last year's bridge. Do I need to use this year's bridge because of firmware loaded onto it?

Also, I have tried DHCP as well as a static IP to connect to the wireless bridge with no luck.

[Mark McLeod]

Use this year's Bridge Configuration Utility, it has changed along with the new control system. The DLink gets setup as a DHCP server, so it can assign the laptop and the roboRIO the proper compatible IP addresses automatically.

You need to use a configured DLink between the laptop and the roboRIO for it to operate properly this year. We don't connect directly to the roboRIO with Ethernet anymore, we use USB if we want to connect directly.

[JacobD]

Originally Posted by Mark McLeod

Use this year's Bridge Configuration Utility, it has changed along with the new control system. The DLink gets setup as a DHCP server, so it can assign the laptop and the roboRIO the proper compatible IP addresses automatically.

You need to use a configured DLink between the laptop and the roboRIO for it to operate properly this year. We don't connect directly to the roboRIO with Ethernet anymore, we use USB if we want to connect directly.

Ok, thanks for the information. I thought that USB vs. Ethernet was optional. I will try the new tool and let you know.