matlab-call-nidaqmx

Use calldaqlib with a daq object, passing the DAQmx function name as a string followed by its arguments. Omit the taskHandle since the daq object owns it, and use string enum names like "DAQmx_Val_Rising" instead of raw integers.

Configure the trigger type first, then call calldaqlib(dq, "DAQmxSetStartTrigRetriggerable", true). Retriggerable mode requires DAQmx_Val_FiniteSamps in DAQmxCfgSampClkTiming and does not work with continuous sampling.

Use the daq object when its properties and methods cover the capability, such as dq.Rate, addtrigger, or addclock. Use calldaqlib only for driver-level features the daq object does not expose, like retriggerable triggers, signal export, or digital filters.

The start() method reapplies dq.Rate to the driver, clobbering any rate set through DAQmxCfgSampClkTiming. Set dq.Rate first and reserve calldaqlib for parameters the daq object does not track, or use DAQmxStartTask via calldaqlib.

No, DAQmxCreateTask and DAQmxLoadTask cannot work through calldaqlib because it owns task creation internally. Device-level functions without a taskHandle, like DAQmxGetDevIsSimulated or DAQmxConnectTerms, work using an empty daq object with no channels.

Error -200228 means the buffer size passed to the getter is too small. The error message includes the required buffer size in bytes; parse it and retry, using 256 for short names and 1024 for long paths or channel lists.