NI-Sync 21.3 Known Issues

Überblick

This document contains the NI-Sync known issues that were discovered before and since the release of NI-Sync 21.3. 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

1249028 173559

Divided Synchronization Clock for Trigger Route Set to Falling Edge But Aligns to Rising Edge

When niSync Connect Trigger Terminals.vi is used with the input update edge set to falling, and synchronization clock set to Clock Divisor 1 or Clock Divisor 2, the output trigger signal transitions on the rising edge of the synchronization clock instead of on the expected falling edge.



Workaround:

There is currently no known workaround for this issue.

Reported Version:

N/A

Resolved Version:

N/A

Added:

Oct 26, 2021

1509459 399570

LabVIEW Slows Down When NI-Sync Terminal Control is Created on Linux RT System

When a user creates an NI-Sync terminal control or constant in a VI in the context of a Linux RT target, LabVIEW becomes slow in responding to edit actions, including dragging and placing nodes on the block diagram.

Workaround:

To prevent the sluggishness in LabVIEW, do the following:
  1. Right-click the control or constant and select I/O Name Filtering from the shortcut menu.
  2. In the Filter Names dialog box, select Allow Undefined Names.

Reported Version:

NI-Sync: 20.1

Resolved Version:

N/A

Added:

Jul 26, 2021

1499857 399570

1588 Time Reference Does Not Start on PXI-6683 on Windows

When the niSync Set Time Reference.vi (1588 Ordinary Clock) is used on Windows, the time reference does not start. However, the time reference does start on Linux.

Workaround:

In a Windows environment, you must invoke the niSync Start 1588 VI for the device to participate in 1588. Alternately, you can start and stop 1588 from the test panel in Measurement & Automation Explorer (MAX).

Reported Version:

NI-Sync: 20.1

Resolved Version:

N/A

Added:

Jul 26, 2021

1507908 399570

PXI-6683H Stops Working in MAX When Ethernet Adapter Mode is Set to EtherCAT on Linux RT

In an NI Linux Real-Time system, when the Ethernet adapter mode for a PXI-6683H is set to EtherCAT, upon saving the settings the device appears grayed out in MAX and it is not possible to change any settings on the PXI-6683H any more.

Workaround:

PXI-6683H does not support EtherCAT on its Ethernet port.

To restore the PXI-6683H to a functional state, reformat the PXI controller and reinstall NI Linux Real-Time.

Reported Version:

NI-Sync: 21.0

Resolved Version:

N/A

Added:

Jul 26, 2021

1518457 399570

LVDS Terminal Misses First Edge After Multiple Routes are Destroyed and Created

On a PXIe-6674T module, if a route to a previous destination has been destroyed and a new route created, the Low Voltage Differential Signaling (LVDS) input terminal does not transmit the first edge to its destination.

Workaround:

Create the desired route and then destroy it before finally creating the desired route again. The first edge should now be passed successfully.

Reported Version:

NI-Sync: 21.0

Resolved Version:

N/A

Added:

Jul 26, 2021

1243494 399570

Error -1074118651 Occurs at niSync Read Trigger Time Stamp (Multiple).vi on Linux

When running NI-Sync on Linux, if time stamp triggers are enabled or clocks are created in a loop that also clears and disables those same timestamp triggers and clocks, an internal software error (-1074118651) may occur at niSync Read Trigger Time Stamp (Multiple).vi.

Workaround:

To prevent this error, add a small delay to the loop after clearing the clocks and disabling the timestamp triggers.

Reported Version:

NI-Sync: 21.0

Resolved Version:

N/A

Added:

Jul 26, 2021

1403449 399570

Unexpected Timestamps Returned When a Trigger Timestamp is Read Before Any Edges

Reading a trigger timestamp after it has been enabled but before any edges have occurred on the terminal sometimes returns two timestamps recording the moment that the trigger timestamp was enabled. After actual edges occur on the terminal, the unexpected timestamps are cleared.

Workaround:

After enabling the timestamp trigger but before reading any timestamps on a terminal, clear the buffer by reading all available timestamps on that terminal.

Reported Version:

NI-Sync: 21.0

Resolved Version:

N/A

Added:

Jul 26, 2021

1484735 399570

Switching Time References is Slower on Linux than on Windows

On Linux OS, switching time references may take more than 10 s, while it typically takes only 100 ms on Windows.

Workaround:

There is no known workaround at this time.

Reported Version:

NI-Sync: 21.0

Resolved Version:

N/A

Added:

Jul 26, 2021

1543704 399570

Last_Sync_ID Does Not Reset to Zero when Changing Time References

When changing the active time reference to GPS from any other time reference, the Last_Sync_ID continues to increment with each pulse from wherever it was last. In Windows or Phar Lap it resets the count to zero under the same circumstances.

Workaround:

There is no known workaround at this time.

Reported Version:

NI-Sync: 21.3

Resolved Version:

N/A

Added:

Jul 26, 2021

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