Diagram of Arduino GIGA R1 Streaming LT data reaching openDAQ and DewesoftM clients.

Arduino OpenDAQ

ByFermiLabs.IT

Arduino OpenDAQ

Quick access

Arduino OpenDAQis an embedded measurement project, not a public web application.

Arduino OpenDAQ is a FermiLabs measurement and instrumentation workstream connectingArduino UNO QandArduino GIGA R1systems withopenDAQ-compatible acquisition workflows and explicit timing/evidence boundaries.

Why it exists

Reading a sensor is not the same as building a measurement system. UsefulDAQneeds 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.

Autumn 2026: openDAQ 3.40.3 and reproducible reference signals

TheopenDAQ 3.40.3MVP has an accepted install → start → open → verify sequence on an owner Mac and oneLinux ARM64Arduino UNO Q target. The exact qualification exercises a deterministicReference Device with two synthetic signalsthrough the native openDAQ connection path; it does not prove acquisition from physical sensors on those boards.

ReferenceDomainInfopreservation has also been qualified in an explicit Linux ARM64 Native path, while the LT 4.0.3 codec is known to drop that reference identity. This distinction matters when comparing simulated, reference, replay and measured data.

Integration with live MCU/EFBus measurements is a separate post-MVP milestone. EFBus remains the single transport/data-session owner; the OpenDAQ application must not introduce a competing SPI controller.

Related projects:Arduino EFBusandRoboCup 2027.

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/Dewesoftinteroperability, 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.

Similar Posts