I found it in the beta version of EcuFlash Here

 

Not sure if this applies to our hardware very well, but it's interesting none the less:
http://www.wire2wire.org/Can_sniffer/Can_sniffer.html

some results based on using this with a VW:
http://translate.google.com/translat...n-confort.html

Using an Arduino plus the can sniffer to sniff messages of interest and insert new messages based on what was observed (sort of like a piggyback):
http://secuduino.blogspot.com/2011/0...an-bus-ii.html

 

Thanks a lot. Very useful information.

 

Thanks for the link. But have you or anyone else been able to get it to work? I've tried numerous times after compiling the code to log the CAN Bus and only managed once to get a little data. I've never dealt much with reverse engineering, so I just wanted to start with some easy stuff logging through the OBD2 port and work my way up to more complex messages by taping directly into the ecu's CAN Bus wires. Maybe its just that the ETACS gateway blocks most of the CAN messages but I doubt it. Below is the only info I managed to log:

I'm still trying to read through and fully understand the code, so I don't yet even know how to begin interpreting this data. I suspect the [xxxxxxxxxx] is a timestamp, but I'm unsure of what part of the remaining message is the ID and what is the data? I'm also still trying to learn about how CAN messages work in general, but to my understanding there is an 11bit identifier followed by up to 8 bytes of data, but the data I logged has more bytes than this so I am confused a little.

Edit: ok I just found the message structure in the code and found I was correct about the timestamp but the rest of the log is data (no IDs were logged, I just added that to the code). After a little more testing, the 05 *might* also represent the ID, however I'm not positive on that (just that when I added the code to log the ID's it was also 5...so maybe they are the same). After a lot of testing I was finally able to replicate my previous log by using ecuflash to read the ECU's ROM, and then after it finished immediately running the can logger. I'm starting to think that maybe the ETAC doesn't allow CAN messages through unless requested from whatever is connected to the OBD2 (and since I'm just sniffing, nothing is getting through).

 

No.
00 00 05 3B is the ID
03 is the length
7F 29 80 is the data message, 7F being an error return, 29 being the request, and 80 being the error code

 

Ok, that makes sense. But why do you think when I print the msg->ProtocolID I get only 5 and not the 53B?

Also do you know why I don't see more messages when logging CAN through the OBD? I'm wondering if the ETACS is blocking all data to the OBD2 unless a request is made from the OBD2 (and since I am not making request, just listening, I'm not logging anything)?

 

ETACS is like a transparent proxy...

 

What would be the easiest (and cleanest) point to connect to the
CAN bus to bypass the ETACS "filtering"?

thanx

 

why do you want to?

 

well according to the meter diagram, there is some CAN signal going in...

http://www.youtube.com/watch?v=yQx7ZSYbd5o

see where I am trying to go?

Mart

 

i dont understand what you are attempting todo

 

1.- Get a good and long CAN bus log and try to figure stuff out.
2.- Figure out if any message are sent/understood by the meter.
3.- Send custom msg to the cluster.
4.- Display useful crap if possible.

Mart

 

well the meter is computer in its own right, it isn't really controlled by the rest of the ECU's in the car..

so your not going to be able to change what is displayed (other than substituting whats already being display with another value) without reprogramming it..

anyways if you get the wiring manual you will see there is a spare CANBUS connector behind the radio from memory...

 

Yes I am aware of all of that. I cannot do as much as I want with the meter.... however having a nice CAN BUS log during an MUT-III session can be fun....

Mart

 

Just curious

Is this the same as I do with my Racelogic Video Vbox?
I spliced into the can wires at the ECU and feed into the box so I can display throttle position, revs and boost on the recorded video. I would love to have something for the brake position too