B2947
Body Control Module Configuration Error
Causes
- Incomplete or failed BCM programming/update
- Replacement BCM not programmed or programmed with wrong calibration/VIN
- Corrupted configuration memory in BCM
- Intermittent or failed CAN/LIN communication preventing configuration validation
- Low battery/voltage interruption during programming
- Aftermarket modules or devices causing network conflicts
Symptoms
- Multiple body functions erratic or inoperative (locks, lights, windows, wipers, HVAC, etc.)
- Loss of communication with BCM via scan tool or intermittent comms
- Other modules reporting related network or configuration faults
- Warning lamps or messages related to vehicle electronics
- Functions working only intermittently or default/limited behavior
What to check
- Read all stored DTCs and freeze frame data from BCM and other network modules
- Verify vehicle battery voltage and charging system stability (>=12.4V during service)
- Inspect BCM connectors, pins, and ground points for corrosion or damage
- Check for recent service history: BCM replacement, reflashing, or battery disconnection
- Scan CAN/LIN network for module presence and message traffic (BCM should be present with expected IDs)
- Confirm no aftermarket modules or accessories are connected to body networks
Signal parameters
- CAN bus Tx/Rx messages and IDs for BCM (verify presence and frequency)
- Module identifier/part number
- Calibration ID (CALID) / software part number
- Programmed VIN and configuration bytes
- Supply voltage to BCM (key-on and during programming)
- LIN messages if used for local networks (windows, mirrors, etc.)
Diagnostic algorithm
- Use an OEM-capable scan tool to read and save all DTCs and freeze frame data from the BCM and other modules.
- Verify and document battery voltage; connect a stable battery charger or maintainer if needed before programming procedures.
- Visually inspect BCM connectors, wiring, and grounds; repair any damage or corrosion and recheck communications.
- Confirm the BCM is present and communicating on the vehicle network. If BCM does not respond, check CAN bus power and termination.
- Check vehicle service history for recent BCM replacement or software update. If present, verify that the proper calibration and VIN were applied.
- Use the OEM tool to read BCM software part number/CALID and compare to factory build data or dealer database for correct variant.
- If configuration is incorrect or software is outdated/corrupt, follow manufacturer procedures to reflash/reprogram the BCM (ensure stable power and follow anti-theft/VIN programming steps).
- After programming, verify configuration values (VIN, feature options) and clear DTCs. Reboot modules if required and re-scan for codes.
- If reprogramming fails or configuration cannot be corrected, consider replacing the BCM with a proper, programmable unit and program it to vehicle specifications.
- After repair, confirm all affected body functions operate correctly and perform a road test if needed. Document programming and parts used.
Likely causes
- Recent BCM replacement or software update that was not completed or used wrong calibration
- CAN bus messages required for BCM configuration not present (network fault)
- Corruption of BCM stored configuration due to low battery or internal fault
- Installed module with mismatched software/VIN/calibration ID
Fault status
Similar codes
Brands with available manuals
The library contains 9,514 repair and diagnostic manuals. Choose a brand to open the full manual tree by year, model and trim.
B2947
Security System Sensor Power Circuit Low
Causes
- Incomplete or failed BCM programming/update
- Replacement BCM not programmed or programmed with wrong calibration/VIN
- Corrupted configuration memory in BCM
- Intermittent or failed CAN/LIN communication preventing configuration validation
- Low battery/voltage interruption during programming
- Aftermarket modules or devices causing network conflicts
Symptoms
- Multiple body functions erratic or inoperative (locks, lights, windows, wipers, HVAC, etc.)
- Loss of communication with BCM via scan tool or intermittent comms
- Other modules reporting related network or configuration faults
- Warning lamps or messages related to vehicle electronics
- Functions working only intermittently or default/limited behavior
What to check
- Read all stored DTCs and freeze frame data from BCM and other network modules
- Verify vehicle battery voltage and charging system stability (>=12.4V during service)
- Inspect BCM connectors, pins, and ground points for corrosion or damage
- Check for recent service history: BCM replacement, reflashing, or battery disconnection
- Scan CAN/LIN network for module presence and message traffic (BCM should be present with expected IDs)
- Confirm no aftermarket modules or accessories are connected to body networks
Signal parameters
- CAN bus Tx/Rx messages and IDs for BCM (verify presence and frequency)
- Module identifier/part number
- Calibration ID (CALID) / software part number
- Programmed VIN and configuration bytes
- Supply voltage to BCM (key-on and during programming)
- LIN messages if used for local networks (windows, mirrors, etc.)
Diagnostic algorithm
- Use an OEM-capable scan tool to read and save all DTCs and freeze frame data from the BCM and other modules.
- Verify and document battery voltage; connect a stable battery charger or maintainer if needed before programming procedures.
- Visually inspect BCM connectors, wiring, and grounds; repair any damage or corrosion and recheck communications.
- Confirm the BCM is present and communicating on the vehicle network. If BCM does not respond, check CAN bus power and termination.
- Check vehicle service history for recent BCM replacement or software update. If present, verify that the proper calibration and VIN were applied.
- Use the OEM tool to read BCM software part number/CALID and compare to factory build data or dealer database for correct variant.
- If configuration is incorrect or software is outdated/corrupt, follow manufacturer procedures to reflash/reprogram the BCM (ensure stable power and follow anti-theft/VIN programming steps).
- After programming, verify configuration values (VIN, feature options) and clear DTCs. Reboot modules if required and re-scan for codes.
- If reprogramming fails or configuration cannot be corrected, consider replacing the BCM with a proper, programmable unit and program it to vehicle specifications.
- After repair, confirm all affected body functions operate correctly and perform a road test if needed. Document programming and parts used.
Likely causes
- Recent BCM replacement or software update that was not completed or used wrong calibration
- CAN bus messages required for BCM configuration not present (network fault)
- Corruption of BCM stored configuration due to low battery or internal fault
- Installed module with mismatched software/VIN/calibration ID
Fault status
Similar codes
Manual library for HUMMER
Browse 138 HUMMER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.
HUMMER
-
HUMMER: 2009
-
HUMMER: 2008
-
HUMMER: 2007
-
HUMMER: 2005
-
HUMMER: 2004
-
HUMMER: 2000
-
HUMMER: 1999
-
HUMMER: 1994
-
HUMMER: 1993
B2947
Down latch RH open:open timeout
Causes
- Incomplete or failed BCM programming/update
- Replacement BCM not programmed or programmed with wrong calibration/VIN
- Corrupted configuration memory in BCM
- Intermittent or failed CAN/LIN communication preventing configuration validation
- Low battery/voltage interruption during programming
- Aftermarket modules or devices causing network conflicts
Symptoms
- Multiple body functions erratic or inoperative (locks, lights, windows, wipers, HVAC, etc.)
- Loss of communication with BCM via scan tool or intermittent comms
- Other modules reporting related network or configuration faults
- Warning lamps or messages related to vehicle electronics
- Functions working only intermittently or default/limited behavior
What to check
- Read all stored DTCs and freeze frame data from BCM and other network modules
- Verify vehicle battery voltage and charging system stability (>=12.4V during service)
- Inspect BCM connectors, pins, and ground points for corrosion or damage
- Check for recent service history: BCM replacement, reflashing, or battery disconnection
- Scan CAN/LIN network for module presence and message traffic (BCM should be present with expected IDs)
- Confirm no aftermarket modules or accessories are connected to body networks
Signal parameters
- CAN bus Tx/Rx messages and IDs for BCM (verify presence and frequency)
- Module identifier/part number
- Calibration ID (CALID) / software part number
- Programmed VIN and configuration bytes
- Supply voltage to BCM (key-on and during programming)
- LIN messages if used for local networks (windows, mirrors, etc.)
Diagnostic algorithm
- Use an OEM-capable scan tool to read and save all DTCs and freeze frame data from the BCM and other modules.
- Verify and document battery voltage; connect a stable battery charger or maintainer if needed before programming procedures.
- Visually inspect BCM connectors, wiring, and grounds; repair any damage or corrosion and recheck communications.
- Confirm the BCM is present and communicating on the vehicle network. If BCM does not respond, check CAN bus power and termination.
- Check vehicle service history for recent BCM replacement or software update. If present, verify that the proper calibration and VIN were applied.
- Use the OEM tool to read BCM software part number/CALID and compare to factory build data or dealer database for correct variant.
- If configuration is incorrect or software is outdated/corrupt, follow manufacturer procedures to reflash/reprogram the BCM (ensure stable power and follow anti-theft/VIN programming steps).
- After programming, verify configuration values (VIN, feature options) and clear DTCs. Reboot modules if required and re-scan for codes.
- If reprogramming fails or configuration cannot be corrected, consider replacing the BCM with a proper, programmable unit and program it to vehicle specifications.
- After repair, confirm all affected body functions operate correctly and perform a road test if needed. Document programming and parts used.
Likely causes
- Recent BCM replacement or software update that was not completed or used wrong calibration
- CAN bus messages required for BCM configuration not present (network fault)
- Corruption of BCM stored configuration due to low battery or internal fault
- Installed module with mismatched software/VIN/calibration ID
Fault status
Similar codes
Manual library for MITSUBISHI
Browse 406 MITSUBISHI manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.
MITSUBISHI
-
MITSUBISHI: 2024
-
Outlander
- Black Edition, AWD
- Black Edition, AWD
- Black Edition, FWD
- Black Edition, FWD
- ES, AWD
- ES, AWD
- ES, FWD
- ES, FWD
- Platinum Edition
- Platinum Edition
- SE, AWD
- SE, AWD
- SE, FWD
- SE, FWD
- SEL, AWD
- SEL, AWD
- SEL, FWD
- SEL, FWD
- SEL Black Edition, AWD
- SEL Black Edition, AWD
- SEL Black Edition, FWD
- SEL Black Edition, FWD
-
Outlander PHEV
-
MITSUBISHI: 2023
-
Mirage
-
Mirage G4
-
Outlander
- 40th Anniversary
- 40th Anniversary
- Black Edition, AWD
- Black Edition, AWD
- Black Edition, FWD
- Black Edition, FWD
- ES, AWD
- ES, AWD
- ES, FWD
- ES, FWD
- Ralliart
- Ralliart
- SE, AWD
- SE, AWD
- SE, FWD
- SE, FWD
- SEL, AWD
- SEL, AWD
- SEL, FWD
- SEL, FWD
- SEL Black Edition, AWD
- SEL Black Edition, AWD
- SEL Black Edition, FWD
- SEL Black Edition, FWD
- SE Special Edition, AWD
- SE Special Edition, AWD
- SE Special Edition, FWD
- SE Special Edition, FWD
-
Outlander PHEV
-
MITSUBISHI: 2022
-
Eclipse Cross
- ES, AWD
- ES, AWD
- ES, FWD
- ES, FWD
- LE, AWD
- LE, AWD
- LE, FWD
- LE, FWD
- SE, AWD
- SE, AWD
- SE, FWD
- SE, FWD
- SEL, AWD
- SEL, AWD
- SEL, FWD
- SEL, FWD
- SEL Special Edition, AWD
- SEL Special Edition, AWD
- SEL Special Edition, FWD
- SEL Special Edition, FWD
- SE Special Edition, AWD
- SE Special Edition, AWD
- SE Special Edition, FWD
- SE Special Edition, FWD
-
-
MITSUBISHI: 2021
-
MITSUBISHI: 2020
