Update: Feb 2015

[Blacky]

Please download and install both the V7.5 and V8 software packages.
Both the V7.5 and V8 software was updated in this release, you must update both software packages.

Download V7.5 Software (98 MB)
Download V8 Software (61 MB)

Release Notes:

Release Notes.

Known Issues:

Check for known issues here.

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

As new issues are verified they will be posted in the "known issues" thread above.

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 276
To view the installed version, select Help->About (in the V7 Scan or Tune software).

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

Boot Block: V2.07.07 (Feb 07, 2014)
To view/update the Firmware, Click the [Check Firmware] button in the V8 Scan and Tune software.

Firmware: V2.07.77 (Feb 05, 2015)
To view/update the Boot Block, Click the [Check Firmware] button in the V8 Scan and Tune software.

Regards
The EFILive Development Team

[Chavez91]

Thanks Guys.

[GMC-2002-Dmax]

Paul,

What changed or was improved/fixed ?

Tony

[Chavez91]

Bug fixes in build 276:

● Some E92 calibrations were showing incorrect axis labels.
● Cummins fuel timing calculator activated for most fuel timing tables. The timing calculator is not supported for stock fuel timing tables in CSP5 tune files.
● LML VIN changing was not working.
● Allison A50 calibration files were corrupt which meant A50 transmission files could not be loaded and/or edited.

Bug fixes in build 270:

● In the V8 [F5: BBX]->[F6: Quick Setup] window, the name of the currently loaded quick setup file was not displayed correctly.
● Updating FlashScan/AutoCal configuration files using the [Check Firmware] button on the main V8 window, then disconnecting and reconnecting FlashScan/AutoCal was not correctly updating some files.
● Black Box Logging for GM controllers would sometimes fail to start.
● Serial wide band O2 data was not being logged.


There might be more Tony, but thats what i grasped from a quick look over of the Notes.

[Blacky]

Paul,

What changed or was improved/fixed ?

Tony

See previous post. Those updates were listed in the "Whats New" document, but were easily missed.

Regards
Paul

[swingtan]

Hi Guys,
Can I ask if the GM BBL Fail To Start issue was where the V2 would not display any valid data and would not write tot the SD card or internal memory?

I found that when attempting to start a BBL session, I'd get all the PID's listed but they displayed as either "0" or minimum values (-40C IAT, etc.). Additionally no data was ever written to either memory.

I'll update anyway and report back.

[Blacky]

Hi Guys,
Can I ask if the GM BBL Fail To Start issue was where the V2 would not display any valid data and would not write tot the SD card or internal memory?

I found that when attempting to start a BBL session, I'd get all the PID's listed but they displayed as either "0" or minimum values (-40C IAT, etc.). Additionally no data was ever written to either memory.

I'll update anyway and report back.

Yes, that was the problem. It should be fixed in this Feb pre-release.
Regards
Paul

[catman3126]

can we tune te A50 now?

[cindy@efilive]

can we tune te A50 now?

As per the release notes.....
A50 – first transmission calibration release for 2009-2010 LML based operating systems.

Cheers
Cindy

[swingtan]

Yes, that was the problem. It should be fixed in this Feb pre-release.
Regards
Paul

OK, I can confirm that this works fine.

I still have one other issue though, and it's been in the last couple of V2 firmware versions. Every time the V2 writes data to either the SD card or the internal memory, it looses the ability to read from either the SD card or internal memory. To replicate the problem....

Black V2 on either of the last 2 firmware versions.

1. Plug the V2 into the OBD-II port and allow to boot.
2. Confirm that it reads the last used PID settings (it has read the internal memory).
3. Start a log using the "power" button and save to either the SD card or internal memory.
4. Stop the log session using the "cancel" button.
5. Attempt to read any file, either perform a calibration flash off the SD card or just change the PID selection.
6. The V2 hangs at "Please Wait..." and can only be fixed with a power cycle, not buttons respond.

Performing any read operations are fine as long as no write operation is performed first. IE. you can perform a calibration flash or change PIDs straight after boot up, just not after the V2 has written data.

Simon.