openDAQ on the Road: From MC2026 to the Smart Prototypes Summit

In May, openDAQ joined two important events in the test and measurement calendar: Dewesoft Measurement Conference 2026 in Laško, Slovenia, and the HBK VI-Grade Smart Prototypes Summit 2026 in Udine, Italy.

The two events had different audiences and different technical angles. MC2026 focused strongly on edge computing, embedded analytics, open measurement architectures, and real-time data acquisition. The Smart Prototypes Summit, hosted by HBK and VI-grade, focused on the connection between virtual and physical testing, smarter prototype development, simulation, and extracting more value from measurement data.

For openDAQ, both events were an opportunity to show the same thing from two different perspectives: true interoperability is not just a proof of concept anymore. It is becoming something practical, usable, and visible in real applications.

Showing the Latest openDAQ Version

At both events, we showcased the latest version of openDAQ, including improvements in stability, performance, and overall usability.

More importantly, we were able to demonstrate several new and upcoming integration points that make openDAQ more useful across different parts of the test and measurement workflow:

• new LabVIEW driver, which allows any openDAQ device to be controlled with LabVIEW

• RTMaps integration, which achieves the same outcome, but for RTMaps,

• MQTT function block, which allows openDAQ devices and applications to act either as an MQTT broker or MQTT client,

• Raspberry Pi module, which allows for much faster prototyping of openDAQ devices,

• improved device discovery, configuration, and streaming,

• and continued work on making openDAQ easier to adopt for software and hardware providers, as well as test engineers and system integrators.

From LabVIEW to RTMaps

One of the most important messages at both shows was that openDAQ is becoming available for use from the tools engineers already know.

With the LabVIEW driver, openDAQ-compatible devices can be accessed from one of the most widely used engineering environments in test and measurement. Instead of writing a custom integration for every new device, LabVIEW users can work through a common openDAQ interface for discovery, configuration, and streaming.

RTMaps adds another important use case. In automotive and ADAS workflows, engineers often need to combine data from many different sources: sensors, vehicles, simulation tools, cameras, and measurement devices. By integrating with RTMaps, openDAQ can participate more naturally in these complex real-time data workflows.

MQTT, Raspberry Pi, and Edge Workflows

Another highlight was the MQTT function block, which opens the door to more IoT-style and distributed measurement scenarios.

MQTT is already widely used for lightweight messaging in connected systems. With openDAQ, this creates a simple way to bridge measurement data into environments where publish/subscribe communication is already the standard pattern.

The Raspberry Pi module also fits into this direction. It shows how openDAQ can move closer to lightweight, embedded, and edge-oriented systems. For users experimenting with prototypes, distributed acquisition, or low-cost measurement nodes, this makes openDAQ more approachable and easier to demonstrate outside a traditional desktop-only setup.

Different Shows, Same Direction

The Smart Prototypes Summit approached the topic from another side: vehicle development, smart prototypes, simulation, and the connection between virtual and physical validation.

Here, the challenge is not only collecting more data. It is making data usable across the whole engineering workflow. Measurement data needs to move between physical tests, simulation environments, analysis tools, and decision-making processes.

This is exactly the kind of environment where a common interface matters. If every device and every application requires a separate custom integration, the engineering workflow becomes slower, more fragile, and harder to scale.

openDAQ’s role is to reduce that friction.

What We Took Away

The biggest insight from both events was simple: the industry is ready for more open connection points.

Engineers want to keep using their preferred tools. Hardware providers want their devices to be easier to integrate. Software providers want access to more devices without building and maintaining a separate driver for each one. And end users want measurement systems that can grow without becoming locked into one closed stack.

That is why the new openDAQ features matter. LabVIEW, RTMaps, MQTT, Raspberry Pi support, and the continued improvements to performance and stability all point toward the same goal: making interoperability easier to use in practice.

Thank You

A big thank you to everyone who visited us in Laško and Udine, asked questions, gave feedback, and challenged us with real integration scenarios.

For us, these events were a valuable reminder that openDAQ is not only about connecting devices and software. It is about helping the test and measurement industry build systems that are more flexible, more scalable, and more open.

See you at the next event.