FPCM / FPDM / Programming guide

FUEL-PUMP CONTROL MODULE

Regulates low-pressure fuel delivery using pump speed, current control and pressure-demand commands.

MODULE GUIDE20/38

01Driver-module software update

02Replacement FPCM setup

03Fuel-system variant coding

04Pump characterization / prime routine

PROGRAMMING DECISION GATES

Identify, protect and recover the operation

Do not treat every service event as a simple flash. Determine what must be transferred, authorized, calibrated and verified before writing software.

01 / IDENTIFY

Define the operation

  • Separate a software update from replacement setup, coding, security pairing and calibration.
  • Record the current software, part number, VIN and configuration before changing anything.
02 / COMPATIBILITY

Pass the compatibility gate

  • Confirm part number, hardware level, supersession, region, options and new-versus-used restrictions.
  • Verify the OEM tool, subscription, interface and required security credentials.
03 / PRESERVE

Protect data and sequence

  • Save the pre-scan, identification, as-built data and learned values the procedure permits you to restore.
  • Follow the OEM module order, ignition states and CAN FD or DoIP transport requirements exactly.
04 / RECOVER

Respond to interruption

  • Do not cycle the ignition or disconnect power unless the OEM recovery prompt directs it.
  • Preserve the error, verify support voltage and communication, then use the approved recovery or bootloader routine.

NETWORK & PROGRAMMING ACCESS

Likely architecture paths

These are common implementations, not a vehicle-specific pinout. Confirm the exact topology, protocol and gateway route in current OEM service information before connecting or programming.

VEHICLE COMMUNICATION

Possible networks

High-speed or body CAN is common; CAN FD appears on newer powertrains. The pump motor is normally a high-current PWM output, not a network node.

DIAGNOSTIC TRANSPORT

Programming access

Usually UDS over CAN/CAN FD through the PCM or gateway; some modules accept configuration indirectly from the PCM.

PROGRAMMING TOPOLOGY

Critical online dependencies

PCM, fuel-pressure sensor, BCM crash status and battery-voltage data may be required. Diagnose the power stage separately from network communication.

BEFORE CONNECTING

✓ Correct part number, hardware level and software package✓ OEM service information, application and active subscription✓ Approved interface and stable OEM-specified support supply✓ Complete pre-scan, identification and configuration saved✓ Communication, power and ground faults resolved

COMPLETE PROGRAMMING SEQUENCE

  1. Save pressure demand, duty cycle, current and original configuration.
  2. Verify pump power, ground, wiring, fuel level and mechanical pressure before replacement.
  3. Program the correct pump, tank and engine variant.
  4. Run prime, pressure or pump-characterization routines when specified.
  5. Compare commanded pressure, actual pressure, duty cycle and current under load.

POST-PROGRAMMING VERIFICATION

  • Identification and calibration match the intended repair
  • Every required setup or calibration reports complete
  • No programming, configuration or communication DTCs return
  • System operation is confirmed under safe operating conditions
VEHICLE-SPECIFIC DATA WINS

Software, subscriptions, security access, voltage targets and ignition sequences vary by manufacturer and model.

NEXT MODULE / SCCM / SZLSteering Column Control Module→