July 2018, Beta Update #2

ATTENTION - BETA 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. lf you conduct a tuning business, please take the necessary precautions to protect your business. EFILive recommends beta testers use a separate FlashScan 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.

Release Notes:

Whats New

Version Numbers:

After installing this beta release you should have the following software, boot block, firmware versions installed:

• EFILive V7 software: V7.5.21 To view the installed version, select Help->About (in the V7 Scan or Tune software).
  
• EFILive V8 software: V8.2.17 To view the installed version, select Help->About (in the V8 Scan and Tune software).
  
• Boot Block: V2.07.008 (Jul 04, 2018) To view/update the Boot Block, click the [Check Firmware] button in the V8 Scan and Tune software.
  
• Firmware: V2.07.134 (Jul 06, 2018) To view/update the Firmware, click the [Check Firmware] button in the V8 Scan and Tune software.

Download here:

Download EFILive V7.5
Download EFILive V8

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:

Adding a key to the [Remote] section of a tune file is only active for the following controllers: LS1B, E38, E40, E54, E60 and E67.

Workaround:

None.
Support for additional controllers will be added in a future update.

.

Paul would fix issue #1 please. That's been on there long enough LOL :cucumber:

I mean, V8 has only been in development for... 10 years? LOL One day.... :notacrook:

I'm glad you've got a sense of humor about it.:thumb_yello:
But seriously I know it's been far too long, working my ass off to get it done.
Paul

Quote:

---

Originally Posted by Blacky

I'm glad you've got a sense of humor about it.:thumb_yello:
But seriously I know it's been far too long, working my ass off to get it done.
Paul

---

It'll be worth it in the end! :)

first bug. When NEVER installing drivers for a v2 unit on a new machine, but you put in the license details so it is not in demo mode, and try to open up a calibration for the first time, it will Lock up the software. Then in the BACKGROUND that you can not see, will be a window box that complains about a missing driver. This is opening Efilive scan and tune. V8..

It fails at the time when the V8 software pulls the usb for a efilive cable.

Second bug. When reading out a 2007 lml vin number 1GCHG396171204317 flashed into it. All stock ecm. The software reads out fine. But when efi does the blend to add in the missing parts to the binary, it fails with a window saying, "cannot merge calibrations with CPU system file" , then it points to my configuration folder looking for Z00.EXT

Anyone hit a $0371 flashing error "Transfer Suspended ($71)."?? or am I the lucky first one?

On a CMD controller too... just for the added info. working on retrieving trace files right now to submit

hmm that same one is coming up here on cm2350b

Updating to the beta release fixed the issue for us. It was remote customer, he was on the last version of the beta software •EFILive V8 software: V8.2.16 instead of •EFILive V8 software: V8.2.17 so once we updated boot block, firmware and all that along with THIS software release, the problem went away and we were able to successfully flash this truck. Everything good so far! :crash:

Hey guys :) having a little trouble out in the field. I will try nd give you the facts as I know them. I sent my V2 to a friend back up in Indiana ( I know ) His work owned laptop did not allow him to Install. Got with Admin and approved. Downloaded Beta 8.2.17 and then updated the firmware. Laptop will connect to V2 but not forward to PCM. just as EXT . V2 will BBX into PCM , Datalog, Read but when trying to write get $06FF backed out and tried to write in 7.5 and 8 again no luck so loaded up on the V2 and the same Checksum error. Jesse remoted in on the original (Work ) Laptop and thought there was a clamp on the USB? So off he goes and buys a new Laptop and Installs 8.2.16 still gets no comms in pass thru . and $06ff. If I can get some help with the Checksum error we should be able to move forward using the V2 to load? Obviously time is a major factor hence him having my V2 overnighted and new laptop and all. Never seen anything like it.


Thanks for the help today Jesse!

Ok what ECM type is this? Based on the error there is every chance if it is a GM gas ECM the ECM already has a tune in there from another tuner that messes with how the checksum are calculated. We see this a bit and it is an easy fix.
Would you be willing post the file up here? Or at least let us know the ECM type and the OS number of the file?

Cheers,
Ross

I posted the file last night I believe it said it was waiting for moderators approval? I will try again. Yes its a E67 OS 12632176 That someone had been in before so I believe you are 100% Correct. I will try to attach the cal in another reply as well as email it in. Thanks Ross!

Cal

Never mind sleep well! all is good. I did not do a good enough job explaining that the OBD cord does not plug directly into the PC.

I really appreciate the help from you all, Thanks! :wallbash:

Hard to follow where you are at with it all :laugh:
All good now?