PDA

View Full Version : V5 "better" than V6 - what about V7?



emarkay
July 10th, 2004, 05:46 AM
I have seen a few posts where V6 won't connect or function with as much features as V5. If this is this true, why?
Will this be remedied in V7?
Regardless of "Enhanced PIDS" I would EXPECT ALL EFILive versions to function as a "generic" OBDII scan tooll, and whatever enhanced PIDS are common across various GM lines, to be supported equally on each vehicle.

I presume it's a software limitation as the B&B interfaces are unchanged between versions.

Will the Flash Scan interface present any problems with compatibility with"other than LSX GM" cars?

Anyone care to clarify?

MRK

Blacky
July 10th, 2004, 07:42 AM
V6 *should* have all the functionality of V5 and more (except for spark/fuel maps which have not been implemented in V6 yet).
V7 *should* have all the functionality of V6 and more.

If some functionality is missing from a previous version then we will fix it.
We just need more people to report the problem(s) so we can fix them.

So if anyone has logged generic PIDs successfully on a non-LS1 using EFILive V5 but gets an error when trying to log the same generic PIDs in V6, please post a description of the problem in this thread - thanks.

The only thing I can think of (apart from a programming error/bug) is that V6 tries to guess a lot more info about the vehicle from the various identifiers stored in the PCM. It may be that it is not seeing "expected" values for non-LS1 vehicles and refusing to process the data.
Whereas V5 just continued on regardless.

Regards
Paul

Highlander
July 11th, 2004, 01:19 PM
How hard is it to make generic communications with other standards? PWM and iso? so have a generic scanner using atap hardware but not software.

Blacky
July 11th, 2004, 08:07 PM
How hard is it to make generic communications with other standards? PWM and iso? so have a generic scanner using atap hardware but not software.

Theoretically it *should* not be difficult at all.
However the non-GM scanning would only work with AT123 and/or ATU interfaces. It would not work with AT1 interfaces nor FlashScan.
It is not a priority right now.

Regards
Paul

deezel
July 11th, 2004, 11:42 PM
I have found v6 to be a bit less friendly than v5. But some better features. Here are some comments and examples:
v5 - I like the look of the interface/dash. I like the separate PIDs tab with pre-configured calculated PIDs and the ability to edit PIDs directly from the interface. I like the maps. I like the consistent 0.1 second data log intervals (frame spacing) in 10X24 mode. Very few dropped frames.
v6 - I like the LS1-specific fuel trims and other info. I like the more detailed information about the PCM. I like the DTC/emissions scanner features of v6.
Some issues with v6:
- still some kinks with bi-di controls (specifically cyl balance test doesnt work, on my truck anyways)
- more dropped frames, even with PCMCIA hi-speed serial port
- less PIDs available than v5 (DYNAIR for example does not appear for my truck in v6, but shows and works in v5) I like being able to see all of the possible PIDs in v5 with red X's through the unsupported ones.

I will email which PIDs show up in both v5 and v6 on my truck as soon as I get a chance to go put the scanner on it.

deezel
July 13th, 2004, 12:42 AM
Ok, I feel like a dumba$$ now. :roll:
After printing out the two lists of PIDs to send to Paul, I finally found most of the "missing" PIDs from v5. Many were renamed or re-listed. The DYNAIR I was looking for is now DYNCYLAIR and listed under "P" for Predicted Air Flow instead of "D" for Dynamic air flow.
I will send the PIDs lists anyway, might be useful.
regards

Blacky
July 13th, 2004, 01:10 AM
Ahh sorry about that - we shortened a whole lot of PID names during the upgrade to V6, here's the complete list. (EFIlive uses this list to convert the PID names "on the fly" when loading in V5 log files.)



V5 V6
------------------------------------ -----------------------------------
"GM.LS1.FLAG00" GM.STATE00
"GM.LS1.FLAG01" GM.STATE01
"GM.LS1.FLAG02" GM.STATE02
"GM.LS1.FLAG03" GM.STATE03
"GM.LS1.FLAG04" GM.STATE04
"GM.LS1.FLAG05" GM.STATE05
"GM.LS1.FLAG06" GM.STATE06

