Feature
Automatic body & platform detection
Connect the vehicle and FCA PROXI Tool figures out the body and platform from the car's own configuration — then loads the correct parameter maps and the real module list. No picking a platform from a dropdown, no generic template that half-fits.
Connect — it knows the car
Instead of asking you to choose a model and trim and hope it matches, the tool reads the vehicle's own configuration on connect and identifies the body and platform itself. The right context is set before you touch a single parameter.
Why the body / platform matters
Parameter maps, byte layouts and module lists differ by body and platform. Detecting the correct one means Fast Parameters show the right value lists, edits land on the correct bytes and bits, and you are not fighting a map that belongs to a different car. See Fast Parameters.
The real module list, not a generic template
Because detection is based on the car's actual configuration, the module list reflects what is really on the vehicle. On Vehicle shows only the modules that are present; All ECUs shows everything the body can have — useful for retrofit planning and for confirming a module exists before you write. More in diagnostics.
Fewer mistakes, faster work
- No manual platform selection — one less place to get it wrong.
- Correct parameter maps loaded automatically for the detected body.
- Scans only the modules that are actually present — faster and accurate.
- Edits stay on-target because the byte map matches the real car.
Detect first, then edit — the configuration you write matches the car you are connected to.
How it fits the workflow
Connect over ELM327 / J2534, let the tool detect the body and platform, then read the configuration, edit the named parameters you need and write CRC-correct output. Detection sets the stage so every later step targets the right car. See the PROXI alignment workflow.
FAQ
What is automatic body detection?
On connect, the tool reads the vehicle's own configuration and identifies the body and platform automatically, so it can load the correct parameter maps and the real list of modules without you picking a platform by hand.
Why does the body / platform matter?
Parameter maps and module layouts differ by body and platform. Detecting the right one means edits target the correct bytes and bits, and the module list reflects what is actually on the car — not a generic template.
Does it scan modules that are not present?
The On Vehicle view shows only modules that are actually present per the vehicle's configuration; All ECUs shows everything the body can have. That keeps scans fast and accurate and helps with retrofit planning.
What if a platform is new or unusual?
Detection is based on the vehicle's own configuration data. Supported platforms load their parameter maps automatically; for edge cases you can still work with exported buffers and the Advanced views.