Update:Oct 16, 2013

[Blacky]

EFILive encourages customers to use this public update in their production environments.

Download here:

The latest stable release is available here: http://www.efilive.com/downloads.htm
Additional updates are listed here: http://www.efilive.com/latest/cat/do...e-nov-07-2013/

Updates:

V7

• E92 Preliminary calibrations release.
  
• CSP5 V1.01 public release.
  
• Cleaned up the DTC editor for late model Duramax controllers.

V8

• Fixed some minor issues with number and date formats when using a non-US locale.
  
• Added warning prior to editing calculated PIDs that explains the required floating point numeric format when using a non-US locale.
  
• Added dashboard/gauge editor (currently available to authorized beta testers only).
  
• Updated default dashboard gauges.
  
• Added Open/Save options for loading/saving charts and gauges independently of the entire dashboard.

IMPORTANT

This release creates (i.e. saves) *.ctz and *.coz tune files that have an updated format that cannot be opened with previous versions of EFILive V7.5 nor EFILive V8. Attempts to open a new file using old software will result in error $0525 "Tune file is not compatible with firmware".
Note: existing *.ctz and *.coz files can be opened by this and newer versions of the EFILive software.

Firmware

• Added support for E20 Custom PIDs.
  
• Updated switching support for CSP5.

Known Issues:

Please post issues, questions, clarifications (large or small) in this thread.

As issues are reported and confirmed they will be re-posted as "Known Issues" below.

Version Numbers:

After installing the latest release you should have the following software, boot block, firmware versions installed:

EFILive V7 software: V7.5.7 Build 244
To view the installed version, select Help->About (in the V7 Scan or Tune software).

EFILive V8 software: V8.2.2 Build 236
To view the installed version, select Help->About (in the V8 Scan and Tune software).

Boot Block: V2.07.06 (Aug 02, 2013)
To view the installed version, Select F7: Licenses (in the V8 Scan and Tune software).

Firmware: V2.07.51 (Oct 11, 2013)
To view the installed version, Select F7: Licenses (in the V8 Scan and Tune software)

[easymon]

Thanks Blacky downloading now.

[vortecfcar]

Paul,

Can .coz and .ctz files be created with this version and sent for BBX flash (autocal use) on older platforms, or must customers update their hardware to allow flashing?

Thanks,
Nick

[Blacky]

Paul,

Can .coz and .ctz files be created with this version and sent for BBX flash on older platforms, or must customers update their hardware to allow flashing?

Thanks,
Nick

The old firmware and/or old software will not be able to read the new file format.
The end users must update their software and firmware to be able to open, and/or flash *.ctz and *.coz files that you create using this latest version.

Regards
Paul

[ScarabEpic22]

Downloading now, as long as I can open old tunes with this Ill be fine. What changed in the file structure, if you can say publicly?

[Blacky]

Downloading now, as long as I can open old tunes with this Ill be fine. What changed in the file structure, if you can say publicly?

It was to fix a bug that under some conditions caused the wrong data to be used to generate seed/key locking data which in turn would cause problems when attempting to unlock that same controller later on.
You can see the entry for it in the Sep 25 release, the one about the E38, E54 and E60 auto-lock fix. The bug fix necessarily "broke" the backward compatibility of the file format. In the Sep 25 release the files were not tagged as incompatible with the older software so the fix was ignored until this release. :(

And yes opening old tune files with the new software is 100% transparent. You just can't open the newer files with the older software since the older software does not understand the changes made in the newer file's format.

Regards
Paul

[ScarabEpic22]

It was to fix a bug that under some conditions caused the wrong data to be used to generate seed/key locking data which in turn would cause problems when attempting to unlock that same controller later on.
You can see the entry for it in the Sep 25 release, the one about the E38, E54 and E60 auto-lock fix. The bug fix necessarily "broke" the backward compatibility of the file format. In the Sep 25 release the files were not tagged as incompatible with the older software so the fix was ignored until this release. :(

And yes opening old tune files with the new software is 100% transparent. You just can't open the newer files with the older software since the older software does not understand the changes made in the newer file's format.

Regards
Paul

I remember seeing that comment, thanks for the clarification!

[wesam]

Thanks for the good work
Any thing for E78 ?
Is the E92 stream available now ?

[cindy@efilive]

Thanks for the good work
Any thing for E78 ?
Is the E92 stream available now ?

Nothing for E78 however I am pleased to say that has now moved up the development list.

E92 uses our VIN license system. Stream licenses are an historical legacy retired some years ago.

Cheers
Cindy

[Chuck CoW]

Nothing for E78 however I am pleased to say that has now moved up the development list.

E92 uses our VIN license system. Stream licenses are an historical legacy retired some years ago.

Cheers
Cindy

OH... My body temp just went up a bit... For fellas like myself, that do a lot of mail order tuning involving ECM swaps, etc...

The old stream system was great for controllers we specialized in and we just used the vin system for odd ball jobs. I do understand

why EFI LIVE feels E38 streams (for instance) were not as profitable as vin licenses for that controller, but for a small group of your customers

limiting the license structure to vin licenses only will make business very difficult and cause guys like me to make drastic changes to how we do business.

I have to say, if it was that stream licenses never existed, I would never have developed many of the products or services I offer and all of the things I learned

along the way.

I would really love to see an alternate licensing option for guys like myself that is more economical for those of us that flash high volumes of the same controllers

both in production work and private development work. I would not be able to justify licensing 20-50 controllers sitting on the shelf with a vin only policy. Development for

some stuff would just halt with that.

Hopefully it's something you'll consider for those of us that do what I do.

Thanks.
Chuck CoW