@Br0ce77 wrote:
Thank you for the reply jiggawax (cool name).
First; What is in 2016 is irrelevant to this discussion, unless there is documentation for that version and it covers these commands.
You are correct. I was just pointing out that if it is an option for you to update to 2016 then I'd consider that because the settings in TestExec.ini are broken out in a more related manner. If it's not an option then I understand.
Br0ce77 wrote:
I do not mean to question your authority but are you a National Instruments representative that knows for a fact that "no such thing exists" or are you just speculating? Perhaps it is simply not a public document?
I am not a representative of NI. I was under the assumption that by posting in a public forum you were asking if this documentation was made available publicly. And although I haven't read everything on the internet I have read about 99% of the TestStand related information. There is a 1% chance I missed where the TestExec.ini file was documented in a public manner and to the level you are asking. Also, there is a 100% chance I like to make up statistics... 🙂 Let me re-phrase my initial post: "I haven't browsed upon any public documentation about TestExec.ini to the level you are looking." The closest I've seen is found here:
TestStand App Data And as you can see- it only talks about what is stored inside of the config files at a high level.
In the 2016 manual it gives a little bit of insight into the 2014 version of the file: "TestExec.ini was a hybrid of a plain INI file and a PropertyObject file stored in INI format." So if you are familiar with both formats then you could potentially go through it and intuitively figure out what those things are. Another thing you could do is look at the items in the file and derive which class it could be related to. For example if you see the word: RecordResults then you can assume that is related to Station Options because that is an option in Station Options. Therefore you could go look at the help about the API for Station Options and determine the type for RecordResults. I've made it easy for you: Click Here This outlines the class for StationOptions and its related methods and properties.
The reason I asked why you needed to know this information is because generally when someone needs to change something in this file they go through the API. I could help point you toward the correct API methods depending on your needs.
Let me describe some things I do know about the file:
-It is generated by TestStand if it doesn't exist in the simplest form. You can go delete it, restart TestStand and see the bare bones of what TestStand expects from this file. Note that default values will not exist in this file (or any PropertyObject file for that matter).
-The file changes depending on what you do in TestStand. So if you change StationOptions then the file will get updated. Therefore it is not worth trying to manage the file through the API if others can simply change it the native way (i.e. a dialog provided by the sequence editor or the user interface). This is, of course, unless you have other motives.
-Most of the items can be accessed through the TestStand API. Which are documented.
-You should always use different settings in the file for a development PC vs a deployment PC. This is tricky to deploy because you are no longer deploying yours from the cfg folder but a pre-created one.
And lastly- if you want access to NI's proprietary information you should contact them in a less public manner. Just saying.
Hope this helps,
