Problems with Connecting to cRio.
 

Hi

Just recently I have had problems deploying code onto the cRio. Everytime I try to deploy code onto the cRio, the terminal which shows the progress of the deployment stops and a window comes up that says "Failed to Connect to Real Time Target" These problems have only started this afternoon, and I have been able to connect to the cRio for the last week. Here is some extra info:

-I am using a cRio 2 with the following modules attached
- Analog Breakout
- Solenoid Breakout
- Digital Sidecar
-We are connecting directly to cRio via a crossover cable.
-The model of the laptop that I am using is an HP dv6-6153CA
-We also have this problem when using different computers and cables.

I have done the following to try and stop this problem:

- Make sure that the ip address is set to something that correlates with my tam number (i.e. 10.13.25.xxx) and the subnet mask is set to 255.255.255.0
- Restarting my computer
- Restarting the cRio
- Re-opening the project in LabView
- Restarting the robot.

Any help would be greatly appreciated.

Re: Problems with Connecting to cRio.
 

If the Dashboard is running when it stops downloading, that is a potential cause. If that's the case just stop the Dashboard before attempting a transfer.

If it's due to cRIO processor overload, then setting the NoApp switch, resetting the cRIO, turning the NoApp switch off again may help.

Re: Problems with Connecting to cRio.
 

Where is the NoApp switch? Is it on the cRio, or on Labview? If it is a cRio overload, are there any other possible solutions to the problem?

Re: Problems with Connecting to cRio.
 

For a cRIO II you get to the NoApp switch through the cRIO Imaging Tool.

If it's a cRIO CPU overload, then that's a code problem that can be fixed.

Re: Problems with Connecting to cRio.
 

How's your battery voltage?

Does the Driver Station connect to the cRIO okay?

Do you have any other network interfaces active on the laptop, or do you have multiple IP addresses assigned to the wired interface?

Re: Problems with Connecting to cRio.
 

Have you try to reformat the CRIO? It should fix it.