PLC Lantern Control System: 2026 Hardware Configuration and Software Design
Share
A PLC lantern control system drives the LED traffic heads, pedestrian signals, and pre-emption inputs on a modern intersection. This How-to walks through the 2026 hardware configuration (CPU, IO, comms, PSU, enclosure) and the software design (ladder structure, fail-safe logic, OPC UA telemetry), based on a working intersection deployment and refreshed against the current NEMA TS 2 / EN 12675 / IEC 61131-3 landscape.
AI Summary
- A PLC lantern controller sits between field sensors (loops, pushbuttons, pre-emption) and LED signal heads, running IEC 61131-3 ladder or structured text with deterministic scan.
- Standard 2026 bill of materials: rugged PLC (Allen-Bradley MicroLogix 1761/1762, Siemens S7-1200, or Omron CP1E), 24V DC PSU with UPS, digital inputs for vehicle/pedestrian calls, relay or solid-state outputs per phase.
- Software patterns that survive field audits: phase-state machine, conflict monitor hand-off, dark-mode default, and per-cycle telemetry over OPC UA or MQTT to the central traffic management system.
- Since 2024: LED drivers replaced 12V incandescent loads, conflict-monitoring moved into firmware (MMU/CMU functions), and controllers gained NTCIP 1202 v04 or ETSI ES 201 for connected corridors.
In short, a 2026 PLC lantern cabinet is a small, deterministic controller, networked as an ITS edge node while still meeting NEMA TS 2 conflict-monitoring requirements.
1. Scope: What a PLC Lantern Control System Covers
A lantern control system is the cabinet that runs a signalized intersection or a pedestrian crossing. In 2026 the cabinet still satisfies the same functional goal ā assign right of way safely ā but the I/O mix and the cabinet architecture have evolved. The PLC now sits next to a conflict-monitoring unit (MMU/CMU), a serial or Ethernet comms module, and an optional ITS backhaul. Sourcing notes for legacy cabinets follow the same playbook as PLC backplane and rack selection for brownfield retrofits; KOEED keeps active and EOL modules side by side.
| Subsystem | 2026 hardware | Typical PLC interface |
|---|---|---|
| Vehicle detection | Inductive loops, video detection, radar | DI module, 24V DC |
| Pedestrian calls | Pushbutton + tactile arrow + audible | DI module, isolated |
| Pre-emption / priority | Strobecom, GPS, EVP | DI / serial module |
| Signal heads | 12V DC LED (red/amber/green) | DO module via load switch |
| Conflict monitor | MMU/CMU (e.g., EDI MMU2-LE) | DI from outputs, DO to PLC |
| Backhaul | Cellular, fibre, NTCIP 1202 | Ethernet / serial module |
2. Hardware Configuration for a 4-Phase Intersection
A typical 2026 deployment has eight vehicle phases, four pedestrian phases, and pre-emption for two emergency approaches. The PLC chosen has to expose a deterministic scan (4-8 ms typical), a long mean-time-between-failures rating, and surge tolerance on every I/O line. Three platforms we see in active cabinets: the Allen-Bradley MicroLogix 1763-LRP (compact, modular), the Siemens S7-1200 CPU 1214C + signal board, and the Omron CP1E-N40DR-A. KOEED keeps each in stock and ships field-tested units with rail and terminal blocks pre-wired.
| Slot / Position | Module | Role | Qty |
|---|---|---|---|
| PSU | 24V DC, 10A, DIN-rail, with UPS | Cabinet supply + battery backup | 1 |
| CPU | PLC (e.g., 1763-LRP or S7-1214C) | Phase controller, scan < 10 ms | 1 |
| DI-1 | 32-pt 24V DC digital input | Vehicle & pedestrian calls | 2 |
| DI-2 | 16-pt isolated DI | Pre-emption, MMU watch | 1 |
| DO-1 | 16-pt relay (or solid-state) DO | Phase outputs to load switches | 2 |
| COM | Ethernet / serial (NTCIP, Modbus) | Central system uplink | 1 |
| Enclosure | NEMA 3R / TS 2 cabinet | Sun, surge, condensation | 1 |
3. IO Point Allocation That Survives an Audit
IO allocation is where lantern PLC projects fail in the field. Two rules help: assign one phase per group of four DOs, keep pedestrian calls on a separate DI word, and wire every output through a conflict monitor channel. The ledger below is what we shipped on a recent dual-ring corridor project; KOEED sources the modules via the Omron CP1 series and Siemens S7-1200 family shelves, both kept in stock alongside the legacy NEMA TS 1 modules.
| Point Range | Type | Signal | Notes |
|---|---|---|---|
| I0.0 - I0.15 | DI | Phase vehicle calls (1-8) | Active high, 24V |
| I1.0 - I1.7 | DI | Pedestrian calls & confirm | Latching |
| I1.8 - I1.15 | DI | Pre-emption, MMU watch | Fail-safe inverted |
| Q0.0 - Q1.7 | DO | Phase drive signals | One-per-output DO |
| Q1.8 - Q2.7 | DO | Pedestrian Walk / Don't Walk | Via load switch |
| Q2.8 - Q2.15 | DO | Flash / dark / test outputs | Latched |
! Warning
Never share a single DO point across conflicting phases. NEMA TS 2 requires the conflict monitor to see every active phase output in parallel; piggy-backed DOs void the MMU cross-check and will be flagged during acceptance testing.
4. Software Design: Phase State Machine + Safety Wrappers
Modern lantern software follows a four-layer structure: cycle clock, phase state machine, ring/ barrier logic, and the comms layer that feeds the central system. Keep each as its own ladder file or AOI; that lets a junior technician diagnose the offending rung without parsing the entire program. The structure below mirrors the PLC sequencer and state-machine design patterns we publish for traffic and transit customers.
- Cycle clock: 100 ms free-running timer drives the phase scheduler; the PLC scan must complete within one cycle.
- Phase state machine: per-phase block with states RED, GREEN, AMBER, RED-AMBER, FLASH, DARK. Transitions only on cycle tick + valid call.
- Ring logic: barrier table enforces that conflicting phases never receive GREEN simultaneously; the barrier feeds the MMU/CMU inputs.
- Comms layer: queue per-cycle status (phase state, calls, MMU health, cabinet temperature) onto OPC UA / NTCIP / MQTT for the central traffic management system.
Sample phase rung (ladder excerpt)
// Phase 2 GREEN condition
|----[ Phase2_Call ]----[ NOT Phase2_Rest ]----( Phase2_Green_Request )--|
| [ Cycle_Tick_100ms ] |
|----[ MMU_Healthy ]----[ Barrier_OK ]---------------------------( Phase2_Permit )--|
> Tip
On Siemens S7-1200 you can implement the same logic in Structured Text inside an FB
(Function Block), then call PhaseFB
per phase. Maintainability improves and the same FB ports to S7-1500 with no code edit.
See our
PLC Hex to Float converter
for the comms scaling math.
5. What Changed Since 2024
Three things materially shifted lantern control design between 2024 and 2026:
- Incandescent heads retired. 12V incandescent signal heads disappeared from most agency specs in 2024-2025; LED load switches draw under 1A per channel, so DO modules sized for tungsten in-rush now work at 30% capacity ā fewer DO points, smaller PSU.
- Conflict monitoring inside the controller. Modern PLCs expose virtual MMU/CMU functions validated against NEMA TS 2; the discrete MMU box is no longer mandatory but still preferred by many authorities.
- Connected corridor telemetry. NTCIP 1202 v04 added object support for pedestrian countdown, adaptive priority, and cybersecurity per IEC 62443-3-3 SL2 ā adjust firewall rules and ladder telemetry blocks accordingly.
- Cybersecurity baseline. Most agencies now require IEC 62443-3-3 SL2 account lockout, signed firmware, and a documented network segmentation diagram ā supply those alongside the program print.
Working on a lantern or intersection controller project?
Send your BOM to Moritta@KOEED.COM. Active stock, EOL stock, and cross-references ā all in one quote within 24 hours.
Send My BOM āRelated on KOEED Blog
- How to wire a 1756-EN2T to an existing ControlLogix chassis
- S7-300 to S7-1500: a practical migration playbook
- Choosing between MicroLogix and ControlLogix for mid-size lines
- PLC fault-finding method flow chart and countermeasures
Frequently Asked Questions
Can a single PLC run a four-way intersection?
Yes. A MicroLogix 1763 or Siemens S7-1214C handles 8 vehicle phases, 4 pedestrian phases, and pre-emption with scan times under 10 ms. Reserve at least 20% spare I/O capacity for future phases and load switch additions.
Do I still need a discrete conflict monitor (MMU) in 2026?
Agency by agency. NEMA TS 2 still references an external MMU for full conformance; many 2026 designs keep the MMU as a hard-wired backup and use the PLC's virtual MMU for diagnostics. KOEED keeps EDI MMU2-LE and equivalent units in stock alongside the PLC.
What power supply size do I need for an LED-only cabinet?
A 24V DC 5A PSU covers the PLC, detection, and comms. Add a separate 12V DC (or constant-current driver) feed for the LED signal heads; modern LED heads typically pull 0.2-0.4 A per channel, so a 3A head supply is usually enough for an eight-channel cabinet. Always add a UPS module rated for at least two hours of full operation.
Which programming language is best for a lantern controller?
Ladder remains the audit-friendly default because most agencies require a printed rung-by-rung review. Structured Text in a Function Block is fine for math-heavy bits (ring cycles, adaptive priority, comms payloads). Combining the two ā ladder for the safety-critical phase logic, ST inside an FB for everything else ā is the 2026 norm.
How do I source the obsolete lamp-driver modules on legacy cabinets?
Send the cabinet's parts list (or a photo of the module labels) to Moritta@KOEED.COM. KOEED cross-references legacy lamp drivers to current solid-state equivalents and ships worldwide. See our obsolete PLC sourcing playbook for the full workflow.