A flashing odometer and a list of new fault codes after replacing a module on a Chrysler, Dodge, Jeep or Ram usually means one thing: PROXI is out of alignment. As of October 2026, a remote wiTECH 2 session that runs the alignment costs $250, with about 24 hours of first-time setup before the first booking. The module you fitted is probably fine. It has not been told what vehicle it is in.
We wrote this post because shops search for the procedure by name and most remote providers list only the category. Our flash page names PROXI configuration alignment, RF hub programming and Restore Vehicle Configuration as session work; this is the explanation behind those three lines.
What PROXI is
A modern vehicle is a network of modules that have to agree about what the vehicle is. Which engine. Which transmission. Whether it has heated seats, a tow package, a particular audio system, rear park assist. Each module behaves differently depending on the answers, and each needs the same answers as its neighbours.
On the Chrysler, Dodge, Jeep and Ram models built on the newer shared corporate electrical architecture, that description is held as a single configuration record. The body computer holds the master copy. PROXI is the name of that record, and PROXI configuration alignment is the procedure that takes the master copy and writes it to every module on the network so that all of them hold the same one.
At the factory this happens once, at the end of the line. In service it has to happen again whenever the set of modules changes — because a new module arrives with no record, or with the record of the vehicle it came from.
How misalignment shows up
| Symptom | What it usually means | Fixed by alignment? |
|---|---|---|
| Odometer display flashing | At least one module's configuration does not match the master | Yes |
| New fault codes about configuration or implausible data in several modules | Modules disagree about the vehicle's equipment | Yes |
| A feature that worked before the repair no longer works | The replaced module does not know the feature is fitted | Usually |
| Communication faults with a module that is physically present | Could be configuration, could be wiring or power | Sometimes — test the wiring first |
| Module does not answer a scan tool at all | Power, ground, network or a dead module | No — not a configuration fault |
The flashing odometer is the one to remember. It is the vehicle's own way of saying that the configuration is inconsistent, and it is frequently misread as a cluster fault. Shops have replaced clusters over it. The cluster is reporting the problem, not causing it.
The last two rows are the ones that matter for not wasting a session. A configuration procedure talks to modules over the network. If a module is not answering at all, there is nothing for alignment to write to, and the fault is upstream of anything a programming session can reach. Our no-communication triage post covers the checks that separate a silent module from a misconfigured one, and the DTC index sorts network codes from internal ones.
When you need it
After replacing the body computer. This is the largest case, because the body computer is where the master record lives. A new one has to be given the vehicle's configuration before it can pass it on, and that is a programming step in its own right before alignment begins.
After replacing almost any other networked module. A new radio, cluster, door module, steering-column module or driver-assistance unit arrives without the vehicle's record. Alignment gives it one.
After adding or removing equipment the vehicle has to know about. A retrofit that the configuration does not describe will not be recognised by the modules that have to work with it.
After a repair that involved swapping modules to test. A module borrowed from another vehicle to prove a diagnosis can leave its configuration behind, or pick one up.
It is not needed after replacing a sensor, an actuator or a component that is not a network module. Those may need a relearn, which is a different procedure; our relearn index lists which is which.
The vehicles that do not use PROXI
Not every model in these four brands uses this scheme. Platforms on the older corporate architecture store the vehicle's configuration differently, and the equivalent procedure in wiTECH is called Restore Vehicle Configuration: the application retrieves the configuration recorded for that VIN and writes it to the module that needs it.
The practical consequence is that you do not need to know which scheme your vehicle uses before booking. The application knows from the VIN, and both procedures are on our session list. What you do need to tell us is which module was replaced and what the car is doing now.
What happens in the session
You plug a J2534 pass-thru device into the vehicle and a Windows laptop. IgniteRemote presents the device on our workstation as though it were local, and we run wiTECH 2 against your vehicle with a video call open alongside. Our step-by-step session post follows the whole sequence.
For an alignment after a module replacement, the order of work is roughly this:
- Scan every module and save the result, so there is a record of the faults that existed before anything is written.
- Program the new module if it needs software — a replacement that arrives blank or on old software is brought to the right level first.
- Run the alignment, which writes the configuration to the modules on the network.
- Clear faults and rescan. Configuration faults should clear and stay cleared. Anything that returns is a real fault that the configuration problem was hiding.
- Run whatever the specific module needs afterwards — a key or RF hub procedure, a calibration, a relearn.
Step four is where a session earns its fee beyond the procedure itself. A car that arrived with fifteen codes and leaves with two has had thirteen configuration faults removed and two genuine ones exposed.
“The odometer stops blinking and people think that was the job. The job was the scan afterwards, when the car finally tells you what is really wrong with it.” — Remote programming desk, ECU Flash Cartel
The security gateway
Later vehicles in these brands carry a security gateway module between the diagnostic connector and the rest of the network. It permits reading freely and restricts writing to authenticated tools. Alignment is a write.
In a session that is not an obstacle you have to solve: authorised gateway access is part of what the manufacturer's application provides, and it is listed among the Mopar session capabilities on our flash page. It is worth understanding anyway, because it is the reason a scan tool that performed this procedure on an older vehicle may refuse on a newer one. Our security gateway post explains the mechanism and the legitimate routes through it.
The 24-hour rule
Mopar is the only platform on our session list that carries a first-time setup notice. Initial J2534 registration takes about 24 hours, so a first booking cannot be a same-day rescue. After that first session, subsequent ones are booked like any other platform: 9 AM to 9 PM Central, seven days a week, earliest slot thirty minutes out.
For a shop, the practical move is to do the registration before the first car needs it. A vehicle sitting on a lift with a blinking odometer and a customer waiting is the wrong moment to learn about a 24-hour lead time.
What alignment will not fix
A used module that is paired to another vehicle. Alignment writes configuration. It does not rewrite a module's identity, and it does not undo the security pairing on parts that are locked to the vehicle they were first fitted to. Our used ECU matching guide covers what has to match before a used part is worth buying, and the VIN mismatch post covers which modules object to a foreign VIN.
A module with the wrong hardware. Configuration cannot turn one part number into another. A module that is physically the wrong variant for the vehicle will not be made right by software.
Wiring and power faults. A connector that is not fully seated, a ground that was disturbed during the repair, a blown fuse feeding the new module. These produce communication faults that look like configuration faults on a code list and are not.
An engine that will not start because the engine computer was replaced. That is a programming and immobiliser job, and it is a different procedure in the same application. Our wiTECH session versus GPEC unlock post separates the two things people most often confuse on this platform, and a swapped ECU that won't start has its own list of causes.
Preparing for the session
Most failed sessions fail on preparation. For this job in particular:
- Fit the module and confirm it has power before the appointment. Alignment cannot write to a part that is still in its box.
- Put the vehicle on a battery maintainer. The procedure writes to many modules with the ignition on and the engine off. Our battery support guide explains what stable voltage means and why a jump pack is not it.
- Check your device against the compatibility matrix. Universal pass-thru devices are marked compatible with the Mopar stack. Devices built for one other manufacturer are not.
- Have both part numbers and the VIN ready, with photographs of the labels.
- Say what was done before the fault appeared. “Replaced the radio with a used one and the odometer started flashing” saves ten minutes of discovery.
Our session failures post lists the six causes that account for most of the rest.
A worked example
A shop replaces a failed body computer on a compact Jeep with a new part. The car starts, but the odometer flashes, the remote functions are dead, and a scan shows configuration faults in nine modules.
In the session the new body computer is programmed and given the vehicle's configuration, the alignment is run, and the RF hub procedure restores the remote functions. The rescan shows one remaining fault, in a door module, that has nothing to do with configuration: a wiring fault that was there before the repair and had been buried in the noise.
The shop had quoted the customer for a body computer. Without the rescan, the door fault would have come back as a complaint a week later and been blamed on the new part.
Why the rescan is not optional
Configuration faults are noisy. One misaligned module can cause half a dozen others to log complaints about it, and a vehicle in that state will show a code list that looks catastrophic. It is tempting to clear everything once the odometer stops flashing and hand the car back.
Do the full scan instead, and compare it with the one taken before the work. Every code that has gone was a consequence of the configuration. Every code that remains is something else, and it was there all along.
Standards and the legal position
Independent access to these procedures rests on SAE J2534, the pass-thru standard that lets one interface carry a manufacturer's application, and on the framework for security-related access administered in North America by NASTF. Fault codes themselves follow the structure defined in SAE J2012, which is why a network code reads the same way across makes.
We do not provide emissions defeat, delete files, or services intended to bypass emissions laws. Our services exist for tuning preparation, diagnostics, repair, motorsport, and off-road use where legally permitted. Customer is responsible for confirming legal use in their location and application.
A configuration alignment writes the vehicle's own factory configuration and nothing else. The federal Clean Air Act governs what may be written into an emissions-relevant controller, whichever tool does the writing.
The short version
PROXI is the vehicle's configuration record on many Chrysler, Dodge, Jeep and Ram models, and alignment writes it to every module so they agree. A flashing odometer after a module swap is the usual sign it was skipped. It is a $250 wiTECH 2 session with about 24 hours of first-time setup, the security gateway is handled inside the session, and the rescan afterwards is where the real faults show. It will not fix a paired used module, wrong hardware or wiring. Fit the part, put the car on a maintainer, and book the session.