pgmfi.org

why i try to write my DL soft. for P29 - because no one soft not working for me, may be all soft. writed for P28/P30 ECU's, and they are have different addresses for datalogging.

1. i was read many posts but can't understend at which addresses i must read a data for logging:
eaxample:
in one post - "MAP (Map Senser Voltage): $A3"
another post - "14h = MAP "
another post - "036h MAP"

2. i will attach a bin file downloaded from my ECU, maybe any one can disassemble it and write for me addresses where i must read data for datalogging(ECT, IAT, O2,BARO,MAP,TPS,RPM)
In ASM i nothing understanding.

3. where read about transfering data ECU<>PC for OBD1 ?
what i mean:
example i need a read data from 0020h:
i must sent to ecu: 1 - 20h, 2 - 0020h, 3 - 2000h(as hi byte low byte inversion) or it have difficulties as for OBD2 (for reading in 032Ch we must send 06ACh ) ?

4. about data sending - how will right if i need read 2 bytes = (word) from addresses 0A02h-0A03h:

A) send to ECU: 0A02h, 0A03h
wait for ECU answer

B) send to ECU: 0A02h
wait for ECU answer
send to ECU: 0A03h
wait for ECU answer

C) send to ECU: 0A03h
wait for ECU answer
send to ECU: 0A02h
wait for ECU answer


Thx to any answers.

[%sig%]

Post Edited (05-23-04 18:26)

I think you're confusing many things here...
OBD1 does not have a simple datalogging protocol (in stock form) like OBD0.
Some people have figured out the protocol, but it is not at all simple.
If you're interested in datalogging off a stock ECU, disassemble the code fully and take a very close look at the stock serial interrupt handler. The serial code used in ECUControl, RTP stuff, etc. is re-written.

[%sig%]