BAFX OBD2 Not Showing Fault Codes? Troubleshooting Guide

Are you experiencing issues with your BAFX OBD2 scanner not displaying fault codes, particularly on newer vehicles? Many users find themselves in this frustrating situation, where their scanner connects to the car but fails to retrieve diagnostic trouble codes (DTCs). This can be especially perplexing when the scanner works perfectly on older vehicles. Let’s explore why your BAFX OBD2 scanner might not be showing fault codes and how to troubleshoot this problem.

One of the most common reasons for this issue is CAN bus incompatibility. Around 2008-2011, many car manufacturers, including Honda, transitioned to the Controller Area Network (CAN bus) protocol for OBD2 communication. Older OBD2 scanners, like your previous MaxiScan MS300 or potentially older versions of BAFX scanners, might not be fully compatible with this newer CAN bus system. While they might establish a basic connection, they can fail to properly communicate with the car’s Engine Control Unit (ECU) to retrieve fault codes.

The original poster mentioned their locksmith successfully used the OBD2 port, which confirms the port itself is likely functional. This points away from a malfunctioning OBD2 port as the primary culprit and strengthens the likelihood of a communication protocol issue. Similarly, the fact that your BAFX scanner works on your wife’s 2009 CRV, but not your 2011 EX, further suggests a change in protocol around this model year.

To resolve this, the most effective solution is to ensure your OBD2 scanner is CAN bus compliant. Newer scanners are specifically designed to work with CAN bus systems and can properly read and display fault codes from vehicles using this protocol. When purchasing a new OBD2 scanner, always check the specifications to confirm CAN bus compatibility to avoid similar issues. Upgrading to a CAN bus compatible scanner should allow you to effectively diagnose your 2011 Honda EX and access the fault codes you need.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *