11-23-2015 08:27 AM
LabVIEW 2013 (old hand)
DIAdem 2012 (complete noob)
According to the help:
So, I made my code write all four of these properties for all channels:
I'm not in a position to measure the load-time, so to see if it worked, I set the "Maximum" property to TWICE the real maximum, as highlighted above.
The TDMS VIEWER, built into LabVIEW, shows the doubled up property value.
Imagine my surprise then, when DIAdem shows the true maximum:
If I use the name "Maximum2" in the code, then TDMS Viewer is no different (except for that name), but DIAdem then shows me a property called "Maximum2" with a value of 2.0 (what I wrote), and a property called "maximum" with a value of 1.0.
If it's going to calculate the maximum value anyway, why bother with setting the property and how does that speed anything up?
What am I missing?
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Solved! Go to Solution.
11-24-2015 01:32 PM - edited 11-24-2015 01:35 PM
Hey Steve,
I noticed a typo in your value for the Monotony property ("Not monitone"). Since this is not a valid value, DIAdem will calculate all 4 of the channel properties. (From the White Paper: all 4 properties must exist and be populated with valid values.)
Adjust the value to "Not monotone" instead and it should no longer calculate the property values.
Happy Thanksgiving!
11-24-2015 01:40 PM - edited 11-24-2015 01:41 PM
Duh !
You're exactly right. When I went to add all FOUR of the properties, I made a typo, and it rejected ALL the properties.
Not sure I understand the reasoning behind that, but it seems to be a fact.
Anyway, thanks!
Blog for (mostly LabVIEW) programmers: Tips And Tricks