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.
The following items are known issues in LabVIEW 2014 DSC Module sorted by Category.
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.
| |||||
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.
| |||||
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
|
The following items are known issues in LabVIEW 2014 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.
| |||||
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.
| |||||
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.
| |||||
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
|
Document last updated on 11/11/2014