NI InsightCM 3.3 Known Issues

Overview

This document contains the InsightCM 3.3 known issues that were discovered before and since the release of InsightCM 3.3. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.

Known Issues by Category

The following items are known issues in InsightCM 3.3 sorted by Category.

InsightCM Monitoring Devices
696438 Users cannot set Modbus TCP Unit ID
InsightCM SDK
- 3.2 and earlier SDK Custom Devices are Incompatible with 3.3 Server
699027 cRIO-9039-Sync not supported in InsightCM SDK 3.3
InsightCM Web Application
680791 Users are unable to create Baselines Data Events for Thermal Camera ROI and Delta Features
703685 Adding Modbus Data Source channels to device causes OPC Historian update issues
724575 Cannot export data from EMSA Spectrum chart
686624 Server-only Features are selectable as Delta EU Operating State Triggers



699027

ID Known Issue
InsightCM Monitoring Devices
696438

Return
Users cannot set Modbus TCP Unit ID
The Unit ID is always set to 1 for Modbus TCP connections. There is no way to set the Unit ID in the InsightCM Web Application.

Workaround: N/A

Reported Version: 3.1    Resolved Version: 3.4    Added: 06/1/2018
InsightCM SDK
-

Return
3.2 and earlier SDK Custom Devices are Incompatible with 3.3 Server
Due to changes to in 3.3 application, custom devices developed with the InsightCM SDK 3.2 and earlier are incompatible with InsightCM 3.3 server. To migrate custom devices to 3.3, contact NI Support for best practices and possible migration paths.

Workaround: n/a

Reported Version: 3.0    Resolved Version: N/A    Added: 06/1/2018
699027

Return
cRIO-9039-Sync not supported in InsightCM SDK 3.3
Support for the cRIO-9039-sync is not included in the cRIO Module Detection, which is used by InsightCM Device application.

Workaround: Add support for the in cRIO-9039-Sync in the cRIO Detect Module.lvproj, located at C:\Program Files (x86)\National Instruments\RT Images\cRIOHWDetectLibrary\FPGABitfiles, and compile the ReadEEPROM bitfile. After, use WebDAV to move the bitfile to cRIO file system at /usr/local/natinst/hwdetectfpga/

Reported Version: 3.2    Resolved Version: N/A    Added: 06/1/2018
InsightCM Web Application
680791

Return
Users are unable to create Baselines Data Events for Thermal Camera ROI and Delta Features
Baselines Data Events can not be set by users for Thermal Camera ROI and Delta Features.

Workaround: N/A

Reported Version: 3.2    Resolved Version: -    Added: 06/1/2018
703685

Return
Adding Modbus Data Source channels to device causes OPC Historian update issues


Workaround: N/A

Reported Version: 3.2    Resolved Version: 3.4    Added: 06/1/2018
686624

Return
Server-only Features are selectable as Delta EU Operating State Triggers
Users can specify these server calculated only features as a source for delta EU triggers. Features that are calculated on the server only (such as the envelope bands) cannot trigger a delta EU data collection.

Workaround: Do not use server calculated only features as Operating State triggers.

Reported Version: 3.2    Resolved Version: 3.5    Added: 06/1/2018
680791

Return
Cannot export data from EMSA Spectrum chart


Workaround: N/A

Reported Version: 3.3    Resolved Version: 3.4 -    Added: 1/4/2019

Document last updated on 06/1/2018

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).