Evo X Real CAN Packets
Evo X Real CAN Packets
This is just a start, but I have logging the real can traffic on the x's bus, and have started to find some matching channels, this is for the 55571006, but sure the scheme is close for the 2008's as well.
I have a list of about 10 more packets that I have found, just not on this local comp right now, I will update with more that I find
TX Packets from ECU
RX Packets from rest of Car
I have a list of about 10 more packets that I have found, just not on this local comp right now, I will update with more that I find
Code:
id sb len type scale offset name 0x308 1 2 u16 1 0 RPM 0x312 2 2 u16 ??? 0x312 4 2 u16 ??? 0x415 0 0 u8 ac swtich (0x10) 0x608 0 1 u8 ECT 0x608 6 2 u16 ??? 0x210 0 2 u16 0.00114 13.37 TPS_AN 0x210 2 2 u16 ??? 0x212 0 2 u16 1 0 IDLE_RPM_TARGET 0x212 2 2 u16 ??? 0x356 4 2 u16 ??? 0x380 1 1 u8 Brake/Clutch???
Code:
Can ID Hex ID In rom TX Slot DLC Ret Func TX Store 100 400 81d1e 18 4 C 811674 101 401 81d1c 17 1 C 811673 210 810 81d1a 16 8 C 81166B 212 812 81d18 15 8 C 811663 255 915 81d16 14 8 C 81165B 308 C08 81d14 13 8 C 811653 309 C09 81d12 12 7 C 81164C 312 C12 81d10 11 8 C 811644 356 D16 81d0e 10 7 C 81163D 380 E00 81d0c 9 2 C 81163B 415 1015 81d0a 8 7 C 811634 4a0 1220 81d08 7 8 C 81162C 590 1610 81d06 6 4 C 811628 608 1808 81d04 5 8 C 811620 6fa 1B3A 81d02 4 8 C 811618 6fe 1B3E 81d00 3 8 C 811610 7bc 1E3C 81cfe 2 8 C 811608 631 1831 81cfc 1 8 B 811BD4 7e8 1F28 81fca 0 8 A 811Bcc
Code:
Can ID Hex ID In rom Rx DLC 110 410 82a4e 27 4 111 411 82a4c 26 8 208 808 82a4a 25 8 215 815 82a48 24 8 218 818 82a46 23 4 248 908 82a44 22 4 265 925 82a42 21 7 2f1 B31 82a40 20 7 300 C00 82a3e 19 6 315 C15 82a3c 18 5 316 C16 82a3a 17 8 318 C18 82a38 16 8 325 C25 82a36 15 6 338 C38 82a34 14 6 365 D25 82a32 13 7 408 1008 82a30 12 6 412 1012 82a2e 11 6 418 1018 82a2c 10 1 428 1028 82a2a 9 8 520 1420 82a28 8 7 591 1611 82a26 7 8 5fe 173E 82a24 6 7 6fb 1B3B 82a22 5 2 6fd 1B3D 82a20 4 3 6ff 1B3F 82a1e 3 1 7df 1F1F 82a1c 2 8 7e0 1F20 82a1a 1 0 630 1830 82a18 0 8
Last edited by hpd_wally; Apr 24, 2011 at 09:53 PM.
Canusb.com. USB dongle. I had to write an app for it in qt. The c interface library is the only one that supports interrupt based message reception. If you used a managed framework (c#) you gave to poll
It's quickest to log packed binary data and open it with atlas or matlab. Your choice really. I logged tandem with the tactrix setup to help correlate the data to known measurements
It's quickest to log packed binary data and open it with atlas or matlab. Your choice really. I logged tandem with the tactrix setup to help correlate the data to known measurements
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Nice gadget, but for little more money you can get a better solution.
Interesting product but I assume that it does not have a phy and cannot actually send messages on the bus and interact with anything else. The canusb device is *****en because its cost sensitive and has an API that you can integrate into lab view. Matlab c# qt vb and others. This thing has been used in much that I do at work
I haven't gone through code for the 9's yet, but could probably try the same method. The key is that the M32R packs the can id in a funky format for the can structure (ie 0x100 is shown in code as 0x400 from the bit rolling and shifting that the hardware nativly wants to see).
Are you going to be running any Nasa events in the next month? I should be up @ button willow in a few weeks with some guys at work. Send me your rom and xml files, and I can open it in IDA and see if they have retained some of the same can spec.
Are you going to be running any Nasa events in the next month? I should be up @ button willow in a few weeks with some guys at work. Send me your rom and xml files, and I can open it in IDA and see if they have retained some of the same can spec.
Trending Topics
I haven't gone through code for the 9's yet, but could probably try the same method. The key is that the M32R packs the can id in a funky format for the can structure (ie 0x100 is shown in code as 0x400 from the bit rolling and shifting that the hardware nativly wants to see).
Are you going to be running any Nasa events in the next month? I should be up @ button willow in a few weeks with some guys at work. Send me your rom and xml files, and I can open it in IDA and see if they have retained some of the same can spec.
Are you going to be running any Nasa events in the next month? I should be up @ button willow in a few weeks with some guys at work. Send me your rom and xml files, and I can open it in IDA and see if they have retained some of the same can spec.
I was actually asking for the Evo 10 / RA
The 8/9 are not CAN based.
if you want to sniff the CANBUS you can do it with an OP20 - Colby includes a packet sniffer - you just need to compile it.
you will need to connect directly to the bus thou and not to the OBD connector as that is proxied via ETACS...
you will need to connect directly to the bus thou and not to the OBD connector as that is proxied via ETACS...







