|
||||||||
|
||||||||
MERCEDES Benz Commander software V 4.0 Instrument Cluster Odometer Correction This function works on clusters, which use K-Line as databus as well as on some clusters, which use CAN (since version 1.5) and were produced by VDO. In the vehicles, which use K-Line the odometer is stored only inside the Instrument Cluster, so changing its value is enough. This is not the case with newer vehicles, where the odometer may be stored in several places like EZS and ECU.
It is very important to note that the instrument cluster of vehicles, that use K-Line as databaus, also stores the history records of the last 5 oil changes. Each record contains the mileage at which the oil was changed, the remaining mileage, the remaining days and the quality of the oil. If you wish to change these records you can do this by using the special function 'Dump Tool'. First, you must read the EEPROM of the instrument cluster by using the special function 'Custom memory read/write'. After that you must load the dump in the dump tool and it will show you the current oil change history records. You can change the data in the records, save the dump and then you can program the saved dump to the EEPROM of the instrument cluster.
|
Dump Tool
This application needs the EEPROM dump, which has been saved as a file, from the corresponding unit. After the dump file is loaded, some modifications will be made and you need to store the dump as a new file, which you can program with a special programmer into the device that the dump is from.
The dump tool receives as input a dump file from the corresponding unit (input dump is loaded with the "Load dump" button). The dump file can be read either via OBDII but also with a programmer (especially for units where reading via OBDII is not possible). As output the dump tool displays some data extracted from the input file and/or makes some modifications to the input data. If modification were made (for some sub-functions there are no modifications made, only data are visualized) the user has to write the modified dump to desired file (with the "Save dump" button), and then this modified dump should be saved back to the device via OBDII or with a programmer.
If data are read/written with a programmer the user must make sure that the proper byte order is used. Because most of the programmers are reading the data on 16bit words, the byte order in the dump depends on the used programmer - some programmers produce dumps starting with the least significant byte, and some produce dumps starting with the most significant byte. This means that for the same unit two different programmers can produce different dumps. For that purpose a button "Swap bytes" is provided. This buttons changes alternatively the byte order into the dump. So, if after loading the dump file into the dump tool data cannot be extracted or modified, please try to swap the bytes to get a correct result.
ECU
By using this special function it is possible to read/write the flash memory of some engine control units. For some engine modules it is also possible to read/write the EEPROM memory.
Immobilizer
The Drive Authorization System (DAS) is the name for the Mercedes Immobilizer system combining vehicle access and drive authorization. Prior to 1996, DAS was separated from the engine control module, and ignition switch operation was based solely on a mechanical key. An early version of DAS was first introduced in approximately 1993 when Mercedes started networking DAS, the engine, transmission, ABS, and traction control systems on a common data bus called CAN.
The Mercedes pneumatic control doorlock system has been in existence since the early 1980s, and although now it is much more advanced, it is still in use today. It steadily became more sophisticated, adding features like central locking, starter lock-out, and steering lockout.
DAS 3 is the most sophisticated and advanced generation of DAS. DAS 3 was introduced on the C, E and CLK class in 1997 and the S class in 1998 (210/208/202), increasing each year with more models phased in. This system has all the same features of DAS 2b except that the ignition switch is now fully electronic (the mechanical key is used only for vehicle access). This means that with DAS 3, both access and drive authorization are fully electronic.
Access authorization using the remote key uses both infrared and radio transmission, but the electronic key drive authorization only uses infrared. The electronic key transfers a radio wave code to the electronic ignition and starter switch (EIS).
With this special function you can read/write AAM and DAS EEPROM data. For Mercedes ML you can program a transponder using the "Key Programming" function. After this you can learn the already programmed transponder to the immobilizer system. Simply specify the key number (it must be between 1 and 8) and press the button "Learn ML Transponder".
TV/AUX Activation/Deactivation
By using this special function you can have the TV/AUX screen in the head unit enabled even when you are driving. You can also disable TV/AUX screen display during driving, if it is currently enabled, but you do not want it.
ESL
This special function allows you to read/write/erase the EEprom of both ESL processors. You can also unlock the ESL by using it. However, for this function to work you must make a direct connection to the ESL via K-line - pin 3 or 4 (pin 3 is the first processor and pin 4 is the second one).
If you erase the EEPROM of the ESL it will unlock automatically. After that you can write it.
In order to read the EEPROM of ESL CPU 1 and ESL CPU 2 the key should NOT be in the ignition lock. Just plug the diagnostic cable of the interface into the diagnostic plug of the car and open and close one of the doors of the car. After that you will have about 10 seconds to connect to the EIS and read the EEPROM of ESL CPU 1, or ESL CPU 2.
|
||||||||||||||||||
Contacts:
|
||||||||||||||||||
|
||||||||||||||||||
|
|
||||||||||||||||||