SRS / RCM / Programming guide

AIRBAG & RESTRAINT CONTROL MODULE

Monitors crash sensors, airbags, pretensioners, occupant classification and restraint-system status.

MODULE GUIDE05/38

01Replacement-module configuration

02Software update when permitted

03Occupant-system setup

04Crash-data disposition per OEM policy

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 dedicated safety CAN is common; CAN FD and FlexRay may be used on newer safety domains. Crash sensors and occupant devices may use PSI5 or dedicated point-to-point circuits—not the vehicle CAN directly.

DIAGNOSTIC TRANSPORT

Programming access

Programming is normally through a protected diagnostic session over CAN/CAN FD or a gateway. Some controllers are not reprogrammable after deployment data is stored and some replacement operations require security authorization.

PROGRAMMING TOPOLOGY

Critical online dependencies

Occupant-classification, seat, buckle, impact-sensor, cluster and gateway status must be valid. Never infer sensor-network type from connector wire count alone.

BEFORE CONNECTING

✓ OEM disabling and waiting procedure followed✓ Correct new or approved module✓ All deployed components and crash sensors inspected✓ Stable support voltage✓ OEM scan and security capability

COMPLETE TEST SEQUENCE

  1. Follow the OEM depowering procedure and observe the specified wait time.
  2. Inspect and repair deployed devices, wiring, connectors and impact sensors before setup.
  3. Install only the approved controller and restore power as directed.
  4. Program or configure the module with exact vehicle build information.
  5. Perform occupant-classification and seat-position routines when required.
  6. Clear faults only after the complete restraint system is restored.
  7. Verify lamp prove-out and rescan without anyone occupying the vehicle during initial checks.

POST-PROGRAMMING VERIFICATION

  • Airbag lamp proves out and turns off normally
  • No current restraint DTCs are present
  • Passenger status indicators behave as specified
  • Module VIN/configuration matches the vehicle
VEHICLE-SPECIFIC DATA WINS

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

NEXT MODULE / EPS / PSCMElectric Power Steering Module→