How to Troubleshoot the InsightCM Test Connection

Issue Details

The Test Connection runs four sequential checks — IP Address, Application, Connection, and Hardware. Each test builds on the previous one, so you must resolve a failing test before interpreting the next. This article explains what a pass confirms for each test and how to act when one fails. You typically reach it from step 9 of the deployment workflow, or from the procedure index, when a device does not pass all four tests.

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

The device has been added to the InsightCM Server.
The device IP address.
Physical access to read the controller status and USER1 LEDs.
Command Prompt access on the server or host computer (for ping and router checks).

Instructions/Solution

1. What Each Test Confirms

Test	What a pass confirms
1. IP Address	A device with that IP is on the network and is reachable by ping.
2. Application	The device has an InsightCM image.
3. Connection	The device has credentials and can communicate with InsightCM.
4. Hardware	The physical hardware matches the configured hardware.

2. Decision Flow

The diagram below shows the four tests and how each pass or fail routes you to the next action. Resolve a failing test before moving on.

Test 1: IP Address

If IP Address passes, a device with that IP is on the network and responds to ping. Continue to Test 2.
If it fails, check whether other devices occupy a similar IP range, and ping the intermediary routers and the final router before the InsightCM device.
If routing is fine, check the LEDs on the hardware (see cRIO Status LED and RESET Button Reference).
If the LEDs are on and USER1 is blinking, the device is healthy and this is a network issue — engage IT.

Test 2: Application

If Application passes, the device has an InsightCM image. Continue to Test 3.
If it fails, the device may be in safe mode or have blocked ports. Check the device LEDs:
1. USER1 blinking: the image is present but communication ports are blocked. Engage IT.
2. USER1 not blinking: the device has no InsightCM image. Deploy the image from InsightCM, or from NI RAD (the LabVIEW Replication and Deployment utility). To deploy with NI RAD, first download the InsightCM device image from Navigation Menu > Utilities > Package Management.

Test 3: Connection

If Connection passes, the device has credentials and can communicate with InsightCM. Continue to Test 4.
If it fails, the device is missing credentials. Run a Reset Connection:
1. If the reset works, the connection is restored.
2. If the reset fails, the connection port may be blocked. Engage IT, or download the connection file and apply it via USB flash drive (see Transferring a Connection File to an Offline Device via USB).

Test 4: Hardware

If Hardware passes, continue with the mapping process (see Deploying an InsightCM Device: Checklist and Workflow).
If it fails, the device does not match the configured hardware. Verify the hardware configuration at
```
 http://<IP_Address>:8002/device/hardwareInfo 
```
and confirm the physical modules.

Outcome

All four tests pass and the device is ready for sensor mapping — or you have identified the failure category (network, image, credentials, or hardware) and the path to resolve it.

Do you need more help?

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

Was this article helpful?

0 out of 0 found this helpful

Articles in this section