This VI is an example of how one could programmatically handle the case where error/warning 66030 appears in RT code due to the scan engine being in in incorrect operating mode.
Example code from the Example Code Exchange in the NI Community is licensed with the MIT license.
The real question is why does this happen in the first place? I notice that when I get a cpu spike sometimes something trips and the scan engine starts spewing 66030 warnings.
The mode is in Fault condition so I usually just reset the target, but really need to prevent this from happening in the first place.
Hi,
I have one cRIO 9074 and two cRIO 9144 using EtherCAT into Scan Mode and sometimes I receive the error 66030. Then I try to put the code that you suggest. So, now I receive the same error 66030 followed by -66450 error.
I try to stop program and start again and the happens the same. If I restart cRIO (Project Window > cRIO > Utilities > Resart) it solves the problem until next time.
Any idea about how to solve it automatically?