I am working on a project 1969 Camaro that is utilizing a good deal of Mercedes bits. Seats from a R172, Seat switch from C118, Dash from C117, Column and steering wheel from C117, etc.

I will share here what I have learned, and hoping for some help with some of the issues I have encountered.

For the C118 seat position switches, I produced the following matrix. This was for a drivers side switch. I believe the passenger side resides at 0x09, but have not confirmed that yet.

Seat Slide Forward: 0x08 0x01 0x00 0x00 0x00 0x00 0xC6
Seat Slide Backward: 0x08 0x02 0x00 0x00 0x00 0x00 0xC5
Backrest Recline Forward: 0x08 0x04 0x00 0x00 0x00 0x00 0xC3
Backrest Recline Backward: 0x08 0x08 0x00 0x00 0x00 0x00 0xBF
Seat Base Front Edge Up: 0x08 0x00 0x01 0x00 0x00 0x00 0xC6
Seat Base Front Edge Down: 0x08 0x00 0x02 0x00 0x00 0x00 0xC5
Seat Base Rear Edge Up: 0x08 0x00 0x10 0x00 0x00 0x00 0xB7
Seat Base Rear Edge Down: 0x08 0x00 0x20 0x00 0x00 0x00 0xA7

I will post some of the other modules when I get more time.

I am looking for help with the steering wheel buttons. As happened when I parsed the buttons themselves for the output voltage each was sending to the N135 module, the buttons are arranged in pairs. When the N135 sends a button press string to the N80 over LIN, I have not been able to differentiate the UP from DOWN, or LEFT from RIGHT, etc. The hex looks like this.Menu Up: 0x1C 0x01 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x5C
Menu Down: 0x1C 0x01 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x5C
Menu Left: 0x1C 0x04 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x59
Menu Right: 0x1C 0x04 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x59
OK Button: 0x1C 0x10 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x4D
Back Button: 0x1C 0x10 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x4D

Volume Up: 0x1D 0x01 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x5B
Volume Down: 0x1D 0x01 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x5B
Mute: 0x1D 0x04 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x58
Voice Control: 0x1D 0x04 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x58
Phone Answer: 0x1D 0x10 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x4C
Phone Hangup: 0x1D 0x10 0x00 0xFF 0xFF 0x61 0xCF 0xFF 0x4C

I have tried looking at other ID's and sending config commands, but I dont actually have a C117 in order to sniff the bus. If anyone has any info about this or a source for say a .ldf file for this bus, that would be great.

TIA

 

Top work mapping that seat switch, that’s useful data. On the steering wheel buttons, you’re hitting the common problem they send the same LIN ID for paired functions. The N135 decides which one based on a resistor ladder in the switch hardware. You need to measure the voltage on the signal wire from each button pair; that’s how the module tells them apart. No different LIN data, just analog voltage levels. Check the resistance values between the switch and ground for each button.

 

Actually, I already did that part, when i planned to just use an Arduino to replace the N135. That was easy. I was going to just send the serial info down to a second arduino, by passing the N80, but decided to try using the N135 instead. The N135 knowing the difference is worthless if it doesnt communicate that to the N80.

i also have the window switches and headlight switch mapped, as well as the multiplex logic for the multifunction stalks. I will post those over the next couple of days. Gemini lost much if my data, so i am all over google about retrieving it.

 

Looks like your reply was meant for a different forum thread about CANbus modules and Arduinos, not the W210 diesel fuel leak. You might have pasted the wrong text.

 

OK, Super member, scroll up and check out the title of this thread “LIN Bus Info”.

since I started it, i should think i know what is the topic.

 

Good luck on your '69 Camaro...

 

thank you so much, fanatic! Good to see you’re not just another self appointed moderator, policing threads, but really contribute!