11-04-2015 11:09 AM
I want to create a container of variables (still under development) that is viewable from all sequences without:
Another option would be to have a custom *.ini file similar to globalstations.ini but for a specific project. I don't know how to do this.
I'm only using TestStand and LabVIEW.
For example if this was in C, we pass a pointer to the massive structure in memory.
Thanks
11-04-2015 01:45 PM
I would like to avoid having a different StationGlobals.ini file for each project. This can become a hassle to manage when there is multiple projects on a test station.
Thanks
11-05-2015 04:28 AM
Hi,
did you have a look at datavalue references? Those are I think the closest you will get to pointers using LabVIEW.
Best Regards
Mathis
11-05-2015 07:18 AM - edited 11-05-2015 07:19 AM
I'm not trying to transfer code from LabVIEW to TestStand. Thanks for the information if I ever need to do that in the future.
I just want to basically have a project variables viewed by a select group of sequence files.
11-05-2015 07:41 AM
Looking into this a bit more it seems to me that your data does not necessarily need to be abstracted by a pointer but could also get abstracted by being cast to a variant or for what that is worth, flattened to a string or XML ... something which is agnostic to what type of data it actually contains.
In particular when looking at the case of variants it becomes clear that this is a limitation of Teststand:
http://forums.ni.com/t5/NI-TestStand/typecasting-Labview-variant-in-Teststand/td-p/2160452
I don't think there is a built in function to dereference a pointer. When dealing with pointers these are usually used to pass them into CVI code modules or activeX/.net calls
That said you can obviously create a code module which references/dereferences pointers or DVRs.
Best Regards
Mathis
11-06-2015 10:36 AM
11-10-2015 09:12 AM
That might actually work. I will need to test it. Is there any plans in TestStand to add a project ini file?
@Scott_Richardson wrote:
A called sequence can define a parameter to be just a container and the calling sequence can pass anything, if you disabled type checking on that parameter. However, a developer of the called sequence cannot see or build expressions easily, they must just know the structure of the parameter's container. Is that an acceptable limitation?
11-12-2015 05:01 PM
I do not know what you mean by a "project ini file"?
11-13-2015 03:02 AM