From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
08-07-2024 02:48 PM
Anyone out there who has developed a LabVIEW test executive for VeriStand? The LabVIEW API's look quite robust, and all the functionality appears to be exposed in order to create a test executive for VeriStand.
An example test case might look like this: 1) Connect to VeriStand, 2) Make all sensors and actuators happy by setting User channels and/or running RT sequences, 3) Set model parameters to elicit a particular response, 4) Run test, 5) Check response and determine pass/fail
VeriStand has the Stimulus Profile, but it seems pretty limited with not much functionality to evaluate limits and report results. Our team has the real-time software completed, but we are now looking to develop a framework for automating tests. Wondering how others have tackled this problem.
Thanks!
08-07-2024 03:23 PM
Why not use TestStand?
08-07-2024 03:29 PM
I'm not ruling it out but waiting for native VeriStand steps to be supported in TestStand before we evaluate it as an option. We are an appliance manufacturer and do not intend to use ASAM XIL test steps.
We are currently comparing Python versus TestStand versus LabVIEW. Looking to understand the pros and cons of each.
08-07-2024 03:36 PM
Another option would be to call stimulus profiles to do what you need. There use to be a shipping example of loading and running them from a Labview GUI. We have used that in the past.
08-08-2024 12:58 AM
A long time ago we developed a dedicated full front-end around the Veristand gateway, the drawback was it must be maintained as a product along with the releases of Veristand.
More recently, we used a mix of TestStand (to code the main ATPs, without the XIL API that is too poor), with a step palette built with LabVIEW (useful for 3rd part instrument driver and some signal processing) and C# (because we had difficulties with Python to address some parts of the Veristand API – that is natively written in .NET, to address other 3rd part or strange instruments and also to reuse existing code).