P4Au
Newbie
Karma: +0/-0
 Offline
Posts: 5
|
 |
« on: April 07, 2013, 07:19:53 AM »
|
|
|
I join this forum about a month ago and learned a lot. (thanks)
My name is Patrick. I am studying electronics engineering and previously done computer programming in C, C++/Aka (Microsoft Foundation Class...MFC), Some assembly language (not real mode), and Java.
I also do all work on my personal cars. (From changing clutch to rebuilding engines)
Because of my background in electronics, fuel injection is all I know. While I know how diesel engines and its almost pure mechanical aspect work, I know nothing about carburetor fuel delivery cars. (don't care to know either)
I am not here to learn how to tune cars...I will leave that to the guys that have the time, skills, and patience to deal with that subject. As we all know, flashing is not tuning... Even thou if told what parameters to adjust and by how much, its still an experiment issue with the possibility of a few things that can go wrong, either immediately or overtime.
Both of my cars are chipped by the way so I am not conservative there.
ONE:
What I am interested in is the memory map layout of the bin files. From what I understand it all depends on what model of AMD EPROM chip the ECU or cluster contain. What location can I find certain data (eg. VIN, SKC, Mileage, Engine Code, etc.) The thought process is to create a software, (NOT simple command line, but Windows or Android versions that will read in bin files and display info...of major interest is the SKC. As read here in the forum, the SkC is coded in hexadecimal (as is everything else in a hex editor) but need to be rotated then add a zero before it. (Thanks DDillenger) Things like this is easy as ABC in programming and one can take advantage of this fact to present the data to the user in a structured or intended English-like form.
Of course I can create a program that chop up/encrypt my data and store them in multiple places, coded or un-coded. I would be the only one who know how to decode this data. (can be figured out with the right tools and skills) The point is, this is what we are faced with and EPROMs contain several different software coding and schemes.
My interest at the moment is ME7xx since this is what I have at my disposal. ME7.1.1 (T box) to be exact. In reality, if a software is to be created it should cover all ME7xx.
TWO:
Calculation of checksums is another.
And yes, I have a bench top setup for both cluster and ECU. This way I can pull my own files. Also VAG-KKL interface, Original VAG-KEY-USB interface, and Galletto 1260 interface. Will get a KWP2000 later.
THREE:
Data logging in OBDII
|
