meatpiHQ / wican-fw

GNU General Public License v3.0
309 stars 65 forks source link

No data using SavvyCAN but ELM327 does work #60

Open WiCanIsCool opened 1 year ago

WiCanIsCool commented 1 year ago

I have an Audi A3 8Y 2022 and I'm trying to read the CAN bus data.

Yesterday I received my WiCan OBD but I'm having trouble sniffing using savvycan. When I use the ELM327 protocol and connect Car Scanner Android app it can read most of the sensors which tells me the can bus communication actually works. It seems to be at 500000 baudrate.

When I try protocol savvycan and connect from my Linux laptop I simply don't receive any data in the sniffer. In the connection window everything seems alright because I can see serial communication going back and forth.

After googling a bit I found posts about the CAN bus needing a kind of wake up signal. I think savvycan does not do this but Car Scanner Android app seems to do something like that.

I also enabled the monitor in the webui of the WiCan to maybe find the wakeup signal data Car Scanner uses but it's quite difficult to figure out what is what.

Here is some info about the ECUs from Car Scanner.

OBD-II
ECU protocol: 6) ISO 15765-4 CAN (11 bit ID, 500 kbaud)
ECU address/CAN Id: 7E8
ECU name:  _
Calibration ID: 05C
In-use Performance Tracking for spark ignition engines: OBD Monitoring Conditions Encountered Counts: 50505

ECU address/CAN Id: 7E9
Calibration ID: 0CW
In-use Performance Tracking for spark ignition engines: OBD Monitoring Conditions Encountered Counts: 64482

Also in the Car Scanner app settings I found an advanced setting to override the ECU initialization mode. Which default seems to do the following:

ATZ
ATE0
ATH1
ATSP0
ATS0
ATM0
ATAT1
meatpiHQ commented 1 year ago

@WiCanIsCool

Some cars don't expose their internal CAN bus on the OBD connector, I think that is the case with your car. When you use car scanner, you're using the OBD2 protocol, which is a request response protocol. If you want to try it on SavvyCAN you need to send the request manually then you'll see the response message.

Here are some information about OBD2 protocol and PID request: https://en.wikipedia.org/wiki/OBD-II_PIDs https://www.csselectronics.com/pages/obd2-pid-table-on-board-diagnostics-j1979