Engine management fault codes such as P0101, P0172 and P1170 are not a final diagnosis, but the starting point for a targeted diagnostic process in which sensors, wiring and actuators are systematically checked. The best repairs do not come from replacing parts based on a code alone, but from using live data, oscilloscope measurements and a thorough inspection of connector plugs and terminals. Want to know how to tackle these fault codes effectively?
What engine management fault codes mean
A fault code indicates that the engine control unit has registered a deviation in a sensor, actuator or control circuit. The ECU stores a fault when measured values are illogical, cables short-circuit or connections between sensor and computer are disrupted. With popular models such as the Volvo XC70, certain fault codes occur regularly, and a systematic diagnostic approach makes the difference between a quick fix and unnecessary replacements.
However, the code does not automatically indicate which component is broken. The same fault code can have different causes: a defective component, a poor connector, a broken wire or a problem in a controlled component. That is why reading live data and carrying out electrical measurements is essential to determine the real cause.
Workshops use a fixed approach: first read out and note all fault codes, then check live data and symptoms, and only then carry out repairs. This methodical way of working prevents you from spending money on parts that do not solve the real problem.
How to identify air–fuel mixture problems
Fault codes P0172 and P0175 point to a mixture that is too rich, meaning the engine is receiving more fuel than it needs. This can lead to black exhaust smoke, higher consumption and poor engine performance. The causes are often defective lambda sensors, contaminated mass air flow sensors or leaking injectors.
During diagnosis you first check the live data of the lambda sensors. These sensors measure the oxygen content in the exhaust and ensure that the engine control unit can correctly adjust the fuel supply. When the sensor gives an incorrect signal, the ECU tries to compensate by adding more or less fuel. This leads to a disturbed air–fuel mixture.
An oscilloscope measurement shows the signal from the lambda sensor in detail. A healthy sensor switches quickly between rich and lean, whereas a worn sensor reacts slowly or gets stuck at one value. The mass air flow sensor also plays an important role: a contaminated or defective sensor provides incorrect information about the amount of incoming air, causing the ECU to meter the wrong amount of fuel.
In addition, when dealing with mixture problems you should check:
- The condition and operation of the lambda sensors using live data and an oscilloscope
- The mass air flow sensor for contamination, damage or incorrect measured values
- Injectors for leakage or incorrect metering
- The fuel pressure with a pressure gauge to see whether it is within specification
- Vacuum leaks in the intake system that allow unmetered air to enter
Fault code P0101 and the mass air flow sensor
P0101 indicates a problem with the signal from the mass air flow sensor. This sensor measures the amount of air entering the engine and passes this information to the engine control unit. When the signal deviates from what the ECU expects based on other parameters such as throttle position and engine speed, this code appears.
The cause may be a contaminated sensor, a defective mass air flow meter or an air leak after the sensor. A damaged connector or damaged wiring can also trigger this fault code. During diagnosis you look at the live data: the mass air flow sensor must show a value that is logical at idle. This value should rise smoothly when you accelerate.
Cleaning the sensor solves the problem in some cases, but with real defects replacement is necessary. When checking, also pay attention to the air side of the intake system: splits in hoses or a poorly sealing air filter disturb the measurement.
Lambda sensor fault codes P1170 and P1173
These specific fault codes point to malfunctions in the control system of the lambda sensors. P1170 and P1173 indicate that the engine control unit cannot adjust the fuel supply correctly within the expected limits. This often occurs when lambda sensors are aged, contaminated or when there are problems with the heating of the sensor.
Lambda sensors need a heating element to quickly reach operating temperature. When this heater does not work, it takes longer before the sensor provides reliable measurements. The ECU detects this and stores a fault code. A poor earth connection or corrosion in the plug can also cause these fault codes.
Diagnosis is carried out by:
- Reading the live data of both lambda sensors
- Checking with a multimeter whether the heater voltage is present
- Measuring the signal with an oscilloscope to assess the response time
- Visually inspecting the plug connections for corrosion and damage
- Testing whether the earth connection has good contact
‘ A sensor can function perfectly, but because of a poor terminal contact the signal does not get through properly. ’
What poor terminal contacts cause
Poor terminal contacts and plug connections are a very common cause of engine management fault codes. Corrosion, moisture and vibrations cause electrical connections to lose contact or build up resistance. This leads to voltage loss, interruptions or short circuits that the engine control unit interprets as a defect.
A sensor can function perfectly, but because of a poor terminal contact the signal does not get through properly. The ECU then sees an illogical value or no signal at all and stores a fault code. The same applies to actuators: when the control signal does not arrive properly due to a terminal problem, the component will not operate as intended.
During diagnosis it is therefore important not only to test the component itself, but also the entire electrical chain. Check connectors for corrosion, gently flex cables to see whether contact problems occur and measure the voltage at several points in the circuit. The engine earth connections are also vulnerable: a poor earth causes all kinds of strange faults.
Practical step-by-step diagnostic approach
An effective diagnosis follows a fixed sequence. Start by reading all fault codes via the OBD connector and note them down before you erase anything. Then look at the freeze-frame data: these show under which conditions the fault occurred, such as engine temperature, speed and load.
Next, check the live data while the engine is running. See whether values change logically: temperature sensors should rise as the engine warms up, the mass air flow sensor should respond to throttle movements and lambda sensors should switch between rich and lean. Deviations in this data point you towards the cause.
Use a multimeter to check voltages, earth connections and continuity. A wiring diagram helps you understand which pins in a plug have which function. Where possible, carry out an actuator test via the diagnostic scanner. This allows you to activate components such as EGR valves or pump relays. You can then see immediately whether they respond.
Only erase fault codes after repair and take a test drive to check whether the fault reappears. If the code returns immediately, the cause has not yet been resolved. If the code does not return, the repair was successful.
Common underlying causes of fault codes
In practice, certain causes keep recurring with engine management fault codes. A defective sensor is logical, but just as often the fault lies in the wiring or connectors. Cables rubbing against sharp edges, connectors that let in moisture or earth connections that rust cause just as many faults as broken components.
Contamination also plays a role. EGR valves that no longer move freely due to carbon build-up, contaminated mass air flow sensors or inlet valves with heavy deposits disrupt the operation of the engine management system. Regular maintenance prevents many of these problems.
In addition, incorrect repairs or non-original parts can cause fault codes. A replacement part that has slightly different specifications can confuse the ECU. Software updates also sometimes resolve fault codes that arise from programming errors in the engine control unit.
‘ A flashing warning light points to severe misfires that can damage the catalytic converter. ’
What you can check yourself straight away
When the engine management warning light comes on, always first check the oil level and coolant level. Low levels quickly lead to additional damage. If the light is on constantly without severe symptoms, you can usually continue driving gently, but have the car read out at a workshop as soon as possible.
If the warning light flashes, pull over safely as soon as you can. A flashing light points to severe misfires that can damage the catalytic converter. Note when the fault occurs: on a cold start, after refuelling, in rain or under load. This context helps the technician with the diagnosis.
If you have your own OBD scanner, read out the fault codes and look up what they mean. This gives you insight into the problem and helps you assess whether it is safe to continue driving. Do not erase the codes straight away: the workshop needs the original fault information to make a proper diagnosis.
Repair and next steps
After diagnosis comes repair. A defective sensor is replaced when the measured values are demonstrably incorrect and the wiring is in order. Connectors, earth points or wiring looms are repaired in the event of voltage loss or short circuits. Contaminated components such as EGR valves are cleaned or replaced.
After repair the workshop will often carry out an adaptation or reset. The engine control unit has to relearn what the normal values of the new sensors are. A test drive will show whether the fault has been permanently resolved. If the fault code returns, further investigation into underlying causes is necessary.
Cheap “solutions” that only erase the fault code without tackling the cause do not solve anything. They hide the problem temporarily, but the fault returns and in the meantime may cause further damage.
On the Carnews website you will find much more information about engine problems, maintenance tips and technical explanations for various car makes and models. Discover what is going on with your car and how to spot and prevent problems at an early stage.
Frequently asked questions
Common engine management fault codes often point to problems with sensors (such as the mass air flow sensor or lambda sensor), actuators (such as the EGR valve or throttle body) or the wiring and plug connections in between. They do not automatically mean that the named component is broken, but that the ECU has seen an illogical or out-of-spec value. In daily driving you usually notice this as loss of power, rough running, increased fuel consumption or the car going into limp-home mode. A constantly illuminated warning light often still allows gentle driving with symptoms, whereas a flashing light may point to serious misfires and makes it necessary to stop immediately to prevent engine damage.
Connect the OBD-II scanner, switch on the ignition and read out all stored fault codes and freeze-frame data, and write these down before you erase anything. Then consult the descriptions of the codes (for example in the manual or online) and check whether the reported sensors/components make sense in relation to the car’s symptoms. If your scanner can do this, look at the live data (such as coolant temperature, MAP/MAF value, lambda signal) and check whether these values change logically with engine speed and load. Only after you have addressed any visible problems (connectors, cables, leaks) should you erase the codes and take a test drive to check whether the fault codes return.
For hobby use, simple ELM327-based OBD-II scanners (for example a reliable Bluetooth/Wi-Fi dongle with a good app such as Car Scanner or Torque Pro) or an entry-level handheld device (Autel, Launch, iCarsoft) are usually sufficient. When buying, check that your car make/fuel type is supported, whether it can read not only engine management but also ABS/airbag/transmission, and whether live data and fault code descriptions are available. Avoid the very cheapest, no-name ELM327 clones, as these are often unstable or do not support all protocols properly. Also check whether the app/software is up to date and has good documentation/user reviews.
Professional help is necessary when the engine management light keeps burning or flashes, the car goes into limp mode, there is noticeable loss of power or rough running, or when you cannot find the cause yourself with scanning and basic checks (fluids, connectors). If fault codes return after being erased, a specialist diagnosis is also recommended to prevent consequential damage. For reading fault codes and a basic diagnosis only, costs are often around €40–€100. For actual repairs (replacing a sensor/actuator, repairing wiring, cleaning and resetting) costs can range from about €150 to well over €600, depending on the component and the labour time required.
Prevent engine management fault codes by carrying out regular maintenance: change oil and filters on time, use the correct spark plugs, fill up with good-quality fuel and have connectors/cables checked for corrosion or damage. Have the intake tract and EGR/throttle body cleaned periodically if your engine is prone to build-up, and do not ignore early signs such as vibrations, smoke or rough running. Adjust your driving style by allowing the engine to warm up gently, not making only short trips, and now and then taking a longer journey at motorway speed so that the engine and exhaust system can burn off deposits. Avoid overloading (very low revs with a lot of throttle, heavy trailer weight) and, if a warning light comes on, have the car scanned in good time to prevent further damage.
