The following items are known issues in InsightCM 3.2 sorted by Category.
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"
| |||||
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"
| |||||
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
| |||||
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.
| |||||
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
|
Document last updated on 1/22/2018