Various Vehicles - Module Reprogramming (G0000150)

MODULE REPROGRAMMING (MR)

MR updates the module software to the latest level if it's not already there. This style of programming should only be performed when an SSM, TSB, FSA, or Pinpoint Test directs you to perform it. Reprogramming will not impact or correct a customer concern unless a message specifically states the software update was released to correct that condition.

PROGRAMMABLE PARAMETERS

Programmable Parameters are used to change how the vehicles modules think the vehicle is equipped. For example: You can turn on and off daytime running lights (DRLs) on certain vehicles. Certain parameters can only be used to disable a feature that the vehicle was equipped with and at the same time, cannot enable the feature on a vehicle never equipped with the feature. A full list of supported parameters that can be modified are listed in PTS WSM, Section 418-01 > Description and Operation. The Ford and Lincoln Technical Assistance Center cannot support programming features on/off outside of those listed in this section. Additionally, the only electronic devices that are supported to be added/removed are those sold through Ford Motor Company at accessories.ford.com or accessories.lincoln.com.

As-Built

As-built configuration data is data that tells a module how the vehicle is equipped. Examples include two doors vs. four doors, Sirius radio vs. less Sirius radio. This data is an exact copy of how the vehicle was built. As-built configuration data is automatically programmed into replacement modules when the PMI process is performed. As-built data programming should not be used as a substitute for a PMI procedure when a new module is installed. If the as-built configuration data is requested by the scan tool and is not available on the PTS service information site, refer Module Programming Routine #6 - Requesting Missing As-built Configuration Data.

NETWORK COMMUNICATION CONCERNS, INVALID DATA AND LOSS OF COMMUNICATION DTCS (U-CODES)

During any type of module programming, the IDS scan tool will be communicating with the module being programmed over one of the vehicles communication networks. On most vehicles 2005 and newer, these networks are controller area networks (CAN) as opposed to standard corporate protocol (SCP) or international standard organization (ISO) networks. In order to successfully program a module, it must be able to communicate properly with the scan tool. All replacement modules must also be capable of communicating with the scan tool for them to be successfully programmed. Network communication faults affecting either a single module or entire network should be addressed before diagnosing a programming error. Tools provided in the IDS scan tool such as the Network Test or Self-Test can be used to determine if a single module or entire network are failing to communicate with the IDS scan tool. Additional information on network diagnostics can be found in PTS workshop manual section 418-00 and in TSBs, GSBs or SSMs.

If all modules are communicating with the IDS scan tool via the Network Test and Self-Test functions but, U-codes for loss of communication and invalid data are present, this can be caused by a fault with an input to a module on the vehicle. This will usually set a more specific DTC in the module that's receiving the faulted input such as a powertrain (P-code), body (B-code) or chassis (C-code). Follow all published WSM or Powertrain Control/Emissions Diagnosis (PC/ED) diagnostics for the DTCs stored, but specific DTCs usually require diagnostics before U-codes as the U-codes can be a result of the more specific P, B or C code.

In certain situations, however, these DTCs may be the result of another module in the vehicle system that is not configured correctly. It is important to understand first that modules will not lose their programming. If a module is replaced in a prior repair attempt and was not correctly programmed upon replacement, that repair attempt may induce these type of DTCs. Review warranty history on PTS OASIS and consult with the customer to inquire about any relevant repairs prior to this concern that may indicate a module has been incorrectly programmed (refer to Module Programming Symptom Chart Routines, new vehicle or module symptoms after a module was replaced and programmed).

DETECTING UNAUTHORIZED/NON-FACTORY POWERTRAIN CONTROL MODULE (PCM) CALIBRATIONS AND REMOVING THEM

Unauthorized/non-factory PCM calibrations may not be detectable using standard tools or diagnostic equipment. Customer acknowledgment is the only conclusive method to verify an unauthorized PCM calibration has been utilized. Two methods often misused to verify the presence of an unauthorized PCM calibration are:

• The PCM Filename of the software file in the PCM.
  • Due to the design of unauthorized calibration equipment (aftermarket tuners) and the inherent possibility that this equipment will utilize a factory PCM filename, the PCM filename cannot be used to verify the presence of an unauthorized calibration. For example, the aftermarket calibration may have the same filename as a valid Ford Motor Company calibration.
• The Ignition Counter (IGN_CTR) located in Mode 9
  • This data displays the number of ignition key cycles since the most recent PCM calibration update. The PCM calibration may be updated at a dealership or a 3rd party facility with an IDS or other scan tool causing the ignition counter to reset. The accuracy of this value cannot be determined as this value resets with any calibration update.

To confirm an accurate repair and prevent repeat failures, follow any applicable publications in OASIS. If no applicable service publications are available, refer to the following:

• Determine extent of damage and complete the repair per the Warranty and Policy Manual and published WSM procedures.
• After the repair is completed, install the factory calibration in the PCM (refer to Module Programming Routine #2 - Programming the PCM to the correct calibration which is outlined further down in this article).
• After the PCM calibration is restored, refer the customer to the Warranty and Policy Manual regarding the vehicle warranty and risks of unauthorized calibrations.

IDS SCAN TOOL VEHICLE IDENTIFICATION PROCESS

When starting a new, automatic session with the vehicle, the IDS scan tool will read the PCM software part number. The IDS scan tool, using an internal look up table, will determine what the year, make, and model of the vehicle is. If the vehicle is identified incorrectly by year, make or model, this is the result of the PCM having been previously programmed incorrectly with Ford service scan tools or aftermarket tuners. If the vehicle is identified incorrectly, this may result in missing scan tool routines or failed programming for any equipped module. To correctly program the PCM, allowing IDS to identify the vehicle correctly, refer to Module Programming Routine #2 - Programming The PCM To The Correct Calibration.

The vehicle identification page also displays the vehicle identification number (VIN). The VIN is read from the PCM. The PCM may receive the VIN during the PMI process automatically. On vehicles equipped with a body control module (BCM), it is also possible that the VIN is sent to the PCM by the BCM via the CAN. Once both modules are correctly programmed via PMI and/or as-built programming, the PCM may still retain the old VIN. If available in IDS for the particular year, make and model, run the PCM keep alive memory (KAM) reset and Relearn Vehicle Data routines. These will force the PCM to accept and store the next VIN sent to it via the CAN network by the BCM.

MODULE PROGRAMMING PRE-CHECKS

Before beginning programming, it's recommended to confirm the following to ensure successful module programming.

• There is a battery charger installed on the vehicle and that it is maintaining 12.6 to 13.6 volts. In some cases, it may be necessary to verify the performance of the battery charger or maintainer. In these cases, it is recommended to monitor the battery voltage using a stand alone digital volt ohm meter (DVOM).
• The negative cable of the charger should be installed on chassis ground, not the negative post of the battery to prevent battery saver mode (BMS) from activating.
• There should be no aftermarket components installed that might interfere with module programming. These include: remote start kits, global positioning system (GPS) devices, radios, insurance trackers and trailer brake control modules.
• The module being programmed should be passing a network test. All modules, including those unprogrammed should be capable of passing a network test.
• The IDS scan tool should be at the latest version. The scan tool updates can be installed from PTS > Rotunda Tab > Diagnostic Tool Support > Download Software.
• Verify that the vehicle is identified correctly in the IDS scan tool, vehicle specification screen. Confirm that the year, make, model and emissions calibration are correct.

MODULE PROGRAMMING SYMPTOM CHART ROUTINES

MODULE PROGRAMMING ROUTINE #1 - OBTAINING AS-BUILT PART NUMBERS

• Start a brand new scan tool session with the vehicle, using the latest level of the scan tool.
• Navigate to the toolbox tab within IDS > module programming menu > as-built menu > select the module you're encountering the error on.
• The first prompt in programming should ask you to confirm the VIN displayed is correct. Confirm all 17 characters are correct or type the full correct VIN into the scan tool if prompted.
• When asked "were you sent here from another procedure to obtain part numbers?", answer Yes to obtain the module and software part numbers the vehicle was built with.
• When the as-built programming procedure is complete, perform the PMI or MR routine again on the module that is experiencing the concern.

MODULE PROGRAMMING ROUTINE #2 - PROGRAMMING THE PCM TO THE CORRECT CALIBRATION

• Start an IDS session. If a previous session is present, select None Of The Above.
• Select No when verifying the information on the Vehicle Specification screen.
• Enter the tear tag into the IDS to identify the vehicle. Use the tear tag from the PTS website, not the one listed on the PCM.

• There will be a second Vehicle Specification screen. Verify the information and select Yes.
• When the session is started, module programming should automatically begin. If it does not, select PMI from the IDS menu and select PCM.
• This procedure will only install the latest factory calibration and will not verify if an unauthorized calibration was installed. Following the repair, attach the PCM filename, ignition counter and any diagnostic trouble codes to the repair order for documentation.
• Re-perform the programming on the module that was previously failing now that the PCM is programmed correctly.

MODULE PROGRAMMING ROUTINE #3 - CONFIRM THE SERVICE AND ENGINEERING PART NUMBER OF THE REPLACEMENT MODULE IS CORRECT FOR THE VIN

• If the module is being replaced during this repair, locate the box the part came in and find the service part number on the box.
• Locate the module you received and find the engineering part number on the module itself.
• Confirm with the parts department, using the Ford electronic catalog (ECAT) parts catalog, that the part received is correct for this VIN.
• If the module was replaced on a previous visit, it may be possible to locate the part number that was installed by reviewing the OASIS warranty history.

MODULE PROGRAMMING ROUTINE #4 - CONFIRM THE IGNITION IS KEY ON, ENGINE OFF AND THE BATTERY SAVER MODE IS NOT ACTIVE

• If equipped with the passive anti-theft system, make sure the keys have been programmed and that the ignition is in the key on, engine off position.
• Make sure a battery charger is installed on the vehicle with the negative cable of the charger connected to chassis ground, not battery negative.
• Make sure the battery state of charge is between 12.6 and 13.6 volts during programming.
• If the error stating "configuration failed, would you like to retry?' occurs again, cycle the ignition off, back on and then click Yes to retry on the error.

MODULE PROGRAMMING ROUTINE #5 - OBTAINING AS-BUILT CONFIGURATION DATA

• Start a brand new scan tool session with the vehicle, using the latest level of the scan tool.
• Navigate to the toolbox tab within IDS > module programming menu > as-built menu > select the module that is encountering the error.
• The first prompt in programming should ask you to confirm the VIN displayed is correct. Confirm all 17 characters are correct or type the full correct VIN into the scan tool if prompted.
• When asked "were you sent here from another procedure to obtain part numbers?", answer No to obtain the module configuration data the vehicle was built with.
• When prompted to manually or automatically obtain and program the data, select to automatically program it.

MODULE PROGRAMMING ROUTINE #6 - REQUESTING MISSING AS-BUILT CONFIGURATION DATA

• On the PTS website, hover over the OASIS tab. Select As-Built.
• At the top of the page, there is a Click Here link to request missing data. Select that link and follow the instructions from the PTS site to request the missing data.
• Missing as-built data requests are answered within 24 hours and when answered, the data will be available on the PTS website if the data was missing.

MODULE PROGRAMMING ROUTINE #7 - CONFIGURING A MODULE WITH AS-BUILT DATA WHEN NO AS-BUILT MENU OPTION IS AVAILABLE

• Unplug the replacement module or remove all of its fuses to depower the module.
• Connect IDS to the vehicle and start a brand new IDS session.
• When the session starts, run the Programmable Module Installation (PMI) on the module.
• When PMI says "install new module", plug the module back in or reinsert the fuses.
• Continue with the PMI per the prompts. The PMI may ask you to enter the manual as-built data as apart of the programming procedure. If it does not ask for you to manually enter the data, it should obtain the data automatically from the server and program the module correctly.

MODULE PROGRAMMING ROUTINE #8 - CONFIGURING A MODULE WITH AS-BUILT DATA USING UPDATE/SPECIAL FUNCTION CODE 53061

• Open IDS and before starting a new session, select the blue ball and socket icon at the top left.
• Select the utility knife icon at the bottom left.
• Select Update/Special Function from the menu.
• In the box provided, type "53061" and press tick.
• After being directed back to the menu, select the blue car icon at the top left.
• Start a new automatic session with the vehicle.
• Run the PMI on the module.
• Continue with the PMI per the prompts. The PMI may ask you to enter the manual as-built data as a part of the programming procedure. If it does not ask to manually enter the data, it should obtain the data automatically from the server and program the module correctly.

MODULE PROGRAMMING ROUTINE #9 - NOT ALL CHARACTERS OF A VIN, TEAR TAG OR AS-BUILT FIT IN THE BOX GIVEN BY IDS

• Right click the desktop on the computer being used and select display settings.
• Adjust the size of test to the recommended size (for example: 100%).
• Adjust the resolution to the recommended setting (for example: 1680 x 1050).
• Restart the computer for changes to take effect.

MODULE PROGRAMMING ROUTINE #10 - CENTRAL CAR CONFIGURATION PROGRAMMING FAILS AT THE SBL - PARTS REQUEST STEP

• Review all SSMs and TBS for applicable messages related to IPC or BCM replacement.
• Run a network test and confirm the BCM and IPC are capable of passing. If either module fails, refer to WSM, Section 418-00 Module Communication > Diagnosis and Testing.

MODULE PROGRAMMING ROUTINE #11 - RECOVERING A PCM WHEN PROGRAMMING FAILED AND RESULTED IN A BLANK MODULE

• Obtain the original IDS used when the programming error occurred during MR or PMI.
• Disconnect the VCM from the IDS and then the DLC.
• Reconnect VCM to the IDS and then the DLC. The VCM icon should appear in the corner of the IDS screen. If the VCM icon does not appear, troubleshoot the IDS-to-VCM connection.
• Attempt to start a new IDS session for the vehicle, if the IDS can read the VIN it will default into the failed programming session. If it cannot read the VIN, locate the original vehicle session used when programming failed. In most cases this would be the last session used. If the original vehicle session cannot be located, use the session created on the date the programming failed. Using an IDS with the latest release available, sessions with failed programming will be highlighted in red.

• Once the session is loaded, the failed process should resume automatically.
• If programming does not resume automatically, proceed to the Module Programming menu and select the previously attempted process (PMI or MR).
• Follow all on-screen instructions to complete the programming process. Near the end of programming, IDS will prompt you to select certain parameters. It is important to make a selection for all parameters listed, even if the correct selection is highlighted you need to click that selection before clicking the tick mark to complete the configuration.
• The last screen on IDS may list additional steps required to complete the programming process. Make sure all applicable steps are performed in the order listed on the screen.

MODULE PROGRAMMING ROUTINE #12 - OBTAINING CALIBRATION FILES

• Check that the computer has an established internet connection, via wi-fi, ethernet or mobile hotspot.
• Retry with a different internet source or at a time of day when the load on the dealer infrastructure is at its lowest, such as early morning or late afternoon.
• Verify that all firewall and anti-virus programs are disabled.
• Review Broadcast and What's New messages on the PTS homepage for the presence of a message indicating a server outage.
• Retry the programming on another computer or tablet device.
• Manually download the file from the corporate server by going to the PTS site > Rotunda Tab > Diagnostic Tool Support > IDS Support > Module Reprogramming. Download the file to the computer per the instructions on this page.