PDA

View Full Version : Australian Holden vt 5 litre error



justice4all3000
October 24th, 2011, 05:57 PM
trying to connect the aldl cable i can only get data with the engine off when i turn it on i lose the connection

heres the log any help will be much appreciated


04:13.580: Initialising...
04:14.192: Opening COM1 8228,8,N,1
04:14.481: Ready.
04:16.323: Start macro: Set air fuel ratio: AFR
04:16.330: Synchronising ALDL communications...
04:16.330: Waiting for heartbeat: $08,$55,$A3
04:16.330: Waiting for Aldl bus silence of at least 10ms...
04:16.681: Com timeout: Data frame truncated: $41,$6B,$00,$48,$00,$7E,$50,$23,$00,$01,$FA,$20,$0 1,$0F,$10,$56,$94,$08,$55,$A3,$00,$00,$00,$00,$00
04:16.686: Synchronising ALDL communications...
04:16.686: Waiting for heartbeat: $08,$55,$A3
04:16.686: Waiting for Aldl bus silence of at least 10ms...
04:16.757: Error: Reply frame checksum failure
04:16.762: Synchronising ALDL communications...
04:16.762: Waiting for heartbeat: $08,$55,$A3
04:16.762: Waiting for Aldl bus silence of at least 10ms...
04:16.901: Error: Reply frame checksum failure
04:16.908: Stop macro: Set air fuel ratio: AFR

04:25.145: Start macro: Engine data and DTCs: DATADTC
04:25.144: Synchronising ALDL communications...
04:25.144: Waiting for heartbeat: $08,$55,$A3
04:25.144: Waiting for Aldl bus silence of at least 10ms...
04:25.166: Error: Reply frame checksum failure
04:25.171: Synchronising ALDL communications...
04:25.171: Waiting for heartbeat: $08,$55,$A3
04:25.171: Waiting for Aldl bus silence of at least 10ms...
04:25.290: Com timeout: Data frame truncated: $00,$FA,$20,$01,$0E,$10,$56,$8E,$A8,$55,$03,$A9,$5 7,$06,$00,$FA,$20,$55,$8B,$21,$58,$34,$2F,$00,$24, $D8,$55,$D3,$90,$55,$1B,$91,$58,$08,$00,$00,$0F,$A 0,$55,$0B,$A1,$57,$00,$00,$08,$11,$5C,$FF,$00,$45, $17,$01,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$0 0,$00,$00,$00,$00,$00
04:25.299: Synchronising ALDL communications...
04:25.300: Waiting for heartbeat: $08,$55,$A3
04:25.300: Waiting for Aldl bus silence of at least 10ms...
04:25.326: Error: Reply frame checksum failure
04:25.333: Stop macro: Engine data and DTCs: DATADTC

04:29.131: Start macro: Engine data: DATA
04:29.138: Synchronising ALDL communications...
04:29.138: Waiting for heartbeat: $08,$55,$A3
04:29.138: Waiting for Aldl bus silence of at least 10ms...
04:29.228: Error: Reply frame checksum failure
04:29.235: Synchronising ALDL communications...
04:29.235: Waiting for heartbeat: $08,$55,$A3
04:29.235: Waiting for Aldl bus silence of at least 10ms...
04:29.270: Send: $F5,$57,$01,$00,$B3
04:29.372: Error: Reply frame checksum failure
04:29.388: Send: $F5,$57,$01,$00,$B3
04:29.484: Error: Reply frame checksum failure
04:29.490: Resuming normal ALDL communications...
04:29.519: Stop macro: Engine data: DATA

Blacky
October 25th, 2011, 08:08 AM
Can you try this with the engine off and then with the engine running.

1. Turn on Serial I/O tracing (menu: View->Serial I/O)
2. Click the Start ALDL button. (Ignore warning message about serial I/O)
3. Wait for around 5 seconds or until it fails.
4. Copy all the trace text (right click "Copy All") and paste into notepad.
5. Attach notepad text file to this thread.

The concern is the checksum errors.
They are indicative of a loose wire of bad connection causing data corruption.

Regards
Paul

Blacky
October 25th, 2011, 08:17 AM
Analyzing this data...
$00,$FA,$20,$01,$0E,$10,$56,$8E,$A8,$55,$03,$A9,$5 7,$06,$00,$FA,$20,$55,$8B,$21,$58,$34,$2F,$00,$24, $D8,$55,$D3,$90,$55,$1B,$91,$58,$08,$00,$00,$0F,$A 0,$55,$0B,$A1,$57,$00,$00,$08,$11,$5C,$FF,$00,$45, $17

