E350 w212 Interior Temperature Sender
11-01-2018, 01:03 PM
#1
Junior Member
Thread Starter
E350 w212 Interior Temperature Sender
Hello everyone I’m looking to see if someone could tell me where the interior temperature sender unit is located please on my W212 e350 ? I have a fault code listed for this item and after clearing the code it’s still coming back so clearly a issue.
Thank you
Thank you
11-01-2018, 01:51 PM
#2
Out Of Control!!
Join Date: Jul 2003
Location: North Scottsdale, AZ
Posts: 15,903
Received 4,446 Likes
on
3,154 Posts
'71 Pinto
Sensor part # 2118300272
The following users liked this post:
Wenglish1984 (11-01-2018)
06-23-2023, 07:20 PM
#4
Newbie
Join Date: Jun 2023
Location: Dallas, TX
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
2012 E350
Konigstiger - Are you able to find part # for the 'other' W212 interior temperature sensor (the one in the overhead console)? Mine is bad, I removed it, it is slightly different from the part you listed here for the in-dash temp sensor, and the numbers on mine don't match anything, maybe it is aftermarket.
06-27-2023, 01:36 PM
#5
MBWorld Fanatic!
Join Date: Apr 2019
Location: Silicon Valley
Posts: 5,936
Received 3,652 Likes
on
2,429 Posts
MY'14 W212 M276 3.5NA @60kMi
Sensor ok... LIN network initialization not so ?
Drew, the "Temp sensor" you're dealing with is hosted inside the OCP. I have the same issue with it reporting junk data to the Air-Con "AAC Module".
Replacement did not cure that issue.
I run a properly resoldered AAC controller.
So we are in the same boat with this issue.
OCP reports both over CAN and simple LIN ... at this stage I am thinking LIN thresholds need to be retrained using Xentry initialization process.
I believe LIN communications are impacted by unreliable power supply levels from the shared (once painted) GND eyelets.
Replacement did not cure that issue.
I run a properly resoldered AAC controller.
So we are in the same boat with this issue.
OCP reports both over CAN and simple LIN ... at this stage I am thinking LIN thresholds need to be retrained using Xentry initialization process.
I believe LIN communications are impacted by unreliable power supply levels from the shared (once painted) GND eyelets.
