NI-DAQmx .NET Framework 4.0 API Reference

Content Type
Programming Language
Current manual
Table of Contents
Product DocumentationNI-DAQmx .NET Framework 4.0 API ReferenceTiming.ConfigureImplicit Method (SampleQuantityMode, Int32)Current page
Table of Contents

Timing.ConfigureImplicit Method (SampleQuantityMode, Int32)

Timing.ConfigureImplicit Method (SampleQuantityMode, Int32)

TimingConfigureImplicit Method (SampleQuantityMode, Int32)

Sets only the duration of the task and the number of samples to acquire or generate without specifying timing.

Namespace:  NationalInstruments.DAQmx
Assembly:  NationalInstruments.DAQmx (in NationalInstruments.DAQmx.dll) Version: 20.7.40.49302

Syntax

public void ConfigureImplicit(
	SampleQuantityMode sampleMode,
	int samplesPerChannel
)
Public Sub ConfigureImplicit ( 
	sampleMode As SampleQuantityMode,
	samplesPerChannel As Integer
)

Parameters

sampleMode
Type: NationalInstruments.DAQmxSampleQuantityMode
The duration of the task. A task is either finite and stops once the specified number of samples have been acquired or generated, or it is continuous and continues to acquire or generate samples until the task is explicitly stopped.
samplesPerChannel
Type: SystemInt32
The number of samples to acquire or generate for each channel in the task if sampleMode is FiniteSamples. For finite counter output tasks, samplesPerChannel is the number of pulses to generate. If sample mode is ContinuousSamples, NI-DAQmx uses this value to determine the buffer size.

Exceptions

ExceptionCondition
DaqExceptionThe NI-DAQmx driver returned an error.

Remarks

Typically, you use implicit timing when sample timing is not required for the task, such as for a task that uses counters for buffered frequency measurement, buffered period measurement, or pulse train generation. Use this method if the task requires a finite number of samples.

The NI-DAQmx driver does not determine if the requested settings are possible until the task is verified. This method does not throw an exception for parameter values that are not compatible with your hardware or other settings in your task. To determine if all of the settings for a Task are valid, you must verify the task by starting the task, either with Start or by reading from or writing to the task, or by calling Control(TaskAction) with Verify.

You cannot apply this method to a subset of devices in the task, and you must apply this method to the task as a whole. You must call this method on the instance of Timing returned from the Timing property on the Task class. Accessing this method on instances of Timing returned from the ItemString property throws an exception.

See Also

Was this information helpful?