Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: BB Logging and AutoVE

  1. #1
    Lifetime Member
    Join Date
    May 2008
    Posts
    389

    Default BB Logging and AutoVE

    Can the BB data recording suffice for the AutoVE?

    I have no room in the dragster to let a laptop bounce around so I want to be able to use just the FalshScan V2 to record the data then upload to the laptop and perform the AutoVE calculations, can I?

    Lee

  2. #2
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    Lee, yes.

    Cheers,
    Joe

  3. #3
    Lifetime Member
    Join Date
    May 2008
    Posts
    389

    Default

    OK, I tried it but I dont think I've got it right.

    When I record it only records AD1. The WBO's are not working. when I tell it that I have the LC-1 it comes up with no controller found or something like that.

    What steps do I need to do in order for this to work correctly?

    I messed with the options.ini but still lost....

  4. #4
    Lifetime Member
    Join Date
    May 2008
    Posts
    389

    Default

    Just send me a darn options.ini with the right info to record the AutoVE PID's. This is getting to be a real pain. I sure wish there was better manuals available!!!

    It looks like you just expect everyone to know how to do all this but in reality, I've spent many many hours reading through this site and my head is spinning...... a snippit here and a snippit there....

  5. #5
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    Lee,

    You are aware that V2 BBL is in beta test phase...?

    If you didn't understand something in the threads why didn't you post questions...?

    On V2, you have to go into options and enable WB serial input and select your WB brand...

    Do you have the right serial cable...?

    Have you just tried logging with the Options.ini that came with...?

    What OS are you using (or what year/model vehicle is it out of)...?

    What pids do yo want to log...?

    (you've hardly given us any info to help us help you...)

    In Options.ini, are you aware that channel count has to be 24 or less...?

    Here's my Options.ini (can be used with 99-08 LS1/LS6), it requires only the LS1B_*.pmm files:
    Code:
    ;  _______________________________________________________________________ 
    ; |                                                                       | 
    ; |                         Copyright © 1999-2007                         | 
    ; |                            EFILive Limited                            | 
    ; |                      web: http://www.efilive.com                      | 
    ; |                        email: info@efilive.com                        | 
    ; |_______________________________________________________________________| 
    ; 
    ; Modifications 
    ; _________________________________________________________________________ 
    ; Version | When        | Who | Why 
    ; _________________________________________________________________________ 
    ; 8.0     | 2007-Feb-16 | PSB | Created file 
    ; _________________________________________________________________________ 
    ; 
    ; _________________________________________________________________________ 
    *PID_SELECTIONS 
    ; 
    ;PID selection list 
    ;------------------- 
    ; 
    ; Cap1 and Cap2 form the "on-screen" display option from which the user may select. 
    ; Controllers lists 1 or 2 "&" seperated pid memory map (*.pmm) files. 
    ; PSL is the PID Selection defined later in this file 
    ; PCU is the PID Custom Units defined later in this file 
    ; 
    ;Cap1    Cap2     Controllers (Engine&Trans) PSL        PCU 
    ;------- -------- -------------------------- ---------- -------- 
    A->,     IBPW,    LS1B_A.pmm,                PSL_A,     PCU 
    B->,     O2S,     LS1B_A.pmm,                PSL_B,     PCU 
    C->,     CAT,     LS1B_A.pmm,                PSL_C,     PCU 
    D->,     LOOP,    LS1B_A.pmm,                PSL_D,     PCU 
    E->,     TRANS,   LS1B_A.pmm,                PSL_E,     PCU 
     
    ; _________________________________________________________________________ 
    ; 
    ; PID Selection List 
    ; ---------------------- 
    ; 
    ; Node:  Is one of PCM, ECM or TCM (use "-" for external PIDs). 
    ;        PCM = Powertran controller, engine and trans combined into one controller. 
    ;        ECM = Dedicated engine controller only. 
    ;        TCM = Dedicated transmission controller only. 
    ; 
    ;        If you are unsure whether to use ECM or PCM, use PCM. PCM will match both ECM and PCM. 
    ;        The Node specified from which controller the PID will be retrieved. 
    ;        i.e. ECM-RPM v's TCM-RPM. 
    ; 
    ; PIDs:  Is one or more "|" seperated PID names. The first valid PID will be used. 
    ; Alarm: Is 5 ":" seperated fields: 
    ;        min:   Minimum value, below which the alarm will sound. 
    ;        max:   Maximum value, above which the alarm will sound. 
    ;        style: Is one of: 
    ;                0 = No sound, No LEDs 
    ;                1 = Low pitch 
    ;                2 = Medium Pitch 
    ;                3 = High Pitch 
    ;                4 = Very high Pitch 
    ;               16 = Illuminate LED 1 
    ;               32 = Illuminate LED 2 
    ;               48 = Illuminate LED 3 
    ;               64 = Illuminate LED 4 
    ;              128 = Illuminate LED 5 
    ;               Add Pitch and LED values together to enable audio and visual alarms. 
    ;               For example, for Medium Pitch and LED 4, use 2+64 = 66 
    ;        time:  Time (in 10ms increments) for which alarm will be sounded. 
    ;        hold:  Time (in seconds) for which the displayed value will be frozen (not implemented yet). 
    ; 
     
    ; _________________________________________________________________________ 
    *PSL_A 
    ; 
    ;Node PIDs (pid1|pid2|...|pidn)  Alarm (min:max:style:time*10ms:hold*sec) 
    ;---- -------------------------- ----------------------------------------- 
    PCM,  RPM 
    PCM,  VSS 
    PCM,  TP 
    PCM,  MAP 
    PCM,  MAF 
    PCM,  ECT,                       -40:110:97:1:0 
    PCM,  IAT 
    PCM,  SPARKADV 
    PCM,  KR,                        0:2:147:1:0 
    PCM,  GEAR 
    PCM,  TCCMODE 
    PCM,  EQIVRATIO 
    PCM,  IBPW1 
    PCM,  IBPW2 
    PCM,  LONGFT1 
    PCM,  LONGFT2 
    PCM,  HO2S11 
    PCM,  HO2S21 
    PCM,  MFTOTAL 
    -,    WO2ST1 
    -,    WO2ST2 
    -,    WO2LAM1 
    -,    WO2LAM2 
    -,    WO2AFR1 
    -,    WO2AFR2 
     
    ; _________________________________________________________________________ 
    *PSL_B 
    ; 
    ;Node PIDs (pid1|pid2|...|pidn)  Alarm (min:max:style:time*10ms:hold*sec) 
    ;---- -------------------------- ----------------------------------------- 
    PCM,  RPM 
    PCM,  VSS 
    PCM,  TP 
    PCM,  MAP 
    PCM,  MAF 
    PCM,  ECT,                       -40:110:97:1:0 
    PCM,  IAT 
    PCM,  SPARKADV 
    PCM,  KR,                        0:2:147:1:0 
    PCM,  GEAR 
    PCM,  TCCMODE 
    PCM,  EQIVRATIO 
    PCM,  LONGFT1 
    PCM,  LONGFT2 
    PCM,  SHRTFT1 
    PCM,  SHRTFT2 
    PCM,  HO2S11 
    PCM,  HO2S21 
    PCM,  HO2S12 
    PCM,  HO2S22 
    PCM,  MFTOTAL 
    -,    WO2ST1 
    -,    WO2ST2 
    -,    WO2LAM1 
    -,    WO2LAM2 
    -,    WO2AFR1 
    -,    WO2AFR2 
     
    *PSL_C 
    ; 
    ;Node PIDs (pid1|pid2|...|pidn)  Alarm (min:max:style:time*10ms:hold*sec) 
    ;---- -------------------------- ----------------------------------------- 
    PCM,  RPM 
    PCM,  VSS 
    PCM,  TP 
    PCM,  MAP 
    PCM,  MAF 
    PCM,  ECT,                       -40:110:97:1:0 
    PCM,  IAT 
    PCM,  SPARKADV 
    PCM,  EQIVRATIO 
    PCM,  IBPW1 
    PCM,  IBPW2 
    PCM,  LONGFT1 
    PCM,  LONGFT2 
    PCM,  SHRTFT1 
    PCM,  SHRTFT2 
    PCM,  HO2S11 
    PCM,  HO2S21 
    PCM,  HO2S12 
    PCM,  HO2S22 
    -,    WO2ST1 
    -,    WO2ST2 
    -,    WO2LAM1 
    -,    WO2LAM2 
    -,    WO2AFR1 
    -,    WO2AFR2 
     
    ; _________________________________________________________________________ 
    *PSL_D 
    ; 
    ;Node PIDs (pid1|pid2|...|pidn)  Alarm (min:max:style:time*10ms:hold*sec) 
    ;---- -------------------------- ----------------------------------------- 
    PCM,  RPM 
    PCM,  VSS 
    PCM,  TP 
    PCM,  MAP 
    PCM,  MAF 
    PCM,  ECT,                       -40:110:97:1:0 
    PCM,  IAT 
    PCM,  SPARKADV 
    PCM,  KR,                        0:2:147:1:0 
    PCM,  GEAR 
    PCM,  TCCMODE 
    PCM,  EQIVRATIO 
    PCM,  FTC 
    PCM,  FUELSYS 
    PCM,  LONGFT1 
    PCM,  LONGFT2 
    PCM,  SHRTFT1 
    PCM,  SHRTFT2 
    PCM,  HO2S11 
    PCM,  HO2S21 
    -,    WO2ST1 
    -,    WO2ST2 
    -,    WO2LAM1 
    -,    WO2LAM2 
    -,    WO2AFR1 
    -,    WO2AFR2 
     
    ; _________________________________________________________________________ 
    *PSL_E 
    ; 
    ;Node PIDs (pid1|pid2|...|pidn)  Alarm (min:max:style:time*10ms:hold*sec) 
    ;---- -------------------------- ----------------------------------------- 
    PCM,  RPM 
    PCM,  VSS 
    PCM,  TP 
    PCM,  MAP 
    PCM,  MAF 
    PCM,  DYNCYLAIR_M 
    PCM,  ECT,                       -40:110:97:1:0 
    PCM,  IAT 
    PCM,  SPARKADV 
    PCM,  KR,                        0:2:147:1:0 
    PCM,  GEAR 
    PCM,  TCCMODE 
    PCM,  SHIFTLAST 
    PCM,  TFMPRS 
    PCM,  TRQENG 
    PCM,  EQIVRATIO 
    PCM,  LONGFT1 
    PCM,  LONGFT2 
    PCM,  MFTOTAL 
    -,    WO2ST1 
    -,    WO2ST2 
    -,    WO2LAM1 
    -,    WO2LAM2 
    -,    WO2AFR1 
    -,    WO2AFR2 
     
    ; _________________________________________________________________________ 
    ; 
    ; PID Custom Units 
    ; ---------------------- 
    ; 
    ; PCU specifies the controller and PID for which to define a custom unit 
    ; Caption is the caption displayed on screen during BB logging (8 characters maximum). 
    ; Prec is the number of decimal places to display 
    ; Units is the display units name. 
    ; Op is the operator, one of: 
    ;   * = multiply 
    ;   / = divide 
    ;   i = invert_then_multiply 
    ; The metric value of the PID is multiplied, divided or inverted then multiplied by Factor. 
    ; Offset is then added. 
    ; 
    ; _________________________________________________________________________ 
    *PCU 
    ; 
    ;   PID         Caption   Prec  Units   Op  Factor        Offset 
    ;   ----------- --------- ----- ------- --- ------------- ------------- 
    PCM,MAF,        AirFlow,    1,  lb/m,   /,  7.559873, 
    PCM,MAP,        Manifold,   1,  psi,    /,  6.894757, 
    PCM,TFMPRS,     Trans,      1,  psi,    /,  6.894757, 
    PCM,TRQENG,     Torque,     1,  ftlb,   /,  1.355818, 
    PCM,VSS,        Speed,      0,  MPH,    /,  1.609344, 
    PCM,EQIVRATIO,  AFR,        3,  AFR,    i,  14.63, 
    PCM,ECT,        Coolant,    0,  °F,     *,  1.8,          32.0 
    PCM,IAT,        Intake,     0,  °F,     *,  1.8,          32.0 
    -,  T1,         T1,         0,  °F,     *,  1.8,          32.0 
    -,  T2,         T2,         0,  °F,     *,  1.8,          32.0

  6. #6
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    Quote Originally Posted by LS1_Dragster View Post
    OK, I tried it but I dont think I've got it right.

    When I record it only records AD1. The WBO's are not working. when I tell it that I have the LC-1 it comes up with no controller found or something like that.

    What steps do I need to do in order for this to work correctly?

    I messed with the options.ini but still lost....
    Did you use the May 19th BBL update...?

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

    Default

    Quote Originally Posted by LS1_Dragster View Post
    when I tell it that I have the LC-1 it comes up with no controller found or something like that.

    What steps do I need to do in order for this to work correctly?
    The first step is making sure you get something other than "Controller not found" when you are attempting to log your LC-1's serial data.

    Make sure your connection from the LC-1 is correct.
    http://forum.efilive.com/showthread.php?t=8115

    When the LC-1 is connected to FlashScan correctly, you will see the left orange LED flashing to indicate that data is being received from the LC-1. If the left orange LED is not flashing then the connection between the LC-1 and FlashScan is probably incorrect.

    Once you have that LED flashing (i.e. data is being transmitted), you need to display the WO2 data on FlashScan's screen. While that screen is being displayed you can press the following keys:
    Backspace = cycle through the various supported controllers - press backspace until Innovate is displayed on the top line.
    OK = toggle between (1) and (2), select (1), which means you only have 1 LC-1 connected.

    Once you can see valid data then you know the connection is good.
    Then you can log the PID EXT.WO2AFR1

    Regards
    Paul
    Before asking for help, please read this.

  8. #8
    Lifetime Member
    Join Date
    May 2008
    Posts
    389

    Default

    Paul, I was not aware that I need to do anything with the serial cable. I just have the brown and white wire going to A1. I do see the voltage change so they are talking.

    So I have to hook up the serial cable too?

    When I take the recorded data from the BBL and try the AutoVE the PID dyncylair_dma will not highlight and give me values.

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

    Default

    I know it is frustrating not having up to date manuals but the latest beta firmware and software is moving too fast for the doco to be kept up to date. For the time being (until it is released publicly and officially) this forum is where you're going to get the information you need.

    There are two ways of logging AFR data from the LC-1 (and many other wide band controllers):
    1. Using the controller's analog AFR signal and connecting that to FlashScan's A1 or A2 A/D input (the orange plugs).
    2. Using the controller's digital (rs232 serial) data and connecting that directly to FlashScan's serial input (next to the USB plug).

    You only need to use one of those methods not both. The serial input is the easiest and most accurate to install and log. Take a look at the wiring diagram in the link I posted previously. That explains how it needs to be wired up.

    The AFR display on FlashScan's screen is ONLY for the digital serial input - it does not work with the analog AFR inputs.

    To get data linked and highlighted in the Tuning Tool maps, you need to make sure you log the correct PIDs. Those PIDs vary per vehicle type and possibly per wide band controller type.

    What engine type are you working on? From your handle, I presume an LS1?
    Let me know and I will tell you how to set it up.

    Regards
    Paul
    Before asking for help, please read this.

  10. #10
    Lifetime Member
    Join Date
    May 2008
    Posts
    389

    Default

    joecar - I've been flooding you guys with questions the past week or so. I didnt know you need all the details for each question!

    Here it is:

    I'm using SD mode
    OS 0202003 V3
    2001 Firbird But now in a dragster with a powerglide trans

    I want to record/monitor all the PID's from your AutoVE instructions

    I want all other vehicles/PID's gone off the FlashScan (I did figure this out with the options.ini)

    I want it to be as simple aas it gets, this is a drag only setup

    I want it to log the data on the FlashScan only then upload to the laptop after the run. (I got this figured out, it's just not recording the right PID's for the AutoVE)

    I would like the FlashScan to default to the 1 and only PMM file everytime it's turned on so I dont have to do that manually.

Page 1 of 3 123 LastLast

Similar Threads

  1. Replies: 32
    Last Post: June 24th, 2010, 05:21 AM
  2. AutoVE take 2.
    By waterbug1999 in forum Gen III V8 Specific
    Replies: 0
    Last Post: July 19th, 2009, 07:29 AM
  3. PID for AutoVE
    By Garry in forum FlashScan V2 BB Logging
    Replies: 3
    Last Post: May 20th, 2008, 08:23 AM
  4. Success with logging AutoVE
    By Gelf VXR in forum Gen IV V8 Specific
    Replies: 0
    Last Post: February 22nd, 2008, 12:12 AM
  5. AutoVE, What next?
    By dbaxter_ss in forum General (Petrol, Gas, Ethanol)
    Replies: 1
    Last Post: April 11th, 2006, 07:45 AM

Posting Permissions

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