June 2016 Release Candidate 1

Please download and install both the V7.5 and V8 software packages.

Both the V7.5 and V8 software were updated in Release Candidate 1, you should download and install both V7.5 and V8 software packages.

Release Notes:

Whats New

Version Numbers:

After installation, you should have the following software, boot block and firmware versions installed:

EFILive V7 software: V7.5.7 Build 307 To view the installed version, select Help->About (in the V7 Scan or Tune software).
EFILive V8 software: V8.2.2 Build 299 To view the installed version, select Help->About (in the V8 Scan and Tune software).
Boot Block: V2.07.007 (Feb 07, 2014) To view/update the Boot Block, click the [Check Firmware] button in the V8 Scan and Tune software.
Firmware: V2.07.101 (June 06, 2015) To view/update the Firmware, click the [Check Firmware] button in the V8 Scan and Tune software.

Known Issues

---

Issue 1:
If you are Black Box Logging PIDs from an ECM and TCM simultaneously and you have selected a PID from the transmission controller (TCM) that has an identically named PID in the engine controller (ECM), then when the log file is loaded back into the V8 software for viewing, that TCM PID will be displayed as if it originated from the ECM. The PID's data will have correctly been logged from the TCM, only its name will appear to indicate that it was logged from the ECM.
Workaround:
None.
It is a restriction of the *.efi (V7.5 log file format). That restriction will be removed and the TCM PIDs will display their true origin once the V8 scan tool software is available and fully integrated with the V8 tuning tool software.

---

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.

---

Issue 3:
V8 Scan Tool [F6: Maps] tab page is no longer available/visible and the Record and Monitor option are no longer enabled. Those options were tagged as visible/active for the beta software only. They were incorrectly deactivated when the software was promoted from beta to RC1.
Workaround:
Install RC2

---

Issue 4:
When saving CMD or CME tune files in V8 the error "VariableCRC_START1_1does not exist" occurs.
Workaround:
Install RC2

---

Issue 5:
When closing the V8 Scan Tool window, if any of the property editor windows (Gauge Properties, Gauge Editor, Chart Editor or Map Editor) were open, an Access Violation occurs.
The Access Violation may prevent you from closing the Scan Tool window, in which case use Task Manager to kill the EFILive_ScanAndTune.exe process.
Workaround:
Install RC2

---

Issue 6:
If the V8 Scan Tool filter is selected while no data is loaded in the Scan Tool an Access Violation occurs.
Workaround:
Install RC2

---

Issue 7:
The GEAR PID does not display gears 7 and 8 correctly for T87 - instead it shows Reverse and Park respectively.
The GEAR PID does not display Neutral, Reverse or Park correctly for T43 - instead it shows Reverse, Park and Low respectively.
Workaround:
Install RC2

---

Issue 8:
CSP5 tune files incorrectly show a bad checksum when loaded into the V8 or V7.5 tuning software. Correcting the "bad" checksum and flashing the file will most likely result in a no-start condition, usually with fault code P0601.
Workaround:
Install RC2

---

.

Paul, thanks, the ! operator now works correctly.

WHEN trying to lock a tune I am getting VaraiableCRC_START1_1 does not exisit

Quote:

---

Originally Posted by House

WHEN trying to lock a tune I am getting VaraiableCRC_START1_1 does not exisit

---

Which controller type?
Which software version (V7.5 or V8)?

Regards
Paul

Quote:

---

Originally Posted by Blacky

Which controller type?
Which software version (V7.5 or V8)?

Regards
Paul

---

v8 and cm2200

Thanks for the info. Working on a fix now...

Regards
Paul

Quote:

---

Originally Posted by Blacky

Please download and install both the V7.5 and V8 software packages.

Both the V7.5 and V8 software were updated in Release Candidate 1, you must update both software packages.

Download V7.5 RC1 (103 MB)
Download V8 RC1 Update1 (65 MB) Updated June 8, 2016, fixes Known Issues 3 and 4 listed below.

Release Notes:

Whats New

Version Numbers:

After installation, you should have the following software, boot block and firmware versions installed:

EFILive V7 software: V7.5.7 Build 307 To view the installed version, select Help->About (in the V7 Scan or Tune software).
EFILive V8 software: V8.2.2 Build 299 To view the installed version, select Help->About (in the V8 Scan and Tune software).
Boot Block: V2.07.007 (Feb 07, 2014) To view/update the Boot Block, click the [Check Firmware] button in the V8 Scan and Tune software.
Firmware: V2.07.101 (June 06, 2015) To view/update the Firmware, click the [Check Firmware] button in the V8 Scan and Tune software.

Known Issues

---

Issue 1:
If you are Black Box Logging PIDs from an ECM and TCM simultaneously and you have selected a PID from the transmission controller (TCM) that has an identically named PID in the engine controller (ECM), then when the log file is loaded back into the V8 software for viewing, that TCM PID will be displayed as if it originated from the ECM. The PID's data will have correctly been logged from the TCM, only its name will appear to indicate that it was logged from the ECM.
Workaround:
None.
It is a restriction of the *.efi (V7.5 log file format). That restriction will be removed and the TCM PIDs will display their true origin once the V8 scan tool software is available and fully integrated with the V8 tuning tool software.

---

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.

---

Issue 3:
V8 Scan Tool [F6: Maps] tab page is no longer available/visible and the Record and Monitor option are no longer enabled. Those options were tagged as visible/active for the beta software only. They were incorrectly deactivated when the software was promoted from beta to RC1.
Workaround:
Install RC1 Update1.

---

Issue 4:
When saving CMD or CME tune files in V8 the error "VariableCRC_START1_1does not exist" occurs.
Workaround:
Install RC1 Update1.

---

---

Thank you very much for the fix! Back to fast CRC via v8!


Sent from my iPhone using Tapatalk

We got a strange error when we edited the AFM VVE tables on an E38 and saved to file...

there was an error message about the minimum vve zone has to be bigger than 3x3 (and I'm sure it was)...

and it would not let me save the file...

and undoing the changes on the AFM VVE tables did not help, the error message persisted, and still could not save the file...

I had to kill the tunetool and go back to the previous file.

Quote:

---

Originally Posted by joecar

We got a strange error when we edited the AFM VVE tables on an E38 and saved to file...

there was an error message about the minimum vve zone has to be bigger than 3x3 (and I'm sure it was)...

and it would not let me save the file...

and undoing the changes on the AFM VVE tables did not help, the error message persisted, and still could not save the file...

I had to kill the tunetool and go back to the previous file.

---

Hi Joe,
Can you email me the file and a sequence of step to reproduce the problem?
Thanks
Paul

Quote:

---

Originally Posted by joecar

I had to kill the tunetool and go back to the previous file.

---

Could you close the file without saving it? Not sure why you would need to kill the tune tool.
Regards
Paul