Bytes for Fiat 500 Proxy Alingment

[AndreiMK5]

Hello,abarthmultije
i would need your help if possible, i got a 2017 fat abarth from japan with original radio missing (im guessing was Uconnect5 original)i bought an Uconnect7 from online ,everithing i need is working on it (bt.controls.lang,radio, and so on ) but i cant do proxy align , i did try all possible way that i found online ,without result ,alway finish with error .can you help me with a correct poxy align ? i will attach the las scan.
thank you!

[abarthmultijet]

Hello,abarthmultije
i would need your help if possible, i got a 2017 fat abarth from japan with original radio missing (im guessing was Uconnect5 original)i bought an Uconnect7 from online ,everithing i need is working on it (bt.controls.lang,radio, and so on ) but i cant do proxy align , i did try all possible way that i found online ,without result ,alway finish with error .can you help me with a correct poxy align ? i will attach the las scan.
thank you!

Have send you an private message

[xav50]

bonjours , je reviens vers vous n'ayant reçu aucune réponse a ma demande .

souhaitant pouvoir découvrir et déterminer l'ensemble des octets et leurs fonctions sur le proxi personnalisé de multiecuscan , et notamment trouver celui qui gère la détection des ampoules pour le supprimer suite a l'ajout d'ampoules Led .

je posède 3 fiat 500 :

Une lounge de 2015 sans toit ouvrant , sans clim auto , sans radar de recul , autoradio d'origine blue and me .
Une abarth de 2008 avec toit ouvrant et clim auto , sans radar de recul , autoradio d'origine blue and me .
Une abarth de 2021 avec toit ouvrant , clim auto , radar de recul , autoradio uconnect .

en faisant un travail de regroupement d'information et de comparaisons , j'ai pu touver :

que les octets 1 à 6 , 12 à17, 19 à22, 28, 31 à37 ,39 à 41, 45,47,52,54 à 61, 63, 67 à 70, 75 à 79, 82 à 84 , 86 à 108 , 112, 116, 119,120,122,124,126 à 128, 131 ...... sont tous identiques aux 3 véhicules.

L' octet , corresponds au pays du véhicule ,pour moi 33 (france).

les octets 20 à 25 , correspondent a la date de fabrication du véhicule.

l'octet 29 correspond a priori a la présence et activation du radar de recul .

Les octets 30 et 38 , correspondent a priori au type d'autoradio installé.

Les octets 48 et 49 correspondent au type de buton city et jauge turbo et shift up ( city=> 1C A0, SHIFT-UP => 17 20, TURBO => 1C C0 ).

l'octet 65 ,type affichage ( 10 =>500 2015, 40 => abarth 2008, 20 Abarth 2021).


je souhaiterais savoir ,comment ceux qui connaissent les codes pour carplay , uconnect ou android auto,ont pu trouver a quoi correspondez ces codes .

Et évidement , si quelqu'un possède l'ensemble des fonctions de l'ensemble des octets , je suis preneur
merci
xavier

TRANSLATION BY MODERATOR
-----------------------------------
Hello, I come back to you who have not received any reply to my request.

wishing to be able to discover and determine all the bytes and their functions on the personalized proxi of multiecuscan, and in particular to find the one who manages the detection of the bulbs in order to suppress it following the addition of LED bulbs.

I have 3 fiat 500:

A 2015 lounge without sunroof, no self-airing airframe, no reversing radar, ex-fing car radio.
A 2008 abarth with sunroof and car air conditioner, without reversing radar, car radio of blue and me origin.
A 2021 abarth with sunroof, car-airing airframe, car radio uconnect .

by doing a job of grouping information and comparisons, I could find:

that bytes 1 to 6 , 12 to 17, 19 to 22, 28, 31 to 37, 39 to 41, 45, 47.52.54 to 61, 63, 67 to 70, 75 to 79, 82 to 84 , 86 to 108 , 112, 116, 119,120,122,124,126 to 128, 131 ... are all identical to the 3 vehicles.

The byte , corresponds to the country of the vehicle, for me 33 (france).

the bytes 20 to 25 correspond to the date of manufacture of the vehicle.

the byte 29 corresponds a priori to the presence and activation of the reversing radar.

Bytes 30 and 38 correspond a priori to the type of car radio installed.

Bytes 48 and 49 correspond to the type of buton city and turbo and shift gauge (city 1C A0, SHIFT-UP 17 20, TURBO 1C C0 ).

byte 65, type display (10 plus 500, 2015, 40 plus abarth 2008, 20 Abarth 2021).


I'd like to know how those who know the codes for carplay, uconnect or android, could find what these codes correspond to.

