EFILive V7.5 and V8 Release Notes

Sep, 2016 Beta 2 Release

Version Numbers

· V7.5 Software: V7.5.8, Build 311

· V8 Software: V8.2.3, Build 305

· FlashScan/AutoCal Firmware: V2.07.104 (Sep 17, 2016)

· FlashScan/AutoCal Boot Block: V2.07.007 (Feb 07, 2014)

IMPORTANT:
The EFILive software version numbers have been updated from: V7.5.7 to V7.5.8 and from V8.2.2 to V8.2.3. That version number change reflects two major compatibility updates:

· The *.ctz and *.coz tune files have been updated.
Tune files that are saved with version V7.5.8 and later or with version V8.2.3 and later are not compatible with previous software versions. Tune files created with previous software versions are 100% compatible with this latest software version.

· The *.obj read/flash script files have been updated.
Script files distributed with this software version will not operate on devices with firmware V2.07.103 and earlier. So if you create a *.bbx quick setup file for your customers' AutoCal devices using this software version, then you must ensure that the target AutoCal devices are using firmware V2.07.104 or later.

Updates in the most recent release are shown in orange.

EFILive V7.5

Calibration Updates:

Dodge Cummins

· Updated CME calibrations.

GM Gas

· E92 - Added support for new operating system.

· E82 - First calibration release for LGX 3.6L Direct Injection engine.

· E39A - Added support for new operating system.

· E78 - Added support for new operating system and enhancements to existing operating systems.

· E80 - Added support for new operating system.

· T43 - Added support for new operating system and enhancements to existing operating systems.

· T76 - Added support for new operating system and enhancements to existing operating systems.

· E39 Added support for new operating systems and enhancements to existing operating systems.

· E80 Bug fixes to existing operating systems.

GM Diesel

· T87 First calibration release for 6 speed Allison Transmissions.

Known Issues:

· When opening a tune file from Windows Explorer, either by double clicking on it or right-clicking and selecting “Open” and the file cannot be opened for any reason, then no error message is displayed and the file is not loaded. To view the error that prevents the file from being opened, first start the Tune Tool software, then attempt to open the tune file; the error will then be displayed normally.

Enhancements:

· Added support for editing recently released E39A controllers.

· Added template for tune file names in V7.

· Added tag <jd> to filename templates. <jd> returns the Julian Day of the year.

· Added option to allow sequence number to be 1, 2, 3 or 4 digits.

Bug Fixes:

· Fixed CVNs not updating correctly under the Pro Tuning license.

· Fixed <seq> template tag not generating the correct filename.

· Fixed right-click context menu not showing up on blank dashboard pages.

· Updated PID MFCYCLDLY to correctly handle PID differences between VPW and CAN modules

· Updated PID MFCYLIDX to be defined as signed instead of unsigned.

EFILive V8

Known Issues:

· 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.

· When Black Box Logging PIDs from an ECM and TCM simultaneously and a PID is selected from the transmission controller (TCM) that has an identically named PID in the engine controller (ECM), (i.e. RPM) then when the log file is opened in the V8 software for viewing, the 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.

Enhancements:

· Changed the order and display names of the supported controllers' right-click menu selection. The new order groups similar controllers together. The display names are now more accurate, concise and easier to locate.

· Split the *.pdf documentation files into subfolders on the Start menu and in the Help menu.

· Added support for CAN integration of the AEM UEGO wide band controller. Select the AEM as a transmission controller to log the wide band PID WO2S11 which includes sub PIDs EQ_RAT11 (lambda) and WO2S11V (millivolts).

· FlashScan icon displayed in the system tray is now a generic representation of both FlashScan and AutoCal devices.

· Updated E39 boot loader software to correctly identify recently released E39A controllers.

· Added E39A as a unique controller for pass-thru scanning, black box logging and OBD operations. Previously selecting E39 covered both E39 and E39A.

· When a read-only *.bbx quick setup file is loaded, the fact that it is read-only is now indicated with the text "(file is "read-only" and cannot be modified)" which is displayed in red after the filename.

· Added support for new GM controller security options.

