Error -1074118552 A Failure Occured While Communicating With the Remote Device

Updated Sep 2, 2022

Reported In

Hardware

  • CompactRIO Controller
  • sbRIO-9606

Driver

  • NI CompactRIO
  • NI-Sync

Issue Details

  • I have connected my Time Sensitive Networking (TSN) enabled device to a network that includes my host computer. I can see my device in Measurement & Automation Explorer (MAX) and it appears in the drop-down menu as an NI-Sync device in LabVIEW so I can select it, but when I try to open an NI-Sync session and use my device I receive an error which indicates it is not accessible. 
  • I am using the Monitor and Configure Time References.vi to verify the PTP synchronization with my sbRIO-9606. I am using LabVIEW 2021, the NI Compact RIO driver 21.0, and NI-Sync 21.0. However, when running the example, I get the following error:
 
Error -1074118552 occurred at niSync Get Time References.vi

Possible reason (s):

Driver Status: (Hex 0xBFFA4068) A failure occured while communicating with the remote device. Ensure the remote device is accessible. 

Solution

Network Issues
To resolve this issue, use the IP address of the device instead of the host name. The device selection should look similar to the image below:

This issue can also be resolved by manually mapping the device host name to the IP address in the DNS hosts file. 

Software compatibility: Host PC 
This error can be caused by incompatibility issues between the software installed on the host PC and the embedded target. Make sure to install the compatible software on the host PC for your embedded device. For instance, if you are using a sbRIO-9606 with LabVIEW 2021, the NI Compact RIO driver 21.0, and NI-Sync 21.0, the error will show up as the last version that supports this target is NI CompactRIO 19.6. 

Firmware
If using cDAQ, check that the firmware version of the cDAQ is higher than 18.1.0
 

Additional Information

This issue can occur in systems without an active DNS server. This includes link-local systems, so directly connecting to a device can induce this issue. This behavior is expected behavior when trying to access a device via hostname when there is no DNS server to associate the hostname with an IP address.