It’s frustrating when your OBD2 reader refuses to communicate with your car’s computer. You’ve got a BAFX OBD2 reader, a trusty app like Torque, and a desire to diagnose that pesky check engine light on your ’99 Miata, but you’re met with a “No response from vehicle ECU” message. You’re not alone, and while the original forum post highlights a user’s specific issue, let’s expand on this and explore why your BAFX OBD2 reader might be failing to connect, and how this relates to the broader issue of not being able to reset codes.
One of the first things to consider is the OBD2 port location. While the user in the original post correctly identified a port near the fuse box, it’s worth double-checking. For the ’99 Miata (NB generation), the OBD2 port is typically located in the driver’s side footwell, often above the pedals or near the fuse box area. It might be slightly hidden, so take a careful look with a flashlight. Ensure you are plugging the BAFX reader firmly into the 16-pin OBD2 port.
Next, let’s think about compatibility. While OBD2 is a standard, some older vehicles, or specific models, can be a bit finicky. The user mentioned their BAFX reader working on a ’98 Civic, suggesting the reader itself is likely functional. However, the ’99 Miata might have specific protocol requirements or sensitivities. While the BAFX reader is generally well-regarded, it’s worth verifying if there are any known compatibility issues with early NB Miatas. Sometimes, trying a different OBD2 app can make a difference. While Torque is popular, apps like Car Gauge Lite (which the user also tried) or others might handle the connection differently.
The error message “No response from vehicle ECU” is key. It indicates a failure to establish communication with the car’s Engine Control Unit (ECU). This is a fundamental problem that must be resolved before you can even think about resetting codes. You cannot reset any codes if your OBD2 reader cannot connect to the ECU in the first place. The ability to reset codes is entirely dependent on a successful connection.
Here are some troubleshooting steps to consider when your BAFX OBD2 reader is not connecting and you’re facing the inability to reset codes:
- Verify OBD2 Port: Double, triple-check you are using the correct OBD2 port in your Miata. Ensure it’s clean and free of debris.
- Ignition and Engine: Try connecting with just the ignition ON (car not started) and also with the engine running. Sometimes, certain protocols or functions require the engine to be running.
- BAFX Reader Power: Confirm the red light on the BAFX reader illuminates when plugged in, indicating it’s receiving power from the OBD2 port. If no light, there might be an issue with the port’s power supply or the reader itself.
- Bluetooth Pairing: Ensure your Android device is properly paired with the BAFX reader via Bluetooth. Double-check the pairing code (usually 1234 or 0000).
- App Settings: Within the Torque app (or your chosen app), explore the connection settings. While “Auto” protocol selection usually works, you might try manually selecting a protocol if you know the ’99 Miata’s protocol (though this is generally not necessary for OBD2 compliant vehicles).
- Reader Reset/Restart: Try unplugging and replugging the BAFX reader, and restarting your Android device.
- Test on Another OBD2 Car (If Possible): Since the user tested on a Civic, this is good. If you have access to another OBD2 compliant car, try the BAFX reader on it again to re-confirm the reader’s functionality.
- Consider a Different Reader: While the BAFX is generally reliable, it’s possible there’s an incompatibility issue with your specific Miata. If all else fails, researching OBD2 readers specifically reported to work well with NB Miatas might be necessary.
In conclusion, when your BAFX OBD2 reader fails to connect to your ’99 Miata, and you’re facing the frustration of not being able to even begin diagnosing or resetting codes, systematic troubleshooting is key. Start with the basics – port location and reader power – and progressively move to compatibility considerations and app settings. While the inability to reset codes is the ultimate outcome of a connection failure, focusing on resolving the communication issue first is the crucial step.
