Study for HMT by building a designed-behavior map for each Honda system before practicing scenarios: what the system is supposed to do, under which conditions, and what evidence separates a designed state from a fault. Then practice interpreting codes as leads, reproducing symptoms on paper, and writing concern-cause-correction summaries. For administrative details about the credential itself, confirm with Honda directly at honda.com.
Why the i-MMD hybrid's three modes change what 'normal' looks like
Honda's two-motor hybrid system is designed to shift among EV Drive, Hybrid Drive, and Engine Drive, so an engine that starts and runs is not automatically evidence of a fault. Learning the modes and their trigger conditions is the foundation.
In simplified terms drawn from Honda's public descriptions of the system: EV Drive propels the vehicle with the traction motor while the engine is off; Hybrid Drive runs the engine as a generator while the motor drives the wheels; Engine Drive couples the engine more directly to the wheels, typically at steady cruising. The exact labels and boundaries vary by model generation, so treat these as a conceptual frame, not a universal spec sheet.
Your study task is to attach conditions to each mode: state of charge, battery and coolant temperature, road speed, and power demand all influence which mode the system selects. Build a one-page map per hybrid generation you work with, then ask a habit question before any diagnosis: which mode should this car be in right now? An engine running during hard acceleration is the system working as designed, not a failure to 'stay electric'.
- EV Drive: motor propulsion, engine off — gated by charge, temperature, and demand
- Hybrid Drive: engine generates, motor propels — the workhorse mode under load
- Engine Drive: direct mechanical coupling — usually steady highway cruising
Confirming the symptom before chasing the code
Treat DTCs as leads, not verdicts. A code identifies a detected circuit or condition, and the diagnostic question is whether the recorded conditions actually match the customer's complaint — or whether a designed behavior was mistaken for one.
A cylinder-specific misfire code, for example, tells you which cylinder the monitoring system flagged, not which part caused it. Fuel delivery, ignition, compression, and command-side issues can all surface the same way. Freeze-frame data attached to the code records the conditions at detection — load, temperature, speed — and that snapshot is your reproduction recipe.
The confirmation step is comparing the complaint against the code's logic. If the customer describes a shudder at steady cruise and the freeze-frame shows a cylinder-deactivation transition, the next question is whether that transition was executing correctly, not whether the code 'proves' a coil failed. Designed behaviors — deceleration fuel cut, deactivation engagement, hybrid mode changes — must sit on your map so they cannot impersonate faults.
Scenario: 'the hybrid warning came on once and it never drives electric'
The better decision is to verify operating conditions before concluding the high-voltage battery has failed, because EV Drive is condition-gated by design and a one-time warning without a repeatable code calls for matched-condition testing.
Paper scenario: a late-model Accord Hybrid arrives with a complaint that the engine 'runs constantly' and a hybrid system warning appeared once last week. The plausible mistake is jumping straight to quoting a high-voltage battery replacement, treating the engine running as proof the hybrid system is broken and the single warning as confirmation. On paper, as in the service bay, the conclusion gets ahead of the evidence because the mode question never gets asked.
The stronger path asks first: was it a cold morning, a short trip, hard acceleration, or a low charge after parking? Each of those can keep the system in Hybrid Drive within its design envelope. Then check for stored and pending codes and try to reproduce the warning under similar conditions. If nothing repeats and behavior matches the mode map, the conclusion is a designed state plus a non-reproducible event, documented as such — not a five-figure battery decision with high-voltage safety obligations attached.
Scenario: a V6 misfire that returns after the plugs were replaced
When a cylinder-specific misfire code persists after ignition parts are replaced, the decision should shift from swapping components to comparing that cylinder against its companions under the recorded conditions — including whether Variable Cylinder Management actuation was involved.
Paper scenario: a V6 truck with cylinder deactivation shows rough idle and a misfire code on one cylinder. Plugs and a coil are replaced; the complaint returns two weeks later. The mistake pattern is continuing down the ignition-parts path, because each swap produces a brief improvement that feels like progress. Repeat repairs on the same code are the signature of a skipped confirmation step rather than a stubborn ignition system.
The better decision re-reads the evidence: pull the new freeze-frame, reproduce the symptom at those conditions, and compare the affected cylinder's results — injector balance, compression, actuation behavior during deactivation transitions — against neighboring cylinders. On engines where rocker-arm actuation switches cylinders in and out of operation, a transition-related contribution is a legitimate diagnostic question alongside the conventional ignition and fuel checks. Documenting which exact conditions reproduce the roughness converts a recurring complaint into a bounded problem.
Documentation that reads like a diagnosis, not a parts list
Professional write-ups follow a concern, cause, correction structure, record the conditions under which the symptom appeared or was ruled out, and show where each conclusion came from — the reviewer should be able to follow the logic without asking you.
Compare two write-ups for the same repair: 'replaced plugs, misfire fixed' versus 'concern: intermittent rough idle; cause: cylinder 4 misfire under cold idle, confirmed by freeze-frame reproduction; correction: plugs replaced and cylinder balanced against neighbors.' The second version survives review, supports warranty questions, and makes the next intermittent event easier to chase because the conditions are on the record.
Documentation also carries the ethics and safety weight of the HMT topic areas: high-voltage work is only performed within one's qualification and the manufacturer's documented procedures, and that boundary belongs in the record. Flag unverified variables too — an aftermarket part or a customer-modified component changes what the system was designed to do, and a reviewer needs to know it was present.
A decision table and an observation drill to self-check
Use a decision table to convert observations into first questions, then run a mode-mapping drill on paper and score yourself against a rubric. The rubric measures your diagnostic reasoning maturity — it is a learning milestone, not a score prediction.
The drill: write five short complaints from vehicles you know or from study scenarios, and for each one decide whether the described behavior is a designed state or a fault candidate, name the system involved, and state the first check. Score each item 0-2 on three axes: correct system identification, correct condition matching, and a write-up sentence a reviewer could follow — 30 points possible in total. A total of 24 or more out of 30 suggests your maps are solid; anything lower tells you which system's map to rebuild.
Expected observations when you do this well: your first instinct shifts from 'which part' to 'which mode and which conditions'; designed behaviors stop appearing in your fault list; and your written sentences start containing conditions instead of conclusions. If all five of your answers name a part in the first check, rebuild the maps before doing more scenarios — the rubric is a learning milestone, not a score prediction.
| Observation | Likely system / state | First diagnostic question | Wrong conclusion to avoid |
|---|---|---|---|
| Engine runs at steady highway speed in a hybrid | Engine Drive (designed) | Is speed and load in the direct-drive range? | 'Hybrid system failed to shut the engine off' |
| Rough idle that smooths after a minute cold | Cold-start enrichment / fast idle | Does duration match cold-start design behavior? | 'Injectors are faulty' |
| Brief shudder at steady cruise | Cylinder deactivation transition | Is it repeatable at the same conditions? | 'Engine mounts failed' on the first pass |
| Steering effort changes mid-corner with driver assist active | Honda Sensing intervention | Was the assist engaged and detecting the driver? | 'Electric power steering fault' |
| One-time warning, no stored or pending code | Non-reproducible event | What conditions surrounded the event? | Immediate major component replacement |
An adaptable preparation sequence and readiness checks
A workable sequence: build designed-behavior maps for each core system, drill code-and-condition interpretation on paper, practice three-C write-ups from those drills, then self-test with the rubric until your first-check instincts are condition-based.
Run stage one by writing each system's normal envelope from Honda's public technical material and dealer training resources, one page per system. Stage two pairs each of your maps with two complaints, one designed-state trap and one genuine fault, so interpretation practice always includes the discrimination step. Adjust depth to your experience: a technician who lives in hybrids can compress stage one and expand stage two's intermittent-fault cases.
Readiness checks before you consider the case-analysis material covered: you can state the three hybrid modes and two trigger conditions for each from memory; given an unfamiliar symptom, you can name the first two checks and why; your last five write-ups each contain conditions, not just conclusions; and you can explain where your qualification boundary sits on high-voltage and driver-assist work. If any check fails, return to that system's map rather than adding scenario volume. Administrative details about the credential come from Honda, not study material.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.