Traffic Signal Controller Programming Guide: Timing, Phases and Coordination
Introduction
A traffic signal controller is only as good as the program that runs it. A well-tuned timing plan reduces delay, improves safety and cuts emissions; a poorly tuned one creates congestion, driver frustration and emergency vehicle preemption failures. This guide walks a traffic engineer or experienced electrician through the parameters that matter when commissioning or upgrading a controller, and shows how GAOQIAO controllers expose those parameters for clear, safe programming.
The Three Things a Controller Program Controls
Every controller program, whether fixed-time, actuated or adaptive, is solving three problems at once: how long each movement gets green, the order in which movements run, and how the controller reacts to traffic in real time. Get any of these wrong and the intersection fails one of its three jobs — moving vehicles, serving pedestrians and responding to demand.
The first decision is the controller mode. Fixed-time is the simplest and cheapest; actuated is the default for most modern intersections; adaptive adds detectors and a coordination layer for arterials. Most GAOQIAO controllers run any of the three on the same hardware, so the programming task is to choose the mode and then set the parameters that follow from that choice.
Phase Sequence and Ring Structure
The phase sequence is the order in which the controller runs movements. A typical four-leg intersection needs at least four vehicle phases (northbound, southbound, eastbound, westbound), two pedestrian phases and one or two overlap phases for protected left turns. GAOQIAO controllers store phase sequence as a ring diagram: the left-side ring runs the NB-SB pair, the right-side ring runs the EB-WB pair, and the barrier between the rings ensures opposing left turns cannot run together.
When you programming a new intersection, draw the ring first. List every movement that must run together (e.g., NB through + NB left + NB pedestrian on the same barrier) and every movement that must never run together (e.g., NB left and SB left). The ring diagram is the map of those rules. Once the ring is right, the rest of the program falls into place.
Timing Parameters You Will Set
Six timing parameters cover most intersection timing. They are:
- Cycle length: the total time for one full rotation of the phase sequence. Typical urban values run 60-120 seconds, with 90 seconds as a common compromise between progression and delay.
- Split: the percentage of the cycle allocated to each phase. Sum of splits must equal 100%, but overlap phases can share split time.
- Offset: the time the first phase starts relative to a system-wide reference. Used for coordinated arterials.
- Yellow change interval: typically 3-5 seconds, computed from approach speed.
- All-red clearance interval: 1-2 seconds, sized for the worst-case intersection width.
- Minimum green: usually 5-7 seconds for vehicles, longer for pedestrians.
GAOQIAO controllers let you set these per phase and per time-of-day plan. Start with the MUTCD or local standard values, then tune with field observations.
Detector Setup and Calls
Actuated control depends on detector calls. GAOQIAO controllers accept inputs from inductive loops, video detection cameras and radar sensors. Each detector is mapped to a phase and a function:
- Presence detection: call while a vehicle is over the loop (used for protected phases).
- Pulse detection: call once when a vehicle enters the loop (used for green extension).
- Count detection: count vehicles per interval (used for adaptive algorithms).
Detector failures look like phase failures. If a phase maxes out without serving traffic, walk the detector loop with a metal tool and confirm the controller sees the call on its diagnostic page. A broken loop, a wrong sensitivity setting, or a miswired harness is more common than a controller software bug.
Coordination and Time-of-Day Plans
For an isolated intersection, programming ends after the timing parameters are set. For an arterial or a grid, the controller needs a coordination plan: a common cycle length, an offset for each intersection, and time-of-day plans that switch the cycle, split and offset based on traffic patterns.
GAOQIAO controllers support up to sixteen time-of-day plans per intersection. A typical setup has a peak plan (longer cycle, more green for the peak), an off-peak plan (shorter cycle), a night plan (very short cycle, flashing yellow optional) and a weekend plan. Schedule the plan changes to match the actual turning movement counts at that intersection; do not use generic templates.
Field Tuning and Acceptance
Programming is not finished when the parameters are entered. The next step is a field acceptance test. GAOQIAO recommends this sequence:
1. Run each phase manually from the controller cabinet, watching the signal heads. 2. Run a full cycle with no calls; verify yellow, all-red and minimum green. 3. Run a full cycle with pedestrian calls; verify walk and clearance intervals. 4. Run with detector calls on each approach; verify extension and max-out behavior. 5. Run the coordination plan with a downstream intersection; verify offset visually.
Each step should produce a written observation: phase number, time of day, observed behavior, expected behavior, pass or fail. The signed sheet becomes the baseline for future maintenance.
Programming Tools and Documentation
GAOQIAO controllers program through a web interface, a local laptop connection, or a central management platform. Always store a backup of the as-built timing parameters before any field change. When the timing is finalized, export the timing plan and file it with the controller's serial number, the cabinet location, the firmware version and the technician's name. Without that record, the next maintenance visit will start from zero.
Featured Products
For a controller that programs cleanly and supports the timing workflow above, see GAOQIAO's traffic signal controller range, the wired controller cabinet solution, the controller selection guide and the controller compatibility checklist.
Conclusion
Programming a traffic signal controller is structured work, not magic. Draw the ring, set the timing parameters, map the detectors, build the time-of-day plans, then prove the result with a field test. GAOQIAO's wired and solar controllers expose all the parameters discussed here and ship with documented timing templates. Send us your intersection layout and we will return a recommended timing plan that your team can field-tune to local conditions.
Get a Quote
Send us your intersection layout, signal head schedule and current controller model. We will return a recommended timing plan and a matching quotation.
Email: sky-sale@njgq.net WhatsApp/Phone: +86-18805173545 Tel: +86-25-84471080
Frequently Asked Questions
How long does it take to program a traffic signal controller?
A first-time setup for a 4-leg intersection takes 2-4 hours including detector mapping and field testing. An experienced technician with the timing plan pre-built can cut that to under an hour. Plan for one full week of follow-up observation after the controller goes live.
What is the difference between fixed-time and actuated programming?
Fixed-time programming sets the cycle and split based on historical counts and never changes them mid-cycle. Actuated programming adds detector calls that extend or skip phases based on demand. Fixed-time is simpler and cheaper; actuated is more responsive and is the modern default for most intersections.
Can a controller run multiple timing plans at once?
Yes. GAOQIAO controllers support up to sixteen time-of-day plans and can switch between them automatically based on the time of day, day of week, or a manual override. The current plan is logged with timestamps for audit purposes.
How do I back up the controller program before making changes?
Every GAOQIAO controller has a web or local interface that exports the active timing plan as a file. Always export and store the backup with the controller serial number and the date. Most agencies keep a per-cabinet folder with the latest backup, the wiring diagram and the acceptance test sheet.
What should I do if a phase maxes out without serving traffic?
Walk the detector loop with a metal tool and check the controller's diagnostic page for detector calls. If the controller sees the call but does not extend, suspect a phase parameter error. If it does not see the call, suspect the loop, the harness or the detector card. Always check the simplest explanation first.
---
[!todo] 发布清单 > - [ ] 用户确认内容 > - [ ] 转 HTML（含 TechArticle + FAQPage Schema） > - [ ] 上传 blog/traffic-signal-controller-programming-guide.html > - [ ] 更新 sitemap.xml > - [ ] GSC 提交抓取
Relevant GAOQIAO products
These public GAOQIAO catalogue pages are related to the guide. Open them for the representative description, then confirm the latest drawing and configuration before ordering.
- Traffic signal controllersWired and solar controllers with 6, 22, 44 and 56 output options.
- LED traffic signal heads200mm, 300mm and 400mm signal heads with MUTCD, EN12368, GB14886 compliance.
- Signal polesVertical, signal arm and double-arm poles for any intersection geometry.
- Spare parts and accessoriesSpare LED modules, lenses, visors, surge arrestors and anchor bolts.