And obviously, if someone has all the functions of the set of bytes, I'm taking
Thank you.
xavier

[ricarpa]

Hi, I have a 2013 Abarth 500 C, and I upgraded the MP3 radio with Blue and Me to a Uconnect 7 with TFT and a 2017 steering wheel. The odometer isn't flashing, but I can't get the steering wheel controls to work. My proxy settings are:

33 32 31 35 30 30 30 34 32 31 39 4F 55 54 50 55 54 2D 4A 49 54 20 10 04 21 4F 8C 00 05 10 00 00 00 09 00 00 04 10 00 00 00 A0 45 75 06 FE 20 17 90 0A 30 00 06 00 01 00 95 06 01 01 00 00 00 00 60 7A 41 0A 00 0C 00 00 2E 23 00 00 00 00 32 22 58 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 44 00 D5 00 00 00 00 00 00 05 00 70 00 00 00 00 00 00 00 00 70 00 00 00 00 00 00 05 00 00 00 00 00 00 00 00 01 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


Scanning ...

CHASIS (Body) / BCM (Body Control Module)
Body Computer Delphi (500c)
Código ISO: 00 00 60 15 14
Código V.I.N.: ZFA31200000712723
Número de HW: 0312N6E4102 - Ver: 01
Número de SW: 28718290 - Ver: 1809


AIRBAG / NAB/ORC (Airbag/Occupant Restraint Module)
Continental Airbag (Ep - PROXI)
Código ISO: EA 07 AE 89 FD
Número de HW: A2C30467500 - Ver: 07
Número de SW: 40468266100 - Ver: 0000

CUADRO DE MANDOS / IPC (Instrument Panel Cluster)
Instrument Panel Marelli TFT
Código ISO: 00 03 40 25 14
Número de HW: 50019650001 - Ver: 00
Número de SW: 04005440545 - Ver: 0423

CUADRO DE MANDOS / ETM (Entertainment Telematic Module)
Uconnect Radio/Nav 7"
Código ISO: 00 24 70 55 15
Código V.I.N.: ZFACF1BJ1PJJ11532
Número de HW: F.EU.D8.V28 - Ver: 28
Número de SW: 23.03.67.12 - Ver: 2303
Errors found:
B1577-13 - Universal Consumer Interface (UCI) - Open circuit
B157A-13 - DAB aerial - Open circuit

CONTROL DEL CLIMA / HVAC (Heating Ventilation Air Conditioning)
Denso climate control (Single zone/PTC)
Código ISO: 34 83 A2 8A 38
Código V.I.N.: ZFA3120000JE94997
Número de HW: MX237110360 - Ver: 02
Número de SW: PFT003_1012 - Ver: 0A0C

OTROS / PAM/NSP (Parking Sensors Module)
Parking control Valeo (3 channel)
Código ISO: 3E 83 15 0B B6
Número de HW: 303409 - Ver: 01
Número de SW: 310273 - Ver: 0405


LUCES
Litronic XENON headlamp (left)
Código ISO: C1 07 08 04 29
Número de HW: 1307329293 - Ver: 01
Número de SW: 1037373937 - Ver: 0001

LUCES
Litronic XENON headlamp (right)
Código ISO: C1 07 89 04 2A
Número de HW: 1307329293 - Ver: 01
Número de SW: 1037373937 - Ver: 0001

COMPLETADO
I enlarged it from 193 to 250 bytes, but it didn't work. I must say that the 2017 steering wheel buttons with the MP3 player do work. I'd appreciate any help.


Thank you

[Apache]

Hey guys, I’m coming to you for some advice.
I’m planning to swap out the Uconnect 7" in my 2017 500C for a newer version that supports DAB and CarPlay.
I already know I’ll need to do a Proxy Alignment, but I wanted to ask—do I need Multiecuscan just to read the code bytes from the current configuration (not to write anything new), or is there another tool I can use for that?

[ricarpa]

Multiecuscan y AlfaObd son las dos mejores opciones

[abarthmultijet]

Hey guys, I’m coming to you for some advice.
I’m planning to swap out the Uconnect 7" in my 2017 500C for a newer version that supports DAB and CarPlay.
I already know I’ll need to do a Proxy Alignment, but I wanted to ask—do I need Multiecuscan just to read the code bytes from the current configuration (not to write anything new), or is there another tool I can use for that?

You can use Multiecuscan or AlfaOBD, my choise will always be Multiecuscan, works way better in my opinion.

Have a bit of a love/hate relation with AlfaOBD, sometimes it will fix things that Multiecuscan can't fix but why and how is always the question.

Multiecuscan multiplexed with an CanTieCar interface works the best (no color adapters needed)