Calc.VET question

[FeetDry]

I'm trying the calc.VET tutorial w/ OS 12212156. I'm not getting very far. The scanner is erroring out right from the start. I don't understand the error, but I think the setup is missing something. I'm not sure what I'm doing, so I'm getting lost fairly quickly.

I have a few Q's:
This OS does not support the GM.EQUIVRATIO PID. Do I really need it? I'm not seeing it used in the calc_pids.txt. (The tutorial say's, I need it.)

Do I need to write a substitute calculation for it (because I don't have that PID)?
Somthing like EqRatio= Commanded_Stoch/WB_Lamda? or EqRatio= GM.AFR/WB_Lamda? or EqRatio= 14.7/WB_Lamda?

Is there some other work around for the lack of a GM.EQUIVRATIO PID?

Does displacement() read the # from the "log file info" screen?
Are there other funtions that will grab these #'s? Something like: vin(), or diffRatio()

I'm thinking of doing something like:
*CLC-00-222 #displacement selection in cc
factor 2600 5700 .4 "iff({GM.ENGSIZE_DMA = 0}, {5328}, {iff({GM>ENGSIZE_DMA = 1},{5669},{0}))"

Thanks

[WeathermanShawn]

Dry:

That OS supports GM. EQIVRATIO, usually found under the Fuel Tab.

As always make sure you are using the latest Software/Firmware Updates. Sometimes you have to go out to the vehicle, turn the ignition key to on, and then 'Validate' your Pids.

If the problem exists, we may have to submit a request for support. You should not have to do what you are proposing..

[joecar]

GM.EQIVRATIO:

(spelled without U)

GM.EQIVRATIO is supported by 12212156, look at the PIDs tab again...
uncheck Supported, then click on the Caption column heading to sort alphabetically on that column, scroll down it is there;

what VIN does the scantool display on the status bar at the bottom...?

displacement():

the Calc.VET tutorial says this:


A. Set Displacement: open a Log File, go Edit->Log File Information->Vehicle Options, and next to Engine enter the displacement in cc, click Ok, and save the log file. This matters only if you're planning to use [%] units for VE.



What year/model/vehicle...?

[FeetDry]

Once I did the Scanner->Info->ValidatePIDs, now I have the GM.EQUIVRATIO.
(My mistake. I thought connecting to the PCM would be enough.)

The "displacement" questions,...
I was trying to come up w/ a way of having the PCM tell the CALC what the displacement is. i.e. Maybe use another PID or the VIN.

Thanks

[WeathermanShawn]

If you are only tuning your car, replace displacement with engine size in Liters (e.g. 5.669).

Displacment was added as a convenience to tuners utilizing multiple engine sizes. Inputting engine size into the formula is probably the easiest way..:)

[FeetDry]

Thanks, I had changed the CALC to use the engine size in cc's. i.e. The log info used cc's.
I will switch it to Liters.

I'm finding that I have to enter the engine size info every time I create a log file. If I open an existing log file and set/save it, the next time I open it, it is blank again. I find this to be a hassle. The PCM knows the engine size. If possible, I'd like to make things easier. Any idea if the GM.ENGSIZE_DMA enumerations change from OS to OS? (Or is there one master list?) i.e Does 0= 5.3L, always?

[joecar]

If you use [g*K/kPa] for VE units then you don't need displacement at all.

[WeathermanShawn]

I'm finding that I have to enter the engine size info every time I create a log file. If I open an existing log file and set/save it, the next time I open it, it is blank again. I find this to be a hassle.

See I have not found that to be the case if you actually log. Have you found that to be the case when you actually log?

You can make this harder than need be. For example: "{SAE.MAF.gps}*({GM.DYNAIRTMP_DMA.C}+273.15)/({SAE.RPM}*{SAE.MAP.kPa})*3445.2/displacement()"

Just put 4.294 in for displacement, or better yet use the default units..

[FeetDry]

My idea of using GM.ENGSIZE_DMA doesn't appear to work. It may be emumerated by GM, but it appears to be interpreted by EFIlive. This PID reports to "unknown". My 4.3L is not in the "size" list. It doesn' tell me what the actual number is. If the number is known (in a list somewhere) the PID will display 5.3, or 4.8,.. Rather than a 0, or 1, or 2,....

Shawn,
I have not logged w/ the engine size info populated. It is grayed out before I can start the log. And I could not set it after the log was done. So I thought the zero (unset size info) was causing a divide-by-zero error. i.e. I thought this was the cause of my earlier log-crash error. It is no longer crashing, so I can't dup the failure.

Joe,
I need to understand this better, to understand your comment. I think I understand what you are saying. I need to look at the details a bit more.

[Taz]

Hello FeetDry,

I have used the CALC VET technique with the VE units as g*K/kPa, and in percent (%). If using percent, when you open the log for the first time, you will need to input engine displacement, resave, and close the file. When you reopen it the second time, the VE data (%) should be displayed.

