Help with connection issues.

[Elfonzo]

We're trying to get last years robot working and are having trouble getting LabView to recognize the robot after we re-imaged the C-rio. Other online resources say its the computer, we tried three. We've already changed the IP address and stuff, necessary for re-imaging. The computer does, but LabView simply refuses to, detect the robot when left click connect is selected.

[Greg McKaskle]

Did the imaging tool complete correctly? If so, does the driver station see the cRIO? If the project doesn't connect to the cRIO, it could also be because the target address in the project hasn't been updated. Does it show the 10.te.am.02 in the parenthesis on the line of the cRIO.

Greg McKaskle

[Elfonzo]

Greg, thank you for the quick response.

We were able to image the cRIO from the 2gopc netbook. So far out of our three computers, that was the only one that would properly image the cRIO. We are completely baffled by this and don't know why none of the other computers can image the cRIO. That being said, after we imaged the cRIO, we haven't been able to load code. Our first thought is to try loading code with the netbook that we were able to image the cRIO with, but the netbook does not have LabVIEW on it and we aren't confident on the netbook's ability to run labVIEW.

So when we plug the computer in directly to the robot, the computer recognizes that there is something plugged in, the driver station sees that there is a robot, but we do not get robot communications (the light is red).

In the diagnostics section of the driver station, this is the error message we are getting:
"Warning<Code> 44002 occured at Ping Results: link-GOOD, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-GOOD, FMS-bad Driver Station
<time>10/1/2013 4:04:51 PM <unique#>32
FRC: Driver Station ping status has changed."

When we open labVIEW, the IP address is set at 10.9.31.2 (and is displayed next to the "RT CompactRIO Target).

When we try to connect to the robot via labview, we receive the error "Unable to resolve from current dialog" and "Failed to connect to Real-Time target.

As background, we changed around our IPv4 IP Address to 10.09.31.5 and disabled wireless connections. We have also completed the Bridge Configuration Utility.

[Greg McKaskle]

I think I'd start by looking at the firewall settings. It sounds like it may be blocking some of the communication ports. It may be that this network is classified as public or whatever the "dangerous" one is.

Greg McKaskle

[Invictus3593]

On top of what Greg said, I'd also check the IP of your PC's network adapter and make sure that it's 10.te.am.5.

The "Ping Status Changed" error you got is normal. It's like a built in watchdog, nothing to worry about, but if you still have problems, I'd open up the Driver Station Log Viewer and check to see how many packets you're losing in that connection. A while back we were losing a lot of packets due to a bad network driver.

[Elfonzo]

Yes, the PC's adapter setting is 10.9.31.5
We turned our firewalls off as well. We have tried several different computers, all with the same results. We have not checked the Driver Station Log Viewer yet. Thank you again for your help.

[Tommy F.]

This may not be beneficial, but have you been trying different Ethernet cables?

If you can't find a solution by next week, I'll be more than happy to come over and give you a hand, if not just to provide another computer to see if we can get it working. Just PM me when you meet and I'll see if I have time in my schedule.