This operator interface was based on the Simple LabVIEW user interface example. Rather than trying to accomplish all of this within the TestStand sequential process model and overriding the database logging function, I chose to dispense with using a TestStand model entirely and just did a direct call to a single sequence and configured a LabVIEW operator interface to handle sequence setup and database logging. We did not need the built-in user management or report generation and database logging was being done through a custom cloud API from another vendor. In a recent project, the design goal was to provide a simple operator interface for an end-of-line tester that would hide most of the complexity of the TestStand engine. TestStand projects typically use a special model sequence, either one of the built-in types (Sequential, Batch, or Parallel) or a modified version of one of those which directs the general test flow from UUT data input, main sequence execution, through to report generation and displaying the overall result. Everything you can do in TestStand can be done with ActiveX API calls to the TestStand engine, and example operator interfaces are provided for C++, C#, CVI, LabVIEW, and VB.NET. There are ways to override all of this behavior within TestStand itself, but it can be easier to implement your specific requirements using your own programming language of choice rather than learning the ins and outs of the TestStand API. However, in some cases the built-in TestStand functionality is either not specific enough or not required. National Instruments TestStand is software for running test sequences that automates many of the functions that are common to a piece of test software, like user permission management, UUT data input, report generation, and database logging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |