Before MoPower can confirm a PCM or ECU programming service, we need to identify the vehicle, controller, requested outcome, and current problem accurately. At minimum, prepare the year, make, model, engine, PCM label photographs, and a clear description of the service you believe you need. Replacement, immobilizer, swap, MDS, and handheld-tuning requests each require additional details.
Key Takeaways
- Complete vehicle and PCM identification comes before programming.
- Describe the symptom and desired result separately.
- Send clear photos of both original and replacement controllers.
- List mechanical modifications precisely; “built engine” is not enough.
- Do not ship keys, modules, or handheld devices unless the selected service requires them.
Start With the Exact Vehicle
Provide the model year, make, model, engine displacement and family, transmission, and drive configuration. Include the VIN when the service requests it. Production date, emissions package, trim, or installed equipment can also matter on applications that changed hardware or software during a model year.
Do not shorten the description to a broad family such as “HEMI truck” or “Ford V8.” The same engine name may span several controllers, security systems, transmissions, and calibration strategies.
Document the PCM or ECU
Send a straight-on, readable photograph of the entire module label. Include all service, hardware, engineering, supplier, and calibration numbers rather than typing only the largest number. Photograph the connector faces and any physical damage. If there is an original and a replacement, label the photos clearly.
Use How to Identify the Correct PCM Part Number when a label contains several possible identifiers. Do not open, clean aggressively, or alter the controller before MoPower reviews the service requirements.
Explain What You Want the Controller to Do
A symptom and a requested service are not the same thing. “Vehicle will not start” describes a symptom. “Program a compatible donor PCM for this VIN and supported security setup” describes a possible service. Explain both, and avoid choosing a programming operation solely from a trouble code or forum suggestion.
Useful requests include replacement-controller preparation, VIN programming, supported immobilizer work, an engine-swap calibration, supported MDS changes, or a compatible handheld-tuning path. If you are not sure which applies, say so. Accurate uncertainty is more useful than an incorrect service label.
For a Replacement PCM
Provide the original and donor part numbers, source of the donor, and whether either module communicates. State whether the donor is used, remanufactured, or new. Include the current VIN when requested, the donor vehicle information if known, and the symptoms before and after replacement.
Note whether the engine cranks, starts and stalls, or does not crank. Record the security indicator behavior and all diagnostic trouble codes. Review used PCM matching before buying a donor and replacement PCM no-start causes if installation has already been attempted.
For VIN Flashing
Provide the recipient vehicle VIN and controller labels, but remember that identity is only one layer. Explain whether calibration, configuration, or immobilizer work is also expected. “VIN programmed” should not be used as shorthand for a completely configured plug-and-play module.
The article VIN Flashing Explained outlines the distinctions. MoPower will confirm what the supported service includes for the application.
For SKIM, Immobilizer, or Ford PATS Work
Security-related requests must be for legitimate owner-authorized repair, replacement, or supported swap use. Provide the vehicle and controller identity, whether the original PCM is available, how many valid keys are present, and what security components remain installed. Include security-related codes and observed indicator behavior without attempting bypass procedures.
For Chrysler-family vehicles, identify whether the platform uses SKIM, SKREEM, WIN, or another architecture if known. For Ford, MoPower's public PATS support stops at model year 2014 and is application-specific; this is not universal coverage for all Fords through 2014. Use the Ford PATS programming guide, Ford service area, and Vehicle Finder for exact support.
For MDS Services
Confirm that the engine was actually equipped with Multi-Displacement System. Provide the vehicle, engine, controller number, transmission, and whether the MDS hardware remains stock. If a mechanical delete is planned or completed, include the exact camshaft, lifters, valvetrain configuration, and other engine changes.
MoPower MDS coverage applies only to supported MDS-equipped applications through model year 2025, not every HEMI. Programming does not repair lifters, camshafts, oiling problems, wiring, compression, or other mechanical damage. Read tuning after an MDS delete kit for the full planning checklist.
For an Engine Swap
Identify both sides of the project: the donor engine, transmission, harness, controller, throttle system, and security components, plus the recipient chassis and intended use. State which donor modules and keys are available. List changes to displacement, camshaft, injectors, induction, transmission, gearing, and emissions-related equipment.
MoPower supports specific engine-swap ECU/PCM calibration applications. A donor engine does not automatically make its PCM the best choice, and an original chassis PCM may not be capable of controlling the new powertrain.
For Handheld Tuning
Identify the device brand and exact model, whether it is new or already married to a vehicle, and which vehicle it is currently associated with. Provide PCM software or strategy information when available. Describe the modification list and the intended tuning goal.
Do not assume every device supports every controller. In the Ram 1500 3.6L Livernois/MyCal supported family, eTorque applications are excluded. Review the ECU programmers service area and verify the exact equipment.
Include Diagnostic Evidence
Useful evidence includes a complete scan report, exact diagnostic trouble codes, freeze-frame data, module-communication results, and measurements already performed. Summarize relevant power, ground, fuse, wiring, battery, charging-system, and network checks. Explain whether the vehicle ran before the PCM was changed.
Do not clear codes repeatedly before recording them. Avoid sending only a dashboard photo or a parts-store code definition. The code number, module that set it, status, and surrounding symptoms matter.
Tell Us About Physical Condition
Disclose water intrusion, corrosion, collision damage, burnt odor, broken connectors, bent pins, prior opening, or previous repair attempts. Programming cannot correct physical damage, and unstable hardware may not be a safe candidate for repeated writing.
If the original PCM failed after reversed polarity, jump-start damage, alternator overvoltage, or a shorted circuit, the vehicle should be repaired before a replacement is installed.
Compatibility Boundaries
All support is application-specific. The 2024–2025 electric Dodge Charger is not supported by MoPower services. Broad Chrysler, Dodge, Jeep, Ram, or Ford pages are starting points, not universal fitment claims. Use the Vehicle Finder for the exact application.
Before You Ship
- Confirm the service and every item that must be included.
- Place the order and retain its identifying number.
- Protect connectors and immobilize the module in sturdy packaging.
- Include the required order identification, not loose unlabeled parts.
- Use the current shipping instructions supplied with the order.
Do not rely on an address copied from an old email, forum, or search result. The mail-in PCM and ECU process guide explains the complete workflow without inventing turnaround promises.
Frequently Asked Questions
Do I always need to provide the VIN?
No, but many replacement and identity-related services require it. Follow the requirements for the exact service.
Can MoPower identify my PCM from the vehicle year and engine?
Sometimes that narrows the family, but the physical controller label is still important because variants and prior replacements exist.
Should I send my keys with the PCM?
Only when the confirmed service specifically requires them. Do not place keys or extra modules in the shipment by assumption.
Can a trouble code prove that I need a new PCM?
Usually not by itself. Wiring, power, ground, sensors, actuators, and network faults can produce controller-related codes.
What if I do not know which service I need?
Provide the vehicle details, controller labels, symptoms, codes, and intended outcome. MoPower can then identify the relevant supported service path.
Does MoPower support the 2024–2025 electric Dodge Charger?
No. Those vehicles are outside MoPower's supported service scope.
Send the Facts Before the Module
Complete information is the quickest route to the right service. Start with the MoPower Vehicle Finder. When the controller, modification, or symptom does not fit neatly, use the contact page to send clear photos and the checklist above before shipping.