Navigating the world of automotive diagnostics can be complex, especially when dealing with vehicles from different regions and eras. For owners and enthusiasts of the Australian Ford AU Falcon, a common question arises: where is the OBD2 port location and is it truly OBD2 compliant? This query is not just about physically finding the port, but understanding the diagnostic protocol it uses. Let’s delve into the specifics of the AU Falcon’s diagnostic system and clarify the confusion surrounding its OBD2 connectivity.
The OBD2 Connector: Appearance vs. Functionality
The Ford AU Falcon, produced from 1998 to 2002, does indeed feature the familiar 16-pin OBD2 (On-Board Diagnostics II) connector. At first glance, this might lead one to assume straightforward compatibility with standard OBD2 scanners. However, the reality is more nuanced. While the physical connector is OBD2-style, the underlying communication protocol may not fully adhere to the OBD2 standards that are commonly associated with vehicles in North America and other markets.
Early discussions among AU Falcon owners, as seen in online forums, highlight this very issue. Users attempting to connect standard OBD2 scan tools often find themselves unable to establish a connection or retrieve diagnostic data. This leads to the crucial question: if it looks like OBD2, but doesn’t communicate like OBD2, then what is it?
Unraveling the Diagnostic Protocol: Beyond Standard OBD2
The AU Falcon’s diagnostic system is believed to operate on a protocol closer to OBD1 or a Ford proprietary system, possibly utilizing the EEC-V (Electronic Engine Control V) engine management system. Some experts suggest it uses the Siemens K-Line protocol, which was common in Australian and Thai-assembled vehicles before the Ford BA Falcon. This K-Line protocol is not the standard suite of protocols (like CAN, PWM, VPW) typically expected with OBD2 in many parts of the world.
The pinout information shared by AU Falcon owners further supports this divergence from standard OBD2. The pin assignments, while within the realm of possible OBD2 configurations, suggest a system tailored to Ford’s specific diagnostic approach at the time. Pin 7 being mentioned as an ISO signal pin and pin 13 potentially for EEPROM writing, hints at a system that requires specialized tools beyond generic OBD2 scanners.
Finding the Right Diagnostic Tool for Your AU Falcon
So, if your standard OBD2 scanner is failing to communicate with your AU Falcon, what are your options? The consensus points towards needing a Ford-specific diagnostic tool. The NGS (New Generation Star) tester, mentioned in older forum discussions, is identified as a tool used by Ford dealerships in Australia for EEC-V systems. This suggests that tools designed for EEC-IV and EEC-V systems might be necessary for comprehensive diagnostics on the AU Falcon.
While generic ELM327-based scanners might establish a basic connection, their functionality is often limited. They may not be able to access the full range of diagnostic trouble codes (DTCs) or provide in-depth data logging. For more advanced diagnostics, including writing to the ECU (Engine Control Unit), specialized tools like the NGS or potentially professional-grade scan tools with Ford-specific software are likely required.
Conclusion: Understanding the AU Falcon OBD2 Location and Diagnostics
The Ford AU Falcon presents a unique scenario in automotive diagnostics. While it features an OBD2-style connector located in the standard position under the dashboard on the driver’s side, its communication protocol deviates from typical OBD2 standards. Therefore, when diagnosing an AU Falcon, it’s crucial to understand that while the OBD2 port location is standard, the system may not be standard OBD2 in its communication. Owners and technicians need to be prepared to use Ford-specific diagnostic tools or scanners capable of communicating with EEC-V or K-Line based systems to effectively diagnose and service these vehicles. Using the correct tool ensures accurate readings and avoids misdiagnosis, ultimately saving time and resources in vehicle maintenance.
