Tested in the openDAQ compliance lab

For DAQ devices whether they reach openDAQ through their own device module or a shared protocol integration.

Discovery

A stock openDAQ client can find the product and read what it is.

• Announces itself over mDNS on IPv4 and IPv6
• Advertises its available connection and streaming capabilities truthfully
• Connects from an unmodified SDK client with no product-specific code
• Exposes a coherent device, channel and signal structure

Streaming

Measurement data arrives, is interpretable and keeps arriving.

• Streams every signal it declares over native streaming or openDAQ Streaming LT
• Publishes a valid data descriptor and an explicit domain (time) signal for each
• Sustains its declared sample rate under a soak test without silent sample loss
• Recovers cleanly from a dropped connection and reports the gap

Configuration

The product describes its own parameters well enough for a generic client to build a real interface.

• Properties carry complete metadata: current value, valid range or selection, unit, default and whether they are writable
• Writes are validated, applied and reflected back including rejected ones
• Structural changes are announced rather than requiring a reconnect
• Read-only and hidden properties behave as declared

Synchronisation

The product is honest about the time base it can share with other vendors' products.

• Reports its synchronisation source, interfaces and lock state through the sync component
• Timestamps align with a reference clock within the declared tolerance
• Declares its own limits rather than claiming a lock it does not hold
• A product with no synchronisation says so rather than reporting a false one

For measurement, analysis, automation and recording software consuming compatible devices through the SDK.

Discovery and connection

The application reaches compatible devices without knowing them in advance.

• Discovers devices on the network and connects without device-specific code
• Handles connection strings, address families and streaming protocol selection
• Connects over each protocol the ecosystem uses and not only the one it was built against
• Reconnects after a device disappears and returns

Structure and properties

The application presents what the device says about itself including things it has never seen.

• Renders the device, channel and signal structure the device publishes
• Presents every property kind correctly including selections, structures and nested objects
• Respects units, ranges, defaults and read-only flags in its own interface
• Handles a property it does not recognise without breaking the view

Streaming and time

The application reads data correctly including the difficult parts.

• Reads signals with their domain signal and applies the data rules correctly
• Aligns data from several devices on a common time base
• Handles gaps, reconnects and descriptor changes without corrupting the record
• Preserves units and ranges through to whatever it exports

Reduced capability

The application still works with products that offer less than it would like.

• Consumes a streaming-only product (one reachable over openDAQ Streaming LT) without expecting configuration
• Presents a device with no writable properties as read-only rather than as broken
• Degrades visibly and explains what is missing instead of failing
• Does not require synchronisation from products that do not offer it