The EFT Module for TestStand is a commercially available architecture and suite of tools for NI TestStand that dramatically reduces test development time and maintenance.
As a principal test engineer at BLOOMY®, one of my roles is to anticipate our customers’ test requirements so that we can evolve our automated test solutions to meet their current and future needs. A common request I receive is the ability for the user to interactively select which tests to run from a menu of tests on the user interface, prior to test sequence execution.
New feature of Bloomy's EFT Module for TestStand improves data recovery in the event of a crashBloomy recently added a new feature to the database logging function of the 2019 EFT Module for TestStand, versions 2019 and later. This new feature allows real time, also known as on-the-fly (OTF), data logging to a datab
To celebrate the release of the newest EFT Module for TestStand version, which adds native support for LabVIEW and TestStand 2019, we wanted to share with you some very useful features that you might not be aware of.
Developing TestStand code on a production machine can lead to unexpected consequences. This describes one way to ensure that production data in the EFT database is not lost as a result of such unintended consequences.
Upcoming New Features
EFT version 2.2 is coming soon with loads of new features to further increase productivity and reduce test development time. While there are dozens of new features and improvements to the EFT Module for TestStand, let’s take a look at five of the most exciting updates.
When developing automated tests for a product, we as test engineers typically focus on what we see as the two most important tasks: ensuring the test works properly, and ensuring appropriate results are collected. Because of this, the person who spends the most time on the system, the test operator, can often be forgotten.
Are you developing test sequences using NI TestStand? If so, beware that a lot more goes into a full test architecture than test sequences. In our experiences, test developers often focus solely on the test sequences and code modules, leaving items like file management, hardware abstraction, operator interfaces, and result processing all but forgotten until you run into a problem. Unfortunately, these items often take longer to develop, and require more in-depth TestStand knowledge than the test sequences themselves.
The Material Review Board (MRB) usually consists of a meeting of personnel from Quality, Materials, Purchasing and Manufacturing engineering. The purpose of an MRB is to review rejected material for disposition. Disposition decisions are often made based on schedule requirements, material cost, availability of alternatives, or analysis of the defect. The MRB material of interest is Printed Circuit Board Assemblies (PCBAs).
