Results 1 to 6 of 6

Thread: vs commodore ute

  1. #1
    New Member
    Join Date
    Aug 2009
    Posts
    5

    Unhappy vs commodore ute

    hey i received no chatter when i ran efilive, am running on windows vista ultimate, on an acer aspire laptop.....if any can help me out as to what i need to reconfigure to get the chatter to respond and then proceed with running the diagnostic?

    cheers all

  2. #2
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,490

    Default

    I don't think the VS ECM's send out any chatter.

    Regards
    Paul
    Before asking for help, please read this.

  3. #3
    New Member
    Join Date
    Aug 2009
    Posts
    5

    Default

    if my vehicle does not send out chatter then what things can i do with this program.......


    maybe this helps?

    57:19.801: Initialising...
    57:20.052: Opening COM2 8228,8,N,1
    57:20.592: Ready.
    58:05.057: Start macro: Clear diagnostic trouble codes: CLRDTC
    58:05.056: Start writing frame
    58:05.058: Send: $F5,$57,$0A,$00,$AA
    58:05.060: Finished writing frame
    58:05.067: Stop macro: Clear diagnostic trouble codes: CLRDTC

    58:13.704: Check vehicle interface...
    58:13.710: Waiting for Aldl bus silence of at least 50ms...
    58:13.761: Requesting Max232 interface to acknowlege: $FF,$55,$AC...
    58:13.764: Start writing frame
    58:13.765: Send: $FF,$55,$AC
    58:13.767: Finished writing frame
    58:13.769: Wait 10 ms after writing, before reading...
    58:13.780: Start reading frame
    58:13.783: Aldl frame header byte: $FF
    58:13.786: Aldl frame length byte: $ 0
    58:13.787: Recv: $FF,$55,$AC
    58:13.789: Finished reading frame
    58:13.790: Max232 interface detected OK

    58:13.804: Scanning for heartbeat and chatter frames...
    58:13.812: Waiting for Aldl bus silence of at least 50ms...
    58:13.864: Start reading frame
    58:13.966: Com timeout: Expecting frame header byte
    58:13.968: No chatter found

    58:28.956: Start macro: Clear diagnostic trouble codes: CLRDTC
    58:28.957: Start writing frame
    58:28.960: Send: $F5,$57,$0A,$00,$AA
    58:28.963: Finished writing frame
    58:28.970: Stop macro: Clear diagnostic trouble codes: CLRDTC

    59:04.033: Start macro: Clear diagnostic trouble codes: CLRDTC
    59:04.033: Start writing frame
    59:04.035: Send: $F5,$57,$0A,$00,$AA
    59:04.036: Finished writing frame
    59:04.041: Stop macro: Clear diagnostic trouble codes: CLRDTC

    05:46.814: Scan for chatter...
    05:46.816: Waiting for Aldl bus silence of at least 50ms...
    05:46.867: Start reading frame
    05:46.969: Com timeout: Expecting frame header byte
    05:46.971: No chatter found
    05:46.975: Start reading frame
    05:47.077: Com timeout: Expecting frame header byte
    05:47.079: No chatter found
    05:47.082: Start reading frame
    05:47.193: Com timeout: Expecting frame header byte
    05:47.195: No chatter found
    05:47.196: Start reading frame
    05:47.298: Com timeout: Expecting frame header byte
    05:47.300: No chatter found
    05:47.302: Start reading frame
    05:47.403: Com timeout: Expecting frame header byte
    05:47.405: No chatter found
    05:47.407: Start reading frame
    05:47.508: Com timeout: Expecting frame header byte
    05:47.510: No chatter found
    05:47.511: Start reading frame
    05:47.613: Com timeout: Expecting frame header byte
    05:47.615: No chatter found
    05:47.621: Start reading frame
    05:47.723: Com timeout: Expecting frame header byte
    05:47.725: No chatter found
    05:47.727: Start reading frame
    05:47.829: Com timeout: Expecting frame header byte
    05:47.831: No chatter found
    05:47.833: Start reading frame
    05:47.934: Com timeout: Expecting frame header byte
    05:47.936: No chatter found
    05:47.938: Start reading frame
    05:48.039: Com timeout: Expecting frame header byte
    05:48.041: No chatter found
    05:48.043: Start reading frame
    05:48.144: Com timeout: Expecting frame header byte
    05:48.146: No chatter found
    05:48.148: Start reading frame
    05:48.249: Com timeout: Expecting frame header byte
    05:48.251: No chatter found
    05:48.252: Start reading frame
    05:48.354: Com timeout: Expecting frame header byte
    05:48.356: No chatter found
    05:48.358: Start reading frame
    05:48.460: Com timeout: Expecting frame header byte
    05:48.463: No chatter found
    05:48.465: Start reading frame
    05:48.567: Com timeout: Expecting frame header byte
    05:48.569: No chatter found
    05:48.571: Start reading frame
    05:48.672: Com timeout: Expecting frame header byte
    05:48.674: No chatter found
    05:48.677: Start reading frame
    05:48.779: Com timeout: Expecting frame header byte
    05:48.781: No chatter found
    05:48.782: Start reading frame
    05:48.884: Com timeout: Expecting frame header byte
    05:48.886: No chatter found
    05:48.888: Start reading frame
    05:48.989: Com timeout: Expecting frame header byte
    05:48.991: No chatter found
    05:48.993: Start reading frame
    05:49.096: Com timeout: Expecting frame header byte
    05:49.098: No chatter found
    05:49.100: Start reading frame
    05:49.201: Com timeout: Expecting frame header byte
    05:49.203: No chatter found
    05:49.205: Start reading frame
    05:49.307: Com timeout: Expecting frame header byte
    05:49.309: No chatter found
    05:49.312: Start reading frame
    05:49.414: Com timeout: Expecting frame header byte
    05:49.416: No chatter found
    05:49.418: Start reading frame
    05:49.520: Com timeout: Expecting frame header byte
    05:49.524: No chatter found
    05:49.526: Start reading frame
    05:49.627: Com timeout: Expecting frame header byte
    05:49.629: No chatter found
    05:49.630: Start reading frame
    05:49.732: Com timeout: Expecting frame header byte
    05:49.734: No chatter found
    05:49.738: Start reading frame
    05:49.839: Com timeout: Expecting frame header byte
    05:49.841: No chatter found
    05:49.844: Start reading frame
    05:49.945: Com timeout: Expecting frame header byte
    05:49.947: No chatter found
    05:49.949: Start reading frame
    05:50.051: Com timeout: Expecting frame header byte
    05:50.053: No chatter found
    05:50.055: Start reading frame
    05:50.157: Com timeout: Expecting frame header byte
    05:50.159: No chatter found
    05:50.161: Start reading frame
    05:50.263: Com timeout: Expecting frame header byte
    05:50.265: No chatter found
    05:50.267: Start reading frame
    05:50.368: Com timeout: Expecting frame header byte
    05:50.370: No chatter found
    05:50.372: Start reading frame
    05:50.473: Com timeout: Expecting frame header byte
    05:50.475: No chatter found
    05:50.489: Start reading frame
    05:50.590: Com timeout: Expecting frame header byte
    05:50.592: No chatter found
    05:50.598: Start reading frame
    05:50.700: Com timeout: Expecting frame header byte
    05:50.702: No chatter found
    05:50.706: Stop scanning for chatter

  4. #4
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,490

    Default

    Its a good thing that your vehicle does not chatter. Chatter is just comms data that is constantly sent between modules, it interferes with data logging. When chatter exists, EFILive must explicitly tell the various modules to stop chattering before data logging can proceed.

    If there is no chatter then data logging is easier and causes less "grief" to the system. When each module expects to see the chatter data, then when it is stopped by EFILive the modules may set trouble codes indicating "loss of communications". So be happy your system has no chatter.

    All you need to do is open the appropriate VS data stream file and click on the ALDL button to start data logging. No need to worry about chatter frames opf trying to suppress them or work around them.

    P.S. EFILive V4 was developed using the VS-V8 Commodore as the test vehicle. So it should work perfectly for the VS-V8.

    Regards
    Paul
    Before asking for help, please read this.

  5. #5
    New Member
    Join Date
    Aug 2009
    Posts
    5

    Default

    btw my car is a vs v6 no different there i imagine, where can i open the vs data stream, then after i do that do i then just start the car as at the moment the key is on at the ignition? i have very little idea about all this, i just dont want to do anything thay may harm the ECM or other electronics?

  6. #6
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,490

    Default

    You won't harm anything by running the scan software.

    Load the gmh-vr68vs8.xml file, using the File->Select vehicle, menu option.
    Start engine.
    Then click on the green ALDL button to start logging data.

    Regards
    Paul
    Before asking for help, please read this.

Similar Threads

  1. Commodore
    By Chevy366 in forum Lounge
    Replies: 2
    Last Post: July 13th, 2009, 03:57 PM
  2. new commodore
    By odd boy in forum E37, E38 & E67 PFI ECM's
    Replies: 18
    Last Post: May 4th, 2009, 09:23 PM
  3. VX and VY commodore
    By Thumper in forum Gen III V8 Specific
    Replies: 1
    Last Post: February 8th, 2009, 10:48 AM
  4. 07 VE commodore
    By ALRAJHI in forum Gen IV V8 Specific
    Replies: 3
    Last Post: October 6th, 2007, 07:44 PM
  5. Commodore vx II V6 on LPG
    By Mike :) in forum General (Petrol, Gas, Ethanol)
    Replies: 1
    Last Post: May 19th, 2006, 10:17 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •