Can ping CRIO and bridge, but DS shows no comm and no code

[Green2]

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

[murthyz]

Hello Barry !

                 We actually had the same problem . Did you try disabling the wireless on your classmate PC.And also turn off your windows firewall on the classmate PC.
Check out your driver station account and it should be running fine !.

Regards,

Murthy

[NI-Bob]

Hello Barry,

Murthy has hit the nail on the head on some of the major things to check out.  The one piece that I wanted to clarify a little further is make sure that you are not logged into the Driver Account and the Developer Account on the Driver Station.  Basically, what happens is if there are two instances of the Driver Station Application running at the same time (one automatically launches in the Driver account, and then you manually launch it in the Developer account) you will not see communication for one of the instances.

So depending if you are running in Debugging mode in the Developer Account or Competition mode in the Driver Account you just need to be aware of the state of the rest of the Classmate.

One other suggestion if these things do not help.  Try turning on the robot and once it has come up, hit the reset button on the cRIO (you will need a paper clip, small screwdriver, pen, etc. in order to push the button).  This will reboot the cRIO again with everything else on the robot already running.  If this ends up being the solution please let us know as R&D is currently looking into startup behavior.

I hope this helps!  Have a great day!

Thanks!
Bob H

NI FIRST Support

[Green2]

Thanks for the replies guys!

Turning off the firewall (we already had wireless disabled) did the trick! Thanks Murthy!

We are having some bridge connection issues. But we do have another wireless network going in the same room. I have been having to turn the other wireless router off, then reboot the robot, then reboot the robot router before everything is connected and happy. Granted...the other wireless router may not be the problem and it may be the boot up sequence issue that others have noted...so I'll keep the resetting of the cRIO trick in mind and will report findings when I have to use that procedure.

Thanks again for the help!
Barry

[MarkGryzwa3206]

We have the same problem but are not connected to the CRIO yet.  Trying to build it up from router to bridge.  Cabled is working fine by wireless from the router or another PC even is unable to see the bridge at 10.xx.yy.1