"GM.LS1.PRND" GM.PRND
"GM.LS1.O2NV" GM.HO2SNVC
"GM.LS1.O2S HEATER" GM.HO2SC
"GM.LS1.FLAG15" GM.STATE15
"GM.LS1.FLAG16" GM.STATE16

"GM.LS1.ICV FAIL" GM.VOLTFAIL

"GM.LS1.MAF B" GM.MAF
"GM.LS1.ICV" GM.VOLTS
"GM.LS1.MAP B" GM.MAP
"GM.LS1.TPS" GM.TPS
"GM.LS1.A/C PRESS" GM.ACP
"GM.LS1.O2S 11" GM.HO2S11
"GM.LS1.O2S 12" GM.HO2S12
"GM.LS1.O2S 21" GM.HO2S21
"GM.LS1.O2S 22" GM.HO2S22
"GM.LS1.EGRS" GM.EGRS
"GM.LS1.ALT-F" GM.ALT-F
"GM.LS1.FTP" GM.FTPS

"GM.LS1.TP" GM.TP
"GM.LS1.EGR" GM.EGR
"GM.LS1.FUEL LEVELS" GM.FLS
"GM.LS1.EOPS" GM.EOPS

"GM.LS1.ECT START" GM.ECT1ST

"GM.LS1.EVAP DC" GM.EVAPDC
"GM.LS1.IAC" GM.IAC
"GM.LS1.EGR DC" GM.EGRDC

"GM.LS1.LONG TERM FT CELL" GM.FTC
"GM.LS1.IDLEDES" GM.RPMDES
"GM.LS1.EGRDES" GM.EGRDES
"GM.LS1.BARO" GM.BARO
"GM.LS1.EOL" GM.EOL

"GM.LS1.ERT" GM.RUN_TIME
"GM.LS1.KNOCK" GM.KR

"GM.LS1.EGR PINTLE" GM.EGRPINTLE
"GM.LS1.EGR TEST" GM.EGRTEST
"GM.LS1.EGR PINTLE ERR" GM.EGRERROR

"GM.LS1.MF CYL IDX" GM.MFCYLIDX
"GM.LS1.MF CYL IDX LVL" GM.MFCYLIDX1
"GM.LS1.MF REV IDX" GM.MFREVIDX
"GM.LS1.ACCEL/DECEL" GM.ACCDEC
"GM.LS1.MF CYCL DELAY" GM.MFCYCLDLY
"GM.LS1.MF CURR STAT" GM.MFCSTAT
"GM.LS1.MF CYL5" GM.MFCYL5C
"GM.LS1.MF CYL6" GM.MFCYL6C
"GM.LS1.MF CYL7" GM.MFCYL7C
"GM.LS1.MF CYL8" GM.MFCYL8C

"GM.LS1.MF:ABNORMAL" GM.MFABNORMAL
"GM.LS1.MF:SPECIAL" GM.MFSPECIAL
"GM.LS1.MF CAT TEST A" GM.MFCAT
"GM.LS1.MF CAT TEST B" GM.MFCATCLR
"GM.LS1.EM TEST A" GM.MFEM
"GM.LS1.EM TEST B" GM.MFEMMAX
"GM.LS1.MF HIST CYL 5" GM.MFCYL5H
"GM.LS1.MF HIST CYL 6" GM.MFCYL6H
"GM.LS1.MF HIST CYL 7" GM.MFCYL7H
"GM.LS1.MF HIST CYL 8" GM.MFCYL8H

"GM.LS1.MF TOTAL" GM.MFTOTAL
"GM.LS1.MF HIST CYL 1" GM.MFCYL1H
"GM.LS1.MF HIST CYL 1" GM.MFCYL2H
"GM.LS1.MF HIST CYL 1" GM.MFCYL3H
"GM.LS1.MF HIST CYL 1" GM.MFCYL4H
"GM.LS1.MF CYL1" GM.MFCYL1C
"GM.LS1.MF CYL2" GM.MFCYL2C
"GM.LS1.MF CYL3" GM.MFCYL3C
"GM.LS1.MF CYL4" GM.MFCYL4C
"GM.LS1.STFT AVG B1" GM.SHRTFTAVG1
"GM.LS1.LTFT AVG B1" GM.LONGFTAVG1
"GM.LS1.STFT AVG B2" GM.SHRTFTAVG2

