Vehicle Platform: NEXON, X4, Q5, TIGOR_MCE ECU Name: PEPS DTC Troubleshooting Data Version: 1.8 Date: 28 Feb 2023 Author: Rajasekhara Reddy Page: 399 of 407 Copyright © TATA MOTORS Ltd. This document must not be used in any way, such as copying and redistributing to third parties, without the consent of author. Fault Detection Condition If the inter-message RX time period exceeds 25500-ms the FDC counter shall automatically increment to 0x01 and report test failed if no message is received PEPS shall monitor RemoteEngAcCmd signal. Normal Operating Condition 1. IGN ON (Normal communication) Probable Trouble Area CAN fault Healing Condition For FDC decrementation to occur the ECU shall monitor for 1000-ms all received messages, Only when all messages are received within the configurable time (1000-ms) shall the FDC counter decrement to 80 (-128 decimal). The frequency at which the checks occur will depend upon the ECU RX frame rate PEPS shall monitor RemoteEngAcCmd signal. Note: Please contact to Tata Motors customer support center. Table 67:- U133A- 08 overview details Component Details:- 3. PEPS ECU. 4. Telematics ECU. Preliminary Checks:- 3. Check Battery Voltage (9V-16V) 4. Check Software and hardware version number of the Telematics and PEPS. Troubleshooting:- DTC’s confirmation:- After rectification, ensure the following points by using TML diagnostic tool before handing over to customer. a) DTC U133A – 08 is not logged at OFF/ACC/IGNON/CRANK/Run. Circuit Schematic Diagram:- NA
RkJQdWJsaXNoZXIy MTIwNTUz