A variable message sign (VMS) is a roadside LED display whose message changes with traffic conditions instead of being fixed. In SİNYAL systems the message is not typed by an operator; it is written by rule from live data such as queue length, travel time and incidents, and every message sent is compared with what the device actually shows. This post describes how a message reaches the sign. The solution as a whole is on the variable message signs page.
What the sign can show
- Free text
- Pictograms from a 134-piece library
- Operator-uploaded regional pictograms
- Multi-page messages
- Display effects
- Travel time for a defined route
- Queue-length diversion
- Traffic incident notices
Travel time is the current measured time for a defined A→B route, shown in the form "airport 18 min". Queue-length diversion fires once the measured queue on an approach crosses its threshold. A traffic incident notice carries the road and the description, whether it is an accident, a closure or roadworks.
How a message reaches the sign
There are five steps:
- Rule: a condition, a message and a priority
- Candidate: every message whose condition currently holds
- Arbitration: the winner is picked by priority, and the reason is recorded with it
- Write: the message is sent to the device
- Reconcile: what is on screen is read back and verified against what was sent
The rules automation obeys
- The operator lock wins: automation never touches a message posted by hand, for any reason.
- A stale source posts nothing: if the feeding data falls silent, "road closed" does not stay on the sign.
- Arbitration records the reason: more than one rule can be right at the same moment; ROTA picks the winner by priority and writes down why, so "why was this message showing?" can be answered afterwards.
Sign faults
The sign's alarms are kept separate: offline, device fault, pixel fault and degraded automation are never conflated. The LEDs the device reports as faulty are drawn on a bad-pixel map at the sign's own resolution, so the operator sees exactly which part of the display has failed.
Part of ROTA
Sign automation is not a separate application. The rules draw on the queue length, travel time and incident data that ROTA already holds, and the sign's alarms join the same fault lifecycle as the rest of the network.