04-17-2009 09:37 AM
04-20-2009 11:23 AM
Hey Sherryl,
Because this was the first device that had multiple subsystems sharing a timing signal, we wanted to have customers "more aware" of the valid values for AO sample clock rate. Therein we did not choose to coerce the AO rates to the next highest value. Unfortunately, that means that you will have to parse the error string or use an array of possible values to get past this issue. There is not a property for valid sample clock rates, just min and max.
Good luck
Gavin Goodrich
National Instruments04-20-2009 12:42 PM
Hi Gavin,
Thanks very much for the information.
Is there a way to put in an enhancement request to provide this functionality in a future release of NI-DAQmx?
04-21-2009 01:08 PM
Sure...
I'll make a request for us to revisit that decision and to reference this post.
-gavin
02-07-2012 11:09 AM
Gavin,
any progress in this regard?
Thanks!
02-08-2012 05:49 PM
Hello diabolo,
I haven't seen this functionality implemented anywhere so far; however, if you need to limit the user interface to certain values, could you not use a combo box with only the accepted values?
You can then feed this into whichever terminal you want and not worry about what the user inputs.