October 2021, V8.3.9 Public Release

[Blacky]

V8.3.9 Public Release



Attention:
V7.5 no longer supports installation to Windows XP or Windows Vista. This change is due to SHA1 having been deprecated by digital certificate authorities. More info on SHA1 (https://en.wikipedia.org/wiki/SHA-1)
V7.5 and V8 are now only supported on Windows 7, 8, 8.1 and 10.




Full Release Notes:
Whats New (https://download.efilive.com/Software/whatsnew_8_3_9.htm)


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



[*=1]EFILive V7 software: V7.5.38 To view the installed version, select Help->About (in the V7 Scan or Tune software).
[*=1]EFILive V8 software: V8.3.9 To view the installed version, select Help->About (in the V8 Scan and Tune software).
[*=1]FlashScan/AutoCal V3 Firmware: V3.00.071 (Oct 05, 2021), Boot Block: V3.00.005 (Oct 20, 2020)
[*=1]FlashScan/AutoCal V2 Firmware: V2.08.178 (Oct 05, 2021), Boot Block: V2.08.009 (Feb 27, 2021)


Download here:

Download V8.3.9 (https://download.efilive.com/Software/V8/EFILiveV8.3.9_Setup.exe)
Download V7.5.39 (https://download.efilive.com/Software/V7.5/EFILiveV7.5.38_Setup.exe)


Known Issues:


Issue #1: Importing JTAG E86B files may result in a Boot Software segment checksum error.
Workaround: None. Don't flash imported files with checksum errors. Don't use the EFILive software to correct checksum errors for the E86B imported files as that does not fix the underlying cause of the checksum error - it just masks the error(s) and causes additional problems.

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.




Regards,
The EFILive Team

[dansdieselp]

I noticed a couple minor bugs. In V8 Editor when using the Speedo calculator for E35A and E35B the decimal for tire diameter is off. A 29.35 inch tire is displaying as 293.59 inch. In the E86A and E86B the Apply button doesn't change the value in the speedometer table. Have to manually enter it in.

[Blacky]

I noticed a couple minor bugs. In V8 Editor when using the Speedo calculator for E35A and E35B the decimal for tire diameter is off. A 29.35 inch tire is displaying as 293.59 inch. In the E86A and E86B the Apply button doesn't change the value in the speedometer table. Have to manually enter it in.

I can see/reproduce the tire diameter for E35 - will fix.

Have you setup the E86 like this?
23949

Regards
Paul

[dansdieselp]

I can see/reproduce the tire diameter for E35 - will fix.

Have you setup the E86 like this?
23949

Regards
Paul
I haven’t tried that. I’ll give it a whirl.

[bobo]

I am currently trying to get v8 to flash an E60 LLY. The flash fails after the erase procedure when the software switches top Programming in the detailed information screen. When it shows programming it takes about 5 seconds to get the $0101 no data received message. Boot Block and firmware are all up to date. I can not get it to flash in pass through or just using the v2. This vehicle is in a remote location so I am not able to be there in person to attempt a bench flash. The new bootblock and firmware will not allow me to use v7.5. Has anyone had success with this latest v8 release on an E60?

[Blacky]

I am currently trying to get v8 to flash an E60 LLY. The flash fails after the erase procedure when the software switches top Programming in the detailed information screen. When it shows programming it takes about 5 seconds to get the $0101 no data received message. Boot Block and firmware are all up to date. I can not get it to flash in pass through or just using the v2. This vehicle is in a remote location so I am not able to be there in person to attempt a bench flash. The new bootblock and firmware will not allow me to use v7.5. Has anyone had success with this latest v8 release on an E60?

The latest V7 software will work with the latest V2 firmware.

Can you have the customer provide the trace file from his AutoCal after getting the $0101 error?
https://service.efilive.com/kb/articles/autocal-v2-trace-file

Then can you log a support ticket with that trace file, thanks
https://service.efilive.com/new-ticket

Regards
Paul

[bobo]

The latest V7 software will work with the latest V2 firmware.

Can you have the customer provide the trace file from his AutoCal after getting the $0101 error?
https://service.efilive.com/kb/articles/autocal-v2-trace-file

Then can you log a support ticket with that trace file, thanks
https://service.efilive.com/new-ticket

Regards
Paul

He is using a V2. I'll get you the info. Thank you.

[bobo]

The latest V7 software will work with the latest V2 firmware.

Can you have the customer provide the trace file from his AutoCal after getting the $0101 error?
https://service.efilive.com/kb/articles/autocal-v2-trace-file

Then can you log a support ticket with that trace file, thanks
https://service.efilive.com/new-ticket

Regards
Paul

Support ticket submitted

[bobo]

Support ticket submitted

I flashed the ECM on my bench harness. It would not flash in the truck. I got V7.5 Tune tool to work before having them bring me the ecm by updating to this latest release. In the truck, V7.5 would start writing to ecm and retry the block over and over. V8 would error out $0101 no data received when the program mode would not get a response after erasing the ecm. Why does v8 not retry to establish a connection like the 7.5 tune tool does? V7.5 was doing an unlimited number of retries and I had to have them hit stop. Is there a way to make v8 retry like that?

[Blacky]

Update 2 is now available here:
https://forum.efilive.com/showthread.php?30453-October-2021-V8-3-10-Public-Release-Update-2

Regards
Paul