DEFINITION OF TERMS
| Terms | Definition |
|---|
| Monitor Description | Description of what the power management control ECU (HV CPU) monitors and how to detects malfunctions (monitoring purpose and its details). |
| Related DTCs | A group of diagnostic trouble codes that are output by the power management control ECU (HV CPU) based on the same malfunction detection logic. |
| Typical Enabling Condition | Preconditions that allow the power management control ECU (HV CPU) to detect malfunctions. With all preconditions satisfied, the power management control ECU (HV CPU) sets DTCs when the monitored value(s) exceeds malfunction threshold(s). |
| Sequence of Operation | Order of monitor priority, applied if multiple sensors and components are involved in a single malfunction detection process. Each sensor and component are monitored in turn and subsequent items are not monitored until the previous detection operation completes. |
| Required Sensor/Components | Sensors and components used by the power management control ECU (HV CPU) to detect each malfunction. |
| Frequency of Operation | Number of times the power management control ECU (HV CPU) checks for each malfunction during each driving cycle. "Once per driving cycle" means that the power management control ECU (HV CPU) only checks for malfunctions once during a single driving cycle. "Continuous" means that the power management control ECU (HV CPU) checks for malfunctions whenever enabling conditions are met. |
| Duration | Minimum time for which the power management control ECU (HV CPU) must detect continuous deviation in monitored value(s) in order to set a DTC. Timing begins when typical enabling conditions are met. |
| Malfunction Thresholds | Value beyond which the power management control ECU (HV CPU) determines malfunctions exist and sets DTCs. |
| MIL Operation | Timing of MIL illumination after a malfunction is detected. "Immediate" means that the power management control ECU (HV CPU) illuminates the MIL as soon as a malfunction is detected. "2 driving cycles" means that the power management control ECU (HV CPU) illuminates the MIL if the same malfunction is detected again during the next driving cycle. |
Scheme 345
Scheme 346
Scheme 347
Scheme 348
Scheme 348: SYSTEM DIAGRAM
Scheme 349
Scheme 350
Scheme 351
Scheme 351: SYSTEM DESCRIPTION
- BATTERY SMART UNIT CONTROL The battery smart unit converts the HV battery condition signals (voltage, current, and temperature), which are needed to determine the charging or discharging values that are calculated by the power management control ECU into digital signals, and transmits them to the power management control ECU via serial communication. A leakage detection circuit is provided in the battery smart unit in order to detect any leakage from the HV battery. Furthermore, the battery smart unit detects the voltage of the cooling fan, which is needed by the power management control ECU to effect cooling fan control. The battery smart unit also converts these signals into digital signals and transmits them to the power management control ECU via serial communication.
CHECK FOR INTERMITTENT PROBLEMS
- CHECK FOR INTERMITTENT PROBLEMS Perform a simulation test. Refer to «HOW TO PROCEED WITH TROUBLESHOOTING»(ref-568589-S05901111982013072300000) . For the simulation test, reproduce the driving conditions that were present when the trouble occurred. These conditions should be based on the customer's comments and freeze frame data that is recorded with DTCs, such as the opening angle of the accelerator pedal, SOC (state of charge), engine coolant temperature, engine rpm, and MG1/MG2 rpm and torque. Check the connector(s) and terminal(s). Refer to «ELECTRONIC CIRCUIT INSPECTION PROCEDURE»(ref-568589-S42645766622013072300000) . Wiggle the harness and connector(s). Refer to «HOW TO PROCEED WITH TROUBLESHOOTING»(ref-568589-S05901111982013072300000) . Heat or cool suspected parts. Refer to «HOW TO PROCEED WITH TROUBLESHOOTING»(ref-568589-S05901111982013072300000) .
Scheme 352
Scheme 352: TERMINALS OF ECU
| Terminal No. (Symbols) | Wiring Color | Terminal Description | Condition | Standard (V) |
|---|
| Z10-4 (TB2) - z10-10 (GB2) | L - L | Battery temperature sensor 2 | HV battery temperature: -40 to 194°F (-40 to 90°C) | 4.8 (-40°F (-40°C)) to 1.0 (194°F (90°C)) |
| Z10-5 (TB1) - z10-11 (GB1) | B - B | Battery temperature sensor 1 | HV battery temperature: -40 to 194°F (-40 to 90°C) | 4.8 (-40°F (-40°C)) to 1.0 (194°F (90°C)) |
| Z10-6 (TBO) - z10-12 (GBO) | W - W | Battery temperature sensor 0 | HV battery temperature: -40 to 194°F (-40 to 90°C) | 4.8 (-40°F (-40°C)) to 1.0 (194°F (90°C)) |
| I1-1 (IB) - i1-6 (GIB) | P - B | Current sensor | Power switch on (READY) | 0.5 to 4.5 |
| I1-5 (VIB) - i1-6 (GIB) | G - B | Power source for battery current sensor | Power switch on (IG) | 4.5 to 5.5 |
| I1-4 (IGCT) - i1-8 (GND) | L - W-B | Control signal | Power switch on (READY) | 11 to 14 |
| I1-2 (BTH+) - i1-8 (GND) | R - W-B | Serial communication | Power switch on (IG) | Pulse generation (waveform 1) |
| I1-3 (BTH-) - i1-8 (GND) | G - W-B | Serial communication | Power switch on (IG) | Pulse generation (waveform 2) |
| I1-7 (VM) - i1-8 (GND) | V - W-B | Battery cooling blower No. 0 monitor signal | Cooling blower activated | 0 to 5 |
| I1-8 (GND) - Body ground | W-B | Ground | Always (continuity check) | Below 1 ohms |
Scheme 353
Scheme 354
- Oscilloscope waveforms HINT: Oscilloscope waveform samples are provided here for informational purposes. Noise and fluttering waveforms have been omitted. Waveform 1 Item Content Terminal i1-2 (BTH+) - i1-8 (GND) Equipment Setting 2 V/DIV., 500 μs/DIV. Condition Power switch on (IG) HINT: The waveform will vary depending on the content of the digital communication (digital signal). Waveform 2 Item Content Terminal i1-3 (BTH-) - i1-8 (GND) Equipment Setting 2 V/DIV., 500 μs/DIV. Condition Power switch on (IG) HINT: The waveform will vary depending on the content of the digital communication (digital signal).
Scheme 355
Scheme 355: DIAGNOSIS SYSTEM
Scheme 356
- DESCRIPTION The power management control ECU (HV CPU) has a self-diagnosis system. If the computer, hybrid vehicle control system, or a component is not working properly, the ECU records the conditions that relate to the fault. The ECU also illuminates the master warning light in the combination meter assembly and provides other appropriate messages on the multi-information display, such as the HV system warning message, the HV battery warning message, on the discharge warning message. TEXT IN ILLUSTRATION *1 READY Light *2 Master Warning Light *3 MIL *4 Multi-information Display HINT: The master warning light will illuminate when the hybrid vehicle control system malfunctions and the light will blink when in inspection mode. When troubleshooting OBD II (On-Board Diagnostics) vehicles, the Techstream (complying with SAE J1987) must be connected to the DLC3 (Data Link Connector 3) of the vehicle. Various data in the vehicle ECM (Engine Control Module) can then be read. OBD II regulations require that the vehicle's on-board computer illuminate the MIL (Malfunction Indicator Lamp) on the instrument panel when the computer detects a malfunction in: The emission control system components. The powertrain control components (which affect vehicle emissions). The computer itself. In addition, the applicable DTCs prescribed by SAE J2012 are recorded in the power management control ECU (HV CPU) memory. If the malfunction does not recur in 3 consecutive trips, the MIL turns off automatically but the DTCs remain recorded in the power management control ECU (HV CPU) memory. To check for DTCs, connect the Techstream to the DLC3. The Techstream displays DTCs, freeze frame data, and a variety of hybrid control system data. The DTCs and freeze frame data can be cleared with the Techstream. In order to enhance the OBD function on vehicles and develop the Off-Board diagnosis system, Controller Area Network (CAN) communication is used in this system. CAN is a network which uses a pair of data transmission lines spanning multiple computers and sensors. It allows for high speed communications between the systems and simplification of the wire harness connections.
- 2 TRIP DETECTION LOGIC When a malfunction is first detected, the malfunction is temporarily stored in the power management control ECU (HV CPU) memory (1st trip). If the same malfunction is detected during the next drive cycle, the MIL is illuminated (2nd trip).
- FREEZE FRAME DATA The power management control ECU (HV CPU) records vehicle and driving condition information as freeze frame data the moment a DTC is stored. When troubleshooting, freeze frame data can be helpful in determining whether the vehicle was running or stopped, whether the engine was warmed up or not, as well as other data recorded at the time of a malfunction.
- AUXILIARY BATTERY VOLTAGE Standard Voltage Switch Condition Specified Condition Power switch on (IG) 11 to 14 V If voltage is below 11 V, replace or recharge the battery. NOTE: After turning the power switch off, waiting time may be required before disconnecting the cable from the negative (-) auxiliary battery terminal. Therefore, make sure to read the disconnecting the cable from the negative (-) auxiliary battery terminal notices before proceeding with work. Refer to «PRECAUTION»(ref-568589-S04857946582013072300000) .
- MIL (Malfunction Indicator Lamp) The MIL is illuminated when the power switch is first turned on (IG), before the READY indicator comes on. When the READY indicator turns on, the MIL should turn off. If the MIL remains illuminated, the diagnosis system has detected a malfunction or abnormality in the system. HINT: If the MIL is not illuminated when the power switch is first turned on (IG), check the MIL circuit. Refer to «MIL Circuit»(ref-568734-S40460594652013072300000) .
Scheme 357
Scheme 357: DTC CHECK / CLEAR
- CHECK FOR DTCS Connect the Techstream to the DLC3. Turn the power switch on (IG). Turn the Techstream on. Enter the following menus: Powertrain / Hybrid Control / Trouble Codes. Check the DTCs and freeze frame data, and then write them down. Check the details of the DTCs. Refer to «DIAGNOSTIC TROUBLE CODE CHART»(ref-568752-S42743818862013072300000) .
- CHECK FREEZE FRAME DATA AND INFORMATION If a DTC is present, select it in order to display its freeze frame data. Read the freeze frame data recorded when the DTC was set. NOTE: A 3-digit information code (INF code) will be displayed as the value for one of the Information 1 to Information 5 lines. Read the information for the information code. Select the item from among Information 1 to Information 5 that has an information code and click the engine icon to view the additional information.
- CHECK FOR DTCS (SYSTEMS OTHER THAN POWER MANAGEMENT CONTROL ECU (HV CPU)) HINT: The power management control ECU (HV CPU) maintains communication with other computers, including the ECM, skid control ECU and power steering ECU. Therefore, if the power management control ECU (HV CPU) outputs a warning, it is necessary to check and record the DTCs of all systems. If DTCs are present, check the relevant systems. HINT: If DTCs for the CAN communication system are present in addition to other DTCs, first troubleshoot and repair any malfunctions in the CAN communication system.
- CLEAR DTCS NOTE: Clearing the DTCs will also clear the freeze frame data, information. Refer to «FREEZE FRAME DATA»(ref-568752-S26165204032013072300000) , and operation history data. Refer to «OPERATION HISTORY DATA»(ref-568753-S18378816432013072300000) . Connect the Techstream to the DLC3. Turn the power switch on (IG). Turn the Techstream on. Check that park (P) is selected. Enter the following menus: Powertrain / Hybrid Control / Trouble Codes. Clear DTCs and freeze frame data.
- CLEAR PERMANENT DTC HINT: Even if the following procedure is not performed, permanent DTCs are cleared by obtaining a normal judgment during 3 consecutive driving cycles. Connect the Techstream to the DLC3. Turn the power switch on (IG). Turn the Techstream on. Enter the following menus: Powertrain / Hybrid Control / Trouble Codes. Check if permanent DTCs are stored. HINT: If permanent DTCs are not output, it is not necessary to continue this procedure. Clear the DTCs. Perform the respective confirmation driving patterns in order to obtain a normal judgment for the output DTCs. HINT: Confirmation driving patterns do not need to be performed for misfire and fuel system DTCs. For the confirmation driving pattern, refer to the procedures for the relevant DTC. Refer to «DIAGNOSTIC TROUBLE CODE CHART»(ref-568752-S42743818862013072300000) . Perform the universal trip. HINT: The driving pattern to obtain a normal judgment and the universal trip driving can be performed consecutively in the same driving cycle. Put the engine in inspection mode. Refer to «INSPECTION MODE PROCEDURE»(ref-568589-S23460353802013072300000) . Idle the engine for 30 seconds or more. Drive the vehicle at 25 mph (40 km/h) or more for a total of 5 minutes or more. HINT: It is possible to complete the drive pattern even if the vehicle decelerates to less than 25 mph (40 km/h) during the driving cycle provided that the vehicle is driven at 25 mph (40 km/h) or more for a total of 5 minutes. Allow 10 minutes or more to elapse from the time the engine is started. Enter the following menus: Powertrain / Hybrid Control / Trouble Codes. Check that the permanent DTCs have been cleared. HINT: The permanent DTCs are cleared when the universal trip is completed.
FREEZE FRAME DATA
- FREEZE FRAME DATA HINT: The power management control ECU (HV CPU) records vehicle and driving condition information as freeze frame data the moment a DTC is stored. It can be used for estimating or duplicating the vehicle conditions that were present when the malfunction occurred. To confirm the details of the hybrid control system, check the detailed information for the DTC information code in the Data List (INF code). Connect the Techstream to the DLC3. Turn the power switch on (IG). Turn the Techstream on. Enter the following menus: Powertrain / Hybrid Control / Trouble Codes. Select a DTC in order to display its freeze frame data. Check the freeze frame information recorded with the DTC. HINT: For the freeze frame data chart. Refer to «INFORMATION / FREEZE FRAME DATA»(ref-568753-S05089431942013072300000) .