"GM.LS1.O2 RL-LR 11" GM.O2RLLR11
"GM.LS1.O2 RL 22" GM.O2RL21
"GM.LS1.O2 LR 21" GM.O2LR21
"GM.LS1.O2 LR 11" GM.O2RL11
"GM.LS1.O2 AVG BIAS 12" GM.O2BIAS12
"GM.LS1.O2 AVG BIAS 11" GM.O2BIAS11

"GM.LS1.O2 AVG BIAS 21" GM.O2BIAS21
"GM.LS1.MF TOTAL FAIL" GM.MFFAIL
"GM.LS1.MF TOTAL OK" GM.MFPASS
"GM.LS1.MF REV IDX LVL" GM.MFREVIDX1
"GM.LS1.MF DATA CYCL" GM.MFCYCLE

"GM.LS1.WU EM FAULTS" GM.WUEMPASS
"GM.LS1.WU NON EM FAULTS" GM.WUPASS
"GM.LS1.ODO LAST" GM.ODOCLR
"GM.LS1.ODO FIRST SET" GM.ODOFIRST
"GM.LS1.ODO LAST SET" GM.ODOLAST
"GM.LS1.FF COUNTER" GM.FFCOUNT
"GM.LS1.FF PASS COUNTER" GM.FFPASS
"GM.LS1.FF NOT RUN COUNTER" GM.FFNOTRUN
"GM.LS1.LTFT AVG B2" GM.LONGFTAVG2
"GM.LS1.TTA 22" GM.TTA22

"GM.LS1.LR TT 11" GM.O2LRTT11
"GM.LS1.LR TT 21" GM.O2LRTT21
"GM.LS1.RL TT 11" GM.O2RLTT11
"GM.LS1.RL TT 21" GM.O2RLTT21
"GM.LS1.O2 RL-LR 21" GM.O2RLLR21

"GM.LS1.MAF RAW" GM.MAFFREQ
"GM.LS1.24x RPM" GM.RPM24x
"GM.LS1.TTA 11" GM.TTA11
"GM.LS1.TTA 12" GM.TTA12
"GM.LS1.TTA 21" GM.TTA21
"GM.LS1.BPW AVG 1" GM.IBPW1
"GM.LS1.BPW AVG 2" GM.IBPW2

"GM.LS1.ETC PED" GM.ETCPED
"GM.LS1.ETC THR" GM.ETCT

"GM.LS1.TP 1" GM.ETCTP1
"GM.LS1.TP 2" GM.ETCTP2
"GM.LS1.TPS 2" GM.ETCTPS2
"GM.LS1.TPS 1" GM.ETCTPS1

"GM.LS1.FUEL LEVEL A" GM.FUELLVL
"GM.LS1.FTP B" GM.FTP
"GM.LS1.IAC DES" GM.IACDES

"GM.LS1.FTRC" GM.FTRC
"GM.LS1.TP DES" GM.TPDES
"GM.LS1.PEDAL" GM.APP

"GM.LS1.FUEL LEVEL B" GM.FUELREM
"GM.LS1.CAM HL" GM.CAMHL
"GM.LS1.CAM LH" GM.CAMLH

"GM.LS1.TORQUE DES" GM.TRQDES
"GM.LS1.TORQUE TRANS" GM.TRQTRANS
"GM.LS1.FUEL LVL R" GM.FUELLVLRS

"GM.LS1.ADAPT SHIFT A" GM.ADAPTSHIFTA
"GM.LS1.ADAPT SHIFT B" GM.ADAPTSHIFTB

"GM.LS1.TFT" GM.TFT
"GM.LS1.TIS" GM.TIS
"GM.LS1.TOS" GM.TOS

"GM.LS1.TCC DC" GM.TCCDC
"GM.LS1.SHIFT 3-2" GM.SHIFT32
"GM.LS1.TFM DC" GM.TFMDC

