Sample Timing Type Property

Short Name: SampTimingType

Property of DAQmx Timing

Specifies the type of sample timing to use for the task.

Select Sample Clock when a hardware signal (usually a clock) must acquire or produce samples. To perform buffered edge counting, for example, select Sample Clock and use SampClk.Src to specify the source of the Sample Clock.

Select Handshake when you want to use bidirectional hardware signals to time the exchange of digital data between two devices.

Select On Demand when you want to acquire data only when DAQmx Read executes or to generate data only when DAQmx Write executes.

Select Implicit when you perform a buffered period or frequency counter measurement or when you generate a finite pulse train.

Sample Clock (10388)	Use a sample clock to determine how often to acquire or generate samples.
Handshake (10389)	Determine sample timing by using digital handshaking between the device and a peripheral device.
On Demand (10390)	Acquire or generate a sample on each read or write operation.
Implicit (10451)	Configure only the duration of the task.
Change Detection (12504)	Acquire samples when a change occurs in the state of one or more digital input lines. The lines must be contained within a digital input channel.
Burst Handshake (12548)	Determine sample timing using burst handshaking between the device and a peripheral device.
Pipelined Sample Clock (14668)	Device acquires or generates samples on each sample clock edge, but does not respond to certain triggers until a few sample clock edges later. Pipelining allows higher data transfer rates at the cost of increased trigger response latency. Refer to the device documentation for information about which triggers pipelining affects. This timing type allows handshaking with some devices using the Pause trigger, the Ready for Transfer event, or the Data Active event. Refer to the device documentation for more information.

Remarks

The following table lists the characteristics of this property.

Permissions	read/write
Resettable	yes
Settable while task is running	device-specific
Available in Run-Time Engine	yes