'99 VS Series III SS Ute and EFILive V4

[Jasun]

Can't seem to get any thing working with EFILive V4 on vehicle.
Try both VS and VT files but neither seem to be successful, can some one help?
Thanx
Jasun

[Tordne]

Are you getting a vehicle connection? What cable are you using and what baud rate?

[Jasun]

The baud rate is 8192 and the cable is a usb to 16 pin connector,
If I use the gmh-vt8 file I receive the following:

08:26.686: Check vehicle interface...
08:26.694: Waiting for Aldl bus silence of at least 10ms...
08:26.696: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
08:26.706: Max232 interface detected OK

08:26.707: Scanning for heartbeat and chatter frames...
08:26.707: Waiting for Aldl bus silence of at least 10ms...
08:26.816: Com timeout: Expecting frame header byte
08:26.825: No chatter found

08:28.519: Start macro: Engine data and DTCs: DATADTC
08:28.520: Synchronising ALDL communications...
08:28.520: Waiting for heartbeat: $08,$55,$A3
08:28.520: Waiting for Aldl bus silence of at least 10ms...
08:28.628: Com timeout: Expecting frame header byte
08:28.633: Synchronising ALDL communications...
08:28.633: Waiting for heartbeat: $08,$55,$A3
08:28.633: Waiting for Aldl bus silence of at least 10ms...
08:28.738: Com timeout: Expecting frame header byte
08:28.744: Synchronising ALDL communications...
08:28.744: Waiting for heartbeat: $08,$55,$A3
08:28.744: Waiting for Aldl bus silence of at least 10ms...
08:28.849: Com timeout: Expecting frame header byte
08:28.857: Stop macro: Engine data and DTCs: DATADTC

and the gmh-vr68vs8 file gives:

09:02.009: Opening COM2 8228,8,N,1
09:06.111: Check vehicle interface...
09:06.119: Waiting for Aldl bus silence of at least 65ms...
09:06.183: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
09:06.194: Max232 interface detected OK

09:06.195: Scanning for heartbeat and chatter frames...
09:06.195: Waiting for Aldl bus silence of at least 65ms...
09:06.492: Com timeout: Expecting frame header byte
09:06.516: No chatter found


09:25.513: Start macro: ECM Engine Data: Engine Data Table0
09:25.512: Send: $F4,$57,$01,$00,$B4
09:25.732: Com timeout: Expecting frame header byte
09:25.743: Send: $F4,$57,$01,$00,$B4
09:25.963: Com timeout: Expecting frame header byte
09:25.973: Send: $F4,$57,$01,$00,$B4
09:26.193: Com timeout: Expecting frame header byte
09:26.207: Stop macro: ECM Engine Data: Engine Data Table0


Thanx,
Jason

[Tordne]

The VS file is likely to be the correct one. I've seen suggestions previously about reducing the T6 timeout to 10ms - from the current value of 65ms.

Perhaps try that and advise the results.

[Jasun]

Changed T6 to 10ms and received:

12:36.056: Opening COM2 8228,8,N,1
12:46.436: Check vehicle interface...
12:46.444: Waiting for Aldl bus silence of at least 10ms...
12:46.453: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
12:46.464: Max232 interface detected OK

12:46.465: Scanning for heartbeat and chatter frames...
12:46.465: Waiting for Aldl bus silence of at least 10ms...
12:46.675: Com timeout: Expecting frame header byte
12:46.685: No chatter found

13:00.976: Start macro: ECM Engine Data: Engine Data Table0
13:01.185: Com timeout: Expecting frame header byte
13:01.408: Com timeout: Expecting frame header byte
13:01.632: Com timeout: Expecting frame header byte
13:01.637: Stop macro: ECM Engine Data: Engine Data Table0


Thanx for the quick replies,
Jason

[Blacky]

Turn on the menu option: View->Serial IO.
Then log the same data as you have shown above.
That will show more detail for us to work with.

Although from what I have seen so far it looks like a faulty cable or connection somewhere. What cable are you using?

Regards
Paul

[Jasun]

I purchased the cable over Ebay, these links are some pics http://i20.ebayimg.com/03/i/000/a2/46/d976_1.JPG
http://i11.ebayimg.com/03/i/000/a2/48/00a7_12.JPG
The extra info is as follows:

VT File,

54:33.591: Opening COM2 8228,8,N,1
55:01.830: Check vehicle interface...
55:01.837: Waiting for Aldl bus silence of at least 10ms...
55:01.845: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
55:01.845: Start writing frame
55:01.845: Send: $FF,$55,$AC
55:01.846: Finished writing frame
55:01.846: Wait 10 ms after writing, before reading...
55:01.856: Start reading frame
55:01.856: Aldl frame header byte: $FF
55:01.856: Aldl frame length byte: $ 0
55:01.856: Recv: $FF,$55,$AC
55:01.856: Finished reading frame
55:01.856: Max232 interface detected OK

55:01.857: Scanning for heartbeat and chatter frames...
55:01.857: Waiting for Aldl bus silence of at least 10ms...
55:01.865: Start reading frame
55:01.965: Com timeout: Expecting frame header byte
55:02.014: No chatter found

