A gear-selection request becomes a lighting command.
Reverse lamps illuminate the area behind the vehicle and indicate that the vehicle is in—or may move in—the reverse direction. To diagnose them, separate the driver’s gear request, the electrical control path, and the lamp power/ground paths.
Know
Identify reverse lamps, trace a simplified backup-light circuit, distinguish mechanical switches from range-sensor/module strategies, and recognize shared versus individual failures.
Prove
Capture voltage evidence for seven virtual cases, meet the 6/8 Challenger target, and demonstrate approved testing and verification on a physical trainer.
Reverse lamps: a warning and a visibility aid.
Backup or reverse lamps are normally rear-facing white lamps. They help illuminate the area behind the vehicle and signal that reverse gear is selected. They are not the same as red stop lamps, tail lamps, or the center high-mounted stop lamp.
What to observe
Locate the reverse lamps in the rear combination lamps or another manufacturer-designated location. Observe whether one or two illuminated positions are specified; this trainer models two independent lamp loads.
When to expect illumination
On many conventional vehicles, reverse lamps illuminate when Reverse is selected with the applicable ignition state. Some newer architectures use module control, delayed behavior, or different power-state logic. Check the service information for the particular vehicle.
Source → protection → reverse request → lamp branches.
Some vehicles use a switch that closes in Reverse and feeds the lamps. Others use a transmission range sensor or selector input that communicates with a body or powertrain module, which then commands the lamp output. The actual wiring diagram determines the circuit arrangement.
↳ LEFT reverse lamp (12 Ω) → return
↳ RIGHT reverse lamp (12 Ω) → return
The diagram above is the virtual lab's electrical model only. “Reverse-request gate” stands for a simple switch or a module-controlled output, not a literal claim about every production vehicle.
Both lamps dark
Begin with shared items: operating conditions, fuse/feed, reverse-request input, output driver, and any common return. Do not replace both bulbs until you have evidence.
Only one lamp dark
Compare branches. A failed individual load, connector, feed, or return can affect one lamp while the other operates. A meter showing feed voltage alone does not prove a complete current path.
Reverse selected does not always mean lamp output energized.
In a mechanical arrangement, gear selection may operate a dedicated reverse switch. In an electronic arrangement, a selector or range sensor provides position information to one or more modules; control logic then commands the lamp circuit. Some systems share the range information with the cluster, powertrain, parking aid, or camera, but those features do not automatically prove that the lamp-output circuit is good.
Input question
Does the controller receive the correct gear-position indication? Verify using the manufacturer’s wiring and scan-data procedure rather than assuming a good shifter mechanically proves an electrical request.
Output question
If Reverse is recognized, is the appropriate supply/ground delivered to the lamps? Compare input data with output-voltage evidence to separate an input issue from an output or load issue.
Stuck ON
Reverse lamps illuminated outside the required conditions can result from a stuck switch, incorrect gear-state signal, or output-circuit fault. Confirm the actual commanded state first.
Vehicle-specific caution
Module outputs may be protected, monitored, pulse-driven, or low-side switched. Never apply this trainer's power-side test points blindly to a real vehicle.
Choose the test that separates possibilities.
Confirm the complaint under the manufacturer-approved conditions. Identify whether both lamps fail, one lamp fails, the lamps are dim, or the lamps remain on incorrectly. Locate a reliable ground reference and the actual power/ground architecture before measuring.
- Verify request and operating state: Is the correct ignition or enable condition present? Is Reverse actually recognized?
- Check shared protection and output: If both lamps fail, measure the fuse's supply and load sides and the appropriate control/output path.
- Compare branches: If one lamp fails, compare its feed, return, connector condition, and load to the operating side.
- Measure loaded losses: If a lamp is dim, use voltage-drop testing across the suspect feed or return while the circuit is commanded ON.
- Verify repair: Recheck the original complaint, normal operation in and out of Reverse, and any related vehicle functions affected by the service procedure.
Reverse-Lamp Diagnostic Bay
Choose the ignition and gear states, install a fault, and select a voltmeter test. Measurements are calculated from this two-lamp model. The meter reads DC volts between the explicitly named endpoints, while load current is shown separately.
Teaching model: ignition enables a fuse and reverse request; two 12 Ω lamps have separate returns. Select faults above to see the effect.
Battery positive → battery negative
Select ignition ON and REVERSE to illuminate both lamps in the healthy model.
Seven diagnostic missions
Set the exact operating state, fault, branch, and meter endpoints specified in each mission; then choose Check my evidence. These missions validate a measurement setup, not an actual physical repair.
The Challenger: Prove Your Diagnostic Logic
Answer eight questions. A score of at least 6/8 meets this virtual knowledge-check target; the hands-on tasks are assessed separately. Each question explains its answer after you submit.
Practical Challenge: Verify a Reverse-Lamp Repair
These checkboxes are a personal practice log only; checking them does not confer a credential or verify physical competence. The instructor must independently observe and sign off the tasks using the applicable vehicle service instructions.
0 of 6 practice tasks logged.
Unit 5 progress
Complete the lessons, virtual lab, assessment, and personal practice log to track your progress.
Progress is local to this file/browser. Integration into the main Autonatomy website and account-based records will require a later development step.