Skip to content

Admin Guide

This guide is for the people who set up and support FIDOs: organization administrators, and the engineers who build SD cards, update firmware and run the cloud server. Field procedures are in the User Guide.

System architecture

The FIDO sampler consists of the following stack of technologies:

  1. The FIDO sampler itself (motors, valves, etc.)
  2. The Sampler Microcontroller, based on an STM32 MCU.
  3. The Sampler Microcontroller Code
  4. A RockPi S controller, which runs the sampler over a serial protocol, serves the local user interface, and connects to the cloud server over MQTT. Useful links:
    1. RockPi Controller Board
    2. RockPi Housing
    3. RockPi WiFi Antenna
    4. 32 GB SD Card
    5. Power Supply
    6. Additional Debugging Tools
      1. USB TTL Debug Cable
      2. USB Power Meter
  5. The Web Application, which runs on the RockPi controller and on Amazon Web Services.
    1. Local Interface (NOTE: You have to be connected to the local WiFi hotspot from the RockPi device to get to this interface.)
    2. Production Cloud Server
    3. Development Cloud Server
flowchart LR
    fido-sampler[Sampler]
    stm32-mcu[Sampler STM32 MCU]
    subgraph Headscale-Tailscale VPN
        rockpi[RockPi Controller]
        subgraph AWS EC2 Server
            nginx[Nginx Server]
            subgraph Docker
                flask[Gunicorn App Server]
                mosquitto[MQTT Broker]
            end
        end
    end
    cloud-app[Web App]
    local-app[Web App]
    fido-sampler --- stm32-mcu
    stm32-mcu <--serial--> rockpi
    rockpi <--telemetry--> mosquitto
    mosquitto <--> flask
    flask <--> nginx
    nginx <--> cloud-app
    rockpi <--wifi--> local-app

Versioning and compatibility

READI-Net (this repository) and the FIDO firmware (esp-sampler) are versioned independently as VN.x.y (READI-Net) and VN.a.b (esp-sampler). The shared leading number N is the compatibility contract: every READI-Net VN.x.y release must work with every esp-sampler VN.a.b release. x.y and a.b are independent of each other and don't correlate. For example, READI-Net V1.0.18 and esp-sampler V1.3.0 are a valid pair.

  • Bump the major in both projects together when either makes a change the other can't handle (serial protocol, command names, parameter file format, result codes).
  • Bump minor/patch independently for fixes and features within the line.
  • The User Guide's footer (copyright in mkdocs.yml) names the major it documents. Publish a new edition of the manual with each new major.

The user-facing explanation is in Software Versions.

Admin tasks