Using the raspi is better for me I think because I can leave it powered up to the bench E67 all the time allowing me to SSH into it to mess around. I can even use a gpio pin to toggle the ignition power with relay if I need to. There's also a crapload of Linux libraries already out there to decode this. thats my next step, running this through log analyzer to see what I get.
Very cool. I'm glad your doing e67. That's what I have too and have always wanted to do similar to what you're doing. I'll be following your progress with great interest, and most likely forking your work if you choose to make your tools public .
I'm not sure if you've been given or found this document but it may help you out when it comes time to start writing code to interact with the ECM.
hjtrbo wrote:Very cool. I'm glad your doing e67. That's what I have too and have always wanted to do similar to what you're doing. I'll be following your progress with great interest, and most likely forking your work if you choose to make your tools public .
I'm not sure if you've been given or found this document but it may help you out when it comes time to start writing code to interact with the ECM.
Thanks! I do have that file and it appears to have useful info although I haven't absorbed any of it yet.
I think tonight I'm gonna log the bus activity during an HP tuners "read entire" with the idle messages filtered out and see what I get. That should get me something to run through the decoder databases I found to identify traffic. I found something called SavvyCan that can load specific databases and decode log based on values already discovered by community. That's the idea anyway.
A cool thing I can do on the raspberry pi is play back a log file to the can bus. I'm assuming I'll need to sift through the log and see where the ECU is responding or requesting feedback and eliminate those messages. Regardless it hopefully should help shed light on some operations going on , on the bus during a read.
I didn't license this ECU on hpt yet because I want to try to get vin changed first because I'm pretty sure hpt won't let me change it to a 2004 p59 vin. Plus the fact that it'll cost me $200 in credits. One credit for the current ECU vin and one for new vin. I'm okay with burning one credit on this but not two.
A much better way to spend $200 cash is to get a MDI clone. It will be your ultimate tool for playing around with CAN pcms. And it will allow you to do much more that you can imagine.
kur4o wrote:A much better way to spend $200 cash is to get a MDI clone. It will be your ultimate tool for playing around with CAN pcms. And it will allow you to do much more that you can imagine.
Hey wait, wouldn't the one I just purchased a couple months ago work?
OBDX Pro VX Key Features 1.8m (~6ft) USB Cable
Supports USB, Bluetooth and Wifi connections
Capable of Advanced Diagnostics or Tuning when used with supporting software
Supported by LS Droid & PCM Hammer
Supports 4x high-speed programming
Read & clear ‘Check Engine’ light using free applications
Supports ELM327 OBD2 Applications(Windows PC, Android & IOS) Supports J2534 programming
Free firmware updates
Meistro wrote:Hey wait, wouldn't the one I just purchased a couple months ago work?
OBDX Pro VX Key Features 1.8m (~6ft) USB Cable
Supports USB, Bluetooth and Wifi connections
Capable of Advanced Diagnostics or Tuning when used with supporting software
Supported by LS Droid & PCM Hammer
Supports 4x high-speed programming
Read & clear ‘Check Engine’ light using free applications
Supports ELM327 OBD2 Applications(Windows PC, Android & IOS) Supports J2534 programming
Free firmware updates
Yeah, that should work, Tazzi here is the developer of that device.. I haven't bought one yet, mainly only because I have too many mdi's to need one, lol.. You could try Powerpcm and see if it sees it, I do believe you'd need to point powerpcm to the j2534 dll that the OBDX pro VX uses though, it's not so user friendly but there is a drop down for the J2534 driver location.. viewtopic.php?f=3&t=6666&hilit=e38+powerpcm