Specifications

ManualsBrandsSiemens ManualsKitchen AppliancesHB 904 Series

3U Traffic Outstation Handbook

667/HB/26568/000 Page 1 Issue 15

Siemens Traffic Controls

Sopers Lane

Poole

Dorset

BH17 7ER

SYSTEM/PROJECT/PRODUCT: 3U Traffic Outstation

SIEMENS

3U TRAFFIC OUTSTATION

HANDBOOK

Prepared: Paul Cox

Function: Engineer

THIS DOCUMENT IS ELECTRONICALLY HELD AND APPROVED

Issue

Change Ref. Date

13 TS001837 23

January 2004

14 Not Released 11

March 2005

15 TS001471 11

March 2005

This is an unpublished work the copyright in which vests in Siemens plc. All rights

reserved.

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 (241 pages)

PAGE 1
3U Traffic Outstation Handbook Siemens Traffic Controls Sopers Lane Poole Dorset BH17 7ER SYSTEM/PROJECT/PRODUCT: 3U Traffic Outstation SIEMENS 3U TRAFFIC OUTSTATION HANDBOOK Prepared: Paul Cox Function: Engineer THIS DOCUMENT IS ELECTRONICALLY HELD AND APPROVED Issue Change Ref. Date 13 TS001837 23rd January 2004 14 Not Released 11th March 2005 15 TS001471 11th March 2005 This is an unpublished work the copyright in which vests in Siemens plc. All rights reserved.
PAGE 2
3U 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
U Traffic Outstation Handbook Maintenance Provision (MP) 1. Product Reference Siemens Remote Monitoring System Outstation Monitoring Control Unit (RMS OMCU) Siemens Car Park Count OMCU Siemens Bus Processor Siemens MOVA Unit 2. Specifications The Outstation Monitoring Unit is design to meet the following Highway Agency specification: MCE 0152A 3.
PAGE 4
3U Traffic Outstation Handbook CONTENTS 1. INTRODUCTION.................................................................................................. 10 1.1 PURPOSE.......................................................................................................... 10 1.2 SCOPE............................................................................................................... 10 1.3 RELATED DOCUMENTS................................................................................... 10 1.
PAGE 5
3U Traffic Outstation Handbook 4. OMCU FACILITIES.............................................................................................. 28 4.1 INTRODUCTION................................................................................................ 28 4.2 OMCU AND BUS PROCESSOR FACILITIES.................................................... 28 4.2.1 Signal Lamp Monitoring ............................................................................ 29 4.2.2 Detector and Push-Button Monitoring......
PAGE 6
3U Traffic Outstation Handbook 5.6.12 Mains Supply Connection ....................................................................... 72 5.6.13 Connect Unit Support Battery ................................................................. 72 5.6.14 Peek TRX Controller I/O connections ..................................................... 72 5.7 INSTALLATION OF THE UNIT IN ADDITIONAL OUTERCASE ........................ 73 6. OMCU COMMISSIONING ...................................................................
PAGE 7
3U Traffic Outstation Handbook 9.6.2 Complete Initialisation............................................................................. 115 9.6.3 Phone Line Sharing Facility (PLS) .......................................................... 116 9.6.4 Serial Link Between MOVA and an ST800 (MIO)................................... 117 9.6.5 MOVA Licence Number (LIC) ................................................................. 118 9.6.6 Setting the Time and Date (CT)........................................
PAGE 8
3U Traffic Outstation Handbook 11.6.3 Green Conflict Fault Data (FLT CFL).................................................... 167 11.6.4 Ignoring Demands Fault (FLT CID) ...................................................... 168 11.6.5 Dim/Bright Fault (FLT DBF) .................................................................. 169 11.6.6 Equipment Data Invalid Fault (FLT EDI) .............................................. 169 11.6.7 External Signal Active / Inactive Fault (FLT ESA / ESI) ..................
PAGE 9
3U Traffic Outstation Handbook TABLE OF FIGURES Figure 1 - Overview .................................................................................................. 12 Figure 2 - Basic OMCU to ST700 or ST800 ............................................................. 15 Figure 3 - Basic OMCU to Any Other Controller....................................................... 15 Figure 4 – MOVA to ST700 or ST800 ......................................................................
PAGE 10
3U 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 3U Traffic Outstation, either as a Siemens RMS OMCU, a Bus Processor or a Siemens MOVA unit. 1.2 SCOPE This document covers the Siemens OMCU, Bus Processor and MOVA units. This document does not include any details about the MOVA strategy or how to set up the MOVA configuration.
PAGE 11
3U Traffic Outstation Handbook PSU RAM RMS TCSU TRL VC - Power Supply Unit Random Access Memory Root Mean Square or Remote Monitoring System Traffic Control and Systems Unit Transport Research Laboratory Vehicle Classification 667/HB/26568/000 Page 11 Issue 15
PAGE 12
3U Traffic Outstation Handbook 2. PRODUCT DESCRIPTION 2.1 INTRODUCTION Figure 1 shows an overview of a Siemens Traffic Outstation (shown with 2 LMU I/O boards and a single Bus / MOVA I/O board) and how it connects as a system.
PAGE 13
3U Traffic Outstation Handbook on Monday, and isolate the plan at 6pm on Friday). See section 4.2.9 for more information on the DUSC application. The Flow application can be connected to up to 16 detectors. Each detector can provide flow data over a configured period of time. If the flow data meets the ‘up threshold’, a flow alarm is raised. If the flow data meets the ‘down threshold’, the flow alarm is cleared. Flow data is stored in the ‘Operations Log’, and can be uploaded to the RMS Instation.
PAGE 14
3U Traffic Outstation Handbook Where a Modem is present, it can be connected through a land line to the PSTN or via a GSM 900 digital network. The unit can be communicated with and will report back faults via the PSTN or GSM. When a modem is not present, all Instation functions are available locally via a local RS232 ‘handset’ port. The platform has the facility to share a PSTN connection with other compatible equipment.
PAGE 15
3U Traffic Outstation Handbook 2.2.1 Basic OMCU The Basic OMCU (667/1/28850/000) can be used with an ST700 or ST800 Controller. See Figure 2 below for details. Lamp Supply Cable – see Section 5.6.3 TR0141 Cable – see Section 5.6.10 OMCU ST700 or ST800 Controller Figure 2 - Basic OMCU to ST700 or ST800 For connection to other Controllers, use the OMCU/LMU I/O Cables kit (667/1/28852/000). If additional I/O is required, also add the OMCU/LMU I/O Board and Cables kit (667/1/28853/000).
PAGE 16
3U Traffic Outstation Handbook 2.2.2 MOVA The MOVA Kit (667/1/28851/000) converts a standard OMCU into a MOVA unit. The MOVA firmware replaces the OMCU firmware. 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.3 OMCU (replace PROM with MOVA PROM) TR0141 Cable – see Section 5.6.
PAGE 17
3U Traffic Outstation Handbook 2.2.3 BUS Processing Bus Processing may be performed by adding the Bus PCB and Cable kit (667/1/28856/000) to the Basic OMCU. If OMCU functionality is also required, also add the cable kit(s) described in Figure 3. Digital I/O – see Section 5.6.5 RS485 to Reader – see Section 5.6.6 OMCU Any Controller As Figure 3 if OMCU functionality is required. Figure 6 – BUS Processing to Any Controller 2.
PAGE 18
3U Traffic Outstation Handbook (i) (j) (k) Voltage Regulation (allowing a range of DC input) Status LED indicators (also see section 7.3 which starts on page 83) Power dissipation less than 100 mW. 2.4 LMU I/O BOARD This is a 3U 220mm long, 100mm wide and 14mm high extended Eurocard. It is a multi-layer PCB, using mostly surface mount components. When required for OMCU monitoring, up to three LMU I/O boards may be fitted to meet the entire controller's monitoring requirements.
PAGE 19
3U Traffic Outstation Handbook This board provides four RS485 communications links enabling communications with RS485 based equipment such as SIETAG and optionally the GPS receiver. The 48 digital inputs and 16 digital outputs meet the TR0141 specification and thus provide MOVA and DUSC with its stage force bit outputs to, and confirm inputs from, any traffic controller configured with a UTC/MOVA/DUSC interface.
PAGE 20
3U Traffic Outstation Handbook 2.6.2 The GSM TC35 Modem Unit (option) This replaces the M20 GSM Modem which is lo longer available. This modem is a dual band GSSM900/1800 unit but limitations of the aerial restrict it’s use in this application to the GSM900 network (Vodaphone or Cellnet). To use the GSM OMCU the Instation must be equipped with the PACE PCM33.6 or the Dynalink PK5-5600 Modem. See section 8.4.3 for compatibility details.
PAGE 21
3U Traffic Outstation Handbook 2.7.1 The Power Supply Unit (PSU) Features (a) (b) (c) (d) (e) (f) Wide range of AC input voltage 3000V isolation from the mains Can be fitted with a single 12V sealed lead acid battery (see section 7.6.3(a) on page 88) Automatic switching to the battery support in the event of mains failure to the system Automatic recharge on restoration of mains supply to the system 3 years minimum battery life (also see section 7.4 on page 85) 2.
PAGE 22
3U 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 3.2.1 Mains Supply Normally the unit is powered from an auxiliary mains supply provided within the controller.
PAGE 23
3U Traffic Outstation Handbook 3.2.4 Support Batteries The unit can be fitted with two rechargeable batteries. The first is the optional Unit Support Battery, which supports the entire unit including the modem, for a minimum of four minutes under all conditions in order that the OMCU may inform the Instation of a mains power failure. Note that some units, e.g. MOVA only units, do not require and will not be shipped with a Unit Support Battery.
PAGE 24
3U Traffic Outstation Handbook 3.5 ISOLATED OUTPUTS The I/O boards are each equipped with a number of relay isolated outputs, four normally open contacts on an LMU I/O board and 16 change-over contacts on a BUS / MOVA I/O board. The following describes the electrical characteristics of these outputs: LMU I/O Board Output MOVA I/O Board Output On Output Impedance 182Ω ± 1%, 0.5 Watts * 182Ω ± 1%, 0.1 Watts † Off Output Impedance 100kΩ min. 100kΩ min.
PAGE 25
3U Traffic Outstation Handbook 3.7 ISOLATED MAINS VOLTAGE INPUTS Each LMU I/O board also supports 10 fully software configurable photo-coupled mains voltage inputs and a fully configured OMCU provides 30 such inputs. The function of these inputs is to provide an isolated means of detection of the presence or absence, of the mains’ signal at the phase drive output terminal blocks. The following describes the electrical characteristics of a single input.
PAGE 26
3U Traffic Outstation Handbook The four RS232 communications interfaces are shown on 667/GA/26580/000 sheet 2 in Appendix B and are as follows: 3.9.1 Communications Channel 1 (TR0141 Port) Location: On back edge of Processor Board (see 667/GA/26580/000 Sheet 2) in Appendix B Connector Type: 25 Way 'D' Type on the end of a flying ribbon cable connected to Plug PL4. 3.9.
PAGE 27
3U Traffic Outstation Handbook 3.9.
PAGE 28
3U Traffic Outstation Handbook 4. OMCU FACILITIES 4.1 INTRODUCTION The Siemens 3U 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 3U Traffic Outstation when used as a Siemens RMS OMCU, Bus Processor or Car Park Count OMCU. Section 4.2.9 describes the facilities available with the GSM OMCU option. Section 4.
PAGE 29
3U Traffic Outstation Handbook Any fault detected is logged and reported to the Instation identifying the type (i.e. signal lamp or detector, etc.) and location (i.e. Phase A-RED or stage 2 demand, etc.). Some reported faults are automatically 'cleared' by the OMCU itself; others can only be 'cleared' by manual means at the Instation. The following lists indicate which reports clear automatically.
PAGE 30
3U Traffic Outstation Handbook 4.2.4 Controller Timing Checks (These checks are not normally required on a 141 controller) Under this category the following is provided: (a) Short Stage Minimum (b) Short and Long Stage Extensions (c) Long Stage Maximum (d) Long Alternative Stage Maximum (e) Short Phase Inter-green (f) Long Inter-Stage (g) Long All-Red (h) Variable Maximum Timing Log (i) SDE/SA Extension Request Log 4.2.
PAGE 31
3U Traffic Outstation Handbook 4.2.5.1 Routing SIETAG Vehicle Detections to an OTU An overview of the SIETAG OMCU - OTU facility is shown in the following figure.
PAGE 32
3U Traffic Outstation Handbook The OTU must be appropriately configured to provide the throughput to the UTC using the following handset commands.
PAGE 33
3U Traffic Outstation Handbook etc. are also passed over the serial link allowing the OMCU and MOVA applications to read them as though they were connected directly to the unit. For more information on MOVA using the enhanced 141 link, see section 9.6.4 on page 117. The OMCU enhanced 141 link is configured on RMS screen 010, by selecting the Monitoring Type as “Serial” rather than “Full” when the controller type is “800P”.
PAGE 34
3U 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 35
3U Traffic Outstation Handbook handset or via user defined conditioning. The DUSC facility has the following features: (a) Up to 16 plans, with 32 groups per plan. Up to 32 streams. (b) Timeswitch table with up to 64 entries. (c) Plan compliance checking and fault reporting. (d) Fault report of simultaneous green confirms (G1, G2 active). (e) Real time update information includes current plan, current group, forces, confirms, on/off control and cycle time.
PAGE 36
3U Traffic Outstation Handbook 4.2.9.1 Force Bit Control Installation SIGNAL HEADS LOCAL HANDSET RS232 RMS PROTOCOL TO INSTATION GREEN CONFIRMS STAGE CONFIRMS PSTN or GSM OPTION: GPS Receiver (clock) TRAFFIC CONTROLLER OMCU (with LGD Battery & MODEM) RS232/ RS485 FORCE BITS DETECTOR LOOPS Figure 8 – Force Bit Control Set-up Figure 8 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 37
3U Traffic Outstation Handbook 4.2.9.2 ST800 Enhanced Serial Link Control Installation LOCAL HANDSET RS232 RMS PROTOCOL TO INSTATION PSTN or GSM OPTION: GPS Receiver (clock) SIGNAL HEADS OMCU (with LGD Battery & MODEM) RS485 FORCE BITS, CONFIRMS, ETC TRAFFIC CONTROLLER ST800 ENHANCED SERIAL LINK DETECTOR LOOPS Figure 9 – ST800 Enhanced Serial Link Control Set-up Figure 9 shows how an OMCU can be set up for the ST800 Enhanced Serial Link control.
PAGE 38
3U Traffic Outstation Handbook 4.2.9.3 Detector Control Installation SIGNAL HEADS LOCAL HANDSET TRAFFIC CONTROLLER PSTN or GSM OPTION: GPS Receiver (clock) GREEN CONFIRMS RS232 RMS PROTOCOL TO INSTATION OMCU (with LGD Battery & MODEM) RS232/ RS485 DEMAND BITS DETECTOR LOOPS Figure 10 – Detector Control Set-up Figure 10 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 39
3U 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 40
3U Traffic Outstation Handbook Configuration data for the OMCU Events facility includes:- Debounce Active Delay and Debounce Inactive Delay. 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 41
3U Traffic Outstation Handbook The user is able to freely specify up to 32 detection conditions via special conditioning e.g. vehicles of between 2m and 5.5m in length occurring at a given site travelling in excess of 80kph. Of these 32 detection conditions, up to 16 may be selected for statistic collection purposes.
PAGE 42
3U Traffic Outstation Handbook presence time. Both fault types are automatically cleared by the OMU. Both fault types may be manually reset by the RMS instation operator. The Vehicle Classification facility also supports a loop pair fault algorithm. This algorithm identifies a loop pair as faulty if one of the loops is activated on N consecutive occasions with no activations on the other loop. The fault is cleared by the OMU if there are M activations (not necessarily consecutive) of both loops.
PAGE 43
3U Traffic Outstation Handbook In addition a means of logging ALOTPV over a configurable period of time is supported. This logged data can then be retrieved from the outstation and used by the instation for traffic analysis and reporting. The instation provides the means of setting thresholds and logging criteria for ALOTPV and communicating them to the outstation via the normal configuration data file.
PAGE 44
3U Traffic Outstation Handbook 4.3 GSM OMCU The GSM OMCU is an extension to the Siemens RMS OMCU described in section 4.2 above. It provides an extremely cost effective means to monitor and control equipment where standard PSTN connection is not available or where the line installation costs are prohibitive. See Sections 2.1 and 2.6.2 for further details of the GSM option. 4.3.
PAGE 45
3U Traffic Outstation Handbook Bus Processor and OMCU functions can be performed simultaneously, limited only by the number of I/O boards that can be accommodated.
PAGE 46
3U Traffic Outstation Handbook 5. INSTALLATION WARNING THIS EQUIPMENT MAY ONLY BE INSTALLED 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 47
3U Traffic Outstation Handbook 5.1 INSTALLATION CHECK LIST The checklist on the following page should be used to install the unit together with the Instation computer printout for the equipment to be monitored. Installation techniques are shown on drawing 667/GA/26577/000 in Appendix B . For GSM OMCU installation, see also 667/CF/26598/010 in Appendix B For further guidance on each step refer to the appropriate section in the REFERENCE column.
PAGE 48
3U 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 9 10 11 OMCU C/P BUS MOVA OMCU C/P BUS MOVA OMCU C/P OMCU — — BUS — — — BUS MOVA OMCU — — — — — — OMCU C/P BUS MOVA 12 OMCU C/P BUS MOVA 13 OMCU — — — 14 OMCU — — — 15 OMCU C/P — — 16 OMCU C/P — — 17 18 — — — — BUS BUS — — 19 — — — MOVA 20 21 22 23 — — — MOVA OMCU C/P BUS OMCU C/P BUS O
PAGE 49
3U Traffic Outstation Handbook THE REST OF SECTION 5 TAKES YOU THROUGH THE STEPS IN THE INSTALLATION CHECKLIST (FROM THE PREVIOUS PAGE) IN MORE DETAIL… Section 5.2 takes you through the steps that ‘configure’ the hardware before the unit it is installed. Sections 5.3, 5.4 and 5.5 take you through the steps to install the unit. And finally, section 5.6 takes you through all the steps involved in connecting up all the various interfaces to the unit. 5.
PAGE 50
3U Traffic Outstation Handbook LMU I/O Board Bus MOVA I/O Board Edge of the board 4 3 2 1 ON ON ON 1 2 1 2 5 Edge of the board 6 S1 LMU I/O Board 4 3 2 Bus / MOVA I/O Board 1 ON ON OR ON 4 3 2 1 1 2 ON 1 ON OR ON 4 PSU CPU Card 3 2 1 2 ON 1 1 S1 1 2 ON S5 1 I/O Board #2 2 OR ON I/O Board #3 2 I/O Board #1 2 S6 Figure 11 – I/O Board Switch position 4 of S1 on the LMU I/O board is used for switching the lamp monitor between 50Hz and 60Hz operation (OFF = 50Hz
PAGE 51
3U Traffic Outstation Handbook PL1 Connector Viewed from the BACK 33 1 34 2 0v - 8v Relay 33 31 29 27 5v - 12v 34 32 30 28 Black Wire: Common Return from the Modem Yellow Wire: Supply To The Modem Orange Wire: Link To Required Voltage For The Modem, e.g. 5v For Example: To select 5V as the modem power supply: 1) Insert the black wire in to socket 34 for 0V. 2) Insert the orange link wire in to sockets 28 and 33 to select 5V. 3) Finally insert the yellow wire in to socket 27 (Modem +ve supply).
PAGE 52
3U Traffic Outstation Handbook WARNING ZX0 WIRES FROM THE UNIT TO THE FIRST LMU I/O BOARD (NEAREST CPU) The red and black wires that come from under the power supply cover through the ferrite are at mains potential when the unit is switched on. The mains supply must be completely removed from the unit prior to: • Disconnecting these wires for any reason, e.g. replacing the unit. • Any ZX0 circuit setting adjustments as defined in this section. • Any operation that would leave these wires exposed.
PAGE 53
3U Traffic Outstation Handbook Note 2: Pins 11, 13 and 14 should be connected as shown on the first LMU I/O board only. These pins should be left unconnected on the second and third boards fitted to a unit. If 120V operation is required then a different variant of the Voltage Monitor Transformer must be used. The 100V Welsh Office version is 667/7/25172/500, see section 5.2.7. A design for a 120V version would need to be requested. 5.2.
PAGE 54
3U Traffic Outstation Handbook 5.2.6 Output Resistor Options (BUS / MOVA I/O Board Only) 9 — — BUS MOVA 5.2.6 Set up Bus/MOVA output relay resistors The BUS / MOVA I/O board has two switches to select the resistor values on the last two outputs: The first switch selects the resistor values for output 15 while the second switch selects the resistor value for output 16. The ‘ON’ position selects 22Ω, while ‘OFF’ selects the normal 180Ω.
PAGE 55
3U Traffic Outstation Handbook 5.4 HARDWARE INSTALLATION 5.4.1 General Installation The unit assembly is a 3U extended unit, requiring 192mm of 3U Rack space. This feature, together with the configurable cableforms, provides sufficient flexibility to install the hardware in most controllers, in one of the three positions described below. Also see Appendix B for details of part numbers. (a) The unit may occupy unused space, in a suitable rack with sufficient space, which exists in a controller's cabinet.
PAGE 56
3U Traffic Outstation Handbook 5.4.2 Radio Clock Installation [This section only applies to Bus applications] The optional Radio Clock is a separate unit that is mounted external to the OMCU using a bracket supplied with the unit. It provides a time signal to the traffic outstation received from the MSF Rugby transmitter. This is used to synchronise the internal real time clock.
PAGE 57
3U Traffic Outstation Handbook 5.5 CABLE AND WIRING [This section applies to all applications] 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. Cables should not obstruct the maintenance work on the controller, the unit being installed, or any other equipment fitted within the cabinet. 5.
PAGE 58
3U Traffic Outstation Handbook (g) (h) (i) Each switched sign phase If regulatory signs are to be monitored then they need to be grouped together Each "flashing amber signal group" phase requires one or two current sensors, depending on monitoring requirements (this phase type is applicable to export signal sequences only) Each current sensor can monitor currents up to 4.25A RMS. If the nominal load current (not including the red/ambers) of a particular controller output exceeds approximately 4.
PAGE 59
3U Traffic Outstation Handbook Figure 13 - Current Sensor Connection Voltage First Current Input on I/O Board 1 Monitoring (Second Current Input on Boards 2 & 3) Transformer Input on I/O Berg Mini-Latch Board 1 Housing Polarisation Pip Orange Wire 1 33 34 2 End Connector Socket Positions Not Used at both ends White Wire To Lamp Supply Red Wire Must be Connected to Top of Connector Voltage Monitor Transformer Current Sensor R To A Lamps G From Controller Output Red Spot Marking on Current Sensor mus
PAGE 60
3U Traffic Outstation Handbook The sensors are terminated with Berg Mini PV terminals and are clipped into a Berg mini latch housing, to provide a complete sensor assembly... 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 61
3U Traffic Outstation Handbook 5.6.2 Lamp Supply Sensor Connection 14 OMCU — — — Connect lamp supply sensor (Unless using ST800 enhanced serial link) 5.6.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 62
3U Traffic Outstation Handbook Note: This connector is also used by the OMCU to monitor the state of other mains level signals, such as the controller’s mains supply (after its switches and fuses) for example, which is normally connected to the first mains state input on the first LMU I/O board.
PAGE 63
3U Traffic Outstation Handbook 5.6.4 Digital Monitor Connections (LMU I/O Board Only) 16 OMCU C/P — — Connect digital monitors cables (Unless using ST800 enhanced serial link) 5.6.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 64
3U Traffic Outstation Handbook process at the Instation, to ensure that detectors on a terminal block should not be split over different ports. Each cableform can cater for up to 8 inputs, and have the same colour coding, as defined below. The input ports are allocated to LMU I/O Boards in the following order. If Bus / MOVA I/O boards are also fitted, then the OMCU application can also read the inputs on those boards, see section 5.6.5 overleaf.
PAGE 65
3U Traffic Outstation Handbook Any of these ports, up to a total of four, may be used for N+1 flow counting.
PAGE 66
3U Traffic Outstation Handbook I/O Board Connector PL1 and PL2 Connector Allocation 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 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Board 1 PL1 Buffered I/P 1 Buffered I/P 2 Buffered I/P 3 Buffered I/P 4 Buffered I/P 5 Buffered I/P 6 Buffered I/P 7 Buffered I/P 8 Buffered I/P 9 Buffered I/P 10 Buffered I/P 11 Buffered I/P 12 Buffered I/P 13 Buffered I/P 14 Buffered I/P 15 Buffered I/P 16 Buffered I/P 17 Buffere
PAGE 67
3U Traffic Outstation Handbook The OMCU application (in PB680 and PB681 issue 10 and later) can also read the digital inputs on any Bus / MOVA I/O boards that are fitted. The following diagram and table summarise where the OMCU’s 64 detector inputs are located when various combinations of I/O boards are fitted.
PAGE 68
OMCU Detectors On Bus / MOVA I/O Boards (PB680 AND PB681 ISSUE 10 AND LATER) 667/HB/26568/000 Page 68 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
PAGE 69
3U Traffic Outstation Handbook 5.6.6 BUS / MOVA Board RS485 Serial Ports 18 — — BUS — 5.6.6 Connect RS485 cables, e.g. for SIETAG The following Table shows the RS485 connector pin assignments on each BUS/MOVA I/O board.
PAGE 70
3U Traffic Outstation Handbook NB: 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 Ω as described in section 5.2.5. The serial port to which each reader is connected must correspond with the data configured for the OMCU on RMS screen 500.
PAGE 71
3U Traffic Outstation Handbook (c) Check On Integrity of Neutral Connections 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. The voltage should be less than 5V RMS to meet IEE Regulations BS7671, if it is not then the neutral connection between the controller and the signal head(s) being tested may be faulty.
PAGE 72
3U Traffic Outstation Handbook Insert this cable into plug PL4 (SIL 18 way) on the processor board (see drawing 667/GA/26580/000 in Appendix B ), and the other end (25 way 'D' Type), into the appropriate 'Handset Socket' of the OTU. Note: This cable is required if the unit is to use the 141 serial link for routing SIETAG vehicle detections to an OTU. 5.6.
PAGE 73
3U Traffic Outstation Handbook When installing the Siemens OMU the detector monitoring inputs require access to the same 24VDC supply as is used to reference the detector inputs. At present this is not directly available. To make the 24VDC supply available to the Siemens OMU the supply should be taken from the back of the TRX backplane. Soldering a wire to the connector pin “+24VDC” on the TRX backplane should make the connection.
PAGE 74
3U Traffic Outstation Handbook 6. OMCU 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. ZX0 WIRES FROM THE PSU TO THE FIRST LMU I/O BOARD (NEAREST CPU). The red and black wires, which come from under the power supply cover through the ferrite, are at mains potential when the unit is switched on.
PAGE 75
3U Traffic Outstation Handbook 6.1 INTRODUCTION The checklist on the following pages should be used to commission the OMCU and Bus Processor 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]’ and the ‘Bus [Processor]’ columns to determine whether the step applies to the type of unit being commissioned.
PAGE 76
3U Traffic Outstation Handbook OMCU Car BUS Park CHECK REFERENCE Controller Checks 3 4 5 6 The controller to be monitored should be checked to verify that: a) All lamps are working, including WAIT lamps; b) All the detection is working; c) All push buttons are working; d) The controller is fully serviceable and servicing all demands and extensions; e) The controller timing is correct; f) That the RUN LED (LP3) is indicating the OMCU is powered and running.
PAGE 77
3U Traffic Outstation Handbook OMCU 9 10 11 12 9 Car BUS Park 9 9 CHECK If the OMCU digital I/O Ports are connected, check that they respond to detector and controller mode changes, etc, using the DIP handset command. REFERENCE Instation config sheet & 11.4 9 Check the OMCU mains state inputs respond to Instation the monitored controller signals (phase greens, config sheets wait indicators, controller supply etc) using the and MSI handset command. 11.
PAGE 78
3U Traffic Outstation Handbook OMCU Car BUS Park CHECK 9 If the OMCU is connected to a TR 0141 controller handset port, check that the controller can be interrogated through the OMCU using the XXC and XXO handset commands. Since the OMCU is not configured at this stage the SCT code may be used to initialise the OMCU UART to the appropriate configuration.
PAGE 79
3U Traffic Outstation Handbook OMCU Car BUS Park CHECK REFERENCE Dial Out & Dial In Checks 20 21 9 9 9 9 Connect OMCU Telephone Connector and a Telephone Handset (e.g. BT ref. 248/2) into a Dual Outlet Adapter (BT ref. LJU10/3A). Connect the Dual Output Adapter into the line Jack Unit. Use the Telephone handset to dial the Instation Operators and inform them the OMCU is ready for Configuration Data Download. (Preferably within an agreed time, e.g. 5 minutes.
PAGE 80
3U Traffic Outstation Handbook OMCU Car BUS Park CHECK REFERENCE Support Battery Check (If Fitted) 26 9 9 9 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 81
3U Traffic Outstation Handbook OMCU Car BUS Park CHECK REFERENCE PAKNET check (if Fitted) With car park count systems the PAKNET interface is used to transmit data to the Instation. The following parameters must be set-up via the handset. a) Enable the PAKNET interface via handset command RCT. b) Set the Instation PAKNET address via handset command RCA. c) Set the address of the OMCU via handset command ADR.
PAGE 82
3U 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 83
3U Traffic Outstation Handbook 7.1 INTRODUCTION With authorisation from Siemens Traffic Controls, the user or a third party may carry out first line maintenance work on the unit. To obtain authorisation the user or third party must undergo a basic training course, provided by Siemens Traffic Controls. 7.2 FIRST LINE The authorised agent is restricted to first line maintenance work only. Maintenance work beyond first line should be referred to Siemens Traffic Controls.
PAGE 84
3U Traffic Outstation Handbook The four LED indicators on the processor board give the following status or fault indication: LP1 RED Processor Error LED RED Watchdog LED GREEN Software Run LED GREEN Communications LED LP4 7.3.1 Processor Error LED This red LED has two states: (a) OFF indicates no processor error. (b) ON STEADY indicates there is an error with the processor. 7.3.2 Watchdog Failure LED This red LED has two states: (a) OFF indicates no watchdog failure.
PAGE 85
3U Traffic Outstation Handbook 7.3.4 Software Run LED LED State OMCU (PB680 issue 1 to 4) OMCU (PB680 issue 5 or later) MOVA† (PB681) On Steady Monitoring — — Slow Flash* — Monitoring On Control Fast Flash* Fault Fault Off Control Off No Power No Power No Power * The slow flash rate is approximately one second on / one second off, whereas the fast flash rate is much faster (several flashes per second).
PAGE 86
3U Traffic Outstation Handbook 7.4.1 Annual Maintenance For a unit fitted with battery support, switch the mains power off and check the unit is supported by the battery for a minimum of 10 minutes. Do this by inspecting the RUN LED and waiting until the power failure has been reported to the Instation. This tests the condition of the Unit Support battery, and if the unit loses support within 10 minutes, the battery must be replaced.
PAGE 87
3U Traffic Outstation Handbook 7.5 PART NUMBERS Plug 3 pin Rectangular 3A................................................................. 508/4/29174/004 OMCU 95 Power PC Firmware ......................................................... 667/1/12680/000 Detector 11” Rack Kit ........................................................................ 667/1/20690/000 Detector 19” Rack Kit ........................................................................ 667/1/20690/001 Traffic O/S Mounting Kit .........
PAGE 88
3U Traffic Outstation Handbook 7.6 SPARES The following spares should be held by the authorised maintenance agent. Some of the parts listed in Section 7.5 above are also available as spares. Contact Siemens Poole for details. 7.6.1 General LMU I/O PCB Assembly .................................................................... 667/1/26570/000 BUS / MOVA I/O PCB Assembly....................................................... 667/1/27881/000 PSU I/P 85-264V AC O/P 15V 3A ...................................
PAGE 89
3U Traffic Outstation Handbook 8. FAULT FINDING AND REPAIR 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 Communication Failures Table 8.4.2 : GSM Communication Failures Table 8.4.3 : MODEM COMPATIBILITY Table 8.5 : EQUIPMENT FAILURES Table 8.
PAGE 90
3U 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 Diagnosis Action (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 91
3U Traffic Outstation Handbook Symptom Diagnosis (b) Unit will not dial Instation Instation Number incorrect. Action Check the configured Instation telephone number is correct using CTN and TNP (section 11.7 on page 174). 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 11.7 on page 174). If not replace modem.
PAGE 92
3U Traffic Outstation Handbook Symptom Diagnosis Action (d) Unit to Instation link communications not completed or intermittent PSTN line intermittent (OMCU only) Check using handset codes CDC, CTR and MDC, what types of faults and the rate of their occurrences (see section 11.7). If this information indicates an intermittent PSTN line, request a line check by the appropriate authority.
PAGE 93
3U Traffic Outstation Handbook 8.4.2 TABLE FOR GSM COMMUNICATIONS FAILURES Note that use of the term ‘modem’ applies equally to GSM modules. Symptom Diagnosis (a) Unit will not answer Instation calls Action GSM Network Check with the Service provider (e.g. BTCellnet or Vodaphone), that the unavailable or blocked. particular SIM Card / phone number are enabled for DATA and are not in any way blocked. The service provider will be able to check the phone number and SIM card through their network.
PAGE 94
3U Traffic Outstation Handbook Symptom Diagnosis (a) Unit will not answer Instation calls (continued) GSM Modem failed Action 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 OMCU PSU plate and so its reflection may be easier to see. The LED has 3 states Constant On – Powered correctly and service available.
PAGE 95
3U Traffic Outstation Handbook Symptom Diagnosis Action (b) Unit will not dial Instation Modem incompatible with Instation modem Check that the unit and Instation are using compatibly configured modems. Refer to section 8.4.3. Instation number incorrect Check the configured Instation telephone number is correct using CTN and TNP (section 11.7 on page 174). If correct replace modem, if not reload the unit’s configuration.
PAGE 96
3U Traffic Outstation Handbook Symptom (d) Unit to Instation link communications not completed or intermittent (continued) Diagnosis Action Modem intermittent (OMCU only) Check using handset codes CDC, CTR and MDC, what types of faults and the rate of their occurrences (see section 11.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 97
3U Traffic Outstation Handbook 8.5 TABLE FOR EQUIPMENT FAILURES Symptom (a) Unit not operating Diagnosis Software watchdog has Check the state of the Watchdog LED (see section 7.3 which starts on page triggered 83), 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. Processor board failed Check using the Handset code FLT for fault LOF.
PAGE 98
3U Traffic Outstation Handbook Symptom Diagnosis Action (a) Unit not operating (continued) Software not running If the RUN 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 99
3U Traffic Outstation Handbook Symptom Diagnosis I/O board faults (continued) Current sensor inputs failed (OMCU only) Action Monitor the relevant input(s) using the Handset code KAC (see section 11.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 100
3U Traffic Outstation Handbook 8.6 TABLE FOR POWER FAILURES Symptom Diagnosis Action (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 101
3U Traffic Outstation Handbook 9. MOVA 9.1 MOVA Introduction IMPORTANT: BEFORE LOADING ANY CONFIGURATION DATA, REFER TO SECTION 9.6.7 ON PAGE 120. 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 102
3U Traffic Outstation Handbook The Original Siemens MOVA unit Prior to issue 10, the OMCU application was not available in the PB681 MOVA firmware PROM. Therefore, if the traffic controller was required to be monitored by a Siemens OMCU, a separate OMCU unit needed to be installed. RMS OMCU MOVA Front MOVA RMS OMCU These two 3U units were normally supplied ‘ready built’ in a single 19” 3U rack as shown right, and could share the same telephone line, see section 9.4 on page 108.
PAGE 103
3U Traffic Outstation Handbook 9.2 MOVA Interfaces Since the MOVA unit uses the same hardware platform as the OMCU, the interfaces are similar to those of the OMCU and thus most are covered by section 5.6 which starts on page 57. There are two main exceptions: (i) Access to the MOVA application through the handset port. Access to the MOVA application is via a PC running suitable software connected to the 25 way D-Type port on the front of the processor board, see section 9.6.1 on page 114.
PAGE 104
3U Traffic Outstation Handbook Also note that PB681 issue 10 can use the enhanced 141 serial link to an ST800 through which it obtains all of its detectors and confirms from, and passes its force bits to, the controller. See section 4.2.6 on page 32 and section 9.6.4 on page 117. 9.2.1 Detector Inputs and Push-Buttons The detector inputs (1-32) are normally connected in parallel to the controller at the controller’s terminal blocks.
PAGE 105
3U Traffic Outstation Handbook 9.2.4 Other I/O Signals The ‘SP - Sync Pulse’ output is only used during development and should be left unconnected. The ‘MF- MOVA Fault’ and ‘DM - Disable Modem’ signals are used by the telephone line sharing option described on page 108. If this facility is not required, then prior to PB681 issue 10 firmware, the ‘DM’ input must be connected to 0V and the ‘MF’ output left unconnected.
PAGE 106
3U Traffic Outstation Handbook MOVA Digital I/O Connections 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 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Wire Colour Blue Yellow Brown Violet Orange Slate Pink Red / Blue Red / Green Red / White Red / Brown Red / Orange Red / Slate Blue / Green Blue / White Blue / Brown Blue / Orange Blue / Slate Green / Orange Green / Brown Green / Slate Brown / Slate Orange / Brown Orange / Slate White White Blue Yellow Br
PAGE 107
3U Traffic Outstation Handbook 9.3 Connection To A Siemens T400 or ST800 To simplify connecting the MOVA unit to a Siemens Type 400 or Type 800 traffic controller, an alternative cableform is available. Note that no I/O cables will be required if MOVA is to use the enhanced serial link to an ST800, see section 9.6.4 on page 117. This cableform connects the first BUS / MOVA 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.
PAGE 108
3U Traffic Outstation Handbook 9.4 Telephone Line Sharing Connections When a separate Siemens OMCU unit and Siemens MOVA unit share the same telephone line, the two units ‘communicate’ with each other using two I/O lines. For details of how to communicate remotely to telephone line sharing units, see section 9.7.2 on page 129. The ‘MOVA Fault’ (MF) I/O line is an output from the MOVA unit to any detector input on the OMCU.
PAGE 109
3U Traffic Outstation Handbook If problems are experienced with the telephone line sharing system, the following should help diagnose the cause of the problem: • Check that the OMCU has been installed, commissioned and configured correctly. The telephone line sharing system between the MOVA unit and the OMCU will not function if the OMCU does not contain the necessary special conditioning. • Check that wires between the MOVA unit and the OMCU are as shown on the previous page.
PAGE 110
3U 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 113. Note that where a separate OMCU unit and MOVA unit are both being installed together into a controller and the two units are to share the same telephone line, then the OMCU should be commissioned and configured first, before the MOVA unit is commissioned, see section 6.
PAGE 111
3U Traffic Outstation Handbook Step Section 10) 9.6.4 Action to be Performed If MOVA is to use a Bus / MOVA I/O Board, check that the SOP handset command shows the correct type of I/O boards have been detected and that MOVA is using one of them, see page 182. If MOVA is to use the enhanced serial link to an ST800 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.
PAGE 112
3U 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 113
3U Traffic Outstation Handbook 9.6 MOVA Commissioning Detail This section expands on the steps in the commissioning checklist from the previous section… Note that where a separate OMCU unit and MOVA unit are both being installed together into a controller and the two units are to share the same telephone line, then the OMCU should be commissioned and configured first, before the MOVA unit is commissioned, see section 6.
PAGE 114
3U 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.9.6. Start the PC in the usual way.
PAGE 115
3U 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. [Prior to issue 10 – set the ‘Phone Home’ flag to 77] Prior to Issue 10: To re-initialise the MOVA unit, enter 'LF' to 'Look at Flags' from the MOVA main menu and then 'S' to 'Set flags'. Then enter 'L' to select the phone home flag.
PAGE 116
3U Traffic Outstation Handbook 9.6.3 Phone Line Sharing Facility (PLS) 9) 9.6.3 Ensure the unit has correctly determined whether the Phone Line Sharing facility to a separate OMCU is required (‘PLS:1’ if enabled and ‘PLS:0’ if disabled). If not, investigate the reason and correct. Prior to PB681 issue 10, the ‘phone line sharing’ facility was always enabled and the PLS handset command was not available. If the facility is not required, the ‘DM’ input had to be connected to 0V as described in section 9.
PAGE 117
3U Traffic Outstation Handbook 9.6.4 Serial Link Between MOVA and an ST800 (MIO) 10) 9.6.4 If MOVA is to use a Bus / MOVA I/O Board, check that the SOP handset command shows the correct type of I/O boards have been detected and that MOVA is using one of them, see page 182. If MOVA is to use the enhanced serial link to an ST800 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 118
3U Traffic Outstation Handbook 9.6.5 MOVA Licence Number (LIC) 11) 9.6.5 Enter the correct MOVA licence number, e.g. ‘LIC=1234 5678’. From PB681 issue 10 onwards, a valid licence number is required before MOVA can be put on control. The licence number is unique to each individual site and is made up of two four-digit numbers separated by a space. To obtain a licence number for a new site, contact the Siemens RMS Helpdesk at Poole.
PAGE 119
3U 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.
PAGE 120
3U 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 (only available from PB681 issue 10 onwards). 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 121
3U Traffic Outstation Handbook that all three plans in its memory have the same number of stages, links and lanes, etc. When the download of a plan is complete, the MOVA unit will display the following: 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.
PAGE 122
3U 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 123
3U Traffic Outstation Handbook 15 from the controller, and the force bits that the MOVA unit is currently outputting. The ‘MOVA enabled’ and ‘On Control’ flags and the ‘Warm-up’ and ‘Error’ counts are described in more detail in section 9.6.10. For inputs on the Bus MOVA IO card, 0 = input open circuit, 1 = input short circuit. For semi-integral MOVA, the input sense can be inverted or not, dependant on the controller configuration.
PAGE 124
3U Traffic Outstation Handbook While the MOVA Main Menu is being displayed, enter the two-letter menu option required and press ‘Return’. When the required option completes, the commissioning screen will automatically re-appear. 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.
PAGE 125
3U Traffic Outstation Handbook It is recommended that the error log be cleared after each site visit if all entries can be explained and the unit is functioning normally. Then the engineer making the next visit to site will only see faults that have occurred since the last visit.
PAGE 126
3U 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 127
3U 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 128
3U 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 114. 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 129
3U Traffic Outstation Handbook ATZ .........................................to reset the modem Ok ...........................................accepted by the modem AT+MS=2,0 ............................to select V22bis protocol Ok ...........................................accepted by the modem ATD 9 01202 123456 .........ask the modem to dial the given number CONNECT .................................response from modem indicating connection made Please wait ........................
PAGE 130
3U Traffic Outstation Handbook calls. This does not limit MOVA calls to five minutes since any call that is in progress between the Instation and the MOVA unit will not be terminated. In the unlikely event that the OMCU detects an urgent fault while a call is in progress between the Instation and the MOVA unit, then the OMCU will interrupt the MOVA unit’s telephone call to report the fault to the RMS Instation.
PAGE 131
3U Traffic Outstation Handbook When a successful call to MOVA is finished, the MOVA unit will switch off the power to its modem and return complete control of the telephone line to the OMCU again. Subsequent calls are therefore answered by the OMCU even if the call was completed within the five-minute time-out period described above. 9.7.
PAGE 132
3U Traffic Outstation Handbook 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 . . . . . . . . . . Flag(20) ON CONTROL FLAG {1=ON CONTROL} Flag(21) MOVA MESSAGE LOG {note 1} . . Flag(23) HOURLY FLOW LOG {note 2} . . Flag(26) ASSESSMENT LOG {note 2} . . Flag(27) ERROR LOG {note 1} . . Flag(28) VA {=0} / MOVA {=1} FLAG . . .
~~PAGE 133~~
3U Traffic Outstation Handbook Prior to issue 10 firmware, the MOVA application itself would attempt to phone a modem connected to a printer for example. When the call has been made, the flag is returned to its original value, normally zero. From issue 10 onwards, the OMCU application within the unit will report ‘MPH MOVA Phone Home’ to the RMS Instation (see section 11.6.2 which starts on page 162); the MOVA application does not actually phone home itself.
~~PAGE 134~~
3U Traffic Outstation Handbook confirm that you do wish to stop the messages. The main menu will re-appear after ‘Return’ is pressed. The messages themselves are by no means self-explanatory because it is essential to minimise the amount of text within each message. Once the messages start appearing, press the ‘F3’ key and the MOVA Communications application will show a full screen display of the information it receives in the messages in a much more understandable form.
~~PAGE 135~~
3U Traffic Outstation Handbook 10. CAR PARK COUNT and PAKNET 10.1 Overview The car park monitor facility is primarily designed for use with the PAKNET communication interface and a SIESpace Instation. The current occupancy of a car park is returned to the SIESpace Instation periodically. This information can then be used by the Instation to guide vehicles to car parks that have spaces.
~~PAGE 136~~
3U Traffic Outstation Handbook • To modify specific Car Park facility configuration data when requested by a Central Office • To provide handset commands to modify the Car Park facility configuration data 10.2 OMCU Status Message to SIESpace The OMCU generates the same status report format regardless of the reason for generating the status report.
~~PAGE 137~~
3U Traffic Outstation Handbook - Initially, every 10 seconds for 10 attempts Then, every hour for 5 attempts Then, every 24 hours until comms is re-established Prior to PB680 issue 13 firmware, comms is only retried every 10 seconds for 10 attempts. 10.3 Difference Count and Thresholds Algorithm The following describes the algorithm for the OMCU when used in the Car Park system.
~~PAGE 138~~
3U Traffic Outstation Handbook Extrapolation A straight line extrapolation is made N minutes into the future to assess whether the car park is filling or emptying at a fast enough rate to require more frequent status reports to the Central Office. The extrapolation is based on two occupancy values (a) the current occupancy and (b) the occupancy from M minutes earlier. M is the fill rate calculation period (handset command FCP).
~~PAGE 139~~
3U Traffic Outstation Handbook down period. The first status report is sent as soon as the decision is taken to enter ramp down mode. If the emptying rate changes so that the ALMOST FULL state would not be reached within N minutes then status reports are no longer sent to the Central Office at X minute intervals. If the occupancy reaches the almost FULL state, status reports are no longer sent at X minute intervals. The Historical Occupancy is calculated and stored at 1-minute intervals. 10.
~~PAGE 140~~
3U Traffic Outstation Handbook 10.4.2 Detector Fault Monitoring Each of the car park entry and exit loops can be configured to have detector fault monitoring, by default this facility is disabled. Each loop can provide a separate detector ‘Active’ and ‘Inactive’ time, the timing range is 0 to 255 minutes and hours respectively. Handset command CPL is used to set-up these times. If the detector remains in either the ‘active’ or ‘inactive’ state for longer than the configured time then a failure is recorded.
~~PAGE 141~~
3U Traffic Outstation Handbook The radio pad requires a 12V DC supply of power. This is supplied from the OMCU (PL1 connector pin 29). This power is passed through a relay mounted on a Din rail within the cabinet. This relay is controlled via an output from the OMCU (PL1 connector pins 27 and 28). The OMCU can then switch this output to turn the radio pad power Off/On.
~~PAGE 142~~
3U Traffic Outstation Handbook 11. HANDSET FACILITIES 11.1 INTRODUCTION Access to the 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 baud, even parity, 1 stop bit. Firmware PB680 issue 5 and later will auto-baud to 1200, 9600 or 19200 baud, on first receiving characters after the handset is plugged in.
~~PAGE 143~~
3U Traffic Outstation Handbook HSET MAJOR CMD INDEX CCL CCP CCT CCU 0-1 CDC 0-1 CDI CEC CFD CGR - MINOR INDEX 0-9 0-7 0-9 0 - 31 0-7 DATA 0 - 255 1 0 - 255 0 - 255 0 - 255 0 - 255 0-1 0 - 10 0 - 31 CGT - 0-7 0 - 255 CID CKA CKM CKR CKS COD CON COS COU CPC CPL CPO CPP CPT CPS CRQ CSI CSO CST CTN CTR CUS CYC DBM DFA DIP DIP DOR EBR EDI EEL ENR ERR EVA EVI 0-9 0-9 0-2 0-1 0-2 0 - FFFF - 0-2 0-3 0 - 15 0-3 0-2 0 0-1 0 - 11 0-2 0 - 15 0 - 15 0-7 0-5 0 – 15 0 – 15 TEXT DATE TEXT DATE TEXT, 0 0-2 0 - 655
~~PAGE 144~~
3U Traffic Outstation Handbook HSET MAJOR CMD INDEX EVS EXR FCP FDC 0-1 FFC aaa FFT FLG FLT FOC FOD FOF FOH FOL FOP FOS FOU FTR FUT IFA 0 - 15 IFN 0 - 15 INI IOP JID KAC 1 - 23 KAS 1 - 23 KDB 0-1 KLS KLM LAN LDV LIC LIP LMO LMR 0-1 LTS MAP MCI MDC 0-1 MDE MIO MON MOS MSI MTS OCC OCD - MINOR INDEX 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 - 31 0 - 31 0-7 0-1 0-6 0-7 0-9 0-1 0 - 12 aaa 0-2 0 - 31 0 - 15 0 – 15 667/HB/26568/000 DATA BINARY BINARY 0 - 63 0 - FFFF 0 -
~~PAGE 145~~
3U Traffic Outstation Handbook HSET MAJOR CMD INDEX OCF OCH OCL OCP OCS OCU OFF 0 - 15 OLG OPM OPS 0-2 PDL PDR PDU PGS PIA PIC PLE PLI PLS PLT 0 - 15 PLX PME POC 0 - 11 POS PUD RAM RAP RCA RCB RCD RCI RCR RCS RCT RCU RDF REN RET RGL - MINOR INDEX DATA DESCRIPTION 0 – 15 0 – 100 OCCUPANCY SMOOTHING FACTOR 0–1 BINARY OCCUPANCY HIGH 0–1 BINARY OCCUPANCY LOW 0 – 15 0 – 100 OCCUPANCY COUNT PERIOD 0 – 15 0 – 100 SMOOTHED OCCUPANCY RESULT 0 – 15 0 - 100 OCCUPANCY UP THRESHOLD 0-1 0 - 255 CLF OFFSET FROM THE BASE
~~PAGE 146~~
3U Traffic Outstation Handbook HSET MAJOR CMD INDEX MINOR INDEX RPL - - RSA RSC RTO RTG RTR - 0 - 31 0 – 15 0-2 DATA 0 – 15, 255 0 - 31 0 - 255 0 - 255 0–(232-1) 0 - 255 RTS - - 0-7 SCT SDC SDF SEB SEC SES SMS SOB SOP SRC STP SWS TAF TAI TDY TIM TIM TIM TIM TIM TIM TMP TNP TOD 0-9 0-2 CLR EXL EXS IGN MAX MIN - TSD - TSH TSW 0 - 31 0 - 63 VCC - VCF - VDE - VLC 0 – 31 VMC 0 - 15 VOA 0 – 31 ACCESS SECT REF REQUESTED CLF PLAN MAINT 11.
~~PAGE 147~~
3U Traffic Outstation Handbook HSET MAJOR CMD INDEX MINOR INDEX 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 VEHICLE CLASSIFIER TEST MESSAGE 0 – 65535 COUNT 0 – 255 VEHICLE CLASSIFIER TEST MESSAGE 0 – 255 VEHICLE CLASSIFIER SPEED BANDS VEHICLE CLASSIFIER DETECT 0 – 15 CONDITION STATISTIC CATEGORY MAP VEHICLE CLASSIFIER SITE 0 – 255 PARAMETERS VEHICLE CLASSIFIER TRAFFIC DATA 0 – 60 PARAMETERS VEHICLE CL
~~PAGE 148~~
3U Traffic Outstation Handbook The ‘+’ (or ‘.+’) and ‘-‘ (or ‘.-‘) keys may be used after a basic read command has been entered to enable the MINOR index (or MAJOR index) to be modified to scan the OMCU. 11.1.2 Display Format The two basic display formats are: • Echo display that is simply an echo of the information typed. • Response display generated by the OMCU when the command is terminated by operating the ENTER (or ‘RETURN’) key or the ‘+’ (or ‘.+’) keys.
~~PAGE 149~~
3U Traffic Outstation Handbook 3. Terminate the command by operating the ENTER (or ‘RETURN’) key. The OMCU responds by repeating the display with a colon and the required data. (e.g. Bright state in this example), i.e. KDB : 1 4. Repeat Steps 2 and 3 for each operation using the ‘+’ (or ‘.+’) or ‘-‘ (or ‘.-’) keys where possible to reduce key entry.
~~PAGE 150~~
3U Traffic Outstation Handbook 11.1.4 Write Procedure (Change Existing Data) 1. Plug the handset into the socket on front of the OMCU. 2. When the OMCU displays the prompt character ‘-’, carry out the appropriate level access enabling operation (described in information supplied separately to each OMCU user). Type out the required command code, any index or indexes necessary, followed by ‘=’ and the required value, e.g.
~~PAGE 151~~
3U Traffic Outstation Handbook The following would be entered: (the OMCU will respond with '__' (prompt) at this position if the command pointer was peviously empty) V DIP 0 .0 [ __ ] [ ______ ] Command Pointer Command to look at state of Digital Inputs (i.e first port on board 0) .1 ] [ PGS O ] [ __ ______ followed by ENTER or RETURN Command Pointer Command to look at state of Phase Greens followed by ENTER or RETURN .
~~PAGE 152~~
3U Traffic Outstation Handbook 11.2 HANDSET COMMAND ERROR CODES Code Name A Access Level Access level for this command has not been enabled. Use PME. C Non-configured THE FACILITY TO WHICH THE COMMAND RELATES IS NOT AVAILABLE D Data Integrity The data cannot be set to the specified value. Data associated with other handset command must be modified before this command can be set to the specified value. F Fixed Base The ‘+’ or ‘-‘ keys are not applicable to current command.
~~PAGE 153~~
~~3U Traffic Outstation Handbook 11.~~
~~PAGE 154~~
3U Traffic Outstation Handbook CODE MAJOR MINOR DATA INDEX INDEX RANGE DESCRIPTION AND REMARKS ACCESS LEVEL MON - MIN - Minimum Green monitoring DATA: (ON/OFF) RO MON - SDE - SDE/SA monitoring DATA: (ON/OFF) RO MON - SEQ - Stage Sequence monitoring DATA: (ON/OFF) RO MON - STK - Controller Stuck monitoring DATA: (ON/OFF) RO MON - VMX - Vari-Max monitoring DATA: (ON/OFF) RO PDL - 0–1 - Display Phase Demands – Latched MINOR INDEX: 0 – Phases A to H MINOR INDEX: 1 – Phases
~~PAGE 155~~
3U Traffic Outstation Handbook MAJOR MINOR DATA CODE INDEX INDEX RANGE DESCRIPTION AND REMARKS ACCESS LEVEL TIM **3 EXS **2 0 - 15 - Display/Reset shortest measured extension time for each stage MINOR INDEX: STAGE DATA: Shortest Extension in seconds and tenths of seconds. RW TIM **3 IGN **1 - TIM **3 MAX **2 0 - 15 - TIM **3 MIN **2 0 - 15 - VMC 0 - 15 **2 0-3 - Display/Reset shortest measured inter-green time for each phase to phase movement MINOR INDEX: PHASE to PHASE.
~~PAGE 156~~
3U Traffic Outstation Handbook SMS: INACTIVE SMS: INTER STG SMS: MIN ACTIVE SMS: MIN END SMS: EXT MONITR SMS: MAX END SMS: AWAIT END Timing monitoring not active Inter-stage period active Stage minimum timing period active Stage minimum completed Stage extension timing active 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
~~PAGE 157~~
3U Traffic Outstation Handbook MSI - 0-2 - Display Mains state inputs. Minor index: MSI 0 - first 8 mains I/Ps on first I/O Board. 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) RO XIP* - - - Display External Input states. DATA: 8 Bit Binary (bit7 - input bit 7 etc) RO * Only valid if monitoring is on. 11.4.
~~PAGE 158~~
3U Traffic Outstation Handbook 11.5 LAMP MONITORING COMMAND TABLE CODE LMO MAJOR MINOR DATA INDEX INDEX RANGE DESCRIPTION AND REMARKS 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 159~~
3U Traffic Outstation Handbook CODE KAS KDB KLM MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL 1 - 23 0 - 6 BINARY Display LMU Aspect Learn RO sensor aspect *NOTE1 Status number pattern Aspect pattern 0=red, 1=green or number wait and 2=amber 0-1 0-2 RO 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 0
~~PAGE 160~~
3U Traffic Outstation Handbook 11.6 FAULT DATA COMMAND TABLE CODE MAJOR MINOR DATA INDEX INDEX RANGE DESCRIPTION AND REMARKS ACCESS LEVEL FDC 0–8 0-1 - Display Fault Diagnostics See 11.6.1 RW FFC EXL 0 – 15 (**2) - Display LONG EXTENSION fault Filter count for each stage. Minor Index: stage Data: Fault Filter Count RO FFC EXS 0 –15 (**2) - Display SHORT EXTENSION fault filter count for each stage.
~~PAGE 161~~
3U Traffic Outstation Handbook CODE MAJOR MINOR DATA INDEX INDEX RANGE DESCRIPTION AND REMARKS FFT - MIN FLT (**3) - - NOTE: **1 - Dependant on number of PHASES configured **2 - Dependant on number of STAGES configured **3 - Restricted use of the ‘.’ (dot) command - ACCESS LEVEL Display SHORT MIN fault filter timer. Data: Time (hours-minutes). RO View current Fault List Selects first non-zero entry (see section 11.6.2 for details) RO 11.6.
~~PAGE 162~~
3U Traffic Outstation Handbook 11.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 OMCU configuration data) are exceeded. Where PB680 issue 5 (or later) firmware is fitted, the FLG command is also available.
~~PAGE 163~~
3U Traffic Outstation Handbook * = Code only used in the fault log (FLG), not the current fault list (FLT) = More details 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 11.
~~PAGE 164~~
3U Traffic Outstation Handbook * = Code only used in the fault log (FLG), not the current fault list (FLT) = More details on these codes is provided in the subsections after this table Code Description - Notes GGR* G1G2 Inactive GPR* Clear GPS Fault GPS GPS Fault GP0* Detector Counts, Group 0 GP1* Detector Counts, Group 1 HSI* Handset plugged In HSO* Handset Out INI* OMCU RAM Initialised IOA* IO line Override Active IPO Instation Plan Override IPR* Instation Pla
~~PAGE 165~~
3U Traffic Outstation Handbook * = Code only used in the fault log (FLG), not the current fault list (FLT) = More details on these codes is provided in the subsections after this table Code Description - Notes NPR No Port Response - from 141 controller handset port OEA* OMCU Event Active OEI OMCU Event Inactive OLC* Occupancy Logging Complete OOV* bus Operations log Overflow PCF PAKNET Comms Failure PCR PAKNET Comms Failure reset PFC* Plessey/Siemens Fau
~~PAGE 166~~
3U Traffic Outstation Handbook * = Code only used in the fault log (FLG), not the current fault list (FLT) = More details on these codes is provided in the subsections after this table Code Description - Notes Absence Fault VCF Vehicle Classifier Confirm Fault VCL* Vehicle Classifier Licence Fault Vehicle Classifier Vehicle VCP Presence Fault Vehicle Classifier Confirm Fault VCR Reset VLF Vehicle Lamp Fault
~~PAGE 167~~
3U Traffic Outstation Handbook : A number 0 to 31, identifying the group number within a plan : A number 0 to 31, identifying the action numberwithin a group : 00 = Car Park Empty 01 = Car Park Almost Full 02 = Car Park Full : Different error codes are used with different fault codes.
~~PAGE 168~~
3U Traffic Outstation Handbook The above example indicates that phases B, D, E, F, K and M were all at GREEN when the conflict occurred: HEX: Binary: PHASES: 1 0001 PONM 4 0100 LKJI 3 0011 HGFE A 1010 DCBA 11.6.4 Ignoring Demands Fault (FLT CID) If the controller is ignoring any detector or push-button demands then the following fault data will be presented: FORMAT: FLT:!CID Where is a letter (A to P) representing the controller phase that is not being serviced.
~~PAGE 169~~
3U Traffic Outstation Handbook 11.6.5 Dim/Bright Fault (FLT DBF) If the controller fails to change from DIM to BRIGHT (or vice-versa) at least once in 24 hours then the following fault data will be presented: FORMAT: FLT:!DBF n Where ‘n’ is a number representing the current state: 0 - currently DIM 1 - currently BRIGHT 2 - state undefined 3 - processing to determine state not yet started 11.6.
~~PAGE 170~~
3U Traffic Outstation Handbook 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 *1 *2 *3 Test Conflict Test No-Conflict Test Non-Equivalence Non-Equivalence Conflict Monitor Status Error Safety Red Lamp Fail *2 Pedestrian Red Lamp Fail *2 Red Lamp Fail *2 Amber Lamp Fail *2 Green Lamp Fail *2 Permanent Detect Permanent No-Detect 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
~~PAGE 171~~
3U Traffic Outstation Handbook 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 Current detector fault status “ “ “ “ “ “ “ “ “ “ “ “ (unused). (unused). (unused). (unused). (unused). Accepted detector fault status “ “ “ “ “ “ “ “ “ “ “ “ (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).
~~PAGE 172~~
3U Traffic Outstation Handbook 11.6.11 Mode Change Fault (FLT MCH) If the OMCU has detected a change in controller operating mode the following fault data will be presented: FORMAT: FLT:!MCH ‘n’ Where ‘n’ represents the mode the controller moved to i.e.: 0 - Fixed Time 1 - Manual 2 - Vehicle Actuated 3 - Cableless Link 4 - Bus priority 5 - Emergency Vehicle 6 - Hurry Call No.1 7 - Hurry Call No.
~~PAGE 173~~
3U Traffic Outstation Handbook The Site Power Fail fault and clearance will be reported with the same priority as configured for the OMU Power Failure report, i.e. “Urgent” or “Non-Urgent”. 11.6.14 Controller Stuck Fault (FLT STK) If, during Fixed Time or CLF operation, the OMCU detects that the controller is not changing stage for more than the configured period, the following fault data will be presented: FORMAT: FLT:!STK 11.6.
~~PAGE 174~~
3U Traffic Outstation Handbook 11.7 PSTN COMMAND TABLE CODE MAJOR MINOR DATA INDEX INDEX RANGE DESCRIPTION AND REMARKS ACCESS LEVEL CDC 0-1 0-9 - Call Disconnect Cause statistics log (see section 11.7.1 for details) Maint CTR 0-1 0-2 - Call Termination Record Maint (see section 11.7.2 for details) CRQ - 0 - CTN 0-2 0 - 11 HEX FTR - 0-3 - Display PSTN FAULT TIMERS.
~~PAGE 175~~
3U Traffic Outstation Handbook CODE MAJOR MINOR DATA INDEX INDEX RANGE DESCRIPTION AND REMARKS MDC 0 - 12 0-1 - Display MESSAGE HANDLER DIAGNOSTIC data. ACCESS LEVEL Maint (see section 11.7.4 for details) MOS - - ASCII User defined modem configuration string Maint RIF - - - Display RETRY INHIBIT flag Data: 0-Inactive (dialling allowed) FF-Active (dialling not Allowed) RO RSC - - - Display RETRY STEP counter.
~~PAGE 176~~
3U Traffic Outstation Handbook Where is the ‘major index’ and is the ‘minor index’. The major index controls the log that is being viewed i.e.: Major Index = 0 Major Index = 1 - Current Log Historic Log The minor index controls the part of the log is being viewed i.e.: Minor Index 0 1 2 3 4 5 6 7 8 9 Function Manual clearance of MTF initiated call. Good termination Carrier failed Not used. Initiate/Dial timeout. Not used. Not used. Message timeout (i.e.
~~PAGE 177~~
3U Traffic Outstation Handbook 11.7.3 Modem Control Indicators (MCI) This command displays the state of the modem interface (some indications are for hardware functions, others will be software). The default display is binary with a “1” indicating the signal is active. FORMAT: MCI where is the ‘minor index’. First Byte (i.e. Minor index = 0): BIT No.
~~PAGE 178~~
3U Traffic Outstation Handbook FORMAT: MDC where is the ‘major index’ and is the ‘minor index’. MAJOR INDEX 0 1 } 2 } 3 } 4 5 6 7 8 9 10 11 12 COUNT TITLE Good Characters received Not used (characters which are received with parity errors etc are substituted with ‘?’ and so cause other error counts to be incremented.
~~PAGE 179~~
3U Traffic Outstation Handbook 11.8 MAINTENANCE COMMAND TABLE MAJOR MINOR DATA ACCESS CODE INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL BAS 0-2 open Handset Display Base: 0 = Binary, 1 = HEX, 2 = Decimal CAL Maint 0-1 Call Instation: Request local dial-back using configured telephone numbers.
~~PAGE 180~~
3U Traffic Outstation Handbook CODE FLG FRE INI MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO Fault Log: Display time stamped fault log, one line at a time. Shows the date and time of the most recent (approx. 1000) faults and events. See section 11.6 for fault abbreviations.
~~PAGE 181~~
3U Traffic Outstation Handbook MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL 256 RO RAM Installed (PB680 or Displayed the number of Kilobytes issue 1024 of RAM installed in the OMU. CODE RAM 17 or later RCS - - SCT - - SEB - 0-3 SEC - - SES 0-9 0-1 SOB - - (PB680 issue 5 or later) - Radio Clock Signal: Displays message being received from the Radio Clock and Radio Clock error counts. See 11.8.
~~PAGE 182~~
3U Traffic Outstation Handbook MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL 0-2 BINARY Set output ports - sets/displays Maint the state of the 16 outputs on Bus board / MOVA I/O board ‘n’ (0-2), e.g.
~~PAGE 183~~
3U Traffic Outstation Handbook MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL 1 - 64 0-1 Maint ‘Temp’ Flags used by OMCU (PB680 flag no. conditioning. issue 5 Flags can be changed to control or later) conditioning operations (where configured on the OMCU). TOD Maint time TOD displays day, date and time. format e.g.
~~PAGE 184~~
3U Traffic Outstation Handbook 11.8.1 OMCU I/O Port State (IOP) The state of the OMCU's input/output ports may be displayed by the use of this command. Also see DIP for digital inputs, MSI for mains’ state inputs and SOP for digital outputs.
~~PAGE 185~~
3U Traffic Outstation Handbook 11.8.4 Soft Error Buffer (SEB) If the OMCU operating system detects a 'soft error' this buffer will store relevant data on the error type. Any entries in this array should be conveyed to Traffic Engineering (Siemens Poole) for detailed analysis. FORMAT: SEB where is the minor index (0 - 3) and enables access to the last four soft errors (0 is the most recent).
~~PAGE 186~~
3U Traffic Outstation Handbook The OMCU internal clock is only synchronised to the radio clock time signal when the radio clock signal has been received correctly over two consecutive minutes and the RF quality indicated by the radio clock is good. After power on, the radio clock takes 10 to 15 minutes to indicate good RF quality to the OMCU. During this period, the RFQ error count is incremented. The error counts are cleared when the OMCU synchronises to the radio clock signal.
~~PAGE 187~~
3U Traffic Outstation Handbook Code BRC Major Index Minor Index - - 065535 - - 0 - 11 (4 ports per board) (Issue 13 or later) BRP Data Range Description V3.0 or earlier SIETAG readers). (Issue 13 or later) TCSU specific command: Major Minor Code Index Index BMD (Issue 13 or later) NOTE : On earlier OMCU s/w versions, it is not possible to supply V3.3 or later test SIETAG vehicle detections. Bus Receive Count: Repeats the BRX command for the given count.
~~PAGE 188~~
~~3U Traffic Outstation Handbook 1.~~
~~PAGE 189~~
3U Traffic Outstation Handbook 3. Corrupt Detect message entry 25-APR-99 10:51:10 E:D4 M:.034578768. E: M: = Error code (HEX) : D2 = Invalid LAN Address D4 = Invalid Message Type D6 = Invalid Checksum D8 = Bad Format Message = Message characters as received on the serial port. Non-printing characters e.g. are displayed as a ‘.’ NOTE : A GAMBICA vehicle detection received from a SIETAG reader is recorded as an Invalid Message Type error (D4). 11.9.
~~PAGE 190~~
3U Traffic Outstation Handbook 11.10 BUS CONFIGURATION COMMAND TABLE Code JID BID For TCSU Major Index - - Beacon BID for - SIETAG Reader SRC - RET - BFT - BFO - 667/HB/26568/000 Minor Index - Data Range Description 0-9 Junction ID: The ID can only be set and if the OMCU is unconfigured (forced by INI=1). 16 digits maximum, including the character. 0 - FF Beacon ID: 0 - 15 beacon 1-F = RS485 Beacon ID number.
~~PAGE 191~~
3U Traffic Outstation Handbook Code BFR Major Index - Minor Index - ASS 0 - 255 0 list entry number 1 2 3 4 5 6 7 8 9 10 667/HB/26568/000 Data Range Description 0-2 Bus DFM Fault Reporting: 0 = no fault reporting 1 = non-urgent (interrogation only) 2 = urgent report (dial out) 0 - FF Output Association List Beacon/Reader ID: 1-FF = accepted ID 0 = List entry not used 0 - 255 Output Action: 1-30 = Activate this Output Action List entry number if the other conditions match 0 = No output action (o
~~PAGE 192~~
3U Traffic Outstation Handbook Code ACT Major Index 1 - 30 Minor Index 0 list entry number 1 2 3 Data Range Description 0-n Output Action List Output Period: 0-n = Time for which the Detect Outputs are activated, in 0.1 sec units (100 sec max. for SIETAG, 2 sec max for TCSU) 0-n Start Delay: 0-n = Time delay before activating the Detect Output, in 0.1 sec units (100 sec max. for SIETAG, 2 sec max for TCSU) 0-n Stop Delay (TCSU only) 0-n = Time delay after activating the Detect Output in 0.
~~PAGE 193~~
3U Traffic Outstation Handbook Code POC Major Index 0 - 11 (4 ports per board) Minor Index 0 1 POS - 2 3 4 - LDV - - RCI - (Issue 13 or later) 667/HB/26568/000 - Data Range Description 0-6 RS485 Port Configurations (use POS to implement) Baud rate: 0=300, 1=1200, 2=2400, 3=4800, 4=9600, 5=14400 and 6=19200 0-3 Parity setting: 0=space, 1=odd, 2=even, 3=mark 0-1 Parity enable: 0=disable, 1=enable 1-2 Stop bits: 1 or 2 7-8 Data bits: 7 or 8 0-1 Port Set: 1=Set RS485 ports to the configured setti
~~PAGE 194~~
3U Traffic Outstation Handbook Code RCR Major Index - Minor Index - RCD - - RTO - - MAP - 0-9 input priority LAN - - TAI - - Data Range Description 0-2 Radio Clock fault Reporting: 0 = no fault reporting 1 = non-urgent (interrogation only) 2 = urgent report (dial out) 0 - 255 Radio Clock fault Delay : 1 - 255 = fault delay in hours. 0 = no delay (any fault is reported) 0 - 255 Real Time clock Output: Pulsed at 05:00 AM each day.
~~PAGE 195~~
3U Traffic Outstation Handbook Code ARM Major Index - Minor Index - ARV - - TAF - - Data Range Description 0-2 Area Mode: 0 = no area filtering applied 1 = ZONE mode: discard vehicle message if area field is not equal to Area Value 2 = PRIORITY mode: discard vehicle message if area field is less than Area Value 0 - F Area Value: 0-F = Sets either the zone or priority level for vehicle message filtering, depending on Area Mode.
~~PAGE 196~~
3U Traffic Outstation Handbook 11.12 CAR PARK COUNT COMMAND TABLE Code FUT Major Index - Minor Index 0 1 AFT - 0 1 Data Range 016383 Access Level Maint This value indicates the car par occupancy level when the car park state changes from Almost Full to Full. 0 - 255 Car park full decreasing threshold offset 016383 This value is subtracted from the full increasing threshold and the result indicates the car park occupancy level when, the car park state changes from Full to Almost Full.
~~PAGE 197~~
3U Traffic Outstation Handbook Code CCL Major Index - Minor Index 0-9 Data Range Description 0 - 255 Current Car Park Loop Counts CPO - - CPT 0-9 FCP - 0 1 2 - 065535 0 - 23 0 - 59 0-4 1 - 63 CPL 0-9 0 0-1 1 0 - 255 2 0 - 255 3 0 - 255 DOR - - 0 - 255 EDI - - 0 - 255 667/HB/26568/000 Indicates the number of vehicles counted by each entry or exit loop since the last status message was transmitted to the Instation.
~~PAGE 198~~
3U Traffic Outstation Handbook Code RMP Major Index - 667/HB/26568/000 Minor Index 0 Data Range 0 - 63 1 0 - 15 2 0 - 63 3 0 - 15 Description Ramp Up Time Threshold The number of minutes before the FULL state is reached at which ramp up mode is entered Ramp Up Period The interval in minutes between status reports to the Central Office whilst in ramp up mode Ramp Down Time Threshold The number of minutes before the ALMOST FULL state is reached (from the FULL state) at which ramp down mode is enter
~~PAGE 199~~
3U Traffic Outstation Handbook 11.13 PAKNET COMMAND TABLE Code RCA RCB Major Index - - Minor Index - - RCT ADR - - RDF - - RCU - 667/HB/26568/000 - Data Range 14 ASCII digits 0-9 Description Remote Comm’s user address (NUA) of the form : 2353ABCDEFGHIJ 2353 is the Data Network Identification Code allocated to the Vodafone Data Network by OFTEL. ABCD identifies the base station channel with which the Radio-PAD is communicating. EFGHIJ is the unique address of a port on the Radio-PAD.
~~PAGE 200~~
3U Traffic Outstation Handbook 11.14 DUSC COMMAND TABLE 11.14.1 CLF Operating Commands CODE APL CCP CCT CGR CGT CID COD MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO A ctive C LF P lan is displayed. Use CLF RPL to request a different plan or plan 0 - 15 Isolate. NOTE: When CLF is isolated due or Isolate to fault this command still indicates the requested plan, even 255 though it’s not running CLF. Call Current Plan i.e.
~~PAGE 201~~
3U Traffic Outstation Handbook CODE CYC MTS OPS RPL SWS MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO CLF 0 - 255 CYCle time for the specified CLF plan. plan secs 0 to 254 = cycle time 0 - 15 255 = plan is disabled RO MoniTor CLF Status for a Stream. 0 - 31 See section 11.14.1.1 for more Stream details.
~~PAGE 202~~
~~3U Traffic Outstation Handbook 11.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 203~~
3U Traffic Outstation Handbook 11.14.2 Accessing CLF Configuration Data Commands CODE ACF CAO CCC CCF CEC IFA MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO CLF Action on Compliance Fail. 0-1 This is the action that is performed when the OMCU detects a compliance failure. 0 = isolate mode 1 = continue normal CLF output control RO Action 0-3 0 - 255 CLF Action Outputs.
~~PAGE 204~~
3U Traffic Outstation Handbook CODE IFN OFF PIA PLE PLI PLT MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO Influe CLF Influe Influence FuNction i.e. which set group Type function does this group perform in the specified influence set. 0 – 15 0 - 31 0-3 RO CLF Time 0 - 59 CLF OFFset from the configured base time (e.g. 2am) for the plan part secs / specified CLF plan. 0 - 15 0-1 mins OFF 0 : <0 to 59 seconds> OFF 1 : <0 to 59 minutes> RO Plans Isolate Action i.
~~PAGE 205~~
3U Traffic Outstation Handbook CODE PLX RSA TDY TSD MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO CLF 0 - 255 Plan Exit time for the specified CLF plan i.e. the normal point in plan secs the cycle where the plan is 0 - 15 required to finish. 255 = plan can exit at any point in the cycle. RO Action Stream Related Stream for Action. number 0 - 31 Displays the stream associated with the specified group action.
~~PAGE 206~~
3U Traffic Outstation Handbook CODE TSH TSW MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO The Timetable Special Holiday Entry Second Date DDMMMYY table defines up to 32 periods Index 0 - 31 between the specified start and 0-1 end dates (inclusive) where 0= different timeswitch events are start executed, e.g. during school 1 = end holidays.
~~PAGE 207~~
3U Traffic Outstation Handbook 11.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 208~~
3U 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. 11.14.
~~PAGE 209~~
3U Traffic Outstation Handbook CODE CKM CKR CKS CSI MAJOR MINOR DATA ACCESS INDEX INDEX RANGE DESCRIPTION AND REMARKS LEVEL RO GPS Clock monitor command is text used to display the last message from the GPS receiver. This will indicate if the OMCU 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 210~~
~~3U Traffic Outstation Handbook 11.~~
~~PAGE 211~~
~~3U Traffic Outstation Handbook 11.~~
~~PAGE 212~~
~~3U Traffic Outstation Handbook 11.17 OMCU EVENT AND SWITCH OVERRIDE COMMAND TABLE 11.17.~~
~~PAGE 213~~
3U Traffic Outstation Handbook 11.18 VEHICLE CLASSIFIER COMMAND TABLE 11.18.1.1 Vehicle Classifier Common Configuration Code VCC Major Index - 667/HB/26568/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 214~~
~~3U Traffic Outstation Handbook 11.18.1.~~
~~PAGE 215~~
3U Traffic Outstation Handbook 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 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 216~~
3U Traffic Outstation Handbook 4 0 – 11 or 250 Transmission Communications Link Indicates on which communications link the messages identified by Transmission Message ID are to be transmitted. 0 – 11 = RS485 serial port 250 = MCE141 port 255 = no port selected 11.18.1.4 Vehicle Classifier Site Parameters Code VSP Major Index 0–3 Minor Index 0 Site number 1 2 3 667/HB/26568/000 Data Description Range 0 – 255 Loop Spacing Distance in 0.
~~PAGE 217~~
3U Traffic Outstation Handbook 4 0 – FF 5 0 – 1F Logging Control Byte 1 Controls whether VC events are to be logged for a given lane at the site. Bit 0 = Logging enable for lane 0 : Bit 7 = Logging enable for lane 7 Bits 0 to 7 set to a 1 indicates logging enabled for the corresponding lane. If the lane is not defined at the site, the unused bit are set to 0.
~~PAGE 218~~
3U Traffic Outstation Handbook Note : Message bytes that are non-printable i.e. have a binary value in the range 0 to 31 or 127 to 255 are displayed as \xx where xx is the ASCII hexadecimal representation of the message byte. Message bytes that are printable i.e. have a binary value in the range 32 to 126 are displayed as the ASCII representation. For example : The 14 byte message “Mickey Mouse” + 2 bytes of CRC 1245 would be displayed on the handset as follows – VTM x y:\0EMickey Mouse\12E 11.18.1.
~~PAGE 219~~
3U Traffic Outstation Handbook 11.18.1.7 Vehicle Classifier Traffic Data Parameters Code VTD Major Index - Minor Index 0 Data Range 0–F 1 0–1 2 1 - 60 Description Statistics Selection Indicates which information types each TD event contains. Can be one or more of the following (appropriate bit set to 1 to indicate statistic is present in TD event) : Bit 0 = Average speed Bit 1 = All configured statistic categories.
~~PAGE 220~~
3U Traffic Outstation Handbook 11.18.1.9 Vehicle Classifier Speed Display Code SDF Major Index - Minor Index - Data Range 0–1 Description Speed Display Format Determines in which format the vehicle speed is displayed by the OLG handset command when a VC or a TD event is read from the Operations Log. 0 = kph 1 = mph (default) Access Level Maint 11.18.1.
~~PAGE 221~~
3U Traffic Outstation Handbook 1 2 3 4 5 0–7 Lane Number Lane number at which vehicle is detected. 0 – 15 Vehicle Type Identifies the vehicle type. 0– Vehicle Length 2550 Vehicle length in 0.01m units. 0 – 255 Vehicle Speed Vehicle speed in kph. 0 – 255 Vehicle Headway Vehicle headway in 0.1s units. The above test message is sent when the VRC command is assigned a count.
~~PAGE 222~~
3U Traffic Outstation Handbook 11.18.1.13 Vehicle Classifier Detect Condition Statistic Category Map Code VSM Major Index - 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). 255 = no statistic category Access Level RO 11.18.
~~PAGE 223~~
3U Traffic Outstation Handbook Field TIMESTAMP “ L:” SITE / LANE ““ VEHICLE TYPE ““ VEHICLE LENGTH “m ” VEHICLE SPEED “kph ” or “mph” VEHICLE HEADWAY “s O:” OUTPUT ACTION Max Size 18 3 2 1 Variable 1 5 2 3 4 4 4 8 Format Range See below Text Hexadecimal Text Text Text Decimal Text Decimal Text Decimal Text Hexadecimal See below 0–3/0–7 Depends on configured text. 0.0 – 25.5 0 – 255 0.0 – 25.
~~PAGE 224~~
~~3U Traffic Outstation Handbook 23-JAN-02 16:30:00 DC:1 11.18.3.3 TD Event The following defines the handset output format for a TC event when the OLG command is used.~~
~~PAGE 225~~
3U Traffic Outstation Handbook Statistics category 0 holds a count of 4563. Site 0 lane 0 contains average vehicle speed, headway and occupancy of 62kph, 8.3s and 11% respectively. Site 1 lane 0 contains average vehicle speed, headway and occupancy of 74kph, 5.1s and 34% respectively. 23-JAN-02 16:32:00 L:00 40mph L:01 52mph Site 0 lane 0 contains average vehicle speed of 40mph. Site 0 lane 1 contains average vehicle speed of 52mph.
~~PAGE 226~~
3U Traffic Outstation Handbook CODE RGL MINOR MAJOR INDEX INDEX n 0-1 RAP - 0 – 15 REN - 0 - 15 667/HB/26568/000 DATA RANGE 8 bits binary ACCESS DESCRIPTION AND REMARKS LEVEL RAID ATGBV Low – Shows 16 ATGBV detectors, 1 indicates that the ATGBV was below the low threshold during the last read only averaging period. Index 0 shows bits 0 – 7; index 1 shows bits 8 – 15 10 – 600 RAID Averaging Period – Time in read only seconds over which RAID measurements are calculated.
~~PAGE 227~~
3U Traffic Outstation Handbook Appendix A MOVA INSTALLATION SHEETS The following two A5 pages may be photocopied onto a single A4 sheet. 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 228~~
3U Traffic Outstation Handbook MOVA INSTALLATION SHEET (1/2) 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/26568/000 Page 228 Use / Name Controller / Det.
~~PAGE 229~~
3U Traffic Outstation Handbook MOVA INSTALLATION SHEET (2/2) MOVA Force and Confirm Bits Det. No. Use / Name Cont. Terminal Det. No. Use / Name Cont. Terminal Det. No. Use / Name Cont. Terminal TO CRB G9 F1 G1 G10 F2 G2 G11 to G16 require a 2nd Bus/MOVA I/O Card F3 G3 G11 F4 G4 G12 F5 G5 G13 F6 G6 G14 F7 G7 G15 F8 G8 G16 Telephone Line Sharing with Siemens 3U OMCU (see section 9.
~~PAGE 230~~
~~3U Traffic Outstation Handbook Appendix B OMCU DRAWINGS B.1 Introduction Section B.2 contains a list of the drawings that are included at the back of this handbook. B.~~
~~PAGE 231~~
3U Traffic Outstation Handbook INDEX — A — ACF (CLF Action on Compliance Fail) ................................................................... 203 ACT (Bus Output Action List) ......................................................................... 192, 195 ADR (Remote Comm’s OMCU Address).......................................................... 81, 199 AEC (Accumulated Error Counts) .......................................................................... 153 AFT (Car Park Almost Full Threshold) .
~~PAGE 232~~
3U Traffic Outstation Handbook Description .................................................................................................. 35, 135 Handset Commands ......................................................................................... 196 Installation........................................................................................................... 46 CBR (Controller Baud Rate)...................................................................................
~~PAGE 233~~
3U Traffic Outstation Handbook CPP (Controller Phase Pattern) ....................................................................... 34, 153 CPS (Car Park State) ............................................................................................. 196 CPT (Car Park Timetable)...................................................................................... 197 CRQ (Call Request Flag) .......................................................................................
~~PAGE 234~~
3U Traffic Outstation Handbook Group Information (CGR/CGT) ......................................................................... 200 Handset Commands ......................................................................................... 200 Influences (IFA/IFN/PLI) ........................................................................... 203, 204 Instation Clock (CDI/CSI).......................................................................... 208, 209 Outputs (CAO/COD/OPS)........................
~~PAGE 235~~
3U Traffic Outstation Handbook FOH (Flow High) .................................................................................................... 210 FOL (Flow Low)...................................................................................................... 210 FOP (Flow Count Period) ....................................................................................... 210 FOS (Smoothed Flow Result) ................................................................................
~~PAGE 236~~
3U Traffic Outstation Handbook — J — JID (Junction ID) .............................................................................................. 78, 190 — K — KAC (Lamp Monitor ADC Readings) .................................................... 34, 77, 98, 158 KAS (Lamp Monitor Aspect Learn Status)........................................................ 34, 159 KDB (Lamp Monitor Dim/Bright State)..............................................................
~~PAGE 237~~
3U Traffic Outstation Handbook Handset Commands ......................................................................................... 174 Power Selection .................................................................................................. 50 PSTN .................................................................................................................. 20 MON (Monitoring Status)........................................................................................
~~PAGE 238~~
3U Traffic Outstation Handbook Status (EVS) ..................................................................................................... 212 OMCU Handset Commands.................................................... see Handset Command OPM (OMCU Operating Mode) .......................................................................... 76, 79 OPS (Output Sense) .............................................................................................. 201 Outputs...................................
~~PAGE 239~~
3U Traffic Outstation Handbook RDF (Reset Car Park Detector Fault)............................................................. 140, 199 RET (Reactivation Time) ................................................................................ 190, 195 RIF (Retry Inhibit Flag) ........................................................................................... 175 RMP (Car Park Ramp Mode Setting) ..................................................................... 198 RPL (Requested CLF Plan).........
~~PAGE 240~~
3U Traffic Outstation Handbook TSD (Timetable Special Days) ............................................................................... 205 TSH (Timetable Special Holiday) ........................................................................... 206 TSW (Timeswitch Settings) .................................................................................... 206 — V — VCC (VC Common Configuration)..........................................................................
~~PAGE 241~~
~~3U Traffic Outstation Handbook LAST PAGE OF THE 3U TRAFFIC OUTSTATION HANDBOOK 667/HB/26568/000 Page 241 Issue 15~~