The following items are known issues in InsightCM 3.1 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| InsightCM Monitoring Devices | ||||||
| InsightCM SDK | ||||||
| 646923 Return |
Multiple VIs are missing when opening a project for the first time with the InsightCM 3.1 SDK When migrating an application to the InsightCM 3.1 SDK from the 3.0 SDK, the several VIs are missing. This behavior is due to the refactoring of several VIs during the process of transitioning from the 3.0 to the 3.1 SDK. Workaround: Manually relink VI per AE KB 7NICKSPU: Multiple VIs are missing when opening a project for the first time with the InsightCM 3.1 SDK.
|
|||||
| InsightCM Web Application | ||||||
| 655502 Return |
Equipment node with only numbers in name can cause integrated features to error DataStorage service Equipment nodes named 11 and 12 caused the DataStorage service to error with below error. The CMS devices were collecting data files but the files are not ingested by DataStorage. The device dashboard shows updated feature values and increasing file count but no new data is added to the database. The Audit Logger will display the follow error message in the log: "Unhandled exception in message callback: System.ArgumentException: Input array cannot be empty. Parameter name: inputData..." Workaround: Rename Equipment node to include non-numeric character, eg '11' to 'CT-11'.
|
|||||
| 672619 Return |
MCSA PT and CT nodes cannot be added to Voltage Bus and Motor (MCSA) nodes on servers after 3.0 migration After upgrading from InsightCM 3.0 to 3.1, 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"
|
|||||
| 665234 Return |
Trend Baseline Configurations not migrated during 3.0 migration After upgrading from InsightCM 3.0 to 3.1, trend baseline are not migrated and cause InsightCM web application errors and audit log errors. Workaround: Use the Data Event dialog to delete any collected Trend Baseline and reset or upgrade to InsightCM 3.2.
|
|||||
Document last updated on 12/01/2017