jeepguy553

Does anyone know which datastream definition was used for a 1990 Chev Caprice, 5.7L TBI (cop car), L05 engine? I have several candidates, but none seems to be just right. Here's a list:
A58
A106
A129
A41
A33
A35
This is really starting to get annoying. It seems like it is right there, but I just can't seem to get all of it in the right place at once.
TIA!!! Beers to all!!!

Grumpy

I would imagine, ie WAG, that if you ran edit and search for the data stream addresses, in the .bin they should match in the right Axx

RBob

iTrader: (1)

And the answer is. . .






























D) none of the above.

Use A090.

RBob.

Mangus

from the hac (by Robert Rauscher)

;-----------------------------------------------
; ALDL list
;-----------------------------------------------

;----------------------------
LD414: FDB $D002 ; 1. eprom id lsb
LD416: FDB $D003 ; 2. eprom id msb
;----------------------------
LD418: FDB $00FD ; 3. current IAC posit, (0-255)
; n = counts
;----------------------------
LD41A: FDB $0023 ; 4. coolant
; see table 1
;----------------------------
LD41C: FDB $0030 ; 5. mph,
; (mph/1)
;----------------------------
LD41E: FDB $002A ; 6. map, (a/d, 0-255)
; volts = n * .0196
;----------------------------
LD420: FDB $001B ; 7. rpm/25
; rpm = n * 25
;----------------------------
LD422: FDB $0042 ; 8. tps (a/d, 0-255)
; volts = n * .0196
;----------------------------
LD424: FDB $00A2 ; 9. integrator, (0-255)
;----------------------------
LD426: FDB $0039 ; 10. O2 (a/d), mvdc = 0.2304 * a/d val??
; mv = N * (1000/226) = N * 4.425??
;----------------------------
LD428: FDB $00E1 ; 11. error flag 1
;
; b7 error code 12 no drp
; b6 error code 13 oxygen sensor
; b5 error code 14 coolant sensor hi
; b4 error code 15 coolant sensor low
;
; b3 error code 21 tps high
; b2 error code 22 tps low
; b1 error code 23 iat sensor lo
; b0 error code 24 vss
;----------------------------
LD42A: FDB $00E2 ; 12. error flag 2
;
; b7 error code 25 iat sensor hi
; b6 error code 31 governor fail
; b5 error code 32 not used (egr)
; b4 error code 33 map sensor high
;
; b3 error code 34 map sensor low
; b2 error code 35 not used
; b1 error code 41 not used
; b0 error code 42 est monitor error
;----------------------------
LD42C: FDB $00E3 ; 13. error flg 3
;
; b7 error code 43 knock spark control failure
; b6 error code 44 O2 lean
; b5 error code 45 O2 rich
; b4 error code 51 prom error
;
; b3 error code 52 adu error, netres/RTS ovrrun
; b2 error code 53 vats
; b1 error code 54 fuel pump relay failure
; b0 error code 55 cal pack missing
;--------------------------------------
LD42E: FDB $000E ; 14. a/f mode word flag 1, (flag),
;
; b7 closed loop flag, 1 = closed loop
; b6 rich/lean flag, 1 = rich
; b5 closed loop flag, 1 = closed loop
; b4 async fuel flag
;
; b3 4-3 downshift for tcc unlock
; b2 low battery, 1 = low
; b1 blm enable flag, 1 = enable store
; b0 clear flood flag, 1 = cranked in c/flood
;--------------------------------------
LD430: FDB $0040 ; 15 battery volts, (a/d, 0-255) vbatt/10
;--------------------------------------
LD432: FDB $0801 ; 16. mcu2 i/o
;
; b7 air conditioner, 0 = a/c requested
; b6 p/s pressure switch
; b5 high gear, 0 = switch open
; b4 park neutral, 0 = drive
;
; b3 tcc/shift light
; b2 a/c
; b1 air divert
; b0 select
;--------------------------------------
LD434: FDB $0069 ; 17. PA3, counts of msb only
;--------------------------------------
LD436: FDB $00A1 ; 18. BLM, (blm/1)
;--------------------------------------
LD438: FDB $0024 ; 19. IAT, a/d
;----------------------------

jeepguy553

Assembly code just became useful...the light just came on!
Thanks guys!
BTW...I am already using A90, just having trouble with it somewhere. I am headed home right now to try to figure it out.

jeepguy553

Now I am at home and I think I may have figured it out.
In the Tuner Pro ALDL ADS Editor, there is a section called the ALDL Definition Header. Well, in that header data, there is a small, ever so easy to overlook field named "Payload Size" and it is given in BYTES. Looking at the hac and the A90 definition, it became clear to me that something was amiss here. The definition and the hac have 20 BYTES (or WORDS). The TunerPro definition header was set to 25 BYTES.
...I wonder if that could be the root cause of the whole problem...

Grumpy

And maybe how this applies source code wise?.
hint-hint.

jeepguy553

Well, Grumpy, I may not be the best at reading the code, but once I saw the hac, I realized that it was telling me which bits and words (bytes) were involved in transmitting the data to the receiving computer system.
FDB (speculation here) has something to do with loading a value from a particular byte. The byte is specified in the second pard of the command as a hex address. (i.e. $0041)
For the status words (flags), the hac breaks down the individual data words into individual bits...8 per word. Each bit serves as an on/off flag. If the bit =1, the flag is set.
Am I even close here?

Mangus

that would do it.

FDB means its a double byte value. FCB means its a single byte value. dont worry about that stuff. just look at the byte number ( numbered in the comments on each line) and the conversion information in the comments to create your ads file.

be careful how you use "word". in *almost* every applicaton (including this one and PC's), a word is 2 bytes (16 bits).

i'll be writing a tutorial on creating ecu and ads files. from hacs/templates.

jeepguy553

I'll be reading that tutorial as soon as it is out.
I'll watch my use of those terms. I'm learning more and more every day.
Thanks, guys!

jeepguy553

Okay,
I just tried the "fixed" version of the ADS...it didn't work. Last night, I found that glitch with the payload and changed it to 20 instead of 25. No worky. While I was in TunerPro, I changed the ALDL interface type to the MAX-232 interface. Still no worky. I changed the sampling rate several times and still nothing. The sample rate box bounces from 111hz to 125hz and I keep getting packet error counts. My PROM ID value comes up as $142F and I get no battery voltage when the ignition is in RUN (engine not running)
Looking at the above posted hac, I see that there are only 19 bytes in the stream definition...not 20 like the A90 definition says.
Any suggestions?

Mangus

125 hz is very wrong. i'm not sure this is even possible (in terms of the program), as the most you could ever get (throttled in the code) is 11hz...

lets take it offline.