Keyless GO function problem.
The front sam (N10/1) is a "hub" for various signals, including the multiple CANs... disconnecting the battery appears to "reset" it. This was advice given to me, based on MB tech who noted that this often resolves CAN issues.
This was the LAST thing I tried, after pulling the cluster, carpeting, etc... Maybe worth a shot, before going in deep going to wiring/function diagrams, electrical checks, trip to dealer. Its also important to ensure your main battery is in good health, as the electrical systems are more sensitive to voltage and voltage drops.
The front sam (N10/1) is a "hub" for various signals, including the multiple CANs... disconnecting the battery appears to "reset" it. This was advice given to me, based on MB tech who noted that this often resolves CAN issues.
This was the LAST thing I tried, after pulling the cluster, carpeting, etc... Maybe worth a shot, before going in deep going to wiring/function diagrams, electrical checks, trip to dealer. Its also important to ensure your main battery is in good health, as the electrical systems are more sensitive to voltage and voltage drops.
The dealer won't order a key for me to run the diagnosis (requires 2 keys), as the government hasn't processed my title application yet (it has been about 6 weeks and counting). The dealer also said they probably wouldn't be able to program the key anyway without the keyless go working. Oh, and it's $600 for a replacement key! They did test the button functions on my fob and they are all working.
I've ordered a used Keyless Go module from Ebay with the same part, hardware, and software numbers to see if that allows me to establish communication. If that still doesn't work, then I think I'm going to have to start measuring resistance and continuity on the appropriate CAN networks. If that does fix the problem, I'll take the old module apart and see if I can figure out what's broken (it worked intermittently before failing, so likely a solder connection).
I guess the one thing I'd like confirmation of is whether or not Xentry should be able to communicate with the Keyless Go module. The car doesn't scan that controller in the "quick test", so it doesn't show a fault. My guess is it just queries all responding controllers and doesn't really know which ones should be present based on the VIN if one doesn't respond. However, this is my first Keyless Go car, so I'm not sure how the controller should respond to a direct query.
This is definitely much more of an adventure than I really wanted to deal with. However, I'd rather be doing this troubleshooting myself vs the dealer doing the same thing for $150/hr and getting nowhere. The dealer tried to sell me a $150 quick scan to identify the problem. Ha! I know that charge code, and I know exactly what it reports. It's useless.
Last edited by Turboaction; Dec 31, 2020 at 02:18 PM.
I can only imagine what face I'd make if Xentry told me I didn't have an instrument cluster! I did cause my cluster to go berserk when I had a cheap OBD2 scanner plugged into the diagnostic port while driving. The car was not amused at all!
Last edited by Turboaction; Jan 1, 2021 at 12:48 PM.
I can only imagine what face I'd make if Xentry told me I didn't have an instrument cluster! I did cause my cluster to go berserk when I had a cheap OBD2 scanner plugged into the diagnostic port while driving. The car was not amused at all!
I'm not sure what version of Xentry you have (or whom from)... but in my experience with a few modules I checked on our cars to see if updates to software were available required logging into MB mothership. However, I'm not fluent on Xentry... I know there's also module start-up activations, which I was hoping to use once I replace my blind spot radar (if needed)... but that might also be online.
Seems like DAS was offline and only good up to W211. W212+ is Xentry mostly online for coding. There's Vediamo, if you want to go down that rabbit hole and risk. There are people who will login for a fee for you to update software.
The Best of Mercedes & AMG
I'm not sure what version of Xentry you have (or whom from)... but in my experience with a few modules I checked on our cars to see if updates to software were available required logging into MB mothership. However, I'm not fluent on Xentry... I know there's also module start-up activations, which I was hoping to use once I replace my blind spot radar (if needed)... but that might also be online.
Seems like DAS was offline and only good up to W211. W212+ is Xentry mostly online for coding. There's Vediamo, if you want to go down that rabbit hole and risk. There are people who will login for a fee for you to update software.
I was actually under the impression that the keys were ordered and arrived at the dealer already working. This is the first I've heard of the key needing programmed to the car.
I was actually under the impression that the keys were ordered and arrived at the dealer already working. This is the first I've heard of the key needing programmed to the car.




We tested the key for door locks at the dealer and as it worked we thought it was all fine but a couple of days later I tried to start the car with it and it did nothing when I pressed the start button. Doors and trunk open just fine with it.
Thought to go back to the dealer but then for some reason I decided to take the start button out and see if the key starts the car using it as a regular key and yes, the car started when I turned the key in the switch. After this I replaced the button and guess what, the keyless start from the button now worked.
My thinking is that the key requires one start by turning it in the start switch before the keyless start from the button works. Wonder if this procedure is what the dealer calls "programming" the key for the car? I think all keys need to be made in MB in Germany and they mail them in. That's why it takes a few days to get the new key.
Anyway, my new key needed to be "programmed" to the car by doing one start with it as a regular key in the switch.




We tested the key for door locks at the dealer and as it worked we thought it was all fine but a couple of days later I tried to start the car with it and it did nothing when I pressed the start button. Doors and trunk open just fine with it.
Thought to go back to the dealer but then for some reason I decided to take the start button out and see if the key starts the car using it as a regular key and yes, the car started when I turned the key in the switch. After this I replaced the button and guess what, the keyless start from the button now worked.
My thinking is that the key requires one start by turning it in the start switch before the keyless start from the button works. Wonder if this procedure is what the dealer calls "programming" the key for the car? I think all keys need to be made in MB in Germany and they mail them in. That's why it takes a few days to get the new key.
Anyway, my new key needed to be "programmed" to the car by doing one start with it as a regular key in the switch.
What you described is what I've read as well. My car already has all of the key tracks open, so the key should require no programming at the dealer. I've read it is possible to reject the programming charge, as they're not actually performing it. I also read starting the car with the key fob in the ignition is what synchs the key to the Keyless Go module. It also gets the key replacement back into the range I've read previously ($450+tax). I will let everyone know what my experience is with the key replacement if I ever get the Keyless Go module up and running.
In the mean time I'm getting my W220 back on the road. I installed an aftermarket alternator in a pinch, and on my 3rd warranty swap I broke off the transmission cooler fitting in the oil line. So now the front of the car is removed while I wait for the new radiator (with integrated transmission cooler) to come in!
So anyway, after deciding the fuse assignments and wiring diagrams didn't make sense (I'm using information for the W212.091, which is what Xentry assigns when it connects to the car), I decided to just start pulling all the fuses in the trunk. I eventually stumbled upon a blown fuse in position 92, which the documentation showed as being for the start-stop function on the transmission. Well, I replaced fuse 92, saw voltage at pin 1 on the keyless go module (the replacement one), and everything started working.
So, I don't know the cause of the blown fuse, but maybe the old module was going wonky and blew it. It seems odd, as the keyless go module looks like a super low power module, so it's likely some other thing that feeds off that circuit (TBD). Either way, I have a different module in the car, it didn't require coding, replaced the fuse, and all is well. Now I just need to reinstall all the trunk carpeting and should be in good shape until the fuse decides to blow again.
So anyway, after deciding the fuse assignments and wiring diagrams didn't make sense (I'm using information for the W212.091, which is what Xentry assigns when it connects to the car), I decided to just start pulling all the fuses in the trunk. I eventually stumbled upon a blown fuse in position 92, which the documentation showed as being for the start-stop function on the transmission. Well, I replaced fuse 92, saw voltage at pin 1 on the keyless go module (the replacement one), and everything started working.
So, I don't know the cause of the blown fuse, but maybe the old module was going wonky and blew it. It seems odd, as the keyless go module looks like a super low power module, so it's likely some other thing that feeds off that circuit (TBD). Either way, I have a different module in the car, it didn't require coding, replaced the fuse, and all is well. Now I just need to reinstall all the trunk carpeting and should be in good shape until the fuse decides to blow again.
You got it! I didn't see the two wiring diagrams listed for W212.091 as identified in DAS. However, I loaded up documentation for another W212 model and the above diagram appeared, aligning with what you provided! I see this fuse now powers the rear switching module and the upper and lower sensors. I have no idea what these are, but I hope they aren't the cause of the fuse blowing. Either way, at least now the problem is isolated and the wife is happy!
I entered a random '14 E550 VIN into WIS, which I used for the above diagram and below fuse assignment for Fuse 92:




I would just confirm the hands-free works, maybe check current draw across circuit (Fuse 92) and leave well enough alone. Next time KeylessGo acts up and the fuse it blown, you can dig deeper again.




I would just confirm the hands-free works, maybe check current draw across circuit (Fuse 92) and leave well enough alone. Next time KeylessGo acts up and the fuse it blown, you can dig deeper again.
Good to know!


