Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial test automation depends on more than selecting instruments or writing test sequences. Engineers must connect hardware, software, validation methods, data, and lifecycle decisions to the needs of a particular industry. The NIDays Europe 2019 agenda, held in Munich, brought these concerns together across aerospace and defence, semiconductors, automotive, academic research, and software engineering.

Rather than treating test as a single discipline, the program presented it as a set of linked engineering challenges: validating complex systems, adapting test platforms to production, managing software and data, and preparing for changing technologies. These themes remain useful considerations for automation engineers, integrators, and operations leaders planning test capabilities.

Industrial test automation spans the system lifecycle

Several sessions addressed the relationship between development, validation, and production. Topics included bridging validation and production test, semiconductor design-to-test workflows, and testing radar sensors in both validation and production contexts. Together, they highlight a practical planning issue: test approaches need to support the stages where a product or subsystem is designed, characterized, verified, and manufactured.

When those stages are treated in isolation, teams may face duplicated effort or difficulty transferring test knowledge and methods. The agenda’s focus on common approaches and workflow improvement points to the value of considering how test requirements evolve across a lifecycle. That does not mean every stage uses identical equipment or procedures. It means that interfaces, measurement needs, and handoffs deserve attention when the overall test strategy is designed.

This lifecycle perspective also appeared in sessions on obsolescence management and scalable test systems. For plant and engineering teams, lifecycle planning includes looking beyond initial deployment: how a system can be maintained, adapted, or scaled as requirements change. The agenda framed these as engineering and business concerns, not merely equipment-selection decisions.

Hardware-in-the-loop testing for complex systems

Automotive sessions put particular emphasis on hardware-in-the-loop (HIL) and simulation. The program covered PXI simulation setups for advanced driver-assistance systems (ADAS), multidomain HIL and sensor simulation for autonomous driving, and virtual testing for driver-assistance development. It also included radar target simulation and connected-vehicle validation.

HIL testing combines physical hardware under test with a simulated environment or system interaction. In automotive development, that can provide a structured way to exercise components and systems under defined conditions before, or alongside, vehicle-level testing. The agenda’s range of sessions shows that the scope can include more than one domain: radar, sensors, connectivity, and vehicle behavior may all be relevant to a validation workflow.

For integrators, the practical design question is how to represent the system under test and its operating context. Teams need to determine which signals, interfaces, and behaviors must be simulated, and how the setup will fit into the wider validation process. The program’s attention to continuous validation and high-fidelity synthetic environments underlined the importance of connecting test methods to development timelines and system complexity.

Modular platforms across sectors

PXI-based systems featured in sessions on defence electronics, radar simulation, satellite integration, and semiconductor test. Other topics included electronic warfare sensor testing, aircraft systems, and production test solutions. This cross-sector appearance illustrates why modular test platforms are relevant to organizations facing varied measurement and control requirements: a platform can be configured around a specific application rather than assuming every test has the same form.

However, modularity alone does not define a successful solution. The agenda paired platform discussions with application-specific concerns, including verification of active electronically scanned arrays, built-in self-test validation, wafer probing at mmWave frequencies, and end-of-line testing for high-voltage battery packs. Such examples reinforce the need to match test architecture to the device, measurement challenge, and operating context.

For system designers, this means balancing reusable infrastructure with application-specific hardware and software. A reusable foundation may support consistency, while the test application still requires careful engineering for its particular signals, timing, interfaces, and validation objectives.

Software and data are part of the test architecture

The program treated software engineering as a core element of test-system design. Sessions covered TestStand and VeriStand updates, LabVIEW and LabVIEW NXG, Python integration, software quality analysis, application security, messaging frameworks, and deployment and diagnostics with SystemLink software. Other discussions focused on scalable architectures and process improvement.

These subjects matter because automated test systems are software-intensive. Test logic, instrument control, data handling, deployment, and maintenance all influence how a system operates over time. Software structure and quality practices can therefore affect more than code readability; they shape how teams work with and support test applications.

Data management also appeared in sessions on analysis workflows, server-side scripting, system management, and machine learning. The agenda did not suggest a single approach for every organization. Instead, it reflected a broader engineering consideration: test data and system information need workflows that suit the intended analysis, deployment, and diagnostic tasks.

Energy and electrification expand test demands

Electric-vehicle topics featured prominently on the second day, including battery cycle testing, battery-pack end-of-line testing, electric-drive validation, inverter testing, and high-voltage HIL simulation for motors. Sessions also addressed DC/DC converter validation and testing electrical aircraft systems.

These topics bring together measurement, power electronics, simulation, and production requirements. For teams developing or manufacturing electrified systems, test planning must account for the specific component and stage under test. A battery cycle test, a production end-of-line check, and an inverter simulation serve different purposes, even when they sit within the same broader product ecosystem.

Turning the agenda into practical planning questions

The NIDays Europe program offers a useful checklist for organizations reviewing their test strategy:

  • Lifecycle: How will validation methods connect with production test and later system support?
  • Architecture: Which parts of the platform can be reused, and which need application-specific design?
  • Simulation: What system behaviors and interfaces must a HIL or virtual test environment represent?
  • Software: How will teams structure, validate, deploy, and maintain test applications?
  • Data: What analysis and diagnostic workflows are required after measurements are collected?

For industrial automation decision-makers, the central implication is that test capability should be planned as an integrated engineering system. Hardware, software, simulation, data practices, and lifecycle support all contribute to how well a test solution fits its purpose. The 2019 agenda’s cross-industry perspective is a reminder to begin with the application and its lifecycle, then shape the platform and workflows around those requirements.

Access Official Technical PDF

About The Author