Live CAN health

Open
  • Is something wrong?
#22 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend, frontend, observability

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Python
Stars
0
Forks
1
Avg merge
18h 37m
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IgniteRobotics/flashpoint

All issues in IgniteRobotics/flashpoint

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.