Dec 17, 2024, V8.4.0 - Public Release - Update 3

[Blacky]

V8.4.70 Public Release

WARNING for all users:
Tune files saved using this release candidate software are not backwardly compatible with previous public release versions of the EFILive software.
Tune files saved using previous versions of the EFILive software are compatible with this beta version.

The method for calling Lua scripts from custom menus has changed, please see \Documents\EFILive\V8\User Defined Menus\SampleCustomMenu.txt for more info.


Full Release Notes:
What's New (https://download.efilive.com/Software/whatsnew_8_4_70.htm)


Version Numbers:

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



[*=1]EFILive V8 software: V8.4.70
[*=1] FlashScan/AutoCal V3 Firmware: V3.00.140
[*=1] FlashScan/AutoCal V2 Firmware: V2.08.214


Download here:

Download V8.4.70_Setup (https://download.efilive.com/Software/V8/EFILiveV8.4.70_Setup.exe)
Download_V7.5.51_Setup (https://download.efilive.com/Software/V7.5/EFILiveV7.5.51_Setup.exe)



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:



Issue #1 Access Violation error when opening some E92 tune files.
Workaround: Download these updated E92 *.cam files. Downloaded and unzip this file (http://download.efilive.com/Software/V8/E92_Access_Violation_Fix.zip) into a temporary folder. Copy the unzipped *.cam files to C:\Program Files (x86)\EFILive\V8\Cam\E92. Overwrite existing files. You may need admin privileges to perform the copy.




Regards,
The EFILive Team

[Tre-Cool]

Hey mate, does this 7.5 version mean we can now flash/read with the current v2 firmware now?

[Blacky]

Hey mate, does this 7.5 version mean we can now flash/read with the current v2 firmware now?

The latest V7 software no longer supports read/flash with any firmware.
You must use the V8 software to read/flash - with V2 and/or V3.

That is due to added security measures that were put in place for V2/V3 devices but that could not be supported via the V7 software. Well, not without months of redevelopment work on the V7 software - which won't happen because the V7 software has been "end-of-life" for a few years now.

The latest V7 software was only released/updated to allow it to be compatible with the latest *.ctz tune files that the latest V8 creates - so you can use either the V7 editor or the V8 editor to edit tune files.

Regards
Paul

[Tre-Cool]

ok, something that's been irritating me for a while now with v8. when modifying the vve, after saving tune file, it still has squares highlighted, signifying that they have changed.. but i dont care once the file has saved.

Am i missing a tickbox or is this meant to be?

[Blacky]

ok, something that's been irritating me for a while now with v8. when modifying the vve, after saving tune file, it still has squares highlighted, signifying that they have changed.. but i dont care once the file has saved.

Am i missing a tickbox or is this meant to be?

I'm not sure (can't remember) how the VVE tbales determine that the cells are modified. It does seem like they should show as unmodified once the file is saved - like all the other (non-VVE) tables/cells.
I will investigate...
Regards
Paul

[Tre-Cool]

sweet. i couldnt work out why you would want to show them as modified still. so was constantly having to re open the tune file again so that if i made changes to the vve by looking at the tracing i knew i was adjusting something new.

While i have your attention, how hard would it be to pull in a selectable BEN PID into the Scan-Link feature?

Something like this.
24712

Also, when looking at the 3d views of the vve maps, if you make a change for example using a smoothing or gradient function, using Cntrl-Z to undo does not work. but it will if you go to table mode.

Cheers

[Blacky]

sweet. i couldnt work out why you would want to show them as modified still. so was constantly having to re open the tune file again so that if i made changes to the vve by looking at the tracing i knew i was adjusting something new.

While i have your attention, how hard would it be to pull in a selectable BEN PID into the Scan-Link feature?

Something like this.
24712

Also, when looking at the 3d views of the vve maps, if you make a change for example using a smoothing or gradient function, using Cntrl-Z to undo does not work. but it will if you go to table mode.

Cheers

I'll add those two things to the "to-do" list :)

The VVE "modified" indicators are fixed in the latest update.
The virtual torque tables had the same issue - they are also fixed.

Regards
Paul

[Tre-Cool]

cheers, it'll somewhat similar to the old roadrunner setup.

speaking of which does that functionality still work via the v7 scanner. i'll be honest & say the roadrunner pcm sits in a shelf at the workshop...somewhere...