Which Test First on a Dead Gate Operator: Power vs Board vs Sensor Decision Tree

Why this matters

A "dead" automated gate is rarely dead. It is far more often a gate that has correctly refused to operate because a UL 325 safety device, an interlock, or its power feed is in a fault state. Techs who jump straight to swapping the control board burn the most expensive part on a fault that was a tripped GFCI or a misaligned photo-eye. Testing in the right order, power first, then board logic, then sensors, finds the cause in minutes and protects you from condemning a healthy board.

Order matters because each stage depends on the one before it. A board cannot pass logic checks on dead power, and a sensor fault reads as a board fault if you have not first confirmed the board is alive. Test upstream to downstream, every time.

Symptom presentation

The customer says "the gate won't open," "the remote does nothing," "it opens but won't close," or "it reverses by itself." Translate each:

• Nothing happens on any input (remote, keypad, wall button): suspect power or a hard board fault.
• Opens but will not close, or closes and immediately reverses: suspect a safety sensor (photo-eye or edge) per UL 325, not power.
• Intermittent, dies in heat or after rain: suspect power feed, connections, or a marginal board.
• Status LED on the board is off or showing a fault code: read the code before touching anything.

Quick checks

Before any meter work, do the no-tool reads:

• Board status LED / diagnostic display: Almost every operator board shows power and fault state. Off means no power to the logic. A blinking fault code is the board telling you exactly which input it is unhappy with; consult the unit's code legend.
• Manual release: Disengage the operator and move the gate by hand. If it binds, drags, or will not move freely, the operator may be protecting itself or the motor against a mechanical bind, and the "electrical" call is actually a mechanical one (post, roller, track, hinge).
• Visible power: Check the GFCI receptacle or breaker feeding the operator. A tripped GFCI is the most common "dead gate."

Isolation tree

Work strictly upstream to downstream.

1. Power stage.
   • Confirm supply voltage at the operator's line input with a multimeter (line voltage for AC units; confirm DC/battery voltage and solar charge state on battery units). No voltage: trace back to GFCI, breaker, disconnect, or transformer. Resolve here before going further.
   • On battery/solar operators, a low or dead battery presents exactly like a dead board. Read battery voltage under the manufacturer's threshold and check the charger/solar input.
   • Power present and correct? Proceed to board.
2. Board / logic stage.
   • With confirmed power, is the board status LED on? Off with good input voltage points to a blown onboard fuse or a failed board. Check the board's fuse first.
   • Read any fault code. If the code points to a specific input (sensor, edge, limit), jump to that input rather than the board.
   • Trigger an open command directly at the board terminals (jumper the open input per the manual) to bypass remotes and keypads. If the operator runs from the terminal but not from the remote/keypad, the fault is in the accessory or receiver, not the board.
3. Sensor / safety stage.
   • UL 325 requires inherent and/or external entrapment protection (photo-eyes, sensing edges). A blocked, misaligned, dirty, or failed photo-eye will correctly inhibit closing. Check eye alignment and the indicator LEDs on each eye; clean the lenses; confirm the beam is unbroken.
   • Test sensing edges for continuity and damage. A pinched or cut edge wire reads as a constant obstruction and stops the gate.
   • Check limit switches and physical stops. A limit out of position can make the operator think it has reached travel end and refuse to move.

Confirming diagnosis

• Power confirmed when the operator runs after restoring the supply (reset GFCI, replace fuse, charge/replace battery) and the board LED comes alive at correct voltage.
• Board confirmed only after power is verified good, the onboard fuse is intact, and a direct terminal command still produces nothing while sensors and limits check clean. Condemn the board last, not first.
• Sensor confirmed when the gate opens normally but refuses to close (or reverses), and aligning/cleaning/replacing the photo-eye or repairing the edge restores closing. The UL 325 device was doing its job.

Remediation

• Power: Reset the GFCI, replace the operator fuse, correct loose terminations, or service the battery and charger. Verify the receptacle is a weather-rated GFCI as required outdoors.
• Board: Replace only after confirming power-good and sensors-clean. Reprogram limits and accessories after swap.
• Sensor: Realign and clean photo-eyes to the manufacturer's gap and height; replace a damaged sensing edge; reposition limit switches. After any sensor work, run a full open-close cycle and verify the gate reverses on a test obstruction.

References

• UL 325, Standard for Door, Drapery, Gate, Louver, and Window Operators and Systems (entrapment protection, photo-eyes, sensing edges, monitored safety devices).
• ASTM F2200, Standard Specification for Automated Vehicular Gate Construction (gate construction requirements that interoperate with UL 325 operators).
• Manufacturer operator installation and service manual (board fault-code legend, limit setup, sensor alignment specifications).