Known issues in V7.2.2
Known issues in V7.2.2, last updated June 17, 2005.
The following issues are fixed in V7.2.2 Patch 001.
The V7.2.2 Patch 001 file can be downloaded here:
http://www.efilive.com/downloads/downloads_7.html
Date:
May 10, 2005
Description:
The Scan Tool cannot connect to FlashScan while the Tuning Tool software is open.
and
The Tuning Tool cannot connect to FlashScan while the Scan Tool software is open.
The Scan Tool will display this message if the Tuning Tool is open:
Error code: ERR_NOCABLE/31
No interface cable found.
The Tuning Tool will not be able to communicate with the PCM or the FlashScan cable if the Scan Tool is open.
Status:
Fixed in V7.2.2 Patch 001
Workaround:
Close the Scan Tool software prior to any PCM read or reflash attempt.
or
Close the Tuning Tool software prior to any connection attempt with the Scan Tool software.The following issues are fixed in V7.2.3 pre-release 001Date:
May 11, 2005
Description:
The engine RPM values are not displayed for each gear when editing vehicle speed data.
Status:
Fixed in V7.2.2 Patch 001
Workaround:
None.
The V7.2.3 is not available yet. It is scheduled for pre-release on May 31, 2005
Date:
May 19, 2005
Description:
The Scan Tool fails if connected and disconnected 3 times in a row, without logging any data.
Status:
Fixed in V7.2.3 pre-release 001
Workaround:
Close and restart the Scan Tool software if you have connected and disconnected without logging any data.Date:
May 21, 2005
Description:
Black-box log files are displayed with zero frames if the FlashScan unit is programmed when one or more PIDs are set to priority 2 or priority 3.
Status:
Fixed in V7.2.3 pre-release 001
Workaround:
Make sure ALL PIDs are set to priority 1 prior to programming them into the FlashScan unit for black-box logging.Date:
May 26, 2005
Description:
IMPORTANT:
There is a small chance that a PCM may be rendered unusable during a full reflash procedure.
Full reflashing has an unavoidable window of failure. EFILive has been designed to include a full flash recovery system that, in the event of failure, allows the full reflash process to be retried until successful (or until power is removed from the PCM).
EFILive's full flash recovery may not operate correctly if a failure occurs after EFILive erases the flash memory and prior to the first block of data being written to the PCM.
Status:
Fixed in V7.2.3 pre-release 001
Workaround:
To prevent this failure, close and reopen the "Reflash PCM Operating System" window, prior to any Full Flash operation. That includes closing it and reopening it between mutliple full flash attempts, successful or not.
Date:
May 28, 2005
Description:
IMPORTANT:
There is a small chance that a PCM will recognise EFILive's custom operating systems as fully calibrated systems. That is not the case, EFILive's custom operating systems do not contain any calibration data. If the PCM attempts to operate normally, when no calibration data is present , it will be rendered inoperable and unrecoverable.
The new operating systems available here: http://www.efilive.com/downloads/downloads_os.html
have been altered to force the PCM into "dead poll" mode after the custom operating system has been reflashed, waiting for you to reflash a valid calibration.
The problem can only occur during a custom operating system upgrade reflash process. If you have already successfully reflashed a custom operating system into your PCM, you do not need to reflash your PCM with the new operating systems that have been made available.
Status:
Fixed in V7.2.3 pre-release 001
Workaround:
Please discard any EFILive custom operating systems that you may have downloaded prior to May 28, 2005.
EFILive has updated ALL custom operating systems and recommend that you re-download any custom operating systems prior to upgrading your PCM.
UPDATE: All custom operating systems were updated again on May 29, 2005. Please discard any custom operating systems downloaded on or before May 28, 2005
The following issues are fixed in V7.2.3 pre-release 003Date:
May 30, 2005
Description:
Changing the ETC tables too far from stock may cause the ETC system into limp mode. A TAC (Throttle Actuator Controller) communications failed DTC will be set.
The TAC module stores a sane ETC table. If the PCM commands a value too far from the TAC sane value then the TAC logs a comms fault. Too many comms faults and the PCM will go into limp mode. How far from stock your ETC tables have been changed, determines how quickly a comms DTC can be set.
Status:
No fix available.
EFILive does not have access to the TAC module and cannot change the calibrations stored in it.
Workaround:
Restore your factory ETC settings.
The V7.2.3 pre-release 003 is scheduled for pre-release on June 19, 2005
Date:
June 15, 2005
Description:
When setting Scan Tool maps to hide cells with a low cell count, the first "n" datapoints are incorrectly discarded. This has the effect of skewing the cells' values.
(where "n" is the low cell count threshold).
Status:
Fixed in V7.2.3 pre-release 003
Workaround:
Do not use the Maps' cell hiding feature until pre-release 003 is available.Date:
June 17, 2005
Description:
Configurations settings are not being saved on some Window 98 operating systems.
Status:
Fixed in V7.2.3 pre-release 003
Workaround:
None
Reply With Quote
Originally Posted by SSbaby
jes
