NI InsightCM 3.2 Known Issues

Overview

This document contains the InsightCM 3.2 known issues that were discovered before and since the release of InsightCM 3.2. 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.2 sorted by Category.

InsightCM Monitoring Devices
682835 CMS-9036 (No IEPE) Device does not include Burst Mode by default after upgrading from NI InsightCM 3.0
InsightCM SDK
InsightCM Web Application
672619 MCSA PT and CT nodes cannot be added to Voltage Bus and Motor (MCSA) nodes on servers after upgrading from NI InsightCM 3.0
682841 Device Dashboard page does not display alarms on integrated features
683334 Updating Device Applications results in "In Queue" status on the Device page and Device Applications fail to update
683386 Readme does not reference OSIsoft PI Asset Framework (AF) Client requirement for NI InsightCM Enterprise Gateway Toolkit



ID Known Issue
InsightCM Monitoring Devices
682835

Return
CMS-9036 (No IEPE) Device does not include Burst Mode by default after upgrading from NI InsightCM 3.0
After upgrading from InsightCM 3.0 to 3.2, the CMS-9036 (No IEPE) Device does not include Burst Mode configuration by default.

Workaround: Reimport the device definitions using the InsightCMConsole and force refresh the web application by clearing your web browser's cache.
"C:\Program Files\National Instruments\InsightCM Server 3.0\InsightCMConsole.exe" importdefinition -t device -f "C:\Program Files\National Instruments\InsightCM Server 3.0\Definitions\DeviceTypes\NI CMS-9036-NoIEPE.json"

Reported Version: 3.2    Resolved Version: N/A    Added: 1/17/2018
InsightCM SDK
InsightCM Web Application
672619

Return
MCSA PT and CT nodes cannot be added to Voltage Bus and Motor (MCSA) nodes on servers after upgrading from NI InsightCM 3.0
After upgrading from InsightCM 3.0 to 3.2, user will not be able to select any CT or PT assets to map to Voltage Bus or Motor (MCSA).

Workaround: Reimport the Motor (MCSA) and Voltage Bus asset node definitions using the InsightCMConsole.
"C:\Program Files\National Instruments\InsightCM Server 3.0\InsightCMConsole.exe" importdefinition -t asset -f "C:\Program Files\National Instruments\InsightCM Server 3.0\Definitions\AssetNodeTypes\Motor (MCSA).json"
"C:\Program Files\National Instruments\InsightCM Server 3.0\InsightCMConsole.exe" importdefinition -t asset -f "C:\Program Files\National Instruments\InsightCM Server 3.0\Definitions\AssetNodeTypes\Voltage Bus.json"

Reported Version: 3.1    Resolved Version: N/A    Added: 10/17/2017
682841

Return
Device Dashboard page does not display Trend Alarms on Integrated Sensor Features
The Device Dashboard do not show alarms on integrated sensor features in the Trend Alarms area of the Device Dashboard. The integrated sensors alarm is displayed on Alarm tab of the main Dashboard page.

Workaround: N/A

Reported Version: 3.2    Resolved Version: N/A    Added: 1/17/2018
683334

Return
Updating Device Applications results in "In Queue" status on the Device page and Device Applications fail to update
After upgrading from InsightCM 3.0 to 3.2, the NI System Management Service (SMS) can hang and cause device application updates to fail. Symptons include the nisms.exe process using large amounts of CPU time, viewable in Windows Resource Monitor, and the device status listed as "In Queue".

Workaround: You can reset the NI SMS and deploy applications after the reset. In Windows Services, stop NI Deployer for SMS, NI System Management Service and then postgresql-x64-9.2 in that order. Once stopped, start postgresql-x64-9.2, NI SMS and then NI Deployer for SMS. Refresh the InsightCM web application and the "In Queue" status will be cleared. It is recommended to deploy applications to 5 devices at a time, and allowing them to reboot and come back online before updating more devices.

Reported Version: 3.2    Resolved Version: N/A    Added: 1/19/2018
683386

Return
Readme does not reference OSIsoft PI Asset Framework (AF) Client requirement for NI InsightCM Enterprise Gateway Toolkit
If you use NI InsightCM Server Enterprise Gateway Toolkit add-on with OSIsoft PI System software, you must install the OSIsoft PI Asset Framework (AF) Client before installing or upgrading to NI InsightCM 3.2.

Workaround: Install the OSIsoft PI Asset Framework (AF) Client on the NI InsightCM Server. Contact OSIsoft technical support for more information and see OSISoft PI AF SDK

Reported Version: 3.2    Resolved Version: N/A    Added: 1/22/2018

Document last updated on 1/22/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).