NI-Sync 16.x Known Issues

Aperçu

This document contains the NI-Sync known issues that were discovered before and since the release of the NI-Sync 16.0. 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-Sync 16.x sorted by Date.

173555 If a large time adjustment occurs, any PPS or clock being generated will not be aligned with the new time of the board.
173559 You cannot specify a delay for the global software trigger.
242012 If Set Time is called, the time will be successfully set as directed no matter what the current time reference has been set to.
327791 NI-Sync may use cached MAX configuration data.
363033 The time reference offset value is no longer updated when the 1588 node switches to master.
366243 The Mobile Mode property may be inconsistent on an NI PXI-6682 after restart.
399570 If you enable the network adapter of a NI PXI-668x module on a real-time system and do not connect it over Ethernet, the IEEE 1588-2008 feature of the module will be in the master state.
401274 The NI PXI-6682(H) produces a static offset on 10 Mbps Ethernet connections when synchronizing to IEEE 1588-2008.
41819 4E3AJQRX The PXI-6682 and PXI-6683 may revert to using the TCXO (because Clk10 is no longer available) without notifying the user
439127 The NI PXI-6683(H) only verifies the first 6 characters of the calibration password, even if the password is longer than 6 characters.
439129 Modifying the calibration password updates the calibration timestamp.
513221 NI-Sync real-time support may fail to install if DAQmx (Full) has previously been installed without its real-time component.
539048 A hang can occur when niSync Create Clock.vi and niSync Clear Clock.vi are called in parallel.
599884 Software triggers sent with niSync Send Software Trigger may not be sent or may be sent non-deterministically if they are requested at a frequency higher than that of the front or rear synchronization clock sources.
407209 IEEE 1588 synchronization does not work between PXI-668x modules in the same real-time PXI system.



ID Known Issue
173555
 
 Return
If a large time adjustment occurs, any PPS or clock being generated will not be aligned with the new time of the board.
           
     Workaround: Monitor for large time adjustments (snaps) and restart clocks each time such an adjustment occurs. You also can use future time events instead of clocks.
     
                                 
Reported Version: 3.0 Resolved Version: N/A Added: 08/03/2015
 
173559
 
 Return
You cannot specify a delay for the global software trigger.
     The global software trigger fires on the next riding edge of the clock even if you specify a delay.
     
     Workaround: N/A
     
                                 
Reported Version: 3.1 Resolved Version: N/A Added: 08/04/2014
 
242012
 
 Return
If Set Time is called, the time will be successfully set as directed no matter what the current time reference has been set to.
     Some time references, such as GPS and IRIG should not allow setting the time.
     
     Workaround: N/A
     
                                 
Reported Version: 3.3 Resolved Version: N/A Added: 08/04/2014
 
327791
 
 Return
NI-Sync may use cached MAX configuration data.
     If you place an NI PXI-6682 module in a slot which previously housed a different NI PXI-6682, NI-Sync will use the the MAX configuration data from the previous module.
     
     Workaround: Set the NI PXI-6682 to recalculate the position on reboot.
     
                                 
Reported Version: 3.3 Resolved Version: N/A Added: 08/03/2015
 
363033
 
 Return
The time reference offset value is no longer updated when the 1588 node switches to master.
           
     Workaround: Do not query the property when the 1588 node is the master and primary time reference.
     
                                 
Reported Version: 3.4 Resolved Version: N/A Added: 08/03/2015
 
366243
 
 Return
The Mobile Mode property may be inconsistent on an NI PXI-6682 after restart.
     After a reboot, test panels for the board may falsely report that the board is in stationary mode.
     
     Workaround: N/A
     
                                 
Reported Version: 3.4 Resolved Version: N/A Added: 08/03/2015
 
399570
 
 Return
If you enable the network adapter of a NI PXI-668x module on a real-time system and do not connect it over Ethernet, the IEEE 1588-2008 feature of the module will be in the master state.
           
     Workaround: N/A
     
                                 
Reported Version: 3.4 Resolved Version: N/A Added: 08/03/2015
 
401274
 
 Return
The NI PXI-6682(H) produces a static offset on 10 Mbps Ethernet connections when synchronizing to IEEE 1588-2008.
           
     Workaround: N/A
     
                                 
Reported Version: 3.4 Resolved Version: N/A Added: 08/03/2015
 
41819
4E3AJQRX
 
 Return
The PXI-6682 and PXI-6683 may revert to using the TCXO (because Clk10 is no longer available) without notifying the user
     The PXI-6682 and PXI-6683 have a protection mechanism so that if they are running off Clk10 and Clk10 disappears, the card will revert to using the TCXO, and will not hang. However, because there is no notification, users who have configured their board to run off Clk10 might unknowingly have a board running off its own TCXO.
     
     Workaround: N/A
     
                                 
Reported Version: 3.0 Resolved Version: N/A Added: 08/03/2015
 
439127
 
 Return
The NI PXI-6683(H) only verifies the first 6 characters of the calibration password, even if the password is longer than 6 characters.
           
     Workaround: N/A
     
                                 
Reported Version: 3.4.1 Resolved Version: N/A Added: 08/03/2015
 
439129
 
 Return
Modifying the calibration password updates the calibration timestamp.
           
     Workaround: N/A
     
                                 
Reported Version: 3.4.1 Resolved Version: N/A Added: 08/03/2015
 
513221
 
 Return
NI-Sync real-time support may fail to install if DAQmx (Full) has previously been installed without its real-time component
           
     Workaround: Reinstall DAQmx (Full) and ensure that real-time support has installed. Once the real-time support for DAQmx has been installed, run the NI-Sync installer to install NI-Sync's real-time support.
     
                                 
Reported Version: 14.5 Resolved Version: N/A Added: 08/03/2015
 
539048
 
 Return
A hang can occur when niSync Create Clock.vi and niSync Clear Clock.vi are called in parallel.  

     Workaround: Call niSync Create Clock.vi and niSync Clear Clock.vi in series.     
                                 
Reported Version: 3.4 Resolved Version: N/A Added: 08/20/2015
 
599884
 
 Return
Software triggers sent with niSync Send Software Trigger may not be sent or may be sent non-deterministically if they are requested at a frequency higher than that of the front or rear synchronization clock sources.  

     Workaround: Designate higher frequency synchronization clock sources with the niSync Property Node or decrease the rate at which you are requesting software triggers.     
                                 
Reported Version: 16.0 Resolved Version: N/A Added: 08/26/2016
 
407209
 
 Return
IEEE 1588 synchronization does not work between PXI-668x modules in the same real-time PXI system. 
    
IEEE 1588 synchronization does not work between two or more PXI-668x modules that are in one of the following setups:
  • In a single PXI chassis with a real-time controller
  • Spread across multiple PXI chassis that are connected via MXI to a PXI chassis with a real-time controller
                                     
Reported Version: 3.4 Resolved Version: N/A Added: 09/19/2016
 

Document last updated on 9/19/2016

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).