Vehicle information is entered under the "Edit" menu ... "Log file information" .... "Vehicle options" ....

Just checked using a 2002 truck VIN, the 4.3 L engine (4294 CC) is in the drop down menu. If your are not seeing this with your VIN (which I believe was originally linked to a Black Box Vortec PCM), try temporarily using a 2001 or later S10 VIN.


Regards,
Taz

[joecar]

...

Joe,
I need to understand this better, to understand your comment. I think I understand what you are saying. I need to look at the details a bit more.

in scantool: use the CALC.VET that has units g*K/kPa.

in tunetool: go Edit->Properties and set VE units to g*K/kPa (only has to be done one time).

[FeetDry]

I updated my V7.5, V8, bootblock, & V2 firmware.
I'm not able to see any GM pids, in the scanner pid list. I have the SAE, the CALC, and the EXT pids, but not one GM pid. (They were there B4 the update.)
"Validate pids" runs, but doesn't change anything.

What am I doing wrong?

Scan/Tune: 7.5.7 build 170
BootBlk: 2.7.2
Firmware: 2.7.14

[WeathermanShawn]

Make sure all the 'Unsupported Pids' are checked.

Post up a screenshot of your problem and your calc_pids.txt file.

Thanks..

[FeetDry]

http://tinypic.com/r/9hq90w/7 http://tinypic.com/r/9hq90w/7
http://tinypic.com/r/ezn1vk/7 http://tinypic.com/r/ezn1vk/7

The calc_pids.txt file is basically WmanShawn's file w/ one change, (displacement).

I believe you are referring to the "supported" check box. It is unchecked (show all).

[WeathermanShawn]

You do not have the GM.DYNAIRTMP Pid selected. If you right-click on any of the red-X Pids, it will tell you what other Pids you need selected.

What is your OS? Have you Validated the Pids per these instructions?:

I. Validate Pids:

1. Connect Scan Tool to your Vehicle (Select Controller)
2. Turn Ignition Key to 'On'
3. Scan Tool>>Info>>Validate Pids

If you have done all that, then I am assuming your OS may not support all the Pids. That is a little over my head, so post up the information requested and we will go from there.

[FeetDry]

I replaced the calc_pids.txt file w/ an empty file. There was no change. (The X-out calc pids are not in the list. Still no GM pids.)
None of the PID lists have GM pids in them. i.e. Default LS2 Metric.pid
Notice the PID count @ the bottom of the PID screen, only 44. A very small number.

I did the validate pids routine. There was no change.

OS=12212156
All the pids in "your" calc.vet list are supported. I have a scan I took B4 the SW update.

Thanks for trying,..

[WeathermanShawn]

Isn't your Controller LS1B?

GM.DYNAIRTMP.DMA is found under the 'Tune' tab. Why are you using the Default LS2 Metric pid list?

[WeathermanShawn]

Also, see Paul's post here: http://forum.efilive.com/showthread.php?16756-Public-Release-Update-July-03-2011&p=149621&viewfull=1#post149621

[FeetDry]

Yes, it is an LS1B controller.
I mentioned the fact that there are no GM pids showing in the Default LS2 Metric lid list as well.
i.e. My scanner is not "seeing" any GM pids, regardless of the PID list selected.

I don't have the GM.DYNAIRTMP pid selected, because there are no GM pids to select.

[FeetDry]

This is the PID list that I am opening inside of the scanner: (WmanShawn_CALC.VET.pid)

[Parameters]
CALC.LTFTBEN=1,4307
CALC.PE=1,4308
CALC.SELBEN=1,4315
CALC.VEN=1,4317
CALC.VET=1,4320
CALC.WO2BEN=1,4321
EXT.WO2LAM1=1,4396
GM.CYLAIR_DMA=1,4481
GM.DYNAIRTMP_DMA=1,4503
GM.ENGSIZE_DMA=1,4524
GM.EQIVRATIO=1,4531
GM.HO2S11=1,4634
GM.HO2S21=1,4632
GM.MAFFREQ=1,4735
SAE.ECT=1,5126
SAE.FUELSYS=1,5136
SAE.IAT=1,5134
SAE.LONGFT1=1,5142
SAE.LONGFT2=1,5143
SAE.MAF=1,5144
SAE.MAP=1,5145
SAE.RPM=1,5165
SAE.TP=1,5172

[FeetDry]

Here is the *.vpl (valid pid list) that I ran a few min ago:
(Notice the lack of any GM pids. I ran it many times, and still no GM pids.)

