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, with more than one controller per comm link.

Axis PTZ

The axisptz protocol can be used for PTZ control of Axis cameras. The default scheme is http. Multi-drop is not supported. One camera can be associated with each controller, using IO pin 1.

Canoga

The canoga protocol can collect vehicle detection data, with vehicle logging instead of binned data. The default scheme is tcp. Multi-drop is supported with drops 0 - 15 (backplane) or 128 - 255 (EEPROM). Up to 4 detectors can be associated with each controller, using IO pins 1 - 4.

CAP

The Common Alerting Protocol CAP is used for polling external feeds such as the Integrated Public Alert and Warning System IPAWS. [Alerts] can be used to automatically post weather and other messages to Dynamic Message Signs. For IPAWS, this requires an HTTPS URI provided by the Federal Emergency Management Agency and a controller set to ACTIVE condition.

CBW

The cbw protocol can be used for beacons, using a Control-By-Web controller. The default scheme is http. Multi-drop is not supported. Depending on the model, up to 16 beacons can be associated with each controller.

The IO Pins are outputs for controlling relays.

ClearGuide

The clearguide protocol can be used for to connect with a ClearGuide external system feed.

Cohu

The cohu protocol can be used for PTZ control of Cohu cameras. The default scheme is tcp. Multi-drop is supported with drops 1 - 223. One camera can be associated with each controller, using IO pin 1.

Din-Relay

The dinrelay protocol can be used for changeable LCS or beacons, using a DLI Din-Relay. The default scheme is http. Multi-drop is not supported. Up to 8 indications can be associated with each controller, using IO pins 1 - 8.

DMS-XML

DMS-XML is a protocol for legacy DMS control systems. The default scheme is tcp, with multi-drop (0-65535).

DR-500

The Houston Radar DR-500 doppler radar can be used to collect speed data only. The default scheme is tcp. Multi-drop is not supported. Only one detector can be associated with each controller, using IO pin 1.

DXM

The Banner Engineering DXM magnetometer can detect vehicle presence for parking area monitoring. The default scheme is tcp. Multi-drop is not supported. Up to 76 detectors can be associated with each controller, using IO pins 11 - 86.

E6

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.

G4

The G4 protocol can collect vehicle detection data, including vehicle counts, occupancy, speed and vehicle classification. The default scheme is tcp. Multi-drop is supported with drops 0 - 65535. Up to 12 detectors can be associated with each controller, using IO pins 1 - 12.

Inc-Feed

The incfeed protocol can be used to interface IRIS with an external system that generates incidents. Periodically, IRIS will poll the URI (using http) for incidents.

Incident Feed Format

The external system should respond with an ASCII text file, with one line per active incident.

Each line should contain 7 fields, separated by comma characters , and terminated with a single newline character \n (ASCII 0x0A). The fields are:

1. incident ID
2. type: CRASH, STALL, ROADWORK or HAZARD
3. incident detail: may be blank, or one of the incident detail names
4. latitude
5. longitude
6. camera ID: may be blank, or the ID of a camera to view the incident
7. direction: NB, SB, EB or WB

Latitude and longitude define coördinates using the WGS 84 datum.

Infinova

The infinova protocol can be used for PTZ control of Infinova cameras. The default scheme is tcp. Multi-drop is supported with drops 1 - 254. One camera can be associated with each controller, using IO pin 1.

Manchester

The manchester protocol can be used for PTZ control of some older cameras. The default scheme is udp. Multi-drop is supported with drops 1 - 1024. One camera can be associated with each controller, using IO pin 1.

MnDOT-170

170 style controllers running the MnDOT 170 firmware can support several types of devices:

There are two versions of the protocol supported:

MonStream

The monstream protocol can be used for switching of monstream video monitors. The default scheme is udp. Multi-drop is not supported. Up to 16 video monitors can be associated with each controller, using IO pins 1 - 16.

Msg-Feed

The msgfeed protocol can be used to interface with an external system that generates DMS messages. Periodically, IRIS will poll the URI (using http) for DMS messages.

The external system should respond with an ASCII text file, with one line per message to be deployed. Each line contains 3 fields: dms, message and expire, separated by tab characters \t (ASCII 0x09), and terminated with a single newline character \n (ASCII 0x0A).

V66E37\tSNOW PLOW[nl]AHEAD[nl]USE CAUTION\t2022-10-02 11:37:00-05:00

dms: Name of the sign to deploy, which must have the hashtag referenced by a DMS action. Additionally, that action must be associated with the current phase of an active action plan. The message pattern of the DMS action must be a feed action tag. For example, if the msgfeed Comm Link name is XYZ, then the pattern must be [feedXYZ].

multi: Message to deploy, using the MULTI markup language. Each line of the message must exist in the pattern's library. This check allows only "administrator-approved" messages, but it can be disabled by changing the msg_feed_verify system attribute to false. WARNING: only disable this check if the message feed host is fully trusted, and there is no possibility of man-in-the-middle attacks.

expire: Date/time when the message will expire, using RFC 3339 full-date / full-time separated by a space. The message will not be displayed after this time. Leave expire blank to cancel a previous message.

Natch

Advanced Traffic Controllers (ATC) using the Natch protocol can support several types of devices:

• alarms
• beacons
• changeable LCS
• ramp meters
• vehicle detection

NTCIP

National Transportation Communications for Intelligent transportation system Protocol is supported for several different device types:

• DMS — NTCIP 1203
• LCS, using DMS for lane control
• RWIS — NTCIP 1204
• vehicle detection — NTCIP 1202
• GPS — NTCIP 1204

There are three supported variants:

Org815

The org815 protocol can be used to collect rwis data from an Org-815 precipitation sensor. The default scheme is tcp. Multi-drop is not supported. One device can be associated with each controller, using IO pin 1.

Pelco D

The pelcod protocol can be used for PTZ control of Pelco cameras. The default scheme is udp. Multi-drop is supported with drops 1 - 254. One camera can be associated with each controller, using IO pin 1.

Pelco P

The pelcop protocol can be used for camera keyboard control from Pelco keyboards. The default scheme is tcp. Multi-drop is not supported. No devices need to be associated with the keyboard controller.

RedLion

The redlion protocol can be used for GPS data from RedLion modems. The default scheme is tcp. Multi-drop is not supported. One GPS modem can be associated with each controller, using IO pin 1.

SierraGX

The sierragx protocol can be used for GPS data from SierraGX modems. The default scheme is tcp. Multi-drop is not supported. One GPS modem can be associated with each controller, using IO pin 1.

SmartSensor

There are three SmartSensor protocols for collecting vehicle detection data from Wavetronix sensors. The 105 and 125 HD protocols collect binned vehicle counts, occupancy, speed and vehicle classification. The 125 vlog protocol logs event data for every vehicle. The default scheme is tcp.

STC

The stc protocol can be used for gate arm control for Smart Touch gate arms. The default scheme is tcp. Multi-drop is supported with drops 1 - 99. One gate arm can be associated with each controller, using IO pin 1.

Streambed

The streambed protocol is for flow stream configuration with a streambed server. The default scheme is tcp. Multi-drop is not supported. Up to 150 flow streams can be associated with each controller, using IO pins.

Vicon

The vicon protocol can be used for PTZ control of Vicon cameras. The default scheme is udp. Multi-drop is supported with drops 1 - 254. One camera can be associated with each controller, using IO pin 1.