Safety Warning
DIY auto repair can cause serious injury, fire, or vehicle damage. These guides are for informational purposes only. Always follow OEM torque specs, wear PPE, and consult a certified mechanic if you are unsure. You are solely responsible for your safety.
FDRS Module Programming Job Aid (24-7011)
Reference number: 24-7011
FDRS MODULE PROGRAMMING JOB AID
TECHNICAL SERVICE BULLETIN
| FORD: | All Models |
MARKETS
North American markets only
SUMMARY
This article provides support for module programming related concerns that may be encountered while using the FDRSÂ scan tool. The information contained within this article assumes that all steps of the service repair process have been completed, including documenting the vehicle owner's current concern, reviewing TSB, SSM, FSAÂ and the WSMÂ . This document does not supersede or replace existing publication or warranty direction.
SERVICE INFORMATION
EQUIPMENT, TOOLING AND DEALER INFRASTRUCTURE
The FDRSÂ scan tool utilizes a cloud-based architecture. The benefits of such an architecture include the ability for Ford to make real time improvements without the need for dealers to complete a lengthy diagnostic tool update. A cloud-based architecture reduces scan tool installation time by reducing installation package size. A result of this architecture may be that dealers experience extended software download time during module programming events if their dealer infrastructure does not meet Ford recommendations. Poor internet connection or upload/download (megabytes per second [Mbps]) times may contribute to extended software download times during module programming. These minimum dealer infrastructure requirements depend on several factors, including the number of devices connected to the dealers' network.
INTERNET SERVICE MINIMUM BANDWIDTH SPECIFICATIONS
| Number Of Connected Devices | Network Download (Mbps) Speed Requirements | Network Upload (Mbps) Requirements |
|---|---|---|
| < 20 devices | >100 Mbps | >10 Mbps |
| 20-100 devices | >300 Mbps | >30 Mbps |
| >100 devices | >500 Mbps | >50 Mbps |
MINIMUM RECOMMENDATIONS - DIAGNOSTIC EQUIPMENT (EXAMPLE - FDRS)
| Processor | 5 Gen 10 or equivalent |
| System Memory (RAM) | 16 Gigabyte (GB) |
| Hard Disk Drive | Solid State 500 GB |
| USB Ports | 2 (Universal Serial Bus (USB) 3.1 Gen 1, USB 3.1 Gen 2) |
| Display | 20 inch monitor (1600x900 minimum resolution) |
| Network Adapter | Wired: Recommend Ethernet-based if available (1 Gigabit); Wireless: 802.11ac, 802.11ax preferred |
| Operating System | Microsoft Windows 10 |
SERVICE FUNCTIONS
Service functions refer to any application within FDRSÂ that might complete a learning routine, calibration, or initialization. These routines include things like LINÂ new module initialization, ABS HCUÂ pressure bleed, and camera alignments. These routines, from a high-level point of view, are not VINÂ -specific. These routines operate in a manner where FDRSÂ instructs the responsible module on the vehicle to execute the routine. FDRSÂ simply sends a go command to the module. The module will then perform the routine as it is coded to do. The most common causes for a service function errors are damaged circuits or components involved in the system. For example, if a BCM LINÂ initialization routine fails, it is possible that a fault on the LINÂ network or a fault with the LINÂ device is the cause. A fault with the FDRSÂ scan tool application could be ruled out by running it on another similarly equipped VINÂ since these applications are not VINÂ -specific.
MODULE SWAPPING AND ORDERING USING A DIFFERENT VIN
Swapping a used module from a vehicle for diagnostic purposes or to complete repairs is likely to cause vehicle symptoms or programming errors and is not recommended. Ordering a replacement module using a VINÂ from a different vehicle is also not recommended. Most modules on these affected vehicles are VINÂ /vehicle specific, and hardware variations between modules do exist. Swapping a module from a vehicle or ordering a module using a different vehicle/VINÂ can cause ineffective repairs and additional vehicle downtime. Make sure all appropriate WSMÂ procedures are followed when diagnosing the condition before any module replacements and only order modules using the correct VINÂ .
ADDING/REMOVING FEATURES USING PROGRAMMABLE PARAMETERS DUE TO VEHICLE MODIFICATIONS
Ford and Lincoln vehicle owners may request modifications to their vehicle such as enabling DRLÂ , adding navigation, changing tire/axle sizes, and/or adding trailer brake control modules. A list of programmable parameters that are available for alteration is shown in WSMÂ , Section 418-01A > Module Configuration. Parameters available for alteration will vary by model and model year. If the desired parameter is not listed in the right column of the Module Configuration And Parameter Chart, alteration of that parameter is not supported by Ford Motor Company. A list of supported parts that can be added to the vehicle is available at accessories.ford.com. Adding/removing accessories and/or programming vehicle features is not warrantable.
MODULE SERVICE REPLACEMENT PARTS
The FDRSÂ service scan tool functionality is largely based on the part number of the individual modules installed in each vehicle. If an incorrect module has been fitted to a vehicle, application and programming errors are likely. If a fault is occurring only on a replacement module, it is recommended that the installed part be verified as compatible by VINÂ using the Historical Vehicle Bill of Material (HVBoM), the Ford ECAT parts catalog or Ford Component Sales (FCS) online 1878 form (for infotainment modules). The first digit of the prefix in a part number indicates the model year that the part was intended for, identical to the 10th digit of the VINÂ .
- Example: MU5T-15604-A. The M indicates that this part is intended for a 2021 model year vehicle.
- Example: LU5T-15604-B. The L indicates that this part is intended for a 2020 model year vehicle.
Most often, replacement modules should share the same part number as the one which the vehicle was built with according to HVBoM, or a later level part found in ECAT or FCS 1878 order forms. For example, a 2021 model year vehicle built with an M prefix part should usually not receive an L prefix part from 2020 model year. This is a general rule for module part numbers and there are few exceptions. Other vehicle parts may not have the same model year correlation to their part numbers.
Module parts are often superseded and intended to be made backward compatible, though. For example, a 2021 model year vehicle built with an M prefix part may receive a superseded part with a prefix that begins with N for the 2022 model year.
MODULE COMMUNICATION
The vast majority of FDRSÂ functions require communication between the FDRSÂ scan tool and one or more modules on the vehicle via the CANÂ . CANÂ and module communication related concerns should be addressed before programming is attempted. Programming while a CANÂ issue is present may result in damaged modules, unnecessary vehicle downtime and unnecessary warranty expenditure. This article will not discuss in depth how network diagnostics should be performed but will focus on a few key concepts as they relate to module programming. Diagnostics for network concerns should be performed per the direction in the WSMÂ .
- On SYNC 4 equipped vehicles, certain modules are programmed between both the CANÂ and USBÂ drive. These modules often include the infotainment modules such as the APIM, TCU, GWMÂ and/or high level IPCÂ . USBÂ port, USBÂ cable, ethernet network or CANÂ faults may contribute to programming errors.
- For all other modules on SYNC 4 or previous generations of vehicles, programming is performed over the CANÂ . Module or network communication faults will contribute to vehicle symptoms and programming errors.
- A module needs three things to communicate properly on the CANÂ and with the FDRSÂ scan tool: power to the module, ground to the module, and the CANÂ wiring.
- The FDRSÂ Network Monitor application will ping each module or network enabled in the test and make sure that FDRSÂ receives a response from the module, proving that communication is likely ok.
- Running the on-demand DTCÂ self-tests will stress test the module communication by forcing the module to activate outputs during the test. Modules failing or aborting the on-demand DTCÂ self-test (grey in color) suggests that the power, ground, or CANÂ wiring may be damaged.
- Modules that respond negatively (purple in color) suggest that the module is communicating but may have failed a previous programming attempt, possibly due to a module or network related communication concern.
When the customer's symptoms, DTCÂ s, and any programming errors present themselves like a possible network concern, it is recommended to not only rely on self-test and network monitor results. These tests are great go/no-go type tests. However, due to network fault tolerance, these tests may pass and suggest that the network is OK. However, module programming often transmits significantly more data over the network than these tests, increasing the odds of an error only during programming. It may be necessary to perform loaded voltage drop testing on all of the module's power and ground circuits. The VCMMÂ oscilloscope is a powerful tool for verifying the integrity of the CANÂ itself. Known good network waveforms are available in WSMÂ , Section 418-00x and additional information regarding VCMMÂ usage and setup can be found in STARSÂ training.
The below example demonstrates a VCMMÂ capture (Figure 1) of an HS-CANÂ network which is being shorted to ground (0.0v) but that the HS-CANÂ modules are communicating (green in color) with FDRSÂ via the ALL CMDTCÂ test. This example demonstrates the potential need to take network diagnostics further than running a network test or self-test.
IDENTIFYING A PROGRAMMING RELATED CONCERN
Vehicle repairs have taken on additional complexity over the last decade. Many repairs include the need to complete module replacement programming, learning, or calibration routines. With repairs being so reliant on scan tools, it is critical to understand how the scan tool functions and when a vehicle symptom may result from a programming error. Determining when a vehicle symptom is programming-related is not always an easy task. It often requires a thorough understanding of the entire service repair process for the vehicle in question. A few of the key things to look for in the service process include:
- Original concern vs. current concern
- If a vehicle came in for service for the same concern that is present after module replacement or programming, this is unlikely to be a programming-related issue.
- The concern may be programming-related if a new DTCÂ or symptom is present only after performing module programming or replacement. Verify that all installation steps per the WSMÂ have been completed properly. If the issue remains, it is likely that the module was flashed or configured incorrectly and requires support from the module programming team.
- DTCsÂ
- Replacement modules have default or manufacturer substate DTCÂ s stored that indicate they require programming, initialization, and/or calibration routines completed. If the same DTCÂ the vehicle entered service with returns on the replacement, the concern is unlikely to require module replacement or programming. Most replacement modules will only store DTCs related to the steps required in the installation process, not circuit or performance related DTCÂ s.
- DTCs stored for components which the vehicle is not equipped with per the build sheet and/or window sticker may suggest a programming-related concern. In some cases, a module may still have wiring for the component it is not equipped with and may still monitor for circuit faults. If the wiring is present, it should still be inspected, particularly for shorts to voltage or ground. These types of circuits are usually expected to be open.
- Service messages
- Review all available service messages that may relate to both the customer's original concern, current concern, and the programming error being encountered.
- Intermittent vs hard faults
- Modules are either programmed correctly or incorrectly. If the module is programmed incorrectly, the symptom or DTCÂ will always be present. Intermittent DTCÂ s suggest that a vehicle-side concern in wiring, connectors or components may be present.
12-VOLT BATTERY TESTING, CHARGING, MAINTENANCE AND STATE OF CHARGE FOR MODULE PROGRAMMING
BATTERY HEALTH AND VOLTAGE MAINTENANCE
- It is recommended to test the 12-volt battery(ies) using approved Rotunda tools prior to a programming event. Ford warranty supports the use of the GRX-3590 and/or DCA-8000 units to perform 12-volt battery testing.
- The battery(ies) should be fully charged or replaced prior to programming, based on the test results from the approved Rotunda tools.
- Once battery health is determined using approved Rotunda tools, the battery should be maintained in the 12.6 volt - 13.6 volt range for module programming. It may be necessary to verify that the voltage is within the desired range using displays on the charger, the battery monitor status at the bottom right corner of the FDRSÂ scan tool or using a digital volt ohm meter (DVOM) connected to the battery.
- If equipped, the tool being utilized to maintain the battery should be adjusted to the maximum time limit possible, to prevent charger/maintainer time outs during long flash events.
- Battery charging should be performed per WSMÂ , Section 414-01 > General Procedures. Depending on the vehicle, the proper charging procedure may vary, but is important so that the charger does not lead the BMSÂ system to believe the vehicle's battery is being discharged. It is recommended to leave the battery connected and connect the battery charger negative clamp to chassis ground, not the battery negative post.
Example of Proper Charging Procedures per WSM, Section 414-01. Always refer to the specific manual for the vehicle in question.Â
| Charger Connected to Engine or Chassis Ground (Battery Connected) | Charger Connected to Battery Posts (Battery Disconnected) |
|---|---|
|
|
BATTERY STATE OF CHARGE PERCENTAGE (BATT_SOC%)
The BCMÂ calculates the battery SOCÂ using inputs from the BMSÂ , known battery capacity, battery voltage, battery time in service and battery temperature. The battery SOCÂ can be used to verify that the battery will support vehicle current consumption demands during module programming. If the battery is in poor condition and the BCM PIDÂ for BATT_SOC reports that SOCÂ is low, offboard battery chargers may not be able to maintain the voltage or current demands required of both the battery and the vehicle, leading to programming faults. This may cause the vehicle load shed to activate and disable ignition switched power to certain modules. Certain modules also have requirements for the SOCÂ to be at a certain percentage before programming can be performed. The FDRSÂ programming applications will call attention to the SOCÂ % requirement for modules that have this requirement. It is generally recommended that the battery SOCÂ be at 75% or greater to be sure of successful programming.
PARAMETER IDENTIFIERS (PIDS) RELATED TO BATTERY HEALTH AND CHARGING
Monitor the following BCM PIDÂ s: BATT_SOC, BAT_CURRENT, VPWR_RAW. Example PIDÂ usage is provided in the tables below.
MAY LEAD TO PROGRAMMING FAULTS
| BCM PID | Value | Detail |
|---|---|---|
| VPWR_RAW | 11.8 volts | Voltage is below minimum recommended voltage of 12.6 volts to 13.6 volts |
| BATT_SOC | 65% | Battery state of charge is below recommended 75% |
| BATT_CURRENT | -17.0 amps | The vehicle is consuming more amperage (power) than the is being provided to the battery |
ACCEPTABLE VALUES WHICH WILL SUPPORT SUCCESSFUL PROGRAMMING
| BCM PID | Value | Detail |
|---|---|---|
| VPWR_RAW | 13.2 volts | The voltage is within the recommended range of 12.6 volts to 13.6 volts |
| BATT_SOC | 77% | The battery state of charge is above the minimum recommend value of 75% |
| BATT_CURRENT | 2.0 amps | The battery is being provided enough power to meet vehicle demands |
FDRS VEHICLE IDENTIFICATION PROCESS
Starting a vehicle session requires the user to select the Read VIN From Vehicle button in FDRSÂ . Once the Read VIN From Vehicle button is selected, FDRSÂ will read the VINÂ via the CANÂ from the PCMÂ using OBDÂ -II protocol from PCMÂ Mode 09 data. The PCMÂ will report the VINÂ to FDRSÂ , which displays it in the VINÂ entry box. The user will then select Go, at which time FDRSÂ will retrieve a vehicle model from the servers for that VINÂ , including which modules are equipped, the powertrain type, and the vehicle program information. This process occurs while FDRSÂ displays a progress bar stating, Downloading Vehicle Information. Once obtained, FDRSÂ will perform a network test on the vehicle and read the part numbers and DTCÂ in all equipped modules.
VEHICLE IDENTIFICATION PROCESS ERRORS
| Error Encountered | Detailed Description | Repair Action |
|---|---|---|
| Error: A problem occurred while performing the Vehicle Identification process. Please check the VIN and Internet connectivity and try again. | FDRSÂ obtained the VINÂ from the vehicle and then tried to download vehicle specific data from the servers but was unable. Firewalls, anti-virus programs, poor internet connection or speed, and server outages are possible causes. |
Verify internet speed and connection meets minimum requirements. (Requirements can be found by clicking the settings icon in FDRSÂ , refer to Figure 2 at the end of this table) |
| Incorrect VINÂ displayed after user selects Read VIN From Vehicle | The BCMÂ is the VINÂ master module. At ignition-on events, the BCM sends the VINÂ via the CAN network to the PCM. The PCM stores the VINÂ that it receives and reports it to the scan tool via OBDII mode 09. It is possible that either PCM or BCM have the incorrect VINÂ stored to cause the VINÂ to be displayed incorrectly. |
|
| VIN Mismatch Window displaying a message stating that one or more modules contain the incorrect VINÂ | The modules displayed with the incorrect VINÂ may have been swapped or configured incorrectly. |
|
| Unable to Retrieve VIN or VINÂ displayed is XXXXXXXXX | When FDRSÂ is unable to obtain the VINÂ from the PCM, it will attempt to obtain the VINÂ from the BCM as a backup. If FDRSÂ cannot obtain the VINÂ from either module, FDRSÂ will not be able to automatically obtain the VINÂ and start a session. This may be due to an error in communication between FDRSÂ , VCM and these two modules. Suspect a vehicle side concern. | Start a manual vehicle entry session and then run the network monitor application. Document the modules which are not responding to FDRSÂ . Follow the appropriate diagnostic path from WSMÂ , Section 418-00 to identify the cause of the network concern. |
MODULE PROGRAMMING PRE-CHECKS
- Verify that the 12-volt battery is maintained between 12.6 volts and 13.6 volts using approved Rotunda tools, including the GRX-3590 or DCA-8000 units. Refer to the 12-Volt Battery Testing, Charging, Maintenance And Sate Of Charge For Module Programming section in this article for additional recommendations and testing.
- Verify that the BCMÂ Battery State of Charge % (BATT_SOC%) PIDÂ is reading 75% or greater. Refer to the 12-Volt Battery Testing, Charging, Maintenance And Sate Of Charge For Module Programming section in this article for additional recommendations and testing.
- Inspect the vehicle for possible aftermarket electronic accessories that may be connected to the vehicle's network wiring. These devices may include remote start kits, GPSÂ devices, radios, alarms, insurance dataloggers, gauge packs/pods, and hotspot devices. They may be located on or near the kick panels, dash A-pillars, glove box, center console, or near the DLCÂ .
- Verify that accessory loads are off, including headlamps, heated/cooled seats, and the climate control system blower motor.
- Verify that the scan tool and vehicle communication interface are at the latest available software levels. The latest levels of each can be downloaded from PTS > Rotunda tab > Diagnostic Tool Support > Download Software.
- Verify that if a module has been replaced, that the correct replacement part has been installed. Refer to the Service Replacement Parts section in this article.
- Verify that the module is properly communicating. Refer to the Module Communication section in this article.
- Verify that service messages (PTS Alerts, TSB, SSMÂ , etc) have been reviewed, not only for the customers original vehicle concern but also for messages which might be related to the programming being attempted.
MODULE PROGRAMMING ERRORS AND TROUBLESHOOTING
COMMUNICATION ERRORS
| Error Encountered | Detailed Description | Repair Action |
|---|---|---|
|
FDRSÂ was unable to communicate with the module. This may be due to a fault on the vehicles network or with communication to a specific module. It may also be possible that a diagnostic file used by the FDRSÂ scan tool or information within the FDRSÂ servers is incorrect. |
|
MISSING DATA ERRORS
| Error Encountered | Detailed Description | Repair Action |
|---|---|---|
|
FDRSÂ was unable to obtain module configuration data or software files from the Ford servers. Internet connectivity, upload/download speeds or missing data from the Ford servers may contribute to these errors. |
|
PARTS AND GVMS WARNING ERRORS
| Error Encountered | Detailed Description | Repair Action |
|---|---|---|
|
FDRSÂ reads the part number from the vehicle and was unable to find a corresponding software lineage on the Ford servers. This may be due to the incorrect module having been installed or a fault with the software lineage on the Ford servers. |
|
FLASH FAILURES
| Error Encountered | Detailed Description | Repair Action |
|---|---|---|
|
The module has failed the flash process via the CANÂ . It is possible that the module programming pre-checks have not been completed, that a module or network communication fault exists, or that an error in the Ford servers exists. |
|
SECURITY FAILURES
| Error Encountered | Detailed Description | Repair Action |
|---|---|---|
|
FDRSÂ was unable to successfully gain security access to the Module. This may be caused by module or network communication errors. This may also be caused by the FDRSÂ database containing the incorrect security key for the module. | Verify that the module can complete a network test and/or on-demand DTCÂ self-test. Refer to the Module Communication section in this article. |
CONFIGURATION FAILURES
| Error Encountered | Detailed Description | Repair Action |
|---|---|---|
|
The module did not accept the configuration data written to it in one or more Data Identifier (DID) ranges. This may happen when the configuration data being written is incorrect for the installed hardware or based on the software on the module. This may be the result of an incorrect part being installed, the module being flashed with the wrong software, or the configuration data being written is incorrect. |
|
Use the Manual With the Right Hardware
Pair factory procedures with proven DIY tools so the instructions are easier to execute.
Disclosure: Verified tool recommendations may earn an affiliate commission at no cost to you.
When to See a Mechanic
Stop DIY work and contact a certified mechanic immediately if any of the following apply:
- • You smell fuel, burning insulation, or see smoke.
- • Brakes feel soft, pull hard to one side, or make grinding noises.
- • The engine overheats, stalls repeatedly, or misfires under load.
- • You are missing required tools, torque specs, or safe lifting equipment.
- • You are not confident in the next step or safety outcome.
