LabView Connectivity Issue - HELP NEEDED

[Neurovirus]

Just a few days ago, we had labview and the driver station set up with mandatory update #2, and the cRIO with image 7. I was able to download and run code from labview without issue. I went home, wrote some more code, came back and ran into a very frustrating problem. When i deploy code from labview, it deploys to the robot, and the driver station detects the battery voltage for a moment, before losing connectivity. labview tells me that it is waiting for the real time cRIO to respond. eventually it times out, and the deploying is canceled. Sometimes, the code doesnt even deploy, it tells me that its waiting for the RT cRIO to respond as soon as i click "deploy". What i realized is that this is the same exact error that one gets if they try deploying when the robot is powered off.

So i updated everything. the driver station and labview are now at the most recent versions, and the cRIO has image 11. I powered on the robot, and for a full minute (new record), the driver station had communications with the cRIO. but the moment i tried deploying code, i ran into my original error. As of right now, I have a laptop running labview plugged in via cable to port 2 of the driver station, which is connected via port 1 to our router. the robot has its wireless link, which is connected to port 1 of the cRIO. somewhere along that chain of communication, the signal is getting lost. Any thoughts? anyone else run into this problem?

[Greg McKaskle]

As a test, bypass the wireless stuff. Connect directly from the DS to the cRIO via an enet patch cable.

If the problem goes away, which I suspect it will, you need to revisit the setup for the gaming adapter and/or the router.

Greg McKaskle