Simplicity AI :: automation intelligence - test measurement control and automation

STANDARDISED PRODUCTION TEST SOFTWARE ARCHITECTURE

Overview

In developing production test systems for a variety of clients, it was found that there were many recurring requirements. Rather than re-inventing the wheel for each test system, it was decided to develop a software framework which supported a set of standard requirements, but also gave flexibility for customisation and expansion. Originally developed to fulfil a specific customer need, this framework is now widely used in all similar Simplicity AI projects and by in-house developers at a variety of clients.

1) Streamlined, Standardised Development Environment
2) Reusable Modules
3) Minimal Programming (Configuration Based)
4) Hardware Vendor Independence
5) Intuitive Operator Environment
6) Flexible, Customisable Reporting/Database Logging

Core Tools

Rather than develop a completely bespoke solution, it was decided to base the solution on industry standard tools, whilst adding a variety of customisations to deliver better functionality, an enhanced user experience and enabling rapid software development.

NI TestStand

The primary purpose of National Instruments TestStand is to sequence test steps (which can be written in any language) and provide a standard framework for sequence development, execution, display, user management and logging. The vast majority of TestStand’s features are fully customisable, which will be tailored to match specific requirements. 14 of the top 15 largest electronic manufacturers and 9 of the top 10 largest contract manufacturers use TestStand for their testing solutions [1]. Due to its extensive utilisation in production test environments and its array of customisation options, the core of the software architecture presented in this solution is based around TestStand. A number of customisations have been introduced to the product to augment the out-of-the-box functionality.

NI LabVIEW

While TestStand can sequence test steps written in any language, the primary development environment was chosen to be National Instruments LabVIEW – owing to its productivity enhancing features, allowing engineers and scientists to develop software quickly without a steep learning curve. Many of the customisations delivered as part of the framework were written using LabVIEW, which gives the end customer examples of how to implement their own customisations

IVI Drivers

For many customers, obsolescence is a major issue. For example, some aerospace clients require test systems to be in use for many decades to support the entire life-cycle for their products. Ensuring that instrumentation can be calibrated and replaced becomes very difficult once a particular instrument reaches its end-of-life. In the past, solutions to this problem often included batch-buys of equipment or re-writing (and re-validating) test applications to use new hardware – both of which waste huge amounts of money. Interchangeable Virtual Instruments (IVI) aim to solve this problem by standardising the software driver layer between instruments of the same class. For example, a test system utilises a Digital Multimeter (DMM) and the software has been written using an IVI DMM Class Driver which provides a standard set of functionality that applies to all instruments that are IVI DMM Class Compliant. The current DMM is later declared obsolete – no spares are available and standard calibration services have ceased. In this architecture, it is then possible to “swap out” the DMM with a new model from the same vendor or one from a completely different vendor without modifying the test software. Therefore, IVI drivers have been used for instrumentation wherever possible in the software architecture.

NI Switch Executive

In most cases, the target test systems incorporated complex switching systems. In order to simplify the process of routing signals from one place to another and to abstract the physical hardware configuration from the test software, National Instruments’ Switch Executive product was selected. This allows for far more readable test applications and allows changes to the physical switching system without having to modify any software.

Next Page: Customisations
Page: 1 2 3

References

[1] NI Developer Zone - Why choose TestStand? http://zone.ni.com/devzone/cda/tut/p/id/4832