pcmhacking.net

I have read the 'how tos' and beginner guides but i'm stumped.

I have VP V6 auto, using a 305 with OSE$12P v111 BJCD (on a 29c256 chip), running TunerproRT with OSE 1.25 plugin.
I can connect at 8hz but the info is garbage (the cable works fine with standard memcal and Win ALDL).
Sample garbage: RPM 464 - 32000+, BLM cell number 256, BLM 256, Coolant Temp Sensor Voltage 0.02 (808 ADX). The V111 adx files give similar numbers.

Car runs fine with BJCD memcal in the 305.
Car runs fine with the standard AWUY in the 305.

I have tried both the 808 and V111_1bar petrol ADX files in TunerproRT.

The cable works fine with AWUY and an 808 ecu using WinALDL.

Do I need a different cable to talk between the ECU and the laptop? Or have I overlooked something?

You may require a different cable as the 808 and VN/VP memcal used 160 baud on the CEL wire while 12P is full bi-directional ALDL at 8192baud on pin A8. You will need to contact whoever you bought the cable from to find out if it supports 8192baud data or just 160baud.

There are interface boards to suit 8192baud here if you require one..
RS232 - https://pcmhacking.net/forums/viewtopic.php?f=14&t=396
USB - https://pcmhacking.net/forums/viewtopic.php?f=14&t=164
USB over vehicle data interface (VR and later have the connector under the steering column) - https://pcmhacking.net/forums/viewtopic.php?f=14&t=622

I was under the impression that the 305 was 8192 baud capable and wouldn't require either the R232 or USB interface.

edit: missed the bit about it being a '305 ecu

The 16206305 is 8192 capable, is an update to the 16183082.
Check the echo settings in the adx, whatever you're using try the opposite.
You will need to edit the adx and there is a tick box for echo on or off.

Yoda

May also need to check the wiring, as I think there are some differences between 160 and 8192 baud rate.

EDIT: In 160 Baud ECU Pin A9 goes to the ALDL connector, and the data is on ECU Pin A5.
For 8192 ECU Pin A9 goes to Pin 6 on the ALDL connector and Pin A8 goes to Pin 9 on the ALDL, it is the latter which carries the 8192 ALDL info and is most likely missing in your case.
NOTE: ALDL connectors are different between VR+ vehicles (16 pin OBDII style) and VN/P which have a 6 pin connector, above ALDL pins refer to the OBDII style plug.
Attached images from the techedge website.
VN/P ALDL connector VR+ ALDL Connector Depending on your interface, it may or may not support 8192 baud rate.

Yoda

Yes, my ECU connector is missing A8, so if I place a wire into A8 and put that in the place of 'E' (A5) on the diagnostic connection, I should have 8192 baud?

Yep, and if your interface supports 8192baud ALDL (hardware wise it will be different as 160 baud is uni-directional) then you will be able to log it.

Thank you Gentlemen, this next week project.

Is it possible just to move the A5 terminal into the position of the A8 terminal?

I only ask as ATM i don't have any suitable clips to insert into A8.