HELP! 500X unresponsive after custom proxy

[JStrongy]

Hey everyone...

First post and this really is a desperate cry for help, as I've effectively left my wife of a 2 month old without a car...

We have a 2014 500X and I recently swapped out the 5* Uconnect for a 7" Uconnect, after I ran a Proxy Align and milage stopped flashing and all worked except for CarPlay.

I then swapped the AUX + USB module for AUX + 2 x USB module and ran a Proxy Align, again, all ok.

Finally, to get CarPlay running I extended the Proxy to 235 bytes and then made the below modifications:

Byte 148= 05 (Uconnect 7)
Byte 157= 01 (CarPlay)
Byte 160= 01 (Android Auto)

The Proxy Align went through fine and as per normal, I was promoted to turn the ignition off.

When turning the car back on, the car would not start. Everything is unresponsive (except for ironically the Uconnect) to the point where I can't even turn off the ignition or open / close the windows.

My next thought was to just restore the Proxy back to before I made the custom changes. I was able to connect to the body computer once and everything looked fine but since then, every attempt has been unsuccessful with the below response:

Code: Select all

Reading CAN configuration data ...
Failed to connect to Body Computer (BCM)

This is the ECS log from when I moved from the standard to custom proxy:

Code: Select all

Reading CAN configuration data ...
CAN CONFIGURATION DATA:
47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 01 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 01 00 00 00 00 02 00 00 00 00 00 00 00
47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00
33 38 33 33 34 30 31 30 36 30 31 4F 55 54 50 55 54 2D 53 49 54 20 15 06 09 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 D9 FA 0E 02 AC 82 07 E2 50 27 89 07 40 10 10 03 A3 28 54 92 01 35 73 14 01 4F 03 34 00 B3 A8 01 49 03 07 00 A2 00 0D FB 00 00 10 01 00 05 03 54 91 05 02 AD 00 52 00 01 8A 13 3D 40 00 05 03 C5 00 D1 24 10 00 00 49 02 81 12 79 42 80 00 00 8B AA 95 71 20 80 80 85 00
Body Computer Node (BCM/NBC)
Engine Control Node (ECM/NCM)
Radio Frequency Hub Node (RFHM)
Electric Steering Node (EPS/NGE)
Brake System Node (ABS/BSM/NFR)
Steering Lock Node (NBS)
Parking Sensor Node (PAM/NSP)
Airbag Node (NAB/ORC)
(Multiecuscan 5.2R1)
28/12/2024 11:55:02 AM
Fiat 500X 1.6 16V
CAN Setup / PROXI Alignment Procedure (334)
--------------------------------------------------------------

Body Computer Node (BCM/NBC): EOL Ok
Engine Control Node (ECM/NCM): EOL Ok
Radio Frequency Hub Node (RFHM): EOL Ok
Electric Steering Node (EPS/NGE): EOL Ok
Brake System Node (ABS/BSM/NFR): EOL Ok
Steering Lock Node (NBS): EOL Ok
Parking Sensor Node (PAM/NSP): EOL Ok
Airbag Node (NAB/ORC): EOL Ok

WARNING: This vehicle is properly configured. PROXI Alignment is not needed!
CUSTOM PROXI NEW DATA:
33 38 33 33 34 30 31 30 36 30 31 4F 55 54 50 55 54 2D 53 49 54 20 15 06 09 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 47 00 20 05 00 00 00 00 02 00 00 00 00 00 00 00 D9 FA 0E 02 AC 82 07 E2 50 27 89 07 40 10 10 03 A3 28 54 92 01 35 73 14 01 4F 03 34 00 B3 A8 01 49 03 07 00 A2 00 0D FB 00 00 10 01 00 05 03 54 91 05 02 AD 00 52 00 01 8A 13 3D 40 00 05 03 C5 00 D1 24 10 00 00 49 02 81 12 79 42 80 00 00 8B AA 95 71 20 80 80 85 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 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
EXECUTING ADJUSTMENT...
PROXI ALIGNMENT PROCEDURE
Writing CAN configuration data ...
Writing to module: Body Computer Node (BCM/NBC) SUCCESS!
Writing to module: Engine Control Node (ECM/NCM) SUCCESS!
Writing to module: Radio Frequency Hub Node (RFHM) SUCCESS!
Writing to module: Electric Steering Node (EPS/NGE) SUCCESS!
Writing to module: Brake System Node (ABS/BSM/NFR) SUCCESS!
Writing to module: Steering Lock Node (NBS) SUCCESS!
Writing to module: Parking Sensor Node (PAM/NSP) SUCCESS!
Writing to module: Airbag Node (NAB/ORC) SUCCESS!
COMPLETED

