NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
This document contains the LabVIEW DSC Module known issues that were discovered before and since the release of the LabVIEW 2013 DSC Module. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The LabVIEW 2013 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The Known Issues Document is divided into two separate tables. The section linked below displays the issues by category.
The following items are known issues in LabVIEW 2013 SP1 DSC Module sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Citadel | ||||||
| 405808 Return | Partial data pages appear to be missing from destination database after a trace archive Partial data pages are lost during an archive operation when the destination database is index rebuilding at the time of the archive. Workaround: Always execute safe shutdowns of Citadel databases as improper shutdowns prompt index rebuilding. In the event of an improper shutdown, allow time for the database finish index rebuilding before performing any archive operation.
| |||||
| I/O Servers | ||||||
| 280037 Return | The first read of an EPICS Client PV returns 'General communication failure' The first read of a PV triggers the creation of the PV item through LogosXT. Due to this, first read will fail. EPICS Servers display similar behavior. Workaround: Use Programmatic Shared Variable API to open the Shared Variable bound to the EPICS Client PV, and wait a sufficient amount of time (>0.1 seconds). You can then read the value successfully through Programmatic Shared Variable API.
| |||||
| 400570 Return | Modbus function code 16 sends "Data Bytes to Follow" byte incorrectly The advanced Modbus Master setting "Use function code 16 for single write" allows users to write to a single register on devices that require function code 16 commands. This setting sends one of the Modbus bytes incorrectly resulting in Error -1967353902. Workaround: Use the Modbus library for devices requiring function code 16 commands.
| |||||
| 430766 Return | Error -1967353902 when using serial ports other than COM1 for Modbus On a Windows machine, attempting Modbus communication on a COM port added after boot will return error -1967353902. On an RT target, attempting Modbus communication on any COM port other than COM1 will return error -1967353902. Workaround: On Windows, restart the shared variable engine service after COM ports have been added. On RT, add the shared variable engine and RIO I/O Scan to the list of startup DLLs for the target.
| |||||
| Installation and Activation | ||||||
| 404513 Return | Installing the DSC Module reverts localized Real-Time Module content to English Installing the DSC Module on a LabVIEW Real-Time Module system with Japanese or Simplified Chinese language support reverts dialog boxes and help topics shared between the modules to English because the DSC Module is not localized. Workaround: Install the DSC Module before installing the Real-Time Module to avoid overwriting localized content.
| |||||
| Performance | ||||||
| 314382 Return | Modbus master write requests can be lost when using fast update rates If a Modbus master submits write requests at very fast update rates (for example: 10ms) packets will be lost. Workaround: Update values at a slower rate to reduce the amount of lost packets.
| |||||
The following items are known issues in LabVIEW 2013 SP1 DSC Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 280037 Return | The first read of an EPICS Client PV returns 'General communication failure' The first read of a PV triggers the creation of the PV item through LogosXT. Due to this, first read will fail. EPICS Servers display similar behavior. Workaround: Use Programmatic Shared Variable API to open the Shared Variable bound to the EPICS Client PV, and wait a sufficient amount of time (>0.1 seconds). You can then read the value successfully through Programmatic Shared Variable API.
| |||||
| 314382 Return | Modbus master write requests can be lost when using fast update rates If a Modbus master submits write requests at very fast update rates (for example: 10ms) packets will be lost. Workaround: Update values at a slower rate to reduce the amount of lost packets.
| |||||
| 400570 Return | Modbus function code 16 sends "Data Bytes to Follow" byte incorrectly The advanced Modbus Master setting "Use function code 16 for single write" allows users to write to a single register on devices that require function code 16 commands. This setting sends one of the Modbus bytes incorrectly resulting in Error -1967353902. Workaround: Use the Modbus library for devices requiring function code 16 commands.
| |||||
| 404513 Return | Installing the DSC Module reverts localized Real-Time Module content to English Installing the DSC Module on a LabVIEW Real-Time Module system with Japanese or Simplified Chinese language support reverts dialog boxes and help topics shared between the modules to English because the DSC Module is not localized. Workaround: Install the DSC Module before installing the Real-Time Module to avoid overwriting localized content.
| |||||
| 405808 Return | Partial data pages appear to be missing from destination database after a trace archive Partial data pages are lost during an archive operation when the destination database is index rebuilding at the time of the archive. Workaround: Always execute safe shutdowns of Citadel databases as improper shutdowns prompt index rebuilding. In the event of an improper shutdown, allow time for the database finish index rebuilding before performing any archive operation.
| |||||
| 430766 Return | Error -1967353902 when using serial ports other than COM1 for Modbus On a Windows machine, attempting Modbus communication on a COM port added after boot will return error -1967353902. On an RT target, attempting Modbus communication on any COM port other than COM1 will return error -1967353902. Workaround: On Windows, restart the shared variable engine service after COM ports have been added. On RT, add the shared variable engine and RIO I/O Scan to the list of startup DLLs for the target.
|
Document last updated on 1/31/2014