Okay but now I'm curious about the info posted here. Can we or can we not see the code by simply powering the car on and holding down the left-hand OK button on the steering wheel, then scroll up or down through the screens to the DTC codes page? And, if so, what does the code tell us?
IOW, if the first part of this is true, that we can see the code, does the code itself actually mean anything (to us, of course -- I know it means something to Ford). If I get a code like 007 is there somewhere I can look it up to see that there is a secret agent hidden in the trunk of my car (oops, excuse me, I don't have a trunk -- perhaps he's handing onto the under carriage)? Or are we no better off having a code because the numbers won't mean anything to us and we'd have to take it to the dealer anyway?
So I guess there are two questions there -- anyone have any answers?
Yes, you can see the codes when powering on the car in ETM. I've been trying to find a list of codes since I learned of ETM displaying DTCs. I have yet to find a listing of DTCs for Ford's consolidated diagnostic standards.
Here's what I found from Ford.
1) Ford consolidated diagnostic standards by: "Adoption of the ISO 14229-1 diagnostic standard for all ECUs on CAN."
2) ISO 14229 sends two additional bytes of information with each DTC, a failure type byte and a status byte.
3) All ISO 14229 DTCs are four bytes long instead of three or two bytes long. Additionally, the status byte for ISO 14229 DTCs is defined differently than the status byte for previous applications with three byte DTCs.
4) The failure type byte is designed to describe the specific failure associated with the basic DTC. For example, a failure type byte of 1C means circuit voltage out of range, 73 means actuator stuck closed. When combined with a basic component DTC, it allows one basic DTC to describe many types of failures.
5) The PCM does not use failure type bytes and always sends a failure type byte of 00 (no sub type information). This is because OBD-II regulations require manufacturers to use two byte DTCs for generic scan tool communications. Additionally, the OBD-II regulations require the two byte DTCs to be very specific, so there is no additional information that the failure type byte could provide.
6) The status byte is designed to provide additional information about the DTC, such as when the DTC failed, when the DTC was last evaluated, and if any warning indication has been requested. Each of the eight bits in the status byte has a precise meaning that is defined in ISO 14229.
7) Here's what Ford says about ETM
- DTC HIST CURR
- xxxxxx x x
- xxxxxx x
Displays all of the Diagnostic Trouble Codes (DTCs) set (history and current Diagnostic Trouble Codes [DTCs]). An X in the HIST or CURR column means the DTC is active. Three Diagnostic Trouble Codes (DTCs) display on each screen. If more Diagnostic Trouble Codes (DTCs) are present, there will be additional screens listing them. If there are no Diagnostic Trouble Codes (DTCs) in history or current, the display will only be the title row.
Edited by Plus 3 Golfer, 24 December 2014 - 11:19 AM.