November 2017, Public Release

3 November 2017

EFILive is pleased to announce November 2017 Public Release software is now available. EFILive has changed the [Check for Updates] process. The [Check for Updates] option will check your current software version against the most recent public release version available on our website. If a newer version is available, users will be directed to our website to download the updated software.

Known Issues:

A list of known issues can be found here:.https://forum.efilive.com/showthread.php?28071-Current-Public-Release-(Nov-2017)

Important Changes

The format of the version number used to identify the EFILive software has changed. The significant numbers in the software version are the first three numbers: Major.Minor.Release. The fourth number, (Build) is no longer used for anything other than tracking the actual build number and some minor internal version management.

Compatibility between *.exe and *.dll files is now determined by the Release number not the build number.

The Major number will be updated when a major new software version is created.

The Minor number will be updated if/when file formats and/or compatibility are changed.

The Release number will be updated whenever a new release is made available - which includes beta releases and release candidates.

The Build numbers will increment independently for each *.exe and *.dll in each of the EFILive software packages

A new option has been added to the V7.5 tune software that allows users to enter calibration values outside of EFILive's recommended limits. The new option is controlled via the Edit->Properties->[Options]->"Allow calibrations to exceed recommended limits." check box.

If you have only just updated to this version from the Feb 2017 public release then the new option will default to checked and you won't see any "Out of Range" messages.

If you have installed any beta version in the past few months then that option may be unchecked by default. That means you may see calibrations being reported as "Out of Range" that previously were not reported as "Out of Range". If you would prefer not to see those "Out of Range" messages, then you should check the option described above.

When that option is checked:

"Out of Range" messages are no longer displayed, and

Calibrations will display the EFILive limits and the controller's actual limits, and

Any value that exceeds EFILive's limits will be displayed with a thin black border.

When that option is unchecked:

"Out of Range" messages are displayed if calibrations exceed the EFILive limits, and

