Resolving LabVIEW 2013 OPC UA Server Detection Failures

Symptom: OPC UA Server Not Detected from LabVIEW

A LabVIEW 2013 application fails to detect an OPC UA server running on an Arburg injection moulding machine configured with TCP/IP. Third-party clients confirm the server side is healthy: UAExpert connects successfully to the same server, yet NI OPC detects neither the Arburg OPC UA server nor the UAExpert endpoint. This pattern — external client connects, NI stack sees nothing — points to the NI-side software, not the machine's server configuration or the network path.

Root Cause: Pre-2013 Driver Defect

The confirmed cause is a defect in the older LabVIEW OPC UA driver — specifically the 2011 version in use on the affected system. The issue is fixed in the DSC Module 2013. Systems exhibiting this exact symptom should be audited for which driver/DSC version is installed; a 2011-era driver paired with LabVIEW 2013 reproduces the detection failure.

Resolution: Upgrade to DSC Module 2013

1. Confirm the installed OPC UA driver/DSC Module version on the development machine. A 2011 version is the defective one described here.
2. Install or upgrade to the DSC Module 2013, which contains the fix.
3. Reconnect from LabVIEW 2013 to the Arburg OPC UA server over TCP/IP and verify the server is now detected.

Verification and Supported API Path

Keep UAExpert in the loop as an independent reference client: because it already connects to the Arburg server, any remaining failure after the DSC 2013 upgrade isolates to the LabVIEW application rather than the server. For programmatic access, LabVIEW supports OPC UA through the NI LabVIEW OPC UA APIs, documented at https://decibel.ni.com/content/docs/DOC-16930. The evidence does not specify whether the failing connection used these APIs or the NI OPC server layer, so if detection still fails after the upgrade, test both paths separately.

FAQ