roboRIO TalonFX status signals log at 4 Hz
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- data, observability
Research direction
The issue identifies rio-bus TalonFX signals and the SignalLogger/status-signal update frequency, but names no files or tests. Start by locating the robot-side SignalLogger and TalonFX status-signal configuration, then check the rio CAN bus utilisation budget. Done means current, voltage, and velocity are logged at a higher rate such as 50–100 Hz without exceeding that budget.
Written by the indexing model from the issue text.
Description
Found during the P4 spike (openspec change p4-views-and-reports).
Problem: the roboRIO-bus TalonFX status signals (supply/stator current, temperature, velocity) log at 4 Hz in the 2026 hoots; CANivore devices log at ~246 Hz. Rio slots (intake, indexer, flywheels, hood) therefore have one current sample every 250 ms.
Impact:
- current spikes between samples are invisible to Replay envelopes, stall detection, and gold P95s, whatever the downsampling;
- stall and brownout intervals on those slots are quantised to 0.25 s.
Replay shows a header note listing slots that log current slower than 20 Hz.
Ask (robot side): raise the SignalLogger / status-signal update frequency for rio-bus TalonFX current, voltage, and velocity (e.g. 50–100 Hz), within the rio CAN bus utilisation budget.
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IgniteRobotics/flashpoint
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
IgniteRobotics/flashpoint#45 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
IgniteRobotics/flashpoint#44 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
IgniteRobotics/flashpoint#43 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
IgniteRobotics/flashpoint#12 ·
Maintainers usually reply within 1 day
-
tools/update-owlet-manifest.py ignores --help and starts downloadingMay be free again @yoveneim claimed this 11 days ago, and no pull request is open. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
IgniteRobotics/flashpoint#11 · 1 comment ·
Maintainers usually reply within 1 day
All issues in IgniteRobotics/flashpoint
Similar issues
-
bump patch
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
autowarefoundation/autoware_carla_scenario#1321 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
QuantConnect/Documentation#2838 ·
Maintainers usually reply within 1 day
-
get_all_subclasses must deduplicate by class identityPossibly taken @Gambit-Checkmate claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 15 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
awslabs/route53-dynamic-dns-with-lambda#67 · 1 comment ·