Specifications

ManualsBrandsSiemens ManualsKitchen AppliancesHB 131. 10 B

GEMINI

Traffic Outstation Handbook

667/HB/32600/000 Page 1 Issue 11

Siemens Mobility and Logistics, Traffic Solutions

Sopers Lane

Poole

Dorset

BH17 7ER

SYSTEM/PROJECT/PRODUCT: GEMINI

Traffic Outstation

SIEMENS

GEMINI

TRAFFIC OUTSTATION

HANDBOOK

Prepared: Paul Cox Eric Burdis Jim Ballantine Mark Retallack

Function: Traffic Engineering

THIS DOCUMENT IS ELECTRONICALLY HELD AND APPROVED

Issue

Change Ref.

Date

Mantis 6633,

6978

TS004779

23-July-2009

TS005210

22-February-2010

TS005647

29-November-2010

TS006234

09-November-2011

TS006588

09-July-2012

The information contained herein is the property of Siemens plc and is supplied

without liability for errors or omissions. No part may be reproduced or used except as

authorised by contract or other written permission. The copyright and the foregoing

restriction on reproduction and use extend to all media in which the information may

be embodied.

Summary of content (367 pages)

PAGE 1
GEMINI2 Traffic Outstation Handbook Siemens Mobility and Logistics, Traffic Solutions Sopers Lane Poole Dorset BH17 7ER SYSTEM/PROJECT/PRODUCT: GEMINI2 Traffic Outstation SIEMENS GEMINI2 TRAFFIC OUTSTATION HANDBOOK Prepared: Paul Cox Eric Burdis Jim Ballantine Mark Retallack Function: Traffic Engineering THIS DOCUMENT IS ELECTRONICALLY HELD AND APPROVED Issue Change Ref.
PAGE 2
GEMINI2 Traffic Outstation Handbook SAFETY WARNINGS In the interests of health and safety, when using or servicing this equipment, the following instructions must be noted and adhered to: (i) Only Skilled or Instructed personnel with relevant technical knowledge and experience, who are also familiar with the safety procedures required when dealing with modern electrical or electronic equipment, are to be allowed to use and/or work on the equipment.
PAGE 3
GEMINI2 Traffic Outstation Handbook Maintenance Provision (MP) 1. Product Reference Siemens GEMINI2 Traffic Outstation 2. Specifications The GEMINI2 Traffic Outstation is designed to meet the following Highways Agency specifications: MCE 0152 Monitoring and Control of Traffic Equipment via the Public Switched Telephone Network.
PAGE 4
GEMINI2 Traffic Outstation Handbook 6. Warning Use of components other than those permitted above or modifications or enhancements that have not been authorised by Siemens Traffic Controls may invalidate Type Approval of this product.
PAGE 5
GEMINI2 Traffic Outstation Handbook CONTENTS 1. INTRODUCTION .................................................................................................. 13 1.1 PURPOSE .......................................................................................................... 13 1.2 SCOPE ............................................................................................................... 13 1.3 RELATED DOCUMENTS ................................................................................
PAGE 6
GEMINI2 Traffic Outstation Handbook 3.10.1 Communications Channel 1 TR2210 (TR0141) Port .............................. 37 3.10.2 Communications Channel 2 (Modem Port) ............................................. 37 3.10.3 Communications Channel 3 (Handset) ................................................... 37 3.10.4 Communications Channel 4 (Ethernet) ................................................... 37 3.10.5 RS485 Communications Interfaces ........................................................
PAGE 7
GEMINI2 Traffic Outstation Handbook 5.5 CABLE AND WIRING ......................................................................................... 80 5.6 INTERFACING ................................................................................................... 80 5.6.1 Serial Linked ............................................................................................. 81 5.6.2 Freestanding............................................................................................. 81 5.6.
PAGE 8
GEMINI2 Traffic Outstation Handbook 9. MOVA ................................................................................................................ 140 9.1 MOVA INTRODUCTION .................................................................................. 140 9.2 MOVA FREESTANDING INTERFACES .......................................................... 142 9.2.1 Detector Inputs and Push-Buttons .......................................................... 143 9.2.2 Confirms and Controller Ready Inputs .
PAGE 9
GEMINI2 Traffic Outstation Handbook 10.4.4 GPRS Configuration ............................................................................. 182 10.5 INSTALLATION .............................................................................................. 183 10.5.1 PAKNET Interface Connector ............................................................... 183 10.5.2 PAKNET Radio Pad Power .................................................................. 183 10.5.3 Door Switch .............................
PAGE 10
GEMINI2 Traffic Outstation Handbook 13.6.12 Stage Sequence Fault (FLT SEQ) ...................................................... 236 13.6.13 Site Power Fail/Clearance (FLT SOF/SON) ....................................... 236 13.6.14 Controller Stuck Fault (FLT STK) ....................................................... 236 13.6.15 Vehicle Absence Failure (FLT VAF) ................................................... 237 13.6.16 Vehicle Presence Failure (FLT VPF) ............................................
PAGE 11
GEMINI2 Traffic Outstation Handbook 13.20.4 UTMC OTU Test / Maintenance Commands ...................................... 324 13.20.5 UTMC OTU Output Override Commands ........................................... 325 13.20.6 UTMC OTU HIOCC Facility Commands ............................................. 326 13.20.7 UTMC OTU Environmental Sensor/SIETAG Interface Commands .... 327 13.20.8 UTMC OTU Engineering Commands ................................................. 328 13.21 UTMC VMS COMMAND TABLE .............
PAGE 12
GEMINI2 Traffic Outstation Handbook TABLE OF FIGURES Figure 1 – Overview ................................................................................................. 15 Figure 2 – Basic OMCU to ST700 or ST800 ............................................................ 19 Figure 3 – Basic OMCU to Any Other Controller ...................................................... 19 Figure 4 – MOVA to ST700 or ST800 ......................................................................
PAGE 13
GEMINI2 Traffic Outstation Handbook 1. INTRODUCTION 1.1 PURPOSE This document is intended to provide sufficient information to the user to install, configure and maintain the GEMINI2 Traffic Outstation, either as a Siemens RMS OMCU, a Bus Processor, a Siemens MOVA unit, a SieClass (Vehicle Classifier) unit, a UTMC OTU, a VMS unit or a Graphos unit. The GEMINI2 Traffic Outstation is based on the original GEMINI Traffic Outstation with an upgraded processor card containing additional memory.
PAGE 14
GEMINI2 Traffic Outstation Handbook Fault Finding and Troubleshooting Guide Handbook ..................... 667/HE/31200/000 1.
PAGE 15
GEMINI2 Traffic Outstation Handbook 2. PRODUCT DESCRIPTION 2.1 INTRODUCTION Figure 1 is an overview of a Siemens GEMINI2 Traffic Outstation (shown with two LMU I/O boards and a single Bus / MOVA I/O board) and how it connects as a system.
PAGE 16
GEMINI2 Traffic Outstation Handbook The RMS OMCU application monitors TR2210 intersection and ‘mid-block’ (or ‘stand-alone’) pedestrian controllers and most pre-TR0141/TR2210 traffic controllers. It reports back faults and status of both the Traffic Controller and the OMCU itself to the Instation. The configuration for the intersection to be monitored is downloaded from the Instation to the OMCU. See section 4.1 for more information on the OMCU application.
PAGE 17
GEMINI2 Traffic Outstation Handbook The UTMC OTU enables second-by-second control of the associated Traffic Controller by the central UTC system, using open-standard protocols. See section 2.2.5 for outline layout, section 4.3.1 for overview, section 5.1.2 for installation prerequisites and cabling, and section 11 for configuration details. The Graphos application is a new strategy for control of a cluster of Signs (up to 4 signs). See section 4.2.14 for more information on the Graphos application.
PAGE 18
GEMINI2 Traffic Outstation Handbook 2.2 Siemens GEMINI2 Traffic Outstation Equipment 2.2.1 The GEMINI2 Platform The GEMINI2 Traffic Outstation is based on the original GEMINI Traffic Outstation with an upgraded processor card containing additional memory and a new version of firmware. The GEMINI2 Traffic Outstation provides additional functionality in terms of dual-stream MOVA 5 and future expansion capability.
PAGE 19
GEMINI2 Traffic Outstation Handbook A number of optional kits are available which, when added to the Basic OMCU, allow connection to any Controller. MOVA and BUS Processing kits are also available. The sections 2.2.2 etc. that follow show the combinations of facilities and the way the components are connected. It is also possible to upgrade an existing “old style” OMU/MOVA/Bus Processor with a new GEMINI2 processor card to provide all the new facilities described in this handbook.
PAGE 20
GEMINI2 Traffic Outstation Handbook 2.2.3 MOVA 2 A standard PSTN GEMINI Traffic Outstation will function as a MOVA unit if the appropriate ‘enable code’ is used. See Figure 4 below for details of the MOVA connections to an ST700 or ST800 Controller; connections to all other controllers are shown in Figure 5. Lamp Supply Cable – see Section 5.6.2.3 Traffic Outstation (MOVA) TR0141 Cable – see Section 5.6.
PAGE 21
GEMINI2 Traffic Outstation Handbook 2.2.4 Bus Processing Bus Processing may be performed by adding the Bus / MOVA I/O card and Cable kit (667/1/28856/000) to the GEMINI2 Traffic Outstation. If OMCU functionality is also required, also add the cable kit(s) described in Figure 3. Digital I/O – see Section 5.6.3 RS485 to Reader/Beacon/RTIG – see Section 5.6.4 Traffic Outstation (Bus Processing + OMCU) Any Controller As Figure 3 if OMCU functionality is required.
PAGE 22
GEMINI2 Traffic Outstation Handbook The UTMC Outstation unit described in Figure 7 may be used with other types of Controllers by adding the UTMC O/S Kit (667/1/30625/000). Traffic Outstation (UTMC OTU) UTMC Detectors, Force and Confirm Bits – see Section 11.2 Any Other Controller Figure 8 – UTMC OTU to Any Other Controller 2.2.
PAGE 23
GEMINI2 Traffic Outstation Handbook (c) (d) (e) (f) (g) (h) (i) (j) (k) (l) (m) Three programmable RS232 Serial communications Ports: - Handset Port. - Traffic controller TR2210 (TR0141) Port. - Modem Port. Battery backed-up Real Time Clock.
PAGE 24
GEMINI2 Traffic Outstation Handbook (h) (i) (j) 5V Failing Warning Circuit (monitors the battery supported DC input supply for a low level). Zero crossover Circuit (not normally used). Board address decoding (board expansion facilities). *Option available for 48V AC (3RD Party ELV) signals. See below. 2.4.2 3RD Party ELV AC LMU I/O Board A modified version of the LMU I/O Board has been created, known as the 3RD Party ELV AC LMU I/O Board.
PAGE 25
GEMINI2 Traffic Outstation Handbook inputs from, any traffic controller configured with a UTC/MOVA/DUSC interface. It also provides MOVA and DUSC with its detector inputs that can be connected in parallel to the controller. Normally, modem power is provided by the CPU card. Alternatively, if required, this board can also provide this supply, with a choice of three different voltages offered.
PAGE 26
GEMINI2 Traffic Outstation Handbook 2.6.2 The GSM Modem Unit 2.6.2.1 SQ864-GPRS Modem Unit As of late 2011 Gemini units will be fitted with a Sequoia SQ864-GPRS modem where connection through the GSM network is required. As its name suggest the modem can also provide a GPRS connection. The SQ-864 is quad band EGSM 850/900/1800/1900MHz which is compatible with all GSM mobile networks in the UK.
PAGE 27
GEMINI2 Traffic Outstation Handbook GPRS Connection The modem may also be used to provide a GPRS connection where Gemini is used for carpark and VMS applications. In order to work with GPRS some service specific information must be entered into the Gemini by way of handset commands (this is normally done by way of a script file). First enter the GPRS attachment and context AT commands into the Gemini MOS command:mos=at+cgatt=1;+cgdcont=1,ip,APN Where APN is the mobile service provider access point name eg.
PAGE 28
GEMINI2 Traffic Outstation Handbook If a GSM OMCU is used, an aerial must be fitted close to the Controller. The aerial feeder is a fixed length of 15 metres. Where no signal pole is available within approximately 8 metres of the controller cabinet, suitable aerial mounting arrangements will need to be provided. There is also a top level Outstation variant which provides for a case mounted antenna (667/1/32600/005). There is one LED on the TC35 GSM unit.
PAGE 29
GEMINI2 Traffic Outstation Handbook Due to its size, it is not possible to mount this modem onto the back of the GEMINI2 power supply unit. During installation of the Outstation a suitable place should be found within the associated cabinet.
PAGE 30
GEMINI2 Traffic Outstation Handbook 2.6.5 The MC35 GPRS Modem The Siemens MC35 Terminal unit is a GSM modem capable of GPRS transmission. The MC35 supports GPRS transmission up to 21.4Kbps per time slot. Interfaces to the unit include an RS232 data port, power and an FME (male) aerial connector. An integrated SIM card reader is included. A diagnostic LED shows the current state of the unit. The MC35 Diagnostic LED is used to indicate the following states.
PAGE 31
GEMINI2 Traffic Outstation Handbook 2.8 THE EXPANSION BUS This is a set of 64 way plugs and sockets. Each board in the system has a connector fitted that passes through the PCB and becomes a socket on the component side and a plug on the solder side. The boards connect using these sockets and plugs through an additional connector, starting with the processor, by plugging an I/O board into its socket, then an I/O board into the I/O's socket and so on.
PAGE 32
GEMINI2 Traffic Outstation Handbook 3. SPECIFICATIONS 3.1 INTRODUCTION The following sections describe the full Electrical, Mechanical, Environmental, Isolated Outputs, Isolated Extra Low Voltage Inputs, Isolated Low Voltage Inputs, Analogue Inputs and Communications specifications of the unit. 3.2 ELECTRICAL For Graphos see the Graphos Product Handbook 667/HB/31200/000 (Section 2.1 – Electrical Specification) for the Electrical information. 3.2.
PAGE 33
GEMINI2 Traffic Outstation Handbook 3.2.3 Power Dissipation Low power CMOS devices are used throughout the unit to keep the power dissipation as low as possible. Total power consumption 8.0 W typical (using maximum configuration of 3 x I/O boards and battery float charging) 3.2.
PAGE 34
GEMINI2 Traffic Outstation Handbook See the Graphos Product Handbook 667/HB/31200/000 (Section 4 – System Elements) for Graphos mechanical information. 3.4 ENVIRONMENTAL Temperature -15°C to +60°C ambient Humidity 20% to 95% non condensing at 40°C 3.5 ISOLATED OUTPUTS GEMINI2 Traffic Outstation boards are each equipped with a number of relay isolated outputs, two change-over contacts on the CPU board, four normally open contacts on an LMU I/O board and 16 change-over contacts on a BUS / MOVA I/O board.
PAGE 35
GEMINI2 Traffic Outstation Handbook 3.6 DIGITAL INPUTS The CPU board supports 8 x TR2210 (TR0141) compliant digital inputs. Each LMU I/O board supports 16 x fully software configurable photo-coupled extra low voltage isolated digital inputs and each BUS / MOVA I/O board supports 48 x TR2210 (TR0141) compliant digital inputs.
PAGE 36
GEMINI2 Traffic Outstation Handbook The High Voltage inputs have the following input electrical characteristic: Input Impedance: 99k Absolute Max. Applied Voltage: 580V RMS Min. Voltage to guarantee signal on condition: 40V RMS Isolation Voltage : 2500V RMS Note: Graphos has no ZXO signal, therefore mains monitoring is not performed. 3.8 3RD PARTY ELV AC INPUTS The 3RD Party ELV AC LMU I/O Board supports 10 photo-coupled 48Vrms AC inputs rather than mains voltages.
PAGE 37
GEMINI2 Traffic Outstation Handbook 3.10 COMMUNICATIONS The processor board contains three serial RS232 and one Ethernet communication port. The variant /000 of the Bus / MOVA I/O board contains four RS485 communications interfaces which are described on the following page. These interfaces are fully software programmable in terms of their transmission characteristic. The three RS232 and the single Ethernet communications interfaces are shown on 667/GA/32600/000 in Appendix B and are as follows: 3.10.
PAGE 38
GEMINI2 Traffic Outstation Handbook Interface : RS485 Isolation : 1000V Link Type: Master on Multi-drop line Master Bias: 560 Bias Resistors Line Termination: Two 120 667/HB/32600/000 Terminating Resistors (selected by switches) Page 38 Issue 11
PAGE 39
GEMINI2 Traffic Outstation Handbook 3.10.
PAGE 40
GEMINI2 Traffic Outstation Handbook 4. FACILITIES 4.1 INTRODUCTION 2 The Siemens GEMINI Traffic Outstation provides a flexible multi-function hardware and software platform, with sufficient interfaces to allow sophisticated monitoring and control tasks to be developed and executed. Section 4.2 highlights the facilities available on the GEMINI2 Traffic Outstation when used as a Siemens RMS OMCU, Bus Processor or Car Park Count OMCU. Section 4.2.9 describes the DUSC facility. Section 4.2.
PAGE 41
GEMINI2 Traffic Outstation Handbook Vehicle Classification Facility Local bus priority facilities in association with the Siemens SIETAG reader system or certain TfL London Bus Priority beacons or an RTIG radio link. Vehicle selective access control, also in association with the Siemens SIETAG reader system or certain TfL London Bus Priority beacons or an RTIG radio link. Graphos Facility Any fault detected is logged and reported to the Instation identifying the type (i.e. signal lamp or detector, etc.
PAGE 42
GEMINI2 Traffic Outstation Handbook 4.2.3 Controller Status Checks Under this category the following is provided: (a) (b) (c) (d) (e) (f) (g) (h) (i) Controller mode, i.e. Manual, Fixed-Time, V.A Controller Stuck – applicable to Fixed-Time mode only Controller ignoring demands – including call/cancel and filter demands Controller mains supply re-applied. Conflicting Phase Greens Stage sequencing fault External signal active, e.g.
PAGE 43
GEMINI2 Traffic Outstation Handbook other equipment such as Traffic Controllers, via up to 16 isolated relay contacts (expandable to 48 with additional I/O boards). Several levels of filtering may be configured in each Bus Processor. Filtering options range from specific access for uniquely identified vehicles to all vehicles of a particular operator. Access may be restricted by time of day and individual or groups of vehicles may be blacklisted. 4.2.5.
PAGE 44
GEMINI2 Traffic Outstation Handbook This facility uses the standard 141 serial cable 667/1/26579/000 to connect the unit to the OTU handset port. Once the OMCU – OTU cable is connected and LDV=4 entered, the XXC command can be used to gain access to the OTU handset (XXO is used to revert to the OMCU handset). The OTU must be appropriately configured to provide the throughput to the UTC using the following handset commands.
PAGE 45
GEMINI2 Traffic Outstation Handbook As a more integrated product, the traffic controller provides some of the facilities that previously only the OMCU could provide. The controller performs the lamp monitoring and detector fault monitoring, passing any fault information to the OMCU for reporting to the RMS Instation. The controller’s digital inputs and mains states, etc.
PAGE 46
GEMINI2 Traffic Outstation Handbook Command Operation (when enhanced link enabled) CST Displays the current stage for stream 0, received from the controller via the serial link MDE Displays the controller mode for stream 0, received from the controller via the serial link MSI Displays the OMCU mains state inputs (not controller greens) DIP Displays the OMCU digital inputs (not controller inputs) SOB & SOP Displays/sets the OMCU digital outputs (not controller outputs) 4.2.
PAGE 47
GEMINI2 Traffic Outstation Handbook 4.2.9 DUSC Facility The DUSC facility is very similar to CLF used in the ST800/700 traffic controller, whereby plans are introduced at specific times of day and each plan cycles through a configured sequence of groups in a repeating cycle. At each configured group time within the cycle, the OMCU activates the specified outputs to influence the controller movements (See DUSC user handbook for full details). Plans are introduced by the timeswitch table i.e.
PAGE 48
GEMINI2 Traffic Outstation Handbook 4.2.9.1 Force Bit Control Installation SIGNAL HEADS LOCAL HANDSET RMS PROTOCOL TO INSTATION RS232 GREEN CONFIRMS STAGE CONFIRMS PSTN or GSM OPTION: GPS Receiver (clock) TRAFFIC CONTROLLER OMCU (with LGD Battery & MODEM) FORCE BITS RS232/ RS485 DETECTOR LOOPS Figure 10 – Force Bit Control Set-up Figure 10 shows how an OMCU can be set up for Force Bit control. This type of setup is used when the controller provides a UK standard UTC style interface.
PAGE 49
GEMINI2 Traffic Outstation Handbook 4.2.9.2 ST800/700 Enhanced Serial Link Control Installation SIGNAL HEADS LOCAL HANDSET RMS PROTOCOL TO INSTATION PSTN or GSM OPTION: GPS Receiver (clock) RS232 OMCU (with LGD Battery & MODEM) FORCE BITS, CONFIRMS, ETC TRAFFIC CONTROLLER ST800 ENHANCED SERIAL LINK RS485 DETECTOR LOOPS Figure 11 – ST800/700 Enhanced Serial Link Control Set-up Figure 11 shows how an OMCU can be set up for the ST800/700 Enhanced Serial Link control.
PAGE 50
GEMINI2 Traffic Outstation Handbook 4.2.9.3 Detector Control Installation SIGNAL HEADS LOCAL HANDSET RMS PROTOCOL TO INSTATION PSTN or GSM OPTION: GPS Receiver (clock) RS232 GREEN CONFIRMS TRAFFIC CONTROLLER OMCU (with LGD Battery & MODEM) RS232/ RS485 DEMAND BITS DETECTOR LOOPS Figure 12 – Detector Control Set-up Figure 12 shows how an OMCU can be set up for Detector control. This set-up is only used where controllers are not to UK standard with a UTC interface, i.e.
PAGE 51
GEMINI2 Traffic Outstation Handbook For each interval completed a report is generated and stored in the Operations Log. When the final interval has been completed and report generation has been enabled, a report is written to the Fault Log to indicate that Flow Logging has been completed and is ready for uploading. More accurate values of flow data can be obtained at 2 or 3 sites, using the N+1 Count Data. The flow threshold would be for the complete carriageway rather than individual lanes.
PAGE 52
GEMINI2 Traffic Outstation Handbook 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.
PAGE 53
GEMINI2 Traffic Outstation Handbook 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.
PAGE 54
GEMINI2 Traffic Outstation Handbook Vehicle absence / presence faults are generated in the Fault Log if a vehicle is not detected over a loop / detected over a loop for longer than the configured absence / presence time. Both fault types are automatically cleared by the OMU. The RMS Instation operator may manually reset both fault types. The Vehicle Classification facility also supports a loop pair fault algorithm.
PAGE 55
GEMINI2 Traffic Outstation Handbook The Graphos facility can generate and report the following failures to RMS: (a) (b) (c) (d) (e) (f) (g) (h) (i) (j) (k) Communication Fault/Power Fail – automatically cleared. Invalid set message – manually cleared. Receiving data from unconfigured signs – manually cleared. Radar has not triggered – manually cleared. Voltage on LDB board is missing – manually cleared. LED driver board system fault – manually cleared. Invalid picture number in last Set – manually cleared.
PAGE 56
GEMINI2 Traffic Outstation Handbook Graphos Rx/Tx N Either wire or radio engineering RS232 is fitted but not both 5 Optional 5 5 9 18 SK2 SMA 2 PL3 P Gemini CPU PL5 PL4 9 PL2 667/1/26608/001 Modem PSTN or GPRS Q 2 R RJ11 PL7 6 AGD 200 ‘Live Wire’ Vehicle Over-Speed Detector M 2 C 5 A Battery Control Circuitry Toroidal Transformer 1:10 2 Battery M 418/4/42314/010 2 BT Cable M PSU 13.8 V d.c. 40W 24 way Term.
PAGE 57
GEMINI2 Traffic Outstation Handbook 4.2.15 RMS Firmware Download Facility The Siemens GEMINI2 Traffic Outstation supports the remote download of firmware from an RMS Instation over a PSTN link. The Outstation configures its modem for 19200,8,N,1 operation. This facility is not supported when an RMS Instation is connected to the local handset. The download of firmware is initiated by the RMS operator.
PAGE 58
GEMINI2 Traffic Outstation Handbook 4.3 UTMC FACILITIES 4.3.1 UTMC OTU Facility 2 The Siemens GEMINI Traffic Outstation can also be configured to provide the Traffic Controller Outstation facility for a UTMC system. In this mode the outstation is configured either as shown in Figure 14 or as shown in Figure 15. In both cases the OTU must be connected to a suitable network modem, usually via the CPU card Ethernet interface.
PAGE 59
GEMINI2 Traffic Outstation Handbook SIGNAL HEADS LOCAL HANDSET RS232 EHANCED SERIAL LINK Ethernet ST700/800 TRAFFIC CONTROLLER UTMC OTU DSL MODEM SCOOT INPUTS UTMC PROTOCOL TO INSTATION SCOOT DETECTOR LOOPS VA DETECTOR LOOPS Figure 15 – ST800/700 Semi-Integral UTMC OTU Set-up Figure 15 shows how an OTU can be set up for the ST800/700 Enhanced Serial Link control. It shows all the information being fed between the OTU and the traffic controller, via the ST800/700 Enhanced Serial Link.
PAGE 60
GEMINI2 Traffic Outstation Handbook RS485 Bus Channel 0 Sign 0 Sign 1 CH #0 Ethernet DSL Modem or other Ethernet Converter Local Handset Gemini Traffic Outstation CH #1 RS232 Sign 2 CPU Card Bus Mova Expansion I/O Card PSU & Chassis Sign 3 RS485 Bus Channel 1 Figure 16 – UTMC VMS System Overview When the Outstation is configured in UTMC VMS mode, UTMC VMS messages from the SIESpace Instation arrive via the Ethernet connection.
PAGE 61
GEMINI2 Traffic Outstation Handbook When a fault or other defined event is detected, it is logged at the unit and a call is made to the Instation to report the occurrence. If required, particular types of fault or event can be configured as “non urgent” so that these are logged but not reported to the Instation, unless a more urgent fault is detected or a call is made from the Instation.
PAGE 62
GEMINI2 Traffic Outstation Handbook designates the OMCU as an IP outstation can be downloaded from the instation and from that point the OMCU will operate as normal but via an Ethernet link.
PAGE 63
GEMINI2 Traffic Outstation Handbook 5. INSTALLATION WARNING THIS EQUIPMENT MAY ONLY BE INSTALLED IN A RESTRICTED ACCESS LOCATION BY SIEMENS TRAFFIC CONTROLS OR BY TRAINED PERSONNEL. AUTHORISED INSTALLER MUST ENSURE THAT INSTALLATION OF THIS EQUIPMENT DOES NOT INTERFERE OR DEGRADE THE DESIGN SPECIFICATION OF THE HOST EQUIPMENT IN ANY WAY WHATSOEVER. ENSURE THAT THE UNIT IS NOT CONNECTED TO THE PSTN LINE DURING INSTALLATION AND SWITCH OFF ALL MAINS TO CABINET PRIOR TO STARTING.
PAGE 64
GEMINI2 Traffic Outstation Handbook 5.1.1 Users Responsibilities It is the responsibility of the user (or purchasing authority) to: (a) Provide a Telephone connection (if PSTN connection with the unit is required). (b) If the unit is to be installed within an existing controller – ensure that adequate space is available for mounting the unit (dimensions are given in section 2.1) and fixings are available. An ancillary outer-case will be required if space is not available (see section 5.7 on page 100).
PAGE 65
GEMINI2 Traffic Outstation Handbook (d) A maximum of 3 off blanking plate kits 667/1/31614/000 or ST4R Detectors 667/1/27663/000 or any combination thereof are also required. That is: If there are no detectors, 3 off blanking plates are required. If there is one detector, 2 off blanking plates are required. If there are two detectors, 1 off blanking plate is required. If there are three detectors, no blanking plates are required.
PAGE 66
GEMINI2 Traffic Outstation Handbook Rear of UTMC OTU with 2U modem shelf (earlier metalwork), modem, modem power supply, and supply socket fitted 667/HB/32600/000 Page 66 Issue 11
PAGE 67
GEMINI2 Traffic Outstation Handbook 5.1.2.
PAGE 68
GEMINI2 Traffic Outstation Handbook INSTALLATION CHECKLIST STEP OMCU C/P BUS MOVA 1 OMCU C/P BUS MOVA 2 OMCU C/P BUS 3 OMCU C/P BUS 4 5 6 7 8 OMCU C/P BUS MOVA OMCU C/P BUS MOVA OMCU C/P OMCU — — — — — BUS — — — 9 — — BUS MOVA 10 OMCU — — — 11 OMCU C/P BUS MOVA 12 OMCU C/P BUS MOVA 13 OMCU — — — 14 OMCU — — 15 OMCU — — 16 OMCU C/P — 17 OMCU C/P — 18 19 — — — — BUS 20 — — — 21 22 23 24 — — — OMCU C/P BUS OMCU C/P BUS
PAGE 69
GEMINI2 Traffic Outstation Handbook INSTALLATION CHECKLIST (contd.
PAGE 70
GEMINI2 Traffic Outstation Handbook INSTALLATION CHECKLIST (contd.) STEP VC UTMC OTU UTMC VMS FUNCTION REFERENCE 33 — — — COMMISSION THE MOVA APPLICATION 9.5 34 VC — — Commission the Vehicle Classifier unit 6.3 OTU 35 — — Commission the UTMC OTU unit 6.3 VMS Commission the UTMC VMS unit 36 — — 6.3 THE REST OF SECTION 5 TAKES YOU THROUGH THE STEPS IN THE INSTALLATION CHECKLIST (FROM THE PREVIOUS PAGES) IN MORE DETAIL… Section 5.
PAGE 71
GEMINI2 Traffic Outstation Handbook Caution On each I/O board, only one of the three board address switches should be in the ‘ON’ position while the unit is powered.
PAGE 72
GEMINI2 Traffic Outstation Handbook On the Processor board, insertion of the modem power lead into the relevant connector socket in the Modem Power connector PL3 selects which supply to use as follows.
PAGE 73
GEMINI2 Traffic Outstation Handbook On the BUS / MOVA (Digital) I/O board, the modem power is available on a separate connector PL4 which is located near the front right-hand corner of the board. The orange wire is not required as the necessary power switching for use during initialisation is built into this board. If the modem power leads are fitted with berg crimps, then the crimps should be cut approximately in half to form a bullet which can be inserted into this connector.
PAGE 74
GEMINI2 Traffic Outstation Handbook 5.2.3 50/60 Hz Operation Applicable To: OMCU and C/P 6 5.2.3 Set up 50/60Hz operation selection The Outstation can operate with 50Hz or 60Hz mains’ supplies, for export purposes. The mains timing reference circuit is provided by the Outstation power supply unit in most applications. If the Processor PCB is added as an upgrade to an old style OMCU, then refer to section 5.8 for further details. 5.2.4 120/230V AC Operation Applicable To: OMCU only 7 5.2.
PAGE 75
GEMINI2 Traffic Outstation Handbook Connector Wire Colour Position 1 Brown Description Mains supply live 2 Blue Mains supply Neutral 3 Green / Yellow Mains supply Earth 4 Link to 5 for 110V working 5 Link to 4 for 110V working 6 Red High voltage I/P No. 2 for Lamp Supply Monitoring (see Notes. Not to be connected when using the 3RD Party ELV AC LMU I/O Board) 7 Yellow High voltage I/P No.
PAGE 76
GEMINI2 Traffic Outstation Handbook The total termination impedance (the ‘sum’ of both ends) for each channel should be 60 . For links up to 250m the I/O board can provide the total termination. If a longer link is required, the far end of the link should be terminated with 120 and the I/O board set to only provide a 120 termination. The total termination impedance must be calculated, based on the terminal impedance provided by all other equipment connected to the communication channel.
PAGE 77
GEMINI2 Traffic Outstation Handbook 5.2.8 RAM Battery Back-Up Applicable To: All Products 11 Switch the RAM battery on and confirm the watchdog link is correctly installed. 5.2.8 RAM Battery The processor board has a Lithium Coin Cell battery fitted to support the RAM and Real Time Clock during periods of mains’ failure. When dispatched from the factory this battery has a small piece of film inserted between itself and the associated holder. This must be ‘pulled out’ to enable the battery to function.
PAGE 78
GEMINI2 Traffic Outstation Handbook section 5.3, or use an Additional Outercase. If the Additional Outercase method is used, then additional installation work is required (see section 5.7 on page 100). (d) If the unit is to be mounted in such a way that the ‘Battery Warning Label’ is visible on the bottom of the unit then the following modifications are necessary. This is to ensure that the battery is not operating upside down.
PAGE 79
GEMINI2 Traffic Outstation Handbook Expansion kits (either LMU I/O cards and/or Bus/MOVA (Digital) I/O cards) to support the required application. Before the Outstation can be installed, these expansion kits require assembling to the Basic Unit. To assemble these expansion kits to the Basic unit, use the methods and Items Lists on General Assembly drawing 667/GA/32600/000 in Appendix B.
PAGE 80
GEMINI2 Traffic Outstation Handbook Modem Supply (PL3 pin2 [+12V] and PL3 pin3 [0V. If the I/O cable 667/1/26585/010 is used then a dedicated supply connection is provided. Figure 18 – Radio Clock Unit 5.5 CABLE AND WIRING Applicable To: All Products It is not possible to adopt a standard cable routing, as mention in 5.1, but the following guidelines should be adhered to: (a) (b) Secure all cables to the controller frame or other suitable locations.
PAGE 81
GEMINI2 Traffic Outstation Handbook This is not an exhaustive list and other applications exist. The following sub-sections detail the methods for the interfaces mentioned... The connection methods to be used when monitoring Controller Lamp Voltages are as described in sections 5.6.1 and 5.6.2 below: 5.6.1 Serial Linked 13 5.6.1 Connect serial linked Gemini The basic Lamp Monitoring configuration requires a TR0141 cable connection back to the Controller (see Figure 2 on page 19).
PAGE 82
GEMINI2 Traffic Outstation Handbook Each controller signal output, which is to be monitored, requires one current sensor as described on the RMS Instation computer printout. Examples of output types to be monitored are indicated in the following list.
PAGE 83
GEMINI2 Traffic Outstation Handbook Figure 19 – Current Sensor Connection Volt a ge F ir st Cu r r en t In pu t on I/O Boa r d 1 Mon it or in g (Secon d Cu r r en t In pu t on Boa r ds 2 & 3) Tr a n sfor m er In pu t on I/O Ber g Min i-La t ch Boa r d 1 H ou sin g P ola r isa t ion P ip Or a n ge Wir e 1 33 34 2 E n d Con n ect or Socket P osit ion s Not Used a t bot h en ds Red Wir e m u st be Con n ect ed t o t op of Con n ect or Wh it e Wir e To La m p Su pply Not used on serial linked OMCU Volt a ge
PAGE 84
GEMINI2 Traffic Outstation Handbook P ola r in g P ip 33 1 34 2 E n d Con n ect or Socket P osit ion s Not Used Con n ect or Viewed fr om t he BACK The mini latch housing is the Analogue connector 508/4/26138/002, which plugs into PL1 on the I/O Board. The PL1 circuit allocation is as follows: Pin No.
PAGE 85
GEMINI2 Traffic Outstation Handbook 5.6.2.2 Lamp Supply Sensor Connection Applicable To: OMCU Only 15 Connect lamp supply sensor 5.6.2.2 The lamp supply sensor (Voltage Monitoring Transformer) should be connected to the cabinet lamp supply as follows and the sensor should be mechanically secured to a suitable location within the controller. See the previous page for details on PL1.
PAGE 86
GEMINI2 Traffic Outstation Handbook Mains Voltages: Pin No.
PAGE 87
GEMINI2 Traffic Outstation Handbook Notes: * The 3RD Party ELV AC LMU I/O Board does not accept mains voltages of any kind. Monitoring of controller mains can be achieved by using High Voltage Input 1 on the PSU connector as described in section 5.2.4†. ** NEUTRAL here refers to 3RD Party ELV Neutral and this cable is to be connected to the same ELV Neutral block used by the signals. There must be NO connection between mains and ELV neutrals anywhere within the controller.
PAGE 88
GEMINI2 Traffic Outstation Handbook 5.6.2.4 Digital Monitor Connections (LMU I/O Board Only) Applicable To: OMCU, VC and Car Park 17 Connect digital monitors cables 5.6.2.4 Digital Monitor points within the controller should be connected using the cableform 667/1/26585/000 as detailed on the Instation Computer Printout. The connectors for these cableforms are on the underside of the board; i.e. on the opposite side to the mains’ states connector.
PAGE 89
GEMINI2 Traffic Outstation Handbook the controller input triggering the ‘reverse circuits’ (For example, when monitoring 24V signals, if the signal voltage goes above the common voltage by between 1V to 3V the 5V monitor circuit will be triggered.) Controller +24V supply OMCU Inputs Controller Input Optional Diode 0V There are two Extra Low Voltage cableforms to each I/O Board. They are made from ribbon cable and therefore need to be spilt as required to suit the routing at the installation.
PAGE 90
5V 24V GEMINI2 Traffic Outstation Handbook + + + + + + + + + + + + + + + + - PORT 0 – PL4 Connector Ribbon and Pin Wire Colour PL4 PIN 1 BROWN PL4 pin 2 RED PL4 pin 3 ORANGE PL4 pin 4 YELLOW PL4 pin 5 GREEN PL4 pin 6 BLUE PL4 pin 7 VIOLET PL4 pin 8 SLATE PL4 pin 9 WHITE PL4 pin 10 BLACK nd PL4 pin 11 2 BROWN PL4 pin 12 2nd RED PL4 pin 13 2nd ORANGE PL4 pin 14 2nd YELLOW PL4 pin 15 2nd GREEN PL4 pin 16 2nd BLUE Input No.
PAGE 91
GEMINI2 Traffic Outstation Handbook 5.6.3 CPU and BUS / MOVA (Digital) I/O Applicable To: Bus, VC, UTMC OTU and UTMC VMS 18 Connect CPU & Bus Processor digital I/O 5.6.3 The Processor and Bus / MOVA (Digital) I/O Boards have different digital input and output connectors than the LMU I/O board described in section 5.6.2.4.
PAGE 92
GEMINI2 Traffic Outstation Handbook Bus / MOVA (Digital) I/O Board Connector PL1 and PL2 Connector Allocation Pin Board 1 PL1 Board 1 PL2 Pin Board 2 PL1 Board 2 PL2 1 Buffered I/P 1 Buffered I/P 25 1 Buffered I/P 49 Buffered I/P 73 2 Buffered I/P 2 Buffered I/P 26 2 Buffered I/P 50 Buffered I/P 74 3 Buffered I/P 3 Buffered I/P 27 3 Buffered I/P 51 Buffered I/P 75 4 Buffered I/P 4 Buffered I/P 28 4 Buffered I/P 52 Buffered I/P 76 5 Buffered I/P 5 Buffered I/P 29 5 Buffered I/P 53 Buffered I/P 77 6 Buffered
PAGE 93
GEMINI2 Traffic Outstation Handbook The OMCU application can also read the digital inputs on any Bus / MOVA I/O boards that are fitted. The following diagrams and tables summarise where the OMCU’s 64 detector inputs are located when various combinations of CPU and I/O boards are fitted.
PAGE 94
GEMINI2 Traffic Outstation Handbook Viewed from Rear 1st I/O Board CPU Board PL5 CPU card only OMCU Detectors 1–8 9 – 16 17 – 24 25 – 32 33 – 40 41 – 48 49 – 56 57 – 64 Board No. Type CPU SOP 2 SOP 2 57 - 64 33 - 56 PL2 PL1 PL5 CPU card + 1 Bus/MOVA I/O Board Connector and Pins PL5 7 – 15 Board No.
PAGE 95
OMCU Detectors On Bus / MOVA I/O Boards 667/HB/32600/000 Page 95 PL4 Ribbon 16W PL3 Ribbon 16W PL1 Berg 50W I/O Board #1 – LMU I/O Board PL2 Berg 50W 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 1 LMU I/O Board plus 1 Bus / MOVA I/O Board 1 BRO 2 RED 3 ORA 4 YEL 5 GRN 6 BLU 7 VIO 8 SLA 9 WHI 10 BLA 11 BRO 12 RED 13 ORA 14 YEL 15 GRN 16 BLU 1 BRO 2 RED 3 ORA 4 YEL 5
PAGE 96
GEMINI2 Traffic Outstation Handbook 5.6.4 BUS / MOVA Board RS485 Serial Ports Applicable To: Bus, VC and UTMC VMS 19 5.6.4 Connect RS485 cables, e.g. for SIETAG The following Table shows the RS485 connector pin assignments on each BUS/MOVA I/O board.
PAGE 97
GEMINI2 Traffic Outstation Handbook ‘B’ connects to SIETAG backplane pin 15 Ensure that the SIETAG backplane is fitted with a link connecting the through-hole immediately above silk screen number “14” to the through-hole above silk screen number “21”. The line termination resistors on the BUS/MOVA I/O board should be set to 120 described in section 5.2.5. as The RS485 serial port configuration must match the external device settings to receive and transmit data.
PAGE 98
GEMINI2 Traffic Outstation Handbook Group 3 – Green Volts Detect Signals. (b) Earth Continuity The EARTH CONTINUITY RESISTANCE must not exceed 0.5 on exposed metal parts of the unit when measured with reference to the EARTHING TERMINATION POINT of the cabinet. (c) Check On Integrity of Neutral Connections (OMCU Applications) With the controller switched on and cycling and a multi-meter set to measure AC volts – measure the voltage between each green feed and neutral, when the green is off.
PAGE 99
GEMINI2 Traffic Outstation Handbook Note: This cable is required if MOVA is to use the enhanced serial link to an ST800/700 even if the OMCU application is not required, see section 4.2.6 on page 44. 5.6.9 TR0141 Cable Installation (OTU) Applicable To: Bus Only 26 Connect 141 cable to OTU handset port (req’d for BUS if using OTU link) 5.6.9 The Outstation communicates with an OTU using ribbon cable 667/1/26579/000.
PAGE 100
GEMINI2 Traffic Outstation Handbook 5.6.11 Connect Unit Support Battery Applicable To: All Applications 30 5.6.11 Connect unit support battery To connect the Unit Support Battery, the fuse (Part Number 518/4/90285/008 supplied separately), is inserted in the Battery Fuse Holder on the front panel. If the unit is to be left not powered after installation, this fuse should be removed and stored in a safe place, ready for insertion during commissioning. 5.6.
PAGE 101
GEMINI2 Traffic Outstation Handbook 5.8 INSTALLATION OF THE GEMINI2 UPGRADE Existing 3U OMUs can be enhanced by replacing the old CPU card with a GEMINI2 version. All the wiring to the existing interface cards (LMU I/Os and BUS/MOVA I/Os) need not be disturbed.
PAGE 102
GEMINI2 Traffic Outstation Handbook 5.8.1.1 50/60Hz Operation (LMU I/O Board only) Applicable To: OMCU and C/P If the Processor is added as an upgrade to an old style OMCU then the associated LMU I/O card will supply the timing reference signal. This will not normally require any change to the existing wiring. However the following information is provided should any changes be necessary.
PAGE 103
GEMINI2 Traffic Outstation Handbook The Power Supply operates from 85 to 265V AC, and therefore needs no external setup to operate from either 120 or 230V AC. However the OMCU’s lamp monitor Zero Crossover circuit requires setting. This setting is achieved by selecting the correct input connector socket on the High Voltage cable form. If 120V setting is required, change the setting as detailed, before applying mains. The relevant connector socket positions for the 120V or 230V setting is described below.
PAGE 104
GEMINI2 Traffic Outstation Handbook 6. TRAFFIC OUTSTATION COMMISSIONING WARNING THIS EQUIPMENT MAY ONLY BE COMMISSIONED BY SIEMENS TRAFFIC CONTROLS OR BY TRAINED PERSONNEL. ENSURE THAT THE UNIT IS NOT CONNECTED TO THE PSTN LINE JACK UNIT AT THE COMMENCEMENT OF COMMISSIONING TESTS. For Graphos see the Graphos Product Handbook 667/HB/31200/000 for the Commissioning Sequence (Section 14).
PAGE 105
GEMINI2 Traffic Outstation Handbook 6.1 INTRODUCTION The checklist on the following pages should be used to commission the Outstation applications if they are required. The checklist should be followed in sequence unless a particular step is not required. Refer to the ‘OMCU’, ‘Car Park [Count OMCU]’, ‘Bus [Processor]’, VC [Vehicle Classifier], UTMC OTU and UTMC VMS columns to determine whether the step applies to the type of unit being commissioned.
PAGE 106
GEMINI2 Traffic Outstation Handbook OMCU Car Park BUS 4    5    6    7    8    9    10  11  12  667/HB/32600/000 CHECK Ensure the RAM backup battery and the Support battery are both connected. If the modem has an on/off switch, ensure it is switched on. Plug the handset into the HANDSET connector and hit the key a number of times, until the sign-on message ‘SIEMENS OMCU’ or the prompt character is displayed.
PAGE 107
GEMINI2 Traffic Outstation Handbook OMCU Car Park BUS 13   14   15   16  17  18  667/HB/32600/000 CHECK REFERENCE DUSC Facility Check (If Configured) The OMCU provides the ability to copy the detector inputs through to the outputs. This is controlled using the ‘COD’ handset command. This allows the VA operation to be maintained even though the OMCU is unconfigured. The BUS/MOVA I/O board provides changeover output relays.
PAGE 108
GEMINI2 Traffic Outstation Handbook OMCU Car Park BUS 19   20   21   22   23   24   25   667/HB/32600/000 CHECK If the telephone line exists, plug in a telephone and dial the OMCU number, which should give engaged tone. If the telephone works, and there is someone at the Instation, it is possible to check the download and monitoring. Normally the Instation is notified that the OMCU is ready to be tested at a later date. Go to step 29.
PAGE 109
GEMINI2 Traffic Outstation Handbook OMCU 26 27 28  Car Park      29 30 BUS  667/HB/32600/000 CHECK Support Battery Check With the battery connected, check that when the power is removed from the OMCU, the OMCU within one minute dials the Instation and a mains failure report’ is logged on the Instation system printer. If the battery does not support the OMCU, then charge the Support battery for at least 10 minutes by restoring the mains and repeat this test.
PAGE 110
GEMINI2 Traffic Outstation Handbook OMCU 31  32  33  34  Car Park BUS      667/HB/32600/000 CHECK Conclusion Of Tests Remove the Dual Outlet telephone adapter from the Line Jack Socket and insert the OMCU Telephone connector. Check that the OMCU Fault Log is clear using the FLT handset code. Disconnect any other test equipment.
PAGE 111
GEMINI2 Traffic Outstation Handbook 6.3 Vehicle Classifier, UTMC OTU and VMS COMMISSIONING CHECKLIST VC 1  2  3 UTMC OTU  UTMC VMS   667/HB/32600/000 CHECK Installation check Check all the connections have been installed in accordance with the Customer Supplied instructions.
PAGE 112
GEMINI2 Traffic Outstation Handbook VC UTMC OTU UTMC VMS  4 5    6    7    8    9    10    667/HB/32600/000 CHECK REFERENCE Variable Message Sign Checks The variable message sign being controlled should be checked to verify that: a) The control logic is functioning; b) The communications interface to the Outstation is working; c) Any associated sign solar cells are working.
PAGE 113
GEMINI2 Traffic Outstation Handbook VC 11  UTMC OTU UTMC VMS   12 13  14  15  16  17  18  19  667/HB/32600/000 CHECK REFERENCE If the outstation is connected to a TR 0141 controller handset port, check that the controller can be interrogated through the Outstation using the XXC and XXO handset 13.8 commands. Since the outstation is not configured at this stage the SCT code may be used to initialise the UART to the appropriate configuration.
PAGE 114
GEMINI2 Traffic Outstation Handbook 20 21 22 UTMC OTU UTMC VMS CHECK REFERENCE  After a period of time, the Comms LED (LP2) on the processor should go off, indicating that the call has terminated. The Outstation Handset “Operating Mode” should show “MONITORING” (OPM : 0) in which case continue with the following steps. If OPM is not 0, go back to step 15. 13.
PAGE 115
GEMINI2 Traffic Outstation Handbook VC 23  24 UTMC OTU UTMC VMS      25   26   667/HB/32600/000 CHECK REFERENCE Software Licence Codes Vehicle Classifier: The VC software licence code is controlled by the Instation and is downloaded along with the VC configuration data. The licence code is obtained from Poole. UTMC OTU & VMS: The UTMC software licence codes are supplied from Poole and before this can be 13.20.
PAGE 116
GEMINI2 Traffic Outstation Handbook VC UTMC OTU UTMC VMS  27  28 29  30    31    32    667/HB/32600/000 CHECK Configuring the UTMC OTU Configuration of the OTU Outstation is described section 11. Configuring the UTMC VMS Configuration of the VMS Outstation is described in section 12. Conclusion Of Tests Remove the Dual Outlet telephone adapter from the Line Jack Socket and insert the Outstation Telephone connector.
PAGE 117
GEMINI2 Traffic Outstation Handbook 7. MAINTENANCE WARNING THE MAINS SUPPLY TO THE UNIT AND THE ASSOCIATED TRAFFIC CONTROLLER MUST BE SWITCHED OFF PRIOR TO ANY MAINTENANCE WORK BEING CARRIED OUT ON THE UNIT. ANY UNAUTHORISED USE OF COMPONENTS OR MODIFICATIONS OR ENHANCEMENTS WITHOUT PRIOR APPROVAL BY SIEMENS TRAFFIC CONTROLS COULD RESULT IN INVALIDATION OF THE TYPE APPROVAL OF THIS PRODUCT. THIS EQUIPMENT MAY ONLY BE MAINTAINED BY SIEMENS TRAFFIC CONTROLS OR BY TRAINED PERSONNEL.
PAGE 118
GEMINI2 Traffic Outstation Handbook bullet connections, which provide protection against accidental contact with mains potentials, remain. General instruction – applicable to all versions of the Outstation: During a unit change out, the Green Voltage Detector connections can be left intact on cableform 667/1/26586/000, which connects to the controller (as defined in section 5.6.2.3 which starts on page 85). 7.
PAGE 119
GEMINI2 Traffic Outstation Handbook 7.3.
PAGE 120
GEMINI2 Traffic Outstation Handbook Possible Causes for Fast Flashing System LED Application Possible Condition Any The outstation may be unconfigured, monitoring turned off, config data invalid or config being downloaded. Check the OPM value to determine if any of these conditions apply. Also check FLT and FLG for any active/logged faults. Any The outstation may have detected a ‘hard’ error condition, e.g. repeated failure of internal software check.
PAGE 121
GEMINI2 Traffic Outstation Handbook (b) Check the tightness of all interface cables and re-tighten where necessary. (c) Check the condition of the interface cables; that there is no chafing of the insulation and that the general condition of the insulation is good. Replace any damaged or worn cables. (d) Check the mechanical tightness of the main securing screws of unit and retighten where necessary. (e) Restore mains power to the controller and the unit.
PAGE 122
GEMINI2 Traffic Outstation Handbook I/O Expansion Kit (with cable & voltage transformer) ............................. 667/1/28853/001 I/O Expansion Kit (with cable only) ......................................................... 667/1/28853/000 Bus/MOVA I/O Expansion Kit (with cables) ............................................ 667/1/28856/000 Digital I/O Expansion Kit (with cables)....................................................
PAGE 123
GEMINI2 Traffic Outstation Handbook PSU I/P 85-264V AC O/P 13.65V 3A ..................................................... 667/7/30613/000 Voltage Sensor (for Welsh Office only) .................................................. 667/7/25172/500 7.6.2 Interface Cables OMCU/LMU High Voltage Cable ............................................................ 667/1/26586/800 BUS / MOVA I/O Cable (Without T/Bs) .................................................. 667/1/26585/005 BUS / MOVA I/O Cable (TfL).........
PAGE 124
GEMINI2 Traffic Outstation Handbook 8. FAULT FINDING AND REPAIR For Graphos see the Fault Finding and Troubleshooting Guide 667/HE/31200/000 for the Fault Finding and Repair Sequence. 8.1 INTRODUCTION The following section comprises of battery, telephone connection information and warnings, together with quick reference tables, to provide a guide to aid fault tracing on the unit for first line maintenance purposes: Table 8.4.1 : PSTN Comms. Failures Table 8.4.2 : GSM Comms. Failures Table 8.4.
PAGE 125
GEMINI2 Traffic Outstation Handbook 8.2 BATTERY FAILURES If one of the batteries has failed, it must be replaced with the specified battery or equivalent (see section 7.6.3 on page 123). Exercise great care when handling old batteries, which may be leaking, and during replacement of new ones, to ensure no damage occurs to either. WARNING OLD BATTERIES MUST BE DISPOSED OF IN ACCORDANCE WITH THE ‘CONTROL OF SUBSTANCES HAZARDOUS TO HEALTH REGULATIONS 1988’.
PAGE 126
GEMINI2 Traffic Outstation Handbook 8.4 COMMUNICATIONS FAILURES 8.4.1 TABLE FOR PSTN COMMUNICATIONS FAILURES Note that use of the term ‘modem’ applies equally to PSTN modems and GSM modules. Symptom Possible Diagnosis Action to Check Diagnosis (a) Unit will not answer Instation calls PSTN line out of order or disconnected Check the line by disconnecting the unit from the line socket and inserting a telephone handset. Try a voice call to and from the service depot.
PAGE 127
GEMINI2 Traffic Outstation Handbook Symptom Possible Diagnosis (b) Unit will not dial Instation Instation Number incorrect. Action to Check Diagnosis Check the configured Instation telephone number is correct using CTN and TNP (section 13.7 on page 239). If correct replace modem, if not reload the unit’s configuration. Unit in a retry sequence Check the unit is in a retry sequence using RSC and RTR (section 13.7 on page 239). If not replace modem.
PAGE 128
GEMINI2 Traffic Outstation Handbook Symptom Possible Diagnosis Action to Check Diagnosis (d) Unit to Instation link communications not completed or intermittent PSTN line intermittent Check using handset codes CDC, CTR and MDC, what types of faults and the rate of their occurrences (see section 13.7). If this information indicates an intermittent PSTN line, request a line check by the appropriate authority.
PAGE 129
GEMINI2 Traffic Outstation Handbook 8.4.2 TABLE FOR GSM COMMUNICATIONS FAILURES Note that use of the term ‘modem’ applies equally to GSM modules. Symptom Possible Diagnosis (a) Unit will not answer Instation calls Action to Check Diagnosis GSM Network Check with the Service provider (e.g. BT Cellnet or Vodaphone), that the unavailable or blocked. particular SIM Card / phone number are enabled for DATA and are not in any way blocked.
PAGE 130
GEMINI2 Traffic Outstation Handbook Symptom Possible Diagnosis (a) Unit will not answer Instation calls (continued) GSM Modem failed Action to Check Diagnosis Check if the modem’s ‘‘ON” LED is lit. (NB On the GSM modem this is a small LED on the top surface of the modem near the SIM Card entry point. Once installed it is likely to be on the modem surface nearest the Outstation PSU plate and so its reflection may be easier to see.
PAGE 131
GEMINI2 Traffic Outstation Handbook Symptom Symptom (b) Unit will not dial Instation (c) Download failure (d) Unit to Instation link communications not completed or intermittent 667/HB/32600/000 Possible Diagnosis Action to Check Diagnosis Unit power failed Check that the mains input to the unit is present. If yes, replace the unit’s PSU. If no, then check the mains supply and fuses. Modem incompatible with Instation modem Check that the unit and Instation are using compatibly configured modems.
PAGE 132
GEMINI2 Traffic Outstation Handbook Symptom Possible Diagnosis Action to Check Diagnosis Modem intermittent. Check using handset codes CDC, CTR and MDC, what types of faults and the rate of their occurrences (see section 13.7). If this information indicates an intermittent modem, check if the modem power and data connectors are securely inserted. If yes, then replace the modem and its cables. If the fault still persists, replace the unit.
PAGE 133
GEMINI2 Traffic Outstation Handbook Symptom (a) Unit will not communicate with the Instation (continued) Possible Diagnosis Action to Check Diagnosis Examine Fault Log Check using handset codes FLG and FLT for PAKNET related comms faults (PCF see section 13.6.2). This will give information on when faults have occurred. Processor to PAKNET connections Check the modem to processor connections; check that the cable is plugged into PL2 on the processor and into the modem.
PAGE 134
GEMINI2 Traffic Outstation Handbook 8.4.4 TABLE FOR UTMC COMMUNICATIONS FAILURES Note that use of the term ‘modem’ applies equally to DSL Modem modules Symptom Possible Diagnosis (a) Unit will not communicate with the Instation Telephone cable disconnected Check the telephone connections to the modem and the Line connection socket. If modem is powered, and connections OK, replace the modem. Ethernet cable disconnected Check the Ethernet cable connections between the modem and the processor card.
PAGE 135
GEMINI2 Traffic Outstation Handbook 8.4.5 Modem Compatibility GEMINI2 Firmware Any Any 667/HB/32600/000 Outstation Modem Dynalink PKS-5600 TC35 GSM RMS Instation Pace PMC33.
PAGE 136
GEMINI2 Traffic Outstation Handbook 8.5 TABLE FOR EQUIPMENT FAILURES Symptom (a) Unit not operating Possible Diagnosis Software watchdog has Check the state of the Watchdog LED (see section 7.3 which starts on page triggered 118), if lit power down and power up the unit to cause a reset. If Watchdog LED lights again, replace the processor board. If the Watchdog LED lights again, replace the unit.
PAGE 137
GEMINI2 Traffic Outstation Handbook Symptom Possible Diagnosis Action to Check Diagnosis (a) Unit not operating (continued) Software not running If the System LED is flashing and an error message is being continually output on the handset, this indicates that an internal check has repeatedly failed. Power down and power up the unit to cause a reset. If fault persists, replace the processor board and then whole unit.
PAGE 138
GEMINI2 Traffic Outstation Handbook Symptom Possible Diagnosis I/O board faults (continued) Current sensor inputs failed (OMCU only) Action to Check Diagnosis Monitor the relevant input(s) using the Handset code KAC (see section 13.5), for correct operation. Observe the handset display and check that the varying reading is approximately 50 per bulb for bright or 40 per bulb for dim. If, the readings are incorrect, replace the relevant I/O board. If, the readings are correct, replace the processor board.
PAGE 139
GEMINI2 Traffic Outstation Handbook 8.6 TABLE FOR POWER FAILURES Symptom Possible Diagnosis Action to Check Diagnosis (a) Unit not operating PSU failed Check the unit has mains power. If yes, replace the PSU. If no, then check the cabinet’s mains fusing and power supply. Mains Input failed Check the cabinet’s mains supply to the unit and repair as necessary. If fault still persists due to no mains, request the electricity authority to restore mains supply.
PAGE 140
GEMINI2 Traffic Outstation Handbook 9. MOVA 9.1 MOVA Introduction IMPORTANT: BEFORE LOADING ANY CONFIGURATION DATA, REFER TO SECTION 9.6.7 ON PAGE 156. The following is an extract from the introduction of AG10. MOVA stands for Microprocessor Optimised Vehicle Actuation, a new strategy for control of traffic light signals at isolated junctions – junctions uncoordinated with any neighbouring signals.
PAGE 141
GEMINI2 Traffic Outstation Handbook The MOVA facility requires the use of an STC supplied licence code in order to be activated. See section 9.6.5, on page 154.
PAGE 142
GEMINI2 Traffic Outstation Handbook MOVA Confirms MOVA I/O Board LMU I/O Board(s) SIEMENS OMCU and MOVA UNIT Processor Board Note: Most of these I/O boards will not be required if the enhanced serial link to ST800/700 option described in section 4.2.6 on page 44 and section 9.6.4 on page 153 is used.
PAGE 143
GEMINI2 Traffic Outstation Handbook I/O Summary: MOVA Connection MOVA Detectors Confirm and Controller Ready Bits MOVA Force Bits (Fn and TO) PL1 & PL2 Input 0V     Connected to… Controller detectors (and ped. Outputs) Controller UTC terminal blocks (Outputs) Controller UTC terminal blocks (Inputs) Controller detector ground connection The digital inputs and outputs used by MOVA are pre-allocated since the MOVA site data is hardware platform independent.
PAGE 144
GEMINI2 Traffic Outstation Handbook Note:The OMCU can monitor the MOVA vehicle detector inputs on the MOVA I/O board. Therefore these detectors do not need to be wired into the OMCU’s LMU I/O board(s) as well as the MOVA I/O board. See section 5.6.3 which starts on page 91.
PAGE 145
GEMINI2 Traffic Outstation Handbook 9.2.4.
PAGE 146
GEMINI2 Traffic Outstation Handbook 9.3 Connection to a Siemens T400 To simplify connecting the MOVA unit to a Siemens Type 400 traffic controller, an alternative cableform is available. This cableform connects the first BUS / MOVA (Digital) I/O Board’s connectors PL1 and PL2 directly to the controller’s UTC Expansion I/O Board’s four connectors PLB, PLC, PLD and PLE. This cable also commons the 24V and 0V connections and thus only requires two wires to be connected to the controller’s 24V and 0V supplies.
PAGE 147
GEMINI2 Traffic Outstation Handbook 9.5 MOVA Commissioning Checklist The following checklist should be used to commission a Siemens MOVA unit. The steps are expanded upon in section 9.6, which starts on page 150. If an OMCU and MOVA unit is being installed, it is recommended that the OMCU application be commissioned before the MOVA application. The checklist should be followed in sequence: Step Section Action to be Performed 1) 5 Check that the MOVA unit has been installed correctly.
PAGE 148
GEMINI2 Traffic Outstation Handbook Step Section 10) 9.6.4 Action to be Performed If MOVA is to use a Bus / MOVA (Digital) I/O Board, check that the SOP handset command shows the correct type of I/O boards have been detected, see page 249. If MOVA is to use the enhanced serial link to an ST800/700 but the OMCU has not been configured, enable the facility manually using ‘MIO=2’ and check that the enhanced serial link is active, i.e. ‘EEL:3’. 11) 9.6.5 Enter the correct MOVA licence codes, e.g.
PAGE 149
GEMINI2 Traffic Outstation Handbook Step Section 18) Action to be Performed 9.6.10 Again using the commissioning screen, put the MOVA unit on control: a) Set the ‘MOVA enable’ flag to ‘1’ * b) Close communications (‘FI’ from the menu) c) Switch the MOVA unit’s power off and back on d) Return to the commissioning screen Check that as the controller changes from stage to stage that the ‘Warm-up Count’ increments. * MOVA cannot be enabled if the licence number is invalid (9.6.5). 19) 20) 21) 9.6.
PAGE 150
GEMINI2 Traffic Outstation Handbook 9.6 MOVA Commissioning Detail This section expands on the steps in the commissioning checklist from the previous section… If an OMCU and MOVA unit is being installed, it is recommended that the OMCU application be commissioned before the MOVA application. The checklist should be followed in sequence: Step Section Action to be Performed 1) 5 Check that the MOVA unit has been installed correctly.
PAGE 151
GEMINI2 Traffic Outstation Handbook 9.6.1 Communicating Locally with the MOVA Unit 7) 9.6.1 Connect the PC to the MOVA unit’s local port (the 25 way D-type connector on the front of the processor board) and start the MOVA communications application. Connect a normal controller handset cable (such as the IPT cable 667/1/17523/003) from the PC to the 25 way port on the front of the MOVA unit. Also see Section 3.10.6. Start the MOVA Communications program, which can be downloaded from the TRL website.
PAGE 152
GEMINI2 Traffic Outstation Handbook 9.6.2 Complete Initialisation 8) 9.6.2 Initialise MOVA by entering the handset command INI=2. If the OMCU application is not required, enter INI=3 to completely reinitialise the whole unit. Enter LDV=7 to request the MOVA facility. Refer to section 9.
PAGE 153
GEMINI2 Traffic Outstation Handbook 9.6.4 Serial Link between MOVA and an ST800/700 (MIO) 10) 9.6.4 If MOVA is to use a Bus / MOVA (Digital) I/O Board, check that the SOP handset command shows the correct type of I/O boards have been detected, see page 249. If MOVA is to use the enhanced serial link to an ST800/700 but the OMCU has not been configured, enable the facility manually using ‘MIO=2’ and check that the enhanced serial link is active, i.e. ‘EEL:3’.
PAGE 154
GEMINI2 Traffic Outstation Handbook 9.6.5 MOVA Licence Codes 11) 9.6.5 Enter the correct MOVA licence codes, e.g. ‘LIN=1234 5678 and LIF=123ABC’. The software licence codes are supplied from Poole and before this can be done the Serial Number of the Outstation Processor must be obtained. This can be found by either looking on the card itself or using the Handset code HIC. Determine whether the site is to be installed with MOVA 4, MOVA 5 or MOVA 6.
PAGE 155
GEMINI2 Traffic Outstation Handbook 9.6.6 Setting the Time and Date (CT) 12) 9.6.6 Set the time and date in the MOVA unit. The unit may display its current time and date before displaying its main menu when connection is first established with the MOVA unit, particularly after a mains power failure or after being initialised. Alternatively, enter ‘CT’ from the MOVA main menu to check the unit’s current time and date, or use the OMCU TOD command.
PAGE 156
GEMINI2 Traffic Outstation Handbook 9.6.7 Download New Site Data (RS, LD, CN and DS) 13) 9.6.7 Download the site data into the MOVA unit from the PC and then clear the MOVA working data as instructed on the screen. Caution: If the new site data contains a different number of links, lanes or stages, or different time-of-day data then MOVA must be re-initialised.
PAGE 157
GEMINI2 Traffic Outstation Handbook Download finished File name: . . . . . . NEWPARLEY.MDS Version: . . . . . . . M6.0 Creation time & date: 9:45 29/10/ 4 Title: . . . . . . . . NEW PARLEY WITH LANE TEN Stage/links/lanes: . . 5 /14 /10 Enter repository plan number to place this download data: 1,2,3 or 4, (or 99 to reject this download) 1 Plan number 1 selected Area 1 is empty. To confirm that you want to place the downloaded dataset in this area, select 'Y'.
PAGE 158
GEMINI2 Traffic Outstation Handbook 9.6.8 Commissioning Screen (LOOK) 14) 9.6.8 Use the commissioning screen to check for following. a) MOVA is currently not enabled (MOVA enabled = 0) b) The Controller is ready* (CRB = 1) c) The Confirm bits are all set to ‘1’, except for the current stage which should be set to ‘0’. Watch the controller perform at least one complete cycle to check that each stage and phase confirm bit is being activated correctly by the controller.
PAGE 159
GEMINI2 Traffic Outstation Handbook flags and the ‘Warm-up’ and ‘Error counts’ are described in more detail in section 9.6.10. For inputs on the Bus MOVA (Digital) I/O card, black background = input open circuit, red background = input short circuit. For semi-integral MOVA, the input sense can be inverted or not, dependant on the controller configuration. The ‘Multistage’ flag is set to ‘1’ if the confirm inputs indicate more than one stage is active, e.g.
PAGE 160
GEMINI2 Traffic Outstation Handbook Pressing the space bar toggles between the single key press commands and the MOVA Main Menu: Typical MOVA 6 Main Menu Screen Detectors: Confirms: CRB SIEMENS 1 2 3 4 17 18 19 20 33 34 35 36 49 50 51 52 MOVA COMMISSIONING SCREEN 5 6 7 8 9 10 11 12 21 22 23 24 25 26 27 28 37 38 39 40 41 42 43 44 53 54 55 56 57 58 59 60 13 29 45 61 1 2 3 4 17 18 19 20 5 6 7 8 21 22 23 24 13 14 15 16 29 30 31 Force Bits: HI/TO 1 2 3 9 10 11 12 25 26 27 28 4 5 6 7 8 14 30 46
PAGE 161
GEMINI2 Traffic Outstation Handbook 9.6.10 Enabling MOVA Control 18) 9.6.10 Again using the commissioning screen, put the MOVA unit on control: a) Set the ‘MOVA enable’ flag to ‘1’ * b) Close communications (‘FI’ from the menu) c) Switch the MOVA unit’s power off and back on d) Return to the commissioning screen Check that as the controller changes from stage to stage that the ‘Warm-up Count’ increments. * MOVA cannot be enabled if the licence number is invalid (9.6.5). 19) 20) 9.6.
PAGE 162
GEMINI2 Traffic Outstation Handbook number of stages plus one (e.g. 6 on a 5-stage junction) then the warm-up cycle is said to be complete. This warm-up cycle allows the MOVA unit to gather information about the junction before it takes control. Following various fault conditions, the MOVA may put itself off control by clearing the ‘On Control’ flag and incrementing its ‘Error Count’. Depending on the nature of the fault, the MOVA unit will increment the ‘Error Count’ by one, two or five.
PAGE 163
GEMINI2 Traffic Outstation Handbook 9.7 MOVA Communications Notes Assistance on communicating locally with the MOVA unit during commissioning is provided in the previous section within the appropriate steps in the commissioning checklist, e.g. section 9.6.1 on page 151. This section provides information on communicating remotely with a Siemens MOVA unit via the telephone network and describes some of the options, which may be useful once MOVA is functioning normally.
PAGE 164
GEMINI2 Traffic Outstation Handbook Ok ATD 9 01202 123456 CONNECT Please wait accepted by the modem ask the modem to dial the given number response from modem indicating connection made message from MOVA application* Press ‘Return’ three times after the ‘connect’ message from the modem to connect to the MOVA application rather than the RMS OMCU application. * After a short delay, the MOVA unit will then ask for the password to validate remote access.
PAGE 165
GEMINI2 Traffic Outstation Handbook Look at Flags The second option displays all the flags and the menu again. Use this option to ‘refresh’ the display, e.g. when looking for a change of state of a particular flag. Set Flags The first option can also be called directly from the main menu by typing ‘SF’ rather than ‘LF’. This option allows some of the flags to be changed: SET FLAGS : Flag(17) ERROR COUNT . . . . . . . . . Flag(18) PHONE HOME . . . . . . . . . .
~~PAGE 166~~
GEMINI2 Traffic Outstation Handbook Normally, the MOVA unit will only ‘phone home’ when it has detected an unrecoverable error, e.g. when its error count has reached or exceeded 20 preventing the MOVA unit putting itself back on-line. However, by setting the ‘Phone Home’ flag to a value in the range 1 to 20, the user can force the MOVA unit to phone home whenever the error count reaches this limit.
~~PAGE 167~~
GEMINI2 Traffic Outstation Handbook 9.7.6 MOVA Detector Status Output The detector status area of the MOVA Commissioning screen is capable of displaying the status of up to 64 detectors. It should be noted that this is the true detector state only where the detector is designated in the MOVA configuration data set. Where a detector is not designated it will be displayed as inactive.
~~PAGE 168~~
GEMINI2 Traffic Outstation Handbook On a local handset connection, when exiting the MOVA function (‘FI’ command) operation will revert to the normal handset interface. To select the other stream ‘MOVA’ must be entered again. On a remote interface FI will drop the telephone call. To select the alternate stream but remain within the same call the special character ‘@’ can be entered. The stream selection dialog will then reappear without terminating the call.
~~PAGE 169~~
GEMINI2 Traffic Outstation Handbook 9.8.2 Serial Interface to Controller The serial protocol from the controller to Outstation provides a status message supporting up to 64 detector status bits and 32 green confirms. In the Outstation to controller direction there is a capacity for up to 32 force bits (though MOVA 5 supports only 10 per stream). This capacity must be split across both streams and a stream 1 controller ready bit must be generated in the controller using conditioning. 9.8.2.
~~PAGE 170~~
GEMINI2 Traffic Outstation Handbook 9.8.2.3 Force Bits The force bits for the first stream start in the first control word (see figure 22). The force bits for the second stream start in the third control word, even if the first stream only uses 8 force bits. The take-over bits (TO) for each stream are placed in the top bit of the second word of each stream. These are OR’d together and placed in the TO header field of the serial message.
~~PAGE 171~~
GEMINI2 Traffic Outstation Handbook Figure 23 – BUS/MOVA Card Pinout STREAM 0 Card 1; Connector 2 (Top) Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 Signal Name Detector 25 Detector 26 Detector 27 Detector 28 Detector 29 Detector 30 Detector 31 Detector 32 CR Green Confirm 1 Green Confirm 2 Green Confirm 3 Green Confirm 4 Green Confirm 5 Green Confirm 6 Green Confirm 7 Green Confirm 8 Green Confirm 9 Green Confirm 10 667/HB/32600/000 0V 0V STREAM 1 Card 1; Connector 1 (Bott
~~PAGE 172~~
GEMINI2 Traffic Outstation Handbook 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Force Bit 9 Force Bit 9 Force Bit 10 Force Bit 10 Force Bit 11 Force Bit 11 Force Bit 12 Force Bit 12 Force Bit 13 Force Bit 13 667/HB/32600/000 T0 T0 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Force Bit 1 Force Bit 1 Force Bit 2 Force Bit 2 Force Bit 3 Force Bit 3 Force Bit 4 Force Bit 4 Force Bit 5 Force Bit 5 Force Bit 6 Force Bit 6 Force Bit 7 Force Bit 7 Force Bi
~~PAGE 173~~
GEMINI2 Traffic Outstation Handbook 9.8.4 Advanced Programming of Stage Confirms with a Serial Interface to the Controller While it is recommended for simplicity that the stage comfirms for each stream be kept in separate words of the controller serial message this is not absolutely necessary. If the first stream requires more confirm bits, and not all of the 15 confirm bits for the second stream are being used, then the first stream can use some of the reply bits in the fourth reply word.
~~PAGE 174~~
GEMINI2 Traffic Outstation Handbook 9.8.5 Stream Interdependency In certain installations it may be of benefit to allow one stream to have some knowledge of traffic flow in the other. To fulfil this requirement the MOVA lane over-saturation (SAT) and link end of saturation (ESLI) codes have been made available to the special conditioning facility within the OMCU. From here they can be passed to the controller through the special conditioning variable TOSL. 9.8.5.
~~PAGE 175~~
GEMINI2 Traffic Outstation Handbook 9 - 15 lost time etc. Not used The individual bit arrays shall be assembled into a 60 element array of type word which shall be accessible to special conditioning via the operands M0Enc and M1Enc where n is the index into the array and equals the link number minus 1 and c corresponds to the bit position of each condition within the indexed word. 9.
~~PAGE 176~~
GEMINI2 Traffic Outstation Handbook 10. CAR PARKS 10.1 Overview The Car Park monitor facility is used to return occupancy data to a Siespace Instation. This information can then be used by the Instation to guide vehicles to car parks that have spaces. Communications with Siespace use either GPRS or PAKNET radio transmissions. Count information is usually gathered by loops, however, if an APT Skidata system is in use at the car park then Outstation can interface directly to this.
~~PAGE 177~~
GEMINI2 Traffic Outstation Handbook To provide handset commands to modify the Car Park facility configuration data 10.2 Outstation Status Message to SIESpace The Outstation generates the same status report format regardless of the reason for generating the status report.
~~PAGE 178~~
GEMINI2 Traffic Outstation Handbook 10.2.3 Loss of Comms to GPRS Modem On loss of communications with the GPRS modem the Outstation will attempt to reconnect to Siespace at 7 minute intervals. If the Outstation detects that communications with the mobile phone network have been lost (indicated by the modem dropping its PPP session) then it will reinitialise the modem.
~~PAGE 179~~
GEMINI2 Traffic Outstation Handbook The ‘SPACES’ state is set when the almost full decreasing threshold is crossed from the ‘ALMOST FULL’ or ‘FULL’ states. The ‘ALMOST FULL’ state is set when the almost full increasing threshold is crossed from the ‘SPACES’ state or when the full decreasing threshold is crossed from the ‘FULL’ state. The ‘FULL’ state is set when the full increasing threshold is crossed from the ‘SPACES’ or the ‘ALMOST FULL’ states.
~~PAGE 180~~
GEMINI2 Traffic Outstation Handbook Occupancy Expected Occupancy Current Occupancy Historical Occupancy M = Fill Rate Calculation Period N Time Figure 26 – Extrapolation If the state is FULL and the car park is emptying fast enough so that the ALMOST FULL state would be reached in N minutes then status reports are sent to the Central Office at X minute intervals (ramp down mode) where X is set to the ramp down period.
~~PAGE 181~~
~~GEMINI2 Traffic Outstation Handbook 10.4 Configuration The Car Park and GPRS or PAKNET facilities are configurable from the handset. Sections 13.12 and 13.13 detail the relevant commands. 10.4.~~
~~PAGE 182~~
GEMINI2 Traffic Outstation Handbook entered to clear the fault, the handset display will change to RDF:0 once all faults have been cleared (this may take up to 1 minute). 10.4.3 PAKNET Configuration By default the PAKNET communication protocol is disabled. The following handset parameters have to be set-up to enable this facility. RCA – Remote Comms user address is the 14-character address of the Instation. RCT – Comms type – set to PAKNET. RCB – Remote comms baudrate, set to 4800.
~~PAGE 183~~
~~GEMINI2 Traffic Outstation Handbook 10.5 Installation 10.5.1 PAKNET Interface Connector An additional interface connector must be placed between the OUTSTATION modem cable and the PAKNET pad.~~
~~PAGE 184~~
GEMINI2 Traffic Outstation Handbook 10.5.3 Door Switch A Door switch can be provided to indicate to the Instation when the cabinet door has been opened. This input is connected to one of the low voltage inputs on the associated LMU I/O card. By default the door switch is assigned to input 16 (PL3 pins 15 and 16) Handset command DOR can be used to modify the OMCU input assigned to this facility. 10.5.
~~PAGE 185~~
GEMINI2 Traffic Outstation Handbook 10.6.1 Information required from APT Skidata The following information is required from APT Skidata to setup the Outstation (The handset command for this parameter is shown in brackets) : 1) APT Facility Number (AFN) Overall identifier for the installation controlled by the APT Skidata equipment (could contain multiple car parks). 2) Car Park Number (ACN) Identifies individual car parks within a facility.
~~PAGE 186~~
GEMINI2 Traffic Outstation Handbook 7) APT IP Address (AIP) Defines the IP Address of the APT Skidata equipment that is running the host comms interface. 8) Outstation IP Address (IPM0 or 3) The IP address of the Outstation should be obtained from Skidata as it needs to be compatible with any other devices connected to the host comms port. For host comms version 1 this IP address will also need to be programmed into the APT Skidata equipment. Use IPM3 to set the subnet mask if required. 10.6.
~~PAGE 187~~
GEMINI2 Traffic Outstation Handbook 11. UTMC OTU 11.1 INTRODUCTION Sections 11.2 and 11.3 describe the configuration of the Outstation to provide the UTMC OTU facility, for the freestanding and semi-integral situations respectively. Prior to this procedure the outstation should have been installed and commissioned as defined in section 6.3 on page 111. The I/O capability of the UTMC OTU is summarised below.
~~PAGE 188~~
GEMINI2 Traffic Outstation Handbook SIGNAL HEADS LOCAL HANDSET RS232 STAGE CONFIRMS TRAFFIC CONTROLLER Ethernet UTMC OTU DSL MODEM FORCE BITS SCOOT INPUTS UTMC PROTOCOL TO INSTATION SCOOT DETECTOR LOOPS VA DETECTOR LOOPS 11.2.1 Configuration Data The UTMC Configuration data is programmed into the OTU via the handset.
~~PAGE 189~~
GEMINI2 Traffic Outstation Handbook OTU – Reply Bit Allocation Table Bit 7 Byte 0 GH Byte 1 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 GG GF GE GD GC GB GA Count 15 Count 0 HIOCC 7 HIOCC 0 Fault DFM Handset Byte 2 Scoot 1 Scoot 1 Scoot 1 Scoot 1 Scoot 0 Scoot 0 Scoot 0 Scoot 0 Byte 3 Scoot 3 Scoot 3 Scoot 3 Scoot 3 Scoot 2 Scoot 2 Scoot 2 Scoot 2 Byte 4 Scoot 5 Scoot 5 Scoot 5 Scoot 5 Scoot 4 Scoot 4 Scoot 4 Scoot 4 Byte 5 Scoot 23 Scoot 23 Scoot 23 Sco
~~PAGE 190~~
GEMINI2 Traffic Outstation Handbook (a) (b) (a)/ = The sense of this input is inverted using the GIS command. See section 13.20.2, starting on page 315. DFM is enabled on the loop inputs on ports 2 and 3. 11.2.2 Example Configuration Commands The detail in this section demonstrates the use of the UTMC OTU commands to configure the Outstation to provide the configuration shown in the tables above. It should be noted that any text following the command example is a comment and should not be entered. 11.2.2.
~~PAGE 191~~
GEMINI2 Traffic Outstation Handbook 2 x control bytes; 6 x reply bytes. The first two reply bytes are mapped to the first two input ports. The remaining four bytes are allocated to 8 SCOOT loops. 11.2.2.4 Transmit Confirm TCA=15 Comment: Assigns the Transmit Confirm signal to output line 15. 11.2.2.5 Define the number of Control & Reply Bytes The OTU need to know how many Control Words it needs to respond to and how many Reply Words it needs to provide.
~~PAGE 192~~
GEMINI2 Traffic Outstation Handbook Reply: We now need to define the detail of each Reply Word: For Byte 0: GRL 0 0=0 GRL 0 1=0 GRL 0 2=0 GRL 0 3=0 GRL 0 4=0 GRL 0 5=0 GRL 0 6=0 GRL 0 7=0 Comment: In this example Reply Byte 0 comes direct from the inputs so set all these to 0. The initial default for this command is 0 so there is no need to enter these commands manually. (Only included here for completeness).
~~PAGE 193~~
GEMINI2 Traffic Outstation Handbook For Bytes 7 & 8: GRL 7 0=57 ;Reply bytes 7 & 8 = Environmental Sensor Comment: Reply Bytes 7 & 8 definitions for the Environmental Sensor inputs. Reply byte 7 is for byte 0 of the sensor data and reply byte 8 is for byte 1 of the sensor data.
~~PAGE 194~~
GEMINI2 Traffic Outstation Handbook UNIDIRECTIONAL LOOP INPUT ALLOCATION GUD 0=54 ;U/D unit 0 uses inputs 54 & 55. 54 being the ‘up-stream’ loop and 55 being the ‘down-stream’ loop. GUD 1=255 ;U/D unit 1 is not used GUD 15=13 ;U/D unit 15 uses inputs 13 & 14 Comment: This command allocates the Unidirectional Loop to a particular input on the outstation. The initial default for this command is 255 so there is no need to enter unused inputs manually. (Only included here for completeness). 11.2.2.
~~PAGE 195~~
~~GEMINI2 Traffic Outstation Handbook 11.2.2.~~
~~PAGE 196~~
GEMINI2 Traffic Outstation Handbook SIGNAL HEADS LOCAL HANDSET RS232 EHANCED SERIAL LINK Ethernet ST700/800 TRAFFIC CONTROLLER UTMC OTU DSL MODEM SCOOT INPUTS UTMC PROTOCOL TO INSTATION SCOOT DETECTOR LOOPS VA DETECTOR LOOPS 11.3.1 Configuration Data The UTMC Configuration data is programmed into the OTU via the handset. The following sections detail the specific commands to enable this facility. 11.3.
~~PAGE 197~~
GEMINI2 Traffic Outstation Handbook 11.3.2.2 Set IP Address and Gateway of the OTU a) To manually set the IP Address to 137.223.152.216 use the following command sequence: Enter the commands: IPM 0=137.223.152.216 IPR=2 Comment: This will manually set the IP Address to 137.223.152.216. See IPM handset command, in section 13.19, page 310 for details of the ‘gateway’ etc. b) For automatic setting of the IP Address ensure the OTU is connected to a network with a BOOTP server.
~~PAGE 198~~
GEMINI2 Traffic Outstation Handbook 11.3.2.6 Allocation of Control and Reply Control: The function of each of the Control Word bits are defined at the UTMC Instation and must match the corresponding bit configurations in the controller. Therefore these do not require any further allocation. When the configuration of the OTU is complete and communication to the Instation is working the definition of these bits can be viewed by using the handset commands GCN and GRN. See section 13.20.
~~PAGE 199~~
GEMINI2 Traffic Outstation Handbook 11.3.2.7 DFM Facility The controller provides its own DFM facility for all its inputs. Any SCOOT inputs on the OTU are monitored by the Instation. No further configuration is required. 11.4 Initialising the OTU When the OTU has been configured and the data checked it can now be connected to the Instation.
~~PAGE 200~~
GEMINI2 Traffic Outstation Handbook 12. UTMC VMS 12.1 INTRODUCTION This section describes the configuration of the Outstation to provide the UTMC VMS facility. Prior to this procedure the outstation should have been installed and commissioned as defined in section 6.3 on page 111. 12.2 UTMC VMS Configuration The Outstation can be configured to provide an interface between a SIESpace Instation and up to 8 UVMS signs via an IP based network using the UTMC VMS system.
~~PAGE 201~~
GEMINI2 Traffic Outstation Handbook 12.2.1 Configuration Commands The detail in this section demonstrates the use of the handset commands to configure the Outstation for UTMC VMS operation. The example given is for a single VMS Sign attached to the UTMC Outstation. If this is not the case then some of the commands will need to be re-entered with different indexes to ‘point’ to the other signs. It should be noted that any text following the command example is a comment and should not be entered. 12.2.1.
~~PAGE 202~~
GEMINI2 Traffic Outstation Handbook It will also be necessary to correctly terminate this communication line and the details for this can be found in section 5.2.5 on page 75. It will then be necessary to specify which RS485 port is being used and what the transmission characteristics are: POC 0 0=4 POC 0 1=0 POC 0 2=0 POC 0 3=1 POC 0 4=8 Comment: In this example Port 0 is being used and is configured for 9600 baud, no parity, one stop bit and 8 data bits.
~~PAGE 203~~
GEMINI2 Traffic Outstation Handbook VMN 0 = 0 Comment: Sets the RS485 channel number that the sign is connected to. VMA 0 = 1 Comment: Set the RS485 Bus address that the sign is using. VMT 0 = SOUTH CAR PARK ACCESS Comment: Set the description of the VMS sign. VMH 0 = 2 Comment: Set the number of rows the sign has. VMW 0 = 12 Comment: Set the number of characters in each row. VML 0 = 2 Comment: Specify if ‘Lanterns’ are fitted. In this case ‘2’ means no. 12.2.1.
~~PAGE 204~~
GEMINI2 Traffic Outstation Handbook 13. HANDSET FACILITIES 13.1 INTRODUCTION Access to the Outstation configuration and status information is gained by entering codes on an approved handset and interpreting the response on the display. The handset port connector is a 25-way female D-type and operates at 1200, 9600, 19200 or 56700 baud, on first receiving characters after the handset is plugged in.
~~PAGE 205~~
GEMINI2 Traffic Outstation Handbook HANDSET CODES HSET MAJOR CMD INDEX ACC ACF ACN - MINOR INDEX DATA DESCRIPTION 1 – 23 - 0–1 0–1 0 – 254 APT SKIDATA COUNTING CATEGORY CLF ACTION ON COMPLIANCE FAIL APT SKIDATA CAR PARK NUMBER OUTPUT ACTION LIST (BEACONS) OUTPUT ACTION LIST (SIETAG) OUTPUT ACTION LIST (RTIG) APT SKIDATA HOST COMMS VERSION APT DEVICE NUMBER REMOTE COMMS OMCU ADDRESS ENABLE APT SKIDATA INTERFACE ACCUMULATED ERROR COUNTS APT SKIDATA FACILITY NUMBER APT SKIDATA LINK FAIL REPORTING CAR PAR
~~PAGE 206~~
GEMINI2 Traffic Outstation Handbook HSET MAJOR CMD INDEX CDC 0–1 CDI CEC CGR - MINOR INDEX DATA DESCRIPTION 0–9 0 – 31 0–7 0 – 255 0 – 255 0–1 0 – 31 CALL DISCONNECT CAUSE STATS CLOCK DRIFT FROM INSTATION CLF ENABLED COMPLIANCE CURRENT CLF GROUP CURRENT CLF GROUP TIME REMAINING CLF DATA SET IDENTITY CLOCK TO ADVANCE GPS CLOCK MONITOR CLOCK TO RETARD LAST GPS CLOCK SYNCHRONISATION COUNTS USED WHEN GRAPHOS IS ENABLED COPY DETECTORS TO OUTPUTS N + 1 COUNTER VALUE CAR PARK OCCUPANCY STATUS DETECTOR COUNTE
~~PAGE 207~~
GEMINI2 Traffic Outstation Handbook HSET MAJOR CMD INDEX MINOR INDEX DATA ERR - - 0 - 100 EVA EVI EVS EXR FCP FDC FFC FFT FLG FLT FOC FOD FOF FOH FOL FOP FOS FOU FTR FUT GAQ GCD 0–1 aaa - 0 – 15 0 – 15 0–1 0–1 0–8 0 – 15 aaa 0 – 15 0 – 15 0 – 15 0–1 0–1 0 – 15 0 – 15 0 – 15 0–3 0–1 0 – 15 0–7 0 – 255 0 – 255 BINARY BINARY 0 – 63 0 – FFFF 0 – 15 TIME 0 – 65535 0 – 65535 0 –100 BINARY BINARY 0 – 100 0 – 65535 0 – 65535 0 – 255 0 – 16838 0 – 255 BINARY GCF - 0 – 15 1–8 GCN GCT 0 – 15 - 0–7 0–6
~~PAGE 208~~
GEMINI2 Traffic Outstation Handbook HSET MAJOR CMD INDEX MINOR INDEX DATA DESCRIPTION UTMC OTU CONSECUTIVE OCCUPANCY SAMPLES UTMC OTU OCCUPANCY SMOOTHED HIGH VALUE UTMC OTU RESET OCCUPANCY AFTER PRE-SET TIME UTMC OTU COUNT /QUEUE /OCC.
~~PAGE 209~~
GEMINI2 Traffic Outstation Handbook HSET MAJOR CMD INDEX IPB IPC - MINOR INDEX - DATA IPI - 0–1 IPM IPP IPR - 0–4 - JID - - KAC KAS KDB KEY KIC KLS KLM LAN 1 – 23 1 – 23 0–1 - 0–1 0–6 - ASCII 0-65535 NUMBER: NUMBER NUMBER NUMBER 1 OR 2 0–9+ SP 0 – 1023 BINARY 0–2 16 ASCII ASCII BINARY 6–8 0 – FFF LED 0–3 0 – 31 0 – FF LDV LIC LIF LIN LIP LMD LMO LMR LOC LSO LTS MAC MAP MCI MDC MDE MIO MON MOS MPC MSI MTS OCC OCD OCF OCH OCL OCP 0–1 0–3 0–1 - 0–7 0–9 0–1 0 – 12 aaa 0–2 0 – 31 0 – 15 0 –
~~PAGE 210~~
GEMINI2 Traffic Outstation Handbook HSET MAJOR CMD INDEX OCS OCU OFF 0 – 15 OID - MINOR INDEX DATA DESCRIPTION 0 – 15 0 – 15 0–1 - 0 – 100 0 – 100 0 – 255 ASCII SMOOTHED OCCUPANCY RESULT OCCUPANCY UP THRESHOLD CLF OFFSET FROM THE BASE TIME OUTSTATION ID STRING OLG - - - OPM OPS PDL PDR PDU PGS PIA PIC PLE PLI PLS PLT PLX PME POC POS PPD PRI PUD PTO RAM RAT RCA RCB RCD RCI RCM RCR RCS RCT RCU RDF RET RIC RIF RFL RMD RMP RMS 0–2 0 – 15 0 – 11 - 0–1 0–1 0–1 0–1 0 – 15 0 – 15 0 – 31 0 – 15 0–4 0–1
~~PAGE 211~~
GEMINI2 Traffic Outstation Handbook HSET MAJOR CMD INDEX MINOR INDEX DATA 0 – 15, 255 0–2 0 – 255 0 – 31 0 – 31 0 – 255 0 – 255 0–2 0 – 255 0–7 A – P 0 – FFFF 0–1 0–3 0 – FFFF 0 – 255 0- 1 0 – FFFF 0–4 0 – 9 0 – 65535 ASCII ENG BINARY 0 – 15 0 – 255 0 – 63 0 – 31 0–1 1–3 0 – 255 0 – 47 0 – 15 TEXT 0–1 0 – 15 0 – 255 0 – 15 0 – 255 PH – PH 0 – 255 0 – 15 0 – 255 0 – 15 0 – FF 1 – 64 0–1 0–2 TIME DATE and 0 – 63 0 – 99 0–1 DATE 0 - 16383 0–5 0 – 215 1 RPL - RPM RSA RSC RTO RTR SCT SDC SDF SEB SEC SES SG
~~PAGE 212~~
GEMINI2 Traffic Outstation Handbook HSET MAJOR CMD INDEX VMA VMC 0 – 15 VMD - MINOR INDEX 0–7 0–3 - VMH - 0–7 VML - 0–7 VMM 0–7 0–5 VMN - 0–7 VMP - - VMS VMT VMV - 0–7 0–7 VMW - 0–7 VOA 0 – 31 0–6 VRC - - VRX VSB - 0–5 0–6 VSM - 0 – 31 VSP 0–3 0–5 VTD - 0–2 VTM 0–4 0–1 VVT 0 – 15 0–1 XXC XXM XXO XIP - - DATA DESCRIPTION 1 – 254 UTMC VMS SIGN RS485 ADDRESS 0 – FFFF VARI-MAX LOG 1 – 240 UTMC VMS OUTSTATION POLL DELAY UTMC VMS SIGN HEIGHT (NUMBER OF 1–6 ROWS)
~~PAGE 213~~
GEMINI2 Traffic Outstation Handbook For read operations, following typing of the command code and any indices if applicable, operation of the ENTER (or ‘RETURN’) key terminates the command. For write operations an equals sign ‘=’ followed by the parameter required is added to the read command before selecting ENTER (or ‘RETURN’).
~~PAGE 214~~
GEMINI2 Traffic Outstation Handbook 2. When the Outstation displays the prompt character ‘-’, type out the appropriate command and any index necessary, e.g. to determine the DIM/BRIGHT state of the controllers signal lamps enter KDB to produce the display: KDB 3. Terminate the command by operating the ENTER (or ‘RETURN’) key. The Outstation responds by repeating the display with a colon and the required data. (e.g. Bright state in this example), i.e. KDB: 1 4.
~~PAGE 215~~
GEMINI2 Traffic Outstation Handbook immediately replaces the colon and the old value in the display. On operation of the ENTER (or ‘RETURN’) key to terminate the instruction, the Outstation repeats the display with = replace by a colon. 13.1.6 Switchable Handset Facility It is possible to store up to 10 handset commands, such that any of these commands may be subsequently recalled by pressing the “.” (dot) key, followed by the appropriate number.
~~PAGE 216~~
GEMINI2 Traffic Outstation Handbook + .0 .1 will now display the status for Phases I to 0 and will be remembered as the new command for ‘.1’ will display input port 0 again. will display the status for Phases I to O. The facility is not restricted to just the commands indicated above; any valid handset facility may be entered in any of the pointers in any order. Note: On some handset commands it is not advisable to duplicate the command in two or more dot buffers.
~~PAGE 217~~
~~GEMINI2 Traffic Outstation Handbook 13.~~
~~PAGE 218~~
GEMINI2 Traffic Outstation Handbook Code MON Major Index - Minor Index SDE Data Range - MON - SEQ - MON - STK - MON - VMX - PDL - 0–1 - PDR - 0–1 - PDU - 0–1 - SDC - **1 A–P - SMS - - - TIM - CLR - TIM **3 EXL **2 0 – 15 - TIM **3 EXS **2 0 – 15 - 667/HB/32600/000 Description SDE/SA monitoring DATA: (ON/OFF) Stage Sequence monitoring DATA: (ON/OFF) Controller Stuck monitoring DATA: (ON/OFF) Vari-Max monitoring DATA: (ON/OFF) Display Phase Demands – Latched M
~~PAGE 219~~
GEMINI2 Traffic Outstation Handbook Major Index **3 IGN PH – PH TIM **3 MAX **2 0 – 15 - TIM **3 MIN **2 0 – 15 - VMC 0 – 15 **2 0–3 - Code TIM Minor Index **1 Data Range - Description Display/Reset shortest measured inter-green time for each phase to phase movement MINOR INDEX: PHASE to PHASE. DATA: Shortest Inter-green in seconds and tenths of seconds.
~~PAGE 220~~
GEMINI2 Traffic Outstation Handbook SMS: MAX END SMS: AWAIT END Stage max time terminating Timing monitoring for the stage has completed, waiting for end of stage Min time was below the defined limit Extension time was below the defined limit Extension time was above the defined limit The max time was above the defined limit SMS: SHORT MIN SMS: SHORT EXT SMS: LONG EXT SMS: LONG MAX 13.
~~PAGE 221~~
GEMINI2 Traffic Outstation Handbook MSI - 0–2 - XIP* - - - Display Mains state inputs. Minor index: MSI 0 - first 8 mains I/Ps on first I/O Board or the two mains state I/Ps on the PSU connector if NO LMU I/O card fitted (MSI 0:000000xx). MSI 1 - last 2 mains I/Ps on first I/O Board & first 6 mains I/Ps on 2nd I/O Board MSI 2 - last 4 mains I/Ps on 2nd I/O Board & first 4 mains I/Ps on 3rd I/O Board. DATA: 8 Bit Binary (bit7 - input bit 7 etc) Display External Input states.
~~PAGE 222~~
GEMINI2 Traffic Outstation Handbook 13.5 LAMP MONITORING COMMAND TABLE Code LMO Major Index - Minor Index - Data Range 0–1 LMR - - - PGS - 0 -1 - KAC KLS KAS 1 – 23 0–1 sensor 0=curr number 1=lamp supply voltage - 1 – 23 sensor number 667/HB/32600/000 - 0–6 aspect pattern number - - BINARY *NOTE1 Description Lamp monitor override Enter 1; Lamp monitor override enabled, allowing OMCU to monitor lamps while using enhanced serial link. Enter 0; Lamp monitor override disabled.
~~PAGE 223~~
GEMINI2 Traffic Outstation Handbook Code KDB Major Index 0–1 Minor Index - Data Range 0–2 KLM 0 - 6–8 Description Display Controller Dim/Bright State KDB (lamp supply:0 – 1) Comment: Indicates the dim/bright state for each of the controller lamp supplies as shown below:0 – state undefined (no change has occurred) 1 – dim 2 – bright Display Lamps ON/OFF State KLM (lamp supply: 0 – 1) Comment: Indicates the state for each of the controller lamp supplies as shown below:6 – lamps off 7 –
~~PAGE 224~~
GEMINI2 Traffic Outstation Handbook 13.6 FAULT DATA COMMAND TABLE Code FDC Major Index 0–8 Minor Index 0–1 Data Range - FFC EXL 0 – 15 (**2) - FFC EXS 0 –15 (**2) - FFC IDM A–P (**1) - FFC IGN PH – PH - (**1) FFC MAX 0 – 15 (**2) FFC MIN 0 – 15 (**2) FFT - EXL - FFT - EXS - FFT - IGM - FFT - MAX - FFT - MIN 667/HB/32600/000 - Description Display Fault Diagnostics See 13.6.1 Display LONG EXTENSION fault Filter count for each stage.
~~PAGE 225~~
GEMINI2 Traffic Outstation Handbook Major Index - Code FLT (**3) NOTE: Minor Index - Data Range - Description View current Fault List Selects first non-zero entry (see section 13.6.2 for details) Access Level RO **1 – Dependant on number of PHASES configured **2 – Dependant on number of STAGES configured **3 – Restricted use of the ‘.’ (dot) command 13.6.1 Fault Diagnostics (FDC) This handset command allows access to general fault monitoring statistics.
~~PAGE 226~~
GEMINI2 Traffic Outstation Handbook 13.6.2 General Fault Data Display Format The FLT command displays a list of current faults (use + and – to scroll through the list). The format is as follows: FLT:!VLF A 0 Fault data Fault code ‘!’= Urgent fault ‘ ’= Non-urgent fault It should be noted that fault reports are only generated when the limits (as defined in the Outstation configuration data) are exceeded. The FLG command is also available.
~~PAGE 227~~
GEMINI2 Traffic Outstation Handbook *= Code only used in the fault log (FLG), not the current fault list (FLT) † = More detail on these codes is provided in the subsections after this table Code Description - Notes ABF Amber Ball lamp Fault - non UK ABR* Amber Ball lamp Replaced - non UK BDC* Bus config Data Change - see section 13.
~~PAGE 228~~
GEMINI2 Traffic Outstation Handbook *= Code only used in the fault log (FLG), not the current fault list (FLT) † = More detail on these codes is provided in the subsections after this table Code Description - Notes GAF Green Arrow lamp Fault GAR* Green Arrow lamp Replaced GCF GPRS Comms Fault GCC GPRS Comms Fault Clear † GFC * GEC 3000 Fault Cleared † GFL GEC 3000 Fault Log entry
~~PAGE 229~~
GEMINI2 Traffic Outstation Handbook *= Code only used in the fault log (FLG), not the current fault list (FLT) † = More detail on these codes is provided in the subsections after this table Code Description - Notes MEN MOVA Enabled (see MOF) MFC* Microsense Fault Cleared MFL Microsense Fault Log entry MOF MOVA Disabled (‘MOVA Off’) - see section 9.6.10 on page 161 MPH MOVA Phone Home flag set - see section 9.7.
~~PAGE 230~~
GEMINI2 Traffic Outstation Handbook *= Code only used in the fault log (FLG), not the current fault list (FLT) † = More detail on these codes is provided in the subsections after this table Code Description - Notes SSR* Switched Sign bulb Replaced † STK Controller Stuck SWF Switched sign tube Fail SWR* Switched sign tube Replaced
~~PAGE 231~~
~~GEMINI2 Traffic Outstation Handbook : The sign identity number as configured in the OMCU lamp monitoring data : Controller fault log number, refer to CX controller handbook~~
~~PAGE 232~~
GEMINI2 Traffic Outstation Handbook 13.6.3 Green Conflict Fault Data (FLT CFL) When the OMCU detects a green/green conflict the following fault data will be presented: FORMAT: FLT:!CLF wxyz Where ‘wxyz’ are four HEX characters representing the conflict condition.
~~PAGE 233~~
GEMINI2 Traffic Outstation Handbook 13.6.6 Equipment Data Invalid Fault (FLT EDI) If the sumcheck on the Outstation configuration data fails during ‘download’ or during periodic background check, then the following fault will be presented: FORMAT: FLT:!EDI 13.6.7 External Signal Active / Inactive Fault (FLT ESA / ESI) If the OMCU has been configured to raise a fault report when an External signal becomes active (e.g.
~~PAGE 234~~
GEMINI2 Traffic Outstation Handbook 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 *1 *2 *3 Detector Flow Error System Stopped *1 Power Fail *1 *2 MIS Failure *2 Checksum Failure *2 Safety 2 Red Lamps Out *3 Safety Red Lamp Out *3 Red Lamp Out *3 Amber Lamp Out *3 Green Lamp Out *3 Wait Lamp Out *3 Red Excess Current *3 Amber Excess Current *3 Green Excess Current *3 Wait Excess Current *3 Green No Output Voltage *3 Checksum Failure *3 These faults are not reported by the OMCU since they do not appear
~~PAGE 235~~
GEMINI2 Traffic Outstation Handbook 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 “ “ “ “ “ “ “ “ (unused). (unused). (unused). (unused). (unused). Phase non-correspondence “ “ “ (unused). (unused). Hardware & firmware conflict pattern check “ “ “ “ “ “ (unused). (unused). EPROM or RAM sumcheck error. Time Error (32mS). J Address error. “ “ “ “ “ “ 13.6.10 GPS Fault (FLT GPS) The OMU continually monitors the data stream from the GPS receiver (if configured).
~~PAGE 236~~
GEMINI2 Traffic Outstation Handbook 3 4 5 6 7 8 9 10 - Cableless Link Bus priority Emergency Vehicle Hurry Call No.1 Hurry Call No.2 UTC (or MOVA) Part-time Start-up NB: The same mode numbers are used in the MDE handset command 13.6.12 Stage Sequence Fault (FLT SEQ) If the OMCU has detected a non-permitted stage to stage movement the following fault data will be presented: FLT:!SEQ ff tt FORMAT: Where ‘ff’ and ‘tt’ are the FROM and TO phase pattern numbers as defined in the OMCU’s configuration data.
~~PAGE 237~~
GEMINI2 Traffic Outstation Handbook 13.6.15 Vehicle Absence Failure (FLT VAF) The OMCU continually monitors detector inputs and if it senses that a particular input has not changed to the active condition for the configured time the following data will be presented: FLT:!VAF n FORMAT: ‘n’ represents the number of the input that has failed in the range 0 to 63. See section 5.6.3, which starts on page 91, for locations of the Outstation inputs on the I/O Boards fitted.
~~PAGE 238~~
GEMINI2 Traffic Outstation Handbook VMS Fault Code Descriptions: VMS Fault Code Fault Name Description MSG VMS Message Set Failed LDF VMS LED Fault LNF VMS Lantern Fault VPF VMS Sign Processor Fault PWF VMS Sign Power Failed CLF VMS Communications Link Fault ERR VMS Emergency LSF VMS Light Sensor Fault WDG VMS Sign Watchdog Reset Fault NSR VMS No Sign Response Fault DIS VMS Not Enabled Cannot set the message on the sign, the message is not formatted correctly.
~~PAGE 239~~
GEMINI2 Traffic Outstation Handbook 13.7 PSTN COMMAND TABLE Code CCA Major Index - Minor Index 0–1 CCM - 0–1 CDA - 0–3 CDC 0–1 0–9 CDM - 0–3 CTR 0-1 0-2 CRQ - 0 667/HB/32600/000 Data Range - Description Show Actual Call Count Minor index: 0 – Actual Call Count Out (today).  1 – Actual Call Count In (today).  0 - 255 Set Maximum Call Count Minor index: 0 – Maximum Call Count Out (per day).  1 – Maximum Call Count In (per day).  Range (0 = no limit).
~~PAGE 240~~
GEMINI2 Traffic Outstation Handbook Code CTN Major Index 0-2 Minor Index 0 - 11 Data Range HEX FTR - 0-3 - MCI - 0-1 - MDC 0 - 12 0-1 - MOS - - ASCII MPC RIF - - 0-1 - RSC - - - 667/HB/32600/000 Description Configured Telephone Numbers Major Index: Telephone number pointer. Minor Index: Digits 0 - 1 : Length of telephone number 2 - 11: Telephone Digits (Displayed in pairs).
~~PAGE 241~~
GEMINI2 Traffic Outstation Handbook Code RTR Major Index - Minor Index 0-2 Data Range TNP - - - Description Display RETRY TIMER Minor Index: 0 - Hours 1 - Minutes 2 - Seconds Data: Time Display TELEPHONE NUMBER POINTER Data: 0 - 2 (showing which telephone will be dialled next). Access Level RO RO  These parameters are reset at midnight or first time power up. (Active calls at midnight are not included in the new call count).  These parameters are reset at first time power up. 13.7.
~~PAGE 242~~
GEMINI2 Traffic Outstation Handbook 7 8 9 Message timeout (i.e. although carrier is present the Instation has not sent a message to the OMCU for at least 20 minutes). Identity timeout (i.e. the OMCU has not received an identity request during the required period). The OMCU detected a supply ‘brown-out’ and terminated the call that was in progress at the time. If the maintenance access code has been entered the log data can be reset by entering ‘=0’. 13.7.
~~PAGE 243~~
GEMINI2 Traffic Outstation Handbook 3 4 DATA SET READY CALLING/ANSWERING 5 6 Not used CALL REQUEST 7 CALLING INDICATE Link established with the Instation modem Call/answer sequence in progress (0 = calling & 1 = answering). Auto-call by OMCU (not set if retry delay is preventing the OMCU from dialling out) Answer to ringing tone required Second Byte (i.e. Minor index = 1): BIT No. 0 1 2 3–7 SIGNAL NAME CALL INTERRUPTED DATA LINE OCCUPIED DATA TERMINAL READY Unused. STATE REPRESENTED Not used.
~~PAGE 244~~
GEMINI2 Traffic Outstation Handbook 11 12 Transmit block-buffer usage Error message buffer usage If the maintenance access code has been entered the log data can be reset by entering ‘=0’. 13.7.5 Modem Power Cycle (MPC) The MPC function will cause the power to the modem to be switched off and on again after approximatley 1 second at 3:50 am. To enable this funtion the handset command MPC=1 should be entered when in maintenance mode, MPC=0 disables it. The default condition is disabled.
~~PAGE 245~~
GEMINI2 Traffic Outstation Handbook 13.8 MAINTENANCE COMMAND TABLE Code BAS Major Index - Minor Index - Data Range 0-2 CAL - - 0-1 CBR - - 0, 101 105 EBR - - 0 - 31 EEL - - 0 - 255 ENR 0 -FFFF - ENG 667/HB/32600/000 Description Handset Display Base: 0 = Binary, 1 = HEX, 2 = Decimal Call Instation: Request local dial-back using configured telephone numbers.
~~PAGE 246~~
GEMINI2 Traffic Outstation Handbook Code ERR Major Index - Minor Index - FLG - - FRE - 0-3 0 - 99 GRC - - text 667/HB/32600/000 Data Range 0 - 100 Description Enable Restart Reports: 0=Disable, 1=Enable Values higher than 1 are used to log diagnostic data in the Operations Log as follows: 2=TCAM UTC control data and status flags. 4=UTC data on serial link to controller. 8=Upload/download data on serial link to controller. 16=Handset messages on serial link to controller.
~~PAGE 247~~
GEMINI2 Traffic Outstation Handbook Code INI Major Index - Minor Index - Data Range 0–3 IOP - 0-7 - LTS - - 0-255 OPM - - - PIC - - - RIC PUD - 0-5 - RAM - - 256 or 1024 667/HB/32600/000 Description Initialise Outstation: INI=0 restarts the software without initialising any RAM data. INI=1 clears all Outstation RAM, Fault Log, Operations Log and configuration data. On a combined OMCU and MOVA unit, INI=1 just initialises the OMCU.
~~PAGE 248~~
GEMINI2 Traffic Outstation Handbook Code RCS Major Index - Minor Index - Data Range - SCT - - 0-7 SEB - 0-3 - SEC - - 0-4 SES 0-9 0-1 0 -FFFF SOB - - ENG 667/HB/32600/000 Description Radio Clock Signal: Displays message being received from the Radio Clock and Radio Clock error counts. See 13.8.5 Set 0141 Controller Type 1=T200/T400, 2=C3000, 3=TLC, 4=Through Port, 5=CX, 6=Microsense, 7=Peek PTC1 0=Command actioned. Only operates while the OMCU is unconfigured. Soft Error Buffer.
~~PAGE 249~~
GEMINI2 Traffic Outstation Handbook Code SOP STP TMP Major Index 0-2 board number Minor Index - Data Range BINARY - - 0 - 63 1 - 64 flag no. 667/HB/32600/000 - 0-1 Description Set output ports - sets/displays the state of the 16 outputs on Bus / MOVA I/O board ‘n’ (0-2), e.g.
~~PAGE 250~~
~~GEMINI2 Traffic Outstation Handbook Code TOD Major Index - Minor Index - XXC - - XXM or MOVA - - XXO - - Data Range Description time format TOD displays day, date and time. e.g.~~
~~PAGE 251~~
GEMINI2 Traffic Outstation Handbook DATA 0 1 2 3 4 5 FUNCTION Monitoring On Monitoring Off Configuration Data being downloaded Configuration Download Fail Configuration Checksum Failure OMCU Unconfigured. 13.8.
~~PAGE 252~~
~~GEMINI2 Traffic Outstation Handbook 13.8.~~
~~PAGE 253~~
GEMINI2 Traffic Outstation Handbook 13.8.6 Green Record Command (GRC) The GRC command displays the last Green Record Logging command (if any) received from the RMS instation. The display format is:GRC: , where = start date + start time each day = end date + end time each day = indicates stage and/or phase logging command received.
~~PAGE 254~~
GEMINI2 Traffic Outstation Handbook 2. Green Record - Phase Termination 18-FEB-10 12:02:02 645.8s phase B end, ON time:10.0s “18-FEB-10 12:02:02” Timestamp of the event “645.8s” Timestamp in seconds from startup “phase B end” This is the phase which has just terminated green “ON time:10.0s” This is the preceeding green period for the phase 3. Green Record - Stage Change 19-FEB-10 13:25:29 4779.7s strm:3 mde:2 15.0s stg:12->255 “19-FEB-10 13:25:29” Timestamp of the event “4779.
~~PAGE 255~~
GEMINI2 Traffic Outstation Handbook 13.8.8 RMS 8-Bit Comms Code BSZ Major Index - 667/HB/32600/000 Minor Index - Data Range Description 1Block Size: The maximum number 1024 of bytes which can be transferred in an 8-bit RMS message between the Outstation and RMS Instation in either direction.
~~PAGE 256~~
GEMINI2 Traffic Outstation Handbook 13.9 BUS OPERATING COMMAND TABLE Code DBM Major Index - Minor Index - OLG - - BRX - - Data Range Description Display Bus Messages: Real time monitoring of bus/vehicle detection message reception on all RS485 channels. Operations Log: Display time stamped operations log, one line at a time. Shows the date and time of the most recent vehicle detections. See overleaf for description.
~~PAGE 257~~
GEMINI2 Traffic Outstation Handbook Code Major Index Minor Index Data Range Description appended. For example : BRX=LS 0123456789ABCDEF BRC - - 065535 BRP - - 0 - 11 (4 ports per board) TfL specific command: Major Minor Code Index Index BMD 667/HB/32600/000 SIETAG Bus Detect Character strings beginning ‘1L’ – ‘4L’ are assumed to be Bus Detect messages from SIETAG Readers V4.0 or later and have a CR appended.
~~PAGE 258~~
GEMINI2 Traffic Outstation Handbook Code RMD Major Index - 667/HB/32600/000 Minor Index - Data Range Description 0 – 9 RTIG Message Delay This command sets / displays the minimum delay in 6.67ms units by which the RS485 responses to RTIG messages are delayed. See BMD description above for values.
~~PAGE 259~~
~~GEMINI2 Traffic Outstation Handbook 13.9.1 Operations Log Display Formats (OLG) The Operations Log holds approximately 10,000 vehicle detect or other messages. 1.~~
~~PAGE 260~~
GEMINI2 Traffic Outstation Handbook 2. Beacon Bus Detection 25-APR-99 10:41:10 BID:6 B:6734256 R:560 PI:2 PO:2 O:1 M:90 BID B R PI PO O Beacon ID Bus Radio ID Bus Logical Route ID Priority Input Level Priority Output Output Action M Message Count HEX, 1 - FF DECIMAL, 0 - 9999999 DECIMAL, 0 - 999 DECIMAL, 0 - 9 DECIMAL, 0 - 7 DECIMAL 0 = No output action defined 1 - 30 = Output Action List entry number 229 - 255 = Reason for rejection DECIMAL, 0 - 99 3.
~~PAGE 261~~
GEMINI2 Traffic Outstation Handbook 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 Trigger Point not Found in Output Association List Schedule Deviation not Found in RTIG Priority Map Input Priority not Found in RTIG Priority Map Movement Number not Found in Output Association List LVCC not Found in Output Association List Invalid Loop Number Invalid Message Count Invalid Tag Mode in Configuration Invalid Area Mode in Configu
~~PAGE 262~~
GEMINI2 Traffic Outstation Handbook 13.10 BUS CONFIGURATION COMMAND TABLE 13.10.1 Generic Commands BFT Major Index - Minor Index 0 - 15 as BID Data Range 0 - 255 BFO - - 0 - 255 BFR - - 0-2 JID - - 0-9 and Code LDV - 667/HB/32600/000 - 0 - 11 Description Bus DFM Fault Time 1-255 = The beacon/reader/RTIG input is reported faulty if no priority vehicle is detected for this number of hours. Reported OK on the next detection. Covers both RS485 and contact type inputs.
~~PAGE 263~~
GEMINI2 Traffic Outstation Handbook Code Major Index Minor Index Data Range Description Access Level defaults. 2 x Control & 6 x Reply bytes. 6 = Load UTMC VMS Outstation defaults. 12 x Characters ; 2 x Rows 7 = Enable MOVA facility. 8 = Load UTMC OTU Outstation defaults for Enhanced Serial Link with 2 x Control & 6 x Reply bytes. 9 = Enable TCAM facility. 10 = Enable GRAPHOS facility. 11 = Load TfL Bus Processor defaults for RTIG operation.
~~PAGE 264~~
GEMINI2 Traffic Outstation Handbook RCR Major Index - Minor Index - Data Range 0-2 RET - - 0 - 300 RTO - - 0 - 255 SRC - 0 - 15 0 - 255 Code as BID 667/HB/32600/000 Description Radio Clock fault Reporting 0 = No fault reporting 1 = Non-urgent (interrogation only) 2 = Urgent report (dial out) Re-activation Time 0-300 = If a vehicle is re-detected within this time (in seconds), then the second detection is ignored. This is only applied to the 16 most recent vehicles detected at the site.
~~PAGE 265~~
GEMINI2 Traffic Outstation Handbook 13.10.2 TfL Beacon Commands Code ACT Major Index 1 – 30 Minor Index 0 Data Range 0 - 1000 1 0 – 20 2 0 – 20 3 0 – 255 0 0 - FF 1 0 - 255 2 3 4 5 6 7 8 0 - 998 0 - 998 0 - 10 list entry number ASS 0 - 255 list entry number 667/HB/32600/000 Description Output Period 0-1000 = Time for which the Detect Outputs are activated, in 0.1 sec units (100 secs max) Start Delay 0-20 = Time delay before activating the Detect Output, in 0.
~~PAGE 266~~
GEMINI2 Traffic Outstation Handbook Code BID Major Index - Minor Index Data Range 9 hh:mm 10 hh:mm 11 12 13 14 0-1 0 - 15 0 - FE beacon list entry number LAN - - 0 - FFF MAP - 0-9 input priority 0-7 667/HB/32600/000 Description 9 = Mon to Fri, 10 = Sat and Sun 0 = Every day (default) Start Time hh = hours, 0-24 mm = min, 0-59 Finish Time hh = hours, 0-24 mm = min, 0-59 If finish < start then the finish time is for the following day (i.e.
~~PAGE 267~~
GEMINI2 Traffic Outstation Handbook 13.10.3 SIETAG Commands Code ACT Major Index 1 - 30 Minor Index 0 list entry number 1 2 3 ARM - 667/HB/32600/000 - Data Description Range 0 - 1000 Output Period 0-1000 = Time for which the Detect Outputs are activated, in 0.1 sec units (100 sec max) 0 - 1000 Start Delay 0-1000 = Time delay before activating the Detect Output, in 0.
~~PAGE 268~~
GEMINI2 Traffic Outstation Handbook Code Major Index Minor Index Data Range ARV - - 0-F ASS 0 - 255 0 0 - FF 1 0 - 255 2 3 4 - list entry number 667/HB/32600/000 0FFFFFF Description 2 = Priority mode: discard vehicle message if area field is less than Area Value Area Value 0-F = Sets either the zone or priority level for vehicle message filtering, depending on Area Mode.
~~PAGE 269~~
GEMINI2 Traffic Outstation Handbook Code BID Major Index - Minor Index 11 12 13 14 0 – 11 Data Range 0 - FF serial port number 12 - 15 not used CUS - 0 - 15 0 - FFF DFA - 0 – 15 as BID 0 - 30 TAF - - 1-3 TAI - - 0 - 255 667/HB/32600/000 Description hh = hours, 0-24 mm = min, 0-59 If finish < start then the finish time is for the following day (i.e. spans midnight) Unused Unused Unused Unused SIETAG Reader ID 1-F = Assign this Reader ID to the RS485 serial port (index).
~~PAGE 270~~
GEMINI2 Traffic Outstation Handbook 13.10.4 RTIG Commands Code ACT Major Index 1 - 30 Minor Index 0 Data Range 0 – 1000 1 0 – 20 2 0 – 20 3 0 - 255 0 0 - FF 1 0 - 255 2 3 4 5 6 7 8 0 - 998 0 - 998 0 - 10 list entry number ASS 0 - 255 list entry number 667/HB/32600/000 Description Output Period 0-20 = Time for which the Detect Outputs are activated, in 0.1 sec units (2 sec max) Start Delay 0-20 = Time delay before activating the Detect Output, in 0.
~~PAGE 271~~
GEMINI2 Traffic Outstation Handbook Code BID Major Index - Minor Index Data Range 9 hh:mm 10 hh:mm 11 0 - 255 12 0 - 255 13 0 - 255 14 0-1 0 – 15 FF serial port numbe r PRI - 0-1 0 - 255 RCM - - 0 - 255 667/HB/32600/000 Description Access Level 9 = Mon to Fri, 10 = Sat and Sun 0 = Every day (default) Start Time hh = hours, 0-24 mm = min, 0-59 Finish Time hh = hours, 0-24 mm = min, 0-59 If finish < start then the finish time is for the following day (i.e.
~~PAGE 272~~
~~GEMINI2 Traffic Outstation Handbook Code RPM Major Index 0 - 31 Minor Index 0 1 2 TSN - 667/HB/32600/000 - Data Range Description functionality of the RTIG radio link.~~
~~PAGE 273~~
GEMINI2 Traffic Outstation Handbook 13.11 Bus Configuration Notes All configuration commands take effect as soon as they are entered, except for POC. The POC command changes the RAM data, but the hardware serial ports are not reconfigured until the POS command is used or the Outstation is powered off then on.
~~PAGE 274~~
GEMINI2 Traffic Outstation Handbook 13.12 CAR PARK COUNT COMMAND TABLE ACC Major Index - Minor Index 1 - 23 Data Range 0-1 ACN - - 0 - 254 ACV - - 0-1 ADN - - 10 ASCII digits ADS - - 0-1 AFN - - 10 ASCII digits AFR - - 0-1 Code 667/HB/32600/000 Description APT Counting category Counts on an APT Skidata systems are divided into categories to cover, for example, contract parking, public parking, people who have used credit cards etc.
~~PAGE 275~~
GEMINI2 Traffic Outstation Handbook Code AFT Major Index - Minor Index 0 1 AIP - - APN - - CCL - 0-9 COS - - CPC CPL 0-9 0 Data Description Range 0 - 16383 Car park almost full increasing threshold This value indicates the car par occupancy level when the car park state changes from Spaces to Almost Full.
~~PAGE 276~~
GEMINI2 Traffic Outstation Handbook Code Major Index Minor Index 1 Data Range 0 - 255 2 0 - 255 3 0 - 255 4 0 - 255 Description Access Level A Loop Input 0 - 47 = Input on 1st I/O board 48 - 95 = Input on 2nd I/O board 96 - 143 = Input on 3rd I/O board 255 = Loop not used No Detect Period 1 - 255 = The car park loop is reported faulty if no vehicle is detected for this number of hours.
~~PAGE 277~~
GEMINI2 Traffic Outstation Handbook Code DBG Major Index - Minor Index 0 Data Range 0 to 4 Description Enable / Disable debug Minor index is the code module from which debug output will be enabled (with the exception of index = 1, see below), data is the level of output.
~~PAGE 278~~
GEMINI2 Traffic Outstation Handbook FCP Major Index - Minor Index - FUT - 0 Code 1 RMP - 0 1 2 3 667/HB/32600/000 Data Range 1 - 63 Description Fill Rate Calculation Period The number of minutes of historical count data that the fill rate is computed over. 0 - 16383 Car park full increasing threshold This value indicates the car par occupancy level when the car park state changes from Almost Full to Full.
~~PAGE 279~~
GEMINI2 Traffic Outstation Handbook 13.13 PAKNET/GPRS COMMAND TABLE ADR Major Index - Minor Index - Data Range 0 - 254 GUP - - - IPI - 0 - KEY - - PPD PTO RCA - - 16 ASCII digits 14 ASCII digits 0 9 RCB - - 0-4 Code 667/HB/32600/000 Description Address of the OMCU This is used to check the message received from the Instation is for this OMCU. GPRS User logon:password e.g. GUP=web:web Set IP address and port number of Instation PC e.g. IPI 0=192.168.100.
~~PAGE 280~~
GEMINI2 Traffic Outstation Handbook Code Major Index Minor Index RCT Data Range 0-6 RCU - - 0-1 RDF - - 0 -1 667/HB/32600/000 Description Remote Comms Type 0 = PSTN 1 = PAKNET 2 = GPRS with iConnector 3 = GPRS with direct connection to MC35 Terminal 4 = Null modem PPP 5 = Leased line PPP 6 = Direct manual access to modem Remote Comms Update This command requests the OMCU to dial the Instation and transmit the status message.
~~PAGE 281~~
GEMINI2 Traffic Outstation Handbook 13.14 DUSC COMMAND TABLE 13.14.1 CLF Operating Commands APL Major Index - Minor Index - CCP - - CCT - - CGR - Stream 0 - 31 CGT - Stream 0 - 31 CID - - Code 667/HB/32600/000 Data Range CLF plan 0 - 15 or Isolate 255 Description And Remarks Active CLF Plan is displayed. Use RPL to request a different plan or Isolate. NOTE: When CLF is isolated due to fault this command still indicates the requested plan, even though it’s not running CLF.
~~PAGE 282~~
GEMINI2 Traffic Outstation Handbook Code COD CYC MTS OPS Major Index - Minor Index BUS/ MOVA I/O board No (0 – 2) Data Range 0-2 Description And Remarks Copy Detectors Copy to Outputs on this board: 0 = Allow normal control of outputs (e.g. by CLF facility).
~~PAGE 283~~
GEMINI2 Traffic Outstation Handbook RPL Major Index - Minor Index - Data Range CLF plan 0 – 15 or Isolate 255 SWS - Event 0 - 31 0-1 Code 667/HB/32600/000 Description And Remarks Requested CLF Plan Displays the plan requested by the timetable / user defined conditioning and can be used by the operator to request a different plan until the next timetable event (or CCP is used). Timeswitch Settings Displays the state of each timeswitch event, either active or inactive.
~~PAGE 284~~
~~GEMINI2 Traffic Outstation Handbook 13.14.1.1 Monitor CLF Status (MTS) 1) When a CLF plan is running MTS n: Plan :,Group :, Action , See table below for explanation of information types.~~
~~PAGE 285~~
GEMINI2 Traffic Outstation Handbook 13.14.2 Accessing CLF Configuration Data Commands Major Index - Minor Index - Data Range 0-1 CAO Action number 0 - 31 0-3 0 - 255 CCC - - 0 – 255 secs CCF - - 0 – 255 secs CEC - Action number 0 - 31 0-1 Code ACF 667/HB/32600/000 Description And Remarks CLF Action on Compliance Fail This is the action that is performed when the OMCU detects a compliance failure.
~~PAGE 286~~
GEMINI2 Traffic Outstation Handbook Code Major Index set 0 – 15 Minor Index CLF group 0 - 31 IFA Influence IFN Influe set 0 – 15 CLF group 0 - 31 OFF CLF plan 0 - 15 Time part 0-1 PIA - - PLE - CLF plan 0 - 15 PLI - CLF plan 0 - 15 667/HB/32600/000 Data Range Action number 0 31 Description And Remarks Influence Action Number i.e. which action (and thus which stream) does this group introduce in the specified influence set. Influe Type Influence Function 0-3 i.e.
~~PAGE 287~~
GEMINI2 Traffic Outstation Handbook PLT Major Index CLF plan 0 - 15 PLX - RSA - Code 667/HB/32600/000 Minor Index CLF group 0 - 31 Data Range 0 – 255 secs Description And Remarks Plan Time For the specified CLF plan and group i.e. the time within the cycle that this group comes into effect, where any value larger than the cycle time disables the group for that plan. These times are specified as an offset from the start of the plan cycle.
~~PAGE 288~~
GEMINI2 Traffic Outstation Handbook TDY Major Index - TSD - TSH Entry 0 - 31 Code 667/HB/32600/000 Minor Index Day Code 0 - 15 Data Range Text Description And Remarks Timetable Day Codes Displays the configured day codes where: ‘Sun’, ‘Mon’… are displayed if the day code just selects a single day. ‘Xsu’, ‘Xmo’… are displayed if the day code selects all but one particular day, e.g. ‘everyday except Sunday’ or ‘everyday except Monday’.
~~PAGE 289~~
GEMINI2 Traffic Outstation Handbook Code TSW Major Index Entry 0 - 63 667/HB/32600/000 Minor Data Index Range Second Value 0 Index 215 0-5 Description And Remarks TimeSwitch Settings Contain 64 ‘timetable’ entries numbered 0 to 63, identified by an ‘N’ in the following descriptions. Each entry consists of 6 items that are described in section 13.14.2.2. If any of the items are out of range, then the OMCU ignores the whole timetable entry.
~~PAGE 290~~
GEMINI2 Traffic Outstation Handbook 13.14.2.1 Influence Function (IFN) Each influence function is described below: Type Explanation 0 Deactivate - Deactivate all outputs associated with this output action stream 1 Activate - Deactivate any existing outputs for the stream and activate the specified output action. NB: Any conditional activations (influence type 2) for the stream are discarded.
~~PAGE 291~~
GEMINI2 Traffic Outstation Handbook TSW N 4 : 3 TSW N 5 : The operation code ‘3’ tells the OMCU to introduce the timeswitch event specified by ‘TSW N 5’, without affecting any other timeswitches. TSW N 4 : 4 TSW N 5 : The operation code ‘4’ tells the OMCU to cancel the timeswitch event specified by ‘TSW N 5’, without affecting any other timeswitches. 13.14.
~~PAGE 292~~
GEMINI2 Traffic Outstation Handbook Code CKM Major Index - Minor Index - CKR - - CKS - - CSI - - 667/HB/32600/000 Data Range text Description And Remarks GPS Clock monitor This command is used to display the last message from the GPS receiver. This will indicate if the Outstation is getting valid GPS clock synchronisation times. The format of the display will be as follows:CKM:$GPRMC,hhmmss,status Where : Hhmmss = time of day Status = A or V, A=available, V=not available.
~~PAGE 293~~
~~GEMINI2 Traffic Outstation Handbook 13.~~
~~PAGE 294~~
~~GEMINI2 Traffic Outstation Handbook 13.~~
~~PAGE 295~~
~~GEMINI2 Traffic Outstation Handbook 13.17 OMCU EVENT AND SWITCH OVERRIDE COMMAND TABLE 13.17.~~
~~PAGE 296~~
GEMINI2 Traffic Outstation Handbook 13.18 VEHICLE CLASSIFIER COMMAND TABLE 13.18.1 Vehicle Classifier Common Configuration Code VCC Major Index - 667/HB/32600/000 Minor Index 0 Data Range 0–4 1 0 or 1 – 255 2 0 or 1 – 255 3 0 or 1 – 32 4 0 or 1 - 32 Description Number of Sites Total number of loop sites Maximum Presence Time The time in minutes after which continued loop activation generates a vehicle presence loop fault.
~~PAGE 297~~
~~GEMINI2 Traffic Outstation Handbook 13.18.1.~~
~~PAGE 298~~
GEMINI2 Traffic Outstation Handbook If Output Action Type is 0 or 1 then the following data is displayed. VOA 0 – 31 1 0 – 255 2 1 – 255 3 0–5 or 255 4 0 – FF 5 0–5 6 0 - FF Output action number 667/HB/32600/000 Activation Delay The total number of seconds that must elapse before the outputs are activated. Activation Duration The total number of seconds that the outputs are to be activated. Port A Port number corresponding to one of the total number of 8-bit ports on one or more IO cards.
~~PAGE 299~~
GEMINI2 Traffic Outstation Handbook If Output Action Type is 2 then the following data is displayed. VOA 0 – 31 1 0 – 255 2 1 – 255 3 0–4 or 255 4 0 – 11 or 250 Output action number Activation Delay The total number of seconds that must elapse before the first transmission message is sent. Activation Duration The total number of seconds that must elapse before the second transmission message is sent.
~~PAGE 300~~
GEMINI2 Traffic Outstation Handbook Code Major Index Minor Index 2 3 4 5 667/HB/32600/000 Data Range 1–8 Description Access Level Number of Lanes The number of lanes at the site. 0–1 Logging Control Byte 0 Bit 0 = Enable / Disable Traffic Data reporting. A Bit set to a 1 indicates that the control is enabled. All other bits (bits 1 to 7) are set to zero. 0 – FF Logging Control Byte 1 Controls whether VC events are to be logged for a given lane at the site.
~~PAGE 301~~
GEMINI2 Traffic Outstation Handbook 13.18.1.4 Vehicle Classifier Transmission Messages Code VTM Major Index 0–4 Minor Index 0-1 Data Range See note Message pair Description Transmission Message Transmission messages are grouped in pairs. A message consists of 40 bytes of binary data that are selected for transmission via one of the available serial communications links when a vehicle satisfies a detection condition that specifies an output action identifying a transmission message.
~~PAGE 302~~
GEMINI2 Traffic Outstation Handbook Code VCF Major Index - Minor Index 1 Data Range 0 – 255 2 0–2 Description Confirmation Fail Clearance Time Time in seconds for which all confirmation inputs must be active before a confirmation fault clearance report is generated [1255]. 0 = input confirm monitoring is disabled Confirmation Fail RRB Urgency setting for confirmation fault and confirmation fault clearance reports i.e. not reported [0], reported on interrogation only [1] or urgently reported [2].
~~PAGE 303~~
GEMINI2 Traffic Outstation Handbook Code Major Index Minor Index 2 Data Range 1 - 60 Description Access Level Averaging Period Indicates the period over which speed, headway and occupancy statistics are collected before averaging occurs. The value is a number of minutes. 13.18.1.7 Vehicle Classifier Speed Bands Code VSB Major Index - Minor Index 0-6 Data Range 0 – 255 Description Speed Band The speed of the vehicle in kph.
~~PAGE 304~~
GEMINI2 Traffic Outstation Handbook 13.18.1.9 Vehicle Classifier Vehicle Type Categories Code VVT Major Index 0 – 15 Minor Index 0 Data Range Up to 20 ASCII chars 0 – 9 and A–F 1 0 - 255 Vehicle Type Description Category Text ASCII text string identifying the type of vehicle being classified in the associated category. The first byte of the string contains the length of the string in bytes [0-19] (not including the length byte).
~~PAGE 305~~
GEMINI2 Traffic Outstation Handbook The above test message is sent when the VRC command is assigned a count. Code VRC Major Index - Minor Index - Data Description Range 0 - 65535 Test Message Receive Count Repeats the VRX command for the given count. Allows the simulation of a large number of vehicles for test purposes. . Access Level Maint 13.18.1.
~~PAGE 306~~
GEMINI2 Traffic Outstation Handbook 13.18.1.12 Vehicle Classifier Detect Condition Statistic Category Map Code VSM Major Index - 667/HB/32600/000 Minor Index 0 – 31 Data Range 0 – 15 Description Statistic Category Identifies the statistic category that is to be incremented each time the corresponding detection condition occurs (assuming counting for the detection condition is enabled).
~~PAGE 307~~
GEMINI2 Traffic Outstation Handbook 13.18.2 Operations Log Capacity The Operations Log holds approximately 12,000 VC. The following table provides a summary of Operations Log capacities containing TD events only for typical configurations assuming a 1 minute averaging period. For other averaging periods the log capacity is increased.
~~PAGE 308~~
GEMINI2 Traffic Outstation Handbook 31. NOTE: A vehicle longer than 25.5m is limited to 25.5m in the VC event. A headway of greater than 25.5s is limited to 25.5s. Examples 23-JAN-02 16:30:00 L:12 CAR 5.23m 50kph 6.2s O:1 A vehicle classed as a CAR on site 1 lane 2 was recorded with a length of 5.23m, a speed of 52kph and a headway of 6.2s. The detection invoked output action 0. 23-JAN-02 16:32:00 L:12 BIG THING 12.01m 70kph 25.
~~PAGE 309~~
GEMINI2 Traffic Outstation Handbook followed by up to 16 statistic categories (there may be none as dictated by the configuration): ““ STATISTIC CATEGORY 1 5 Text Decimal 0 – 65535 followed by up to 8 locations supplied with average speed, average headway and average occupancy values: “ L:” SITE / LANE ““ AVERAGE SPEED “kph ” or “mph ” AVERAGE HEADWAY “s ” AVERAGE OCCUPANCY “%” 3 2 1 3 4 4 2 3 1 Text Hexadecimal Text Decimal Text Decimal Text Decimal Text 0–3/0–7 0 – 255 0.0 – 25.
~~PAGE 310~~
GEMINI2 Traffic Outstation Handbook 13.19 UTMC GENERAL COMMAND TABLE Code IPM Major Index - Minor Index 0 Data Range Number 1 Number 2 Number 3 Number 4 Number (IPR=2 to activate) 667/HB/32600/000 Description IP Outstation Address Manual configuration. Number is of the form: xxx.xxx.xxx.xxx Default – not specified. IP Gateway Address configuration. Number is of the form: xxx.xxx.xxx.xxx Default – not specified. IP Broadcast Address configuration. Number is of the form: xxx.xxx.xxx.xxx.
~~PAGE 311~~
GEMINI2 Traffic Outstation Handbook IPR Major Index - Minor Index - IPB - - BPR - - OID - - LDV - - Code 667/HB/32600/000 Data Range 1 or 2 Description IP Reset Command Used to initialise communications with the Instation via the Ethernet port. For networks with automatic address allocation, use IPR=1. For networks with manual address allocation, enter address using IPM 0 etc and then use IPR=2. IPR=1 initiates an automatic BOOTP sequence across the network.
~~PAGE 312~~
GEMINI2 Traffic Outstation Handbook IPA Major Index - Minor Index 0-4 Data Range Number LOC - - ASCII Location MAC - - HEX MAC address LIF - - ASCII Code Facilities code LIN - - nnnn nnnn Licence code 667/HB/32600/000 Description IP Address Displays the actual IP address being used by the outstation following IPR=1 or IPR=2 commands. Format as IPM above. Outstation Location Displays the location of the outstation as a text string e.g. PINHOE, ST MARKS.
~~PAGE 313~~
GEMINI2 Traffic Outstation Handbook HIC Major Index - Minor Index - Data Range number KIC - - text Code 667/HB/32600/000 Description Hardware Identity Code Displays the identity number assigned to the CPU card in production. The value is the same as the bar code serial number on the CPU card. Kernel Identity Code Displays the issue string of the eCos operating system kernel.
~~PAGE 314~~
GEMINI2 Traffic Outstation Handbook 13.20 UTMC OTU COMMAND TABLE 13.20.1 UTMC OTU Communication Set-Up Commands GCW Major Index - Minor Index 0 Data Range 0–8 Control GRW - 0 0 – 16 Reply GOE - - 0 or 1 Enable Code 667/HB/32600/000 Description No. of control words Configures the number of bytes of control data sent each second from the UTC Instation. The index of zero is used for compatibility with the TC12 GCW command. Default: (2) No.
~~PAGE 315~~
GEMINI2 Traffic Outstation Handbook 13.20.2 UTMC OTU Control and Reply Bit Allocation Commands Code GSA Major Index - Minor Index 0 to 23 SCOOT Loop Data Range 0 to 151 Input Description Note GSA references inputs from 0, ie GSA 0 = 0 allocates SCOOT loop 0 to input 1 LDV - - 5 or 8 GUD - 0 - 15 0 – 151 Input number U/D number SCOOT Loop Input Allocation For each SCOOT loop, enter the number of the input to which the SCOOT detector is connected or 255 for unused.
~~PAGE 316~~
GEMINI2 Traffic Outstation Handbook Code GRL Major Index 0 – 15 Reply byte Minor Index 0–7 Reply bit Data Range 0 – 255 Description Function GCN 0 – 15 0–7 Control Control byte bit ASCII name GRN 0 – 15 Reply byte 0–7 Reply bit ASCII name TCA - - 0 – 49 TC output 667/HB/32600/000 OTU Reply Bit Definition For each reply byte (0 to 15) set up the function of each bit (0 to 7) in this reply byte. This command is therefore repeated up to eight times for each bit in a reply byte.
~~PAGE 317~~
GEMINI2 Traffic Outstation Handbook Code GIA Major Index 0 – 15 CQO unit Minor Index 0 1 Data Range 0 – 151 Input Description 0–7 Function GAQ - 667/HB/32600/000 0 – 15 CQO unit 0 – 255 Queue active time (secs) Count, Queue & Occupancy Input Configuration Input Allocation: Configure the input line number for the count, queue or occupancy unit. Note: For N + 1 sites the input line allocation represents the kerbside lane loop.
~~PAGE 318~~
GEMINI2 Traffic Outstation Handbook Code GIQ GCF Major Index - - Minor Index 0 – 15 CQO unit 0 – 15 Count unit Data Range 0 – 255 Queue inactive time (secs) 1–8 Weighting factor Description Queue Inactive Time To specify the time in seconds that a configured queue unit input must be inactive before its output (which was previously active) is cleared. Default: 0 Count Unit Weighting Factor The weighting factor is used to define the number of counts required to cause the reply bit to change state.
~~PAGE 319~~
GEMINI2 Traffic Outstation Handbook GIS Major Index - Minor Index 0–7 Input Port DTA - 0 DTI - 0 DEA 0–7 Input Port 0–7 Port Bit DEI 0–7 Input Port 0–7 Port Bit Code 667/HB/32600/000 Data Range Description 00000000 11111111 Input Inversion Enables any of the inputs to be inverted. This facility is required to cater for detectors with normally open output contacts. Default: 00000000 2 – 255 DFM Stuck Active mins The limit specifies the time in MINUTES.
~~PAGE 320~~
GEMINI2 Traffic Outstation Handbook Code GLT Major Index - Minor Index - Data Range 0 – 143 Input number 0-255 GMO Description Lamp Test Setting this value to a valid input number provides a lamp test facility (for use with a green wave box). If the allocated input is active (i.e. “1”) then all the OTU output relays are energised. Default: 255 – lamp test facility disabled. Assigns a bit position in the UTC control word to indicate MOVA fallback.
~~PAGE 321~~
GEMINI2 Traffic Outstation Handbook Data Value 51 52 53 54 55 56 57 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 100 to 199 200*1 201 202 203 204 205 206 207 208 209 210 211 212 213 214 667/HB/32600/000 Meaning for GRL Command unit 2, HIOCC alarm bit, unit 3, HIOCC alarm bit, unit 4, HIOCC alarm bit, unit 5, HIOCC alarm bit, unit 6, HIOCC alarm bit, unit 7, HIOCC alarm bit. Selects two consecutive reply bytes for the return of environmental sensor or SIETAG reader data.
~~PAGE 322~~
GEMINI2 Traffic Outstation Handbook Data Value 215 216 217 218 219 220 221 222 223 Meaning for GRL Command Scoot loop 15 output Scoot loop 16 output Scoot loop 17 output Scoot loop 18 output Scoot loop 19 output Scoot loop 20 output Scoot loop 21 output Scoot loop 22 output Scoot loop 23 output Note: *1 SCOOT loop allocations MUST be on either bit 0 or bit 4 of a reply byte.
~~PAGE 323~~
GEMINI2 Traffic Outstation Handbook GOU Major Index - GQU - ERD - Code GCT Minor Index 0 – 15 Occ Unit 0 – 15 Queue Unit Data Range 8 bits binary - 0-2 0–6 0 - 65535 Comms Diag Description 8 bits binary Display Occupancy Unit Count Displays the current value for the selected occupancy counter. Display Queue Unit State Displays the current state of the selected queue unit output (0 = queue inactive, 1 = queue active). Echo & Repeat Disable ERD=1 disable ‘repeat’.
~~PAGE 324~~
GEMINI2 Traffic Outstation Handbook 13.20.4 UTMC OTU Test / Maintenance Commands IPP Major Index - Minor Index - IPC - - GIO - - GID - 0 – 15 Reply Byte Code 667/HB/32600/000 Data Description Range IP Address Test IP Address Ping: xxx.xxx.xxx.xxx Internet Protocol address to be ‘pinged’ by the outstation in order to check network comms. Default: 0.0.0.
~~PAGE 325~~
GEMINI2 Traffic Outstation Handbook Code RFL Major Index - Minor Index - Data Range 0 or 1 Description Reset The OTU Fault Log RFL = 1 clears the OTU current fault log and extinguishes the fault LED provided that fault conditions are no longer present (historic fault log is unaffected). – NB: Only required to clear DFM Access Level Maint 13.20.
~~PAGE 326~~
GEMINI2 Traffic Outstation Handbook GDO Major Index - Minor Index 0–7 Control Byte Data Range 8 bits binary GDT - - 1 - 254 Override Time (secs) Code Description Control Byte Override Value Allows the default override value of each control byte to be entered. The data is only output when the override timeout expires. This command is only used where a VMS sign uses a “pulsed” interface (e.g. Dambach).
~~PAGE 327~~
GEMINI2 Traffic Outstation Handbook Code GHN GHF Major Index - - Minor Index 0–7 Data Range 1 – 10 Occ Unit Number Consec. Samples - 0 –100 Smooth Factor GHC - - 0 – 100 Threshold Description Consecutive Occupancy Samples The number of consecutive occupancy samples used to determine if an alarm condition exists. Default: 3 Occupancy Smoothing Factor The smoothing factor used in calculating the new smoothed occupancy. This value represents actual smoothing factors of 0 to 1, i.e.
~~PAGE 328~~
GEMINI2 Traffic Outstation Handbook 13.20.8 UTMC OTU Engineering Commands Code SIP Major Index 0–9 Minor Index 0–9 Channel Number Item SIE Data Range 0 – 65535 Time (secs) or State 0-1 Description Simulate Input Simulate input for the selected channel. The Item Index is: 0 – line number of input to simulate, 999 = channel not used.
~~PAGE 329~~
GEMINI2 Traffic Outstation Handbook 13.21 UTMC VMS COMMAND TABLE 13.21.1 UTMC VMS Common Configuration Code VMP Major Index - Minor Index - Data Range ASCII password VMD - - 1 – 240 secs VMS - - 0–7 sign 0 – 120 minutes VMI Description VMS Outstation Password Specified by the customer for remote access. 30 character limit Default: (unset) Outstation Poll Delay. Set the delay (in seconds) between each poll of the signs. Note: This option should be used with care. A delay of less than 8 secs.
~~PAGE 330~~
GEMINI2 Traffic Outstation Handbook VMH Major Index - Minor Index 0–7 sign VMW - 0–7 sign VML - 0–7 sign VMT - 0–7 sign VMA - 0–7 sign VMV - 0–7 sign VMM 0–7 sign 0–5 row Code 667/HB/32600/000 Data Description Range 1–6 Sign Height sign height Define the height (no. of rows) that each sign has. Default: 2 1 – 100 Sign Width sign width Define the width (no. of characters) of each sign. Default: 12 1 or 2 Sign Lanterns lanterns Set to 1 if Lanterns are present, 2 if they are not.
~~PAGE 331~~
GEMINI2 Traffic Outstation Handbook 13.22 GRAPHOS COMMAND TABLE Major Index - Minor Index 0–5 Data Range 0 – 65535 ENG 72 – 75 0 – 255 FLG FLT - 0 – 40 or 0 – 16 - GFR - - 4 – 10 GIP - 0–3 - GMD - - 0–4 GSP GTM - 0–3 0–3 0–4 0 – 255 Code CNT 667/HB/32600/000 - Description Graphos Counts 0 = loss of communications 1 = loss of modified config.
~~PAGE 332~~
GEMINI2 Traffic Outstation Handbook Code LED Major Index 0–3 Minor Index 0 – 31 Sign Number LED String Data Range 0 – 255 LMD - - 0–2 LSO SGM - 0–3 0–4 0 – 100 0–4 Sign Number Description Status of the LED strings A bit set to ‘1’ means a String fault. Major Index: 0 - Master Sign 1 - Slave1 Sign, etc. Minor Index: 0 - LDB1 port1 1 - LDB1 port2 2 - LDB1 port3 3 - LDB1 port4 4 - LDB2 port1 5 - LDB2 port2 ..
~~PAGE 333~~
GEMINI2 Traffic Outstation Handbook 9 - Incorrect picture being displayed 11 - Missing or defect LDB board The third byte is only used with the ‘comms failure/power fail’ fault and it gives the Sign number that has lost the link, i.e., 1 indicates the loss between the Gemini and the Master, 2 indicates the loss between the Master and Slave 1, etc. If the Sign Number is 1 then the loss of comms could be due to a power fail fault because the LSCU has no battery support where as the Gemini Unit has.
~~PAGE 334~~
~~GEMINI2 Traffic Outstation Handbook 667/HB/32600/000 Page 334 Issue 11~~
~~PAGE 335~~
GEMINI2 Traffic Outstation Handbook Appendix A MOVA INSTALLATION SHEETS A copy of this sheet should be completed for each MOVA installation and kept in the controller cabinet as a record of the MOVA installation details for that site.
~~PAGE 336~~
GEMINI2 Traffic Outstation Handbook MOVA INSTALLATION SHEET 1a Site Name and Location: MOVA Licence Number: Installation By: Date: MOVA Detector Inputs Det. No. Use / Name Controller / Det. Terminal Det. No. 1 17 2 18 3 19 4 20 5 21 6 22 7 23 8 24 9 25 10 26 11 27 12 28 13 29 14 30 15 31 16 32 667/HB/32600/000 Page 336 Use / Name Controller / Det.
~~PAGE 337~~
GEMINI2 Traffic Outstation Handbook MOVA INSTALLATION SHEET 1b MOVA Detector Inputs (contd. If requied) Det. No. Use / Name Controller / Det. Terminal Det. No. 33 49 34 50 35 51 36 52 37 53 38 54 39 55 40 56 41 57 42 58 43 59 44 60 45 61 46 62 47 63 48 64 667/HB/32600/000 Page 337 Use / Name Controller / Det.
~~PAGE 338~~
GEMINI2 Traffic Outstation Handbook MOVA INSTALLATION SHEET 2 MOVA Force and Confirm Bits Det. No. Use / Name Cont. Terminal Det. No. Use / Name Cont. Terminal Det. No. TO CRB G11 F1 G1 G12 F2 G2 G13 F3 G3 G14 F4 G4 G15 F5 G5 G16 F6 G6 G17 F7 G7 G18 F8 G8 G19 F9 G9 G20 F10 G10 G21 Use / Name Cont.
~~PAGE 339~~
~~GEMINI2 Traffic Outstation Handbook Appendix B GEMINI2 DRAWINGS B.1 Introduction Section B.2 contains a list of the drawings that are included at the back of this handbook. B.~~
~~PAGE 340~~
~~GEMINI2 Traffic Outstation Handbook 667/HB/32600/000 Page 340 Issue 11~~
~~PAGE 341~~
GEMINI2 Traffic Outstation Handbook Appendix C GNU Open Software License The text below is the licence for the GNU open software that is embedded in the Outstation firmware. This firmware contains modified GPL code and that source code is available on application to Siemens Traffic Controls Ltd as per clause 3a or 3b. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
~~PAGE 342~~
GEMINI2 Traffic Outstation Handbook TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License.
~~PAGE 343~~
GEMINI2 Traffic Outstation Handbook In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3.
~~PAGE 344~~
GEMINI2 Traffic Outstation Handbook court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all.
~~PAGE 345~~
~~GEMINI2 Traffic Outstation Handbook 12.~~
~~PAGE 346~~
GEMINI2 Traffic Outstation Handbook Appendix D MOVA 4 and 5 Setup of MOVA 4 and 5 is largely identical to that for MOVA 6. Some differences are describde here. D.1Complete Initialisation 8) 9.6.2 Initialise MOVA by entering the handset command INI=2. If the OMCU application is not required, enter INI=3 to completely reinitialise the whole unit. Enter LDV=7 to request the MOVA facility. Refer to section 9.
~~PAGE 347~~
GEMINI2 Traffic Outstation Handbook b) Wait for LEDs to start flashing c) Check the ‘MIO’ setting. If 0, set to 1 or 2 appropriately. d) Enter the MOVA Commissioning Screen on the connected PC and set the MOVA Enable Flag. (Section 9.6.8 - Commissioning Screen (LOOK)) e) Use the MOVA Commissioning Screen to confirm that the unit follows the normal warm -up sequence and sets itself back in control.
~~PAGE 348~~
GEMINI2 Traffic Outstation Handbook This option is password protected to prevent unauthorised changes to the site data and can only be attempted locally. The password is case sensitive and is defaulted to ‘AVOMGO’. Up to three ‘plans’ can be loaded into the MOVA 4 unit’s memory. Normally, only plan 1 will be used. However, it is possible to configure the MOVA unit to switch between the plans at different times of day.
~~PAGE 349~~
GEMINI2 Traffic Outstation Handbook finished Reading site data in to plan 1 complete. Do you want to clear the MOVA working data? 1) If you are about to read in another plan then answer “N”. 2) If you have just read in new site data that only makes minor changes and would like to keep the old working data (e.g. the vehicle flows and the assessment log) then answer “N”.
~~PAGE 350~~
GEMINI2 Traffic Outstation Handbook D.3Commissioning Screen (LOOK) 14) 9.6.8 Use the commissioning screen to check for following. a) MOVA is currently not enabled (MOVA enabled = 0) b) The Controller is ready* (CRB = 1) c) The Confirm bits are all set to ‘1’, except for the current stage which should be set to ‘0’. Watch the controller perform at least one complete cycle to check that each stage and phase confirm bit is being activated correctly by the controller.
~~PAGE 351~~
GEMINI2 Traffic Outstation Handbook Typical MOVA 5 Comissioning Screen Detectors: 1--4 0000 SIEMENS MOVA COMMISSIONING SCREEN 5--8 9-12 13-16 17-20 21-24 25-28 29-32 1001 1001 1000 0000 0000 0000 0000 33-36 37-40 0000 0000 Confirms: CRB 1 Force Bits: 1--4 0111 5--8 1111 HI/TO 1 41-44 45-48 0000 0000 49-52 53-56 0000 0000 57-60 61-64 0000 0000 9-12 13-16 0000 0000 17-20 21-24 0000 0000 25-28 29-31 0000 0000 1 1 2 0 3 0 4 0 5 0 6 7 8 9 10 MOVA enabled. . 1 Warmup. . . . .
~~PAGE 352~~
GEMINI2 Traffic Outstation Handbook 16) 9.6.8 Important: The following causes the MOVA unit to take control of the Intersection and care should be taken to avoid undue disruption to traffic flows. Still using the commissioning screen, force each stage in turn and check that the controller moves to the required stage and that the correct stage / phase confirm bits are activated.
~~PAGE 353~~
GEMINI2 Traffic Outstation Handbook Typical MOVA 5 Main Menu Screen Detectors: SIEMENS MOVA COMMISSIONING SCREEN 5--8 9-12 13-16 17-20 21-24 25-28 29-32 1001 1001 1000 0000 0000 0000 0000 1--4 0000 33-36 37-40 0000 0000 Confirms: CRB 1 Force Bits: 1--4 0111 5--8 1111 HI/TO 1 41-44 45-48 0000 0000 49-52 53-56 0000 0000 57-60 61-64 0000 0000 9-12 13-16 0000 0000 17-20 21-24 0000 0000 25-28 29-31 0000 0000 1 1 2 0 3 0 4 0 5 0 6 7 8 9 10 MOVA enabled. . 1 Warmup. . . . . 6 Multi stage . .
~~PAGE 354~~
GEMINI2 Traffic Outstation Handbook INDEX — A — ACF (CLF Action on Compliance Fail) ................................................................... 282 ACT (Beacon Output Action List) ........................................................................... 262 ACT (Bus Output Action List) ................................................................................. 270 ACT (RTIG Output Action List) ...............................................................................
~~PAGE 355~~
GEMINI2 Traffic Outstation Handbook — C — CAL (Call Instation) ................................................................................ 118, 242, 254 CAO (CLF Action Outputs) ..................................................................................... 282 Car Park Commissioning ................................................................................................. 101 Description ..................................................................................................
~~PAGE 356~~
GEMINI2 Traffic Outstation Handbook Controller MOVA Connections .......................................................................................... 141 MOVA Connections (T400/ST800) ................................................................... 143 OMCU Monitoring Commands .......................................................................... 214 TR0141 Interface Cable Installation .................................................................... 96 COS (Car Park Occupancy Status) .......
~~PAGE 357~~
GEMINI2 Traffic Outstation Handbook Handset Commands (SOB and SOP) ......................................................... 43, 245 MOVA Outputs .................................................................................................. 141 Specification........................................................................................................ 32 DIP (Digital Input Ports).................................................................... 43, 103, 109, 217 DOR (Door Input) .............
~~PAGE 358~~
GEMINI2 Traffic Outstation Handbook FFT (Fault Filter Time) ........................................................................................... 221 FI (MOVA Menu – Finish)............................................................................... 159, 161 Firmware Download General Description ............................................................................................ 54 FLG (Fault Log) ..............................................................................................
~~PAGE 359~~
GEMINI2 Traffic Outstation Handbook GIA (CQO Input Configuration) .............................................................. 190, 205, 314 GID (OTU Reply Byte Test Pattern) ............................................................... 205, 321 GIO (OTU Reply Data Override) .................................................................... 205, 321 GIQ (OTU Queue Inactive Time) ............................................................ 191, 205, 315 GIS (OTU Input Inversion)........................
~~PAGE 360~~
GEMINI2 Traffic Outstation Handbook UTMC OTU Output Override ............................................................................ 322 UTMC OTU Test / Maintenance........................................................................ 321 UTMC VMS Common Configuration ................................................................. 326 UTMC VMS Sign Control Configuration ............................................................ 326 Vehicle Classifier ..............................................
~~PAGE 361~~
GEMINI2 Traffic Outstation Handbook Spare Sensors .................................................................................................. 120 LAN (LAN Address) ........................................................................................ 263, 270 LD (MOVA Menu – Load Data set from RAM) ............................................... 154, 346 LDV (Load Default Values) ..............................................................106, 178, 259, 270 LF (MOVA Menu – Look at/set Flags) ....
~~PAGE 362~~
GEMINI2 Traffic Outstation Handbook Telephone Line Sharing .................................................................................... 149 MSI (Mains’ State Inputs) ......................................................................... 43, 103, 218 MTS (Monitor CLF Status) ..................................................................................... 279 — O — OCC (Occupancy Count) .......................................................................................
~~PAGE 363~~
GEMINI2 Traffic Outstation Handbook PIA (Plans Isolate Action)....................................................................................... 283 PIC (Program Identity Code) .................................................................. 104, 110, 244 PLE (Plan Entry Time)............................................................................................ 283 PLI (Plan Influence Set) .........................................................................................
~~PAGE 364~~
GEMINI2 Traffic Outstation Handbook — S — SCT (Set 141 Controller Type) ............................................................... 104, 110, 245 SDC (SDE/SA Extension Requests) ...................................................................... 215 SDF (VC Speed Display Format) ........................................................................... 300 SEB (Soft Error Buffer) ................................................................................... 245, 248 SEC (Soft Error Count).....
~~PAGE 365~~
GEMINI2 Traffic Outstation Handbook Handset Commands ......................................................................................... 311 UTMC OTU Communication Commands ............................................................... 311 UTMC OTU Diagnostic Display Handset Commands ......................................................................................... 319 UTMC OTU Engineering Handset Commands ........................................................................................
~~PAGE 366~~
GEMINI2 Traffic Outstation Handbook VMI (VMS Inactivity Timeout) ................................................................................. 326 VML (VMS Sign Lanterns)...................................................................................... 327 VMM (VMS Sign Message Display) ....................................................................... 327 VMN (VMS RS485 Channel) .................................................................. 200, 209, 326 VMP (VMS Outstation Password) .....
~~PAGE 367~~
~~GEMINI2 Traffic Outstation Handbook LAST PAGE OF THE GEMINI2 TRAFFIC OUTSTATION HANDBOOK 667/HB/32600/000 Page 367 Issue 11~~