How does the system know what to do?
By the end of this unit, distinguish a requested setting from a sensor reading, an actuator command from actual movement, and an HVAC fault from a sensor or network input problem. Use observations to justify a diagnostic conclusion and verify an approved repair.
Automatic climate control is a conversation.
In manual mode, the driver selects blower speed and often air distribution. In AUTO mode, the controller may adjust blower speed, air temperature, inlet-air choice, and outlet routing to approach a requested cabin temperature. Actual choices depend on manufacturer logic, cabin conditions, and limits.
Setpoint is a target
A display showing 72°F (22°C) is a temperature request, not proof that the cabin or outlet air is already at that temperature.
Feedback is evidence
The module compares relevant sensor inputs with the request and adjusts outputs. A biased input can produce an apparently strange response even while the actuator obeys its command.
Comfort changes with conditions
Sunlight, outside temperature, humidity, and cabin temperature affect comfort and control decisions; not every system measures all of these directly.
Protective strategies intervene
Evaporator freeze protection, engine thermal limits, high-pressure protection, and electrical/energy-management strategies may temporarily override a cooling request.
Read the sensors—not just the dashboard.
In-car temperature sensor
Reports cabin temperature. Some systems use a small aspirator fan to draw cabin air across it. A bias or blocked aspirator can distort the apparent cabin condition.
Ambient temperature sensor
Reports outside-air temperature for display and control decisions. Its location and filtering strategy can affect readings, especially near heat sources.
Sunload sensor
Detects sunlight intensity so the controller can compensate for radiant heating. Test under known light conditions; a high reading in direct sunlight is not inherently a fault.
Evaporator temperature input
Helps prevent evaporator icing where fitted. An implausibly cold reading may lead the controller to limit compressor operation in some designs.
Other possible inputs
Coolant temperature, humidity, refrigerant pressure/temperature, air-quality data, and occupant or seat-zone information can influence equipped systems.
Sensor reading ≠ reality
Compare reported live data with independent observations under stable conditions. Service information determines accepted ranges, sensor behavior, and test points.
A command is not the same as a result.
An HVAC control module may command a blower-control module, temperature blend-door motor, mode-door motor, recirculation actuator, coolant valve, or A/C request. Some inputs and outputs arrive through shared vehicle networks rather than direct switches and wires.
Blend-door request versus position
A controller may request 20% warm-air blending, while an actuator stuck at full heat stays at a different actual position. Where supported, compare commanded and reported positions; confirm physical airflow temperature.
Module requests versus permission
An A/C request is not proof that the compressor or refrigerant control device has been enabled. Powertrain, battery-management, pressure, and other systems may deny or limit operation.
Network communication
Missing or stale data can affect automatic behavior. Record communication-related faults and identify which module owns the missing input before testing wiring or replacing parts.
Dual-zone systems
Left and right sides may have separate setpoints, sensors, and blend doors. A one-sided temperature complaint can narrow the search, but verify system design first.
Four questions before replacing a part.
Start by documenting outside conditions, setpoint, AUTO/manual selection, fan behavior, and left/right outlet temperatures where applicable. Use the vehicle-specific scan-tool data list, HVAC self-tests, wiring diagram, diagnostic procedures, and any relevant fault codes.
Inspect sensor location and airflow, then check wiring, sensor, and scan data according to service information.
Check power, ground, command, position feedback, linkage, and initialization/calibration procedures appropriate to the design.
Identify whether an inhibit is intentional; evaluate enabling conditions using approved information rather than bypassing protective controls.
Check communication status, relevant codes, data validity, and the network/service-information path before assigning a root cause.
Who is commanding what?
Explore a simplified healthy control response with cabin temperature, sunload, setpoint, and AUTO mode. Then investigate five fictional customer complaints with independent, predefined fault conditions. Explorer settings do not alter the diagnostic cases.
Part A · Healthy system explorer
This model gives qualitative outputs; it does not predict actual outlet temperatures, actuator percentages, compressor cycling, or vehicle-specific AUTO algorithms.
Part B · Five diagnostic missions
Choose a case. Perform at least two distinct observations, including the case-specific critical observation, before diagnosing. Then choose a targeted next action and an appropriate verification method. The displayed information is pre-scripted for each teaching scenario.
0 of 5 diagnostic missions completed
The Challenger · Command vs. response
Answer all eight questions. Learning target: 6 of 8 or higher. Review explanations and retry. Your highest score is saved on this browser.
Prove it on an approved trainer.
Use an instructor-supervised low-voltage training vehicle or simulator and manufacturer-approved service information. These six checkbox items track practice planning only; your instructor must verify physical competence separately.
Instructor verification (outside this prototype): Learner ____________________ Vehicle/trainer ____________________ Date __________ Instructor ____________________
Control proven. What's next?
Unit 6 can bring together HVAC electrical control diagnosis, scan data, wiring diagrams, sensor plausibility, and actuator tests in a broader diagnostic workflow. Keep Unit 5 in the same folder as Unit 4 for the previous-unit link to work. This unit is standalone; it has not yet been integrated into the main Autonatomy website.
Return to top ↑