Just to add another data point.
I saw the same thing here with LabVIEW 18 and DAQmx 18.6. A timing property node reported SampClk.MaxRate as 1.0 MHz and the task gave the same 200040 warning when I tried to set the rate higher anyway.
FWIW, when I used a *device* property node rather than a "timing" property node to query for AO.MaxRate, it output the documented 2.86 MHz. (Rounded -- technically a timing property node reported a timebase divisor of 7, so the task apparently derives its sample clock from the internal 20 MHz timebase.)
I further explored what I got from an AI task. That worked correctly, giving results expected from the spec sheet. A 1-channel task reported SampClk.MaxRate as 1.25 MHz while a 2-channel tax reported 500 kHz (corresponding to the 1 MHz *aggregate* in the specs.) The device property node had separate properties to query for single channel and for multi-channel. Single channel again gave 1.25 MHz while multi channel reported the *aggregate* rate of 1.0 MHz. The online help for the property makes it clear that it's *meant to* report the aggregate rate, so no real discrepancy there.
Looks to me like a bug or a DAQmx database mistake. During task config, it must consult the "timing node" property to compare the requested rate to (what it thinks is) the device's max rate and then issues the observed warning.
What DAQmx version do you have on your end?
-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.