How to Clear an Invalid Configuration on an InsightCM Device

Issue Details

This article explains how to clear an invalid configuration on an InsightCM device and then isolate the root cause, working from the broadest checks (asset tree, log files) down to module- and channel-level isolation. Start by clearing the invalid configuration and re-running the Test Connection. If the connection itself fails, resolve that first before chasing configuration faults.

The procedure applies to InsightCM (all current versions) running on devices that use National Instruments (NI) CompactRIO (cRIO) hardware controllers and supported C Series modules.

Prerequisites

1. The device has been added to the InsightCM Server and is accessible.

2. Access to the asset tree and the Device Health page.

3. The ability to download device log files.

4. The device IP address (for the diagnostic URLs).

Table of Contents

1. Decision Flow

2. Procedure

3. Notes on Critical Sensors

Instructions/Solution

1. Decision Flow

The diagram below supports the procedure: it shows how each check branches and where to go next. Use it alongside the numbered steps.

2. Procedure

1. Open the Action menu and select Clear invalid configuration.
2. Run a Test Connection:
   1. Passes: the fault is configuration-related (a bad module, channel, or error). Continue below.
   2. Fails: troubleshoot the connection first (see Troubleshooting the InsightCM Test Connection (4 Tests)).
3. Check the asset tree:
   1. Any invalid configurations for that equipment or device?
   2. Any disabled equipment or sensors for that equipment or device?
4. Check the log files:
   1. Download the log files from the device configuration page and review them.
   2. Use the diagnostic URLs (see InsightCM Device Diagnostic URLs).
5. Check the Device Health page:
   1. If the device has been in the invalid-configuration state for a long time, send Clear invalid configuration and observe CPU and memory usage as the device runs into the error and reboots.
   2. If the device is crashing on memory or CPU, review the sampling rate, file length, and number of data events collected (too many).
6. If the log files point to a specific module, troubleshoot it: test the module, then replace it if it is confirmed faulty.
7. If the error is channel-level but the channel is not identified, deactivate some sensors (mapping does not need to be undone). Be careful not to deactivate critical channels used in calculations — for example, a tachometer or the RPM/speed reference used to define the operating state.
8. If the device has multiple equipment mapped (for example, an MCSA device can carry up to nine equipment), disable equipment one at a time to narrow down the fault.
9. If the issue remains unresolved, contact the Cutsforth support team (see Do you need more help? below).

3. Notes on Critical Sensors

Deactivating a sensor preserves the mapping, you do not need to remap when you re-enable it. Always preserve critical sensors and calculations, such as the tachometer or RPM/speed reference, and any other channels referenced by operating-state or other calculations.

Outcome

The invalid configuration has been cleared and the root cause isolated to a specific module, channel, or equipment, or the case has been escalated to the Cutsforth support team with the log files and observations you gathered.

Related

How to Deploy and Troubleshoot an InsightCM Device

Troubleshooting the InsightCM Test Connection (4 Tests)

InsightCM Device Diagnostic URLs

Troubleshooting — Server-to-Device Connection

Do you need more help?

Submit your questions or requests using the Support Ticket Submission form.