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.
| Protocol | Default Scheme | Drops | Device Types |
|---|---|---|---|
| ADEC TDC | tcp |
1-255 | vehicle detection |
| Axis | http |
1 | camera |
| Banner DXM | tcp |
1 | vehicle detection |
| CampbellCloud | https † |
1 | external |
| Canoga | tcp |
0-15; 128-255 ⸸ | vehicle detection |
| CAP-IPAWS | https |
1 | external |
| CAP-NWS | https |
1 | external |
| CBW | http |
1 | alarm, beacon |
| Central Park | https |
1 | external |
| ClearGuide | http |
1 | external |
| Cohu | tcp |
1-223 | camera |
| Cohu Helios | tcp |
1-223 | camera |
| DLI DIN Relay | http |
1 | beacon |
| DMS-XML | tcp |
0-65535 | DMS |
| DR-500 | tcp |
1 | vehicle detection |
| HySecurity STC | tcp |
1-99 | gate arm |
| Inc-Feed | http |
1 | external |
| Infinova D | tcp |
1-254 | camera |
| Manchester (AD) | udp |
1-1024 | camera |
| MnDOT-170 4-bit | tcp |
1-15 | MnDOT devices |
| MnDOT-170 5-bit | tcp |
1-31 | MnDOT devices |
| MonStream | udp |
1 | video |
| Msg-Feed | http |
1 | external |
| Natch | tcp |
1 | MnDOT devices |
| NDORv5 | tcp |
1 | gate arm |
| NDOT Beacon | tcp |
1 | beacon |
| NTCIP A | udp |
1 | NTCIP devices |
| NTCIP B | tcp |
1-8191 | NTCIP devices |
| NTCIP C | tcp |
1 | NTCIP devices |
| ONVIF | http |
1 | camera |
| OSi ORG-815 | tcp |
1 | weather sensor |
| Pelco D | udp |
1-254 | camera |
| Pelco P | tcp |
1 | camera keyboard |
| RedLion | tcp |
1 | GPS |
| RTMS Echo | http † |
1 | vehicle detection |
| RTMS G4 | tcp |
0-65535 | vehicle detection |
| SierraGX | tcp |
1 | GPS |
| Sierra SSH | tcp |
1 | GPS |
| SmartSensor 105 | tcp |
1-9999 | vehicle detection |
| SmartSensor 125 | tcp |
1-65534 | vehicle detection |
| Streambed | tcp |
1 | flow stream |
| Transcore E6 | udp |
1 | tag reader |
| Vicon | udp |
1-254 | camera |
† Communicates using pollinator service
⸸ Backplane: 0-15, EEPROM: 128-255
MnDOT Devices
Old style 170 controllers using MnDOT-170 and Advanced Traffic Controllers (ATC) using Natch support 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 |
NTCIP Devices
Multiple device types are supported by NTCIP:
| Device Type | Standard | IO Pins |
|---|---|---|
| Alarm | 1201 | 11-?? |
| DMS | 1203 | 1 |
| GPS | 1204 | 2 |
| LCS | 1203 | 1 |
| Vehicle detection | 1202 | 1-?? |
| Weather sensor | 1204 | 1 |
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.
-
CampbellCloud: external weather sensor data feed
-
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 a URI provided by the Federal Emergency Management Agency.
-
CAP-NWS: CAP feed from National Weather Service NWS. Alerts can be used to automatically post weather messages to DMS.
-
Central Park: external parking area system for vehicle detection. Use the "Data per stall" endpoint (URI ending in
/integration/spot). -
ClearGuide: external DMS message feed
-
DMS-XML: external DMS system (legacy)
-
Inc-Feed: external incident feed
-
Msg-Feed: external message feed