Got it ! To display first element:
↧
Re: Accessing Object Reference from C#
↧
How TestStand Deployment Utility determines the LabVIEW version to build?
I am trying to build a packed library from a .tsd file (TestStand utility file). I built using TestStand 2017, but the built packed library is LV2018 (I can see in build log as below that build occured in the LabVIEW 2015).
I couldn't find in LabVIEW options under deployment utility for any LabVIEW version selection.
TestStand is also selected with Auto selection for RunTime engine and NO selection given for LabVIEW Development System
↧
↧
Re: How TestStand Deployment Utility determines the LabVIEW version to build?
Found it...!
The Active LabVIEW version determines it. If I have LV2015 opened and trigger the build, then TSD can pack in LV2015. If any later version is opened (like 2018 in my case), then TSD packs in that version.
So, for my continuous integration, it's important to load the desired LabVIEW version first before triggering the build in TestStand Deployment.
--
Thanks
AJ
↧
Where are Report Options settings stored locally?
Where (folder/file) are the settings stored on computer for things like Report Options, etc.? Is it a .INI file we can view?
↧
Re: Where are Report Options settings stored locally?
Most of those settings are stored in the "TSAppData\Cfg" folder, which is located in a directory similar to C:\ProgramData\National Instruments\TestStand 2019 (32-bit)\Cfg. Most specifically on the report options, dive deeper into the ModelPlugins folder to find ResultProcessing.cfg. This is actually an XML file.
↧
↧
Re: Where are Report Options settings stored locally?
Thanks crossrulz!
I found this XML file, but doesn't look like it updated the contents based on what I entered in the Report Options UI. The file's modified date/time is also not the same when I updated. It must be getting saved somewhere else.
↧
Property Loader - JSON, NoSQL, SystemLink, or More Advanced Features?
I am tasked with upgrading an old test sequence at my company. One of the steps is the property loader. I thought I had everything correct, but I am still getting issues. I would like to upgrade the property loader to use a more friendly syntax or scheme. Some questions:
1. Can we use a JSON formatted property loader file? I think this would look a lot lot nicer than CSV or tab delimited.
2. I have seen that it is possible to use a database connection to query and load the properties. Is it possible to use a NoSQL database?
3. Is it possible to write a plug-in for TestStand to add either of the above features myself? I figure asking this here might simply provide a faster answer with better links than I could find on my own.
4. Is there any thought of integrating the property loader with SystemLink? I know that SystemLink uses a MongoDB server underneath to store all the system information, so I think it would be a small leap to add a "Property Modifier" tab or section where users could add their own properties to be stored with all the other pertinent system information.
↧
Re: Reading Network Variable value in Teststand sequence
Hi jigg,
Thank you for your response.
I have the Network Variables called out on a LabVIEW .lib file. Do you mean that I call the LabVIEW utility feature in test stand and Deploy library to read/write the status of Network Variable ?
Thanks,
Kaizen14
↧
Re: How do I return the VI path of a test step in LabVIEW?
Hi guys,
I know that this thread was solved, but I have the same problem, and I do not know how to find this particular constant type (TSAdp.LabViewModule).
Thank you in advance.
↧
↧
Re: Reading Network Variable value in Teststand sequence
Yes
↧
Report only last fail
Hello,
is there a way to report only fail from subsequence to teststand db? For now if product fails, I can see in log file:
Step fail
Subsequence fail
Mainsequence fail
and in teststand db its similar:
mainsequence callback fail
subsequence fail
step fail
I would like to report only step fail. Is it possible to set it up?
↧
Create "TypeDef" Step (TestStand)
Hello everyone,
I was wondering if there's a way to create a Step that updates itself if I change any copy of it, as it happens in LabVIEW with the TypeDef controls.
In case I'm not being clear, if I have Step "Turn Off Voltage PS" saved as Template then I use the exact same Step in many places from many Subsequences. Then, if I make a change in one of these in any sequence, I have to manually update every one in the sequence.
It would be great for it to update automatically, is there a way to do this or some similar sort of thing?
Thank you in advance.
Best Regards.
↧
Re: Create "TypeDef" Step (TestStand)
Hello,
I think you are describing the purposes of Custom Step Types. It allow to define a Step definition, that is shared. If you make some modification to the definition, it is propagated to all instances.
Be aware that some configuration elements are specific to each instance of your step (adapter configuration for instance), and other are shared. It implies more work than the use of Tempalte, but it seems to be more relevant in your case.
Pick a look at the TestStand Custom Step Type Development Best Practices, in particular the table "Comparison of Step Templates Versus Custom Step Types"
Best regards,
↧
↧
Re: Create "TypeDef" Step (TestStand)
Hi, thank you for your response.
I tried that but It doesn't update the already placed Steps.
I tested it modifyng the Test Limits, Comparison Type and Pre-expression.
Do you know if I might be doing something wrong?
↧
Re: Create "TypeDef" Step (TestStand)
These are typically instance related values. If I modify a test limit in one NumericLimitTest, I would prefer not to apply this limit on every other NumericLimitTest instances.
For limits, you may want to point to a global variables. The value of the limit will be global, and every instances will point to this variable. Comparison Type can also use this mecanism.
For Pre-Expression, you can define in a Step Type the Default Expressions. It mean default value, that can be modified once the step is instanciated. It is still possible to force the propagation to "in-memory" sequences using the Apply Changes in this Dialog Box to all Loaded Steps of This Type checkbox. Loaded sequence files that have instances of a Step Type will(should) be updated when you will click OK :
Hope this helps
↧
Re: Create "TypeDef" Step (TestStand)
I clicked once that checkbox and thought it would remain Checked forever.
It works thank you.
↧
TestStand Deployment Utility not picking the correct version of LabVIEW
Hello All, I'm hoping someone can provide some insight into how to correct the situation I find myself in. I have a project that I'm trying to package up the LabVIEW and TestStand pieces into a package. So, I'm using the 64-bit version of TestStand 2017. I have installed and opened the TestStand Deployment Utility (64-bit) and configured it all. In TestStand 2017 I've configured the LabVIEW adapter to be 2017 32-bit, which is what I developed the LabVIEW portion in. I have even opened up TestStand and the LabVIEW modules to make sure that everything is looking good.
The problem here happens when I try to load and build the package using the deployment utility. I get error -19053. If you look further up at Code 19401 it shows that the LabVIEW version is 2016 f5 (16.0.0) (64-bit) English. The Picture is attached.
My question is how/where do I change that?
I appreciate any help anyone can provide.
Thanks,
Erich
↧
↧
Re: Teststand simple UI using Labview
Hello,
Thank you all for your support. In fact the event on my list control was working, I just forgot to close the sequencefile reference.
↧
User login from code
Hi All,
I have the following question regarding user login. I would like to pass username and login from C# to engine and start it.
I have found some old topics, but links are no longer valid.
axApplicationMgr.Start() displays login dialog, but I would like to avoid and do it in the background.
Thanks,
Mike
↧
Re: User login from code
The engine calls the LoginLogout sequence of FrontendCallbacks.seq, so looking at the frontend.dll C source code to see how that handles logging in the system user may be helpful to you. I believe as long as you have a valid user in the in the User Manager, you can override this callback, call TS_EngineSetCurrentUser and then bypass the Login dialog in the same manner as how frontend.dll handles the system user.
I know it's not C#, but the method should be equivalent.
I hope this helps.
-Jack
↧