Accessing advanced engine properties in TestStand

[misha]

How the following properties of TestStand engine can be accessed programmatically:
1) Station Options
2) Search Directories
3) Report Options
????????????????

Regards,

Misha.

[Alejandro_del_Castillo]

Misha,

1) You can access the station options programatically by using the class engine.stationoptions. For more information visit:

http://digital.ni.com/public.nsf/websearch/540AB704BADC5A9686256D820071029A?OpenDocument

2) The classes searchdirectory and searchdirectories will give you programmatic access to the defined search directories. For more information:

http://digital.ni.com/public.nsf/websearch/94419ED0C471910186256D82007432EC?OpenDocument

3) You can can overwrite the default report options by modifying the report options callback in your client sequence. This method (as well as others) is explained in the following document:

http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/9c863f119ed03cf286256c450
0540b7a?OpenDocument

Best Regards,

Alejandro del Castillo
Application Engineer

[misha]

Alejandro,

Thanks for your reply.

First of all, I'm working in TestStand 2.0, and have neither StationOptions nor SearchDirectories classes.
Actually I'm accessing SearchDirectories property, but the way, which I used, has side effect. Explanation I have posted as another question under the same title. See:
"Accessing advanced engine properties in TestStand".(posted by misha on 12/29/2003 in TestStand).
Additionally, I have difficulties with updating user manager filename.
Concerning ReportOptions, I would prefer to access it by means of Engine (this code will work in Operator Interface), and not from report options callback.
Anyway the link above is invalid.


Regards, Misha.

[Alejandro_del_Castillo]

Misha,

The engine itself in 2.0 exposes some of the options that the new StationOption class in 3.0 has.

You can use the LabWindows/CVI instrument driver inifile.fp to directly modify the ini files that have the default options that are loaded by the engine during initialization:

+ \Cfg\TestStandModelReportOptions.ini
This file contains all the report options. The correct link for the KB that talks about how to overide the report options callback is: http://digital.ni.com/public.nsf/websearch/9C863F119ED03CF286256C4500540B7A?OpenDocument

+\Cfg\TestExec.ini
This file contains the station options. You will find the search directories here as well. To add a seach directory you will need to add a section (
look for one already created) with the new path and then modify the item %HI: SearchDirectories = [#] (# will have the number of search directories in total)

You can use the CVI sample project ini.prj (\CVI\Samples\toolbox) to visualize the ini files in sections/items and to get familiar with the functions from the instrument driver used to programatically modify ini files.

I haven't validated the bug that you reported on your other post. Soon I shall post my answer. In the meantime you can use the method explained above.

Best Regards,

Alejandro del Castillo
Application Engineer

[Scott_Richardson]

Misha -
If you decide to modify the Testexec.ini file, make sure that the TestStand engine is not running within an application such as the sequence editor or an operator interface. If the engine is running, any changes that you make to the file may be overwritten if the engine performs an operation that forces it to persist its in memory copy of the file.

Scott Richardson