cRIO Locks Up - RT

[Starla_T.]

I would agree with some earlier posts that this sounds like you code is requiring 100% CPU usage.  When a code requires 100% CPU usage, the first thing the operating system will do is drop communication to the outside.  It may appear like the cRIO is locked up, when in reality it is running, but all of it's threads are in use.   Try adding wait functions in your loops.   Also, make sure any loops that are not time critical, are not marked that way. 

Hope this helps,

Starla T. 

[gsussman]

For cRIO applications, I have generally found it to be good practice to put the toggling of the User1 LED in my main loop. This will often times give me some indication as to what is going on in the program (program not running, running too slow or running at the correct speed). Even if the communication has been lost the LED will toggle and can give you some basic indication as to whether the controller is locked up or has suspended the communications based on 100% CPU use

[Robert_Hoffman]

For what its worth, I think I may have found the culprit, but I am not positive yet.  We are using Ethernet/IP to talk to a PLC via the second ethernet port, and using standard TCP/IP to communicate to the PC on the first port.  IP addresses got changed due to a mixup on the first port that put the first and second port on the same subnet.  There were other complicating factors here due to the exposure of the CRIO to the plant network that may have had external influences, but so far isolating the first and second ports on the CRIO has seemed to do the trick.

Rob

[gsussman]

You can run Ethernet over an EtherCAT network if you use an EtherCAT to Ethernet gateway (Ethernet tunnels through the EtherCAT network) but it will not work the other way around.