AUTONATOMY
HVAC Systems / 09.7 / Thermal Management
Reading 0%
Mastery 0%
Course 09 · HVAC Systems · Module 09.7

Battery, Power Electronics & Drivetrain Thermal Management

Follow heat as diagnostic evidence. Learn how the vehicle senses thermal need, commands pumps, valves, fans and chillers, protects high-value components, and changes charging or propulsion performance when temperature control cannot keep up.

Thermal Need → Architecture → Sensor Evidence → Control Command → Flow / Heat Transfer → Protection / Performance → Verification
01 / LEARN

Build the mental model

Seven short lessons establish the thermal path before diagnosis.

1

Thermal management protects performance and life

Battery cells, inverters, converters, motors and driveline components create or absorb heat. Thermal control keeps them inside architecture-specific operating targets; a protection response is evidence, not automatically a failed component.

2

Identify the real thermal architecture

Vehicles may use separate or shared coolant loops, refrigerant chillers, radiators, pumps, valves and air-cooled elements. Use current service information before tracing heat.

3

Traction-battery conditioning

Battery temperature affects charging, power capability, regeneration and life. Diagnose requested conditioning, pump/valve/chiller or heater commands, flow and temperature response.

4

Power-electronics and motor heat

Inverters, DC/DC converters, onboard chargers and electric machines can share or separate cooling paths. Determine which heat source and loop is active under the complaint conditions.

5

Pumps, valves, radiators and chillers

Thermal actuators route and reject heat. Compare command with actual flow/temperature change instead of condemning an actuator from a DTC alone.

6

Derating, protection and range

A vehicle may limit propulsion, charging or regeneration to protect components. Treat the limit as a symptom of system state and find the evidence that caused it.

7

Diagnose the whole thermal path

Start with complaint and operating state, identify the protected component and loop, compare sensor plausibility and commands, verify heat movement, then prove root cause and post-repair recovery.

02 / EXPLORE

Trace the thermal system

Move from the protected component outward through sensing, flow, heat exchange and supervisory control.

1. Protected componentBattery, inverter, converter, charger, motor or drivetrain component establishes the thermal need.
2. Temperature sensingMultiple sensors provide local and loop temperature evidence; plausibility matters as much as a single value.
3. Coolant loopCoolant carries heat among components, heat exchangers and architecture-specific heaters/chillers.
4. Electric pumpCreates coolant flow when commanded; verify command, electrical operation and thermal/flow response.
5. Valves / manifoldsRoute coolant among loops and heat exchangers; position or routing faults can mimic component overheating.
6. Radiator / fanRejects heat to ambient air when operating conditions permit.
7. Refrigerant chiller / heaterOn applicable vehicles, refrigerant or electric heat can condition a coolant loop or battery.
8. Supervisory controlModules coordinate thermal demand, available energy, charging/propulsion limits and component protection.
03 / INTERACT

Interactive thermal-response lab

Change the system state and compare demand, command, heat-transfer response and protection margin. Values are normalized teaching indices—not OEM limits or service specifications.

Thermal demand
55
Command
70
Heat-transfer response
72
Protection margin
88

Normal: demand, command, heat movement and protection state agree.

04 / DIAGNOSE

Use an ordered diagnostic process

  1. Verify complaint, operating state, charging/propulsion conditions and any power/charge/regeneration limitation.
  2. Identify the protected component and the vehicle-specific thermal architecture from current service information.
  3. Establish HV/refrigerant/invasive-service boundaries; remain in approved data and low-voltage domains unless qualified and equipped.
  4. Check sensor plausibility and compare thermal request with pump, valve, fan, heater/chiller and supervisory commands.
  5. Verify actual coolant flow and temperature/heat-transfer response with approved tests; separate control, circulation, routing, heat-rejection and component-load causes.
  6. Repair only the proven cause, then repeat comparable conditions and verify temperatures, thermal commands, protection/derating recovery and documentation.
Safety boundary: This module teaches system reasoning, not authorization for high-voltage, battery-pack, refrigerant or invasive thermal service. Follow current OEM procedures, PPE, equipment, isolation and qualification requirements. Never defeat interlocks or protection strategies.
05 / PROVE THE DIAGNOSIS

Evidence-gated cases

Commit to an evidence branch. Reading the case is not completion; making the diagnostic decision is.

1. Fast-charge power falls as battery temperature rises

Charge request remains present; battery temperature climbs and thermal system command increases.

Evidence branch: Follow battery-conditioning performance—pump/valve/chiller/heat-rejection evidence—before blaming the charger.

2. Inverter temperature rises but coolant outlet barely changes

Pump command is present; expected loop temperature movement is weak.

Evidence branch: Verify actual coolant circulation, restriction/air, pump response and routing before condemning the inverter.

3. Propulsion power limited with implausible temperature input

One reported temperature disagrees strongly with related sensors after soak.

Evidence branch: Prove sensor/circuit/data plausibility before treating the protection strategy as a cooling-system failure.

4. Cooling command changes when cabin demand increases

Shared thermal architecture reallocates valve/chiller operation as cabin load changes.

Evidence branch: Compare behavior with OEM thermal strategy; shared-resource behavior is not automatically a fault.
06 / FINAL ASSESSMENT

Knowledge check

Ten questions. An 8/10 score is required for the assessment portion of mastery.

Not attempted
07 / PRACTICAL VERIFICATION

Instructor practical rubric

Digital mastery and practical competency remain separate. An instructor can use these six dimensions to verify hands-on performance.

Complaint & operating-state verification
Architecture / loop identification
Safety & work-boundary decision
Sensor / command plausibility
Flow & heat-transfer evidence
Protection recovery & documentation

Course 16 connection: Course 16 remains the deeper Hybrid/EV path for HV architecture, traction batteries, power electronics, charging and propulsion. 09.7 uses those concepts to diagnose integrated thermal-management behavior.