IRIS
Intelligent Roadway Information System
Lane Control Signs (LCS)
Select View ➔ Lane Use ➔ LCS
menu item
Lane Control Signs (LCS) are traffic-control devices for displaying downstream lane conditions to motorists. Typically, one sign is mounted over each lane as an array. They can display standard indications:
Indication | Symbol |
---|---|
Dark |
|
Lane open |
↓ |
Use caution |
⇣ |
Lane closed ahead |
✕ |
Lane closed |
✖ |
Merge right |
》 |
Merge left |
《 |
Must exit right |
⤷ |
Must exit left |
⤶ |
HOV / HOT |
◊ |
Variable speed advisory |
A |
Variable speed limit |
L |
API Resources 🕵️
iris/lcs_indication
(lookup table)iris/lcs_type
(lookup table)iris/api/lcs
(primary)iris/api/lcs/{name}
Access | Primary | Secondary |
---|---|---|
👁️ View | name, location, status | geo_loc |
👉 Operate | lock | |
💡 Manage | notes | shift |
🔧 Configure | controller | pin, lcs_type, preset |
There are a few different types of LCS:
- Dedicated signs over each lane
- General purpose DMS over each lane
- In-pavement LED striping / marking
Setup
The LCS properties form has setup information.
Field | Description |
---|---|
Notes | administrator notes, possibly including hashtags |
LCS Type | dedicated sign, DMS, in-pavement |
Preset | verification camera preset |
Shift | roadway corridor lane shift |
An LCS array must also be associated with a controller, on IO pin 2. For NTCIP, any controller for a DMS in the array is allowed.
LCS States
Each indication that can be displayed on each lane of an LCS array is represented by an LCS state.
API Resources 🕵️
iris/api/lcs_state
(primary)iris/api/lcs_state/{name}
Access | Primary | Secondary |
---|---|---|
👁️ View | name, lcs | |
💡 Manage | lane, indication | msg_pattern, msg_num |
🔧 Configure | controller | pin |
Each state must be assigned to a separate IO pin on a controller. The pin specifies a digital output to activate that state.
For DMS type signs using NTCIP, the pin is not relevant; any number 3+ will work. Instead, message pattern is used to specify the MULTI for the indication. Message number (2-65535) can be used to speed up activation, by caching the message in the controller's message table.