FlashScan weekly update April 16, 2004

[Blacky]

I hope everyone is safe and well and back to work after the Easter break.

The FlashScan hardware has undergone some revisions and will offer longer data logging than previously stated - possibly up to 25 minutes.

The EFILive web site is having a major facelift and will include an online shop where you can safely and securely purchase all EFILive products.

EFILive V6.4.1 Scan Tool is currently in internal testing and is expected to be available for public beta testing on Monday 19th April 2004.
It includes the VIN change option that did not make it into V6.4.0

A new set of PIDs are being developed for the EFIlive Scan Tool that will take the mystery out of the LS1 spark maps. There are numerous tables that contribute to the final spark advance value. EFILive is being configured so that the spark contribution from *each* table can be logged seperately.
Being able to "see" each table's contribution to the final spark value will take a lot of the guesswork out of calibrating the spark advance.

The spark/fuel maps from EFILive V5 have been redesigned for EFILive V6. The maps in V6 will not offer any override capabilities. (EFIlive's Tuning Tool will do a much better job of that).
The new maps will allow much greater flexibility and will allow you to log any combination of PIDs - not just spark and fuel.
We hope to include the new maps into V6.4.2

As usual, feel free to ask questions...

Regards
Paul

[Highlander]

WOW!!!!!!!! that is a REAL utility!!! im glad I have a key!!!!!!

Got any pricing worked out?? expected release date?

THanks

[deezel]

Very cool! 8)

[GMPX]

A new set of PIDs are being developed for the EFIlive Scan Tool that will take the mystery out of the LS1 spark maps. There are numerous tables that contribute to the final spark advance value. EFILive is being configured so that the spark contribution from *each* table can be logged seperately.
Being able to "see" each table's contribution to the final spark value will take a lot of the guesswork out of calibrating the spark advance.

I would just like to add to this, I have been doing some testing on my car and all I can say is it is showing me some very interesting things, once we get this function operating 100% you all will be pretty impressed.
It's really good to see your final timing value of say 28degrees, but then seeing the four or five parameters that actually make up that timing value of 28 degrees.

Don't worry, it hasn't distracted us too much from FlashScan, in fact, whilst we were doing some timing tables for FlashScan the idea for this came around.

[XLR8NSS]

These updates are good and bad. Good because they explain some of the cool features being developed and bad because knowing this stuff makes it that much harder to wait.

Keep the updates coming.

[Highlander]

I AGREE

[66ImpalaLT1]

I have wanted to map any 3 pid's ever since the discussions about calculating VE began on ls1tech.

I cant wait.

[bink]

Great News!! Thanks.
Joel

[GMPX]

I have wanted to map any 3 pid's ever since the discussions about calculating VE began on ls1tech.

What '3' in particular?, at the moment we are working on the additional spark PID's, you mention VE, does that mean additional fuel PID's would also be welcomed?.

[66ImpalaLT1]

I'd like to see the columns by rpm, rows by map with calculated ve in the cells.

Additional fuel pid's would be nice, I'd like to see the values that contribute to the DYNAIR calculation. My understanding is that these pcm's are not purely speed density or maf based most of the time, but that dynair is a combination of the two methods.