M-Class (W164) Produced 2006-2011: ML280CDI, ML320CDI, ML420CDI, ML350, ML500, ML550

Keyless go

Thread Tools
 
Search this Thread
 
Rate Thread
 
Old Oct 13, 2024 | 06:30 AM
  #1  
Kejvi's Avatar
Thread Starter
Newbie
 
Joined: Feb 2024
Posts: 7
Likes: 0
W164 ML-Class 350 Bluetec 2011
Keyless go

Helli everyone. I have an ML 350 bluetec 2011 (Grand Edition) and the keyless go system wont work. There is no message showed on the Control Unit and also no error codes from any scanner. The scanners I have tried are dispöaying the Keyless Go system to work fine. The button in the handle won’t work and also the start and stop button. Does anybody have an idea what that should be?
Reply
Old Oct 13, 2024 | 06:16 PM
  #2  
Baltistyle's Avatar
MBWorld Fanatic!
5 Year Member
Community Builder
Liked
Loved
 
Joined: Feb 2017
Posts: 2,289
Likes: 1,196
From: Baltimore County, MD
'13 s212 63 p30. '06 LX470
The first thing to be asked is was a new battery installed in the remote? Do other handles and feature work?
Reply
Old Oct 14, 2024 | 01:53 AM
  #3  
Kejvi's Avatar
Thread Starter
Newbie
 
Joined: Feb 2024
Posts: 7
Likes: 0
W164 ML-Class 350 Bluetec 2011
None of the handels works and no other features too. I bought the car like that. I replaced the battery of the remote and norhing changed.
Reply
Old Oct 14, 2024 | 11:40 AM
  #4  
jimyj's Avatar
Member
 
Joined: Jun 2024
Posts: 191
Likes: 57
E320
It sounds like your ML 350's Keyless Go system might be experiencing issues related to the sensors or communication between the key fob and the vehicle. Since there are no error codes and the scanners show the system as functioning, it could be a problem with the proximity sensors in the door handles or the antenna system responsible for detecting the key fob's presence. Corroded or damaged wiring in the door handle can also disrupt the signal, preventing the button from working. Additionally, since the start/stop button is also unresponsive, it's worth checking the condition of the start/stop button itself, as a faulty button mechanism could be causing this issue. To get to the root of the issue, I recommend checking the Comfort Convenience Module for any stored fault codes or unusual activity logs that might not trigger a dashboard warning. This module handles functions related to keyless entry and start systems. A comprehensive scan with a full system scanner like youcanic will help access these modules effectively, whereas a basic scanner such as the Ancel AD310, which typically reads engine codes, might not detect these specific issues. Have you already tried the basics like testing the button cell battery in the fob to ensure it's not a simple power issue?
Reply

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 


You have already rated this thread Rating: Thread Rating: 0 votes,  average.


All times are GMT -4. The time now is 06:15 AM.