Access Official Technical PDF

Share Summary:LinkedInEmail

Real-time data acquisition and control is essential when an application must respond to measured signals within a predictable time. In test stands, production equipment and research systems, relying on a general-purpose PC alone can make timing dependent on the computer’s operating system and workload. A dedicated real-time system addresses this challenge by handling time-critical tasks locally, while a PC manages visualization, user interfaces and other standard functions.

This division of work supports applications such as online measurement analysis, complex triggering, open- and closed-loop control, and waveform generation. The practical value lies not simply in processing speed, but in making process execution deterministic: the system can respond to inputs and run control tasks according to defined timing.

How a dedicated real-time architecture works

In an ADwin system, a local processor acts as the real-time core. It executes acquisition and control processes independently of the connected PC, using its own processing resources and memory for program code and measurement data. Analog and digital inputs and outputs, counters, interfaces and optional expansion modules connect the processor to application signals and equipment.

The PC and real-time system have distinct responsibilities. The real-time processor handles fast, predictable tasks close to the signals. The PC can display graphical interfaces, visualize data, and access databases. Communication between them can use Ethernet or USB, while fieldbus interfaces can connect the system to a PLC. A bootloader option supports operation without a continuously connected PC.

This separation also affects system behavior during a PC interruption. The real-time system can continue executing its application if the PC crashes, helping preserve the operation of the real-time process. Communication and real-time execution can also run at the same time without the communication disturbing the deterministic timing of those processes.

Real-time data acquisition and control in practice

Each sampled value can be evaluated as part of the acquisition process, allowing an analysis or control action to follow within the same sampling step. This is useful where the relationship between a measurement and the response matters, including fast machine control, quality assurance, endurance testing and production or research test stands.

Applications can include:

  • Acquiring analog, digital, counter and bus signals.
  • Evaluating trigger conditions and measurement data online.
  • Running open-loop or closed-loop controller functions.
  • Measuring encoder position, frequency, pulse periods or revolution speed.
  • Generating periodic, non-periodic or arbitrary waveforms for testing and control.

Timing requirements vary by task. The described ADwin architecture supports applications ranging from millisecond and microsecond process cycles toward the kilohertz and megahertz ranges, with response times specified as short as 300 nanoseconds for the real-time system. Actual configuration and performance depend on the hardware and application requirements; the key design principle is that the dedicated processor, rather than the PC, is responsible for time-critical execution.

Developing and monitoring real-time processes

ADbasic is the development environment for creating deterministic processes on ADwin systems. Its functions provide access to inputs, outputs and interfaces, as well as process control and communication with a PC. The real-time operating system manages multiple processes with different priorities and cycle times, enabling tasks to run in a multitasking arrangement.

ADbasic also supports source-code compatibility across previous versions and different ADwin systems, according to the supplied technical description. That can help teams carry existing application code forward when using other compatible hardware, rather than treating every hardware change as a complete software rewrite.

For application development and operation, ADtools provides indicators and controls for exchanging parameters and viewing measurement data. ADlog can acquire, visualize and store analog, digital, counter and CAN signals in formats including ASCII, CSV, binary and DIAdem. Drivers provide PC software with functions for data exchange, process downloads and starts or stops, and monitoring system resources. Supported environments listed in the technical material include Windows, macOS and Linux, alongside a range of programming and engineering tools.

Matching I/O and processor options to the task

Compact systems and modular platforms address different application scales. Compact systems such as ADwin-Gold and ADwin-light-16 combine a local processor and memory with onboard I/O in small packages intended for laboratory, machine, mobile and OEM applications. Available configurations and options differ, including channel counts, communication interfaces, counters and encoder functions.

ADwin-Pro II is a modular, expandable system for applications ranging from a small number of signals to several hundred. Its modules can be selected for the measurement and control job, including multiplexed or parallel analog inputs, digital I/O, counters, PWM, signal conditioning, interfaces and analog outputs.

When parallel sampling matters

With multiplexed analog inputs, channels are measured sequentially. Parallel analog input modules use one analog-to-digital converter per channel to acquire channels simultaneously, avoiding phase shift between those measurements. This can matter when signals must be correlated, such as when analyzing phase relationships or using several measurements together in a control loop. The described Pro II platform can be expanded with additional modules for higher channel counts.

Using a co-processor for module-level tasks

The embedded TiCo processor is a co-processor available on specified ADwin systems and modules. It can access the inputs and outputs of the module where it resides, while the main ADwin processor accesses TiCo variables, data and processes. TiCo can run multiple programs in multitasking mode and is intended for deterministic tasks such as data preprocessing, trigger handling, digital filtering, bus analysis and controller functions.

TiCoBasic provides a development environment with an approach similar to ADbasic. This adds a way to place certain processing tasks closer to the relevant module while retaining coordination with the main real-time system.

Practical implications for system design

Choosing a real-time platform starts with the timing and signal requirements: which inputs must be sampled, whether simultaneous acquisition is necessary, what control or waveform tasks must run, and how the system should connect to a PC or PLC. Channel count, signal conditioning, fieldbus needs, standalone operation and future expansion also influence the hardware configuration.

A dedicated real-time processor can separate deterministic execution from PC-based visualization and data handling, supporting responsive acquisition and control without assigning time-critical work to a general-purpose computer. For engineers and integrators, the practical task is to match processor, I/O, software and communication options to the application’s required timing and signals. Early technical consultation can help clarify that configuration, particularly for specialized or OEM systems.

Access Official Technical PDF

About The Author