This document contains the InsightCM 3.4 known issues that were discovered before and since the release of InsightCM 3.4. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.
InsightCM does not warn user that calculated MCSA features cannot be used for gating and delta EU
Using calculated features from an MCSA asset for gating conditions or delta EU triggers will cause an invalid configuration. InsightCM currently does not notify the user of this when creating the asset configuration.
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.
Order Waveform and Spectrum viewers don't display data if there are only two tachometer pulses
When doing slow roll compensation in order waveform or order spectrum viewers, an error is returned if there is only one revolution in the slow roll data.
OPC Historian does not start after upgrade or fresh install
If you have not selected an OPC security policy besides "None", the OPC Historian will be unable to start.
Workaround: Select an OPC security policy on the InsightCM Options page. If you do not want any additional security policies selected, you can then deselect all policies besides "None". The OPC Historian should start after restarting the server.