programmatically export properties

[ADL]

i am using Teststand 3, with a single sequence file that contains multiple sequences. What i want to be able to do is with the click of a button, export all properties from all sequences within a single file to multiple excel spreadsheets. Is there any way to programmatically access the Export Property code.

[Naresh]

Hi ADL,

I am also interseted to know a programmatic way for exporting limits.

But here is a workaround.

Put the property loader in each of the subsequences and disable the runtime error of the property loader or programatically ignored the error -18.

The file that is called by the property loader has the limits for each and every subbsequence that are present in the main sequence file.

Every time a subsequence is called it limits are automatically loaded even thought limit file has more steps than in the subsequence.

This method gives a way to have one limit file for your entire sequence.

How do you collect you results? usually all the information neeed by the limit file will be in the results.
First generate the results file and then cut and paste th
e stape names, comp,unit low limit and high limit to create you own limit file.

Hope this works for you.


Thanks,
Naresh

[David Mc]

Hi ADL,

The DLL that TestStand uses to popup the Import / Export Properties dialog is TSDBComponents.dll. This DLL and its Visual C++ / LabWindows CVI code contained in this folder:

C:\Program Files\National Instruments\TestStand 3.0\Components\NI\StepTypes\Database

David McClelland
National Instruments

[ls5302]

I've noticed there is an example in TestStand 3.1
C:\Program Files\National Instruments\TestStand 3.1\Components\NI\Tools\GenericImportExport.seq which shows how to bring up the dialog box from a step.
My problem is that when I try to use this step in my code I receive an Error:-17306 message.
All I want to do is export a couple of variables during my sequence.

Any suggestions welcomed.

Thanks,

Lukasz

[glennjammin]

Could someone give an example of how to export Properties programatically?  I could really use this.  I believe there should be an export step type also not just a property loader.

[RayFarmer]

Hi,

Have a look at the Import/Export Tool sequence. You should find it in the Tools folder.

Regards

Ray Farmer

[Jervin Justin]

Hi,

Ray: I think Glenn wants to do this programatically, ie, during execuation, like the Property Loader step lets you do. The Import/Export Tool lets you export during edit time, not execution.

Glenn: Unfortunately this is not functionality does not come built-in with TestStand. However as Lukasz mentioned, you can modify the source code of TSDBComponents.dll to allow you to do this. (Not an easy task).

If you'd like to see this feature implemented in a future version of TestStand I would encourage you to file a Product Suggestion. We take customer feedback very seriously and each product suggestion is evaluated by our R&D Team.

Thanks!

[RayFarmer]

Hi Jervin,

I realised this but thought glennjammin might gleam some information from the tool.

Hi glennjammin,

What do you particular what to export and to why?

Regards

Ray Farmer

[glennjammin]

What I really want to accomplish is this:

I have multiple systems I deploy to and they each have a little different setup.  I need to save various settings and be able to recall them.

Currently I have a  configuration entry point that displays a window with different setting like instrument addresses and etc.  It saves these values to the StationGlobals file.

This works fine as long as I don't install other sequences.  And I want to avoid using the stationglobals for various reasons.

If you have a simple way to do this I would greatly appreciate it if you would share.

I thought about creating my own configuration file.

Thanks for the help.

[glennjammin]

I found a way using the write() and ReadEX() in the teststand API.

Here is an example: