Specifications

GEMINI
2
Traffic Outstation Handbook
667/HB/32600/000 Page 53 Issue 11
travelling in excess of 80kph. Of these 32 detection conditions, up to 16 may be
selected for statistical collection purposes.
NOTE: Non-vehicle classifier special conditioning mnemonics may be used in the
definition of the detection conditions, however they should not be mixed with the
vehicle classifier special conditioning mnemonics.
Vehicle detections may be collected over a user specified averaging period of
between 1 and 60 minutes to be summarised in the Operation Log as TD events by
average speed, average occupancy and average headway. The average speed,
headway and occupancy values may be recorded on a site or a lane basis or be
omitted entirely. The statistic categories increment during the averaging period to
reflect the occurrence of user defined detection conditions. These category counts
are presented in the Operations Log alongside the summary information in the TD
event described above. The statistic categories may be omitted from the TD event.
The data collection is synchronised to the minute boundary. The time stamp
associated with the TD event corresponds to the end of the averaging period.
TD event generation may be enabled / disabled via the configuration download.
When vehicle detection satisfies a detection condition, a DC event may be recorded
in the Operations Log identifying the detection condition. It is possible for a single
vehicle detection to satisfy more than one detection condition (depending on how the
detection conditions have been defined) and hence there may be more than one DC
event associated with single vehicle detection.
The DC, VC and TD events in the Operations Log may be selectively uploaded to the
RMS Instation for analysis.
The occurrence of a user-defined condition may be used to force the activation of
one or more OMU outputs (up to a maximum of 16 allocated across 2 output ports)
to trigger an action in an external device such as a traffic controller. A configurable
text message may also be presented to one or more message signs such as UVMS
or a SIESPACE sign. A sign may be connected to the 141 serial port or one of the
available RS485 serial ports on a 1 to 1 basis. The text message is displayed for a
configurable period and may be subsequently blanked by a blanking message
applicable to the sign or be replaced by a second text message. NOTE: If a second
text message is output to the sign, the message will remain on the sign until another
action causes the same sign to be addressed. Alternatively, the sign configuration
could perform a self-blanking using a suitable inactivity timeout.
Confirmation checks are carried out to detect the absence / presence of an expected
input state arising from an output activation. The absence of an expected input state
for a configured period generates a fault in the Fault Log. The presence of the
expected input state for a configured period clears the fault (if the fault is present).
The RMS Instation operator may manually reset the fault.
NOTE: Confirmation checks are not performed on sending text messages to a sign.