Specifications

GEMINI
2
Traffic Outstation Handbook
667/HB/32600/000 Page 52 Issue 11
An OMCU Event has to be continuously active for the configured active debounce
time, before a report is written to the Fault Log, indicating the OMCU Event is active.
Conversely, an OMCU Event has to be continuously inactive for the configured
inactive debounce time, before a similar report is written to the Fault Log, indicating
the OMCU Event is inactive. The Instation then processes these events via a
decision tree and takes the appropriate configured response (Switch Override).
The RMS Instation can request a Switch Override at the OMCU, when the OMCU
Event becomes active. The OMCU will reply to the Switch Override Request with a
message indicating that the Switch Override Request has been received.
When the OMCU starts the Switch Override (start time is reached) and report
generation is enabled, a report will be written to the Fault Log to identify the start of
the Switch Override.
The Switch Override will remain active for a fixed period of time, or until cancelled
from the Instation.
A similar report will be generated at the end of the Switch Override, (end time is
reached, assuming that an indefinite override period has not been specified) if
enabled.
4.2.13 SieClass Vehicle Classifier Facility
The Vehicle Classification facility provides classification of vehicles by length into a
maximum of 14 user specified length categories. Vehicles that exceed the length in
the longest length category are assigned to the “Unassigned” length category.
Vehicles that are not able to be measured (e.g. transit one of the loops only) have
zero length and are assigned to the “Unmeasured” category. Each length category is
configurable to provide user names for the categories, e.g. “Car / Small Van”.
Vehicles may be logged on up to 8 loop pairs distributed across up to 4 sites, each
site containing up to 8 lanes. It is recommended that the facility use standard
SDE/SA loops of typically, 2m loop length and 3.5m loop separation. The ST4R loop
detector is also recommended.
It is important to note that differently sized loop pair configurations must be assigned
to different sites.
The vehicles may be individually logged in the Operations Log when they are
detected as VC events. The VC event identifies the vehicle type, length, speed,
headway and action taken (if any) on detecting the vehicle. Each value may be
optionally configured for inclusion / exclusion from the VC event. VC event logging
may be enabled / disabled for any given lane within a given site via the configuration
download.
The user is able to freely specify up to 32 detection conditions via special
conditioning e.g. vehicles of between 2m and 5.5m in length occurring at a given site