"GM.LS1.TCC SLIP" GM.TCCSLIP
"GM.LS1.LAST SHIFT TIME" GM.SHIFTLAST
"GM.LS1.LAST 1-2 TIME" GM.SHIFT12
"GM.LS1.LAST 2-3 TIME" GM.SHIFT23
"GM.LS1.LAST 3-4 TIME" GM.SHIFT34
"GM.LS1.LAST SHIFT ERROR" GM.SHIFTERR
"GM.LS1.SHIFT ERR 1-2" GM.SHIFT12ERR
"GM.LS1.SHIFT ERR 2-3" GM.SHIFT23ERR
"GM.LS1.SHIFT ERR 3-4" GM.SHIFT34ERR

"GM.LS1.GEAR" GM.GEAR

"GM.LS1.BOXRATIO" GM.BOXRATIO
"GM.LS1.TFT B" GM.TFTS

"GM.LS1.TURBINE SPD" GM.TURBINE
"GM.LS1.TORQUE ENG" GM.TRQENG

"GM.LS1.TCC APPLY TIME" GM.TCCTIME

"GM.LS1.TCC MODE" GM.TCCMODE

"GM.LS1.AFR" GM.AFR
"GM.LS1.DYNAMIC AIR FLOW" GM.DYNAIR

Blacky
July 13th, 2004, 01:19 AM
I have found v6 to be a bit less friendly than v5.
Some issues with v6:
- still some kinks with bi-di controls (specifically cyl balance test doesnt work, on my truck anyways)
- more dropped frames, even with PCMCIA hi-speed serial port


There is no reason V6 should drop any more frames than V5 - except if the PC's CPU is "not keeping up".

Are you sure you are using 10x24 scan mode - and not dynamic?
Is the PC keeping up with the data logging rate? What is your CPU speed?

When logging, display the Profile window (Ctrl+Y) - it tells you the scan mode (in the profile window title bar) and the number of frames per second you are logging. You should see it range between 9.8 and 10.2 frames per second.

If the PC is not keeping up (i.e. the profile window is not showing and average of 10 fps) try displaying a less CPU intensive tab page - like [OBDII (F7)]. Not having to display the charts or gauges will free up a lot of CPU time.

If you have already tried all of that and you are still getting dropped frames:
1. Wait until you are certain that some frames have been dropped
2. Terminate the logging by pressing F4 - within 3 seconds of the frames being dropped.
3. Generate a user error report Ctrl+G
4. Send it to me at paul@efilive.com.

That way I can take a look at the comms and try and see what is happening.

Thanks
Paul

Highlander
July 13th, 2004, 05:35 AM
Hey paul...

Is there a list of all common shortcuts for v5,v6 and v7?

Thanks

Blacky
July 13th, 2004, 07:13 AM
There's a list of shortcuts for V5 and V6 in their respective documentation. But there is no list that covers common shorcuts.
Paul

deezel
August 29th, 2004, 01:00 AM
Just an update... I tested v6.4 some more and found it runs around 10fps and has about the same dropped frame rate as v5. I think it was an earlier version of v6 where I was getting excessive dropped frames.


There is no reason V6 should drop any more frames than V5 - except if the PC's CPU is "not keeping up".

Are you sure you are using 10x24 scan mode - and not dynamic?
Is the PC keeping up with the data logging rate? What is your CPU speed?


10x24, 1.4 GHz P4
So, I'd say v6.4 is equivalent to v5 in my application with regards to logging rate. I haven't done the hi speed one-PID test to see which one is fastest.
Thanks for all the hard work and updates. 8)


I'm really looking forward to Flashscan. Hoping it will take care of all the "bugs" with the programmer I currently use. I still have to use a bench cable to flash the PCM. :evil: And, the most recent software update has a bunch of new stuff for 03 trucks - but, it will cost me another $100 for a years worth of updates... :x :evil:

So, a Flashscan that can program through the dash connector and properly access the tables in my PCM would be really nice about now. Hoping for pre-release info soon...
:)