· AutoCal will no longer "auto-link" to the file being flashed when AutoCal is not already linked to a FlashScan device. To remotely link an AutoCal use the EFILive Control Panel -> [F7: Licensing]->[Link]->[Generate Remote-Link Code] option. To remotely un-link an AutoCal use the EFILive Control Panel -> [F7: Licensing]->[Link]->[Generate Remote-Unlink Code] option.

· Added an option to "downgrade" the security capabilities of secondary FlashScan devices. Downgrading the security capabilities allows you to distribute additional FlashScan devices that can be used to link AutoCals and save files for those AutoCals but that cannot be used to remove security settings on files nor unlink AutoCals.

· Added a new attribute to all FlashScan devices called "Protected Number". The protected number is used to implement the options described in the previous bullet point.

· Changed error message dialogs when trying to open *.coz files so that they now explain that *.coz files cannot be viewed or edited - instead of just showing a generic "unsupported file type" error message.

· Split template properties into Scan and Tune sections so that unique templates can be configured for both Scan and Tune files.

· Added tag <jd> to filename templates. <jd> returns the Julian Day of the year.

· Added option to allow sequence number to be 1, 2, 3 or 4 digits.

· Added option to allow *.coz filenames to use auto-incrementing filenames.

· Added option to prevent auto-incrementing sequence number from being dynamically updated when changing folders in the "File Save" dialog.

Bug Fixes:

· Fixed [F4: OBD]->[Retrieve All Information] which was giving a "Range Check" error if the retrieval attempt was made with 10 seconds of switching on the ignition.

· Fixed [F4: OBD]->[Tests] results not showing up when a transmission controller was detected.

· Tune file comments and history were not being displayed.

· Restored icons to main menu items.

· Filenames longer than 130 characters can cause "Access Violation" when displayed in the list of "Recent Items" on the main window.

· Scroll bars were not displaying or not displaying the correct size on dashboard property editor windows.

· Fixed "Access Violation" when loading a dashboard with calculated PIDs to be displayed, but those calculated PIDs were not selected in the currently open log file.

· Cummins (CMD/CME) operating system numbers were not displaying the last 2 digits on the [F4: OBD] window.

· Fixed pass-thru scan tool not detecting controllers under some conditions when starting a data log.

· Fixed [Yes/No] dialog boxes in EFILive Explorer that would respond as if the user clicked [Yes] when the dialog box's red close button was used to cancel the dialog.

· Re-enabled calculated PID function sum() which had been disabled.

· Re-enabled calculated PID function damp() which had been disabled.

· Fixed Access Violation when changing the name of a calculated PID while a log file is loaded that displays that same calculated PID.

· Optimized log file loading to only compute calculated PIDs once the entire file had been loaded.

· Fixed fault when BBX flashing a *.coz file for a P12 controller.

· Fixed "Index out of Range" error when clicking on the [Copy] button in the [F7: Licenses] window.

· Changed all occurrences of "wideband" to "wide band".

· Fixed "Perform Test Flash Only" default setting not being set correctly on the [F6: Cal-Flash] and [F7: Full-Flash] tab pages.

· When editing the filename in the "Save File" dialog, automatic updates to the auto-incrementing sequence number can cause the filename to disappear or to change unexpectedly.

FlashScan/AutoCal

Known Issues:

· 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. EFILive recommends stopping the data log and restarting the data log when switching off the ignition for extended periods.

Enhancements:

· Added descriptions for negative response error codes in the range $0300..$037F.

Bug Fixes:

· Fixed internal test functions which were incorrectly reporting that the ALDL and SCI interfaces were faulty.

Documentation Updates

· EFILive V8 Reference Manual

· EFILive AutoCal Info for Tuners

· EFILive AutoCal Info For End Users

· Controller Authorization

· EFILive Error Codes

· EFILocker COS Patch

Knowledgebase Updates

· Controller Authorization

· Move Tune and Log Files to/from FlashScan V2/AutoCal

· Configure FlashScan V2 and AutoCal for BBX

· SD Card Configuration

· Finding FlashScan & AutoCal Boot Block and Firmware Versions

· Finding FlashScan & AutoCal Serial Number and Authentication (Auth) Codes

· Device Settings

· License Status

· Problems Reading a Controller

· Problems Flashing a Controller

· Device Settings

· USB FAQ