If anyone can help I would be extremely grateful, as I've stupidly put my family is a silly situation.

More than happy to donate for time.

I've disconnected the battery and leaving it for a couple of hours but if that fails, then effectively, I'm at the point where I'm going to need to arrange for it to be towed to the main dealer tomorrow and god knows what they will change.

Thank you in advanced.

[JStrongy]

No joy after leaving the battery off for 2 hours unfortunately - still not able to communicate with the BCM.

I was able to run a Diagnostics and below was the output:

Code: Select all

Body / RFHUB (Radio Frequency Hub Module)
Radio frequency hub (RFHUB) Continental
ISO Code: 34 86 07 0D 23
VIN code: XXXXXXXXXX
Hardware number: 91132300AA - Ver: 02
Software number: 40617925AA - Ver: 1120
Errors found:
B1040-64 - Communication with Body Computer (BCM/NBC) - Signal/message plausibility
B1033-64 - Communication with Body Computer (BCM/NBC) - Signal/message plausibility
U2056-87 - Error in communication with Body Computer Module (BCM) - Missing message
U2055-87 - Error in communication with Body Computer Module (BCM) - Missing message
U2054-87 - Error in communication with Body Computer Module (BCM) - Missing message
U2064-87 - Error in communication with Instrument Cluster (IPC/NQS) - Missing message
U2062-87 - Error in communication with Instrument Cluster (IPC/NQS) - Missing message
U2066-87 - Error in communication with engine control unit (ECU) - Missing message
B1041-16 - Power supply inside ECU - Voltage too low

NB: The VIN was correctly populated, I've just blanked out on this forum post.

None of that really means much to me though... There were no errors before I attempted the custom proxy though.

Could it as simple as a flat battery?!

I would have expected to still be able to communicate with the BCM, so doesn't seem likely.

Anyway, if anyone can assist / point me in the right direction, it would be greatly appreciated.

Thank you.

[rodspower]

Well,

First of all , try to switch back to the original proxy alignment, let`s sacrifice something!! Uconnect 7 , at this moment it`s not important.

Second.

Try to clear all DTC`s and see if you car battery is reached the lifespan, I have to change mine because of some BCM Errors.

Post the results here please.

[JStrongy]

Thank you for getting back to me.

I did try and restore the original Proxy but every attempt to communicate with the Body Computer failed, so I was unable to do so.

Thankfully, I have managed to resolve this and I'm putting it down to either:

1. Battery depleted of charge when I was programming
2. In the USB setting of the ELM adapter, I didn't have the "Latency Timer" set to 1ms

After the battery was changed and I correctly set the Latency Timer in the ELM's USB settings, I was able to communicate to the Body Computer again.

I cleared all error codes and restored the original Proxy.

Finally, performed the "soft reset" process after a battery disconnect (with the steering in the middle, turn engine on, wait for all errors to show, full steering lock left and hold, full steering lock right and hold, steering back to middle).

All errors then cleared and everything back to normal - panic over!


The goal of this was to get CarPlay working, so I then proceeded to flash across the custom proxy. This time only extended to 193 bytes (as opposed to extended to 235 based on advise from another forum post).

That all worked fine, CarPlay is working and no dramas!

The final proxy which I flashed across was:

Code: Select all

33 38 33 33 34 30 31 30 35 34 35 4F 55 54 50 55 54 2D 53 49 54 20 15 06 09 4F 04 20 05 10 00 00 00 02 00 00 00 00 00 00 00 4F 04 20 05 10 00 00 00 02 00 00 00 00 00 00 00 D9 FA 0E 02 AC 82 07 E2 50 27 89 07 40 10 10 03 A3 28 54 92 01 35 73 14 01 4F 03 34 00 B3 A8 01 49 03 07 00 A2 00 0D FB 00 00 10 01 00 05 03 54 91 05 02 AD 00 52 00 01 8A 12 3D 40 00 05 03 C5 00 D1 24 10 00 00 49 02 81 12 79 42 80 00 00 8B AA 95 71 20 80 80 85 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

[chrener]

It was caused just because of proxi extending... 500X has proxi lenght check... If you want to change proxi lenght you also have to change the lenght value

[JStrongy]

Ah understood.

I was scratching at straws what I had done wrong, so thanks for confirming!