new member - Hello from Bothell, WA, USA - CAN data logging

by **yosemitesammy217** » Mon Nov 11, 2013 7:31 pm

Hi all

My name is Sam. I'm in Bothell, WA, USA. Im a network engineer by trade, running some large (massive) networks for a large company in the area.

Anyway, as a network dude I have become interested in capturing and decoding the CAN networks in my Chrysler LX platform (2006 Dodge Charger SRT8), and am now looking around for information on the PCM and TCM in these, as well as references to KWP2000 protocol which is apparently used to communicate to the ECUs and tell them to downlaod a new firmware image, reset TCM adaptation etc.

After various stops and starts with Raspberry Pi (an old ARM architecture), Cubieboard and Hackberry A10 (Allwinner A10-based boards ARM boards), mBed and Arduino microcontrollers, I have built a CAN data logger from a Beagle Bone Black single board computer running Linux (Ubuntu 13.10), which is an 1 Ghz ARM Cortex A8 with 512 MB ram. It is about the size of a mint tin, cost about $45 + a 3 channel CAN expansion board ("cape" in Beagle-speak) from Italy which was $79 euro + shipping.

I have set these up with SocketCAN and can-utils, presently have this wired into the CAN C bus and now am able to log all the data off the C bus. I have some issues to work through (permanent under-dash mount, regulated 5V DC power from the 13.2VDC in the car, and then a system of scripting to start and stop captures, roll the data log files and compress and upload when in range of home wifi), but I have made good progress recently with logging all the data off the CAN C bus and starting to decode the messages. I have captured a TCM adaptation reset of the TCM, a download of a new program of data into the PCM, and some other programmer commands.

Looking for information about the LX platform TCM and PCM ECUs, the underlying computer architectures, and protocols, for further understanding of the systems and decoding of the messages.

Pointers to open (free) sources of information on ISO14230 and KWP2000 would be greatly appreciated.

Sam
http://the8thlayerof.net - my blog and project notes

by **ludvik** » Wed Jan 22, 2014 7:22 pm

Hi!

Very interesting post! Did you manage to connect your board to OBD II connector?

Best regards,
Ludvik

by **ludvik** » Wed Jan 29, 2014 7:46 pm

Hi again!

I'll try to be a little more specific :).

You've mentioned MCP2515DB-BM board(s) on your blog. My question is: did you manage to connect that board to OBD-II connector? I assume you need to connect only CAN-Hi, CAN-Low and Signal ground since the board is already powered via USB?

Best regards,
Ludvik

by **whereisit** » Thu Jan 30, 2014 5:03 am

I'm going to guess that you are right about what needs to be connected. Otherwise you'd have to remove a CAN device in the circuit and provide a dummy signal for it in order to monitor the CAN network. (so long as you do not remove one of the gateways)

by **ludvik** » Wed Feb 26, 2014 6:39 pm

Hi everyone!

Now I am able to confirm that aforementioned method of connecting diagnostic board to OBD-II connector of the vehicle (can-H to can-H, can-L to can-L and GND to signal ground) indeed works :). I was able to get some traffic from my Hyundai i30 (see attached image - MCP2515 Bus Monitor unfortunately does not offer copy/paste).

Regards,
Ludvik