September 2020, Beta 50 release 1

[Blacky]

**Edit** New software now available, please see the updated post in the Software Updates and Installation Help forum
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 V3/V2 device (when installing the latest beta firmware) and only install the EFILive beta test software on a separate PC, laptop or virtual machine.

This beta update contains a new CSP switchable tune operating system for CMF controllers. It is an "early access" feature that is not intended for production use just yet. EFILive is looking for feedback on the performance of the CMF CSP OS. Please do not install the CMF CSP OS on remote vehicles. Only install it on vehicles in your workshop that you can recover easily if the CSP5 OS causes problems.

For users dealing with the V3 AutoCal products you must use this release and ensure that all devices have the firmware updated to the version in this release prior to being used on vehicles.

The current public release is available here (https://www.efilive.com/download-efilive).




Changes to V8 software


Multiple *.cax8 files may now be defined for a single operating system.
Provider details are now displayed per calibration so that the user can know if a calibration is provided by the EFILive software or via a third party *.cax8 file.
Fixed CMB flash attempts that were failing with $0301 errors.


Changes to V2 firmware (V2.07.164)


None.


Changes to V3 firmware (V3.00.046)


Full control over user defined menus, colors, fonts background and splash images is now available. See \Documents\EFILive\V8\User Defined Menus\SampleCustomMenu.txt for more details.


Full Release Notes:

Whats New (https://download.efilive.com/Software/whatsnew_8_3_1(50).htm)


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



[*=1]EFILive V7 software: V7.5.31 To view the installed version, select Help->About (in the V7 Scan or Tune software).
[*=1]EFILive V8 software: V8.3.1 To view the installed version, select Help->About (in the V8 Scan and Tune software).
[*=1]FlashScan/AutoCal V3 Firmware: V3.00.049 (Sep 09, 2020).
[*=1] FlashScan/AutoCal V2 Firmware: V2.07.164 (Jul 30, 2020).


Download here:

**Edit** New software now available, please see the updated post in the Software Updates and Installation Help forum


Known Issues (in beta 49):


Issue #1:


Providing custom splash and/or background images that are not exactly 240x320 pixels in size can cause the V3 device to crash while displaying the main menu - rendering the device unusable.


Workaround:


Update to beta 50.



Issue #2:


Reading and flashing via V8 pass-thru or V3 BBx fails.


Workaround:


Update to beta 50.





Regards,
The EFILive Team

[aaronc7]

Went to black box cal flash today and got $0503 error "script file not valid"--LS1B. After the failed attempt, I re-downloaded the latest beta softwares, wiped the config and SD card, re-saved the tune file in V7.5 software just in case. Reloaded the config and tune file to FlashScan V2.... did the "check firmware" button the V8 software and said all was OK. Had the same error when attempting to flash out in the car.

edit: Just tried pass-thru flashing. Works fine using V7.5 tune tool. Same error when I use V8 software.

I've been actively using it the past several months/weeks, worked fine on last beta. No other changes. Let me know if you need any other info or ideas to try.

[Blacky]

Went to black box cal flash today and got $0503 error "script file not valid"--LS1B.
Investigating...
Regards
Paul

[Highlander]

OH OH....... first time no updates on V7......... :rippedhand:

[Blacky]

Went to black box cal flash today and got $0503 error "script file not valid"--LS1B.

This problem affects all controllers for V8 pass-thru and V3 BBx reading and flashing.
A new beta release (Beta 50) with multiple fixed issues will be posted later today.

Really sorry for the inconvenience.

Regards
Paul

[Blacky]

Beta 50 has been made available to fix the known issues in beta 49.
See first post.

Regards
Paul

[aaronc7]

Beta 50 installed and updated the BBX config files. All good now, was able to Black box flash no problems!

[Highlander]

This beta is working nice!!!!!!

[juddski88]

I am trying to edit an A50 file, it will open in V7.5 on my Windows 7 machine running V8.2.24 and V7.5.28 but won't open (says this file is not available for editing) on my Windows 10 machine running the latest releases as of today.23506

[Blacky]

I am trying to edit an A50 file, it will open in V7.5 on my Windows 7 machine running V8.2.24 and V7.5.28 but won't open (says this file is not available for editing) on my Windows 10 machine running the latest releases as of today.23506

While the V8 software is still in beta and while we are still validating the correctness and stability of the V8 editor, we have only provided editing for the following controller/OS combinations:

32170101 CME
12628594 E35
12617248 E37
12647991 E38
15189044 E54
15228758 E60
12656245 E67
12202088 LS1B

We will be releasing V8 editing support for additional controllers and operating systems soon. For now when editing other controllers and operating systems, you will need to keep using the V7 editor.

Regards
Paul

[Blacky]

You can view which controllers have editing support in V8 by looking in the folder:
\Program Files (x86)\EFILive\V8\Cam\XXX for *.cam files.
where XXX is the controller name.
The *.cam files will be named after the operating system for which they provide editing.
Regards
Paul

[Kennedy Diesel]

I have a loaded Autocal in the hands of end user with the $0503 error. Is this a simple fix with firmware or does it need configuration updates etc? Tunes need to be "rebuilt" with the latest or OK as is?

[Blacky]

It should be fixed after the customer downloads and installs this beta 50 release and updates the firmware and config files using the [Check Firmware] button in the V8 software.
Regards
Paul