Apr 27, 2024, V8.4.52 Release Candidate 1
V8.4.52 Release candidate 1
Be careful when installing release candidate software on your production systems. Even though the release candidate software has passed the beta testing phase there may still be some as yet undiscovered faults in the software.
If you intend to use this release candidate software on your production systems, please ensure that you can manage failures of the EFILive software. failures such as (but not limited to) engine no-start conditions after a failed flash.
Pay particular attention to the warnings below - once you have updated your FlashScan/AutoCal firmware to this latest version you cannot "go back" to using the previous firmware or software versions.
WARNING for FlashScan/AutoCal V2 users:Firmware versions V2.08.199 and later are ONLY compatible with the EFILive V8 software, they are NOT compatible with any version of the EFILive V7.5 software.
You SHOULD only update the firmware to version V2.08.199 or later if you intend to use the EFILive V8 software.
You SHOULD NOT update the firmware to version V2.08.199 or later if you intend to use the EFILive V7.5 software.
NOTE: The V7.5 software is no longer actively supported - EFILive does not provide technical support for the EFILive V7.5 software.
WARNING for FlashScan/AutoCal V3 users:Firmware versions V3.00.117 and later may only be rolled back to version V3.00.114.
WARNING for all users:Tune files saved using the beta software are not backwardly compatible with previous versions of the EFILive software.
Tune files saved using previous versions of the EFILive software are compatible with this beta version.
The current public release is available here.
Full Release Notes:
Version Numbers:
After installing this release you should have the following software and firmware versions installed:
- EFILive V8 software: V8.4.52
- FlashScan/AutoCal V3 Firmware: V3.00.121
- FlashScan/AutoCal V2 Firmware: V2.08.205
Download here:
Known Limitations: Limitation #1: 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.
Limitation #2: When logging DMA PIDs (i.e., PIDs whose names end with "_M" or "_DMA"), that are specific to a custom operating system such as DSP2 or DSP5 PIDs when running a stock operating system, the values returned by those DMA PIDs will not contain valid information and should be ignored.
Workaround: Ignore unsupported DMA PIDs.
Known Issues:
None.
Regards,
The EFILive Team
