2016 COMAND NTG 5s1 (5.1) RETROFIT from NGT4




My 2016 COMAND NTG 5s1 retrofit into my 2010 W207.
















So???
What 2016 parts was needed SO FAR to do this retrofit from NTG4 to 5s1:
1. Comand 5s1 big version with built in HD navi
2. Screen
3. Video cable to screen
4. Repinning of cables in sockets
5. LAN antenna
6. H/K Amp
7. Camera and cablekit
8. Screen frame
9. New joystick with 4 buttons
10. Pincode
11. Maps with activation code
I am experimenting alot with programming and activating of menues. I got the AMG logo to start it of. And alot else so far.
So ALL that works now but
only PROBLEMS so far:
Navigation dont get a speed signal. So maps stop moving when it loses satelites.
Media dont showup in cluster. All else show up and work. Radio,Navi.phone...
AMG dails, then middle big one dont work. Guess it is also speed signal issue.
Camera dont send video
Last edited by Chris The Swede; Aug 17, 2016 at 07:09 PM.




Also the Camera wont work. It activates but just says camera not avalible even though it is there and it is powered up and can be programmed. I wonder if it has to do with the PDC that suddenly can be seen by star diagnose after installing a new front sam. Guess it goes into a different place on the SAM....
Now I am curious how easy it would be to retrofit this system into a 2012 W204.
How much programming did you had to do just to get the Comand system to work properly?





This is what I figured out so far of the rear.
And the pinout is as I think:
15 2.5mm Red and Blue +12v (20amp fused feed from F26 in front SAM)
12 2.5mm Brown, Ground
11 2.5mm Bround, Ground
9 0.75mm Blue and White. Mute input from E-Call or Telematics
16 0.5mm Blue/Black - MOST Wakeup
14 0.5mm Blue/Green = Wakeup output to the multimedia connection unit
13 Ground for multimedia connection unit BUT not used for codes 505/522/531 - But used if you have Telematics Service Unit
10 0.5mm Ground also goes to the multimedia connection unit
the black-12-pin subconnector (Connector C on the wiring diagram), it has 2 CAN connections
Body Can (Brown/Red to pin 9, and Brown to pin 3)
Telematics Can Black.White to pin 10, and Black to pin 4)
5,6,7,11,12 are the ethernet connection to the diagnostic socket for uploading online-manual from Star Diagnosis
Without Telematics CAN the display can not turn on
DISPLAY wiring - just in case this has changed
Pin 2 = +12v (red/white)
Pin 1 = Ground
Pin 8 = Telematics can black/white
pin 4 = Telematics can black
3,5,6,7 not connected




Actually the NEEDED programming is just the anti theft pin code. The rest is optional..

This is what I figured out so far of the rear.
And the pinout is as I think:
15 2.5mm Red and Blue +12v (20amp fused feed from F26 in front SAM)
12 2.5mm Brown, Ground
11 2.5mm Bround, Ground
9 0.75mm Blue and White. Mute input from E-Call or Telematics
16 0.5mm Blue/Black - MOST Wakeup
14 0.5mm Blue/Green = Wakeup output to the multimedia connection unit
13 Ground for multimedia connection unit BUT not used for codes 505/522/531 - But used if you have Telematics Service Unit
10 0.5mm Ground also goes to the multimedia connection unit
the black-12-pin subconnector (Connector C on the wiring diagram), it has 2 CAN connections
Body Can (Brown/Red to pin 9, and Brown to pin 3)
Telematics Can Black.White to pin 10, and Black to pin 4)
5,6,7,11,12 are the ethernet connection to the diagnostic socket for uploading online-manual from Star Diagnosis
Without Telematics CAN the display can not turn on
DISPLAY wiring - just in case this has changed
Pin 2 = +12v (red/white)
Pin 1 = Ground
Pin 8 = Telematics can black/white
pin 4 = Telematics can black
3,5,6,7 not connected
Trending Topics
The Best of Mercedes & AMG
When I asked retro-fitter in UK if this was possible they said flat out it could not ..."The unit simply wont work. the technology is different and during the installation process the system checks validity of part to chassis and NTG5 came much later. the coding will fail even if we could get it to talk to the car. Also we wouldn't be able to generate map pins as your chassis doesn't tally with an NTg5 car."
Given Chris has done the impossible ... He must be incredible talented at hacking the configuration! I have no Idea how he can update the Maps in the future given a map pin cannot be generated, is that perhaps one of the compromises Chris, you have to stay on the factory Maps or have you figured out some way to spoof the original VIN/codes from the car the retrofitted NTG 5.1 came from?
I'd love to know how Chris
When I asked retro-fitter in UK if this was possible they said flat out it could not ..."The unit simply wont work. the technology is different and during the installation process the system checks validity of part to chassis and NTG5 came much later. the coding will fail even if we could get it to talk to the car. Also we wouldn't be able to generate map pins as your chassis doesn't tally with an NTg5 car."
Given Chris has done the impossible ... He must be incredible talented at hacking the configuration! I have no Idea how he can update the Maps in the future given a map pin cannot be generated, is that perhaps one of the compromises Chris, you have to stay on the factory Maps or have you figured out some way to spoof the original VIN/codes from the car the retrofitted NTG 5.1 came from?
I'd love to know how Chris





Its a real pity your facing this hurdle on the speed signal, it seems unlikely the existing sensor is incompatible with NTG5.1 interface but have you managed to compare part numbers/spec from 2016 EClass to 2010 EClass to see if speed signal sensor is the same?
In relation to getting maps & unit to code correctly, do you need full Xentry/Star tools or is there anyway to code without that equipment through the inbuilt engineering menu or similar?