55:05.779: Start macro: Engine data and DTCs: DATADTC
55:05.790: Synchronising ALDL communications...
55:05.790: Waiting for heartbeat: $08,$55,$A3
55:05.790: Waiting for Aldl bus silence of at least 10ms...
55:05.797: Start reading frame
55:05.897: Com timeout: Expecting frame header byte
55:05.921: No heartbeat found - ALDL not synchronised yet
55:05.926: Synchronising ALDL communications...
55:05.926: Waiting for heartbeat: $08,$55,$A3
55:05.926: Waiting for Aldl bus silence of at least 10ms...
55:05.927: Start reading frame
55:06.028: Com timeout: Expecting frame header byte
55:06.052: No heartbeat found - ALDL not synchronised yet
55:06.057: Synchronising ALDL communications...
55:06.057: Waiting for heartbeat: $08,$55,$A3
55:06.057: Waiting for Aldl bus silence of at least 10ms...
55:06.058: Start reading frame
55:06.158: Com timeout: Expecting frame header byte
55:06.182: No heartbeat found - ALDL not synchronised yet
55:06.191: Stop macro: Engine data and DTCs: DATADTC


VS File,


53:35.277: Check vehicle interface...
53:35.286: Waiting for Aldl bus silence of at least 10ms...
53:35.286: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
53:35.286: Start writing frame
53:35.286: Send: $FF,$55,$AC
53:35.287: Finished writing frame
53:35.287: Wait 10 ms after writing, before reading...
53:35.297: Start reading frame
53:35.297: Aldl frame header byte: $FF
53:35.297: Aldl frame length byte: $ 0
53:35.297: Recv: $FF,$55,$AC
53:35.297: Finished reading frame
53:35.297: Max232 interface detected OK

53:35.298: Scanning for heartbeat and chatter frames...
53:35.298: Waiting for Aldl bus silence of at least 10ms...
53:35.306: Start reading frame
53:35.507: Com timeout: Expecting frame header byte
53:35.587: No chatter found

54:19.292: Start macro: ECM Engine Data: Engine Data Table0
54:19.293: Start writing frame
54:19.293: Send: $F4,$57,$01,$00,$B4
54:19.294: Finished writing frame
54:19.294: Wait 10 ms after writing, before reading...
54:19.304: Start reading frame
54:19.304: Aldl frame header byte: $F4
54:19.304: Aldl frame length byte: $57
54:19.304: Recv: $F4,$57,$01,$00,$B4
54:19.304: Finished reading frame
54:19.304: MAX232 echo: $F4,$57,$01,$00,$B4
54:19.304: Wait 10 ms after writing, before reading...
54:19.314: Start reading frame
54:19.514: Com timeout: Expecting frame header byte
54:19.552: Aborting request due to previous error
54:19.556: Start writing frame
54:19.556: Send: $F4,$57,$01,$00,$B4
54:19.557: Finished writing frame
54:19.557: Wait 10 ms after writing, before reading...
54:19.567: Start reading frame
54:19.567: Aldl frame header byte: $F4
54:19.567: Aldl frame length byte: $57
54:19.567: Recv: $F4,$57,$01,$00,$B4
54:19.567: Finished reading frame
54:19.567: MAX232 echo: $F4,$57,$01,$00,$B4
54:19.567: Wait 10 ms after writing, before reading...
54:19.577: Start reading frame
54:19.775: Com timeout: Expecting frame header byte
54:19.812: Aborting request due to previous error
54:19.815: Start writing frame
54:19.815: Send: $F4,$57,$01,$00,$B4
54:19.816: Finished writing frame
54:19.816: Wait 10 ms after writing, before reading...
54:19.826: Start reading frame
54:19.826: Aldl frame header byte: $F4
54:19.826: Aldl frame length byte: $57
54:19.826: Recv: $F4,$57,$01,$00,$B4
54:19.826: Finished reading frame
54:19.826: MAX232 echo: $F4,$57,$01,$00,$B4
54:19.826: Wait 10 ms after writing, before reading...
54:19.836: Start reading frame
54:20.035: Com timeout: Expecting frame header byte
54:20.090: Aborting request due to previous error
54:20.099: Stop macro: ECM Engine Data: Engine Data Table0


Thanx for the time and effort,
Jason

[Blacky]

There are 3 possible reasons (that I can thing of right now) that may cause what you are seeing.

1. The vehicle's PCM is not transmitting any data in response to the request: $F4,$57,$01,$00,$B4, or there is a fault in the OBDII connector/loom wiring.

You would need to borrow a Tech1 or other scan tool capable of communicating with the VS to check that the ALDL comms is functional.
i.e. take it to a Holden dealer and see if their Tech1 can communicate with it.

2. The EFILive software is not communicating with the ALDL cable, but is instead talking to the laptop's built in modem.

Check the COM port assignment of the virtual serial port that is configured for your ALDL cable. Did you uinstall the USB drivers for the USB/ALDL cable and configure the virtual COM port? Make sure EFILive is using the same com port.

If EFILive is connecting to the COM port assigned to the modem (instead of the ALDL cable) it may receive data back from the modem so that it "thinks" it is connected to the ALDL cable.

3. The interface cable is faulty.

I'm not sure how to test for that possibility, you'd need to ask the seller or manufacturer.

Regards
Paul

[Jasun]

Thanks paul, will give it a try and run down a local holden dealer.
Again thanx for the time.
regards
jason