How to Deploy an InsightCM Device: Checklist and Workflow

Issue Details

This article walks through the complete process of deploying an InsightCM device, in the correct order, from verifying the device image through confirming valid data in the Test Panel. Follow it when you are setting up a new device from start to finish. If a step fails, the article points you to the matching troubleshooting procedure so you can resolve the fault and rejoin the flow.

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 latest device image and firmware available for the device.
  2. A hardware configuration (InsightCM technology type, controller, and C Series modules) that matches both the requirement and the physical device.
  3. Network details for the device: static IP address, subnet mask, and gateway.
  4. Ping access from the InsightCM Server (or a host computer) to the device.

 

Table of Contents

1. Quick Deployment Checklist

2. Step-by-Step Procedure

3. Data Validation in the Test Panel

 

Instructions/Solution

The diagram below shows the full deployment flow and the two points where a failure branches into a troubleshooting procedure. Review it before working through the steps.

device-deployment-workflow.svg


 

1. Quick Deployment Checklist

Use this as a pre-flight summary. Work through the items in order; connectivity and the four-test gate must pass before sensor mapping, and data validation is the final confirmation.

Device image is the latest available — verify on the Software tab of the device configuration page.

Firmware is the latest — verify in NI MAX, or in InsightCM by showing the Firmware column on the Software tab of the device configuration page.

Hardware configuration (technology type, controller, and modules) matches both the requirement and the physical configuration.

Network cable is connected to the lowest-numbered Ethernet port on the controller.

Network settings are configured correctly — static IP address, subnet mask, gateway.

IP address and MAC address of the device are documented.

Ping succeeds from the server (or computer) to the device.

☐ Device is added to the server as an online device.

☐ Device passes all four tests — IP Address, Application, Connection, Hardware.

Sensors are mapped to channels and the configuration is updated.

Data is validated in the Test Panel.

 

2. Step-by-Step Procedure

Verify the device

1. Confirm the device image is the latest available on the Software tab of the device configuration page.

2. Confirm the firmware is the latest, in NI MAX or by showing the Firmware column on the Software tab.

3. Confirm the hardware configuration (technology type, controller, and modules) matches both the requirement and the physical device.

Establish connectivity

4. Connect the network cable to the lowest-numbered Ethernet port on the controller.

5. Configure the network settings: static IP address, subnet mask, and gateway.

6. Document the device IP address and MAC address.

7. Ping the device from the server or host computer. If the ping fails, this is a network/connectivity issue — engage IT and see Troubleshooting Network Connection Issues in cRIO before continuing. Re-run the ping until it succeeds.

Add to the server and pass the four tests

8. Add the device to the server as an online device.

9. Run the Test Connection and confirm the device passes all four tests — IP Address, Application, Connection, and Hardware. If any test fails, see Troubleshooting the InsightCM Test Connection (4 Tests), resolve the failing test, then continue.

Map sensors and update the configuration

10. Map the sensors to channels and update the configuration.

Validate the data

11. Validate data in the Test Panel, as described in the next section.

 

3. Data Validation in the Test Panel

This is the final confirmation that the deployment is correct.

  1. Check for expected values and ranges.
  2. Check for expected waveforms.
  3. Confirm nothing was mapped incorrectly — for example, verify you are not receiving a tachometer waveform on a channel that should carry an accelerometer signal.


 

Outcome

The device passes all four Test Connection checks, its sensors are mapped to the correct channels, and the Test Panel shows expected values and waveforms with no cross-mapped signals. The deployment is complete.

 

Related Articles

How to Deploy and Troubleshoot an InsightCM Device

Troubleshooting the InsightCM Test Connection (4 Tests)

cRIO Status LED and RESET Button Reference

Getting Started — Adding Cutsforth Monitoring Devices

Overview of the InsightCM System — Setup Process Overview

Troubleshooting Network Connection Issues in cRIO

 

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