This document contains the NI-TimeSync known issues that were discovered before and since the release of the NI-TimeSync 18.1. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.
Disabling/re-enabling an Ethernet port on a cRIO-903x (Sync) or an IC-317x in NI-MAX or in the command line will cause synchronization issues unless the system is rebooted. Issues might appear as undefined static time offsets, asynchronous FPGA times or the Time Source I/O reporting “None”. Never disable eth0 on the cRIO-9035x (Sync) or eth1 on IC-317x, this will cause all synchronization to halt.
Installing a custom installation on a Linux Real-Time target which includes System Configuration 18.5.0 and Timesync 18.1.0 or Timesync 18.0.0 will cause the target to become unreachable by NI MAX and the System Configuration API. If SSH, WIF, WebDAV, or FTP access were enabled prior to the target becoming unreachable, they will still be usable.
Workaround: This issue is resolved in Timesync 18.1.1. If a target has entered an unreachable state, it can be recovered by restarting the target in safe mode and reformatting it from NI MAX.