The software should be splitting it into messages like this:

.....$00,$FA,$20,$01,$0E,$10,$56,$8E,
$A8,$55,$03,
$A9,$57,$06,$00,$FA,
$20,$55,$8B,
$21,$58,$34,$2F,$00,$24,
$D8,$55,$D3,
$90,$55,$1B,
$91,$58,$08,$00,$00,$0F,
$A0,$55,$0B,
$A1,$57,$00,$00,$08,
$11,$5C,$FF,$00,$45, $17......

That's all chatter data and should be suspended by the EFILive software.

Make sure you have selected the VT V8 vehicle.
And make sure it has the suspend and resume commands set up correctly, as per the image below.


Regards
Paul

justice4all3000
October 25th, 2011, 01:51 PM
Hi thank you for your help I have attached log files with the engine on and off

cheers

Blacky
October 25th, 2011, 01:59 PM
Thanks for the data, I just need a little more info...

Can you try this with the engine off and then with the engine running.

1. Turn on Serial I/O tracing (menu: View->Serial I/O)
2. Click the "Automatically Detect Chatter" button. (Ignore warning message about serial I/O)
3. Wait until it finishes or fails.
4. Copy all the trace text (right click "Copy All") and paste into notepad.
5. Attach notepad text file to this thread.

Regards
Paul

justice4all3000
October 25th, 2011, 02:26 PM
Hi i followed your instructions for further data and for some reason the connection works now also with the engine running heres the logs

sorry about the zipfile the file size was too large

Blacky
October 25th, 2011, 03:03 PM
Even though its working now, it may fail again like it did earlier unless we can determine exactly what the problem is/was.

I would also like to see the output from the "Display ALDL Chatter" button.
Preferably with the engine off and with the engine on.

Regards
Paul

justice4all3000
October 25th, 2011, 10:45 PM
hi heres the new log you where right! now I cant connect with the engine running anymore, I had trouble starting the car after other successful attempt to get efi live to connect the car wouldn't fire at first, then when it finally fired it ran very rough for a few seconds before correcting itself (aldl cable was not plugged in at the time) could this be anyway related to me fiddling around with efi live?



cheers

Blacky
October 26th, 2011, 07:50 AM
There is most likely something wrong with either the vehicle's ALDL wiring, connector or the ALDL cable.

These two lines tell the story:

32:58.078: Recv: $41,$63,$00,$2A,$00,$7E,$55,$23,$00,$08,$FA,$2B,$0 1,$1F,$10,$56,$99
...
32:58.254: Recv: $41,$63,$00,$2A,$00,$7E,$55,$23,$00,$00,$FA,$2B,$0 1,$17,$10,$56,$99


The green $99 is the checksum for the frame. Both frames have the same checksum, yet the data payload differs by one byte.
The $08 in the first frame is a data corruption error.

The $08 in the first frame, in binary is 00001000
The $00 in the second frame, in binary is 00000000
It is almost certain that some external electrical noise has caused the solitary 1 bit to appear on the ALDL data line that corrupted the $00 into a $08

When the engine is on, there is much more electrical interference so I would start looking for bad wiring or bad connections to/from the engine controller.

Regards
Paul

justice4all3000
October 26th, 2011, 10:12 AM
There is most likely something wrong with either the vehicle's ALDL wiring, connector or the ALDL cable.

These two lines tell the story:

32:58.078: Recv: $41,$63,$00,$2A,$00,$7E,$55,$23,$00,$08,$FA,$2B,$0 1,$1F,$10,$56,$99
...
32:58.254: Recv: $41,$63,$00,$2A,$00,$7E,$55,$23,$00,$00,$FA,$2B,$0 1,$17,$10,$56,$99


The green $99 is the checksum for the frame. Both frames have the same checksum, yet the data payload differs by one byte.
The $08 in the first frame is a data corruption error.

The $08 in the first frame, in binary is 00001000
The $00 in the second frame, in binary is 00000000
It is almost certain that some external electrical noise has caused the solitary 1 bit to appear on the ALDL data line that corrupted the $00 into a $08

When the engine is on, there is much more electrical interference so I would start looking for bad wiring or bad connections to/from the engine controller.

Regards
Paul




Hi thank you for all your help whats the best way to trouble shoot this electrical problem?