EFILive v4 problem

[gre0005]

i got this coming up ???

57:37.328: Check vehicle interface...
57:37.342: Interface not checked because 160-baud interface is selected

57:37.342: Scanning for heartbeat and chatter frames...
57:37.342: Waiting for Aldl bus silence of at least 50ms...
57:38.494: Com timeout: Expecting frame header byte
57:38.512: No chatter found
what do i do?

[Tordne]

Is 160 baud the correct setting for your vehicle? The other option is 8192 baud; this is often a problem if using a USB/Serial converter which does not support that rate.

The other thing to try is setting timeout values for T6 to 10ms.

[gre0005]

Is 160 baud the correct setting for your vehicle? The other option is 8192 baud; this is often a problem if using a USB/Serial converter which does not support that rate.

The other thing to try is setting timeout values for T6 to 10ms.

Well the vehicle is a Vn 5L so is that the right settings?

[Tordne]

In that particular case I would expect the baud rate to be correct. But do try lowering the T6 chatter value to 10ms.

[gre0005]

In that particular case I would expect the baud rate to be correct. But do try lowering the T6 chatter value to 10ms.

14:30.920: Opening COM1 160,8,N,1
14:35.857: Check vehicle interface...
14:35.866: Interface not checked because 160-baud interface is selected

14:35.873: Scanning for heartbeat and chatter frames...
14:35.873: Waiting for Aldl bus silence of at least 50ms...
14:37.023: Com timeout: Expecting frame header byte
14:37.040: No chatter found

15:33.816: Updating vehicle information...
15:33.936: Opening COM1 160,8,N,1
15:37.324: Check vehicle interface...
15:37.334: Interface not checked because 160-baud interface is selected

15:37.334: Scanning for heartbeat and chatter frames...
15:37.334: Waiting for Aldl bus silence of at least 10ms...
15:38.443: Com timeout: Expecting frame header byte
15:38.457: No chatter found

17:28.498: Updating vehicle information...
17:28.615: Opening COM1 160,8,N,1
18:40.379: Check vehicle interface...
18:40.388: Interface not checked because 160-baud interface is selected

18:40.388: Scanning for heartbeat and chatter frames...
18:40.388: Waiting for Aldl bus silence of at least 50ms...
18:46.793: Can't find silence greater than 50ms
18:46.797: Hint: try halving T6 from 50ms to 25ms
18:47.081: Error: Reply frame checksum failure
18:47.083: No chatter found

19:17.436: Updating vehicle information...
19:17.548: Opening COM1 160,8,N,1
19:19.652: Check vehicle interface...
19:19.661: Interface not checked because 160-baud interface is selected

19:19.661: Scanning for heartbeat and chatter frames...
19:19.661: Waiting for Aldl bus silence of at least 25ms...
19:26.076: Can't find silence greater than 25ms
19:26.091: Hint: try halving T6 from 25ms to 12ms
19:27.164: Error: Reply frame checksum failure
19:27.170: No chatter found

19:43.808: Updating vehicle information...
19:43.931: Opening COM1 160,8,N,1
19:45.497: Check vehicle interface...
19:45.506: Interface not checked because 160-baud interface is selected

19:45.506: Scanning for heartbeat and chatter frames...
19:45.506: Waiting for Aldl bus silence of at least 12ms...
19:46.593: Error: Reply frame checksum failure
19:46.613: No chatter found


I noticed under the Application tap it said VN/VP but says liters 3.6 not 5.0L and saying v6 not v8? as far as I am aware this is the correct code for my car VN68VP68

[Tordne]

I'd say you have the right file. The XML file name should be 'gmh-vn68vp68.xml' which is for the VN V6 & V8 and the VP V6 & V8.

Couple of things to ask:
- Is the PCM stock or has it been programmed? I'm aware from previus cases where the chip has been changed they don't work the same as factory and the V4 software does not work with them.
- Do you have another vehicle (friend perhaps) that you might test with? That would validate a few things (cable, configuration).

Cheers,

[gre0005]

I'd say you have the right file. The XML file name should be 'gmh-vn68vp68.xml' which is for the VN V6 & V8 and the VP V6 & V8.

Couple of things to ask:
- Is the PCM stock or has it been programmed? I'm aware from previus cases where the chip has been changed they don't work the same as factory and the V2 software does not work with them.
- Do you have another vehicle (friend perhaps) that you might test with? That would validate a few things (cable, configuration).

Cheers,

I tried with a V6 VN and same thing happening :(

[Tordne]

Is you vehicle chip stock or is it a performance chip (see my previous post)?

[gre0005]

Is you vehicle chip stock or is it a performance chip (see my previous post)?

Well the v6 commy is for sure. mine I not to sure about