Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Implement the charge port command

Open
#38 0 comments 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
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

e-gmp

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

Open in Codespaces

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

  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 OpenCarControls/firmware

All issues in OpenCarControls/firmware

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.