I may be more knowledgeable then the average person when it comes to computers, but I do not have a clue what to do with the stuff you posted. I know what the Binary and Hexadecimal number system is, but when you say things like "streams a decimal + 1", I have no clue what that means.
1. Do I just copy and paste this stuff to a Word document?
2. Since this is code it has to be run through a compiler to get output...what compiler would that be?
3. Currently I have no computers running any kind of Linux OS. Can any of this stuff be run on Windows, or a DOS Command Prompt?
Ugh - those two .DS files don't format right within a web browser - all the line returns are gone (I guess because the browser is looking for HTML).
So I can see your questioning on that ... I will convert those two to plain text files and try re-post them tonight.
Or ... it appears that gearhead-efi has a direct link to all of them, along with the zipfile. You may want to grab the zipfile, and then open up the A138.DS in something like Wordpad so the ^M (carriage returns) can be seen.
http://gearhead-efi.com/gearhead-efi/def/aldl/ALDLstuff.zip
http://gearhead-efi.com/gearhead-efi/def/aldl/
Regardless, those two .DS files are just for reference and they are not used in the compiling nor running of the aldl-io program. They just list out the datastreams that are available from the ECM.
The only "code" that needs to be compiled would be the aldl-io, and there should be a README type file listing it out. Maybe as simple as a "make install" when you have the .tar archive file extracted.
All the conf files are readin when the program starts up.
I am not 100% sure if aldl-io is portable to Windows. While aldl-io is written in C, and there are C compilers for Windows - there maybe libraries and references that you will had to get and/or alter to make it work.
Its been a number of years since I did any real C programming to make a comment if it would run on Windows. I don't want to tell you what to do, but you may just want to wait until you get a Raspberry PI and do the work on that.
You may spend more time getting it work in Windows that what you want to be using as end result.
With the hex vs decimal question, if you look at my specific config file, you will see that I am referencing the datastreams as hex. For example, for the RPM:
D2.OFFSET=0x21
D2.NAME=RPM
D2.DESC="ENGINE RPM"
D2.UOM=RPM
D2.TYPE=FLOAT
D2.MULTIPLIER=25
D2.LOG=1
D2.DISPLAY=1
D2.MIN=0 D2.MAX=6375
The D2.OFFSET line is the datastream address. If you convert that hex, 0x21, to a decimal, you will get "33". Well, the RPM defined in the A138.DS file has it at address "34". That is what I was saying the .DS file has everything off by one.
I think the reference file just starts at 1, where in reality (what the ECM expects) is one less .. meaning the file should have started at 0.
I wouldn't let that throw you - if there is a datastream that you want to see, just work backwards from the file ... minus the value by 1 and then convert to hex. Example, see the knock sensor count:
47 PA2OLD KNOCK SENSOR COUNTER (MSB)^M
N = COUNT
File has it at "47". I would then substract 1 from 47, then convert that 46 to hex - which would be "2e". Does that make sense?
Sorry that the .DS files don't format right for your viewing. I will PM you my cell number if you want to chat more about this.
-graham
