NI-Sync 15.0 Known Issues

Publish Date: Sep 28, 2015 | 0 Ratings | 0.00 out of 5 | Print

Overview

This document contains the NI-Sync known issues that were discovered before and since the release of the NI-Sync 15.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 15.0 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.
   532983       PXI-668X and PCI-1588 cards return errors or show up as disconnected on Windows 10.



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          
 
  532983
 
 Return
 

PXI-668X and PCI-1588 cards return errors or show up as disconnected on Windows 10.
     The PXI-6682(H), PXI-6683(H), and PCI-1588 may appear as disconnected in NI MAX or return errors on Windows 10, such as:

    • Error -50202 occurred at Device Configuration when selecting a device in NI MAX or opening a Test Panel.
    • The self test failed. Status Code: -88705 when running a self test.
    • Error -1073807360 occurred at Property Node when accessing the 1588 tab of a Test Panel

 

     Workaround: N/A    
                                  

            Reported Version: 15.0                            Resolved Version: 15.0.1                            Added: 08/20/2015          
 

Document last updated on 9/28/2015

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit