Implement the charge port command
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
- rust
- Domain
- embedded-iot
Research direction
Start with cars/egmp/src/lib.rs and the existing ChargePortCommand, then review the SavvyCAN logger and firmware#22 reference for the car’s frames. Add the captured frames to dbc/m-can.dbc in contracts and send them from the firmware, ensuring sending is gated by read-only mode and the car check. Done means the command opens and closes the charge port using the captured frames and respects both checks.
Written by the indexing model from the issue text.
Description
Open and close the charge port door (ChargePortCommand). It currently returns "Not implemented" (cars/egmp/src/lib.rs).
Capture the frames the car sends when this is done from the car itself (SavvyCAN logger, firmware#22), add them to dbc/m-can.dbc in contracts, then send them from the firmware.
Only send while read-only is off and the car identity check passes.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
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
-
Refresh stale docsOpen
Difficulty 1/5 1-3 hours Newbie friendliness 67/100
OpenCarControls/firmware#35 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
OpenCarControls/firmware#34 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenCarControls/firmware#31 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
OpenCarControls/firmware#30 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
OpenCarControls/firmware#57 ·
Maintainers usually reply within 1 day
All issues in OpenCarControls/firmware
Similar issues
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
cssparser-color: debug assertion in hsl_to_rgb for a hue that overflows f32Possibly taken @BartWaardenburg claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
servo/rust-cssparser#460 ·
-
`-w -r <range>` fails empty range but changed working treePossibly taken @dajiaohuang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days