Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Implement CAN logging with SavvyCAN's protocol

Abierto
  • ¿Algo no está bien?
#10 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
embedded-iot, networking

Línea de trabajo

Read the existing CAN debug implementation in core-interface/src/can_debug.rs and trace the board taps, MCP2515 debug mask switching, and publish_can_debug_task mentioned in the issue. Then identify the firmware entry points for vehicle tasks, client disconnects, and command/state queues. Done means SavvyCAN protocol logging sends CAN frames over Wi-Fi, handles disconnect and read-only behavior, validates bus IDs, and accounts for the listed legacy CAN debug path.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

We need a way to make it easy to reverse engineer CAN buses from the firmware itself. The idea is to implement SavvyCAN's network protocol and send CAN frames using Wifi. We may need to disable the normal vehicle tasks when using this.

There was already a CAN debug tool that was started to be implemented in the firmware, but it will be easier to just use SavvyCAN instead.

Notes from the audit (old BLE CAN debug, still in main)
  • Remove the old BLE CAN-debug path as part of this (or before):
    core-interface/src/can_debug.rs, CAN_DEBUG_RX_CHANNEL, the board taps,
    MCP2515 debug mask switching, and publish_can_debug_task. In contracts,
    mark SetCanDebugEnabled / UpdateCanDebugFilters / CanDebugUpdate
    [deprecated = true] (append-only rule).
    Until then it's reachable by any bonded phone: SetCanDebugEnabled with
    bus_id >= 8 panics with a shift overflow in debug builds
    (can_debug.rs:73, also :46). Release builds silently wrap.
  • Lessons for the new version:
    • Validate bus_id against MAX_CAN_BUSES / the configured bus count.
    • Turn logging off when the client disconnects (the old one stays on).
    • With "disable normal vehicle tasks", also force read-only on.
    • Keep logging traffic off the shared command/state queues.
Lenguaje dominante
Rust
Estrellas
1
Forks
0
Merge medio
13 h 37 min
PR fusionados (30 d)
8

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenCarControls/firmware

Todos los issues de OpenCarControls/firmware

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.