w210 EIS/EZS problem

**batrady** · 20th March, 2019, 05:43 PM

Hi to all,I have a problem with w210 e270cdi, have 1 key and it wont turn ignition on
The eis number 2105450208Q2
I read eis motorola with mask 1d69j and key dump 0f82b, can someone tell me is that a correct dump. I made esl virgin, but do not have any changes

**khoulioking** · 29th March, 2019, 08:26 AM

Hello dear,

yes the dump is correct, try to program new key then test it if is still the same problem so EIS must be replaced

**alexbeshko** · 29th March, 2019, 10:29 PM

Hi. Same problem. Central locking is ok but key dont want turn. In actual values i see that start message is not received from transmitter key. Key data are beeng entered - NO. Energy supply for transmitter key - NO.
Please check dumps from EZS out CPU and KEY.

**MVVL** · 30th March, 2019, 09:13 AM

Read MCU2. These dumps are ok. Thanks.

**droidwayne65** · 30th March, 2019, 01:02 PM

Originally Posted by alexbeshko

Hi. Same problem. Central locking is ok but key dont want turn. In actual values i see that start message is not received from transmitter key. Key data are beeng entered - NO. Energy supply for transmitter key - NO.
Please check dumps from EZS out CPU and KEY.

The problem is apparent in the data you posted. The EIS isn't turning on power to activate any key, so making another key won't solve it; repair or replace the EIS.

**alexbeshko** · 30th March, 2019, 01:09 PM

Thanks. So it means that dumps look ok. If I take new EIS from scrapyard I can load this dumps and all must be ok? Or need renew ESL and ECU?

Надіслано від мого SM-J500H, використовуючи Tapatalk

**droidwayne65** · 30th March, 2019, 01:23 PM

Originally Posted by alexbeshko

Thanks. So it means that dumps look ok. If I take new EIS from scrapyard I can load this dumps and all must be ok? Or need renew ESL and ECU?

Надіслано від мого SM-J500H, використовуючи Tapatalk

Get the same part number, clone the eeproms and you're good to go.

**alexbeshko** · 30th March, 2019, 01:26 PM

I will read mcu2 and post here. Maybe possible to repared?

Надіслано від мого SM-J500H, використовуючи Tapatalk

**droidwayne65** · 30th March, 2019, 01:43 PM

Originally Posted by alexbeshko

I will read mcu2 and post here. Maybe possible to repared?

Надіслано від мого SM-J500H, використовуючи Tapatalk

May as well verify that nothing is wrong with it.

**alexbeshko** · 30th March, 2019, 08:02 PM

This is a dump from cpu inside

**alexbeshko** · 30th March, 2019, 08:03 PM

Please check if all is ok with this dump. Thanks.

**droidwayne65** · 30th March, 2019, 09:41 PM

Originally Posted by alexbeshko

Please check if all is ok with this dump. Thanks.

The dumps are individually ok but they don't belong to the same EIS

. Someone may have previously swapped the outer mcu and made a key for it. It's unlikely they'd have gone to the trouble of swapping the inner. Did you save a ESL read before renewing?

**alexbeshko** · 30th March, 2019, 09:44 PM

I did nothing with esl and not yet try swap it.

Надіслано від мого SM-J500H, використовуючи Tapatalk

**droidwayne65** · 30th March, 2019, 09:54 PM

Originally Posted by alexbeshko

I did nothing with esl and not yet try swap it.

Надіслано від мого SM-J500H, використовуючи Tapatalk

Did you read and save the ESL data? If so, post the file, so I can try to determine which mcu matches it. Funny thing about this EIS is that both mcus have a data pattern that's usually found in the outer.