NI-Sync 20.0 Known Issues

Überblick

This document contains the NI-Sync 20.0 known issues that were discovered before and since the release of NI-Sync 20.0. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details

197566 574978

NI-Sync does not report firmware revision information through System Configuration API on LinuxRT.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 15.2

Resolved Version:

N/A

Added:

May 22, 2017

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

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 3.4

Resolved Version:

N/A

Added:

Aug 3, 2014

453062 633239

Windows targets will crash when the PXI-6682 board time is set to 0 using the Set Time VI (Manual Time).

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 17.0

Resolved Version:

N/A

Added:

May 22, 2017

452928 363033

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:

NI-Sync 3.4

Resolved Version:

N/A

Added:

Aug 3, 2014

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

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:

NI-Sync 16.1

Resolved Version:

N/A

Added:

Aug 26, 2016

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

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 3.4.1

Resolved Version:

N/A

Added:

Aug 3, 2014

453949 41819

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:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 3.0

Resolved Version:

N/A

Added:

Aug 3, 2014

453157 401274

The NI PXI-6682(H) produces a static offset on 10 Mbps Ethernet connections when synchronizing to IEEE 1588-2008.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 3.4

Resolved Version:

N/A

Added:

Aug 3, 2014

452933 366243

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:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 3.4

Resolved Version:

N/A

Added:

Aug 3, 2014

454299 327791

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:

NI-Sync 3.3

Resolved Version:

N/A

Added:

Aug 3, 2014

453135 513221

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:

NI-Sync 14.5

Resolved Version:

N/A

Added:

Feb 26, 2015

454293 539048

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:

NI-Sync 3.4

Resolved Version:

N/A

Added:

Aug 19, 2015

892032 173555

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:

NI-Sync 3.0

Resolved Version:

N/A

Added:

Aug 3, 2014

892038 173559

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:

There is currently no known workaround for this issue.

Reported Version:

NI-Sync 3.1

Resolved Version:

N/A

Added:

Aug 3, 2014

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

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