Calibrations will only display the EFILive limits (not the controller's actual limits), and

Any value that exceeds EFILive's limits will be truncated to the EFILive limit. However, the truncated value(s) will not be updated in the tune file unless you modify the calibration, causing its data to be saved back to the file.

V8 Software: V8.2.10

Known Issues:

Issue 1 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 2 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.

Build V8.2.10 Enhancements

Added an [Add] button on the [F8: Authorization] tab page to allow auth-codes to be entered via the keyboard.

Build V8.2.8 Enhancements

Removed "build number" from version number displayed in Help->About.

Build 332 Enhancements

Chart vertical scales (y-axis) can now be extended to use the complete vertical space of each chart.

Chart captions can be moved left/right to allow for extended vertical scales (y-axis) to be displayed.

Separator line can now be displayed between each chart.

Changed default precision for "degrees" from 0 to 1, and for "btdc" and "atdc" from 2 to 1.

Units are now displayed on PID selection menus for PIDs defined with only one unit (i.e. % or mV) .

Build 327 Enhancements

Controller Authorization has been changed so that the auth-code and related details will be updated whenever an attempt is made to read/flash a controller - if and only if the auth-code is not yet authorized.

Changed some Cummins HD PIDs that were defined with units of bar to units of MPa so that other display units can be selected for those PIDs.

Build 325 Enhancements

File and folder templates are now validated to ensure the generated file name is a valid Windows file system name.

Added a description to the top of the template properties window explaining when templates are used and when they are not used.

Build 323 Enhancements

"Minimum" and "Maximum" defined values for user defined and third party PIDs are now used as the default min and max scale values when adding PIDs to the charts. The min/max values are automatically adjusted to compensate for different units selected by the user.

Added short cut key <Numeric KeyPad 0> to start/stop data logging in pass-thru logging mode. It is easier to press that key on a laptop keyboard when sitting inside a vehicle, then to press either Ctrl+R/Ctrl+Q or click the Record/Stop buttons. Note: if the input focus is currently a text entry field, then pressing <Numeric Keypad 0> will result in a 0 being inserted into the field, it will not start/stop logging. It will only start/stop logging when the input focus is not a text field.

Build 322 Enhancements

Added "Capture Screen to Clipboard" option for Charts, Gauges and Maps display in the Scan Tool. Use drop down menu off of the [Save] button or the hotkey Shift+Ctrl+C.

The [Check Firmware] option correctly displays the status of the currently connected device if the user disconnects one device and re-connects a different device.

Added VIN, Serial Number and Operating System Number as tags for scan and tune filename templates.

Fixed scan and tune filename template tag <ctrl> not resolving to the controller type name correctly.

Added option to load security settings and remote control options from an existing tune file when setting up security restrictions for individual tune files and BBX quick setup files.

Added a command line interface to allow tuners to automate AutoCal programming using batch files. Use the EFILive_CmdLine.exe file and related documentation EFILive Command Line Reference.pdf.

Added new user defined PIDs option that allows users to define their own data logging PIDs, including DMA PIDs. For instructions on creating your own user defined PIDs, please review the comments in the *.ini files in the folder \Documents\EFILive\V8\User Defined PIDs.

Build 321 Enhancements

Allow searching for partial checkusm values. That allows searching for CVN (Calibration Verification Numbers) for those controllers that embedd the CVN in the checksum value.

Build 320 Enhancements

Multiple scan or tune files can be opened at the same time by selecting multiple files in Windows Explorer and dragging them onto the main V8 window. Note: right clicking in Windows Explorer and selecting Open, does not support opening multiple files, only a single file at a time can be opened that way.

Added new tab page [F7: Licenses]->[F5: Convert] to make it easier for AutoCal customers to apply license conversions issued by their tuner.

Added new option in EFILive Control Panel [F7: Licenses] tab page to allow tuners to change AutoCal's maximum number of VIN slots for any AutoCal linked to the tuner's FlashScan device.

Added new option in EFILive Control Panel [F7: Licenses] tab page to allow tuners to generate a remote code that can be sent to their customers so that the customer can remotely update AutoCal's maximum number of VIN slots for any

AutoCal linked to the tuner's FlashScan device.

Added "EFILive Explorer" shortcut link to main screen of EFILive Scan and Tune.

Added "EFILive Control Panel" shortcut link to main screen of EFILive Scan and Tune.

Added option to allow tuners to change the maximum number of VIN slots allowed on their customer's linked AutoCal devices.

Added extended descriptions for PIDs with "state encoded data" such as: FUELSYS. Descriptions are now displayed alongside the cryptic codes.

Build 317 Enhancements

Added two new DPF PIDs: REGENR and REGENIR.

Added search option to allow searching for segment checksums.

Optimized the "Search Entire File" to first search all files' meta data to quickly exclude any files that do not match, then and only then are the remaining files searched for other, more detailed criteria.

Added a new template sequence option tag <seq0> which will add a sequence number of 1 to 4 digits depending on the magnitude of the number. I.e. the number is not zero padded to a fixed number of digits.

Added a new template option to allow the sequence number to include the letters A..Z.

For CMD/CME controllers, added a new FAST CAN Mode flash option. The old FAST CAN Mode is now called "Unlimited", a new fast CAN mode has been added called "Fast" which is slightly slower but more robust than Unlimited.

Saving tune files while a read, flash or pass-thru scanning is in operation is now not allowed. Because the save process communicates with FlashScan/AutoCal to validate security options and that can interfere with reading, flashing or pass-thru scanning.

Local.ska file was not being updated with controller's details if a matching auth-code already existed for that controller when the controller was being read for a second or subsequent time.

When loading a new dashboard, any chart y-axis that changed from "enumerated" to "numeric" did not have it's numeric scale rendered correctly until the window was resized.

When adding PIDs to the chart display the precision setting is ignored for PIDs defined with only one unit (i.e. % or mV) .

The dynamic resize limit property was ignored when resizing the scan tool window, preventing charts being resized dynamically while the entire window was resized.

When making the chart or gauge displays full screen (F10/F11) - if the scan window was already maximized then the display was slightly cropped.

MAP PID scaling was incorrect for some late model controllers.

Build 332 Bug Fixes

The EFILive Control Panel may terminate unexpectedly (instead of minimizing to the System Tray) after changing any setting, then immediately closing the window and selecting [Cancel] to cancel the changes.

When saving a newly recorded scan file, the file template name was being generated incorrectly and the sequence number was not being updated properly.

When searching for V8 (*.pld) scan files, the comments in the scan file were not being searched.

When saving a tune file the segment checksums were always being updated. Now they are only updated if/when the user right clicks on one or more selected segments and chooses the "Force Checksums to be Correct" option.

After modifying a Cummins CMC *.bin file outside of the EFILive software then using the V8 software to "Force Checksums to be Correct", the checksums calculated and stored in the *.ctz file may not be correct.

<os>, <sn> and <vin> tags were never enabled in the right-click drop-down menu of the file and folder templates in the advanced file/folder properties window.

Build 324 Bug Fixes

When editing chart properties in the V8 scan tool, clicking in the Y-axis area of a chart to select it for editing has the unintended side effect of resetting that chart's Y-axis min/max values to their defaults.

PIDs with text values such as "FUELSYS1" and "FUELSYS2" were not displaying the correct value nor the correct text descriptions.

Build 323 Bug Fixes

Filename extensions are now treated as case-insensitive.

<vin> tag in filename templates was not resolving to the file's VIN.

Build 322 Bug Fixes

When re-opening the same log file that is already open with no zoom factor, the newly opened log file is not displayed, instead the current log file display remains unchanged. Specifically if a log file was opened, then notes were deleted, then the same log file was re-opened without saving the changes, the notes that were deleted were not being re-displayed until a change in zoom factor was made.

Starting a pass-thru data log when not connected to a vehicle controller will not log any data but the software behaved as if logged data existed.

Timestamps displayed during pass-thru data monitoring were incorrectly being updated even though no data was being recorded.

Fixed the segment number meta data stored in VPW based controllers' *.ctz files. Previously the segment numbers were not being stored when reading the controller.

Enabled T87A scanning and OBDII info support.

Fixed PID RPM24x from reporting a wrong or no value.

Fixed pass-thru logging so that frames are only saved when all PIDs have been received. Previously the scan tool was logging frames up to 4x too fast which cause 3 duplicate frames to be logged for every actual frame received.

Build 318 Bug Fixes

Renamed the CMD enhanced PID: AAT to AAT_B to resolve name clash with the generic AAT PID. Previously logged CMD data files that included the enhanced AAT PID will not display correctly.

Fixed V8 pass-thru data logging not working on VPW based controllers.

Fixed Cummins "Fast CAN Mode".

Fixed the "Save As..." option not defaulting to the file's original folder.

Some custom DMA PIDs were being incorrectly scaled after the MAF re-scaling options were recently added. E.g. for E38 controllers VSS_M and SCALCORVE_M were being incorrectly scaled.

Build 317 Bug Fixes

User selected flash options are no longer cleared when loading a new controller that may not support those options.

The options now remain set to the user's choice and are silently ignored if not supported on the target controller.

Fixed display issues when changing Gauges and Charts between full screen mode and windowed mode.

Fixed AutoCal/FlashScan device setting: "Use EFILive's Fast Can Mode" for CMD/CME controllers. Even when this option was disabled, CMD/CME flashing would still use fast CAN mode.

Fixed folder templates problem where new folders were not being created (if required) when using the "Save As" option for Scan and Tune files.

Fixed [Copy] option not working in [F3: Tune]->[F3: Calibration] display.

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

FlashScan/AutoCal Firmware: V2.07.128 (Nov 03, 2017)

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.

Build 121 Enhancements:

Added option to display either O2% or EQR when displaying data from the ALM wideband controller.

Build 120 Enhancements:

The "Self Tests" option in AutoCal's advanced menu now requires the user to press [Ok] and [Next] simultaneously to activate. That prevents unwanted/accidental activation of the "Self Tests" option - which is destructive to the Data and Config file systems.

Added option to display either EQR or O2% for the ALM wideband on FlashScan's "Display WO2" screen. Use the [0] key to toggle the display between EQR and O2%

Updated the ALM wideband serial interface to report as "warming up" while temperature is reported as being below 500C (932F). Once temp is above 500C the sensor's lambda/AFR value will be displayed.

Build 126 Bug Fixes

Fixed PLX SM-AFR wideband display issues.

Build 125 Bug Fixes

When reading a tune file, if there is not enough room on FlashScan or AutoCal to save it the error $050A "Not enough space to save tune file" is now displayed instead of the error $0522 "Incorrect CRC in tune file".

When black box logging some controllers the timestamp on each data frame was set to zero instead of the actual time that the data frame was recorded.

Remote.ska file was not being updated with controller's details if a matching auth-code already existed for that controller when the controller was being read for a second or subsequent time

Build 124 Bug Fixes

Low power mode was being incorrectly activated during pass-thru data logging.

Build 120 Bug Fixes

Fixed ALM wide band display on FlashScan.

Fixed read/flash failures on VPW based controllers if/when a serial device (such as a wide band controller) is connected and transmitting serial data to FlashScan.

Fixed wide band data logging issue for ALM serial wide band.

Fixed problem that caused some GM controller types to be recognized as Cummins controller types which caused flashing to be disallowed with FlashScan devices that were GM only.

Build 119 Bug Fixes

Fixed some GM controllers that could not be licensed when flashing using FlashScan in standalone mode or in pass-thru mode from EFILive V8 (AutoCal is not affected, EFILive V7 is not affected).

Build 118 Bug Fixes

Fixed PID scaling for MAF, MAP, EQR and O2V when recording freeze frame data in the "Record All Diagnostics" option.

Fixed PID values displaying as minimum or default values in freeze frame data if the PID is selected for data logging.

Build 117 Bug Fixes

Fixed problem where *.ctz tune files are incorrectly deleted from the FlashScan or AutoCal device after a failed flash followed by a failed read.

V7 Software: V7.5.15

Known Issues

The E92 controller's serial number is not displayed correctly in the V7.5 software. Please use the V8 software to display the E92 controller's serial number.

Added VIN, Serial Number and Operating System Number as tags for scan and tune filename templates.

Added VIN display when opening Cummins HD tune files.

Added "full binary compare" option to compare the complete binary data of each segment when doing tune file comparisons. Useful for detecting tune file changes not made by the EFILive software.

Build 329 Enhancements:

Added option to edit labels for calibrations that support editable axis labels. Right click on the calibration and select "Edit Row Labels" or "Edit Col Labels".

Out of range cell value are now displayed with a black border. The red border used previously was difficult/impossible to see when the cell's background color was also red.

Build 328 Enhancements:

Removed controllers that can't be read using the V7 software from the list of controllers available for uploading (reading). The V8 software must be used to read those controllers instead.

Added support for E81 controller.

Added "Save tuning file using template..." option.

The "Save" option is now enabled after modifying a log file's calculated PID selection.

Allow V7 tune editor to enter values larger or smaller than the EFILive pre-defined limits. You may now enter values up to the controller's physical storage limits.

Build 324 Enhancements:

Added two new DPF PIDs: REGENR and REGENIR.

Added a "script compatibility mode" option that allows scripts with ambiguous labels to execute without error. This option ignores ambiguous labels and uses the first label in a table's axis that matches the label in the script. This is the way scripts used to execute in older versions of EFILive.

Added a new template sequence option tag <seq0> which will add a sequence number of 1 to 4 digits depending on the magnitude of the number. I.e. the number is not zero padded to a fixed number of digits.

Added a new template option to allow the sequence number to include the letters A..Z.

Build V7.5.15 Bug Fixes

Fixed *.ctz tune file saving issue that caused tune files to be saved in a corrupt format that could not be re-opened with either the V7 ro V8 software packages.

Fixed SAE.MAP scaler for forced induction data logging platforms.

Build 344 Bug Fixes

E98 *.cax file address ranges were configured incorrectly, causing some *.cax definitions to be incorrectly rejected as "out of range".

Build 341 Bug Fixes

The following controller type files may not load correctly in V7.5 with the error "Integer Overflow": E35A (LBZ), E35B (LMM), E80, E81, E82 and E84.

The following controller type files may display invalid checksums when opened in V7.5, even though the checksums in the file are correct: CMB, CMC, CDM and CME.

Some CME tune files are not displaying some calibration tables correctly.

Build 332 Bug Fixes

CMD/CME transmission segment checksums were not being computed correctly and may result in a failed flash.

Build 331 Bug Fixes

The beta-8 release was not recognizing previously licensed controllers as licensed.

When opening a badly formatted (corrupt) tune file, the attempt to re-save the file as "badbinfile.ctz" is no longer made as that may cause further corruption. When reading a file from a controller, corrupt data will still be saved as "badbinfile.ctz" so that it can be sent to EFILive for analysis.

Build 330 Bug Fixes

Fixed "Range Error" when loading tune files that are not supported for editing in V7 but are supported for reading/flashing via the V8 software.

Fixed Pro License detection problem

Build 329 Bug Fixes

Fixed CMC CSP5 tune files not loading.

Calibrations that are outside of EFILive defined ranges are no longer flagged as "out of range" and are no longer automatically modified to fall within the EFILive ranges when loading a tune file.

Build 324 Bug Fixes

Bitmasks in user defined calibrations (*.cax files) were not being applied to fields defined as 32 bit.

Fixed folder template problem where new folders were not being created (if required) when using the "Save As" option for Scan and Tune files.

Fixed installer so that the [Edit]->[Properties]->[Folders] settings are now preserved correctly during a software re-install. Previously those settings were incorrectly reset to defaults during an install.