How to Deploy and Troubleshoot an InsightCM Device

Issue Details

This article is the starting point for deploying an InsightCM device and resolving the most common issues you may hit during setup, connection, and mapping. It consolidates the core procedures — deploying a device, validating connectivity with the Test Connection workflow, and clearing invalid configurations — and routes you to the dedicated article for each task. Use it as an index: identify your situation in the When to Use Each Procedure table, then open the linked article.

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

Prerequisites

1. InsightCM Server access with permission to configure devices.
2. An InsightCM device built on NI CompactRIO hardware with supported C Series modules.
3. Network details for the device: static IP address, subnet mask, and gateway.
4. Command Prompt access on the server or host computer (for network diagnostics).

Table of Contents

1. Overview of the Deployment-Then-Troubleshoot Flow

2. When to Use Each Procedure

3. Sequence and Dependencies

4. Reference Material

1. Overview of the Deployment-Then-Troubleshoot Flow

A successful deployment follows a fixed order: confirm the device image, firmware, and hardware configuration; establish network connectivity; pass all four Test Connection checks; map sensors to channels; and finally validate data in the Test Panel. If any stage fails, you branch into the matching troubleshooting procedure, resolve the fault, and rejoin the main flow. The articles below cover each stage and each branch.

2. When to Use Each Procedure

Find your situation in the left column, then open the linked article in the right column.

3. Sequence and Dependencies

Follow these rules to avoid chasing the wrong fault:

1. Connectivity and the four-test gate must pass before sensor mapping. Do not map sensors until the device passes all four Test Connection checks.
2. The four tests are sequential — each builds on the previous one, so resolve a failing test before interpreting the next.
3. When clearing an invalid configuration, confirm the Test Connection passes first. If the connection itself fails, fix that (Troubleshooting the Test Connection) before troubleshooting configuration faults.
4. Data validation is the final confirmation. After mapping, validate expected values, ranges, and waveforms in the Test Panel, and confirm nothing was mapped incorrectly.

4. Reference Material

These references support all of the procedures above:

1. cRIO Status LED and RESET Button Reference: confirm boot state and recover network settings — [LINK: cRIO LED & RESET Reference]
2. InsightCM Device Diagnostic URLs (port 8002): firmware, connection, hardware, hostname, and log endpoints — [LINK: Device Diagnostic URLs]
3. Network Troubleshooting Commands: ping, tracert, pathping, netstat, arp, nslookup — [LINK: Network Troubleshooting Commands]

Outcome

You have identified the correct procedure for your situation and opened the matching article — or, if you followed the full deployment flow, you have a device that passes all four tests, has its sensors mapped, and shows validated data in the Test Panel.

Related Articles

Deploying an InsightCM Device: Checklist & Workflow

Troubleshooting the InsightCM Test Connection (4 Tests)

Clearing an Invalid Configuration on an InsightCM Device

Transferring a Connection File to an Offline Device via USB

Troubleshooting — Server-to-Device Connection

Overview of the InsightCM System — Setup Process Overview

Getting Started — Adding Cutsforth Monitoring Devices

Troubleshooting Network Connection Issues in cRIO

Do you need more help?

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