ALDL Logging on 808

[elcap]

hi guys,

im trying to get logging working on my 808 ecu with tuner pro rt v5.

so ive got a kalmaker tune, N05 (i assume as im running a 2bar map sensor).
i have an aldl cable that came with the car (see pic).
i can log with that cable using winaldl at 160 baud using the 808 as the ECM type.
i am using a serial to usb converter, with FTDI chipset.

i have tried to get tuner pro rt to datalog but i cant get it to connect...
i grabbed the 1227808 ads file from the sticky in this section.
i have converted the 1227808.ads to .adx file using tunerpro rt.
i have selected the correct com port for my converter. the interface test cant find my cable, but i assumed that was bcos it was trying to do it at 8192 baud.
when i click the acquire data button it says "connecting" but never connects.

Does anyone know what the problem could be?
Has anyone used that 1227808 ads file to successfully log in tunerpro?
i noticed that the ads file definition has the baud rate set to 8192..... shouldnt this be 160?

Thanks
Rob

[antus]

I would try the kalmaker SP3 ADX with TP5 in the filename for an N05. You might need to change the equasion for the MAP to get it to read correctly as I assume the scale is wrong. This assumes you have an 8192 baud interface. I cant confirm that data will line up though, and cant really troubleshoot further if it doesnt just work as I have 12P on my car. Other than keeping an eye on data such as engine temp which moves slowly, 160 baud is pretty much useless for tuning. TP5 requires different connection setup stuff that is not present in TP4, so importing an ADS will give you a base but requires the connection macros to be set up to get a link. This is why its better to start with a TP5 ADX. I cant comment on that interface, ive never seen one of those before, either. Perhaps it is 160 baud only?

[VL400]

With a datalogging on/off switch I will bet its a 160baud interface only. The early ECUs required a resistor to get data flowing on the CEL wire. Try winaldl, that works with the '808, not sure about Kalmake though. http://winaldl.joby.se/

[elcap]

ok ill give the Kalmaker_SP3_N03 TP5.adx file a quick shot tonight.
is it worth trying to get the 1227808.ads file working in tunerpro rt v4?

yeh the interface is only 160 baud at the moment, i dont have the 8192 going yet on my ecu. yep winaldl connects ok but its a bit basic.

i think i will concentrate on getting the 808 high speed comms mod working.
with tunerpro rt v5, u can disable the echo, so does that mean i dont need to put a 1k resistor and diode between ports 11 and 12 on the max232?
Edit: Also, will the flash tool work without the echo?

[antus]

ok well forget the 8192 baud TP5 adx at this stage. 160 baud is not much data, dont expect to get more out of it than what you see with winaldl. the lack of speed is why there is not much data available. The ads has more chance of working without modification on tp4 and your hardware provided its all for 160 baud.

Yes, wire the tx and rx to the ecu directly for an '808 and use no echo. Most 8192 baud software for modified '808s will default to no echo and work fine.

[elcap]

so i found the rs232 to ttl adapter that i bought a few years ago, and after a fair bit of mucking around i still cant connect to my ecu.



i suspect that the adapter board i have isnt correctly connected according to the diagram. https://pcmhacking.net/forums/view ... f=11&t=173

heres the pinouts of the IC and where they go to on the board.
1-6 have caps
7 - rs232-1 T1
8 - rs232-1 R1
9 - R1
10 - T1
11 - T0
12 - R0
13 - rs232-0 R0
14 - rs232-0 T0
15 - gnd
16 - vcc

i connected the ecu to the correct pins on the adapter. that seems fine.
+5V - vcc - 16
gnd - gnd - 15
t1 in - T0 - 11
r1 out - R0 - 12

i then checked the rs232 db9 connector and where it is supposed to connect to the IC
db9 - IC
2 - 14
3 - 13
5 - 15
Pins 2 and 3 dont seem to be connected to the IC..... WTF?!?!?
Do i need to solder the underside of the db9 pins to rs232-0 R0 and T0?

[elcap]

i used a bit of wire and soldered those connections together.
2-14 and 3-13 but still cant get the cable to work arrrggghhhh.
tunerpro rt wont detect the cable either.....

any ideas?

[charlay86]

tunerpro won't detect the cable unless it is setup to have echo, which means connecting rx & tx via a resistor & diode.

[elcap]

good to know about the cable test

i pulled apart my cable between the 232 ttl adapter and my pc and the pins are connected properly...

heres the setup:
ecu pins <--> rs232 ttl adapter <--> male to female db9 cable <--> usb to serial cable <--> pc

is there a way to test the rs232 ttl adapter?
like checking voltage on the transmit/receive pins when ecu is on?

i get a red light on the adapter so i know at least vcc is connected to the ecu properly...
maybe the next step is to check the continuity from ecu to the rs232 adapter....

pretty over this shit atm!!!

Edit: how important is the values of the Capacitors?
i have 5 x 0.01uF caps and 1 x 10uF cap...

[VL400]

Can disconnect the TTL side of the adapter from the ECU and link the tx and rx of the board (leave it powered by the ECU though). Then open a terminal program, or even TP to detect the cable, and see what you get. In a terminal program can just type characters and see if they echo back.

Are you using a USB-serial adapter?

EDIT: just read you are using a USB-serial adapter. Could be your problem if its not an FTDI chipset. Most dont like the 8192 baud of the ECU.