Home Support Documentation Bugs

NI-TimeSync 17.5 Known Issues

Updated Mar 10, 2020

Overview

This document contains the NI-TimeSync known issues that were discovered before and since the release of the NI-TimeSync 17.5. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.

Known Issues by Date

The following items are known issues in NI-TimeSync 17.5 sorted by Date.

246727—Changing the priority in NI MAX or the Web-based Configuration & Monitoring Utility may leave ni-rt.ini in an inconsistent state.
477434—The NI-TimeSync Software-Based 1588 plug-in fails to synchronize properly when used with a secondary network adapter on PharLap ETS and VxWorks targets.
493251—Running an ARM-based Linux Real-Time target as a 1588 master may degrade synchronization
652137—Disabling/re-enabling primary ethernet ports in NI-MAX or in the commnad line will cause synchronization issues.
652959 & 675763—Physically disconnecting and reconnecting an ethernet cable from a device participating in a IEEE 802.1AS protocol can cause synchronization issues.



IDKnown 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

Reported Version: 1.1  Resolved Version: N/A  Added: 08/03/2015
477434

Return		The NI-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 NI-TimeSync Software-Based 1588 plug-in.

Reported Version: 14.0  Resolved Version: N/A  Added: 08/03/2015
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.

Reported Version: 14.0  Resolved Version: N/A  Added: 08/03/2015
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

Reported Version: 17.0  Resolved Version: N/A  Added: 07/07/2017
652959 & 675763

Return

Physically disconnecting and reconnecting an Ethernet cable from a cRIO-903x (Sync), cRIO-904x or an IC-317x participating in an IEEE 802.1AS protocol can cause synchronization issues. Devices might not be able to synchronize to each other over an IEEE 802.1AS network. A full power cycle of a device eliminates these issues.

Workaround: It is highly recommended to always power cycle controllers anytime physically reconfiguring Ethernet cabling.

Reported Version: 17.0  Resolved Version: 18.0  Added: 05/16/2018

Document last updated on 05/16/2018

Back to top

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).