LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Ford >> 2010 >> Expedition RWD >> Repair and Diagnosis >> External Pages >> Different car >> Section 1500 (Module Configuration System) >> Diagnosis And Testing >> Module Configuration >> Principles of Operation >> Definition of Terms
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Definition of Terms

WARNING: This page is about a different car, the 2010 Ford Focus. However, it is still accessible from the selected car via links, so may be relevant.

The following are definitions of configuration terms:

Programmable Module Installation (PMI) 

PMI  is a scan tool process which configures settings in a new module. Data used for the PMI  process is automatically downloaded from the original module and stored when a scan tool session is started. If this data cannot be retrieved from the module being replaced, the scan tool may prompt for As-Built data entry or display a list of parameter values that need to be manually selected. Some modules are reprogrammed during PMI  when a strategy/calibration update is available. To carry out PMI  , refer to PROGRAMMABLE MODULE INSTALLATION (PMI) .

NOTE: It is important that the scan tool identifies the vehicle and obtains configuration data prior to removing any modules. The new module must be able to communicate with the scan tool in order to carry out PMI  .

Module Reprogramming 

Module reprogramming (also referred to as "flashing") is a scan tool process which updates the strategy/calibration in a module. Reprogramming a module with the same level of software will not improve module operation or repair a hardware failure. Module reprogramming is automatically carried out during PMI  when a later strategy/calibration is available.

NOTE: Module reprogramming should be limited to circumstances where a published TSB procedure recommends doing so.
NOTE: A module cannot communicate with other modules on the communication network while being reprogrammed. Clear any network communication DTCs which may have been set in other modules during the reprogramming process.

Accessory Protocol Interface Module (APIM) Programming 

Accessory Protocol Interface Module (APIM) programming is a process that updates the APIM  Consumer Interface Processor (CIP) and Vehicle Interface Processor (VIP) software. The VIP  programming updates the calibration files in the portion of the APIM  that interfaces with the Controller Area Network (CAN). The CIP  programming updates calibration files in the portion of the APIM  that interfaces with mobile phones and other customer devices.

APIM  programming uses the Vehicle Communication Module (VCM) to read and program the VIP  software through the Data Link Connector (DLC). A web-based On-Line Automotive Service Information System (OASIS) application is used to read and program the CIP  software via a Universal Serial Bus (USB) cable between the scan tool and the vehicle USB port. Both the VCM and the OASIS application must be running on the scan tool during APIM  programming. To carry out APIM  programming, refer to ACCESSORY PROTOCOL INTERFACE MODULE (APIM) PROGRAMMING .

Programmable Parameters 

Programmable parameters are customer preference items that may be modified by the dealer via scan tool or in some cases, modified by the customer following a procedure listed in the vehicle Owner's Literature. While many configuration options may exist for a module, only a few of these options are programmable parameters.

Adaptive Learning and Calibration 

Some modules require a separate learning procedure be carried out if replaced as part of a repair procedure. For adaptive learning and calibration instructions, refer to the specific module removal and installation procedures.

Vehicle Identification (VID) Block 

Some PCMs contain a memory area called a Vehicle Identification (VID) block. The PCM VID  block commonly stores powertrain configuration items such as Vehicle Identification Number (VIN), tire size, axle ratio, and whether or not the vehicle is equipped with speed control.

Module Address 

A unique module address is assigned to each module on the network for identification.

As-Built Data 

As-Built data is a VIN  -specific module configuration record. During vehicle build, the configuration from all modules is downloaded and stored in the As-Built database. As-Built data does not reflect customer preference items that have been changed from the default state. These items need to be changed using programmable parameters after the module is configured.

NOTE: It is not necessary to obtain As-Built data unless directed to do so by the scan tool. This data may be accessed from the technician service publication website.

The following chart lists As-Built data addresses and describes specific module configuration information:

MODULE CONFIGURATION AND PARAMETER CHART

Module Module Address Requires PMI  Reprogram/Flash Capable Requires Adaptive Learning or Calibration Available Programmable Parameters
ABS module 760 Yes Yes No None
Accessory Protocol Interface Module (APIM) 7D0 Yes Yes No
  • Steering wheel controls
  • Stereo in passthrough
Audio Control Module (ACM) 727 Yes Yes No
  • 2-way front speakers
  • 2-way rear speakers
  • APIM 
  • SDARS  module
  • Stereo auxiliary jack
  • Steering wheel controls
  • Steering wheel controls type
  • Subwoofer
Front Controls Interface Module (FCIM) 7A7 No Yes No None
Front Display Interface Module (FDIM) 7A6 Yes Yes No
  • SDARS  module
  • APIM 
HVAC module 733 No No No None
Instrument Cluster (IC) 720 Yes Yes No
  • Belt-Minder®
Occupant Classification System Module (OCSM) 765 No Yes
  • Seat weight sensor re-zero
None
PCM 7E0 Yes Yes
  • Adaptive airflow
  • Idle speed
  • Refueling event
  • Fuel trim
  • Axle ratio
  • Speed control
  • Tire size
Restraints Control Module (RCM) 737 Yes Yes
  • Seat weight sensor re-zero
  • Driver seat Belt-Minder® activation
  • Passenger seat Belt-Minder® activation
Smart Junction Box (SJB) 726 Yes Yes No
  • Autolock
  • Auto-unlock