|NI-SCOPE (English | Japanese)|
The following forms of synchronization are available, listed in order by synchronization accuracy.
|Note Synchronization accuracy specifications depend on the system and device(s) being used. Refer to your device Specifications for more information.|
|Note Sharing a clock (reference clock or sample clock) among devices can achieve time locking. In some cases, time locking among clocks can achieve greater determinism; however, it does not affect any overall delays in signals sent.|
You can send a synchronization software command from a host computer to a device. Synchronizing events by software is not deterministic on operating systems such as Windows or Mac.
|Note You can use a time-based protocol, such as GPS, 1588, or IRIG-B, to coordinate events at large distances, typically greater than 10 m.|
You can send an electrical signal from one device (master) to another (slave) to signal an event using the trigger routing available from a PXI chassis or RTSI cable. The devices dictate the level of determinism. The signal path length mainly determines the synchronization accuracy.
Synchronization Explained (trigger routing and sharing clocks and triggers)
|Note In this case, external refers to triggering external to your PXI chassis or external to the device for other device form factors, for example USB and PCIe.|
You can send triggers to each device through PFI, channel, or other I/O lines on the device front panel. When trigger lines have matched signal path lengths, measured synchronization results may improve.
You can use NI-TClk to programmatically phase align clocks and coordinate triggers between devices and multiple chassis. NI-TClk is an advanced synchronization method, and is not supported by all devices.