LabVIEW 2014 DSC Known Issues

Panoramica

This document contains the LabVIEW DSC Module known issues that were discovered before and since the release of the LabVIEW 2014 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 2014 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Known Issues by Category

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

Functions, VIs, and Express VIs
387275 Array of ByteString data type in OPC UA reports generic error
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
466347 Modbus Ethernet I/O Servers fail communication when slave addresses are mismatched



ID Known Issue
Functions, VIs, and Express VIs
387275

Return
Array of ByteString data type in OPC UA reports generic error
Support for the ByteString Array data type has not been added although the option appears in the data type ring control.

Workaround: Don't use ByteString Array data type until support is added.

Reported Version: 2012    Resolved Version: N/A    Added: 01/18/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
466347

Return
Modbus Ethernet I/O Servers fail communication when slave addresses are mismatched
Modbus I/O servers configured for Modbus Ethernet behave erratically when the slave addresses are mismatched. Communication between a master and a slave with mismatched addresses leads to a failure with error -1967353902: Modbus I/O Server failed to receive response from Modbus I/O Slave device. When changing the address to a matching set, the communication is successful.

Workaround: N/A

Reported Version: 2013 SP1    Resolved Version: N/A    Added: 07/31/2014



Known Issues by Date

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

280037 The first read of an EPICS Client PV returns 'General communication failure'
387275 Array of ByteString data type in OPC UA reports generic error
400570 Modbus function code 16 sends "Data Bytes to Follow" byte incorrectly
466347 Modbus Ethernet I/O Servers fail communication when slave addresses are mismatched



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
387275

Return
Array of ByteString data type in OPC UA reports generic error
Support for the ByteString Array data type has not been added although the option appears in the data type ring control.

Workaround: Don't use ByteString Array data type until support is added.

Reported Version: 2012    Resolved Version: N/A    Added: 01/18/2013
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
466347

Return
Modbus Ethernet I/O Servers fail communication when slave addresses are mismatched
Modbus I/O servers configured for Modbus Ethernet behave erratically when the slave addresses are mismatched. Communication between a master and a slave with mismatched addresses leads to a failure with error -1967353902: Modbus I/O Server failed to receive response from Modbus I/O Slave device. When changing the address to a matching set, the communication is successful.

Workaround: N/A

Reported Version: 2013 SP1    Resolved Version: N/A    Added: 07/31/2014

Document last updated on 11/11/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).