In-Ve
POWERTRAIN CONTROL SOFTWAREInternational Standards Organization (ISO) 14229 Diagnostic Trouble Code (DTC) Descriptions
One of the fundamental criteria for entering RPM control is an indication of closed throttle. Throttle mode is always calculated to the lowest learned throttle position (TP) sensor voltage seen since engine start. This lowest learned value is called ratch, since the software acts like a one-way ratch. The ratch value is displayed as the TPREL PID. The ratch value is relearned after every engine start. Ratch learns the lowest, steady TP sensor voltage seen after the engine starts. In some cases, ratch can learn higher values of throttle position. The time to learn the higher values is significantly longer than the time to learn the lower values. The brakes must also be applied to learn the higher values.
All PCM functions are done using this ratch voltage, including idle speed control. The PCM goes into closed throttle mode when the TP sensor voltage is at the ratch value. An increase in TP sensor voltage, normally less than 0.05 volts, puts the PCM in part throttle mode. Throttle mode can be viewed by looking at the TP MODE PID. With the throttle closed, the PID must read C/T (closed throttle). Slightly corrupt values of ratch can prevent the PCM from entering closed throttle mode. An incorrect part throttle indication at idle prevents entry into closed throttle RPM control, and could result in a high idle. Ratch can be corrupted by a throttle position sensor or a circuit that drops out or is noisy, or by loose/worn throttle plates that close tight during a deceleration and spring back at a normal engine vacuum.
International Standards Organization (ISO) 14229 Diagnostic Trouble Code (DTC) Descriptions
The ISO 14229 is a global, diagnostic communication standard. The ISO 14229 is a set of standard diagnostic messages that can be used to diagnose any vehicle module in use and at the assembly plant. The ISO 14229 is similar to the Society of Automotive Engineers (SAE) J2190 diagnostic communication standard that was used by all Original Equipment Manufacturers (OEMs) for previous communication protocols, like J1850 standard corporate protocol (SCP).
The ISO 14229 changes the way PIDs, DTCs, and output state control (OSC) is processed internally in the PCM and in the scan tool software. Most of the changes are to make data transfer between electronic modules more efficient, and the amount and type of information that is available for each DTC. This information may be helpful in diagnosing driveability concerns.
DTC Structure
Like all digital signals, DTCs are sent to the scan tool as a series of 1s and 0s. Each DTC is made up of 2 data bytes, each consisting of 8 bits that can be set to 1 or 0. In order to display the DTCs in the conventional format, the data is decoded by the scan tool to display each set of 4 bits as a hexadecimal number (0 to F). For example, P0420 Catalyst System Efficiency Below Threshold (Bank 1).
The table below shows how to decode the bits into hex digits.
The first 4 bits of a DTC do not convert directly into hex digits. The conversion into different types of DTCs (P, B, C and U) is defined by SAE J2012. This standard contains DTC definitions and formats.
ISO 14229 sends 2 additional bytes of information with each DTC, a failure type byte and a status byte.
All ISO 14229 DTCs are 4 bytes long instead of 3 or 2 bytes long. Additionally, the status byte for ISO 14229 DTCs is defined differently than the status byte for previous applications with 3 byte DTCs.
Failure Type Byte
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.
For example, P0110:1C-AF means intake air temperature (IAT) sensor circuit voltage out of range. The base DTC, P0110, means IAT sensor circuit, while the failure type byte 1C means circuit voltage out of range. This DTC structure was designed to allow manufacturers to more precisely identify different kinds of faults without always having to define new DTC numbers.
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 2 byte DTCs for generic scan tool communications. Additionally, the OBD II regulations require the 2 byte DTCs to be very specific, so there is no additional information that the failure type byte could provide.
A list of failure type bytes is defined by SAE J2012 but is not described here because the PCM does not use the failure type byte.
Status Byte
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 8 bits in the status byte has a precise meaning that is defined in ISO 14229.
The protocol is that bit 7 is the most significant and left most bit, while bit 0 is the least significant and right most bit.
DTC Status Bit Definitions
Refer to the following status bit descriptions:
Bit 7
- 0 - The ECU is not requesting warning indicator to be active
- 1 - The ECU is requesting warning indicator to be active
Bit 6
- 0 - The DTC test completed this monitoring cycle
- 1 - The DTC test has not completed this monitoring cycle
Bit 5
- 0 - The DTC test has not failed since last code clear
- 1 - The DTC test failed at least once since last code clear
Bit 4
- 0 - The DTC test completed since the last code clear
- 1 - The DTC test has not completed since the last code clear
Bit 3
- 0 - The DTC is not confirmed at the time of the request
- 1 - The DTC is confirmed at the time of the request
Bit 2
- 0 - The DTC test completed and was not failed on the current or previous monitoring cycle
- 1 - The DTC test failed on the current or previous monitoring cycle
Bit 1
- 0 - The DTC test has not failed on the current monitoring cycle
- 1 - The DTC test failed on the current monitoring cycle
Bit 0
- 0 - The DTC is not failed at the time of request
- 1 - The DTC is failed at the time of request
For DTCs that illuminate the MIL, a confirmed DTC means the PCM has stored a DTC and has illuminated the MIL. If the fault has corrected itself, the MIL may no longer be illuminated but the DTC still shows a confirmed status for 40 warm up cycles at which time the DTC is erased.
For DTCs that do not illuminate the MIL, a confirmed DTC means the PCM has stored a DTC. If the fault has corrected itself, the DTC still shows a confirmed status for 40 warm up cycles at which time the DTC is erased.
To determine if a test has completed and passed, such as after a repair, information can be combined from 2 bits as follows:
If bit 6 is 0 (the DTC test completed this monitoring cycle), and bit 1 is 0 (the DTC test has not failed on the current monitoring cycle), then the DTC has been evaluated at least once this drive cycle and was a pass.
If bit 6 is 0 (the DTC test completed this monitoring cycle) and bit 0 is 0 (the DTC test is not failed at the time of request), then the most recent test result for that DTC was a pass.
The status byte bits can be decoded as a 2 digit hexadecimal number, and displayed as the last 2 digits of the DTC, for example for DTC P0110:1C-AF, AF represents the status byte info.
Multiplexing
The increased number of modules on the vehicle necessitates a more efficient method of communication. Multiplexing is a method of sending 2 or more signals simultaneously over a single circuit. In an automotive application, multiplexing is used to allow 2 or more electronic modules to communicate simultaneously over a single media. Typically this media is a twisted pair of wires. The information or messages that can be communicated on these wires consists of commands, status or data. The advantage of using multiplexing is to reduce the weight of the vehicle by reducing the number of redundant components and electrical wiring.
Multiplexing Implementation
Currently Ford Motor Company uses CAN communication language protocol to communicate with the PCM.
For additional information about the module communications network, refer to the Information Bus, Module Communications Network for Description and Operation.
Permanent Diagnostic Trouble Code (DTC)
The software stores a permanent DTC in non-volatile random access memory (NVRAM) whenever a DTC is set and the MIL has been illuminated. Permanent DTCs can only be cleared by the module strategy itself. After a permanent DTC is stored, 3 consecutive test passed monitoring cycles must complete before the permanent DTC can be erased. At that time, both the permanent DTC is erased and the MIL is extinguished. The PCM clears permanent DTCs after one monitoring cycle if a request to clear DTCs is sent by the scan tool, and the test subsequently runs and passes (test must continue to pass for the entire driving cycle for continuous monitors) and a Permanent DTC Driving Cycle has been completed. A Permanent DTC Driving Cycle requires a total of 10 minutes of engine run time, consisting of 5 minutes of vehicle operation above 40 km/h (25 mph) and 30 continuous seconds of vehicle operation at idle. After clearing DTCs, running the OBD Drive Cycle ensures that all monitors complete, the Permanent DTC Driving Cycle completes, inspection/maintenance (I/M) readiness codes are set to a ready status and any permanent DTCs are erased. A permanent DTC cannot be erased by clearing the KAM. The intended use of the permanent DTC is to prevent vehicles from passing an in-use inspection simply by disconnecting the battery or clearing the DTCs with a scan tool prior to the inspection. The presence of permanent DTCs at an inspection without the MIL illuminated is an indication that a correct repair was not verified by the on board monitoring system.
Vehicle Speed Limiter
The PCM disables some or all of the fuel injectors whenever a vehicle over speed condition is detected. The purpose of the vehicle speed limiter is to prevent damage to the powertrain. Once the driver reduces the excessive vehicle speed, the engine returns to the normal operating mode. No repair is required. However, the technician should clear the DTCs and inform the customer of the reason for the DTC.
Excessive wheel slippage may be caused by sand, gravel, rain, mud, snow, ice, or excessive and sudden increase in RPM while in NEUTRAL or while driving.