Access Official Technical PDF

Share Summary:LinkedInEmail

Graphical system design offers a way to bring software, measurement hardware and control logic into a connected engineering workflow. For industrial automation teams, the approach is relevant wherever an application must acquire data, process it and act on it—whether in an embedded controller, a test system or a research installation. The NIWeek 2012 program illustrates how engineers were applying this design approach across those varied settings, while also examining how processor and FPGA technologies could support increasingly demanding systems.

What graphical system design means for automation

Rather than treating measurement, software development and control as isolated tasks, graphical system design links them as parts of a complete system. Engineers can use software to define application behavior and connect that logic with hardware for data acquisition, signal processing, monitoring or control. The appropriate implementation depends on the task: a system may need to handle real-time inputs, coordinate multiple instruments or perform processing close to the hardware.

This system-level view is useful during both development and deployment. It encourages teams to consider how components work together, including how signals are acquired, how control decisions are made and how the system will be tested. It also makes architectural choices—such as using a real-time controller, an FPGA or a PC-based test platform—part of the design conversation rather than late-stage integration decisions.

Matching the architecture to the application

Automation requirements vary significantly. A portable measurement device, an embedded machine controller and a high-channel-count test system do not have the same constraints. The conference program highlights several hardware and software combinations used to address these differences, including PXI-based systems, CompactRIO and Single-Board RIO platforms, LabVIEW Real-Time and LabVIEW FPGA.

These examples point to a practical design principle: select the architecture according to the work the system must perform. Real-time control may call for a deterministic embedded approach. Applications requiring custom I/O or hardware-level processing may benefit from FPGA-based design. Test and measurement systems may need to coordinate instruments and acquisition tasks through a modular platform. The tools and hardware should follow the requirements, not the other way around.

Real-time control and FPGA-based design

Real-time and FPGA technologies can be important when an application has timing or processing demands that must be addressed within the system architecture. The NIWeek workshop, for example, focused on configuring and programming a reconfigurable I/O system using LabVIEW Real-Time and LabVIEW FPGA. The system-design symposium also discussed the trade-off between higher levels of programming abstraction and the need to understand underlying hardware when optimizing performance or developing multirate digital signal processing applications.

For engineers, abstraction can make hardware-oriented development more accessible, but it does not remove the need to understand the application’s timing, processing and I/O requirements. Those constraints should guide how the system is partitioned between software, processors and programmable logic.

Connecting development with test and validation

Test is not simply a final checkpoint. It can influence architecture and development from the beginning. The program included examples of automated test systems built with PXI, LabVIEW and NI TestStand, as well as a virtual vehicle test application integrating motors, power electronics, mechanical dynamics and control software. Virtual prototypes can help teams consider component sizing, system integration and test strategy before a physical prototype is available.

Other examples show the range of measurement and control challenges engineers address:

  • Embedded monitoring: CompactRIO and related systems were used in applications such as energy control, fatigue testing and structural monitoring.
  • Automated test: Modular test platforms were applied to equipment verification, including systems in regulated manufacturing environments.
  • Research and diagnostics: PXI-based systems supported applications such as laser-system control, signal analysis and real-time imaging acquisition.
  • Transportation: Test and measurement workflows were used to investigate electric-drive systems and high-voltage transients.

These are distinct applications, not a single universal solution. Their shared lesson is that control, acquisition and verification need to be designed with the complete system in mind.

Design productivity depends on system choices

The symposium also addressed processor and FPGA convergence, high-level synthesis and many-core computing. These topics reflect a recurring engineering challenge: as system complexity grows, teams must balance performance, flexibility and development effort. Higher-level tools can help express system behavior, while knowledge of the target hardware remains important for optimization and implementation.

For system integrators and plant engineering teams, this balance has practical consequences. Reusable software structures and modular hardware can support a more organized development process, but integration still requires careful attention to interfaces, timing and the behavior of connected subsystems. A design that works in isolation may need further engineering to operate reliably as part of a larger control or test environment.

Practical implications for industrial teams

When assessing a graphical system design approach, begin with the application rather than the platform. Define what must be measured or controlled, the timing behavior required, the processing involved and how the system will be validated. Then determine which elements belong in software, which require real-time execution and whether programmable hardware is appropriate.

Training also matters. The NIWeek program paired technical sessions with courses and certification preparation, reflecting the importance of developing skills alongside adopting tools. A team’s ability to maintain and extend an application depends not only on its initial architecture, but also on whether developers understand the software, hardware and engineering practices used to build it.

Conclusion

Graphical system design is most useful when it helps engineering teams treat measurement, control, computation and test as connected parts of one application. The examples presented at NIWeek 2012 span embedded monitoring, automated test, research and transportation, but they share a need to match system architecture to real operating requirements. For industrial automation decision-makers, the practical takeaway is to define those requirements early, plan validation as part of development and choose tools and hardware that fit the complete system.

Access Official Technical PDF

About The Author