Introduction
Is your BMW showing “Not Ready” OBD2 readiness monitors? This article guides you through using INPA software to potentially force OBD2 readiness and reset emission monitors, specifically focusing on the MSV80 DME found in certain BMW models. We’ll outline a step-by-step process to diagnose and address potential issues hindering monitor readiness. Understanding the status of these monitors is crucial for passing emissions tests.
Understanding OBD2 Readiness Monitors and INPA
OBD2 readiness monitors track the performance of various emission-related systems in your vehicle. A “Not Ready” status indicates a specific monitor hasn’t completed its diagnostic cycle. INPA, a diagnostic software for BMWs, allows deeper access to these systems than a generic OBD2 scanner. While forcing readiness isn’t always possible, addressing underlying issues is key.
Troubleshooting “Not Ready” Monitors with INPA
INPA Readiness Monitor Screen
If your INPA screen displays multiple “No” entries in the readiness monitor section, as shown above, follow these diagnostic steps:
1. Comprehensive Fault Code Scan
Begin by scanning ALL modules for fault codes using INPA’s Functional Jobs. This provides a holistic view of potential issues affecting monitor readiness.
2. DME (MSV80) Fault Code Check
Specifically target the DME (MSV80 for this example) and read its fault memory. Document any codes found, including fault details and freeze frame data. This information is critical for pinpoint diagnosis.
3. Clearing Fault Codes
After meticulously documenting all fault codes, clear them within the DME using the proper INPA procedure. This crucial step often allows the monitors to reset. Remember, clearing codes without documentation makes diagnosing recurring issues difficult.
4. Ignition Cycle and Monitor Status Check
Turn the ignition OFF, wait approximately 10 seconds, and turn it back ON. Recheck the readiness monitor status. Expect them to show “Not Ready” immediately after clearing fault codes.
5. Drive Cycle and Re-Evaluation
Perform the appropriate drive cycle for your specific BMW model. This allows the monitors to run their diagnostic tests. After the drive cycle, re-check both fault codes and monitor status using INPA. Avoid clearing any new codes at this point, as it will reset the monitors back to “Not Ready.”
Addressing Underlying Issues
(Image placeholder – insert an image showcasing an INPA fault code screen if available in the original post)
If monitors remain “Not Ready” after these steps, deeper diagnosis is required. Refer to the saved fault codes and freeze frame data. Common culprits include issues with:
- Tank Vent System: Problems with the evaporative emissions system can prevent readiness.
- Oxygen Sensors: Faulty O2 sensors or their heaters hinder accurate emissions monitoring.
- VANOS System: Issues with the Variable Valve Timing system can affect emissions and readiness.
Conclusion
Using INPA to diagnose and address the root cause of “Not Ready” OBD2 monitors is crucial. While forcing readiness isn’t a guaranteed solution, systematically troubleshooting with INPA increases your chances of resolving the issue and passing emissions tests. Remember to consult your vehicle’s specific repair information for detailed drive cycle procedures and fault code definitions. This systematic approach empowers you to take control of your BMW’s emissions system and ensure its optimal performance.
