IMSA Traffic Signal II common mistakes
IMSA Traffic Signal II · Understand the traps and how to avoid them.
Reading each plan sheet in isolation and answering phasing questions from the signal display sheet without cross-checking the lane-use arrows, approach geometry, and timing sheet, so left-turn phases get assigned to the wrong approach.
Plan sets split information across display, phasing/timing, and geometric sheets; candidates study one sheet at a time and never build a consolidated phase-to-approach picture.
What to do instead
Before answering, draw a quick phase-by-approach matrix (approach, lanes, movements, phase number, overlaps) using every relevant sheet, and verify it against the cabinet wiring/terminal sheet.
Treating MUTCD warrant volume thresholds as design criteria and selecting signal type, lane configuration, or phasing directly from the warrant chart.
Warrants and design are taught together, so candidates conflate the justification for a signal with the engineering decisions that define it.
What to do instead
State explicitly that warrants answer 'should a signal exist here?' while design (phasing, lane use, head placement) comes from the plans and engineering judgment; answer warrant questions only from Part 4 warrant tables.
Calculating the clearance interval from the posted speed limit alone and accepting a default 3-second yellow, ignoring approach grade, perception-reaction time, and the all-red component.
Default values are common in the field and candidates memorize '3 seconds yellow' instead of the calculation method.
What to do instead
Use the standard kinematic formula with 85th-percentile approach speed, perception-reaction time, deceleration rate, and grade, then add the all-red for intersection clearing distance; practice one calculation per approach type.
Assuming a recall setting will force a phase to be served during coordinated operation when recall actually only applies in free (non-coordinated) mode.
Controller terminology overlaps between free and coordinated operation, and candidates memorize function names without the mode in which each is active.
What to do instead
Review the controller manual's mode table and the coordination timing plan; for each function state whether it is active in free, coordinated, or both, and test your answer against a sample timing plan.
In troubleshooting, swapping the controller or conflict monitor first instead of checking supply voltage, cabinet ground, and the input file.
The controller is the most visible component and 'swap it out' is a common field shortcut, so candidates adopt that order.
What to do instead
Follow a power-first sequence: verify AC supply, then cabinet ground, then DC/logic voltages, then inputs and detection, then the MMU, then the controller; document each step.
Releasing an intersection after installation without verifying conflict-monitor configuration/jumpers and without a detection zone test, leaving a misconfigured MMU in service.
Checkout is treated as a wiring continuity exercise; the MMU is often assumed to be factory-correct and detection is assumed to work because the light changes.
What to do instead
Use a written checkout checklist that includes MMU channel/configuration verification, conflict and redundancy tests, and a physical detection test (presence and pulse) for every zone before release.
Leaving existing signal and pedestrian timings unchanged during a lane closure that reduces capacity, so queues spill back into the work zone and pedestrians lose a usable path.
Work zone plans focus on traffic control devices, and candidates treat signal timing as outside the temporary traffic control plan.
What to do instead
Recalculate cycle length, splits, and pedestrian walk/clearance for the reduced capacity, and verify a temporary pedestrian access route; include timing changes in the work zone plan and check them before opening.
Answering code questions from memory of an older MUTCD edition or citing a state DOT standard as if it were the MUTCD.
Candidates train on whichever edition was current when they studied and do not track the hierarchy between federal standard and state supplement.
What to do instead
Know the current MUTCD edition and Part 4 structure, and state the hierarchy: MUTCD sets the minimum national standard, state/local supplements may be more restrictive and govern in that jurisdiction.
Checking vertical clearance to the top of the signal head or to the span wire rather than to the bottom of the signal head, and answering clearance-height inspection questions from memory instead of the plan.
Clearance is visually associated with the highest point, and field values are often 'known' rather than looked up.
What to do instead
Measure and inspect to the lowest point of the signal head (and lowest point of any attached equipment), and always read the required clearance from the plan sheet before judging compliance.
Ignoring the cable, conduit, and wiring schedules on the plan set, so conductor counts, spare pairs, and homerun sizes cannot be answered.
Schedules are dense tables at the back of the plan set and candidates focus on the plan-view drawings.
What to do instead
Locate the schedule sheets first, tabulate each cable/conduit by number, size, conductor count, and route, then cross-reference against the plan view and cabinet termination sheet.