Printable View
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
Lee, yes.
Cheers,
Joe
:cheers:
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....
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....
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
Did you use the May 19th BBL update...?Quote:
Originally Posted by LS1_Dragster
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.Quote:
Originally Posted by LS1_Dragster
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
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.
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
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.
The next update of the FlashSCan BBL firmware has some new hotkeys:Quote:
Originally Posted by LS1_Dragster
Ctrl+F1 - select predefined PID selection 1.
Ctrl+F2 - select predefined PID selection 2.
Ctrl+F3 - select predefined PID selection 3.
Ctrl+F4 - select predefined PID selection 4.
On/Off - Start data logging.
So after plugging in FlashScan, you'd only need to press two keys to start logging:
Ctrl+F1, then the Start/Stop button.
Note: The Start/Stop button is the one to the right of the Ctrl key.
More info on your AutoVE requirements coming...
P.S. Just for your info, the current beta software is not how the final product will operate. The final released software will have an easy to use PC/laptop based configuration program. You won't have to mess around with editing files. You just need to bear with this manual procedure for a little while longer until the PC/laptop software is done.
Regards
Paul
If you take a look in the file:
\Program Files\EFILive\V7.5\Configuration\cal_link.txt
you will see the setup for the LS1 VE table B1010
What that means is, you need to log SAE.RPM and SAE.MAP and one ofCode:;Main VE Table
B0101.ROW=SAE.RPM
B0101.COL=SAE.MAP
B0101.RRR=CALC.BEN1,CALC.BEN2,CALC.BEN_AUT1,CALC.BEN_AUT2,CALC.BEN_FJO1,CALC.BEN_FJO2,
CALC.BEN_LC11,CALC.BENLC12,CALC.BEN_LM11,CALC.BEN_LM12,CALC.BEN_PLX1,
CALC.BEN_PLX2,CALC.BEN_TE1,CALC.BEN_TE2,CALC.BEN_WBC1,CALC.BEN_WBC2
CALC.BEN1,CALC.BEN2,CALC.BEN_AUT1,CALC.BEN_AUT2,CA LC.BEN_FJO1,CALC.BEN_FJO2,CALC.BEN_LC11,CALC.BENLC 12,CALC.BEN_LM11,CALC.BEN_LM12,CALC.BEN_PLX1,CALC. BEN_PLX2,CALC.BEN_TE1,CALC.BEN_TE2,CALC.BEN_WBC1,C ALC.BEN_WBC2
in order to use AutoVE and/or RTACS.
For an LC1 in analog mode (connected to A1), you would need to log:
CALC.BEN_LC11 (or if you connected it to A2, then you would log CALC.BEN_LC12).
The prerequisites for CALC.BEN_LC11 are:
GM.AFR for LS1 (this PID is different for E40, E38 and E67)
EXT.AD1
CALC.AFR_LC11
The prerequisites for CALC.BEN_LC12 are:
GM.AFR for LS1 (this PID is different for E40, E38 and E67)
EXT.AD2
CALC.AFR_LC12
For ANY wide band in digital mode (connected to RS232), you would need to log:
CALC.BEN1 (if you had 2 LC1s then you would ALSO log CALC.BEN2.
The prerequisites for CALC.BEN1 are:
GM.AFR for LS1 (this PID is different for E40, E38 and E67)
EXT.WO2AFR1
When you select a CALC.xxxx PID, you can see what other PIDs you need to select that it depends on by right clicking on it in the [PIDs (F8)] tab page and selecting More info...
For the High/Low octane spark maps:
Which means you need to log SAE.RPM and one of:Code:B5913.ROW=SAE.RPM
B5913.COL=GM.DYNCYLAIR_DMA,GM.CYLAIR_DMA,GM.DYNCYLAIR,CALC.CYLAIR
GM.DYNCYLAIR_DMA,GM.CYLAIR_DMA,GM.DYNCYLAIR,CALC.C YLAIR
I recommend using GM.DYNCYLAIR_DMA
Regards
Paul
Quote:
Originally Posted by Blacky
How do I tell the BBL to log GM.DYNCYLAIR_DMA ??? This is the problem, it does not record it. When I have the laptop logging it does record it! Does this make sense?
Make sure you specify jut DYNCYLAIR_M in the Options.ini file.Quote:
Originally Posted by LS1_Dragster
The BBL PIDs are specified without the GM. SAE. E38. prefix and the DMA PIDs are changed from _DMA to just _M
Regards
Paul
OK - Done.
Now, just to let you know and give you an example of how "I FEEL" you should've answered:
Make sure you specify just DYNCYLAIR_M in the options.ini file, for example add this line to your PID section:
-, DYNCYLAIR_M
So your new section should look like this:
*PSL_LS1
;
;Node PIDs (pid1|pid2|...|pidn) Alarm (min:max:style:time*10ms:hold*sec)
;---- -------------------------- -----------------------------------------
PCM, ECT, -40:110:1:1:0
PCM, IAT
PCM, MAP
PCM, RPM, 0:6500:2:1:0
PCM, SPARKADV
PCM, TP
PCM, AFR
PCM, KR
PCM, AD1
-, DYNCYLAIR_M
This type of information will eliminate the guess work and help give us an idea of how it should look. Then in the future we'll know exactly what to do! I hope this makes sense...
I do appreciate your help and I hope I'm not too big a pain.
Lee
Lee,Quote:
Originally Posted by LS1_Dragster
I read pretty much every post, I can't remember each person's setup, so you will be helping yourself if you include details in each new thread (and save me from having to dig around)... any user browsing will be more likely to chime in with an answer if they see details.
Cheers
Joe
:cheers:
Steep learning curve Lee, good to see your grabbing the bull by the horns so to speak!
Your pulling into shape very quickly now!
I bet your line of attack has changed since your first post...:)
Hows the Dragster coming along? I bet she sounds a bit better now!
Sounds like you have had a couple of passes in it? How did you go?
Next weekend we have the Australian Winter Nationals hear at my home track, Willowbank. Sorry rest of Aus, yes it's here again then it's heading to Sydney I think, It's my favorite time of year where the misses gives me a reprieve.
Cheers
Mick
Hi Lee,
You could just edit your signature (click on "User CP" at upper left of forum page) to include something similar to:
2000 LS1, 02020003, PRC 2.5, MS3, Vic Jr. intake, stock TB/MAF, PG, 4500 stall
If you log the analog WB signal, you can add the AFR/BEN calc pids in when you view the log using the scantool on your laptop (open the log, select the AFR and BEN pids for your wideband, do File->Save).
If you can get your Auto VE done, you will have these benefits:
- OLSD throttle response will be excellent,
- the AFR you command in B3647 and B3618 will be the AFR you actually get (you can set the commanded AFR to give the best TQ/HP from your experience or from published data... no guessing around required... saves you a lot of time at the track...),
- you will be confident that the AFR will safe (make best TQ/HP and protect motor).
In the other thread you ask about power valve and pump shot "tables"... since you're going from zero throttle to WOT I don't think those yet-to-be-found tables matter... a dialed in VE table with a suitable commanded AFR (B3647, B3618) will give you very good results regardless.
Like MICK said, it is a steep learning curve... but you're doing fine (time deadlines are a great motivator... :D)...there is alot of reading involved (90% reading, 10% application) ...keep asking questions, you're not a pain, sometimes things "move" slowly on the forum, but they will eventually be answered.:cucumber::banana:
Cheers,
Joe
:cheers:
Thanks guys, I feel I have a pretty good idea how things work now, just enough to go crazy.
No passes on the dragster yet, that's the problem. My wife has been patient with me but the season is passing her by and she wants to get out there and race. So the home front is not smooth right now!
Right now all I can do is zing the RPM and adjust the MAP in those areas, this way I should be able to at least get a smoother MAP towards WOT then I have now. It runs far better and getting better all the time.
One thing that really hurts compared to the Holley Commander is no real time adjusting. I know there is roadrunner but I just dont want to learn anymore software/hardware at this time.
It will be at the track this Friday even if I have to drag it down the strip with the golf cart......
Question - in the options.ini I want to record the MAP in kPa instead of inHg, what do I change this setting to?
PCM,MAP, M'Fold, 1,psi, /, 6.894757,
This way the logged data will match the tun program.
V2 already records MAP in kPa.
In your scantool, on the PIDs tab, rightclick on MAP and select Metric.
Hi, I hope you guys can help me. I just did the bbl upgrade, upgraded the 2.4.72, then 5.8.18fw.
I have the V7.5.74 and V8.1
I'm trying to log with an LC1-serial cause my A/D volt inputs are burnt. Now I'm stuck trying to find why I'm missing an Option.ini file, it also seems I've lost all my VINs.
Any help would be much appreciated....
The ini file I presume you're looking for is Options.ini. That is meant to be in the folder:
\Program Files\EFILive\V8.1\Config
however, it got misplaced in the last software update and now it gets installed in the folder: \Program Files\EFILive\V8.1\Programs
You can check which licenses on your V2 cable are used/unused by using the menu option (on FlashScan): F4 Options -> F3 Licensing -> F2 VIN Licenses.
Regards
Paul
Quote:
Originally Posted by cyclerage