Professional Documents
Culture Documents
Release History
Release History
----------------
Release 2.5.6.1981-1983
- Security updates
Notes:
Using the command line in PowerShell and CMD you can verify all files in a folder
for compatibility.
Subfolders will be automatically generated and all files moved into "Done",
"Duplicate" and "Error" folders.
The list of up-to-date ecu identifier numbers can be seen running the C++ script
named "GetSolutionInfo.cs" from within the application.
Release Comments/Hints:
+ Remember the software only accepts P-Codes when working with Renault
+ DF-Code to P-Code convertion can be different between car models; the included
cross reference is static
Release Comments/Hints:
+ More presets are available on the forum at this link
http://www.mtx-electronics.com/e107_plugins/forum/forum_viewforum.php?74
Release Comments/Hints:
+ We advise you verify that your default settings are correct (ex. disable file
size check if you use partial files)
+ The preset window is shown by pressing the (P) circle button on the top/right
corner of the application window
Release Comments/Hints:
+ Testing ecu are not officially supported
Release Comments/Hints:
+ When you have both OBD and manufacturer inputs if you fill them both the faults
will be scanned in both tables at once and cleared
+ VAG 4 digit hexadecimal manufacturer code input should not contain the group
letter (ex. P3071 = 3071)
+ VAG 5 digit decimal manufacturer code input should always be leading zero padded
(ex. 123 = 00123)
+ VAG 5 digit decimal manufacturer code input should always be fixed length (ex.
0123456 = 123456)
Release Comments/Hints:
+ When you have both OBD and manufacturer inputs if you fill them both the faults
will be scanned in both tables at once and cleared
+ VAG 5 digit decimal manufacturer code input should always be leading zero padded
(ex. 123 = 00123)