Arduino OpenDAQ

Arduino OpenDAQ

Arduino OpenDAQ is a FermiLabs measurement and instrumentation workstream connecting Arduino UNO Q and Arduino GIGA R1 systems with openDAQ-compatible acquisition workflows and explicit timing/evidence boundaries.

Why it exists

Reading a sensor is not the same as building a measurement system. Useful DAQ needs channel identity, timing, metadata, repeatability, provenance and a clear distinction between live acquisition, replay and simulated data. Arduino OpenDAQ explores those requirements on accessible embedded hardware.

Project scope

• Arduino UNO Q gateway and application paths;
• Arduino GIGA R1 Streaming LT evolution;
• EFBus-backed transport for UNO Q applications;
• optional openDAQ integration kept separate from EFBus core;
• independently deployable/rollbackable GIGA and UNO Q paths;
• evidence that distinguishes software behaviour from hardware-measured results.

Engineering boundary

EFBus remains the transport authority for UNO Q SPI access. The openDAQ companion is optional. Hardware claims are published only where referenced evidence explicitly supports them.

Why it matters to FermiLabs

Arduino OpenDAQ provides the measurement side of the FermiLabs model → simulate → measure → compare workflow. It can connect software and physical experiments while keeping acquisition quality and provenance visible.

Where to explore

FermiLabs should present supported hardware, acquisition architecture, openDAQ/Dewesoft interoperability, current readiness, selected experiments and related learning material. The technical repository remains authoritative for exact source, compatibility and evidence.

Publication contract

This file is the canonical public narrative consumed by FermiLabs.fermilabs/publication.jsonis the machine-readable project contract andfermilabs/updates.jsonis the public update feed.

Any PR that materially changes supported hardware, acquisition/provider behaviour, public interoperability, installation, release identity, validation status, documentation entry points or known limitations must update the relevant publication files in the same PR. Significant public milestones should add an update item.