GMH VTV6 '97 communication problem ? with info. i need help

what am i doing wrong? i just got this cable off the net and it is in the diagnostic plug, and my lappy, and im running the efilive pro v4 registered, i have selected the gm-vt6 xml and chosen the correct com port whick has been assigned to the device and NOTHING...

screen as follows


31:33.642: Initialising...
31:34.207: Opening COM4 8228,8,N,2
31:34.469: Ready.
31:39.002: Start macro: Engine data and DTCs: DATADTC
31:39.000: Synchronising ALDL communications...
31:39.000: Waiting for heartbeat: $08,$55,$A3
31:39.000: Waiting for Aldl bus silence of at least 50ms...
31:39.151: Com timeout: Expecting frame header byte
31:39.163: Synchronising ALDL communications...
31:39.163: Waiting for heartbeat: $08,$55,$A3
31:39.163: Waiting for Aldl bus silence of at least 50ms...
31:39.314: Com timeout: Expecting frame header byte
31:39.325: Synchronising ALDL communications...
31:39.325: Waiting for heartbeat: $08,$55,$A3
31:39.325: Waiting for Aldl bus silence of at least 50ms...
31:39.476: Com timeout: Expecting frame header byte
31:39.489: Stop macro: Engine data and DTCs: DATADTC

31:43.789: Check vehicle interface...
31:43.794: Waiting for Aldl bus silence of at least 50ms...
31:43.844: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
31:43.865: Max232 interface detected OK

31:43.866: Scanning for heartbeat and chatter frames...
31:43.866: Waiting for Aldl bus silence of at least 50ms...
31:44.017: Com timeout: Expecting frame header byte
31:44.032: No chatter found

with i/o on

10:30.102: Check vehicle interface...
10:30.108: Waiting for Aldl bus silence of at least 50ms...
10:30.158: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
10:30.158: Start writing frame
10:30.158: Send: $FF,$55,$AC
10:30.159: Finished writing frame
10:30.159: Wait 10 ms after writing, before reading...
10:30.169: Start reading frame
10:30.174: Aldl frame header byte: $FF
10:30.174: Aldl frame length byte: $ 0
10:30.174: Recv: $FF,$55,$AC
10:30.174: Finished reading frame
10:30.174: Max232 interface detected OK

10:30.174: Scanning for heartbeat and chatter frames...
10:30.174: Waiting for Aldl bus silence of at least 50ms...
10:30.225: Start reading frame
10:30.326: Com timeout: Expecting frame header byte
10:30.384: No chatter found

One thing that you could try, which has helped others with your error is lowering the Chatter T6 timing to 10 (often set to around 50). Let us know if that helps at all…

done it and still doesnt work this is beyond a joke..:help2:

this is what shows with usb view


Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0403 (Future Technology Devices International Limited)
idProduct: 0x6001
bcdDevice: 0x0400
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x03
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: Full
Device Address: 0x01
Open Pipes: 2

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Quote:

---

Originally Posted by southaussie

31:33.642: Initialising...
31:34.207: Opening COM4 8228,8,N,2
31:34.469: Ready.
.
.
.

---

Should be 1 stop bit.

Quote:

---

Originally Posted by Tordne

Should be 1 stop bit.

---

Yeah fixed the stop bit set to 1 now still the same result.
No anything.

Are you 100% positive that COM4 is the actual COM port that your ALDL cable is using?
If COM4 happens to be your built in modem, then you may get those results.

You should also check with the ALDL cable supplier whether or not you need to have MAX232 echo checked on or off in the Edit-Properties->Comms area. (Or just try it with that setting on and off to see if either setting works).

Also for a VT V6 you should see chatter when you click on the "detect chatter" tool bar icon. If no chatter is detected then no data is getting from the ECM to the PC.

Regards
Paul