Hours: 07–23 daily

TuningBot DTC Database · v4.37.15

P1633 Diagnostic Trouble Code (8 interpretations)

8 manufacturer-specific interpretations across 7 manufacturers in the TuningBot DTC database.

P · PowertrainBatteryOBD2

Ford

1 interpretation
P1633
Keep Alive Power Voltage Too Low Ford · battery Data confidence 62%

The control module detected that the Keep Alive Power Voltage value was below the expected limit. This is the manufacturer-specific definition used by Ford.

Possible causes

  • Wiring
  • ECM

Honda

1 interpretation
P1633
Engine control module (ECM) circuit problem Honda · engine Data confidence 62%

The control module detected a fault associated with the Engine control module (ECM) circuit problem circuit or function; the stored code identifies the affected component rather than a single failure mode. This is the manufacturer-specific definition used by Honda.

Possible causes

  • Wiring
  • motor control module (MCM) programming
  • MCM

Hyundai

1 interpretation
P1633
Battery Overcharge Hyundai · engine Data confidence 62%

The control module detected a fault associated with the Battery Overcharge circuit or function; the stored code identifies the affected component rather than a single failure mode. This is the manufacturer-specific definition used by Hyundai.

PSA

1 interpretation
P1633
Engine ECU : ECU internal fault PSA · engine Data confidence 72%

The control module detected the fault condition "ECU internal fault" for the Engine ECU. Documented for the Bosch EDC16C34 injection ECU (DV6TED4 1.6 HDi) on Peugeot applications; the same PSA control units are also fitted to Citroën models.

Applies to Peugeot Bosch EDC16C34 injection ECU (DV6TED4 1.6 HDi)

Toyota

1 interpretation
P1633
Engine control module (ECM) - throttle actuator control (TAC) system - malfunction Toyota · engine Data confidence 62%

The control module detected improper operation of the Engine control module (ECM) - throttle actuator control (TAC) system. This is the manufacturer-specific definition used by Toyota.

Possible causes

ECM

VAG

2 interpretations
P1633
Accelerator pedal position (APP) sensor 2 - low input VAG · engine Data confidence 62%

The control module detected that the Accelerator pedal position (APP) sensor 2 signal stayed below the expected range. This is the manufacturer-specific definition used by Audi.

Possible causes

  • Wiring short to ground
  • APP sensor
Applies to Audi
P1633
Accelerator Position Sensor 2 (G185): Signal too Low VAG · engine Data confidence 84%

The control module detected that the Accelerator Position Sensor 2 (G185) value was below the expected limit. This is the manufacturer-specific definition used by Volkswagen. Volkswagen Group tools also report it as fault code 18041. Documented across Volkswagen Group applications (Audi, SEAT and Škoda included).

Symptoms

Unknown

Possible causes

  • Wiring and/or connections faulty
  • Sensor (G185) faulty
Applies to Volkswagen

Volvo

1 interpretation
P1633
CAN data bus, ABS (VSS signal) - not received in time Volvo · engine Data confidence 62%

The control module detected a fault associated with the CAN data bus, ABS (VSS signal) - not received in time circuit or function; the stored code identifies the affected component rather than a single failure mode. This is the manufacturer-specific definition used by Volvo.

Possible causes

  • Wiring
  • CAN data bus
  • ABS control module

Related and nearby codes

How to read P1633

P

Powertrain: engine, transmission and driveline systems.

1

Manufacturer-defined range: the meaning can differ between brands.

633

Specific fault index within the subsystem.

Frequently asked questions about P1633

What does P1633 mean?

Diagnostic Trouble Code (8 interpretations). The control module detected that the Keep Alive Power Voltage value was below the expected limit. This is the manufacturer-specific definition used by Ford.

Is P1633 generic or manufacturer-specific?

P1633 is a manufacturer-specific code. In this database it is documented for: Ford, Honda, Hyundai, PSA, Toyota, VAG, Volvo. The same number can mean something different on other brands.

Can TuningBot remove P1633 at file level?

If the fault logic lives in the ECU calibration, yes: our DTC Removal file service disables the specific fault entry. Checksum correction is not included: it is a separate, optional service. Not sure whether your case qualifies? Request a free assessment and our engineers will check your ECU file.

Other file services

ECU tuningDyno-tested results by model and engine See the results →

← Search the full DTC database