After coming back from the regional, we unpacked the robot and stored it in a corner. Two weeks ago we received a request to demo the robot at the Lion’s organization. When we fired it up, it started doing all kinds of weird things (devices running at startup with no autonomous code). As long as we were tethered to the cRIO everything worked. However, there is no communications between our router and the wireless bridge on the robot or the wireless bridge and our computer.
I suspect that the update of the Wireless bridge at regional is now stopping us from communicating with the robot. Has anyone else experienced anything similar?
I’m with Ed on resetting the Regional’s wireless bridge security.
Here’s a previous post discussing what to do.
There’s something really wrong though if your robot starts running as soon as you turn it on without the Driver Station enabling it.
Any more detail about that, preferably the simplest series of steps to get it to do that?
E.g., 1) Driver Station disconnected, 2) robot power main breaker switched on, 3) robot starts moving.
After resetting the router, bridge, and pc, and then reconfiguring everything, the bridge doesn’t seem to be working (the Wireless part).
Using Ethernet cables I connected the bridge directly to the PC. I reset the appropriate IP Address and made sure there weren’t any security settings. I connected the bridge to the router and the PC to the router and I could ping the router, bridge, & PC. I tethered to the cRIO and it pinged.
I then hooked up everything for wireless. I could ping the router but not the bridge. I’m beginning to believe there is a problem with the bridge.