04-27-2010 02:53 PM
Hey Peter,
I have reproduced the behavior. The key to reproducing this is actually what we call "reconfiguration". That is, if the task transitions to a "Verified" state, something like setting an attribute can force the task to recompile. For this bug, when recompiling the DAQmx Task, a cached value was not reset. This is probably more information than you care about. Long story short, we see the bug and can fix this in a future DAQmx version.
There is a slightly better workaround that you can use than what you're currently doing (since this workaround will continue to work with future versions of DAQmx in which the bug is fixed and the code still mostly make sense). If you set a units attribute besides acceleration units (like temperature units), it will force the cache to get reevaluated. Here's a code snippet of what I'm referring to:
You can drag that onto your block diagram anywhere before you begin the acquisition.
Sorry for the inconvenience, and thanks for bringing this issue to our attention.
04-27-2010 10:52 PM
Andy McRorie,
can you post the CAR number?
04-27-2010 11:06 PM
04-29-2010 04:43 AM
06-13-2010 01:45 AM
Hello Peter_S
I just take a look at your second message and I'm quite interested by your subVI "Get DAQ setting" and "Read sensor data" . Can you explain how you program these subVI or why not post them here.