NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
The following items are known issues in NI-Sync 3.x sorted by Date.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
222651 Return | The NI PXI-6682 is incorrectly identified as a VISA device on a 64-bit host computer with more than 4 GB of RAM. Workaround: N/A
| |||||
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.
| |||||
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
| |||||
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
| |||||
246967 Return | Enabling or disabling the PFI 10kOhm Termination on the NI PXI-6674T affects PFI threshold value. Enabling the 10kOhm termination causes the threshold voltage to decrease slightly, while disabling the 10kOhm termination causes the threshold voltage to increase slightly. Workaround: N/A
| |||||
246972 Return | On the NI PXIe-6674T, setting 10kOhm Termination on PF1 causes an error. If the threshold voltage for PFI1 is set close to its maximum value, enabling PFI1 10kOhm termination causes the following calls to hang: Get PFI Threshold Voltage, Set PFI Threshold Voltage, and Enable PFI1 10kOhm termination. Workaround: N/A
| |||||
322232 Return | Setting the User LED State property on an NI PXIe-6674T results in error -1074118653: This operation requires a feature that is not supported. Workaround: N/A
| |||||
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.
| |||||
330043 Return | Reading Future Time Events on NI PXI-668x Modules may cause a crash. Enabling trigger timestamps on a line while the hardware timestamps a trigger on a different line may result in a system crash. Workaround: N/A
| |||||
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.
| |||||
364088 Return | Running niSync Start 1588.vi resets all the 1588 properties to default. When you run the niSync Start 1588 VI, all 1588 properties are reset to default, including Log Sync Interval, Priority 1, and Priority 2. Any settings configured prior to running this VI are erased. Workaround: N/A
| |||||
365208 Return | The NI PXIe-6674(T) self-test fails with error -201427. Due to an intermittent error in initialization of the device, an NI PXIe-6674(T) self-test results in error -201427: The specified device is not supported within the NI-DAQmx API. Workaround: Reboot the system.
| |||||
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
| |||||
367753 Return | Resetting the PXI-6682(H) or PCI-1588 multiple times cause errors Multiple asynchronous resets to the PXI-6682(H) or PCI-1588 cause a variety of errors and may even result in a system hang or crash. Workaround: N/A
| |||||
381561 Return | The network adapter on the NI PXI-6682 initializes with incorrect settings. When an NI PXI-6682 is configured as the secondary NIC, the network adapter will initialize to 10Mbps/Full Duplex mode regardless of the user-defined settings. Workaround: N/A
| |||||
385300 Return | When in polling mode, the NI PXI-6682 and NI PXI-6683 modules fail to acquire an IP address. When these modules are configured to use polling mode, the network adapters on the NI PXI-6682 and NI PXI-6683 modules fail to receive an IP address with the LabVIEW 2011 Real-Time Module. Workaround: N/A
| |||||
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
| |||||
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
| |||||
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
| |||||
438783 Return | The NI PXI-6682 and NI PXI-6683 modules may cause excessive jitter on real-time systems. Workaround: National Instruments recommends that you carefully evaluate the performance of applications sensitive to jitter that use NI PXI-668x modules to verify that jitter requirements are met.
| |||||
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
| |||||
439129 Return | Modifying the calibration password updates the calibration timestamp. Workaround: N/A
| |||||
506257 Return | The NI PXI-6683 Ethernet driver may cause real-time systems to hang or crash. Workaround: Disable the Ethernet adapter on the NI PXI-6683 to prevent the system hang from occurring.
|
Document last updated on 6/26/2015