Detect a silent CAN bus and mark the state as stale
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- embedded-iot
Research direction
Start with the design and open questions in issue #11, then read contracts issue #20 for the freshness definition. The issue calls for logging sleep and wake behavior, tracking the last matching CAN frame, and handling heartbeat and awake-only values after N seconds without frames. Done means those behaviors are implemented and checked against the observed bus traffic; the timeout value and design details need clarification.
Written by the indexing model from the issue text.
Description
Part of https://github.com/OpenCarControls/firmware/issues/11, which has the design and open questions.
- Record a log of the car falling asleep and waking up, and check what it sends.
- Track the last matching frame and send freshness as defined in https://github.com/OpenCarControls/contracts/issues/20.
- Stop or flag the heartbeat after N seconds without frames, and clear values that only make sense while awake.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 14h 32m
- Merged PRs (30d)
- 21
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 OpenCarControls/firmware
-
e-gmp enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenCarControls/firmware#75 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenCarControls/firmware#74 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenCarControls/firmware#73 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
OpenCarControls/firmware#72 ·
Maintainers usually reply within 1 day
-
e-gmp enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenCarControls/firmware#71 ·
Maintainers usually reply within 1 day
All issues in OpenCarControls/firmware
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
haowjy/mars-agents#228 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
redlib-org/redlib#604 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dividebysandwich/rust-dos#240 ·
Maintainers usually reply within 1 day
-
A-UI C-Bug S-Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bevyengine/bevy#26330 ·
Maintainers usually reply within 2 days