The following items are known issues in InsightCM 3.3 sorted by Category.
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
| |||||
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
| |||||
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/
| |||||
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
| |||||
703685 Return | Adding Modbus Data Source channels to device causes OPC Historian update issues Workaround: N/A
| |||||
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.
| |||||
680791 Return | Cannot export data from EMSA Spectrum chart Workaround: N/A
|
Document last updated on 06/1/2018