hardbyte / hardbyte/python-can
SocketCAN Kvaser no response
- Lingua principale
- Python
- Stelle
- 1.6k
- Fork
- 697
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Hello,
I am trying to communicate with a device over CAN using python-can. I have been able to successfully establish communication in both directions on Windows (using Kvaser's canlib) and am trying to do the same on Linux (Ubuntu 18.04) with python-can.
The messages I'm sending have the correct arbitration IDs and I'm not using CAN FD.
` bus = can.interface.Bus(bustype='socketcan', channel='can0', bitrate=500000, receive_own_messages=True)
`
Some additional information is that when using 'kvaser', it says that my device is not found. I suspect that could've been part of the issue, and I also do not know how to fix this. However, when I run the same program on Windows and the device IS found, there is still no bidirectional communication. (The success with Windows was a result of using Kvaser's canlib, apparently.)
Using can.logger, I can see my messages supposedly getting sent out properly, but I am not receiving any of the expected messages back. Any thoughts/ways I could troubleshoot this? Thanks in advance!
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start with the can.interface.Bus configuration for the socketcan and kvaser backends, then use can.logger while reproducing the Ubuntu 18.04 and Windows cases. Compare the reported device discovery and bidirectional message behavior; the investigation is complete when the communication failure is isolated to a backend or setup issue.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- linux, python, ubuntu
- Ambito
- networking
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100