EXT.AD1=Dynamic
EXT.AD2=Dynamic
EXT.AD3=Dynamic
EXT.AD4=Dynamic
EXT.SW1=Dynamic
EXT.SW2=Dynamic
EXT.TEMP1=Dynamic
EXT.TEMP2=Dynamic
EXT.WO2AFR1=Dynamic
EXT.WO2AFR2=Dynamic
EXT.WO2LAM1=Dynamic
EXT.WO2LAM2=Dynamic
EXT.WO2ST1=Dynamic
EXT.WO2ST2=Dynamic
SAE.AIR_STAT=Dynamic
SAE.AUXIS=Dynamic
SAE.ECT=Dynamic
SAE.FUELSYS=Dynamic
SAE.IAT=Dynamic
SAE.LOAD_PCT=Dynamic
SAE.LONGFT1=Dynamic
SAE.LONGFT2=Dynamic
SAE.MAF=Dynamic
SAE.MAP=Dynamic
SAE.MIL_DIST=Dynamic
SAE.MONDTC=Dynamic
SAE.O2S11=Dynamic
SAE.O2S12=Dynamic
SAE.O2S13=Dynamic
SAE.O2S21=Dynamic
SAE.O2S22=Dynamic
SAE.O2SLOC=Dynamic
SAE.OBDSUP=Dynamic
SAE.RPM=Dynamic
SAE.SHRTFT1=Dynamic
SAE.SHRTFT2=Dynamic
SAE.SPARKADV=Dynamic
SAE.TP=Dynamic
SAE.VSS=Dynamic

[WeathermanShawn]

Its a little over my head. I have not had that problem or heard anyone else having it.:confused:

I have Pid list not validate until I log. If you really have that occurring, post up in the latest software update thread.

Thanks..

[FeetDry]

I think you are referring to the comment about some pids showing as invalid until the logging start, I'm not seeing that. w/ or w/o logging, I'm not seeing any GM pids.
I'll post in Blacky's thread.

[joecar]

Are you logging with V7 or with V2...?

[FeetDry]

My hardware is a V2. My software is V7.5 & V8. The V8 SW is not seeing any GM pids as well.
I sent Paul the log file.

[Blacky]

The trace file shows this:

09:02:29.578|1548|LoadConfig file: C:\Program Files\EFILive\V7.5\Configuration\sae_generic.txt
09:02:29.578|1548|ClearConfig
09:02:29.734|1548|Calc PIDs filename: C:\Junk\My Stuff\CAR Stuff\EFILive\V7.5\User Configuration\calc_pids.txt
09:02:29.734|1548|LoadFile (sae_generic.txt) Section (FILE)
09:02:29.734|1548|LoadFile (calc_pids.txt) Section (FILE)
09:02:29.734|1548|LoadFile (sae_generic.txt) Section (ENHANCED)
09:02:29.734|1548|Enhanced file: C:\Program Files\EFILive\V7.5\Configuration\
09:02:29.734|1548|LoadFile (sae_generic.txt) Section (UNITS)
09:02:29.750|1548|LoadFile (calc_pids.txt) Section (UNITS)

That line in red should display as:

09:02:29.734|1548|Enhanced file: C:\Program Files\EFILive\V7.5\Configuration\gm_enhanced.prn

For some reason, the EFILive software is not loading the enhanced PIDs.
Can you please try this:
Delete the folders:
\Program Files\EFILive\V7.5
and
\Program Files\EFILive\V8

Re-install the software from the downloaded install executables from our web site here:
http://www.efilive.com/index.php?option=com_content&view=article&id=48&Itemid=133

Don't run the "Check for New Update" option for either V7 or V8.
Then check to make sure the software loads and displays the GM enhanced PIDs.

If you're feeling brave, then perform the "Check for New Update" for V7.5 and V8, then re-run the software and see if the GM enhanced PIDs are still available.
If not, then that points to the auto-update causing the problem. (Let me know how it goes).

Regards
Paul

[FeetDry]

Thanks for the explanation. I thought it odd that there was no mention of GM pids on the log. But I was looking for a TXT file, not a PRN. The file is & was there. Apparently it just wasn't being called.

Originally I did run the "update" to get the latest version.

I can't seem to duplicate the problem.
I del (renamed) the V7.5 & V8 program folders. Dwnld'd the latest V7.5 from the WWW. The GM pids are there. Ran the 7.5 update, the GM pids are there. Dwnld'd the latest V8 from the WWW. The GM pids are there. Ran the 8 update, the GM pids are there.

I have not connected to a vehicle yet, but I can tell by the pid count (I see 111 now, was 41), the GM pids are there.

I can't remember anything odd happening during my original "update". I wish I could explain it for you, but I can't say what the cause was.

I suspect all is well again. I'll connect in a few min.

Thanks

[Blacky]

I can't remember anything odd happening during my original "update". I wish I could explain it for you, but I can't say what the cause was.

It may have something to do with whether or not you run the install as administrator (i.e. right click on the exe and select Run as Administrator).
There may be some situations where certian files do not get updated/overwritten if you don't do it "as administrator", yet at other times even though you're not "as administrator" the files may still get updated/overwritten.
That's just a guess based on other customers' stories that have had install problems.

Regards
Paul

[DrX]

I had the same issue today after I installed the current builds followed by the update process. I re-installed without updating and now have all my PIDs back. Prior the the 2nd install, the PID validation process flashed by very quickly and didn't seem to really do anything. Module validation was pretty much the same.