PROXI Questions - Encoding, NBC PROXI Push, etc?

Currently reading:
PROXI Questions - Encoding, NBC PROXI Push, etc?

tanders2112

New member
Joined
Dec 18, 2017
Messages
1
Points
1
Hello All -

I am a new user, and I hope I am in the correct forum for this type of inquiry.
I have seen a lot of chat on the web about PROXI Alignment, etc. but I have never seen a description of how the data structure for the PROXI file is actually encoded in terms of bits and bytes. Is this published anywhere?

Also, I was under the impression that the configuration check that the NBC does at start up includes receiving a PROXI configuration code from the configurable ECUs in the system such as NIT, and checking that code against the configuration code the NBC has. If they don't match, I thought the NBC could update the faulty controller on its own without a test tool being involved. Is this done on any of the vehicles in the Fiat Group?

Thanks in advance for any help,

Tony
 
The data/structure will be documented in Fiat official data that is released (sold) to diagnostic equipment manufacturers documented. Like you I've seen little other information on the web.

Here is a typical Proxi configuration report:

Reading CAN configuration data ...
CAN CONFIGURATION DATA:
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 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
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 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 4F 04 20 05 10 00 00 00 02 00 00 00 00 00 00 00
33 38 33 33 34 30 30 31 35 38 32 4F 55 54 50 55 54 2D 53 49 54 20 15 06 11 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 01 AC 81 07 E2 20 27 89 07 40 10 10 03 A3 1E 24 92 01 35 73 14 01 4F 03 34 00 B3 A8 01 46 03 07 00 8E 00 11 56 00 00 10 01 00 05 03 54 91 05 02 A5 00 52 00 01 8A 12 3D 40 00 05 03 C5 00 D1 24 10 00 00 49 01 81 12 79 42 80 00 00 13 AA 97 71 20 80 80 85 00
Body Computer Node (NBC)
Engine Control Node (NCM)
Electric Steering Node (NGE)
Dashboard Node (NQS)
Brake System Node (NFR)
Climate Control Node (NCL)
Steering Lock Node (NBS)
Parking Sensor Node (NSP)
Airbag Node (NAB)
Entertainment Telematic Node (ETM)
Radio Frequency Hub Node (RFHM)
23/12/2016 11:59:34 (Multiecuscan 3.4)
CONNECTED TO:
Fiat 500X 1.4 16V MultiAir
CAN Setup / PROXI Alignment Procedure (334)
--------------------------------------------------------------

Body Computer Node (NBC): EOL Ok
Engine Control Node (NCM): EOL Ok
Electric Steering Node (NGE): EOL Ok
Dashboard Node (NQS): EOL Ok
Brake System Node (NFR): EOL Ok
Climate Control Node (NCL): EOL Ok
Steering Lock Node (NBS): EOL Ok
Parking Sensor Node (NSP): EOL Ok
Airbag Node (NAB): EOL Ok
Entertainment Telematic Node (ETM): EOL Ok
Radio Frequency Hub Node (RFHM): EOL Ok


In the MultiECUScan forums then there have been discussions about specific byte offsets and values for some items like dashboard display configurations.

Would also add/warn that playing with proxy data value can trash/cause serious problems with your vehicle operation.
 
Back
Top