Importing station globals

[JShaffer]

I have a long list of station globals (48 in all) that I'd rather not have to manually enter into each installation of TestStand. I've tried loading them in with the property loader step and import/export properties tool, but they only seem to load values for station globals that already exist. I did find the TestStand .ini text file that contains the globals, but it seems like a cheesy backdoor way to do it. Is there a better way?

John 🙂

[SercoSteve]

You can create Tools that programatically create and populate the required Station Globals at run time.  This would remove the need to add your modified StationGlobals.ini to TestStand Cfg directory. 

The Tool can be written in anything that can call the TestStand API, use the TestStand Automation Adapter if you want to stick with TestStand Sequences.

I have included a TestStand sequence that calls an example in LabView 7.1.

Also see http://forums.ni.com/ni/board/message?board.id=330&message.id=10081 for more info.

Hope this Helps

Steve

Message Edited by SercoSteve on 03-10-2006 02:15 AM

[JShaffer]

Thanks Steve.

I pared down the VI to set up individual global variables. Makes sense to do it this way for TestStand, now I can add steps that create and set values for the globals as needed, as well as set up sequences to create the lists of variables. I'd post the code, but I'm in TestStand training this week (away from my PC). If anyone wants it let me know...

John

[sjain]

I have a same problem i.e. exporting long list of station globals. I don't have LabView and even don't want to use it. Is there a way to create a tool in C#.Net to generate a list of Station Globals in NI teststand?

Thanks,

Saurabh

Message Edited by sjain on 08-24-2009 01:23 AM

[SercoSteveB]

Hi Saurabh

I have never used the .NET Module Adapter in TestStand (I am guessing you have).  If you haven't got a copy of LabVIEW you are going to struggle to identify the correct methods to call to generate your variables programmatically.

I have attached a screen shot of some of the Block Diagram of the VI defined above to give you a starting point.  Hopefully you have done some LabVIEW.  If you haven't you should still be able to identify the the methods I am calling (NewPropertyObject, SetValString etc.)

Regards

Steve

[SercoSteveB]

Hi Saurabh

I have never used the .NET Module Adapter in TestStand (I am guessing you have). If you haven't got a copy of LabVIEW you are going to struggle to identify the correct methods to call to generate your variables programmatically.

I have attached a screen shot of some of the Block Diagram of the VI defined above to give you a starting point. Hopefully you have done some LabVIEW. If you haven't you should still be able to identify the the methods I am calling (NewPropertyObject, SetValString etc.)

Regards

Steve