QUOTE (Daklu @ Aug 22 2008, 02:26 AM)
Flattening the class is the only way to pass a class between TestStand and LabVIEW because LabVIEW does not currently support passing classes in their activeX interface. But flattening is well supported because LabVIEW needs to be able to flatten classes in order to save them to disk.
QUOTE (Daklu @ Aug 22 2008, 02:26 AM)
To be honest, wrapping my class methods in a flatten/unflatten vi isn't that big of a deal. I am wondering if I'm trying to use TestStand with LabVIEW modules that are too small. (i.e. Don't do enough) Maybe I should bundle them into larger components.
That is generally a good idea- there is a lot more overhead making a call from TestStand to LabVIEW then LabVIEW calling a subVI. Try to avoid calling LV for code that takes less than 1ms. Also, try to make a TestStand Step for each items that you want to see in your report- you don't want to have TS call a single VI that returns a pass/fail Boolean and no info when things fail!
For example, let's say you want to take 100 points, average them, and perform a limit test. You should NOT loop in TS and take one point at a time in your LV. Instead use a single numeric limit test step to call a VI that takes the points averages them and returns the value to TestStand. Make your VIs very modular so that you can pass the number of points, the channel info etc. so this VI can be easily re-used by changing the parameters in TestStand.
-Rick Francis
