IRIS
Intelligent Roadway Information System
Protocols
A comm link communicates with remote controllers using one of several protocols, each of which supports specific device types. Some also support multi-drop addressing, allowing for more than one controller per comm link.
Device Control
These protocols support multiple device types:
| Device Type | NTCIP | Natch | MnDOT 170 |
|---|---|---|---|
| Alarm | ☑️ | ☑️ | ☑️ |
| Beacon | ☑️ | ☑️ | |
| DMS | ☑️ 1203 | ||
| GPS | ☑️ 1204 | ||
| LCS | ☑️ 1203 | ☑️ | ☑️ |
| Ramp meter | ☑️ | ☑️ | |
| Vehicle detection | ☑️ 1202 | ☑️ | ☑️ |
| Weather sensor | ☑️ 1204 |
| Protocol | Default Scheme | Drops |
|---|---|---|
| NTCIP A | udp |
1 |
| NTCIP B | tcp |
1-8191 |
| NTCIP C | tcp |
1 |
| Natch | tcp |
1 |
| MnDOT v4 | tcp |
1-15 |
| MnDOT v5 | tcp |
1-31 |
Advanced Traffic Controllers (ATC) using Natch and older 170-style controllers using MnDOT-170 can have many devices:
| Device Type | # |
IO Pins |
|---|---|---|
| Beacon | 1 | 2 |
| Ramp meter | 2 | 2 - 3 |
| LCS | 3 | 19 - 36 |
| Vehicle detection | 24 | 39 - 62 |
| Alarm | 10 | 70 - 79 |
Camera Control
Several protocols for camera control / PTZ are supported:
| Protocol | Default Scheme | Drops | IO Pins |
|---|---|---|---|
| ONVIF | http |
1 | 1 |
| Axis | http |
1 | 1 |
| Cohu | tcp |
1-223 | 1 |
| Infinova | tcp |
1-254 | 1 |
| Pelco D | udp |
1-254 | 1 |
| Vicon | udp |
1-254 | 1 |
| AD Manchester | udp |
1-1024 | 1 |
Video Control
Various video systems are supported:
| Protocol | Default Scheme | Drops | IO Pins |
|---|---|---|---|
| MonStream | udp |
1 | 1-16 |
| Streambed (flow stream) | tcp |
1 | 1-150 |
| Pelco P keyboard | tcp |
1 | N/A |
Gate Arm Control
Two protocols for gate arm control are supported.
| Protocol | Default Scheme | Drops | IO Pins |
|---|---|---|---|
| HySecurity STC | tcp |
1-99 | 1 |
| NDORv5 | tcp |
1 | 1-8 |
Beacon Control
| Protocol | Model | Default Scheme | Drops | IO Pins |
|---|---|---|---|---|
| CBW | http |
1 | varies | |
| X-WR-1R12 | 1 | |||
| X-301 | 1-2 | |||
| X-401 | 1-2 | |||
| X-310 | 1-4 | |||
| X-410 | 1-4 | |||
| X-WR-10R12 | 1-10 | |||
| X-332 | 1-16 | |||
| DLI DIN Relay | http |
1 | 1-8 | |
| NDOT Beacon | tcp |
1 | 1 |
Vehicle Detection
There are a few types of vehicle detection data:
- Binned, time-based counts, occupancy, speed, classification
- Event, per-vehicle, arrival time, speed, classification
- Presence, suitable for parking area monitoring
| Protocol | Default Scheme | Drops | IO Pins | Data Type |
|---|---|---|---|---|
| ADEC TDC | tcp |
1-255 | 1 | event |
| Banner DXM | tcp |
1 | 11-86 | presence |
| Canoga | tcp |
0-15; 128-255 † | 1-4 | event |
| Central Park | https ‡ |
1 | 1-64 | presence |
| DR-500 | tcp |
1 | 1 | binned |
| RTMS G4 | tcp |
0-65535 | 1-12 | binned |
| RTMS G4 vlog | tcp |
0-65535 | 1-12 | event |
| SmartSensor 105 | tcp |
1-9999 | 1-8 | binned |
| SmartSensor 125 HD | tcp |
1-65534 | 1-8 | binned |
| SmartSensor 125 vlog | tcp |
1-65534 | 1-8 | event |
† Backplane: 0-15, EEPROM: 128-255
‡ Use "Data per stall" endpoint (URI ending in /integration/spot)
GPS Devices
| Protocol | Default Scheme | Drops | IO Pins |
|---|---|---|---|
| RedLion | tcp |
1 | 1 |
| SierraGX | tcp |
1 | 1 |
| Sierra SSH | tcp |
1 | 1 |
Weather Data
Some protocols can be used to collect weather sensor data.
| Protocol | Default Scheme | Drops | IO Pins | Notes |
|---|---|---|---|---|
| OSi ORG-815 | tcp |
1 | 1 | precipitation |
| Campbell Cloud | http |
1 | 1 | separate service |
External Systems
Some protocols allow IRIS to poll external systems periodically using http
or https. Typically, a single controller should be assigned and made
ACTIVE, but no devices need to be connected to IO pins.
| Protocol | Description |
|---|---|
| CAP-IPAWS | CAP feed from Integrated Public Alert and Warning System IPAWS. Alerts can be used to automatically post weather and other messages to DMS. This requires an https URI provided by the Federal Emergency Management Agency. |
| CAP-NWS | CAP feed from National Weather Service. Alerts can be used to automatically post weather messages to DMS. |
| ClearGuide | ClearGuide external system feed |
| Inc-Feed | External incident feed |
| Msg-Feed | External message feed |
| DMS-XML | Legacy DMS system (drops 0-65535) |
Tag Readers
The e6 protocol can be used for collecting data from Transcore tag readers.
The default scheme is udp. Multi-drop is not supported. One tag reader
can be associated with each controller, using IO pin 1.