big problems with cRio

[tavwtby]

I have been trying to build a vi that will communicate with the cRio 9014. I had a vi working, I was communicating and reading all ins and outs. Then the PC froze up. When I tried to deploy, I got an error of a realtime conflict. I thought I resolved this because I was then able to communicate with the vi I had made in version 2011. The PC froze up again, after all morning communicatiing and working on the project, now I cant connect to the cRio any more. The deployment takes a while then I get an error "Failed to connect to real time target" I am about to loose it here. This happened to me twice and I had to start over. Any ideas on why this is happening?

[Jed394]

You might try opening the distributed system manager and removing all processes.  After this you will have to redeploy all variables and vi's.  You might also open max and reboot the devices, double check the network settings, and worse case you could format the crio and start from scratch.  

[tavwtby]

Actually I have two rio's. I wasn't having any lucjk with either, so I decided to format the second one, and now it's IP address is 0.0.0.0, and I can't access it to change the IP. When I go to network settings, it tells me there is no network adapters. I had them working, I don't have a solution to this, and I'm out in California from the east coast to fix this and I'm stuck

[Jed394]

This article may help you

http://digital.ni.com/public.nsf/allkb/ABE4BC247E8AC9BC8625734E005CAB42

[Alisha_P]

The article Jed394 posted has pretty comprehensive troubleshooting steps for a cRIO that you can't connect to in MAX. If you're connecting your cRIO directly to the computer via a crossover cable, here's another document that may be helpful: http://digital.ni.com/public.nsf/allkb/72AE8CADA1AF075686256A16005D55B1

The most important thing when trying to configure your cRIO is getting it within the same subnet as the computer you are accessing it from.

If you're having problems accessing it over a network, you might try connecting directly to it via a crossover cable. For trying to connect to a cRIO with a 0.0.0.0 IP address, make sure all your firewalls are temporarilly turned off.

If you consistently see the cRIO disconnecting when you deploy a VI to it, then you may be overtaxing the processor. Make sure that you have only the software installed that you need and that you have appropriate wait times in your programs loops. If you install System State Publisher, you will be able to view the memory use and CPU use of your cRIO from the Distributed System Manager. We recommend you keep the CPU usage below 75% .