We are having a weird problem with communicating to the robot using wireless.
First, we were able to re-image the crio and had it running basic code with a kit bot using a tether. The updated drive station is working properly and image is showing up good while using a tether.
The problem is with the wireless communication.
All the wireless components seems to be communicating properly. I am able to log onto the wireless bridge using IE and get to the 10.xx.xx.1 IP. Same with the router…which is using 10.xx.xx.4. The classmate PC is set to 10.xx.xx.5. Pinging the cRIO is also good at 10.xx.xx.2. Note that on the driver station, all the above mentioned components are green (meaning getting a ping response). That was done all using wireless from router to bridge, but wired connection from classmate PC to router.
But the problem is that the DS is still showing “no communication” and “no code”. The robot can not be enabled (not even to run the default code that was set to run at start-up) because of the no communication problem. The weird part is that we were able to deploy code to the cRIO using the classmate PC (using wireless).
We have reset the bridge and router multiple times and re-did the setup just as many times. Still not working properly.
More details: The bridge is set to run at 2.4Ghz as per the instructions for the 160 router.
Any ideas on what the problem could be?
Thanks!
Barry