Issue Details
Controllers may enter an Invalid Configuration state due to an alarm-related issue on the server. In affected cases, the controller may reboot repeatedly (for example, 10 events in less than one hour) and fail to return to an operational state.
The reboot log may include entries similar to the following:
2025-04-24 13:04:22 | Unknown | TrendAlarm|??? in AlarmQueryActiveTrendInstancesResponse_Parse.vi->TrendAlarm.lvlib:Process.vi->Main
2025-04-24 13:05:14 | Startup |
The device log may also display the following error:
2025-04-24--13:04:23.69406 | ControllerMajorOps | TrendAlarm|??? in AlarmQueryActiveTrendInstancesResponse_Parse.vi->TrendAlarm.lvlib:Process.vi->Main.vi|-375005
2025-04-24--13:05:50.75474 | | ERROR: Code:-375005 @ ??? in AlarmQueryActiveTrendInstancesResponse_Parse.vi->TrendAlarm.lvlib:Process.vi->Main.vi
This condition can prevent the controller from returning to a normal
operational
state.
Solution
To restore the controller to an operational state, follow these steps:
1. On the server, open the Alarm Event window.
2. Review all active alarms.
3. If any alarm displays an Infinite or NaN value:
- Clear the alarm.
- Acknowledge the alarm.
4. Verify that the cRIO returns to an operational state.
Recommendation:
After performing a system upgrade, clear and acknowledge all alarms to reduce the risk of this issue occurring.
Do you need more help?
Submit your questions or requests using the Support Ticket Submission form.