Hi, i decided to tune my 500X with Navigation by changing the Uconnect module.
Originally I have Uconnect VP2 5" with RVC but without NAV and DAB options.
I bought on ebay used Uconnect VP2 NAV RVC DAB ( specification photo attached ). As my car is 2015 and already warranty is invalid decided to do the change DIY.
After the change and all connections and the camera enable by MES software the Uconnect doesn't work with RVC. Navigation works perfect but RVC no reaction.
Anyone tried to do it ? Someone have any idea how to fix it ?

Thanks a lot !

Have you got the camera connected to the correct pins?

Pin 31 = Rear Camera Signal +
Pin 32 = Rear Camera Signal -
Pin 33 = Rear Camera Shield

Thanks, will check connections again but i just change the Uconnect unit from that one when RVC was working correct, all cables connected the same way to the new one... ? Is it possible that the connection was different with camera on the other Uconnect unit - the same model VP2 334 but without NAV ?

Jarek0808 said:

Thanks, will check connections again but i just change the Uconnect unit from that one when RVC was working correct, all cables connected the same way to the new one... ? Is it possible that the connection was different with camera on the other Uconnect unit - the same model VP2 334 but without NAV ?

Click to expand...

OK I've just checked again and the connection on VP2 and VP2+NAV are the same so this is not a cable/connection issue but a Proxi issue.

Although MES may have done the PROXI aligment correctly as in recognising the VP2 unit I suspect there is also a proxi byte value(s) that have to be changed to enable the camera function.

Suggest you search the MES forum to see if this has been covered before.

s130 said:

OK I've just checked again and the connection on VP2 and VP2+NAV are the same so this is not a cable/connection issue but a Proxi issue.

Although MES may have done the PROXI aligment correctly as in recognising the VP2 unit I suspect there is also a proxi byte value(s) that have to be changed to enable the camera function.

Suggest you search the MES forum to see if this has been covered before.

Click to expand...

Yes, after checking at MES forum there is probably an issue with byte values. But no solution found till now. Will search and let you know results if i will find the right answer. Thx.

Jarek0808 said:

Yes, after checking at MES forum there is probably an issue with byte values. But no solution found till now. Will search and let you know results if i will find the right answer. Thx.

Click to expand...

Well if you still have your old unit you could reconnect that and download the Proxi byte data and then compare this to the new unit's data.

There will no doubt be several byte difference so the tricky / dangerous bit is identifying which are the relevant bytes.

While you are there make sure you BACKUP all the original byte data so you can always put everything back as it was.

Also on the MES forum there have been a number of posts over the years that have identified some of the byte positions/functions (e.g vehicle image on instrument panel cluster) so these will help eliminate some of the possible differences.

Also have to STRESS/WARN that playing with custom proxi data can be a dangerous game so one has to be absolutely certain you have identified the right ones. Randomly poking around is bound to cause grief.

I know that this is an old thread but is it possible to connect a RVC to PIN 31, 32 and 33 to the Uconnect 5? I found that for the Alfa Romeo Giulietta with Uconnect 6.5 and want to do it for my Alfa Romeo Mito with Uconnect 5 now.