Power diagnostic on the LED grid at start-up: LiPo, solar, alkaline
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
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- arduino, cpp
- Área
- embedded-iot
Línea de trabajo
Start with Okapi.cpp:397 to determine which voltage reading corresponds to the LiPo, then read readOnBoard() and powerAuto() for the existing power measurements and rail selection. Review NW-Status/studies/okapi-leds/ and the Okapi section of NW-Status/QUEUE.md for the design context. Done means the three sources show the specified levels for three seconds at startup, with charging and USB-only cases handled, messages raised as needed, and the LED driver asleep between displays.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Show the state of Okapi's three power sources on the LED grid at start-up, even when none is in a warning zone, so that the installer knows the overall picture before walking away. This is the one deliberate exception to "dark means fine" on the grid, for the same reason the READY chirp exists: the person is standing there, and the question after "is it logging" is "how are the batteries".
The grid as it is laid out (Project-Okapi/Hardware/Okapi.brd, board held USB-C down):
| A | B | C | |
|---|---|---|---|
| row 3 | red | – | green |
| row 2 | yellow | green | yellow |
| row 1 | green | yellow | red |
With fixed cell colours a column is a three-level gauge: one cell lit at the level.
Proposed display, for the three-second window at start-up, then dark:
| Column | Source | Lit cell |
|---|---|---|
| A | rechargeable (LiPo) | A1 green good, A2 yellow middling, A3 red low or absent |
| B | solar | B2 green charging, B1 yellow no charge current |
| C | alkaline primary | C3 green good, C2 yellow middling, C1 red low or absent |
The status RGB LED keeps Margay's patterns unchanged; the grid shows only what Okapi has and Margay does not.
What must exist first, in order. Today readOnBoard() logs VBeta, VPrime, ISolar and IBeta, and powerAuto() tells which rail came up; nothing raises a message.
- Decide which of VBeta and VPrime is the LiPo (the open comment at
Okapi.cpp:397). - A LiPo voltage-to-level curve. Margay's alkaline fit does not apply.
- Two band thresholds per chemistry, in Page 1's battery block (Blocks 0–1 are provisioned for this).
- A definition of "charging": ISolar above a floor, or the LT3652's
!CHRGline, which reaches the I/O expander at GPA3 and is never read. Check what ADS1115 channel 1 measures, sinceV_SOLAR_SENSEgoes to the PAC1934. - The USB-only discriminator, so a benched board with no pack fitted does not show red (the four bench readings in NW-Status/QUEUE.md).
- Messages:
BATTERY_LOWexists and is raised nowhere; add the backup-in-use message from_powerState. - The PCA9634 driver: wake, LEDOUT, sleep, with pin 0 reclaimed from the stale
ADC_Sense_SWdefine. Awake it draws 2.5 mA against an 80 µA sleep budget, so it sleeps between displays.
Hardware, while the boards are not yet made (Project-Okapi): label the columns on the silk (LiPo, SOLAR, AA) and mark column C's direction, or fit column C's LEDs the same way up as A. The current labels sit on the documentation layer, not the silkscreen.
Design notes and the studies behind them: NW-Status/studies/okapi-leds/ and the "Okapi's grid carries what Okapi has and Margay lacks" section of NW-Status/QUEUE.md.
🤖 Generated with Claude Code
- Lenguaje dominante
- C++
- Estrellas
- 1
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NorthernWidget/Okapi_Library
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
NorthernWidget/Okapi_Library#10 · 1 comentario ·
Todos los issues de NorthernWidget/Okapi_Library
Issues similares
-
audit(c2): add_project_arguments('/experimental:c11atomics', language: ['c', 'cpp']) for MS (C2-13)Abiertohygiene type:refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
OMPI 5.0.x CI builds failingAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
sandialabs/Fenix#172 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
rocketride-org/rocketride-server#2886 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
scp-fs2open/fs2open.github.com#7953 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
SteveMacenski/slam_toolbox#907 ·