Calc.VET question

[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.

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?opt...=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.