Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Telemetry backlog: rows since the last successful push, stored on the card, sent in full, reported when it grows

Abierto
  • ¿Algo no está bien?
#10 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
arduino, cpp
Área
data-engineering, embedded-iot

Línea de trabajo

Start with Okapi.cpp:255–296 to trace afterLogEvent() and the current push flow, then read NW-Status/QUEUE.md requisite 6 for the Feather handshake dependency. The proposal also names the status file, data file, and LED grid plan in NW-Status; inspect those entry points before estimating the changes. Done means the last-success marker survives resets, pushes cover the backlog within the Boron session limit, and the backlog is reported and recorded as described.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Keep a telemetry backlog: the rows logged since the last push that succeeded, kept where a reset cannot lose it, sent in full at the next push, and reported when it grows.

What the firmware does today (Okapi.cpp:255–296). _logCount counts rows in RAM and afterLogEvent() pushes when it reaches _logCountPush (5) and the board is on main power. The push prints the last five rows by SD index, sets _logCount = 0, and then waits up to 180 s for FeatherGPIO to fall. Three consequences:

  1. The counter is zeroed before the result is known, so a push that times out loses its five rows from telemetry.
  2. _logCount and _lastSdIndex are RAM. A reset (watchdog, brown-out, battery swap) forgets both, and the next push sends five rows counted from the reset, not from the last success.
  3. On backup power the push is skipped but the counter keeps climbing; when main power returns the push still sends five rows, and everything before them is never sent.

There is no backlog, only a five-row window, and the window drops rows in each of these cases.

Proposed.

  • The marker, not the count, is the state. Store the timestamp (or SD index) of the last row that a successful push covered. Write it once per success, after FeatherGPIO falls, never before. The backlog is then every row after the marker, and it needs no counter of its own.
  • Where it lives. On the card, as a line in the status file, which the logger already writes and which survives a reset at no wear cost. EEPROM would work for the marker alone (one write per successful push) but a per-row counter in EEPROM would wear a cell out in months at one row a minute, which is why the count is derived and the marker is stored. At boot, read the marker and count rows after it in the data file.
  • The push sends the backlog, from the marker to the newest row, not a fixed five, so a return from backup power or a reset sends what was missed. Cap a single push at a size the Boron session can carry and let the next push continue.
  • Report it. A TELEMETRY_BEHIND message (CAUGHT) when the backlog passes twice _logCountPush, cleared by a success; a column in the data file with the backlog at the time of the row, so the gap is visible in the record afterwards. On the LED grid it is the telemetry column (B1 yellow), per the grid plan in NW-Status.

Depends on separating "connected" from "sent" in the Feather handshake (requisite 6 in NW-Status/QUEUE.md), because a success must mean the rows arrived, not that the modem woke.

Should it survive a boot cycle? Yes. The rows it counts are on the card and survive; a backlog that forgets them while the rows remain unsent is wrong by construction.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BazaY6meA6yMRDeuUsv1Wd

Lenguaje dominante
C++
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NorthernWidget/Okapi_Library

Todos los issues de NorthernWidget/Okapi_Library

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.