Skip to content

About

GCP measurement slave (ESP32-P4) for the E-Lotto dual-ESP system

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

E-Lotto Slave — GCP Measurement Node (ESP32-P4)

Worker firmware for the E-Lotto GCP project. An ESP32-P4 that runs the identical GCP engine as the master (same Z-score math, same extraction code) and no lottery logic. It waits on UDP port 5000 for commands from the master and measures on its own independent noise source.

The array is up to four nodes — one master plus three of these — found by broadcast at every session start, so there is no node count configured anywhere. The master combines z = Σ z_i / √k over the k nodes that answered that run, so a node missing one reply costs that run's gain rather than the session.

⚠ The √k gain assumes the nodes are independent, and that is not established. Judge a session on per-block combined σ and the full pairwise matrix, never on one correlation figure.

Authors

hpheuer Design, hardware, experiment, and repository ownership
Grok (xAI) Co-author — implementation, debugging, live OTA validation, and docs (Grok Build)

Its own source, never a shared one. This node has its own camera (OV5647 or IMX219) on its CSI connector; entropy is its readout noise in total darkness, from non-overlapping frame pairs. Sharing one camera across nodes would make their measurements identical by construction and the √k gain fictional. The firmware probes both chips and binds whichever answers (GET /diag cam_sensor).

⚠ The enclosure is totally dark, LEDs off. An OV5647 needs RAW10 for that (set in sdkconfig.defaults); on RAW8 its dark LSB is biased and over-dispersed.

A node whose camera stops answers E:<reason> and is dropped and rebooted by the master.

Full architecture, protocol timing, camera physics and robustness details: see the master repo's Dual-ESP: Master & Slave and Camera Entropy sections, and CLAUDE.md there for the rules that bind both repos.

Ethernet, not UART (Phase C)

The UART1 crossover (GPIO14/15, 460800 baud) is gone. This node is a plain Ethernet node on the switch: the master triggers it with a broadcast datagram — one packet, so at n nodes they all start within microseconds instead of after n sequential UART writes — and it answers unicast.

It also runs a small HTTP server, and that is not a convenience. With CONFIG_BOOTLOADER_APP_ROLLBACK_ENABLE=y, an image that cannot be reached over the network is reverted on the next boot by design, so a slave without a webserver cannot be installed at all. That is why this node ran the recovery updater from Phase A until Phase C gave it one.

endpoint
GET / what this node is
GET /diag camera health and firmware identity
GET /camlog this node's per-window camera ring
GET /linearity mean_px per exposure; a light leak makes it grow
GET /otainfo image version / slot / state
POST /update push firmware; 409 only while a window is open (g_measuring)
POST /expose set exposure/gain; 409 for the whole session (latch: M/K set, A or 60 s silence release)

⚠ Three components come from the master repo

CMakeLists.txt pulls them in with EXTRA_COMPONENT_DIRS=../elotto/components, so:

  • The two repos must sit next to each other on disk (…/elotto and …/elotto_slave). There is no copy here — one source of truth means byte-identical extraction on both nodes (elotto_camera), a wire format the two ends cannot disagree about (elotto_link), and one implementation of the logic that decides whether a node is still reachable (elotto_ota).
  • A change to any of them affects several nodes — build and flash all of them, and commit the repos together.

Camera: OV5647 or IMX219 on the CSI connector, SCCB on GPIO8/7, XCLK unwired (RPi-style modules clock themselves). 15-pin FPC, same as the OV module — not the Pi-5 22-pin cable. PSRAM is mandatory.

Protocol (ASCII over UDP; the slave only ever answers)

Every datagram is one frame: EL1 <seq> <payload>. The payload is unchanged from the UART era — swapping the transport was deliberately kept separate from changing what is measured.

Command Reply Meaning
P OK Discovery (broadcast)
M<seg> Z:<z>[,<h1>,<h2>][,wsig=] One measurement; halves of the same window; camera σ tagged
K<budget_ms>,<segs> OK:<exp>,<gain>,<bias>,<mbit_s>,<G|U> Sweep the exposure ladder and certify a rung
D D:<ready>,<bias>,<σ>,<Mbit/s>,<stalls>,<stuck>,fw=<sha>,… Camera diagnostics; the master asks once per block for /loops
A OK Abort — also releases the session latch
R OK Reboot (the master's answer to a camera fault here)

Any command can answer E:<reason> instead. That is the whole failure path: the master names the node in fault, drops it, and sends R.

The segment count travels on the wire, in M and K. It is a session parameter on the master (derived from ?run=), not a constant compiled into both firmwares, so no two nodes can integrate over different lengths. ⚠ A receiver that gets an out-of-range count does not clamp it — it substitutes its own, which is visible in the reply rather than silently wrong.

Why the sequence number. UART was lossless and ordered, so a reply could only belong to the command just sent. UDP guarantees neither. A late reply, accepted blindly, would pair z_slave of run k with z_master of run k+1 — a correlation bug that looks exactly like physics. So mismatched frames are dropped and counted (net_stale in the master's /status), never used. The master resends under the same sequence number and this node answers a repeat of a completed command from a one-entry cache, so a lost reply costs a round trip rather than a second measurement.

⚠ Keep in sync with the master

  • The wire format lives in components/elotto_link/ and is compiled into both ends — there is nothing to keep in sync by hand, which is the point.
  • The segment count arrives with each command, so there is no length to agree on by hand. EL_SEG_MIN/EL_SEG_MAX are one definition in components/elotto_link/ for both firmwares.
  • The yield/abort-poll cadence in gcp_zscore_raw() must match the master's — per-run wall time is max(master, slave), so a mismatch slows every measurement to the slower device.
  • Task priority is load-bearing. The entropy consumer here is the link task, created at ELOTTO_CAM_TASK_PRIO + 1. It must not live in app_main, whose priority IDF hardcodes to 1 — below the camera extraction task. Without the higher priority the producer starves the consumer and a run takes 5.1 s instead of 0.47 s (signature: ring drops huge, waits == 0).

Build & Flash

Flashing is over Ethernet, like every other node:

cd D:\E-Lotto\elotto
.\build.ps1 -C ../elotto_slave build
curl http://192.168.178.103/update --data-binary @../elotto_slave/build/elotto_slave.bin

The node writes the inactive slot, reboots, and marks itself valid only once its webserver answers, so a failed transfer or a dead image cannot strand it. USB (COM6) is only for the bootloader, the partition table, or a board whose recovery updater is gone.

sdkconfig.defaults must keep CONFIG_ESP32P4_SELECTS_REV_LESS_V3=y before CONFIG_ESP32P4_REV_MIN_0=y — the latter depends on it, and without it the choice silently falls back to rev v3.1 and the binary refuses to boot on these v1.3 boards. It must also point CONFIG_PARTITION_TABLE_CUSTOM_FILENAME at ../elotto/partitions.csv: all three projects share one table, or a board flashed by one cannot be updated by another.

About

GCP measurement slave (ESP32-P4) for the E-Lotto dual-ESP system

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages