Introduction
Controller performance depends on the timing program. A suitable plan can reduce delay and support safer, more efficient operation; unsuitable settings can cause congestion or preemption problems. This guide reviews commissioning and upgrade parameters for qualified personnel. Available settings and programming interfaces must be confirmed in the selected model’s manual.
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.
Choose the operating mode against the project requirements. Fixed-time control follows a preset plan; actuated control responds to detector calls; adaptive control adjusts timing using traffic data. Supported modes, detectors and coordination functions depend on the selected model, firmware and system configuration, and must be confirmed before programming.
Phase Sequence and Ring Structure
Phase sequence defines the order in which movements are served. In a ring-and-barrier arrangement, phases within each ring run in sequence and the rings cross a barrier together to coordinate compatible movements and separate conflicting traffic streams. Opposing protected left turns may operate together when the approved geometry and phasing permit. Confirm the phase plan and the selected controller’s documented implementation.
Before programming, develop an approved movement-compatibility and phase plan. A ring-and-barrier diagram can show sequencing and coordination constraints. Do not assume opposing left turns always conflict or that through traffic, left turns and pedestrians can always run together; verify the actual geometry, signal indications and pedestrian conflicts.
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.
- Signal timing must be calculated for the actual intersection, approach conditions and pedestrian needs under the applicable authority’s rules. Have the responsible engineer approve minimum green, yellow change and any red-clearance intervals. Example durations are not installation defaults.
- Signal timing must be calculated for the actual intersection, approach conditions and pedestrian needs under the applicable authority’s rules. Have the responsible engineer approve minimum green, yellow change and any red-clearance intervals. Example durations are not installation defaults.
- Signal timing must be calculated for the actual intersection, approach conditions and pedestrian needs under the applicable authority’s rules. Have the responsible engineer approve minimum green, yellow change and any red-clearance intervals. Example durations are not installation defaults.
Confirm whether the selected model allows these settings per phase and per time-of-day plan. Timing values must follow the applicable authority’s approved design and safety requirements; any field adjustment should be reviewed and tested by qualified personnel.
Detector Setup and Calls
Actuated control depends on detector calls. Inductive loops, video detection and radar may provide those calls through compatible interfaces. Confirm the selected controller’s supported input types, then map each detector to the approved phase and 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.
The number of time-of-day plans must be confirmed for the selected controller. A project may use peak, off-peak, night and weekend plans, with cycle lengths and green allocations based on measured turning movements. Night flashing requires authority approval and supported hardware. Schedule changes using site data rather than 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
Programming access may be local, web-based or through a central platform, depending on the selected model and firmware. Confirm the supported method. Back up the as-built timing parameters before field changes. Record the final plan, controller serial number, cabinet location, firmware version and technician’s name so future maintenance has a verified reference.
Featured Products
For GAOQIAO controller options, confirm the supported programming functions in the model documentation and see the traffic signal controller range, the wired controller cabinet solution, the controller selection guide and the controller compatibility checklist.
Conclusion
Programming requires an approved phase sequence, timing parameters, detector mapping and time-of-day plans, followed by acceptance testing. Confirm which functions, templates and documentation are available for the selected controller. Engineering assistance and timing-plan preparation must be agreed separately; the final plan needs approval and site verification.
Get a Quote
Send your intersection layout, signal head schedule and controller model to discuss the project and quotation. Timing-plan preparation, engineering review and site validation are services whose availability, scope and responsibilities must be agreed separately.
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?
Confirm the selected controller’s maximum number of timing plans, supported time/day schedules, manual override and event logging. Automatic plan changes and timestamped records are model- and firmware-dependent and must be verified in the approved configuration.
How do I back up the controller program before making changes?
Before changing a timing plan, preserve the current settings using the selected controller’s documented backup method. Confirm whether file export is available. Store the backup or verified parameter record with the controller serial number, date, wiring diagram and acceptance test sheet in the cabinet’s records.
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.
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.