NefMoto > Technical > Reverse Engineering > EDC16 Can Bus data bytes 0x280 etc
Pages: [1]
« previous next »
Author Topic: EDC16 Can Bus data bytes 0x280 etc  (Read 8213 times)
Keith-i
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 14
« on: September 21, 2019, 01:17:51 PM »
I have a VW-Marine 3.0Tdi in my boat which sends data to the multifunction tacho over can bus. I'm trying to read some of that data to get it onto  a different display unit via Arduino. I've sniffed the can bus and can see a repeating stream of data packets including 0x280, 0x288 etc. I've worked out some of the bytes I'm interested in such as rpm and coolant temp but there is data showing which isn't referenced anywhere that I can find on the net. The best resource was the Bosch EDC15 FR but it doesn't document all of the available information that my EDC16 is spewing out.

For example, I know that:
0x588 byte 2 is Elev info (don't know factor or offset)
0x288 byte 1 is coolant temp
0x280 byte 2 & 3 is rpm
0x480 byte 2 & 3 is fuel consumption

What I need help on is:
0x588 byte 4
0x480 byte 7

Any help would be appreciated.
Logged
fknbrkn
Hero Member
*****

Karma: +186/-24
Offline Offline

Posts: 1455


mk4 1.8T AUM
« Reply #1 on: September 21, 2019, 01:30:19 PM »
me7 funktionzrahmen
CAN
Logged
Keith-i
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 14
« Reply #2 on: September 22, 2019, 01:38:29 AM »
Superb, thanks.
Logged
jochen_145
Full Member
***

Karma: +9/-4
Offline Offline

Posts: 177
« Reply #3 on: September 22, 2019, 02:12:25 AM »
Quote from: fukenbroken on September 21, 2019, 01:30:19 PM
me7 funktionzrahmen
CAN

Becareful:
ME7 is PQ34, EDC16 starts in PQ35. CAN base differs in some signal compared to PQ34!

Quote
The best resource was the Bosch EDC15 FR but it doesn't document all of the available information that my EDC16 is spewing out.
This is the problem:
Best source of EDC16 is EDC16FR, not EDC15.. 3.0Tdi is CR, so at least you have to search for a EDC16 Cx FR for commonrail variant.
AFAIR there are wandering a few out there in net meanwhile.

FYI:

0x588, byte4 -> charge air pressure, if supported
0x480, byte 7 -> checksumm
Logged
Keith-i
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 14
« Reply #4 on: September 22, 2019, 10:34:10 AM »
Thanks jochen

I think I'm almost there with identifying the relevant unknown data bytes. Between the EDC15 and ME7 documents I have found the description of the data bytes tallies with the actual data I'm receiving. I was hoping to find oil temperature and pressure in there somewhere but that doesn't seem to be on the can bus from my ECU.
Logged
jochen_145
Full Member
***

Karma: +9/-4
Offline Offline

Posts: 177
« Reply #5 on: September 22, 2019, 01:05:28 PM »
It is, but not in ME7 DBC..

You have to look for EDC16 specific FR
Logged
Keith-i
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 14
« Reply #6 on: September 25, 2019, 01:49:26 PM »
Ok, thanks. I've pulled a blank so far in trying to find an EDC16 FR on line that details what each byte in each message relates to. If you have any pointers that would be great.
Logged
gremlin
Hero Member
*****

Karma: +196/-9
Offline Offline

Posts: 654
« Reply #7 on: September 25, 2019, 09:12:09 PM »
Quote from: Keith-i on September 25, 2019, 01:49:26 PM
Ok, thanks. I've pulled a blank so far in trying to find an EDC16 FR on line that details what each byte in each message relates to. If you have any pointers that would be great.

To discover exact CAN-version of your EDC16 ECU you must find in dump FrmMng_stCANVer_C parameter.
There are many versions of CAN framing 3.xx, 4.xx, 5.xx etc. and the same bit in frame may carry different meanings.
As example see attached doc for CAN version 4.23

Logged
Keith-i
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 14
« Reply #8 on: September 26, 2019, 04:04:36 AM »
Much appreciated gremlin. Thanks for the pdf too.
Logged
Keith-i
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 14
« Reply #9 on: September 27, 2019, 01:24:13 PM »
Using gremlin's pdf I have deduced that byte 1 of 0x288 contains the can version. This results in 0x2D for my engine which is not listed in the table of can versions in the v4.2.3 pdf. It must therefore be a later version. Does anyone know what can version this is or have a later can data pdf that might help? My engine is MY 2005 so a pdf from that era might help.
Logged
gremlin
Hero Member
*****

Karma: +196/-9
Offline Offline

Posts: 654
« Reply #10 on: September 28, 2019, 08:30:04 PM »
Quote from: Keith-i on September 27, 2019, 01:24:13 PM
This results in 0x2D for my engine which is not listed in the table of can versions in the v4.2.3 pdf.

It's version V4.7.7 used in Audi/C6 ECU row.
Closest to this version i can found in my archives is 4.9.7 (dbc-file, CAN-header ID's are in decimal)
HTH.
Logged
gremlin
Hero Member
*****

Karma: +196/-9
Offline Offline

Posts: 654
« Reply #11 on: September 28, 2019, 08:41:46 PM »
Another one frame manager description taken from FR for EDC16CP34 approx. 2005 year.
Logged
Keith-i
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 14
« Reply #12 on: September 30, 2019, 05:31:15 AM »
Really appreciate your help, thank you gremlin.
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 27, 2024, 12:33:17 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.019 seconds with 17 queries. (Pretty URLs adds 0s, 0q)