The Australian-made AU Falcon is a popular vehicle, and like many modern cars, it features an OBD2 connector. However, owners and mechanics alike have discovered that connecting a standard OBD2 scan tool to an AU Falcon doesn’t always yield the expected results. This raises a crucial question: Does the AU Falcon truly adhere to the standard OBD2 protocol, or is there more to the story? Let’s delve into the complexities surrounding the AU Falcon’s diagnostic system.
It appears that despite having the physical OBD2 connector, the AU Falcon, particularly models from the late 1990s and early 2000s, might not fully implement the standard OBD2 protocols we see in many other vehicles. Forum discussions amongst automotive enthusiasts and professionals suggest that Ford might have utilized the OBD2 connector for a different, possibly proprietary, diagnostic system, or perhaps an earlier OBD protocol like OBD1 or EEC-V.
The pinout configuration of the AU Falcon’s OBD2 connector, as discussed in online forums, hints at a non-standard implementation. Some pins are assigned to functions that deviate from the typical OBD2 setup. For instance, there’s mention of pins for “Bus +ve,” “Bus -ve,” “ISO Signal tx/rx,” and even “eeprom” and “programming voltage,” suggesting a system capable of more than just standard OBD2 diagnostics, possibly including ECU programming or deeper system access.
This divergence from the standard OBD2 protocol means that generic OBD2 scan tools might struggle to communicate effectively with the AU Falcon’s engine control unit (ECU). While some basic diagnostic functions might be accessible, deeper diagnostics, live data streaming, and comprehensive fault code reading could be limited or unavailable with a standard OBD2 scanner.
Discussions also point towards the “Siemens K Line protocol” as a possible communication method used in AU Falcons and other vehicles assembled in Australia and Thailand around that era. This protocol is different from the standard OBD2 protocols like CAN (Controller Area Network), PWM (Pulse Width Modulation), and VPW (Variable Pulse Width Modulation) commonly used in OBD2 systems. The mention of the Ford NGS (New Generation Star) tester, a dealership-level diagnostic tool, further suggests that specialized equipment might be necessary for comprehensive diagnostics on the AU Falcon.
For owners and technicians working on AU Falcons, understanding this potential difference in diagnostic protocols is crucial. If you’re facing difficulties connecting to an AU Falcon with a generic OBD2 scanner, it’s likely not a fault with your scan tool, but rather a characteristic of the vehicle’s diagnostic system. Exploring Ford-specific diagnostic tools or scanners compatible with Siemens K Line protocol might be necessary to unlock the full diagnostic potential of the AU Falcon and effectively troubleshoot any issues. Further research into Ford’s diagnostic protocols of that era and consulting with experienced Ford technicians could provide more clarity and effective solutions for diagnosing AU Falcon vehicles.
