Technical Description of OBD-II Trouble Code
The circuit for the Intake Manifold Runner Position Sensor/Switch is located in Bank 2.
What does that signify?
This particular diagnostic trouble code is applicable to fuel injected engines from various manufacturers since 2003. These manufacturers include Ford, Dodge, Toyota, Mercedes, Nissan, and Infiniti. The code primarily focuses on the value provided by the intake manifold flow control valve/position sensor, also known as the IMRC valve/sensor. This component, typically located at one end of the intake manifold, assists the vehicle’s PCM in regulating the amount of air entering the engine at different RPMs. The code specifically pertains to Bank 2, which refers to the bank of cylinders that does not include cylinder number 1. The issue can be either a mechanical or electrical circuit fault, depending on the vehicle manufacturer and fuel system.
The troubleshooting steps may vary depending on the manufacturer, type of fuel system, and the type of intake manifold runner control valve/position sensor (IMRC) and wire colors.
Symptoms
The P2019 engine code may exhibit the following symptoms:
Causes
The common causes for this code to be triggered are:
Diagnostic Steps and Repair Information
It is always advisable to check for technical service bulletins (TSB) specific to your vehicle as a starting point. Your issue may be a known problem with a known solution provided by the manufacturer, which can save you time and money during diagnosis.
First, check if there are any other diagnostic fault codes present. If there are any related to the intake/engine performance system, address them first. Misdiagnosis can occur if this code is diagnosed before thoroughly diagnosing and dismissing any intake/engine performance related system codes. Ensure that there are no intake or exhaust leaks, as an intake or vacuum leak can cause the engine to run lean, while an exhaust leak can give the impression of a lean running engine based on the air fuel ratio/oxygen (AFR/O2) sensor.
Next, locate the IMRC valve/sensor on your specific vehicle and visually inspect the connectors and wiring. Look for any signs of chafing, rubbing, bare wires, burn spots, or melted plastic. Separate the connectors and carefully examine the terminals inside. Check for corrosion, burns, or any unusual green coloration. If necessary, clean the terminals using Electrical Contact cleaner or 91% rubbing alcohol and a light plastic bristle brush. After cleaning, let them air dry and apply dielectric silicone compound to the contact points.
If you have a scan tool, clear the diagnostic trouble codes from memory and check if the code returns. If it does not, the issue was likely related to the connections.
If the code does reappear, you will need to test the voltage signals to and from the IMRC valve/sensor using a scan tool or a digital volt ohm meter (DVOM). With the sensor connected, monitor the IMRC sensor voltage or test the signal wire with the DVOM. As the engine RPM increases, the IMRC sensor signal should change. Refer to the manufacturer’s specifications for the expected voltage at a given RPM.
If the IMRC sensor fails this test, you should verify that the IMRC valve is not binding or sticking inside the intake manifold. Remove the IMRC sensor/actuator and check for any binding or looseness in the plates/valves inside the intake manifold. If necessary, replace the plates/valves, which may require replacing the entire intake manifold. It is recommended to seek professional assistance for this task.
If the IMRC plates/valves turn without any binding or excessive looseness, it indicates the need to replace the IMRC sensor/actuator and retest.
Once again, it is crucial to diagnose any other codes before addressing this one, as issues that trigger other codes can also trigger this code. Additionally, if the problem is not evident after the initial diagnostic steps, consulting an automotive professional for the repair of your vehicle is advisable. Most repairs beyond this point involve removing and replacing the intake manifold to properly resolve this code and the related engine performance issue.
