Live CAN health

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, frontend, observability

Línea de trabajo

Start with the proposed live-can-health change in openspec/changes/live-can-health and read its proposal, spec, design, and tasks. The scope spans a robot-side NetworkTables contract, a live service in flashpoint serve, a CAN health view, and a Python fake robot, and depends on two private issues plus a separate Robot-2026 publisher PR. Check the OpenSpec validation command; done means the contract, guide page, suggested Java sample, and specified tests are complete.

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

Descripción

roadmap

Size: M · Depends on: IgniteRobotics/flashpoint-private#71, IgniteRobotics/flashpoint-private#74 · OpenSpec: live-can-health (archived 2026-11-01)

Status

Update 2026-11-01: merged (PR #35) and archived (PR #41), 22/23 tasks. Spec synced to openspec/specs/live-can-health. Only 7.3 [HUMAN] (pit check with the Robot-2026 publisher deployed) is open, tracked in #13. Close this once it passes.

Status: proposed 2026-10-19. Proposal, spec, design and tasks are written and validate (openspec validate live-can-health --strict).

  • Needs a Robot-2026 PR for the publisher (to be filed separately). This repo carries only the contract, a guide page and a suggested Java sample.
  • Split out of IgniteRobotics/flashpoint#18 (Live & Pit views). The Pit board can consume it later.

Scope

  • Change: live-can-health.
  • What it adds:
    • a robot-side contract: robot code publishes running totals per CTRE device over NetworkTables under /Flashpoint/Live/CANHealth/ (dropouts = loops where the watched status signal is older than 2.5× its update period, worst signal age, resets, fault bits, lowest supply voltage), plus bus status, Enabled and a contract version. Totals, so a 40 ms dropout still counts over a ~100 ms NT link;
    • a live service in flashpoint serve: one NT connection (opened only while a view is open), compares each update with the last to make events (dropout, reboot, fault, bus errors, restart), maps devices to slots through the robot config, and applies the can-health sibling rule (isolated vs bus-wide);
    • a Live CAN view: device grid by bus and slot (ok / dropped / rebooted / faulted / disconnected / missing / unmapped), event log, and in-browser marks ("now wiggling: FL module");
    • a Python fake robot that publishes the contract, for tests and for working without a robot.
  • Both test styles, no mode switch: every event is tagged enabled (drive test) or disabled (shake test).
  • Non-goals: nothing written to the lake (marks and events live in the browser only); the Pit board and its verdict (#18); reading the bus when robot code isn't running (Phoenix diagnostics server dropped); non-CTRE devices; chain-order localisation.
  • New dependency: robotpy-ntcore (2026 line). ADR-0016 will amend ADR-0013 for the outbound robot connection.
Lenguaje dominante
Python
Estrellas
0
Forks
1
Merge medio
18 h 37 min
PR fusionados (30 d)
15

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 IgniteRobotics/flashpoint

Todos los issues de IgniteRobotics/flashpoint

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.