Archived: LabVIEW 2013 DSC Module Known Issues

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.

Aperçu



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.

Document Organization

The Known Issues Document is divided into two separate tables. The section linked below displays the issues by category.

Known Issues by Category

The following items are known issues in LabVIEW 2013 SP1 DSC Module sorted by Category.

Citadel
405808 Partial data pages appear to be missing from destination database after a trace archive
I/O Servers
280037 The first read of an EPICS Client PV returns 'General communication failure'
400570 Modbus function code 16 sends "Data Bytes to Follow" byte incorrectly
430766 Error -1967353902 when using serial ports other than COM1 for Modbus
Installation and Activation
404513 Installing the DSC Module reverts localized Real-Time Module content to English
Performance
314382 Modbus master write requests can be lost when using fast update rates

 

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.

Reported Version: 2012    Resolved Version: 2014    Added: 05/02/2013
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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 03/29/2013
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.

Reported Version: 2013    Resolved Version: N/A    Added: 11/11/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 04/24/2013
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.

Reported Version: 2011    Resolved Version: N/A    Added: 12/07/2012

Known Issues by Date

The following items are known issues in LabVIEW 2013 SP1 DSC Module sorted by Date.

280037 The first read of an EPICS Client PV returns 'General communication failure'
314382 Modbus master write requests can be lost when using fast update rates
400570 Modbus function code 16 sends "Data Bytes to Follow" byte incorrectly
404513 Installing the DSC Module reverts localized Real-Time Module content to English
405808 Partial data pages appear to be missing from destination database after a trace archive
430766 Error -1967353902 when using serial ports other than COM1 for Modbus

 

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.

Reported Version: 2010    Resolved Version: N/A    Added: 02/08/2011
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.

Reported Version: 2011    Resolved Version: N/A    Added: 12/07/2012
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 03/29/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 04/24/2013
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.

Reported Version: 2012    Resolved Version: 2014    Added: 05/02/2013
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.

Reported Version: 2013    Resolved Version: N/A    Added: 11/11/2013

Document last updated on 1/31/2014

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).