What This Actually Means
In plain language — no jargon
The fuel level sensor B is sending a signal that's too low, like a radio station coming in too weak. The ECU can't accurately read how much fuel is in the tank.
Symptoms You May Notice
3 known symptoms for this code
Fuel gauge reads empty or fluctuates erratically
Check Engine Light illuminated
Inaccurate fuel consumption data on dashboard
How Your ECU Detects This
Technical sensor logic and voltage thresholds
The ECU monitors the analog voltage output from the fuel level sensor, which should vary between 0.5V and 4.5V as the float moves in the tank. When the voltage drops below the minimum threshold and stays low, the ECU detects a circuit low fault condition.
Voltage & Parameter Thresholds
| Parameter | Normal Range | Fault Condition |
|---|---|---|
| Sensor Output Voltage | 0.5V to 4.5V | Below 0.5V |
| Signal Stability | Smooth voltage transitions | Erratic or stuck-low readings |
Diagnostic & DIY Fix Guide
Check these in order — from cheapest to most complex
1
Fuel Level Sensor Connector
Locate the sensor connector at the fuel tank and inspect for corrosion, loose pins, or water damage; clean contacts with electrical cleaner.
2
Fuel Level Sensor Wiring Harness
Trace the wiring from tank to ECU for damaged insulation, pinched wires, or loose connectors and repair or reseat as needed.
3
Fuel Level Sensor Unit
Remove the fuel pump/sender assembly and replace the fuel level sensor if it reads no resistance change when float moves.
When to See a Professional Mechanic
Not all fault codes are safe to DIY
Code P1353 is a moderate fault. You can generally drive to a workshop, but avoid long trips or high-load driving (motorway, uphill towing) until it is diagnosed. If the code keeps returning after clearing, or if you notice the symptoms listed above worsening, do not delay professional diagnosis. Many moderate codes have multiple possible root causes — a mechanic with live OBD data can identify the exact fault more efficiently than part-by-part trial and error.
Safety note: OBD-II codes identify the system or circuit where a fault was detected — they do not always identify the exact failed component. A professional mechanic using live sensor data will diagnose the root cause more accurately than replacing parts based on the code alone.
How to Clear Code P1353
What happens after you fix the fault
Once the fault is repaired, P1353 can be cleared using any OBD-II scanner. Connect the scanner, navigate to "Clear Codes" or "Erase DTCs," and confirm. The check engine light turns off immediately.
The code will return if the root cause was not actually fixed. The ECM re-detects the fault within 1–3 drive cycles and sets the code again.
✅ Safe to Clear When
- Fault has been diagnosed and repaired
- You want to confirm the repair worked
- Code appeared after a sensor was cleaned
⚠️ Do Not Clear When
- Preparing for an emissions/PUC test
- Root cause is still undiagnosed
- Check engine light is flashing
Emissions test note: Clearing codes resets OBD readiness monitors. Most vehicles need 50–100 km of mixed driving before monitors complete. Do not clear codes immediately before an emissions or PUC inspection.