Proposal: add TestBaseVCI support to python-can

Abierto

#2,043 abierto el 1/4/2026 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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: Necesita aclaración
Estado de actividad: Tranquilo
Stack tecnológico: python
Área: embedded-iot, networking

Línea de trabajo

Comienza revisando el backend hrcan existente y distribuido por separado, así como HRCANBus; después, inspecciona el punto de entrada can.interfaces.BACKENDS utilizado para el registro. Confirma cómo encajan las suposiciones del SDK TestBaseVCI y del controlador con python-can, y establece que el adaptador propuesto admite CAN/CAN FD sin afectar a los usuarios de otros dispositivos.

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

Descripción

enhancement

Hi maintainers,

We are a company that develops CAN bus communication and simulation products, and I'd like to ask whether support for our TestBaseVCI CAN / CAN FD hardware could be accepted in python-can.

We already have a working backend for it, and it has been used for quite a while as a separately distributed extension. The current backend name is hrcan, with bus class HRCANBus.

Current status:

supports classic CAN and CAN FD
has been used in practice for a long time
currently installed manually by copying files into the Python environment and registering it in can.interfaces.BACKENDS

Environment:

Windows 10 / 11
Ubuntu 20 / 22
64-bit Python
TestBaseVCI driver >= 2.4.1
currently used with python-can 4.5.0

Supported features:

start CAN / CAN FD channels with different bus parameters
send / receive single frames
periodic transmission, with manual and logger-based receive flows
multi-device support
multi-process support
unified timestamp behavior

A few notes before I prepare a PR:

I will only submit the Python-layer adapter code to python-can
if a user wants to use our hardware but has not installed the SDK / device driver, I can provide a public SDK download link and a clear text reminder
I will make sure that if users do not use our device, this support will not affect any existing python-can functionality

If this direction looks okay, I'm happy to clean it up and prepare a PR. I'd also appreciate any suggestions before I start.

Thanks.