ML-GL Eis
ML-GL Eis
ML-GL Eis
Complaint:
Intermittent no start with both smart keys and the ICM will not turn on (only the multi function display will illuminate ty-
pical of a CAN wake-up). No codes are stored in the EIS ECU. The central locking system operates normally. The gui-
ded test for the EIS and smart keys as outlined in DAS may not reveal a fault.
Please Note:
• If the fault cannot be verified, then monitor if there is a delay to when the ICM turns on 'after' the ignition is tur-
ned to the number 2 position. Normally the reaction time of the ICM should be immediate.
• Monitor if the complaint can be readily duplicated immediately after the vehicle is unlocked.
• In the initial short test, there are no Drive Authorization codes stored in the ME control module.
• Check the EIS ECU log and verify that there is a fault event stored as shown in the attached file (Initial EIS con-
trol unit log).
Cause:
Faulty EIS
Remedy:
Perform the guided DAS test in EIS.
Note: Prior to performing the DAS test, you should see event code "65535" in the EIS ECU log. After performing the
DAS test, this code will change to another value such as 4, 6, 17, 25 etc. instead of 65535. This new value will be dis-
played on the test result page and indicates which component is faulty (EIS, ESL; key) or if the system is okay.
If diagnosis leads to replacement of EIS, please include the following with the returned part:
Please Note: Claims will be debited if the EIS is replaced for any other reason other than the criteria mentioned in this
LI document, and/or the DAS data requested is not accompanied with the returned part (see attached document for
example of a drive authorization code indicating replacement of EIS).
Attachments
File Description
DAS_EIS_Test_Result.pdf Fault event after processing Drive Authorization codes di-
recting replacement of EIS