An additional little tip:
If you look over the shipping examples for AI, you'll see that after calling DAQmx Timing to "request" a sample rate, many (most? all? Dunno for sure, didn't do the homework to check them all) will follow up by querying a DAQmx Timing property node for the sample rate. The query will give you the real true actual sample clock rate (provided you're using the default internal clock to derive it). The vast majority of AI devices only support specific discrete rates based on dividing down a master clock by some integer.
With some devices, such as your own for example, the # of supported integer divisors is pretty limited, so there are pretty sizeable gaps between the available frequencies. Others put fewer restrictions on the integer divisors allowed, other than requiring a certain minimum that corresponds to the max sample rate the rest of the circuitry is rated to handle. With those devices the frequency gaps are considerably smaller, but there still *are* discrete steps between allowed frequencies.
So it can be a good general practice to do like the examples show, and make the habit of querying for the actual sample clock rate right after attempting to set it.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
