August 2021, V8.3.8 Beta 1

V8 BETA 1 SOFTWARE RELEASE

We strongly recommend that you do not install the beta software over the top of your production systems. It is possible that the beta test software may fail and your production system may not be recoverable. If you conduct a tuning business, please take the necessary precautions to protect your business. EFILive recommends beta testers use a separate FlashScan V3/V2 device (when installing the latest beta firmware) and only install the EFILive beta test software on a separate PC, laptop or virtual machine.

The current public release is available here.

Attention:

V7.5 no longer supports installation to Windows XP or Windows Vista. This change is due to SHA1 having been deprecated by digital certificate authorities. More info on SHA1
V7.5 and V8 are now only supported on Windows 7, 8, 8.1 and 10.

Full Release Notes:

Whats New

Version Numbers:

After installing this beta release you should have the following software and firmware versions installed:

• EFILive V7 software: V7.5.37 To view the installed version, select Help->About (in the V7 Scan or Tune software).
  
• EFILive V8 software: V8.3.8 To view the installed version, select Help->About (in the V8 Scan and Tune software).
  
• FlashScan/AutoCal V3 Firmware: V3.00.067 (Aug 27, 2021), Boot Block: V3.00.005 (Oct 20, 2020)
  
• FlashScan/AutoCal V2 Firmware: V2.08.176 (Aug 25, 2021), Boot Block: V2.08.009 (Feb 27, 2021)

Download here:

Download V8.3.8 (This is a beta software release and should not be used in production environments yet)
Download V7.5.37 (this is a production software release and may be used in production environments)

Known Issues:

Issue #1: Importing JTAG E86B files may result in a Boot Software segment checksum error.
Workaround: None. Don't flash imported files with checksum errors. Don't use the EFILive software to correct checksum errors for the E86B imported files as that does not fix the underlying cause of the checksum error - it just masks the error(s) and causes additional problems.

Issue #2: When logging DMA PIDs (i.e., PIDs whose names end with "_M" or "_DMA"), if the ignition is switched off for an extended period while data logging but data logging is not terminated, then when the ignition is switched on again the data log automatically continues. However, the DMA PIDs may no longer return valid data.
Workaround: EFILive recommends stopping the data log and restarting the data log when switching off the ignition for extended periods.

Regards,
The EFILive Team