EFILive Release Notes

 

Version Numbers

EFILive Software V8.3.24

 

·         FlashScan/AutoCal V3:  Firmware: V3.00.092 (Boot Block: V3.00.006)

·         FlashScan/AutoCal V2:  Firmware: V2.08.190 (Boot Block: V2.08.009)


EFILive V8 Software

 

V8.3.24

·         Fixed VIN change option on the CM2450B (CMF) controller - which was failing with error $0101 "No data received." if the "Clear DTCs before changing VIN" checkbox was checked (even when it was disabled)".

·         When unlocking controllers via the [F3: Tune]->[F2: Read]->[Lock/Unlock] option with the "Try Common Alternate Keys" method selected, the ECM would not allow itself to be unlocked even when the correct alternate unlock key was computed and used.

·         Fixed justification of Y-axis on the right end of each chart. They were right justified, should have been left justified.

V8.3.23

·         Added two new serial-based, wide-band, BEN factor PIDs: BENLAM_1 and BENLAM_2, based on commanded v's actual lambda.

·         Added visual/color alarms for dashboard gauges.

·         Added right-click option to manually reset min/max, tell-tale values on dashboard gauges (or hotkey Ctrl+R).

·         Fixed selection bug when moving gauges up/down in the gauge list of the dashboard editor.

·         Fixed "Item not found" error when deleting a gauge while it was expanded, with its details visible.

·         Fixed bug that allowed non-calculated PIDs to be added to an existing data log. Only calculated PIDs may be added to an existing data log.

·         Fixed "integer overflow" error when loading user defined PIDs that have one or more DMA operating systems defined but zero DMA PIDs defined.

 

FlashScan/AutoCal V3 Firmware

V3.00.092

·         When black box logging an external CAN based wide-band data, the PIDs were being incorrectly renamed from "GPM.pidname" to "WO2.pidname". That meant those PIDs would not be displayed correctly when the BBX log file was displayed in the V8 scan tool.

V3.00.091

·         When flashing a tune file via an AutoCal device, verify that the AutoCal is linked to a FlashScan device before checking if the tune file is linked to the AutoCal. That way an un-linked AutoCal will report that it is unlinked instead of the more confusing error of "the tune file is not linked to the AutoCal".

FlashScan/AutoCal V2 Firmware

V2.08.190

·         When flashing a tune file via an AutoCal device, verify that the AutoCal is linked to a FlashScan device before checking if the tune file is linked to the AutoCal. That way an un-linked AutoCal will report that it is unlinked instead of the more confusing error of "the tune file is not linked to the AutoCal".

Calibration Updates

V8.3.24

·         A41

·         E98

V8.3.23

·         CM2220

·         CM2350A

Documentation Updates

V8.3.24

·         EFILive V8 Reference.pdf.


V8.3.23

·         Connections and Wiring Reference.pdf.

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.