The following items are known issues in Timesync 18.1 sorted by Date.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
246727 Return | Changing the priority in NI MAX or the Web-based Configuration & Monitoring Utility may leave ni-rt.ini in an inconsistent state. Workaround: N/A
| |||||
477434 Return | The Timesync Software-Based 1588 plug-in fails to synchronize properly when used with a secondary network adapter on PharLap ETS and VxWorks targets. Workaround: National Instruments recommends that you only use the primary network adapter when using the Timesync Software-Based 1588 plug-in.
| |||||
493251 Return | Running an ARM-based Linux Real-Time target as a 1588 master may degrade synchronization. Workaround: National Instruments recommends that you only use ARM-based targets running NI Linux Real-Time as 1588 slaves. ARM-based targets running NI Linux Real-Time are slave only by default.
| |||||
652137 Return | 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. Workaround: N/A
| |||||
707309 Return |
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.
|
Document last updated on 06/18/2018