Preview only show first 10 pages with watermark. For full document please download

Type 400 Controller General Handbook Siemens Traffic Controls Limited Sopers Lane Poole Dorset.

Rating
Date

January 2018
Size

1.9MB
Views

6,452
Categories

technology and computing mp3 and midi router electronic components electricity software

Transcript

Type 400 Controller General Handbook SIEMENS TRAFFIC CONTROLS LIMITED Sopers Lane POOLE Dorset. BH17 7ER PRODUCT: T400 CONTROLLERS T400 CONTROLLER GENERAL HANDBOOK Prepared : P. COX Approved : J.P. BURGESS Function : Software Engineer Function : Engineering Manager Signature : ISSUE: Signature : CHANGE REF.: 1 DATE: APPROVED BY: 13/04/89 2 83/15278 18/07/89 3 83/15611 19/04/90 4 83/15950 15/02/91 5 83/16025 22/03/91 6 83/16703 24/09/92 7 83/17049 10/02/92 8 ANL00272 12/11/96 9 ANL00476 4/7/97 10 Jan 99 © Siemens plc. 1996 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 authorized 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. 667/HB/20200/000 Page i Issue 10 Type 400 Controller General Handbook SAFETY WARNING 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/electronic equipment are to be allowed to use and/or work on the equipment. All work shall be performed in accordance with the Electricity at Work Regulations 1989. (ii) Such personnel must take heed of all relevant notes, cautions and warnings in this handbook, the Maintenance Handbook (667/HA/20200/000) and any other document or handbook associated with the equipment including, but not restricted to, the following: (iii) (a) The equipment must be correctly connected to the specified incoming power supply. (b) The equipment must be disconnected/isolated from the incoming power supply before removing protective covers or working on any part from which protective covers have been removed. (c) This equipment contains a Lithium battery which must be disposed of in a safe manner. If in doubt of the correct procedure refer to the Siemens instructions. In the event of any person working elsewhere on the junction, the mains supply to the controller should be switched off and the master switch locked in the OFF position using the master switch lock facility (667/1/21386/000). Warning:- Removal of the electricity board fuse or switching off the controller switch or manual panel signals ON/OFF switch does not guarantee isolation of the equipment. 667/HB/20200/000 Page ii Issue 10 Type 400 Controller General Handbook ISSUE STATE Note: Source of documents is shown under Type as below. 1=Paper, 2=VAX, 3=Microfilm, 4=CALTEXT Disk, 5=DECmate Disk, 6=Paper Insert, 7=Disk, 8=AMW , 9=SUN, 10=Other - PC Disk The document comprises the following components : Pages Current Issue Type Part ID i to ix 1-1 to 1-17 2-1 to 2-19 3-1 to 3-17 4-1 to 4-15 5-1 to 5-6 6-1 to 6-32 7-1 to 7-16 8-1 A-1 B-1 C-1 to 3 D-1 to 7 E-1 10 10 10 10 10 10 10 10 10 10 10 10 10 10 8 8 8 8 8 8 8 8 8 8 8 8 8 8 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 667/HB/20200/000 Information in this document is subject to change without notice. Companies, names and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Siemens plc. 667/HB/20200/000 Page iii Issue 10 Type 400 Controller General Handbook CONTENTS 1. INTRODUCTION .................................................................................................1-1 1.1 GENERAL ......................................................................................................1-1 1.1.1 FACILITIES ............................................................................................1-3 1.1.2 SIGNALS................................................................................................1-3 1.2 GLOSSARY OF TERMS ................................................................................1-4 1.2.1 Associated Documentation ....................................................................1-5 1.2.2 Kindred Documents................................................................................1-8 1.3 BASIC SYSTEM OVERVIEW .........................................................................1-8 1.3.1 HARDWARE OVERVIEW ......................................................................1-8 1.3.2 Customisation ........................................................................................1-9 1.4 CONSTRUCTION.........................................................................................1-10 1.4.1 Small Outercase...................................................................................1-10 1.4.2 Large Outercase ..................................................................................1-10 1.5 SAFETY........................................................................................................1-12 1.5.1 Controller System Checks....................................................................1-12 1.5.2 Power up Checks .................................................................................1-13 1.5.3 Green Correspondence Tests..............................................................1-14 1.5.4 System Background Test .....................................................................1-15 1.5.5 Operation of the Safety System ...........................................................1-16 1.5.6 Red Lamp Monitoring...........................................................................1-17 2. SPECIFICATION .................................................................................................2-1 2.1 MAINS SUPPLY .............................................................................................2-1 2.1.1 Electrical Noise ......................................................................................2-2 2.2 DETERMINATION OF LOADING, SELECTION OF DIMMING TRANSFORMER & LAMP FUSE .........................................................................2-3 2.2.1 Controller Load ......................................................................................2-3 2.2.2 Lamp Drive Capability............................................................................2-3 2.2.3 Selection of Dimming Transformer.........................................................2-4 2.2.4 Calculating The Lamp Supply Fuse Required .......................................2-5 2.2.5 Calculation Of An Intersection’s Power Requirements For Running Costs Estimate ..........................................................................................................2-7 2.2.6 Regulated Logic Supplies ....................................................................2-10 2.2.7 Regulated Interface & Detector Supplies.............................................2-10 2.2.8 Audible Supplies ..................................................................................2-11 2.3 FUSE RATINGS ...........................................................................................2-12 2.4 PHASES .......................................................................................................2-13 2.5 STAGES .......................................................................................................2-13 2.6 TIMINGS.......................................................................................................2-13 2.7 MASTER TIME CLOCK & CABLELESS LINK FACILITY SUMMARY ..........2-17 2.8 MODES OF OPERATION ............................................................................2-17 2.9 OUTERCASE ...............................................................................................2-17 2.10 ENVIRONMENTAL.....................................................................................2-18 2.10.1 Temperature.......................................................................................2-18 2.10.2 Atmospheric .......................................................................................2-18 2.10.3 Humidity .............................................................................................2-18 2.11 HANDSET INTERFACE (RS232 PORT) ....................................................2-18 667/HB/20200/000 Page iv Issue 10 Type 400 Controller General Handbook 3. TRAFFIC FACILITIES.........................................................................................3-1 3.1 STAGES .........................................................................................................3-1 3.1.1 Stage Facilities.......................................................................................3-1 3.1.2 Allocation Of Phases..............................................................................3-1 3.1.3 Stage Active ...........................................................................................3-1 3.1.4 Stage Terminating..................................................................................3-1 3.1.5 Inter Stage Period ..................................................................................3-1 3.1.6 Stage Movement Restrictions ................................................................3-1 3.1.7 Prevent Stages/Phases..........................................................................3-2 3.2 PHASES .........................................................................................................3-2 3.2.1 Types Of Phases....................................................................................3-2 3.2.2 Conflicting Phases .................................................................................3-2 3.2.3 Opposing Phases...................................................................................3-2 3.2.4 Phase Delays .........................................................................................3-3 3.2.5 Timing Periods .......................................................................................3-3 3.2.6 Limiting Values.......................................................................................3-3 3.2.7 Conditions Of Appearance For Phases..................................................3-3 3.2.8 Fixed Phase ...........................................................................................3-3 3.2.9 Non Fixed Phases..................................................................................3-4 3.2.10 Conditions Of Termination For Phases................................................3-4 3.2.11 Early Termination Of Phases ...............................................................3-4 3.3 DEMANDS AND EXTENSIONS .....................................................................3-4 3.3.1 Types Of Demands ................................................................................3-4 3.3.2 Origins Of Demands And Extensions.....................................................3-4 3.3.3 Repeat Pulses........................................................................................3-4 3.3.4 SDE/SA ..................................................................................................3-5 3.3.5 Handset..................................................................................................3-5 3.3.6 Operation Of Demands And Extensions During Certain Modes ............3-5 3.4 HIGH SPEED VEHICLE DETECTION............................................................3-7 3.4.1 Speed Discrimination Equipment (SDE) ................................................3-7 3.4.2 Speed Assessment (SA) ........................................................................3-7 3.4.3 Assessors Available ...............................................................................3-7 3.4.4 Extra Clearance Periods ........................................................................3-7 3.4.5 SDE/SA on Green Arrows ......................................................................3-8 3.4.6 Other Manufacturers Loops ...................................................................3-8 3.5 MODES ..........................................................................................................3-9 3.5.1 Start-Up Mode........................................................................................3-9 3.5.2 Part-Time Mode .....................................................................................3-9 3.5.3 Urban Traffic Control..............................................................................3-9 3.5.4 Priority Mode ..........................................................................................3-9 3.5.5 Hurry Call Mode .....................................................................................3-9 3.5.6 Selected Manual Control........................................................................3-9 3.5.7 Selected Fixed Time or V.A. or CLF. .....................................................3-9 3.5.8 Normal Mode........................................................................................3-10 3.5.9 Cableless Link Facility (CLF) Mode .....................................................3-10 3.5.10 Vehicle Actuated Mode ......................................................................3-10 3.5.11 Fixed Time Mode ...............................................................................3-10 3.6 MASTER TIME CLOCK................................................................................3-10 3.7 LINKING .......................................................................................................3-10 3.8 ALTERNATIVE SIGNAL SEQUENCES........................................................3-11 667/HB/20200/000 Page v Issue 10 Type 400 Controller General Handbook 3.9 INPUTS & OUTPUTS...................................................................................3-12 3.10 MANUAL PANEL FACILITIES....................................................................3-14 3.10.1 Full Intersection Controller Manual Selection Panel ..........................3-14 3.10.2 Police Manual Panel (Hong Kong) .....................................................3-14 3.10.3 Internal Manual Panel (Hong Kong)...................................................3-15 3.10.4 Basic Manual Panel ...........................................................................3-15 3.10.5 Optional Manual Panel Facilities .......................................................3-15 3.11 SIGNAL AND DETECTOR ISOLATING SWITCHES .................................3-15 3.12 T400 FAILURE FLASHER FACILITY (EXPORT ONLY) ............................3-16 3.13 HANDSET ..................................................................................................3-16 3.14 SPECIFICATION SHEETS (667/DJ/15900/000) ........................................3-17 4. PELICAN/PEDESTRIAN CONTROLLER ...........................................................4-1 4.1 GENERAL ......................................................................................................4-1 4.1.1 Fixed Vehicle Period mode ....................................................................4-1 4.1.2 Pelican VA mode....................................................................................4-1 4.2 PELICAN/PEDESTRIAN TIMINGS.................................................................4-2 4.2.1 Puffin Sequence Timings .......................................................................4-2 4.3 MANUAL PANEL FACILITIES........................................................................4-3 4.3.1 Select VA/FVP .......................................................................................4-3 4.3.2 Continuous Ped. Demand ......................................................................4-3 4.3.3 Continuous Vehicle Extension ...............................................................4-4 4.3.4 DFM Reset .............................................................................................4-4 4.3.5 Auxiliary LEDs (AUX1, AUX2, AUX3) and Switches (SW1, SW2, SW3)4-4 4.4 HANDSET ......................................................................................................4-5 4.4.1 Timings...................................................................................................4-5 4.4.2 Speed Discrimination (SDE/SA).............................................................4-5 4.4.3 Manual Facilities ....................................................................................4-5 4.5 I/O LINE ALLOCATION ..................................................................................4-6 4.6 WAIT INDICATORS .......................................................................................4-7 4.7 AUDIO CONTROL AND MONITOR ...............................................................4-7 4.8 GREEN CONFLICT FAULT ACTION .............................................................4-7 4.9 RED LAMP MONITORING .............................................................................4-7 4.10 DESCRIPTION OF I/O LINE FUNCTIONS ..................................................4-8 4.10.1 UTC Facilities.......................................................................................4-8 4.10.2 Local Link Facilities............................................................................4-11 4.10.3 Call/Cancel Function..........................................................................4-13 4.10.4 Puffin I/O Facilities.............................................................................4-13 4.11 TIMESWITCH FACILITIES.........................................................................4-14 4.12 CLF FACILITIES.........................................................................................4-15 4.13 CROSS-INHIBIT LINKING..........................................................................4-15 5. HANDSET COMMANDS .....................................................................................5-1 6. GENERAL ARRANGEMENT OF T400 HARDWARE.........................................6-1 6.1 SMALL OUTERCASE.....................................................................................6-1 6.1.1 Master Switch Panel ..............................................................................6-1 6.1.2 Controller Panel .....................................................................................6-1 6.1.3 PCB Module ...........................................................................................6-1 6.1.4 Manual Panel & Cabinet Alarm ..............................................................6-1 667/HB/20200/000 Page vi Issue 10 Type 400 Controller General Handbook 6.1.5 Uncommitted Space ...............................................................................6-2 6.2 LARGE OUTERCASE ....................................................................................6-4 6.2.1 Master Switch Panel ..............................................................................6-4 6.2.2 Distribution Panel...................................................................................6-4 6.2.3 PCB Module ...........................................................................................6-4 6.2.4 Manual Panel & Cabinet Alarm ..............................................................6-4 6.2.5 Uncommitted Space ...............................................................................6-5 6.3 EXPANDED DESCRIPTIONS OF T400 HARDWARE & OTHER EQUIPMENT6-10 6.3.1 O.T.Us/O.M.Us.....................................................................................6-10 6.3.2 TELECOMMAND 8 INTEGRAL SCOOT OTU (EXPORT ONLY).........6-10 6.3.3 OTU Functions.....................................................................................6-10 6.3.4 Detector Racks and Detectors .............................................................6-11 6.3.5 Manual Panel & Cabinet Alarm ............................................................6-12 6.3.6 PCB Module .........................................................................................6-21 6.3.7 Power System ......................................................................................6-22 6.3.8 LED Indicators......................................................................................6-23 6.3.9 Handsets ..............................................................................................6-23 6.3.10 300mA Controller Residual Current Detector.....................................6-23 6.4 EXPANDED DESCRIPTIONS OF T400 PCBs.............................................6-24 6.4.1 Main Processor P.C.B (667/1/20221/000) ...........................................6-24 6.4.2 4 Phase Driver PCB (667/1/20223/000)...............................................6-26 6.4.3 2 Phase Driver PCB (667/1/20225/000)...............................................6-26 6.4.4 Manual Panel P.C.B (667/1/20227/000) ..............................................6-27 6.4.5 Expansion I/O PCB (667/1/20229/000) ................................................6-28 6.4.6 Expansion I/O PCB (667/1/20229/001) ................................................6-29 6.4.7 SDE/SA P.C.B (667/1/20231/000) .......................................................6-30 6.4.8 Ancillary Processor P.C.B (667/1/21611/000)......................................6-31 7. GUIDE TO T400 SPECIFICATION FORMS........................................................7-1 7.1 GENERAL ......................................................................................................7-1 7.2 LIST OF FORMS ............................................................................................7-2 7.3 FILLING OUT THE FORMS ...........................................................................7-3 8. T400 MOD STATE CONTROL AND CONFIGURATION....................................8-1 APPENDIX A - SPECIFICATION SHEETS ................................................................ 1 APPENDIX B - MOD STATE CONTROL AND CONFIGURATION ....................... B-1 APPENDIX C - 50-0-50 VOLT CONTROLLER...................................................... C-1 C.1 50-0-50 VOLT CONTROLLER...................................................................... C-1 C.1.1 Signal load limitations........................................................................... C-1 C.1.2 Miniature Circuit Breaker (MCB)........................................................... C-2 C.1.3 Street Equipment .................................................................................. C-2 C.1.4 Dual Solar Cell ..................................................................................... C-2 C.2 GAS PLINTH................................................................................................. C-3 APPENDIX D - ADDITIONAL REQUIREMENTS FOR TUEN MUN....................... D-1 D.1 LAMP DRIVE CAPABILITY........................................................................... D-1 D.1.1 Lamp Load Per Aspect (Watts) ............................................................ D-1 D.1.2 Dimming Transformer ........................................................................... D-1 667/HB/20200/000 Page vii Issue 10 Type 400 Controller General Handbook D.1.3 Calculation Of An Intersections Power Requirements.......................... D-2 D.1.4 Calculating The Lamp Supply Fuse Required ...................................... D-3 D.2 HANDSET RANGE LIMITS, DEFAULT VALUES ......................................... D-4 D.3 INPUTS AND OUTPUTS .............................................................................. D-5 D.4 ADDITIONAL INFORMATION FOR TUEN MUN SPECIAL SPEC. SHEETSD-6 APPENDIX E - T400 CONTROLLER DRAWINGS ................................................ E-1 LIST OF ILLUSTRATIONS FIGURE 2.2 - THEORETICAL JUNCTION..............................................................2-9 FIGURE 6.1 - T400 IN A SMALL OUTERCASE......................................................6-3 FIGURE 6.2(A) - T400 LARGE OUTERCASE FRONT VIEW (TYPICAL)...............6-6 FIGURE 6.2(B) - T400 LARGE OUTERCASE REAR VIEW (TYPICAL) .................6-7 FIGURE 6.2(C) - T400 LARGE OUTERCASE FRONT VIEW (HONG KONG) .......6-8 FIGURE 6.2(D) - T400 LARGE OUTERCASE REAR VIEW (HONG KONG)..........6-9 FIGURE 6.3.5.1 - INTERSECTION CONTROLLER MANUAL SELECTION PANEL6-14 FIGURE 6.3.5.2 - POLICE MANUAL PANEL LAYOUT (HONG KONG) ...............6-16 FIGURE 6.3.5.3 - INTERNAL MANUAL PANEL LAYOUT (HONG KONG)...........6-18 FIGURE 6.3.5.4 - BASIC MANUAL PANEL LAYOUT ...........................................6-19 FIGURE 6.3.5.5 - PELICAN CONTROLLER MANUAL PANEL.............................6-20 FIGURE 6.3.6 - ARRANGEMENT OF PCB’S WITHIN MODULE..........................6-21 FIGURE 6.4.1 - MAIN PROCESSOR PCB............................................................6-25 FIGURE 6.4.8 - ANCILLARY PROCESSOR PCB .................................................6-32 667/HB/20200/000 Page viii Issue 10 Type 400 Controller General Handbook PREFACE It is intended that this preface should guide the reader as to the use of this handbook, thus assisting the reader in selecting the best section to read in order to obtain the information required. Section 1 Introduction:- This will in a brief manner give a basic understanding of the controller construction and capabilities. Section 2 Specification:- This gives values and ranges for the following items: Weight, Size, Currents, Voltages, Lamp loads, Phases, Stages etc. Section 3 Traffic Facilities:- This contains a list of the controllers functions and facilities as a brief overview of its capabilities. Each heading in the list is extracted from Facilities Manual Handbook 667/EB/20200/000. Where further details on each subject can be found. Some headings are followed by brief descriptions to aid understanding. Section 4 Pelican/Pedestrian Facilities:- This contains a brief description of each of the 0125 Pelican and 0145 Pedestrian, and Puffin controller facilities. Section 5 Simplified Handset Commands:- This contains a simplified set of handset commands to give an example of the accessibility of the data stored in the T400. Handbook 667/HH/20200/000 contains full details of T400 handset commands. Section 6 Technical Descriptions:- This contains descriptions of the units of hardware which together make up a T400 Controller. The descriptions are written such that they detail the functions of each unit of hardware. The section starts at a high level with an overview of the controller and then step by step breaks it down to individual unit details. Section 7 Guide to T400 Specification forms:- this section is provided to help the user to fill out the Specification sheets contained in Appendix A. Section 8 PCB issues for use with T400 Firmware: - this section simply refers to the document entitled “Use of T400 Firmware and Configuration” which is contained in Appendix B. Appendix A Specification Sheets:- This is a copy of document number 667/DJ/15900/000 and is used to specify the facilities required in the controller. Appendix B Copy of 667/SU/20200/000 - Mod state control and configuration. Appendix C 50-0-50 Volt Controller Appendix D Tuen Mun Special Requirements Appendix E T400 Controller Drawings 667/HB/20200/000 Page ix Issue 10 Type 400 Controller General Handbook 1. INTRODUCTION 1.1 GENERAL The Type 400 controller is based on the 80188 microprocessor. This is a 16 bit device compatible with but having enhancements over the 8088 processor used in the T200 controller. The software is written in a powerful high level language. This has allowed the implementation of the T400 Controller’s extensive facilities. The Controller offers up to 16 stages and 16 phases controlled using solid state switching. The controller is capable of producing all the required facilities specified in U.K. Department of Transport specification MCE 0141 (Microprocessor Based Traffic Signal Controller for Isolated Link and Urban Traffic Control Installations), MCE 0125 (Pedestrian Operated Equipment) & MCE 0145 (Pedestrian Operated Equipment other than Pelican controllers) plus a number of optional facilities. (See Section 2 traffic facilities). Specification MCE 0141 is based on the following specifications and incorporates their most commonly used features. MCE 0105 - Fixed Time Traffic Signal Controller (Solid State) for use in Area Traffic Control Systems. MCE 0106 - Vehicle Actuated Signal Controllers (Solid State) for use in Area Traffic Control. MCE 0124 - Cableless Linking Controllers. MCE 0126 - Traffic Signal Controller for Isolated and Linked Vehicle Actuated Installations. TCD 316 - Area Traffic Signal Controller Modifications Specifications. Unit for use with Traffic Signal Thus, controllers supplied to specification MCE 0141 can be characterised to allow them to operate in existing Urban Traffic Control Schemes employing MCE 0105, MCE 0106 or TCD 316 control philosophies. The controller appears in two styles:(a) SMALL T400S The small T400 controller consists of a 2 phase pelican or a 4 real phase controller with a minimal set of I/O and is intended to perform at small intersections or where a pelican is required. This controller can be expanded up to 8 Phases and can accommodate Detectors, OTU, OMU and LMU. The 667/HB/20200/000 Page 1-1 Issue 10 Type 400 Controller General Handbook small outercase is ground mounted but is of reduced size and has an access door at the front only. Expansion may be achieved by adding combinations of the following equipment:Additional Phase Boards 2 or 4 phase board plus additional conflict monitoring circuitry - giving up to 8 real phase capability. Input/Outputs May be expanded to a maximum of 96 input/outputs provided as:64 Inputs (50 buffered & 14 unbuffered) 32 Outputs(all buffered). Detectors These can be either Siemens, Microsense, Sarasota self tune units or other external units (micro-wave, infra-red etc). Ancillary Equipment OTU - Outstation Transmission Unit. OMU/OMCU - Outstation Monitoring (& Control) Unit. LMU - Lamp Monitoring Unit. (b) LARGE T400L The large T400 is housed in a ground mounted case of standard size (large outercase) with access doors at the front and rear. There is room to expand the basic system to cater for practically any intersection. Additional Phase Boards 2 or 4 phase boards plus additional conflict monitoring circuitry - giving up to 16 real phase capability. Input/Outputs May be expanded to a maximum of 96 input/outputs provided as:64 Inputs (50 buffered & 14 unbuffered) 32 Outputs (all buffered). Detectors These can be either Siemens, Microsense, Sarasota self tune units or other external units (micro-wave, infra-red etc). Ancillary Equipment OTU - Outstation Transmission Unit. OMU/OMCU - Outstation Monitoring (& Control) Unit. 667/HB/20200/000 Page 1-2 Issue 10 Type 400 Controller General Handbook Bus Priority Interrogator. LMU - Lamp Monitoring Unit. 1.1.1 FACILITIES Operational:Vehicle actuated - SDE/SA is an addition to V.A. - Fixed Time - Computer control in U.T.C system - C.L.F Timetable selected plans - Master time clock This is a real time clock used for the introduction/deletion of selected events or C.L.F plans. - Hurry call - Manual - Priority - Part time (Both OFF/ON or Normal operation/Flashing) - Parallel stage streaming 1.1.2 SIGNALS - Normal traffic phases - Pedestrian phases (with WAIT indicators) - Pelican vehicle phases - Pelican pedestrian phases (with WAIT indicators & audible signal) - Green arrow (filter and indicative) - Switched signs - LRT phase (it has the signal sequence of a pedestrian phase with flashing green instead of blackout.) 667/HB/20200/000 Page 1-3 Issue 10 Type 400 Controller General Handbook 1.2 GLOSSARY OF TERMS AC ACT CLF CLU CMOS CPU CRC DC DFM ELCB EPROM GP I/O LCD LED LSTTL MC OMCU OMU OTU PCB PPM PROM RAM RCD RMS ROW RTC SA SCOOT SDE ST SWG TTL UTC VA Alternating Current Advanced CMOS compatible with TTL Cableless Linking Facility Cableless Linking Unit Complementary Metal Oxide Silicon Central Processing Unit Cyclic Redundancy Code Direct Current Detector Fault Monitor Earth Leakage Circuit Breaker Erasable Programmable Read Only Memory General Purpose Input/Output Liquid Crystal Display Light Emitting Diode Low Power Schottky Transistor Transistor Logic Manual Control Outstation Monitor and Control Unit Outstation Monitor Unit Outstation Transmission Unit Printed Circuit Board Parts Per Million Programmable Read Only Memory Random Access Memory Residual Current Device Root Mean Square Right Of Way Real Time Clock Speed Assessment Split Cycle Offset Optimisation Technique Speed Discrimination Equipment Self Tuning Standard Wire Gauge Transistor Transistor Logic Urban Transport Control Vehicle Actuated 667/HB/20200/000 Page 1-4 Issue 10 Type 400 Controller General Handbook 1.2.1 Associated Documentation 667/EB/20200/000 - T400 CONTROLLER FACILITIES MANUAL This handbook details the uses of, and how to specify (using customer spec. sheets) the requirements for the following facilities: Stages Phases Demands and Extensions Call/Cancel High Speed Vehicle Detection All Red Displays Phase Delays Modes:Start Up Part Time Urban Traffic Control (UTC) Emergency Vehicle Priority Hurry Call Selected Manual Stage Control Manual Stage Control Manual Step On Selected Fixed Time/Vehicle Actuated Cableless Linking Facility (CLF) Vehicle Actuated Fixed Time Stage Movement Restrictions The Master Time Clock System Event Time Table Linking Alternative Signal Sequences and Flashing Signals Inputs and Outputs Manual Panel Equipment Options At the end of this handbook are worked examples of intersections with customer specification sheets completed. 667/HB/20200/000 Page 1-5 Issue 10 Type 400 Controller General Handbook 667/HH/20200/000 - TYPE 400 CONTROLLER HANDSET COMMAND LIST The handbook details the following:Data entry, display and command formats. The controller data which can be accessed via the handset and the handset commands necessary to access the items. Operational aspects of the intelligent terminal software, which allows an EPSON HX20 to act as an intelligent terminal for use with a T400. Operational aspects of the software, which allows a Portable IBM-compatible computer to act as an intelligent terminal for use with a T400. 667/HH/15900/010 - TUEN MUN HANDSET SUPPLEMENT This supplement to the handset command handbook 667/HH/20200/000 details the operational facilities of the TRAFFIC CONTROLLER TERMINALS, supplied on the TUEN MUN - YUEN LONG LRT/TRAFFIC CONTROL contract. 667/HD/15900/000 - INTERSECTION CONFIGURATOR 3 USERS H/BOOK (Only available to owners of the configurator) This handbook details the following:(a) The hardware requirements for a configuring system (the configurator is Siemens software running on an IBM PC compatible computer). (b) How to use the configuring system to enter data from the completed customer specification sheets into the computer and produce the programmed EPROMs required to configure the T400 controller. This includes the writing of special conditioning and details on error messages which may be produced during the processing of data entered. 667/HB/20200/000 Page 1-6 Issue 10 Type 400 Controller General Handbook 667/HE/20200/000 - T400 CONTROLLER INSTALLATION AND COMMISSIONING MANUAL This handbook details the requirements for installation and commissioning a T400 controller. 667/HA/20200/000 - MAINTENANCE H/BOOK FOR T400 CONTROLLERS This handbook details the following:Safety procedures when working on the T400 traffic controller and its ancillary equipment. The use of the handset/terminal for maintenance purposes. Routine maintenance/inspection procedures. Fault finding procedures. Procedures for replacing pcbs. Clarification of specific controller functions. PCB histories and retrospective modifications since initial design. The last section of the handbook contains a basic overview of the controller hardware at module level with a block diagram representation of the hardware. 667/KM/20200/000 - SPARES ITEMS LISTS (WITH MANUFACTURING PART NUMBERS) This contains items lists for the hardware assemblies which together make up the traffic controller. These hardware assemblies may be used as spares. If any components not listed in this document are used then the controller approval is null and void. 667/HB/26900/000 - GENERAL H/BOOK FOR T400 CONTROLLERS IN USER OUTERCASES This handbook provides basic details of the T400 mounted in a U.K. user outercases as specified by the Traffic Signals User Group (TSUG). 667/HB/20200/000 Page 1-7 Issue 10 Type 400 Controller General Handbook 1.2.2 Kindred Documents 667/DJ/15900/000 - CUSTOMER SPECIFICATION SHEETS This is a set of blank customer specification sheets. Note - A set of these are included in this book as Appendix A. 1.3 BASIC SYSTEM OVERVIEW Control Microprocessor Program Storage Program Data Program Variables Logic - Intel 80188 family Powerful chip set High level language (PLM) PROM (27C010) PROM (27256 & 27512) (Intersection data) - Battery backed static RAM (16k x 8). - CMOS Lamp Switching Triac - Opto isolated, Zero crossing. - No load dimming changeover - Signals on dim at start up to reduce surge currents Conflict System PROM Data - Self testing Physical Hardware Logic:Peripheral:- Double Extended Euro Card Single Extended Euro Card 1.3.1 HARDWARE OVERVIEW 1.3.1.1 Main Processor Board The operations of the T400 are controlled by the Main Processor Board. This board contains a microprocessor based on the Intel 80188 microprocessor. It also contains a Real Time Clock, an RS232C interface for communications with a handset, the Configuration, Conflict and Firmware Proms, I/O for interfacing with the Phase Driver Boards, Manual Panel and general inputs and outputs e.g. detectors, control signals etc. 667/HB/20200/000 Page 1-8 Issue 10 Type 400 Controller General Handbook 1.3.1.2 4 Phase Driver Board This board contains the triacs which are used to switch the mains on to the traffic signals, up to four Phases can be controlled by one board. It also contains a solar cell monitor, a lamp supply Monitor and a mains zero voltage crossover monitor. A maximum of four boards can be fitted in the large controller and two in the small controller. 1.3.1.3 2 Phase Driver Board and Red Lamp Monitor This board is similar to the 4 Phase Driver Board except that only two Phases are controlled and it has a Red Lamp Monitor which is for use with Pelican (and certain pedestrian crossings). 1.3.1.4 Expansion I/O Board This board adds sixteen buffered inputs and sixteen buffered outputs to the controller. 1.3.1.5 SDE/SA Board This board allows speed discrimination or speed assessment to be applied to up to sixteen assessors(sixteen loop pairs). 1.3.2 Customisation The software for the T400 consists of an operating system which is identical in every controller, plus data to configure the operation of the controller for the specific application. The configuration PROM is prepared by means of a system consisting of a desk-top microcomputer. The data is composed using question and answer techniques in traffic engineering terms, which require no specific knowledge of the Intel 80188 programming language. The output of the system is data for the configuration PROM, a print-out of the controller’s specification and functional performance, together with detail necessary for its installation. The system is also used to prepare the conflict PROM for the conflict monitor system and therefore allows controllers to be configured quickly and easily. 667/HB/20200/000 Page 1-9 Issue 10 Type 400 Controller General Handbook 1.4 CONSTRUCTION The T400 is available in two sizes of outercase. In addition, the T400 is available in two ‘user outercases’ as specified by the Traffic Signals User Group (TSUG). The T400US and T400UL are described in the ‘T400U General Handbook’ (667/HB/26900/000). 1.4.1 Small Outercase See section 6 for layout details of the controller. The small outercase is of robust construction and is intended to be ground mounted. It has a door at the front only, access being obtained by means of screwlocks at the top and bottom, and a key operated camlock in the middle. All three fixings are on the left hand side. A panel on the right hand side holds the Master switch, Master fuse, Maintenance socket, R.C.D. and Maintenance socket fuse. A sub chassis on the left hand side holds the power input and circuit breakers at the bottom, the power supply and filtering, with the main processor and phase driver boards at the top. The printed circuit boards are vertically mounted in a small rack module. Detectors and other ancillary equipment can be accommodated to the right of this chassis. 4 Terminal block positions are provided on the sub-chassis, with additional space available on the rear and right hand side walls. Fore and aft castellated rails are provided for termination of armoured cables. A manual panel can be fitted behind a lockable cover on the right hand side of the cabinet. See section 2 for details of the outercase. 1.4.2 Large Outercase See section 6 for layout detail of the controller. The large outercase is of robust construction and is intended to be ground mounted. It has front and rear doors each secured with screwlocks and a key operated camlock. A panel on the right hand side holds the Master switch, Master fuse, Maintenance socket, R.C.D. and Maintenance socket fuse. 667/HB/20200/000 Page 1-10 Issue 10 Type 400 Controller General Handbook A panel in the base houses the circuit breakers, filter and power supply. Terminal blocks are mounted at the rear of this panel, with an optional panel being available for expansion should this be required. Castellated rails are provided for termination of armoured cables. Above is one or more PCB Rack modules logic rack which accommodate the main processor board and phase driver board(s) together with boards providing additional operating facilities. A manual panel can be fitted behind a lockable cover on the right hand side of the cabinet. The remaining space above the rack module is available for the accommodation of ancillary equipment (Detectors, OTU, OMU etc.) See section 2 for details of the outercase. 667/HB/20200/000 Page 1-11 Issue 10 Type 400 Controller General Handbook 1.5 SAFETY 1.5.1 Controller System Checks The Type 400 controller performs a number of tests/checks both in software and hardware to ensure system integrity and safety. During these checks the microprocessor and/or system hardware will switch the signals off if any fundamental test fails. The processor will also inhibit the re-triggering of the hardware watchdog timer which, when it expires, will reinforce the signals-off state. An entry will also be made in the Fault Log and the System Error LED will be illuminated. There are some failures of a non-catastrophic nature which may occur (i.e. battery supported data corrupted), in which case the microprocessor will reload the old data from configuration PROM, indicate the failure with the system error LED and fault log, and continue to function. Tests are performed in the following areas: i) Basic power up tests ii) Green correspondence iii) Conflict PROM iv) Configuration PROM v) T400 Firmware vi) Battery supported memory vii) Correct operation of system software viii) SDE/SA PCB functioning properly ix) Red lamp monitoring 667/HB/20200/000 Page 1-12 Issue 10 Type 400 Controller General Handbook 1.5.2 Power up Checks When power is applied to a T400 controller, basic system checks are performed before the traffic signals are illuminated. These are: i) RAM test ii) CRC check of system firmware (program errors) iii) CRC check of configuration data (configuration errors) iv) CRC check of battery supported timings v) Real-time Clock Note: CRC (cyclic redundancy check) coding is a very powerful error checking technique employed in computer communication systems. 1.5.2.1 RAM Test A non-destructive read/write test is performed on the battery supported memory to ensure that all RAM is working. If this test fails the fault is logged (if possible), the microprocessor halts, the watchdog will not be re-triggered, and the signals will not be switched on. 1.5.2.2 System Firmware Test The system PROM is checked against its respective CRC digits to ensure that the program data is still intact. If the test fails the fault is logged, the watchdog is not re-triggered, and the signals will not be switched on. 1.5.2.3 Configuration PROM Test The configuration PROM is checked against its own individual CRC digit to ensure data validity. If the test fails the fault is logged, the watchdog is not retriggered, and the signals will not be switched on. 1.5.2.4 Battery Timing Test The battery supported timings are checked using the CRC digits for each area protected. If that test fails then the error is logged, old timing reloaded from configuration PROM, and a comparison made between battery memory of configuration PROM. If still faulty, the watchdog is not re-triggered and signals are not switched on. 1.5.2.5 Real-Time Clock The Real-time Clock (i.e. duration of power failure) is checked to ensure that it has not exceeded the limit value specified in the configuration. If the test fails the error is logged and the master time clock system is disabled (i.e. CLF and timeswitch facilities will not be available). 667/HB/20200/000 Page 1-13 Issue 10 Type 400 Controller General Handbook 1.5.2.6 I/O Expansion Tests The configured number of I/O Expansion boards is tested to ensure that they are present. 1.5.2.7 Phase Driver Tests The Phase Driver cards are tested to ensure there is the correct number present and that they are in the correct position. 1.5.3 Green Correspondence Tests During normal operation of the T400 traffic controller, a number of system tests are continuously performed on the state of the signal greens. The controller employs two independent green monitor systems, one based in Software and the other based in Hardware. 1.5.3.1 Software The microprocessor updates the signal lamps status information every 20mS and during this time it also reads the state of the green signals as seen by the green monitor circuit. If there is a mismatch between the state of the greens output and the state read back, the processor will perform a number of retests, and if the error is persistent it will be logged, indicating which green(s) was at fault, and the signal will be switched off. Also during this time a number of tests are performed on the Independent Hardware Monitor system to ensure that the data stored in the conflict EPROM matches that stored in the configuration EPROM, and that the green comparator circuit and signal lamp supply relay driver is still functioning properly. 1.5.3.2 Hardware Green Conflict System The independent hardware green conflict monitor system comprises: i) Dual green voltage detectors, the outputs of which are compared to ensure that they are still functioning. ii) Green conflict monitor PROM which stores all the permitted and nonpermitted signal combinations. Should a conflict occur, the output of the PROM monitor, which is also monitored by the software, is passed through a delay network and then removes the drive to the signal lamp supply relays. Under normal circumstances, the software will remove power from the signal lamps before the hardware does, thus providing a duplicate system. 667/HB/20200/000 Page 1-14 Issue 10 Type 400 Controller General Handbook Should the hardware system detect an error and switch the signals off, a signal is returned to the microprocessor which also reinforces the signals off condition. 1.5.4 System Background Test During any spare time the microprocessor continuously tests the following areas: i) CRC check of system firmware (program errors) ii) CRC check of configuration PROMs iii) CRC check of battery supported timings iv) Software watchdogs for both the main system, the SDE/SA and the integral OTU/LMU processors. 1.5.4.1 Check of System Firmware The test described in Section 1.5.2(1.5.2.2) is repeated. 1.5.4.2 Check of Configuration PROM The test described in Section 1.5.2(1.5.2.3) is repeated. 1.5.4.3 Check of Battery Support The check of the battery support of timing data is divided into two areas: i) ii) Battery supported phase timings, etc. Battery supported time switch settings and CLF timings. A failure of a test in the i) area will be logged, the original timing information will be copied from the configuration EPROM into the RAM, and a comparison made. If the memory is still faulty, the watchdog will not be retriggered, and the signal will be retriggered and the controller will work to the original configured timings. A failure of a test in the second area will be logged, the old timing information will be restored and checked as above, but if an error still occurs, the master time clock system will be disabled, otherwise the master time clock system and CLF functions will work to the original configured data. On a pelican controller if either of the above checks fail then it will be logged and all lamps are switched off. Manual intervention (i.e. RFL=1) and power OFF/ON is required to restore normal operation (i.e. to restore the lamps to ON) 667/HB/20200/000 Page 1-15 Issue 10 Type 400 Controller General Handbook 1.5.4.4 Software Watchdogs The system also incorporates an internal software watchdog which checks that the following operations are being performed: i) ii) iii) iv) The main 200mS scheduler is running the correct number of modules. The 20mS scheduler is running the correct number of modules. Memory checks are still being performed. Continued operation of the SDE/SA processor. If any failure is detected, the hardware watchdog re-trigger is inhibited. 1.5.5 Operation of the Safety System To prevent the possibility of a hazardous signal condition being displayed, the supply to the signals is switched off when any of the following conditions occur: - The green conflict monitor detects a green conflict condition present on the signal drive outputs which connect to the green lamps. - The microprocessor performs a green conflict test on the green conflict monitoring system and does not receive back from the system the response that is expected. - The hardware comparator on the green monitor circuit sees a discrepancy between the outputs from the dual monitoring channels. - The microprocessor performs a test on the hardware comparator and does not receive back the response that is expected. - The microprocessor monitors the state of the green signal feeds via the green monitor circuit, and non correspondence is detected between these and the green states that the microprocessor has previously requested. - The watchdog facility detects that the microcomputer processing operations have deviated from normal. The green conflict monitor system monitors the mains voltage feeds that supply the green signals. The monitor consists of two independent channels, one channel monitors the positive mains half cycles of the green feeds and the other monitors the negative half cycles of the same feeds. The opto isolated outputs from these two independent channels connect to the green monitor circuit on the Main Processor Card. A hardware comparator on this card compares the two channels which should be the same. The output from this comparator, together with the negative half cycle channel signals, are fed to the microprocessor. The microprocessor can 667/HB/20200/000 Page 1-16 Issue 10 Type 400 Controller General Handbook disconnect the negative half cycle channel input from the green voltage detector circuit and apply its own signals instead. In this way it can test the green conflict monitor system and test the hardware comparator. The microprocessor can also monitor the state of the green signal feeds via the opto isolated inputs. The Main Processor card holds the conflict PROM which produces a nonconflicting output only provided a non-conflicting pattern of greens is indicated by the negative half cycle channel signals. The output of this PROM together with the output from the hardware comparator are fed via a delay to the contactor drive circuits. This controls the relays A and B which supply the mains power to the phase drivers. A watchdog trip occurs if the microcomputer fails to trigger the watchdog circuit within nominally 500mS. To trigger the watchdog the microcomputer has to write to two particular addresses correctly within 8us of each other. This normally happens every 200mS. The trip operation removes the drive signal from lamp supply contactors which in turn removes the supply to the lamps. 1.5.6 Red Lamp Monitoring To prevent the possibility of a hazardous signal condition being displayed, the following checks are made on the vehicle red lamps. On a intersection with audible or tactile pedestrian indications, the controller, using an ancillary processor card (see section 6.4.8), monitors the current following through the conflicting vehicle phases’ red lamps. If two or more lamps fail on the same phase, then the conflicting pedestrian phases are inhibited from appearing. On a part-time intersection, all the vehicle red lamps are monitored by the ancillary processor card. If two or more lamps fail on the same phase, then all the controller lamps are switched off. On a mid-block controller (e.g. pelican), each vehicle approach is monitored by the hardware of the 2-phase phase driver board (see section 1.3.1). If any monitored approach has no vehicle red lamps illuminated, then all the lamps are switched off. 667/HB/20200/000 Page 1-17 Issue 10 Type 400 Controller General Handbook 2. SPECIFICATION 2.1 MAINS SUPPLY The following table shows the supply voltages which may be used: Nominal Voltage 240 230 * 220 * 200 120 110 Minimum Voltage 192 192 188 170 96 96 Maximum Voltage 264 264 252 229 132 132 Peak Voltage 276 276 264 240 The peak voltage levels shown in the above table have a half hour rating. (* - The auto-transformer facility is required for these voltages.) It is recommended that the signals are supplied at the nominal mains voltage during bright. i.e. For a 200 volt nominal supply, use 200 volt transformer/bulbs. (See Appendix D for details of Tuen Mun requirements). PROSPECTIVE SHORT CIRCUIT CURRENT OF THE SUPPLY MUST NOT EXCEED 16,000 AMPS. Frequency: 50Hz ±2Hz or 60Hz ±2Hz (factory selectable) Mains Brownout: Continues operating with up to 50mS loss of mains. Mains Fail: Restart without operator intervention. Battery Support: Provides support for the following during power failures. (a) Clock Synchronisation (programmable upto 31 days). (b) Timing Data (greater than one year). Dimming Voltage: 120, 140, 160 V rms Solar Cell Input: Dimming cannot be provided at low mains supply voltages, e.g. 120v or less, as solar input operating voltages are as follows:Bright to Dim > 140v RMS Dim to Bright < 22v RMS Note: Dimming is available on 50-0-50 volt controllers. The Type 400 controller solar cell enables the controller to identify the light level and thus dim the signals when it is dark. The switch is set to operate at 55 lux and release at 110 lux. The voltage range for the device is 240v ± 20%. 667/HB/20200/000 Page 2-1 Issue 10 Type 400 Controller General Handbook 2.1.1 Electrical Noise 2.1.1.1 Supply Transients The T400 can withstand the following transients on its supply as required in MCE 0141. ±100% Supply R.M.S. voltage for 10mS ±200% Supply R.M.S. voltage for 1mS ±300% Supply R.M.S. voltage for 0.02mS ±500% Supply R.M.S. voltage for 0.005mS 2.1.1.2 Electrical Interference The T400 Controller has been designed to create very little electrical interference by the use of mains filters and solid state lamp switching control. The mains filters protect the incoming mains supply from any T400 generated signals. The lamp switches are switched at zero cross-over of the mains supply to reduce any switching transients. The switching of the signals for dim/bright lamps changeover is controlled carefully to ensure the inductive switching does not cause interference. The T400 controller design is also extremely tolerant of externally generated electrical interference. Care is taken to avoid earth loops using a ‘Star’ point earthing system to which the cabinet, the cabinet doors, the internal metalwork, the junction cabling and the mains earth is connected. Extra logic supply filtering is provided by the switched mode power unit. The arrangement and partitioning of the controller equipment is carefully arranged to reduce electrical noise. The PCBs have a gridded zero voltage track layout with extensive decoupling of logic supplies. Unused inputs are connected to the logic supplies to ensure their logic state. The phase switching system has isolation provided by opto-SCR’s and zero crossing switched triacs for the mains switching. The circuit includes a snubber filter circuit which aids triac switch off when an inductive circuit is connected. 667/HB/20200/000 Page 2-2 Issue 10 Type 400 Controller General Handbook 2.2 DETERMINATION OF LOADING, SELECTION OF DIMMING TRANSFORMER & LAMP FUSE This section describes the method used to determine that the controller can supply the total lamp load required, how to select the correct dimming transformer and lamp fuse and how to determine the overall power used for estimation of site running costs. 2.2.1 Controller Load Typical supply requirement for a controller including dimming transformer (excluding lamp loads, detectors and O.T.U) is: - 75 watts - Siemens St. or Microsense detectors require 6 watts per unit and the Sarasota MTS36Z (2 channel) or MTS38Z (4 channel) detectors require 3 watts per unit. (NB The power consumption is the same for both 2 and 4 channel units.) 2.2.2 Lamp Drive Capability Amps 20A Max Power (Watts) 4800W No. of Tungsten Halogen HI Lamps (63W) 76 Maximum lamp load for one phase driver card (including red/amber) 10A 2400W 37 Maximum load for one triac output on a phase driver card 4A 960W 15 Maximum supply for regulatory signs (76 volt-amps per sign) 5A 1200W 15 Reg. Signs Maximum lamp current that the controller can supply including regulatory signs and short term illumination, i.e. red/amber. Note 1: The 5 Amp Regulatory Signs supply may be extended to a 10 Amp supply using the Mod kit 667/1/20699/000. (Note that total controller supply is still limited to 20 Amps and that a 45A Master switch fuse must be fitted). Note2: The regulatory signs supply on a T400L can also be extended without reduction in Lamp drive capability by means of an Excess Current Regulatory Signs Mod Kit (667/1/20699/001). This 667/HB/20200/000 Page 2-3 Issue 10 Type 400 Controller General Handbook involves separating the Live and Neutral feeds to the Regulatory signs from the signal feeds. This will allow for up to 10A (unfiltered) for the Regulatory signs and up to 20A for the signal lamps. Note 3: The Lamp and Wattage columns are equivalents for the currents shown, based on a 240 volts supply. Note 4: If the lamp load is 13A up to 20A then a 45A Master Switch kit, 667/1/20246/000, must be used. 2.2.3 Selection of Dimming Transformer Calculate the Total average signal lamp power as follows and using the figures in Table . Total average signal Lamp Power is the sum of the signal lamp power plus the sum of the Wait indicator power. For the theoretical junction (Figure 2.2) this would be:One lamp per signal head @ 63W x 12 signal heads Wait indicators at 40W x 4 Total average signal lamp power = = = 756W 160W 916W Note: When selecting the dimming transformer the peak lamp power is not used as the transformer can withstand the overload for the 2 second Red / Amber period. Table 2.2.3(a) Lamp Load Per Aspect (Watts) Tungsten filament 65 watt WAIT Indicator 40 watt WAIT Indicator 50 watt High Intensity 100 watt High Intensity Regulatory sign (wattage) (Use this for estimation of power consumption) Regulatory sign (Volt-Amps) (Use this for calculation of current) Bright 65 65 42 63 120 30 Dim 160V 53 53 25 33 60 - Dim 140V 27 - Dim 120V 35 35 1 20 40 - 76 - - - Note that the values given in the above table relate to the average lamp power plus power losses involved in driving the lamp. Now using Table choose which dimming transformer is required for the dimming voltage required. 667/HB/20200/000 Page 2-4 Issue 10 Type 400 Controller General Handbook For the theoretical junction, using the figure obtained above (916W) and 160V dimming the transformer required would be the 1kVA version. (Note that in this case the same transformer would be chosen regardless of the Dimming voltage required.) Table 2.2.3(b) Selection of Dimming Transformer. Dimming Voltage 120v 140v 160v Max. Lamp Power @ 240v Dimming Transformer load < 2830W 2830W < load < 4090W 4090W < load < 4560W load < 2260W 2260W < load < 3400W 3400W < load < 4560W load < 2000W 2000W < load < 2800W 2800W < load < 3960W 1.0 kVA 1.5 kVA 2.0 kVA 1.0 kVA 1.5 kVA 2.0 kVA 1.0 kVA 1.5 kVA 2.0 kVA Max. Number Of lamps Illuminated Continuously 49 73 98 Note 1 40 59 78 Note 1 35 50 66 Notes:1. The absolute maximum number of lamps supported in these cases is limited by the Lamp fuse in Bright condition. This also applies to short time illumination e.g. Red / Amber periods. See also section 2.2.2. 2. All lamps are assumed to be tungsten halogen (63W bright). See table 2.2.3(a) for ratings at dimmed voltages. 2.2.4 Calculating The Lamp Supply Fuse Required In order to calculate the lamp supply fuse required the worst case red/amber is used, i.e. the red/amber during which the most signal heads are at red/amber. For the theoretical junction (Figure 2.2) this is during the move 2 to 1 with 5 signal heads at red/amber. The lamp power is then re-calculated using 126 Watts for every signal head at red/amber (assuming 63W lamp power). This gives us the peak lamp power e.g. for our theoretical junction Figure 2.2. Signal heads at red/amber x 126 watts Signal head with 1 lamp illuminated x 63 watts Every WAIT indicator illuminated x 40 watts 5 x 126 7 x 63 4 x 40 = = = 630W 441W 160W 1231W This is divided by 240 volts to give us the peak lamp current: i.e. 1231/240 = 5.2 Amps. 667/HB/20200/000 Page 2-5 Issue 10 Type 400 Controller General Handbook Then from the following table we derive our HRC fuse and hence the Master switch fuse:Table 2.2.4 HRC and Master Switch Fuse Selection Peak Lamp Current Up to 7A 7A to 10A 10A to 13A 13A to 15A 15A to 20A H.R.C. Fuse 20ET 25ET 40ET 40ET 55ET Master Switch Fuse 30A 30A 30A 45A 45A For the theoretical junction this would lead to a choice of a 20ET HRC fuse and a 30A fuse in the Master Switch. Note 1 The Regulatory Signs do not have any impact on the selection of the HRC fuse. Note 2 If 15A to 20A lamp load and up to 10A of Regulatory signs is required then the excess Regulatory signs current kit is required as Note 2. Note 3 The xxET type fuses are selected for their high current fast blowing characteristic. This provides protection for the phase drive triacs. Note 4 The numbers associated with ET fuses do not indicate the fuse rating. e.g. A 20ET fuse is not for 20A loads. 667/HB/20200/000 Page 2-6 Issue 10 Type 400 Controller General Handbook 2.2.5 Calculation Of An Intersection’s Power Requirements For Running Costs Estimate The following worked example is based upon a 240 volts mains supply. Firstly the Total average lamp power for the junction is calculated. Secondly the Total average lamp power is added to the Total average controller power: This gives the total average junction power which a local authority may use to estimate running costs. i.e. Total average junction power = Total average lamp power + Total average controller power. Total average lamp power is calculated as follows:For every signal head, 1 lamp is illuminated at 63 watts, every WAIT indicator is illuminated at 40 watts and every Regulatory sign is illuminated at 30W. Therefore, considering our theoretical junction (Figure 2.2), we have:1 lamp per signal head at 63 watts Every wait indicator illuminated at 40 watts One Regulatory Sign at 30W. 63 x 12 40 x 4 30 x 1 Total average Lamp Power is 756Watts 160Watts 30Watts 946 Watts Total average controller power is calculated as follows:Average Controller power + Average Detector Power. See section 2.2.1. A controller with dimming is rated at 75 watts. Detector cards are rated at 6 watts/card for every Siemens ST detector. Therefore for our theoretical junction (Figure 2.2) the total average controller power is:1 x Controller 1 x Siemens ST detector 75 Watts 6 Watts Total average controller power 81 Watts 667/HB/20200/000 Page 2-7 Issue 10 Type 400 Controller General Handbook For the total average junction power to aid local authorities with running cost estimates, the total average lamp power must be added to the controller average power. Total average Junction power is calculated as follows:Total average lamp power Controller power Total average Junction Power 946 Watts 81 Watts 1027 Watts If it required to make an estimate of running costs which include the period of time that the signals are dimmed this can be approximated as follows:Total average Junction Power (Dimmed) is :Total average Signal Power * (Dimmed Voltage / Nominal Mains voltage) plus Total Regulatory signs power plus Total average Controller Power. Therefore for the theoretical junction :Total average Junction Power (Dimmed) = (160v/240v)x(946W-30W) +81W +30W = 722 Watts Note 1 The power used by the regulatory signs for estimation of running costs is approximately 30W. For fusing purposes the regulatory signs are rated at 76 VA due to the inductive nature of the load they present to the supply. Ensure that the 76VA figure is used when assessing whether to use a 5A or 10A fuse. Note 2 The controller power should also include any additional equipment supplied by the controller. This may include, for example, OTU, OMU or Auxiliary detector power supply. 667/HB/20200/000 Page 2-8 Issue 10 Type 400 Controller General Handbook Figure 2.2 - Theoretical Junction C C D D A B E E NRT C A A STAGE 1 STAGE 2 B STAGE 3 C D A E B 667/HB/20200/000 Page 2-9 Issue 10 Type 400 Controller General Handbook 2.2.6 Regulated Logic Supplies +5v (± 5%) @ 5 Amps with over-voltage and over-current protection. +12v (± 10%) @ 0.1 Amps with over-current protection. -12v (± 10%) @ 0.1 Amps with over-current protection. 2.2.7 Regulated Interface & Detector Supplies (a) The logic PSU also provides a 24v supply to the power interface circuits for the controller together with some spare capacity for powering detector cards. +24v (± 10%) @ 2 Amps with over-current protection. The spare capacity is between 1.1 and 1.7 Amps dependent on the number of I/O and SDE cards fitted; see the T400 Facilities Manual (667/EB/20200/000) for details. (b) If the power provided by the 24v logic supply is insufficient, an additional power supply may be used to supply power to internal or external detection equipment. Two versions of this supply are available. +27.5v (± 4%) @ 2 Amps or 4 Amps. This supply voltage has been specified to overcome the voltage drop on feeders and to remove the need for supply regulation at remotely situated detection equipment. NOTE Facilities exist for separately powering detectors. Refer to Above Ground Detectors Handbook, 667/HE/20665/000). 667/HB/20200/000 Page 2-10 Issue 10 Type 400 Controller General Handbook 2.2.8 Audible Supplies The Audible power supplies on the T400 are designed to provide a dc voltage between 10 and 24 volts, and typically provide 50mA at 18v dc. Audible and tactile units used must operate correctly over the voltage range 10 to 24 volts dc. Audible units recommended and supplied by STCL which meet this requirement are; Sonalert Malary SC628P, Highland Electronics type SC628P and Roxborough type SPCI535A4 Audibles:- Tactiles:- 667/HB/20200/000 667/4/04785/000 Highland Electronics type SC628P (was Sonalert Malary SC628P), and Roxborough type SPCI535A4 667/7/17390/000 PELICAN currently Radix RS250 or RS252 667/7/17390/001 INTERSECTION currently Radix RS251 or RS252 Page 2-11 Issue 10 Type 400 Controller General Handbook 2.3 FUSE RATINGS Electricity Board Cut-out - Dependent on lamp load, see below. FS1 Master Switch Fuse - Dependent on lamp load, see below. FS2 Maint’ce Socket Fuse - 5Amp HRC cartridge fuse to BS1361 FS3 OTU/OMU Supply Fuse* - 5Amp HRC cartridge fuse to BS1361 FS4 Optional Supply Fuse* - 5Amp HRC cartridge fuse to BS1361 FS5 Reserved for future use - FS6 Reserved for future use - FS7 Lamp Supply Fuse - Dependent on lamp load, see below. FS8 Controller Switch Fuse - 30Amp HRC cartridge fuse to BS1361 FS9 Reg Signs & Solar Cell - 5Amp HRC cartridge fuse to BS1361 FS10 Switched Signs Supply - 5Amp HRC cartridge fuse to BS1361 FS11 Alt. Reg. Sign Supply (heavy current controller) - 5Amp HRC cartridge fuse to BS1361 Logic PSU Mains Input Fuse - Farnell P.S. 3Amp A.T.(1¼x¼) Ceramic - OR, Weir 4Amp A.T. fastblow HRC Detector PSU Mains Input Fuse* - 2Amp Hitron - No fuse - 4Amp Hitron - 2.5Amp (20x5mm) Delay Fail Flasher Fuse - 20Amp HRC cartridge fuse to BS1361 Phase Driver Fuse - 10Amp QB (518/4/97020/120) * If required: Lamp Load 2A Hinchley 2Amp (20x5mm) Anti-surge 4A Hinchley 4Amp (20x5mm) Anti-surge Electricity Board Cut-out FS1 Master Switch Fuse FS7 Lamp Supply Fuse † Up to 7A 25Amp fuse 15A HRC fuse 20ET - 518/4/90287/003 7A to 10A 30Amp fuse 30A HRC fuse 25ET - 518/4/90287/004 10A to 13A 30Amp fuse 30A HRC fuse 40ET - 518/4/90287/005 13A to 15A 45Amp fuse 45A HRC fuse 40ET - 518/4/90287/005 15A to 20A 45Amp fuse 45A HRC fuse 55ET - 518/4/90287/006 † ( Low current controller requiring 15A Mod Kit 667/1/20246/001) HRC fuse 5Amp 518/4/90638/yyy /000 667/HB/20200/000 15Amp /003 20Amp /004 Page 2-12 30Amp /005 45Amp 518/4/90637/003 Issue 10 Type 400 Controller General Handbook 2.4 PHASES Maximum number of software phases for small T400 Controller = 16 Maximum number of software phases for large T400 Controller = 16 Maximum number of hardware phases for small T400 Controller = 8 Maximum number of hardware phases for large T400 Controller = 16 Maximum number of hardware plus software phases = 16 2.5 STAGES Maximum of 16 (Note:- Stage 0 is normally ALL RED) 2.6 TIMINGS All controller timings are stored in EPROM at configuration time. These timings are subsequently transferred to battery supported RAM. Once in RAM most timings can be varied by handset commands (see section 7). However, should the total power failure time be long enough to drain the battery supporting the RAM and cause loss of data, (i.e. typically four years), the controller will revert to the original timings in EPROM. Some timings considered to be safety timings cannot be changed by handset, these are typically the Amber and Red/Amber periods. These timings can, however, be changed at configuration time to suit other signal sequences, export requirements etc. Following is a summary of some of the timings available within the Type 400 controller. It also shows their upper and lower limit values and where applicable the configurable limits. All timings are in seconds unless otherwise marked. Tolerance All timings, except CLF and Master Time Clock, are derived from the crystal frequency which has a tolerance of 35 parts per million. An additional error, due to random signals not being synchronised to the clock pulse, may add up to 200mSec to the time. If the result of the above timings is required to change the signal lamps, a further error may occur, which may be up to a max. of 21 mSec. The set-up accuracy of the real time clock and offsets calculated from it will be 1 sec. The average long term drift will be 1 sec. per year or better, subject to the quality of the mains supply. 667/HB/20200/000 Page 2-13 Issue 10 Type 400 Controller General Handbook Lower Limit (sec) Upper Limit (sec) Resol’n (sec) Config’ble Lower Limit Config’ble Upper Limit Minimum green 0 255 1 per phase per phase Maximum green (4 sets) 0 255 1 per phase per phase 0.0 31.8 0.2 1 value 1 value Conflicting phase change intergreen 0 199 1 per change (256) 1 value Starting intergreen 0 255 1 1 value 1 value All red extension 0 31.8 0.2 - - All red maximum 0 255 1 - - Phase delay 0 255 1 1 value 1 value Pedestrian blackout/ Flashing Green Man 0 255 1 1 value 1 value Pedestrian window 0 255 1 - - Hurry call delay 0 255 1 1 value 1 value Hurry call hold 0 255 1 1 value 1 value Prevent hurry call 0 255 1 1 value 1 value Hurry call watchdog 0 500 2 - - Hurry call request watchdog 0 255 1 - - Call delay period 0 255 1 - - Cancel delay period 0 255 1 - - 255 1 - 1 value General Timing Period Green extension Hurry Call Timing Period Detector Timing Period D.F.M. * † * 0 † Active DFM times are specified in minutes and inactive DFM times are specified in hours. The value zero gives a one minute D.F.M. time for test purposes. 667/HB/20200/000 Page 2-14 Issue 10 Type 400 Controller General Handbook Lower Limit (sec) Upper Limit (sec) Resol’n (sec) Config’ble Lower Limit Config’ble Upper Limit Linked pedestrian controller release (conditioning timer) 0 255 1 - - C.L.F. group time‡ 0 255 1 1 value 1 value C.L.F. offsets 0 255 1 - - Monitor time 0 2550 10 - - Emergency gap 0 255 1 - - Priority extension (4 sets) 0 255 0.2 - - Priority maximum (4 sets) 0 255 1 - - Priority inhibit (4 sets) 0 255 1 - - Phase compensation (4 sets) 0 255 1 - - Priority 1st delay time 0 255 1 1 value 1 value Priority 2nd delay time 0 255 1 1 value 1 value 0 55 1 - - Amber leaving 3 - - - - Red/Amber 2 - - - - Fixed Vehicle Period 20 60 1 1 value 1 value Pelican all-red time 1 3 1 1 value 1 value Vehicle Green Min. time 6 15 1 1 value 1 value Vehicle Extension time 0 4 1 1 value 1 value Vehicle Green Max. time 10 60 1 1 value 1 value Linking Timing Period Priority Timing Period Speed Discrimination Period SDE/SA extra clearance Fixed Timing Period§ Pelican/Pedestrian Timings ‡ § Cycle length equals the sum of all group times in a plan. These are timings not alterable by the handset and are fixed in the configuration PROM. 667/HB/20200/000 Page 2-15 Issue 10 Type 400 Controller General Handbook Lower Limit (sec) Upper Limit (sec) Resol’n (sec) Config’ble Lower Limit Config’ble Upper Limit Pedestrian Green time 4 9 1 1 value 1 value Intergreen step 0 - red & fl/grn 0 2 1 1 value 1 value Intergreen step 1 - fl/amb & fl/grn 6 18 1 1 value 1 value Intergreen step 2 - fl/amb & red 1 2 1 1 value 1 value Pedestrian Green time 3 15 1 1 value 1 value Intergreen step 0 - red & blackout 5 15 1 1 value 1 value Intergreen step 1 - red & red/man 1 8 1 1 value 1 value MCE0125Timings MCE0145Timings 667/HB/20200/000 Page 2-16 Issue 10 Type 400 Controller General Handbook 2.7 MASTER TIME CLOCK & CABLELESS LINK FACILITY SUMMARY Master Time Clock • Timing Sources - Mains 50Hz (60Hz Wire link and configuration). • Standby Timing - On board crystal and battery support programmable up to 31 days. Accuracy of standby crystal oscillator is 35 PPM • Programmable changeover to mains synchronisation. • Facility for synchronising the real time clock or group timer from existing UTC • Number of time switch settings - 64 • Number of time switch functions - 3 (a) Isolate controller (b) Introduce a CLF plan (c) Introduce a set of events (11 types of event) (16 sets of combinations of events) Cableless Link Facility Number of plans 8 Number of plan influence tables per stream 8 Number of groups per plan 16 Number of group influences 10 types 2.8 MODES OF OPERATION • Vehicle actuated (SDE/SA can be added to V.A) • Timetable selected fixed time plans either cableless linked or in isolation. • Central computer controlled in a traffic control system. • Fixed time • Hurry call • Manual • Parallel stage streaming • Priority • Part time OFF/ON • Part time Flash/Normal operation. • Pelican VA • Pelican Fixed Time 2.9 OUTERCASE 667/HB/20200/000 Page 2-17 Issue 10 Type 400 Controller General Handbook SMALL LARGE Height (above ground level) 1170mm 1400mm Width 465mm 660mm Depth 370mm 490mm Weight of bare outercase 32Kg 42kg Assembled controller only (Including Outercase) 71Kg 90Kg Both cases are manufactured in aluminium and finished with grey epoxy or acrylic paint. In addition to the screwlocks, the main controller doors are fitted with one S18 lock per each. The key lock must not be operated unless the screw locks are tight. ie. Unlock the door before undoing the screwlocks and only lock the door after tightening the screw locks. The lock used on the police manual panel is a small Yale lock with a 900 pattern barrel. There is a facility to change the S18 lock to a Yale with an RKA27C pattern barrel. 2.10 ENVIRONMENTAL 2.10.1 Temperature The T400 in a grey outercase is designed to operate in external ambient temperatures of -15ºC to +60ºC. A white tropical outercase may be supplied when requested by a customer, but this does not provide any benefit with regard to solar radiation. Use in countries where high levels of and long periods of, solar radiation are expected, may impose restrictions on T400 hardware configuration. Contact Engineering at Poole for more details on hardware restrictions. 2.10.2 Atmospheric The controller is proofed against driving rain and sand, dust conditions and industrial pollution. 2.10.3 Humidity The equipment will withstand a temperature of 35°C with a relative humidity of 95%. 2.11 HANDSET INTERFACE (RS232 PORT) Type 667/HB/20200/000 Page 2-18 Issue 10 Type 400 Controller General Handbook RS232C CCITT V24 and V28 Method of Connection Controller Terminal Device - Cannon DP 25-way socket connector Cannon DP 25-way plug connector Pin Allocation Pin 1 Pin 2 Pin 3 Pin 4 Pin 5 Pin 6 Pin 7 Pin 8 Pin 9 Pin 10 Pin 18 Pin 19 Pin 20 } } } } - Protective ground Transmit data from terminal to controller Received data from controller to terminal Request to send Clear to send Data set ready Signal ground Rx Signal detect (reserved) 5V supply (controller 5 volt logic/user supply) Ground supply Data terminal ready Bit Format START (SINGLE BIT) 1 (LSB 2 • 3 • 4 • 5 • 6 • 7 MSB) PARITY (EVEN) STOP (SINGLE BIT) Baud Rate 1200 Bd Mode Full duplex Character Set ISO Alphabet No. 5 (ASCII) 667/HB/20200/000 Page 2-19 Issue 10 Type 400 Controller General Handbook 3. TRAFFIC FACILITIES The following list of controller functions and facilities is a brief overview of the capabilities of the T400 Controller. Each heading is an extract from handbook 667/EB/20200/000 where further details on each subject can be found. At the back of this section, a copy of our specification sheets are included which, will indicate the data required to configure these facilities. 3.1 STAGES 3.1.1 Stage Facilities 16 stages (0-15) Stage 0 - all red Stage 1 - Normally start up stage (which cannot be deleted) 3.1.2 Allocation Of Phases Phases are allocated to stages. However each phase in a stage runs independently and therefore the timings of a stage depend upon the interaction of the phase timings within that stage. 3.1.3 Stage Active A stage is considered active when:All fixed phases allocated to the stage are at green and all fixed and non fixed phases not allocated to the stage are at red. 3.1.4 Stage Terminating A stage is considered to be terminating when:The first phase which has had R.O.W, (i.e. been at green) during the stage, loses right of way. 3.1.5 Inter Stage Period The interstage period is the time between one stage terminating and another stage becoming active. 3.1.6 Stage Movement Restrictions Ignore moves:- The controller can be configured to ignore certain possible moves from a stage, and so will look for other acceptable moves. Prohibited moves:- The controller can be configured such that it will never make certain stage to stage moves. 667/HB/20200/000 Page 3-1 Issue 10 Type 400 Controller General Handbook Care must be taken when deciding to use prohibited moves, to ensure that a “lock up” situation cannot occur. Alternative moves:- Alternative moves can be configured for those moves prohibited, thus providing an allowed movement to help prevent lock-up. Once in the alternative stage, the controller will perform its normal movement decision programme in order to decide which stage to move to next. This therefore means that this movement is not a move to a stage via an alternative stage. If a move via a stage to another stage is required other move restrictions have to be applied to the alternative stage. Permitted moves:- All stage to stage moves not configured as any of above types. 3.1.7 Prevent Stages/Phases Stages and phases can be prevented from appearing provided all safety requirements and controller cycle requirements are met. The facility can be introduced when user defined conditions are satisfied, for example by using special conditioning and/or master time clock. 3.2 PHASES 3.2.1 Types Of Phases Traffic phase Pedestrian phase Pelican vehicle phase Pelican pedestrian phase Green arrow phase:- Filter green arrows or indicative green arrows. Dummy phase Switched sign phase LRT phase - Uses a pedestrian phase with different aspect display. 3.2.2 Conflicting Phases Real phases which cannot appear together for safety reasons are considered to be conflicting and as such must have intergreen times between them. 3.2.3 Opposing Phases If two phases oppose each other then a demand for one will start the max green timer of the other phase if it is at green. 667/HB/20200/000 Page 3-2 Issue 10 Type 400 Controller General Handbook 3.2.4 Phase Delays Phases can be delayed:- (a) from losing right of way and (b) from gaining right of way. 3.2.5 Timing Periods See section 2.6 for Phase timing periods. 3.2.6 Limiting Values This is a value which can be defined during configuration for certain timings, which then ensures that the appropriate times can not be set above or below the limit value, by use of the handset. (See section 2.6). Note: Prom held values can be set lower than the limit value. These are transferred to the RAM at initialisation an the controller works to these values. The handset may only alter the times within the limits specified. If they have been altered, they cannot be set back down to the original value without the complete set of timings being loaded from prom by re-initialising the controller. 3.2.7 Conditions Of Appearance For Phases Type 0:- Always runs if the stage to which it is allocated becomes active. Type 1:- Will only appear whenever its associated stage becomes active, if a demand is inserted before the start of the preceding interstage. Type 2:- Will only appear whenever its associated stage becomes active, if a demand is inserted. No limitations on when demand is inserted. Type 3:- This is as type 2, however once a stage associated with a type 3 phase becomes active, a window timer can be started. During this window time, a demand for the phase will cause it to appear. After the expiry of the window timer, demands for the phase will be stored but not actioned. The window timer will start when its associated stage is active and there is an opposing demand, however, if the controller is in UTC mode the window timer will start as soon as its associated stage becomes active. 3.2.8 Fixed Phase Real or dummy phases with a type 0 condition of appearance. 667/HB/20200/000 Page 3-3 Issue 10 Type 400 Controller General Handbook 3.2.9 Non Fixed Phases Real or dummy phases with type 1, 2 or 3 conditions of appearance. 3.2.10 Conditions Of Termination For Phases Type 0:- Phase terminates at end of associated stage. Type 1:- Phase terminates when an associated phase gains right of way. Type 2:- Phase terminates when an associated phase loses right of way. 3.2.11 Early Termination Of Phases Available using two consecutive stages, or phase (losing) delays. 3.3 DEMANDS AND EXTENSIONS 3.3.1 Types Of Demands Latched - Demand remains until phase is served Unlatched - Demand is cleared if the demand condition ceases before phase is served. 3.3.2 Origins Of Demands And Extensions (a) On-street detection equipment (b) Pedestrian push button (c) Revertive demands (d) U.T.C demand bits (e) Demands and/or extensions can be inserted when set conditions arise (special conditioning). (f) LRT requests provided via interface from LRT interrogator. 3.3.3 Repeat Pulses Controllers when linked, can repeat demands and/or extensions between them. 667/HB/20200/000 Page 3-4 Issue 10 Type 400 Controller General Handbook 3.3.4 SDE/SA Extensions for high speed vehicles. 3.3.5 Handset Demands and extensions can be inserted for phases via the handset. 3.3.6 Operation Of Demands And Extensions During Certain Modes 3.3.6.1 Manual, Fixed Time And Start-Up While in manual mode the demands and extensions are disregarded, however when leaving this mode demands are inserted (if configured) for all non running phases. Demands and extensions are normally disregarded during fixed time mode. The controller cycles using fixed time periods for each stage. As an alternative, the fixed time facility can be configured to run to the current maximums. Using this latter facility demands are used, thus allowing demand dependence of some phases in fixed time. (Note: the controller mode will show VA mode.) Demands are inserted for all phases during start-up unless otherwise specified. 3.3.6.2 U.T.C For U.T.C it is possible to configure the following. 1. Which phases and/or stages have latched or unlatched demands inserted when a certain U.T.C demand bit is applied. 2. Which phases are extended by which U.T.C demand bits. 3. Demand dependent force bits and for each force bit which demands are to be considered. 3.3.6.3 C.L.F Mode Extensions are disregarded during C.L.F mode, except if an extension exists when a phase is terminated then a revertive demand is inserted. However it is possible to configure demand dependent moves to stages during C.L.F. This 667/HB/20200/000 Page 3-5 Issue 10 Type 400 Controller General Handbook is achieved by selecting the group influence as a demand dependent move to a stage and specifying the stage. Three alternative movements can also be specified by selecting the ‘Add demand dependent move’ group influence. 3.3.6.4 Call/Cancel There are up to 8 call/cancel units (0 to 7) available which may be used for turning movements or in conjunction with queue loops or switched facilities. The input to a unit must be active for a “call period” before the output changes to active and similarly the input must be inactive for a “cancel period” before the output changes to inactive. Where call/cancel is used to control an early cut off, there are 3 control techniques:(i) Normal system D detectors are used to call and extend the main stage and the call cancel loop is used to call and extend the turn stage. (ii) If a turn call exists then the system D detectors providing extensions for the main stage from the approach with the turn will be inhibited. Then during the turn stage the above system D detectors will also extend the turning stage. (iii) System D detectors for the main stage on the approach with the turn will extend both the main stage and the turn stage. The choice of which of the above methods of control to use depends on the relative amounts of traffic for each movement. See the facilities handbook for a fuller description. 667/HB/20200/000 Page 3-6 Issue 10 Type 400 Controller General Handbook 3.4 HIGH SPEED VEHICLE DETECTION 3.4.1 Speed Discrimination Equipment (SDE) 3.4.1.1 Double SDE - One assessment point (2 loops) per approach lane. - Extensions given for vehicles above a set speed threshold. - Extra clearance to extend an intergreen period. 3.4.1.2 Triple SDE - As double SDE except with 2 assessment points (2x2 loops) per approach lane. - The threshold speed for the inner assessment point will be different from that of the outer assessment point. 3.4.2 Speed Assessment (SA) Fixed extensions are given but the delay between a vehicle crossing an assessor and the start of the extension, varies depending upon speed of vehicle. 3.4.3 Assessors Available There are up to 16 assessors (0 to 15) available for use on SDE or SA. Each assessor may be checked with a Soundmark test set by plugging into the socket provided and selecting the assessor on the thumb wheel switch on the SDE/SA PCB. 3.4.4 Extra Clearance Periods Each phase which is equipped with SDE or SA can be allocated an extra clearance period to extend the subsequent intergreen. The extra clearance period for each phase will be introduced if any of the following conditions occur:(a) An SDE or SA extension is active for the phase during its amber leaving state. (b) Any speed measurement detector does not detect a vehicle during the associated phase green period. 667/HB/20200/000 Page 3-7 Issue 10 Type 400 Controller General Handbook (c) Optionally, any extension, (speed extension, green extension or Priority extension), is active for the phase when it changes from green to amber leaving. The condition in (c) is normally disabled for individual phases at the time of configuration. Speed extensions will still request extra clearance because of the operation of condition (a). An extra clearance period will be given under any mode of control, i.e. manual, VA, fixed time, CLF, UTC, vehicle priority or hurry call. Its effect is to increase all the inter-green timings for the phase which is being given the extra clearance, and also to increase the phase change delay times for gaining phases. If the intergreen is not dependent on the SDE/SA phase inter-green time, (because another losing phase has a longer inter-green time), then the extra clearance period may not actually delay the appearance of the gaining phase. The range of the timing period for the extra-clearance is 0 to 50 seconds in 1 second steps for each SDE/SA phase. The programmed value may be changed via the handset using the SCT command. 3.4.5 SDE/SA on Green Arrows Where these are single aspect, the red and amber drives of the Phase Switch PCB are not available to drive other green arrows, as they must be programmed as 3-aspect to get the amber signal to meet the requirement of 6.4, even though only the green arrow is connected. 3.4.6 Other Manufacturers Loops The SDE/SA facility can be configured to operate with loop spacings of 12ft instead of 10ft. 667/HB/20200/000 Page 3-8 Issue 10 Type 400 Controller General Handbook 3.5 MODES These are listed in a typical order of priority. 3.5.1 Start-Up Mode The controller will start up in a set and controlled manner to ensure the safety of the junction users. 3.5.2 Part-Time Mode The signals can be switched on or off at set times or under set conditions. 3.5.3 Urban Traffic Control The T400 controller can be linked to a central computer for remote control via an OTU etc. 3.5.4 Priority Mode The T400 can be equipped to give a rapid change to right of way for vehicles fitted with special vehicle transponders. 3.5.5 Hurry Call Mode The T400 can be configured such that on receipt of one of two special input signals, it will rapidly change to a selected stage to give special junction conditions. 3.5.6 Selected Manual Control Selecting this mode by operating a push button on the manual panel allows the policeman to control the operation of the controller manually. 3.5.7 Selected Fixed Time or VA or CLF. There are three pushbuttons on the manual panel which may be used to select:- or Fixed Time. VA CLF as the working mode. 667/HB/20200/000 Page 3-9 Issue 10 Type 400 Controller General Handbook 3.5.8 Normal Mode Selected by push button on the manual panel. The normal position allows the controller to choose its own working mode using its mode priority table and taking into account all other necessary influences. 3.5.9 Cableless Link Facility (CLF) Mode Linking two or more controllers using synchronised clocks. 3.5.10 Vehicle Actuated Mode Stage change decisions made using vehicle detection equipment. 3.5.11 Fixed Time Mode Controller cycles using fixed time periods. This is obtained by manual selection or as an alternative to VA. 3.6 MASTER TIME CLOCK A real time clock can be provided which can control all time dependent functions, e.g.:Introduction of C.L.F plans Switch to an alternative MAX set. Switch an input active or inactive. Switch an output active or inactive. Switch a sign on or off. Delete a Phase. Delete a Stage. Switch an audio indicator off. Switch to part time mode. Switch a flag readable in special conditioning. Switched DFM Plus many other functions which can be constructed using special conditioning. 3.7 LINKING The linking facilities can be used in numerous applications e.g.:- 667/HB/20200/000 Page 3-10 Issue 10 Type 400 Controller General Handbook (a) Linking a T400 to a pelican controller (b) Linking a T400 to another traffic controller (c) Passing signals to other controllers such a detectors (demands etc), hurry call requests etc. (d) Linking O.T.U control and reply signals to other controllers. 3.8 ALTERNATIVE SIGNAL SEQUENCES User defined signal sequences can be implemented when requested. 667/HB/20200/000 Page 3-11 Issue 10 Type 400 Controller General Handbook 3.9 INPUTS & OUTPUTS The hardware can provide a maximum of 96 lines as follows:Main Processor Card (one of these in every controller) Two variants of the main processor card exist. The I/O characteristics of each are detailed below. /001 variant - Intersection controller processor board. 2 input ports providing a total of 16 lines (8 per port), 2 lines of which are buffered. Buffered inputs 1 and 2 should be used first on all applications. 1 output port providing 4 lines, buffered via relays (2 normally open and 2 normally closed). Note:- Only two buffered inputs are recognised by the configurator. /002 variant - Pelican controller processor board. 2 input ports providing a total of 16 lines (8 per port), 4 lines of which are buffered. Buffered inputs 1 and 2 should be used first on all applications. 1 output port providing 4 lines, buffered via relays (2 normally open and 2 normally closed). Expansion I/O Card (up to 3 of these can be fitted in a controller) 2 input ports providing a total of 16 buffered lines (8 per port). 2 output ports providing a total of 16 buffered lines (8 per port). SDE/SA Card 4 input ports providing a total of 32 buffered lines (8 per port). 32 inputs caters for 16 assessors. Any inputs not used for SDE/SA may be used for other purposes e.g. detectors. Connections The ports on the Expansion I/O, Main Processor and SDE/SA PCBs are accessed by sockets on the rear. The Expansion I/O Board has 4 sockets, the Main Processor has 2 and the SDE/SA PCB has 2. Normally equipment is connected to the controller inputs via the controller Expansion I/O Boards, which isolate the controller logic from the outside world. However, if the equipment is within the controller cabinet, it is possible to connect directly to the controller Main Processor unbuffered inputs without going via Main Processor buffered inputs or Expansion I/O Boards. 667/HB/20200/000 Page 3-12 Issue 10 Type 400 Controller General Handbook This is only possible if the device to be connected to the controller input has isolated (voltage free) reed relay contacts, or the Solid State equivalent, as an output with the following impedance characteristics. Device output low impedance < 2 kΩ Device output high impedance > 300 kΩ This will not operate within a standard solid state output as specified in MCE0100. Such output contacts must be commoned to Controller 0 volts if required. N.B. If controller inputs are to be monitored by an Outstation Monitoring Unit (part of a Remote Monitoring System), then the controller inputs cannot be unbuffered - they MUST be buffered. Port Allocation Port numbers are allocated as per the following table: Board Type CPU CPU CPU Expansion I/O Expansion I/O Expansion I/O Expansion I/O SDE/SA SDE/SA SDE/SA SDE/SA Port No 0 1 11* (a) (b) (c) (d) 6 7 8 9 Port Type INPUT INPUT OUTPUT INPUT INPUT OUTPUT OUTPUT INPUT INPUT INPUT INPUT Connector name PLE PLE PLC PLB PLC PLD PLE PLB PLB PLC PLC Where (a), (b), (c) and (d) are ports on the Expansion I/O Boards numbered using the rotary switch on the front of each board:- (a) (b) (c) (d) * INPUT INPUT OUTPUT OUTPUT Expansion I/O Board 0 2 3 4 5 Expansion I/O Board 1 6 7 8 9 Expansion I/O Board 2 10 11* - Expansion I/O Board 2 10 11* Port 11 can be defined as either 4 bits of output (CPU) or 8 bits of input or output (Expansion I/O board 2). Note: The Tuen Mun contract requires a specific I/O allocation which is detailed in Appendix D. 667/HB/20200/000 Page 3-13 Issue 10 Type 400 Controller General Handbook 3.10 MANUAL PANEL FACILITIES There are four versions of the Intersection Manual Panel:(a) A full Intersection controller manual panel. (b) A Police manual panel. (c) An Internal Manual Panel (d) A basic manual panel. For further information refer to section 6. 3.10.1 Full Intersection Controller Manual Selection Panel The Manual Panel incorporates the following:• Eight stage selection push buttons and associated indicators • Five mode selection pushbuttons • Signals ON/OFF switch • Lamp test push button • Prohibited move indicator • Hurry call indicator • Higher priority indicator • 3 spare indicators e.g. for priority, UTC Active • 3 spare push buttons (which can be used alone or in conjunction with the Indicators) e.g. for DFM Reset, Dim over-ride, Remote Reconnect, Part Time Select, Flashing Signals, Alternative Maximum, Audio Signal Override etc. Some of these facilities would only be used abroad. Refer to 667/2/20645/000 for the T400 Manual Panel label for these facilities. 3.10.2 Police Manual Panel (Hong Kong) The Police Manual Panel incorporates the following:• DFM LED. • Signals ON/OFF switch. • Manual step-on control enable and disable pushbuttons. • Optional proximity switch for disabling step-on when the manual panel door is shut (always used for Hong Kong). • Select All Red button. • Manual step-on button. • ‘Active’ LED indicator. This is not DTp approved and is normally only used on export orders. 667/HB/20200/000 Page 3-14 Issue 10 Type 400 Controller General Handbook 3.10.3 Internal Manual Panel (Hong Kong) This is fitted inside the controller and access is limited to persons who have controller door keys. It incorporates the following:• Eight stage selection push buttons • Five mode selection pushbuttons and associated indicators • Lamp test push button • Prohibited move indicator • Hurry call indicator • Higher priority indicator • 1 spare indicator • Override Dim pushbutton and indicator • Signals Flash This panel would normally be used in conjunction with a Police Manual panel which is fitted with a signals on/off switch. 3.10.4 Basic Manual Panel • A basic panel consisting only of a signals ON/OFF switch & cabinet alarm. 3.10.5 Optional Manual Panel Facilities • Fixings for British Telecom terminations 3.11 SIGNAL AND DETECTOR ISOLATING SWITCHES Signals Isolating Switch A single pole 30 amp switch is fitted to the controller switch DIN rail to isolate the signal supply. Detector Isolating Switch A double pole 30 amp switch is fitted to the controller switch DIN rail. One pole isolates the 24v detector supply. The second pole can be used to isolate the 27½V detector supply if fitted in addition to the 24v supply. 667/HB/20200/000 Page 3-15 Issue 10 Type 400 Controller General Handbook 3.12 T400 FAILURE FLASHER FACILITY (EXPORT ONLY) This facility uses a type 400 failure signal to release a set of contactors which switch between the T400 phase output drives and the mains drive from the fail flasher board. The combination of fault log entries which cause the contactors to switch is pre-programmed into the configuration. The speed or frequency of the flashing is controlled by 2 link fields on the fail flasher board. One link field governs the on time, the other controls the off time, both are programmable from 0 to 1.260 seconds in 20mSec steps. This facility can be disable (if facility is fitted) by removing the 20 amp fuse on the flasher pcb. The contactors can be wired to flash either the red, amber or green aspect of any phase. 3.13 HANDSET The handset available has alpha numeric displays and keyboards. When in use the handsets plugs into the RS232 port socket, on the front of the C.P.U board. Using a handset it is possible to view and/or change some of the data held in the T400 battery supported R.A.M. e.g. timings etc. Handsets are sold as separate items. 1. G.R. Electronics Handset. 2. Epson with standard terminal software. 3. Epson with intelligent terminal software. Note: This provides facilities such as:(a) auto dump of controller times. (b) hard copy print outs, etc. See handset handbook 667/HH/20200/000. 4. Any computer terminal with an RS232 port socket capable of operating at 1200 Bauds. See section 6.3.9 for more information on individual handsets. 667/HB/20200/000 Page 3-16 Issue 10 Type 400 Controller General Handbook 3.14 SPECIFICATION SHEETS (667/DJ/15900/000) A copy of the specification sheets is provided in Appendix 0 of this handbook, with a guide in section 7. It should provide an idea of the flexibility of the controller and the data required to configure the facilities available. Spare sets can be ordered by quoting the above number. These sheets, if filled in at the time of the order, will reduce the delivery time, misinterpretations and reduce the possibility of additional costs. Note: Certain contracts use a subset of these, see Appendix 0 for Tuen Mun specification sheets. 667/HB/20200/000 Page 3-17 Issue 10 Type 400 Controller General Handbook 4. PELICAN/PEDESTRIAN CONTROLLER 4.1 GENERAL There are a number of basic configuration PROMs, covering the following configurations: single or dual stream, MCE0125, MCE0145, Puffin or Toucan. One of these basic configurations is selected for the controller and it is further altered via the handset i.e. timings may be altered within approved ranges, IO lines on the controller may be set up to have different functions etc. Selection of some facilities may require extra hardware, e.g. extra Expansion I/O card. Timings and selections made via the handset are stored in battery backed RAM which is continually validated by CRC checking. There are two modes of operation of a Pelican/Pedestrian controller: 4.1.1 Fixed Vehicle Period mode In this mode the controller runs a set Vehicle Green period (ranging from 20 to 60 seconds in 1 second increments) after which it will service a pedestrian demand if one exists. If no pedestrian demand is present it will rest on vehicle green until there is a ped. demand which it will then service immediately. 4.1.2 Pelican VA mode In VA mode, the controller will respond to vehicle extension detectors once the minimum vehicle green has expired in the following manner : (a) Extending/Maximum Change If a pedestrian demand is inserted but vehicles are passing continuously over the detectors, the vehicle green will be extended to a preset maximum, after which the pedestrian demand is serviced. In this instance, for safety reasons, a “maximum change” all-red period will be inserted between the vehicle green and the pedestrian green after the amber leaving period. If no pedestrian demand exists the vehicle max. green timer will not be started and the vehicle phase will rest in green. (b) Gap Changing If a pedestrian demand is inserted where vehicles are not passing continuously over the detectors, the controller will wait until no vehicle extensions are being timed and then service the pedestrian demand, before the vehicle green max. timer has timed out. In this instance, a “gap change” all-red period alterable between 1 and 3 seconds, is inserted between the vehicle and pedestrian greens. 667/HB/20200/000 Page 4-1 Issue 10 Type 400 Controller General Handbook (c) Pre-timed Maximum vehicle green If this mode is selected, the controller will start the max. vehicle green timer as soon as vehicle green is gained, instead of waiting for an opposing/pedestrian demand. If no pedestrian demand occurs before the max timer expires the controller will rest in vehicle green until a pedestrian demand is inserted which it will then service immediately by completing a “max change” to pedestrian green, even if a vehicle is inserting a continuous extension. If a pedestrian demand is inserted before this max. timer has expired there can still be a gap change if there are no vehicle extensions present. 4.2 PELICAN/PEDESTRIAN TIMINGS The minimum green, maximum green and vehicle extension timings for a pelican are alterable via the handset within ranges approved in MCE0125 and MCE0145. These are different to those for MCE0141 vehicle phases and thus they are accessed by different handset commands. There are other alterable timings for the all-red time from vehicle green to ped. green in UTC and Local Link modes following the removal of PV and PV1 respectively. If both of these signals occur simultaneously then the UTC signal PV always overrides the Local Link signal. If SDE/SA is selected (via the handset) and fitted on the controller then all of the vehicle green to pedestrian green all-red times are fixed at three seconds. If there has been a DFM failure on the controller then a maximum all-red time is included in the change from vehicle green to pedestrian green for safety reasons. If the Vehicle Detector Checking facility has been enabled and there has been no activity on one or more of the vehicle extension during the vehicle green period, then a maximum all-red time is included in the change from vehicle green to pedestrian green for safety reasons. 4.2.1 Puffin Sequence Timings The Puffin controller sequence is similar to an intersection pedestrian, since there are no flashing aspects. However, the blackout period of the intersection pedestrian is replaced with an extendable clearance period, during which red is displayed to traffic and pedestrians. This clearance period is extendable up to a maximum by detecting pedestrians on the crossing. Pedestrians are also detected as they wait to cross, by means of a kerbside detector. If after a demand has been registered no-one is still waiting, the pedestrian demand is cancelled. 667/HB/20200/000 Page 4-2 Issue 10 Type 400 Controller General Handbook The Puffin operates in conjunction with Red lamp monitoring, SDE/SA, UTC, CLF etc. in the same manner as the Pelican. The Puffin Extendable Clearance Period The clearance on the change from pedestrian green to vehicle green and is composed of:• a configured minimum red period, followed by • a variable red period (extendable by ‘on-crossing’ detectors up to a configured maximum), followed by • a clearance red period (this is the ‘long’ clearance period if the variable red has been extended up to its maximum otherwise the ‘short’ clearance period is used). 4.3 MANUAL PANEL FACILITIES When the T400 is used as a pedestrian controller the Manual Panel is usually equipped as a ‘basic manual panel’ providing only cabinet alarm together with a signals on/off switch (see Figure 6.3.5.4). If specifically requested then a full pedestrian manual panel may be provided which duplicates a few of the facilities which are provided via the handset (see section 5) onto pushbuttons. A brief description of the full pedestrian manual facilities are described in the following sections. For a ‘basic panel’ these facilities are available via the controller handset (see section 5). 4.3.1 Select VA/FVP The mode on the pelican/pedestrian controller may be selected between FVP and VA. However the Select VA function is only actioned if VA mode has been enabled via the handset. The associated LED reflects the position of the pushbutton only and this is not necessarily the mode that is currently running. 4.3.2 Continuous Ped. Demand When this button is pushed, the associated LED is illuminated and a permanent demand is inserted for the pedestrian phase of that pelican stream. 667/HB/20200/000 Page 4-3 Issue 10 Type 400 Controller General Handbook 4.3.3 Continuous Vehicle Extension When this button is pushed, the associated LED is illuminated and the vehicle extension timers are continually reset so that in VA mode the vehicle phase always runs to a max. When this switch is released, the extension timer running continues to time out and after it has expired, the pelican stream reverts to normal operation. 4.3.4 DFM Reset This button is used to reset the DFM lamp and only has that effect if all faulty detectors/pedestrian pushbuttons have changed state since the fault was registered. 4.3.5 Auxiliary LEDs (AUX1, AUX2, AUX3) and Switches (SW1, SW2, SW3) There are two functions available which may be assigned to any of these three switches and LEDs. The requirements in terms of switches and LEDs for these two functions are given below: Remote Reconnect : Both a switch and LED are required. Computer Control LED : LED alone is required. 667/HB/20200/000 Page 4-4 Issue 10 Type 400 Controller General Handbook 4.4 HANDSET On street selection of pelican facilities by the handset can be carried out. A list of the pelican handset commands is given in section 5. The following settings can be altered on the pelican controller :4.4.1 Timings Handset commands are provided to control the pelican timing steps separately from the intersection timings. Use of the intersection timing commands (e.g. MIN, MAX, EXT, IGN, IGS etc.) have no effect on the pelican timings. Local linking times for link delay, link window, override and link fail times are also alterable on the handset. 4.4.2 Speed Discrimination (SDE/SA) No SDE/SA operation, Double or Triple SDE or SA operation and the number of speed assessor units required for the Pelican/Pedestrian may be selected via the handset. Both of the standard PROMs have capability for SDE/SA facilities but only for the DTp standard loop spacing of 12ft. If a non standard loop spacing is required then a non standard configuration PROM will be required. 4.4.3 Manual Facilities When a controller is equipped with a ‘basic manual panel’, handset commands are provided to support the selection and display facilities which were provided on the old style ‘full manual panel’ (see section 5 for details). 667/HB/20200/000 Page 4-5 Issue 10 Type 400 Controller General Handbook 4.5 I/O LINE ALLOCATION Each of the following functions may be allocated to an IO line :Input functions UTC ped. inhibit PV UTC ped. demand PX UTC take over TO (enable SC, PV, PX) UTC switch to FVP working UTC switch to alternative timings UTC Dim Override / remote dim control DO UTC vehicle extensions inhibit SC local link disable LL local link ped. inhibit PV1 local link ped. demand LD call/cancel ped. demand CC 3 vehicle extension detectors 4 push button ped. demand 2 Kerbside detectors (Puffin Only) 4 ‘On crossing’ detectors (Puffin Only) * * * Output functions UTC vehicle green confirm GX UTC wait indicator confirm WT UTC ped. green confirm PG DFM fail confirm DF UTC signals off confirm SO local link disable confirm LL UTC bright confirm remote reconnect RR (active state = disconnect) link out (vehicle green confirm) link out (bright confirm) Kerbside detector test signal (Puffin Only) A description of each of these I/O functions is given in section 4.10. * - These output signals must be allocated to normally closed (N/C) contacts. The first two bits of the CPU output port (port 11) are N/C contacts. The first two bits of each output port on the I/O expansion board are defaulted to the N/O state. However each of these output bits are connected to relays with changeover contacts. Hence they may be wired to give N/C operation. All other output bits operate in the N/O state. 667/HB/20200/000 Page 4-6 Issue 10 Type 400 Controller General Handbook In addition it is possible to :(a) enable/disable DFM on each input (DFS) and define the group (DGP) (b) define the action taken when DFM detects a fault (DFA) as:- continue to use input as before - override input state to active - override input state to inactive (c) invert the sense of particular inputs (IPS) (d) define number of red lamp monitor channels used on each pelican traffic phase (RLM) 4.6 WAIT INDICATORS This facility allows the user to select (via the handset using the WTI command) whether the wait indicator is illuminated by any of the following demands: - Pushbutton ped demands - UTC ped demands - Manual Panel Ped demands - Local Link ped demands - Handset ped demands 4.7 AUDIO CONTROL AND MONITOR An output activates the audio unit during the ped steady green time. An input monitors the drive voltage to the audio unit and a check is made that the monitored state corresponds with the requested state. Repeated failure of the check causes the lamps to be turned off within 500mS (from the point at which the first occurrence of the fault was detected) and an entry made in the fault log. Since the audio drive is derived from the ped green supply, turning the signals off removes the audio drive. 4.8 GREEN CONFLICT FAULT ACTION On detection of a green conflict (as indicated by monitoring the output of the green conflict PROM) the controller turns all the controller lamps and audio indicators off. The lamps will remain off until manually reset (RFL=1), using the handset, turning the power off and then restoring the power. 4.9 RED LAMP MONITORING The current through the vehicle red lamps is monitored to check that there is at least one vehicle red lamp showing while there is a steady green signal showing to pedestrians. If a fault occurs, the controller turns all the signals and the audio indicators off. The lamps will remain off until manually reset 667/HB/20200/000 Page 4-7 Issue 10 Type 400 Controller General Handbook (RFL=1), using the handset, turning the power off and then restoring the power. 4.10 DESCRIPTION OF I/O LINE FUNCTIONS 4.10.1 UTC Facilities • UTC Ped. Inhibit (PV) This input signal prevents the pedestrian phase on a pelican. When PV is released, vehicle extensions will be inhibited for a period specified via the handset. Even if PV is re-applied during this period it will have no effect. • UTC Ped. Demand (PX) This input signal puts in a request for the pedestrian stage of a pelican. • Vehicle Extensions Inhibit (SC) This input signal forces the controller to ignore all vehicle extension requests. To ensure safety of operation, the vehicle to ped. change becomes a UTC. all-red change rather than a gap change. The UTC all-red change time is alterable via the handset. • UTC Transmission Confirm (TC) or Takeover Control (TO) The TC signal, if allocated to an IO line, is received at the controller from the OTU if valid data has been received by the OTU. The TO signal is very similar in effect except that it is transmitted from the UTC Central Office and not from the OTU and it too signifies that valid data is being sent by the UTC Central Office. The presence of either of these signals disables the Local Link facility. • Computer Control LED on the Manual Panel The rules governing the illumination of this LED are as follows: (1) If the TC/TO function has not been assigned to an IO Line then the presence of PV alone lights this LED. (2) If TO has been assigned to an IO line then the LED is only illuminated when TO is present in conjunction with PV. (3) If TC has been assigned to an IO line and selected to control the LED, then the presence of this TC signal alone lights the LED. (4) If TC has been assigned to an IO line and selected not to control the LED, then the LED is illuminated only when both PV and TC are present (as in case 2). 667/HB/20200/000 Page 4-8 Issue 10 Type 400 Controller General Handbook • Switch to FVP mode This input disables Pelican VA mode and thus forces the controller to run in FVP mode. This signal only has an effect when the Pelican is running VA mode. VA mode is active under the following conditions : (a) VA operation is selected via the handset. AND (b) VA mode is activated using the VA switch on the manual panel. • Switch to Alternative Timings This input signal forces the Pelican to switch to the first alternative set of timings. • UTC Dim Override (DO)/Local Link Dim Request One of these two types of remote dimming can be selected via the handset for the pelican/pedestrian. The main difference between the two types is: a) the UTC input signal overrides any request for the controller to be in the dim state provided by the solar cell output and thus provides a “Bright Request” signal. b) the Local Link Dim Request signal is required for a slave pelican controller in a linked dimming situation and provides a “Dim Request” signal. This means that a master controller which has a solar cell controlling its dimming facility may be able to pass on its dim/bright state to another (slave) controller without a solar cell. • Local Link Disable (LL) The effect of this input signal is to disable the Local Link Pedestrian Inhibit facility (PV1) which is detailed in • Vehicle Green Confirm (GX) This output signal indicates that the vehicle phase is showing green on the street. This output signal must always be assigned to a Normally Closed relay so that it fails to the inactive (closed contact) state. 667/HB/20200/000 Page 4-9 Issue 10 Type 400 Controller General Handbook • Wait Indicator Confirm (WT) This output signal indicates that the Wait indicator for the pedestrian phase is illuminated on the street. This output signal must always be assigned to a Normally Closed relay so that it fails to the inactive (closed contact) state. • Pedestrian Green Confirm (PG) This output signal indicates that the pedestrian phase is showing green on the street. This output signal must always be assigned to a Normally Closed relay so that it fails to the inactive (closed contact) state. • DFM Fail Confirm (DF) This output signal indicates when the DFM lamp has been illuminated. This output signal should be assigned to a Normally Open relay so that it fails to the active (open contact) state. • Signals Off Confirm (SO) This output signal indicates that the signals on the CPU pelican/pedestrian are off for whatever reason i.e. Signals switched off from the Manual Panel, Red Lamp Monitor failure, Conflict detected etc. This output signal should be assigned to a Normally Open relay so that it fails to the active (open contact) state. • Local Link Disable Confirm (LL) This output signal indicate that the local link facility on the controller has been disabled, for whatever reason i.e. Local Link disable switch on Manual Panel active, UTC local link disable control bit active, timeswitch function etc. • UTC Bright Confirm This output signal indicates that the signals on the controller are in the bright state, for whatever reason i.e. daytime operation, dim override switch on Manual Panel active, UTC dim override control bit active etc. • Remote Reconnect (RR) This reply bit is generated when the Remote Reconnect Switch on the Manual Panel when fitted/configured is activated (indicated by the illumination of the associated LED). This switch indicates to the UTC central office that the controller is ready to resume under UTC control. 667/HB/20200/000 Page 4-10 Issue 10 Type 400 Controller General Handbook 4.10.2 Local Link Facilities • Local Link Ped Inhibit (PV1) While this signal is active, it prevents the appearance of the ped. phase irrespective of demands, subject to the effect of the Override timer described below. A delay time can be set via the handset so that there is this delay between the PV1 signal being released and the Inhibit on the controller being lifted. After this, a Window time which is also alterable via the handset, can come into effect. This is the time after the Inhibit has been lifted during which the controller ignores vehicle extension detectors and looks for a pedestrian demand to service, even if PV1 has been reapplied during this time. If the window timer expires and PV1 has not been reapplied the controller reverts to its normal (FVP or VA) working mode. If PV1 is active the Override timer will start to time if it has been set to a non-zero value via the handset and normally at the start of the vehicle phase green. This override timer can optionally be selected (via the handset) to commence timing only if a pedestrian demand is present while the vehicle phase is at green. This timer is reset when the PV1 signal goes inactive. If it times out one of two actions may be taken, depending on handset selection : (i) it will ignore the PV1 signal and revert to normal unlinked operation and only recognise the PV1 signal again if it is now released and re-applied. (ii) it can operate in self resetting mode i.e. once the override timer expires it reloads itself, introduces the Link Delay and Link Window times and commences re-timing when either the Window time expires or the controller returns to vehicle green as a result of serving a Pedestrian demand during the Window period. If PV1 is released and reapplied normal linked operation resumes. The Override timer is usually used only for MCE0125 pelicans and its use is determined by checking for a non-zero timing value. There is another watchdog mechanism used for MCE0145 pedestrian controllers which checks that the link is not permanently operated nor permanently released. This mechanism will be used if there is a nonzero timing value for the Link Failure Active/Inactive times (LKA/LKI). Timeout of either of these signifies “link failure” which causes the following actions: Inhibit the appearance of the Pedestrian Phase. Light the Wait Indicator Light the Cabinet Alarm Lamp Set a Fault Log Flag 667/HB/20200/000 Page 4-11 Issue 10 Type 400 Controller General Handbook After a “link failure”, manual intervention is required to reset the fault log before the controller can resume normal operation. In certain circumstances e.g. light traffic flow, the intersection controller will be unable to generate link inhibit release pulses often enough to prevent the timeout of a Fail timer and in these cases a pulse generator is required in the main controller to signify that the link is good. The pulse generator must ensure that the link inhibit is released and reapplied periodically to reset both the FAIL ACTIVE and FAIL INACTIVE link fail timers. To ensure that this pulse generator does not cause the link inhibit signal to be released erroneously certain timing restrictions are imposed on the pulses and signals: 20ms < Inhibit release pulse Inhibit Release signal <= >= 300ms 340ms This means that if the signal on this line is released for less than 300ms and then reapplied the only effect will be to reset the Link Fail Active and Inactive timers. If the signal is released for more than 340ms and then reapplied, then the effect will be to reset the Link Fail Active and Inactive timers and to start the Link Delay timer. • Local Link Dim Request This input signal is treated in the same manner as UTC Dim Override (DO) and is described in section 4.10.1. • Local Link Ped. Demand (LD) This input signal puts in a remote pedestrian demand. • Link Out (Vehicle green confirm) This output signal is essentially a Vehicle Green Confirm signal and can be used to provide a Ped. Inhibit (PV1) to another pelican usually in a staggered link situation. The effect then is to inhibit the ped. of the other pelican while it itself is not in the vehicle green period. NOTE that this does not take account of any race condition between two controllers that are linked together and as such if the pushbuttons of the two controllers are pressed simultaneously there is a possibility that both pelicans could go to green at the same time and so true dual pelican operation cannot be achieved in this manner. In order to overcome this problem a T400 dual pelican must be used. • Link Out (Dim Request) 667/HB/20200/000 Page 4-12 Issue 10 Type 400 Controller General Handbook This signal is used by the master controller in a linked dimming situation, where it is usually used to pass on the dim/bright state of the master to the slave pelican controller. 4.10.3 Call/Cancel Function • Call/Cancel Ped. Demand (CC) This input signal acts as a normal call/cancel demand, in that a demand must be present for a certain period (call time) before the demand is accepted. Similarly if the demand disappears before the controller has satisfied it, then it must permanently disappear for a certain period (cancel time) before the controller will cancel the demand. The effect of the input is to put in a demand for the pedestrian phase. 4.10.4 Puffin I/O Facilities • Push Button and Kerbside Detector Inputs Two push button inputs are available on each Puffin stream. In addition, each Puffin stream has two kerbside detector inputs which indicate when there are pedestrians waiting to cross. Each input from push button or kerbside detector is held active in the controller for a configurable hold time (after the input has gone inactive). The pedestrian demand is only registered if the following conditions are met:a) a push button is being pressed or hold period active AND b) a pedestrian is being detected by the kerbside detector or the kerbside hold period is active. The pedestrian demand is cancelled and the wait indicator turned off if all kerbside detectors indicate no pedestrians present for a configured detector timeout period. NOTE: Pedestrian demands from UTC or local link operate as on the Pelican controller i.e. the demand does not require the kerbside detector to be active in order to be registered and the demand is latched - not cleared when the kerbside timeout period expires. • Kerbside Detector Test Output 667/HB/20200/000 Page 4-13 Issue 10 Type 400 Controller General Handbook One test output is provided for each Puffin stream. This output should be wired to connect +24V through the ‘normally open’ relay contacts to the detector test input on surface mounted kerbside detectors. While there is no pedestrian demand registered, each detector is tested at 10 second intervals. Note that the kerbside detector is tested during the pedestrian push button hold time, providing that no demand is registered. The test output is driven with a 400mS pulse by the controller and a check is made for a detector response pulse. A missing or late response forces the detector active (within the controller) and an entry is made in the fault log. A subsequent correct response from the detector removes the force condition. Detector testing is required with surface mounted detectors, but not with ‘above ground’ detectors. Detector testing is enabled by default. Testing can be disabled by de-allocating the corresponding detector test output. NOTE: The test sequence results in a pulse appearing on the kerbside detector output. This will be treated as a normal pedestrian presence, activating the kerbside hold and timeout periods. • ‘On-crossing’ Detector Inputs Up to 4 inputs are available on each Puffin stream. The ‘on-crossing’ detector indicates when there are pedestrians moving on the crossing and is used to extend the variable clearance period on the move from pedestrian green to vehicle green. Any configured ‘on-crossing’ detector remaining inactive during a cycle is assumed faulty and forces the following variable clearance period to be extended up to it’s maximum. An entry is also made in the fault log. If the detector subsequently operates correctly, then the force is removed and normal operation resumed. 4.11 TIMESWITCH FACILITIES • Switch Audio off This facility allows the pelican ped. audio signal to be turned off on a time of day basis. • Alternative Max. sets 667/HB/20200/000 Page 4-14 Issue 10 Type 400 Controller General Handbook There are four time sets available for each of the modes. I.e. Pelican VA and FVP, which may be selected on a time of day basis. The selection of these timesets is required to have a lower priority than the UTC ‘Switch to Alternate Times’ signal (described in section 4.10.1). As a result of this requirement the time switch settings will only be effective if the UTC ‘Switch to Alternate Times’ signal is not active. • Switch to FVP mode This facility disables Pelican VA mode and thus introduces FVP mode on the pelican/pedestrian controller on a time of day basis. 4.12 CLF FACILITIES The only effect of CLF on a pelican controller is to provide a ped. inhibit signal. There is a corresponding group influence to cancel this ped inhibit influence i.e. an “Allow Ped” influence which is used to provide a ped window. This CLF inhibit signal inhibits the Pedestrian phase for as long as this input is active provided that there is an Allow Ped influence somewhere in the same group. If there is no Allow Ped influence within the same group then the CLF input has no effect. 4.13 CROSS-INHIBIT LINKING On multi-stream Pelican controllers there are some situations when it is desirable to prevent the pedestrian phases from running concurrently (e.g. when two pedestrian crossings are positioned on the road where a central island is provided). This inhibit facility can be introduced by handset command (LKM) (see section 5 for details). 667/HB/20200/000 Page 4-15 Issue 10 Type 400 Controller General Handbook 5. HANDSET COMMANDS Access to the T400 timings and status information is gained by entering commands on an approved handset and interpreting the response on the display. The pages following give an example of the types of handset codes that can be used. The document “Handset Command List” 667/HH/20200/000 gives up to date information on handset operation and codes. This should be used when operating the handset. 667/HB/20200/000 Page 5-1 Issue 10 Type 400 Controller General Handbook (A-ACCESS LEVEL: O=OPEN, R=READ ONLY, 2=LEVEL 2, 3=LEVEL 3) CODE INDX1 ADF AMX BAS BSA BSR CCI CCP CFE CGR CGT CIC CIL CKL CNN CPL CPT CST CTS CUD DAY DCL DCN DET DFA DFD DFS DFZ DGP DHC DIT DMV DOV DPG DSA DSI DTO ENC ENG ENM ENO ENR ENS EXT FAC FDS FFS FIO PHASE STR’M 0-63 STR’M 0-5 0-7 0-7 0-95* 0-95* 0-95* 0-59 0-95* 0-1 0-59 0-59 0-7 0-7 0-3FFF CODE 0-7FF 0-FFF 0-1FFF 0-7FF PHASE FACIL 0-127 0-63 0-139 INDX2 DATA 1 0-255 0-2 1-52 1-52 1 0-1 0-1 1 0-255 PLAN 0-1 0-2 0-255 0-255 0-255 0-2,99 0-2 0-255 PHASE 0-7,255 0-255 0-1 0-FF 0-1 0-255 T/SET 0-255 T/SET 0-255 0-1 OFFS. 0-31.8 0-95,255 667/HB/20200/000 DESCRIPTION A ACCEPT DETECTOR FAULT(S) SECOND MAX PERIOD SELECT MEMORY DISP. BASE SET BST ADVANCE WEEK SET BST RETARD WEEK COMPUTER CONTROL INDICATOR RESTORE CLF OPERATION CONDITIONING FAC. ENABLE CURRENT GROUP CURRENT GROUP TIME CONFIGURATION CODE CROSS INHIBIT LINKING LOAD MASTER TIME CLOCK 2nd CONTR RESET COMMAND CURRENT PLAN CONFLICT PROM TEST REQUEST CURRENT STAGE IN STREAM SELECT MST SYNC SOURCE ASSIGN U/D UNIT TO AN INPUT LINE MASTER TIME CLOCK DAY DET. CALL DELAY PERIOD DET. CANCEL DELAY PERIOD DETECTOR INPUT SETTING DETECTOR FAULT ACTION DET. FAULT MONITOR TIME DET. FAULT MONITOR DISABLE PHASE TO BE DELAYED ASSIGN INPUT LINE TO A DFM GROUP HURRY CALL DELAY PERIOD I/O DIMMING (0=UTC,1=LLINK) PHASE DELAY MOVEMENT TABLE DIM OVERRIDE PHASE DELAY PERIOD DFM SET ACTIVE FAILURE DFM SET INACTIVE FAILURE DFM TIME OVERRIDE DISPLAY CONFIG. PROM DATA DISPLAY ENG. CODE MEMORY DISPLAY IMU SHARED MEMORY DISPLAY OTU/LMU SHARED MEMORY DISPLAY RAM. MEMORY DATA DISPLAY SDE SHARED MEMORY PHASE EXTENSION PERIOD FACILITIES TABLE FAULT DATA SCAN FAULT FLAG SCAN FUNCTION I/O ALLOCATION Page 5-2 2 2 2 2 2 R 2 3 R R R 2 2 3 2 2 R 2 2 R 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 R R R R R R 2 R R R 2 Issue 10 Type 400 Controller General Handbook CODE FIX FLD FLF FRE FVA FVB FVC FVD HHC HKD HPB IFA IFB IFC IFD IGN IGS IOB IOP IPS ITV LAT LFT LKA# LKD LKI# LKM LKO LKW LLD LMP LMX LPT LRN MAX MBX MCX MDX MIN MND MOD MPA MST MTS MTV OFF OMF OTF INDX1 INDX2 DATA DESCRIPTION A STAGE 0-255 F.T. STAGE PERIOD 0-127 FAULT LOG DATA 0-63 FAULT LOG FLAG 0-2 0-100 FREE PROCESSOR TIME STR’M 20-60 FIX. VEH. PERIOD TIME SET A STR’M 20-60 FIX. VEH. PERIOD TIME SET B STR’M 20-60 FIX. VEH. PERIOD TIME SET C STR’M 20-60 FIX. VEH. PERIOD TIME SET D 0-1 0-255 HURRY CALL HOLD PERIOD STR’M 1.0-2.0 PUFFIN KERBSIDE DET. HOLD STR’M 1.0-2.0 PUFFIN PUSH BUTTON HOLD 0-7 0-15 0-7F GROUP INFLUENCES COMB. A 0-7 0-15 0-7F GROUP INFLUENCES COMB. B 0-7 0-15 0-7F GROUP INFLUENCES COMB. C 0-7 0-15 0-7F GROUP INFLUENCES COMB. D PHASE PHASE 0-199 PHASE INTERGREEN PERIOD 0-199 STARTING INTGRN. PERIOD 0-2 0-1 I/O BOARD 0-2 FITTED (IF 1) 0-11 I/O PORT STATUS 0-95* 0-1 I/O LINE SENSE:0=NORM,1=INVERTED PHASE PHASE INTERGREEN THRESHOLD VALUE PHASE 0.0-31.8 VARIABLE AMBER LEAVING TIME 0-15 0-255 STAGE COMBINATION DURATION STR’M 0-255 PEL LINK ACT FAIL TIM (MIN) STR’M 0-255 PEL LINK DELAY TIME (SEC) STR’M 0-255 PEL LINK INACT FL TIM (MIN) 0-1 0-1 PELICAN LOCAL LINK MODE STR’M 0-255 PEL LINK O/RIDE TIME (SEC) STR’M 0-255 PEL LINK WINDOW TIME (SEC) 0-1 LOCAL LINK DISABLE PHASE 1-3 ILLUMINATE PHASE ASPECT STR’M 0-255 MAX ALL RED PERIOD 0-1 LAMP TEST 0-255 3rd RESET COMMAND PHASE 0-255 PHASE MAX PERIOD PHASE 0-255 SECOND MAX PERIOD PHASE 0-255 THIRD MAX PERIOD PHASE 0-255 FOURTH MAX PERIOD PHASE 0-255 PHASE MIN PERIOD 0-1 MANUAL PANEL ENABLE/DISABLE STR’M CURRENT OPERATING MODE 0-3 0-255 MANUAL PANEL ALLOCATION 0-3 DATA SET MST SYNC CHANGE TIME MASTER TIME SWITCH STATUS PHASE MINIMUM THRESHOLD VALUE PLAN 0-1 0-255 GROUP OFFSET TIME 0-1 INTEGRAL OMU (IMU) FITTED 0-1 INTEGRAL OTU/LMU/RLM CARD FITTED 667/HB/20200/000 Page 5-3 2 R R 2 2 2 2 2 2 2 2 2 2 2 2 3 3 2 R 2 R 3 2 2 2 2 2 2 2 2 3 2 2 3 2 2 2 2 3 2 R 3 2 R R 2 2 3 Issue 10 Type 400 Controller General Handbook CODE INDX1 INDX2 OTO PAR PAR PAR PAR PAR PBG PBT PCn PDE PDR PDS PFD PFT PGT PGT PGT PHC PHD PHE PIA PIC PIR PIT DATA DESCRIPTION A 0-1 STR’M STR’M STR’M STR’M STR’M 0-7 PHASE UNIT UNIT UNIT UNIT 0-2 STR’M STR’M STR’M 0-1 PHASE PHASE 0-15 STR’M 0-1 0 1 2 3 4 ALLOCATE AN INTEGRAL OTU OUTPUT PEL A/R GAP CH. TIME (SEC) PEL A/R MAX CH. TIME (SEC) PEL A/R FVP CH. TIME (SEC) PEL A/R UTC CH. TIME (SEC) PEL A/R LLK CH. TIME (SEC) IDENTIFY PUSH-BUTTON DFM GROUPS PED BL’OUT/FL’ING GRN TIME (SEC) PHASE (n) COMP. TIME PRIORITY DEMAND ENABLE PRI. DFM SELF-RESET ENABLE DISP. PRIORITY DEM/EXTS FIRST PRIORITY DELAY TIMER RTC POWER FAIL LIMIT TIME MCE0125 - PED GREEN TIME (SECS) MCE0145 - PED GREEN TIME (SECS) PUFFIN - PED GREEN TIME (SECS) HURRY CALL PREVENT PERIOD MANUAL PHASE DEMAND MANUAL PHASE EXTENSION PRIORITY INH. TIMER STATUS PROGRAM PROM ID CODE PELICAN DELAY PERIODS PELICAN INTERGREEN TIMES: (SECS) 2 3 3 3 3 3 2 3 2 2 2 R 2 2 3 3 3 2 2 2 R R 2 3 PIT PIT PIT PIT PIT PIT PIT STR’M STR’M STR’M STR’M STR’M STR’M STR’M 3 3 3 3 3 3 3 0-7 0-255 MCE0125: V/ RED + P/FLGRN TIME MCE0125: V/FLAMB + P/FLGRN TIME MCE0125: V/FLAMB + P/ RED TIME MCE0145: V/ RED + P/BKOUT TIME MCE0145: V/ RED + P/ RED TIME PUFFIN MIN. CLEARANCE TIME(SECS) PUFFIN LONG RED EXTRA CLEARANCE TIME PUFFIN SHORT RED EXTRA CLEARANCE TIME PRIORITY UNITS INHIBITED PLAN INFLUENCE SELECTION PLAN-GROUP TIME SETTINGS PIT STR’M n2 0-3 PIU PLI PLT PLAN PLAN PME PMT PMV PRD PRE PRI PRS PSA PSD UNIT 0-1 UNIT UNIT UNIT UNIT GROU P T/SET T/SET PHASE - R 2 2 0-255 0-1 0-255 0-1 0-1 0-1 0-1 0-255 MAINTENANCE ACCESS MONITOR TIME (0s-2550s) PED. MOVEMENT ALGORITHM AUTO PLAN RE-ENTRY DELAY TIME PRIORITY REV. DEM. ENABLE PRIORITY INH. TIMER ENABLE AUTOMATIC PLAN RE-ENTRY SWITCH PRIORITY STRAT. VA DEMS PRIORITY 2ND DELAY TIMER O 2 2 2 2 2 2 2 2 0-255 1-3 1-3 1-3 1-3 1-3 0-1 0-255 T/SET 0-255 T/SET 0-1 0-255 DATA 4-9 3-15 4-9 0-255 0-1 0-1 0-255 0-2 VARIOU S 0 0-2 1 6-18 2 1-2 0 5-15 1 1-8 n0 2-5 n1 0-3 667/HB/20200/000 Page 5-4 3 Issue 10 Type 400 Controller General Handbook CODE PSE PUI PUP PUT PVE PVG PVI PVM PVP PVS PVU PWN RDF REX REX RFL RLM RLT RMR RMX RMX SAS SCI SCR SCT SDS SDT SEA SGT SHC SPH SIE STA STP STM SWS TKD TKE TMA TMC TMT TOD TOT TSW INDX1 INDX2 DATA DESCRIPTION A UNIT PHASE 0-1 PRIOR. STRAT ENFOR. DEM UNIT 0-FF PRIORITY UNITS TO BE INH. UNIT PHASE PRIORITY UNIT PHASE UNIT PRIORITY UNIT TYPE UNIT T/SET 0.0-31.8 PRIORITY EXTENSION TIME UNIT 0-255 DET. INTERRUPT PERIOD UNIT T/SET 0-255 INHIBIT TIME PERIOD UNIT T/SET 0-255 PRIORITY MAXIMUM TIME PHASE PRIORITY VEH. UNIT STATUS STAGE PRIORITY VEH. STAGE STAT. UNIT PRIORITY VEH. UNIT STATUS STAGE 0-255 PED. WINDOW PERIOD 1 RESET DETECTOR FAULT MON. STR’M 0-31.8 ALL-RED EXTENSION PERIOD n 0.4-5.0 PUFFIN CLEARANCE EXTENSION TIME (0.2s) 0-1 RESET FAULT LOG STR’M 1-4 No. RLM CHANNELS ENABLED PHASE 0-255 ENHANCED RLM PHASE DELAY TIME REMOTE RECONNECT STR’M 0-255 ALL-RED MAXIMUM PERIOD n 0 - 13 MAXIMUM CLEARANCE TIME (SECS) STR’M 0-16 PEL: No. SDE/SA ASS. USED 0-1 EXTRA CLEARANCE STATUS 0-1 EXTRA CLEARANCE REQUEST PHASE 0-50 SDE/SA EXTRA CLEAR. TIME 0-2 PEL: SELECT - 0=NONE 1=SA 2=SDE STR’M 0-1 PEL: SDE/SA - 0=DOUBLE 1=TRIPLE 0-1 SPEED EXTENSION STATUS 1 RESET TO GROUP 0 UNIT HURRY CALL STATUS PHASE PHASE STATUS STR’M 0-31.8 SUPPLEMENTARY I/G EXT (LMU) CONTROLLER STATUS MESSAGE STAGE 0-255 MANUAL STEP ON 0-3 DATA SET MASTER TIME CLOCK 0-15 0-1 SWITCH FACILITY STR’M 2.0-5.0 PUFFIN KERBSIDE DET. TIMEOUT 0-255 1st CONTR RESET COMMAND 0-255 CONTROLLER TEST MODE (ACCESS) 0-255 CONTROLLER TEST MODE (COUNTDOWN) 0-255 CONTROLLER TEST MODE (TIMER) MASTER TIMER CLOCK SETTING 0-1 PEL TC/TO UTC BIT TYPE 0-63 0-5 DATA TIME SWITCH SETTING 667/HB/20200/000 Page 5-5 2 2 R R 2 2 2 2 R R R 2 2 2 2 2 3 3 2 2 2 3 R R 2 3 3 R 2 R R 2 R 2 2 2 2 3 3 2 2 R 2 2 Issue 10 Type 400 Controller General Handbook CODE INDX1 INDX2 DATA TWD - - - UDT UIE VAD VAE VAM VAX VBX VCX VDX WEK WTI 0-5 STR’M STR’M STR’M STR’M STR’M STR’M STR’M STR’M 0-4 0 - 0-255 0-255 0-4 0-4 6-15 10-60 10-60 10-60 10-60 1-52 0-1 DESCRIPTION A TRIP WATCHDOG - WARNING - 3 CAUSES IMMEDIATE SHUTDOWN CONSEQUENTLY MUST NOT BE USED UNDER ANY CIRCUMSTANCES TO TEST EQUIPMENT WITH SIGNALS ON AND CONTROLLING TRAFFIC. U/D TIMEOUT (IN 10 SECOND UNITS) PEL UTC "PV" WINDOW TIME PEL VA MODE PEL VEH. GRN EXT TIME (SEC) PEL VEH. GRN MIN TIME (SEC) PEL VEH. GRN MAX TIME (SEC) PEL VEH. GRN ALT1 MAX (SEC) PEL VEH. GRN ALT2 MAX (SEC) PEL VEH. GRN ALT3 MAX (SEC) MST WEEK SETTING WAIT IND ILLUMINATION 2 2 3 2 3 2 2 2 2 2 2 * = Line numbers # = Local site approval must be sought before the use of these facilities. 667/HB/20200/000 Page 5-6 Issue 10 Type 400 Controller General Handbook 6. GENERAL ARRANGEMENT OF T400 HARDWARE 6.1 SMALL OUTERCASE Refer to Figure 6.1 for diagrammatic layout. 6.1.1 Master Switch Panel The mains supply is terminated by the electricity board cutout, for which a mounting board is provided at the lower right hand side of the rear cabinet wall. 6.1.2 Controller Panel At the left side is a sub-chassis controller panel to which most of the components are mounted. At the right side is located the Master switch and fusing, together with a Maintenance socket protected by an RCD and a fuse. At the bottom is the controller panel switch, a mains filter, and a solid state relay. Above is the logic power unit and above that is the PCB module. The controller panel can accommodate 4 x 12 way terminal blocks for connection to street cabling e.g. detectors, lamp feeds etc. Additional termination panels can be provided (2 max) which can accommodate a further 8 x 12 way blocks. Armoured cable can be secured to castellated bar positions beneath the terminal blocks. 6.1.3 PCB Module The main processor and phase driver boards are located at the top left of the cabinet in a small rack module. 6.1.4 Manual Panel & Cabinet Alarm A membrane type panel with integral indicator LEDs is fitted behind a lockable door on the right hand side of the case. The cabinet alarm indicator on this panel is visible to outside observation through a red coloured lens in the Manual panel door. 667/HB/20200/000 Page 6-1 Issue 10 Type 400 Controller General Handbook 6.1.5 Uncommitted Space The middle and upper central areas of the cabinet are available for mounting ancillary equipment. i.e. Detector racks OTU OMU/OMCU LMU Table 6.1.5 Accommodation of Ancillary Equipment within a Small Outercase Total Capacity : 17U Combination no. Top of Cabinet Bottom of Cabinet Not Preferred Key: 3U 5U* 5U# OMU 1 3U 3U 3U 3U 5U* 2 3U 3U 3U 5U* 3U 8 8 3 3U 3U 5U* 3U 3U 4 5U# 3U 3U 3U 5 OMU 3U 3U 6 3U 3U OMU = 11” Detector Rack = Siemens OTU = Siemens OTU or Ferranti OTU/OMU (short rack version) = Siemens OMU Notes: a) These are typical combinations for general use - see drawing 667/GA/20279/000 for other combinations. b) The above equipment is located on the small controller ‘Equipment Mounting Frame’. c) Although the controller can accommodate a large number of detector racks, which implies a large number of detector cards, this will be limited in practise by the available capacity of the power supplies provided. d) Mounting studs for the Siemens LMU are provided on the ‘backwall’ of the controller cabinet. e) Due to space restrictions it is not possible to accommodate both the Siemens LMU and Ferranti OTU. 667/HB/20200/000 Page 6-2 Issue 10 Type 400 Controller General Handbook Figure 6.1 - T400 In A Small Outercase PCB MODULE (EXPANSION) MANUAL PANEL CONTROLLER PANEL ASSEMBLY PCB MODULE E F TERMINAL BLOCKS A G H J L K M ADDITIONAL TERMINATION BLOCKS B N C R D T X P S W Y POWER SUPPLY UNIT MASTER SWITCH AND FUSE RAIL CONTROLLER SWTICH AND FUSE RAIL 667/HB/20200/000 Page 6-3 Issue 10 Type 400 Controller General Handbook 6.2 LARGE OUTERCASE Refer to Figure 6.2(a) and Figure 6.2(b) for diagrammatic layout. 6.2.1 Master Switch Panel The mains supply is terminated by the electricity board cutout for which a mounting board is provided on the Master switch panel at the cabinet rear right hand side. Above this is located the Master switch and fusing together with a maintenance socket protected by an RCD and fuse. 6.2.2 Distribution Panel The front face of the distribution panel holds the remaining power components:Controller switch and fuses mount on a DIN rail with expansion if required. The lamp dimming transformer, mains filtering, solid state relay and logic power supply. The rear of the distribution panel accommodates terminal blocks for connection to street cabling e.g. detectors, lamp feeds etc. Optionally, a transparent cover (667/1/21493/000) may be fitted to the controller in front of the distribution panel; an aperture allows access to the fuses and switches. 6.2.3 PCB Module A modular PCB racking system is employed to accommodate the main processor board with up to 4 Phase driver boards and additional facilities as required. 6.2.4 Manual Panel & Cabinet Alarm A manual panel is fitted behind a lockable door on the right hand side of the case. Several versions of manual panel are available (see section 6.3.5). The cabinet alarm indicator on this panel is visible to outside observation through a red coloured lens in the Manual panel door. 667/HB/20200/000 Page 6-4 Issue 10 Type 400 Controller General Handbook 6.2.5 Uncommitted Space The upper area of the cabinet is available for mounting ancillary equipment. i.e. Detector racks OTU OMU/OMCU LMU See the following table for possible combinations. Table 6.2.5 Accommodation of Ancillary Equipment within a Large Outer-case Total Capacity : 12U Combination no. Top of Cabinet Bottom of Cabinet Key: 1 3U 3U 3U 2 6U 3U 3U 3 5U 3U 3U 4 5U 6U 5 3U 6U 3U = 19” Detector Rack 5U = Siemens OTU/OMU, Ferranti OTU/OMU/MOVA, GEC OTU/OMU 6U = Siemens Controls Interrogator Unit Notes: a) These are typical combinations for general use - see drawing 667/GA/20287/000 for other combinations. b) Although the controller can accommodate a large number of detector racks, which implies a large number of detector cards, this will be limited in practise by the available capacity of the power supplies provided. c) Special mounting brackets are available to support the Siemens LMU. 667/HB/20200/000 Page 6-5 Issue 10 Type 400 Controller General Handbook Figure 6.2(a) - T400 Large Outercase Front View (Typical) OTU or OMU (if fitted) Detector Rack (if fitted) Logic Rask Assembly (Made up of up to four PCB modules) Logic PSU Fuse Rail Dimming Transformer 667/HB/20200/000 Page 6-6 Issue 10 Type 400 Controller General Handbook Figure 6.2(b) - T400 Large Outercase Rear View (Typical) MANUAL PANEL ADDITIONAL TERMINATION PANEL DD BB Z X T R N EE CC AA Y W S P MAINTENANCE SOCKET LOGIC RACK MASTER SWITCH FUSES AND RCD DISTRIBUTION PANEL 667/HB/20200/000 L J G E C A M K H F D B Page 6-7 ELECTRICITY BOARD CUT-OUT MOUNTING BLOCK Issue 10 Type 400 Controller General Handbook Figure 6.2(c) - T400 Large Outercase Front View (Hong Kong) OTU or OMU (if fitted) Detector Rack (if fitted) Internal Manual Panel Logic Rask Assembly (Made up of up to four PCB modules) Logic PSU Fuse Rail Dimming Transformer 667/HB/20200/000 Page 6-8 Issue 10 Type 400 Controller General Handbook Figure 6.2(d) - T400 Large Outercase Rear View (Hong Kong) MANUAL PANEL SECOND PANEL (FITTED AS REQUIRED) 1 G J L N R T X H K M P S W Y 12 1 12 MAINTENANCE SOCKET LOGIC RACK MASTER SWITCH FUSES AND RCD FIRST PANEL (ALWAYS FITTED) 1 1 E F E 24 1 C A 12 12 1 1 F 24 1 D 12 36 6 31 1 TBZ ELECTRICITY BOARD CUT-OUT MOUNTING BLOCK B 12 PED AUDIO 667/HB/20200/000 Page 6-9 Issue 10 Type 400 Controller General Handbook 6.3 EXPANDED DESCRIPTIONS OF T400 HARDWARE & OTHER EQUIPMENT 6.3.1 O.T.Us/O.M.Us A number of different type OTUs and OMUs can be fitted into the T400 racking system. Their usual position being at the top of the controller. The units which it is possible to fit are as follows:Siemens O.T.U 666/1/40700/etc Siemens Scoot O.T.U 666/1/16600/etc Siemens Short Rack O.T.U. 666/1/17000/etc Siemens O.M.U 667/1/17500/etc G.E.C Elliot O.T.U Ferranti O.T.U Ferranti O.M.U O.T.U:- Out Station Transmission Unit links a controller to a central computer to allow the co-ordination of traffic signals over a wide area. Scoot O.T.U:- This is a Special Adaptation of the O.T.U which also sends special loop detection information back to the central computer allowing the computer to study traffic flow and optimise it. O.M.U:- An Outstation Monitoring Unit again sends data to and receives data from a central computer however, this unit monitors the controllers performance and indicates any faults at the junction, which means faster and more efficient maintenance. 6.3.2 TELECOMMAND 8 INTEGRAL SCOOT OTU (EXPORT ONLY) This section has been deleted. 6.3.3 OTU Functions The functions of the TC8 SCOOT OTU are as follow: (1) To demodulate the serial voice frequency data received from the Instation Control. (2) To identify messages intended for the address or addresses for which the OTU is set, otherwise take no action. 667/HB/20200/000 Page 6-10 Issue 10 Type 400 Controller General Handbook (3) To output the data content of Control messages in parallel form to the traffic controller. (4) To input intersection and detector data. (5) To process this data (4 above) in the microprocessor. (6) To convert this processed data to serial form. (7) To convert the serial data to voice frequency signals and to transmit these signals to the Instation in response to an appropriate Control message. (8) Maximum number of OTU inputs and outputs are:24 inputs 16 outputs 6.3.4 Detector Racks and Detectors A number of detectors and their associated racks can be fitted into the T400 racking system. The units available are as follows:• Racks 19” Detector Rack (for T400 Large Controller) 667/1/20690/001 11” Detector Rack (for T400 Small Controller) 667/1/20690/000 Detector ‘L’ Bracket (for mounting 1 detector card) 667/1/17212/000 • Back-Plane Double Back-Plane kit (for 2 detector cards) 667/1/15990/002 Single Back-Plane kit (for 1 detector card) 667/1/15990/003 • Detectors Sarasota - MTS 36Z - 2 channel unit 667/7/21031/002 - MTS 38Z - 4 channel unit 667/7/21031/004 Microsense loop Detectors Type MXED 667/HB/20200/000 Page 6-11 Issue 10 Type 400 Controller General Handbook The following obsolete types may be utilised when replacing existing controllers:Siemens (ST) Self Tune Detectors MkII 667/1/17180/012 = 2 detector channel unit 667/1/17180/014 = 4 detector channel unit Microsense (ST) Self Tune Detectors Type MSE 667/7/20360/002 = 2 detector channel unit 667/7/20360/004 = 4 detector channel unit *Sarasota MCE45Z * 654/4/01023/000 Due to interference - these Sarasota cards must not be used in the same rack that has any other type of detector cards fitted. 6.3.5 Manual Panel & Cabinet Alarm The T400 can be equipped with various Manual panels to support different controller configurations and customer needs. These panels are detailed below:(a) A full Intersection controller manual selection panel. (b) A Police manual panel (step-on). (c) An Internal Manual Panel. (d) A Basic manual panel. (e) Optional Pelican Controller Manual Panel One of the above is fitted behind the small manual panel access door on the side of the controller. When item (b) - Police manual panel - is fitted there is an additional option to fit item (c) - the internal manual panel - inside the controller. Access to the internal panel is via the main controller door. The cabinet alarm LED is situated in the manual panel access door and lights when the detector fault (DFM) system has detected an inoperative detector. The LED is extinguished either by the DFM RESET push-button* (provided the fault has been cleared) or when a defective detector is switched out of use. Note:- * Only if item (e) Optional Pelican Manual Panel fitted; on a standard intersection or pelican controller the “RDF” handset command should be used. 667/HB/20200/000 Page 6-12 Issue 10 Type 400 Controller General Handbook 6.3.5.1 Functions of the Intersection Controller Manual Selection Panel The functions of the controls on the Intersection controller manual selection panel are as follows: Signals ON/OFF Switch In the ON position allows the microcomputer to control the signal lamps supply. With OFF selected switches off the signal lamps. Mode selection pushbuttons These buttons enable the selection of Manual, VA, CLF, Fixed Time or Normal modes of operation, provided no higher priority mode is operative. The VA, Fixed Time or CLF button may be disabled if they are not required. Mode Select Indicators The indicator associated with the button illuminates when the button has been operated. All Red selection With the manual mode operative, causes the controller to change to All Red when selection is implemented. Stage selection pushbuttons 1 to 7 These pushbuttons enable the selection of a user defined stage which appears in each stream. It is important to note that the number of the pushbutton selected will not necessarily reflect the number of the stage(s) that has been selected. Stage Indicators These indicators illuminate to indicate the button which is associated with the current stage. Lamp Test Applies a signal to the microcomputer Pushbutton which illuminates all indicators on the manual panel, including the cabinet alarm lamp for test purposes. Awaiting Command Indicator With manual mode operative (selected on internal manual panel) lights when a manual change is possible, i.e. the associated minimum times have expired. Prohibited Move Indicator With manual mode operative (i.e. manual selected on internal manuals panel) it lights indicating the attempted manual stage change is prohibited and will not be implemented. 667/HB/20200/000 Page 6-13 Issue 10 Type 400 Controller General Handbook Hurry Call Indicator (AUX4) Lights when the Hurry Call mode is ACTIVE. Alternatively, this indicator may be used for other special purposes. Higher Priority mode indicator Lights (AUX5) when a mode with a higher priority mode than manual mode is active. Alternatively this indicator may be used for other special purposes. SW1, SW2 and SW3 Indicators Provide special facilities Override, DFM Reset etc. AUX1, AUX2 and AUX3 Indicators These may be configured to perform user defined functions. e.g. Dim Figure 6.3.5.1 - Intersection Controller Manual Selection Panel SIGNALS CABINET ALARM OFF ON MANUAL CONTROL BT TERMINAL BOXES TYPE 14A & 35A CAN BE FITTED HERE BT LINE JACK UNIT 1A CAN BE FITTED HERE ALL RED 1 2 NORMAL 3 4 5 MANUAL 6 7 AWAITING COMMAND FIXED TIME HURRY CALL (AUX 4) HIGHER PRIORITY (AUX 5) PROHIBITED MOVE AUX 1 AUX 2 AUX 3 SW 1 SW 2 SW 3 BT LINE JACK UNIT 1A CAN BE FITTED HERE 667/HB/20200/000 MODE SELECT Page 6-14 VEHICLE ACTUATED CABLELESS LINK LAMP TEST BT TERMINAL BOXES TYPE 14A & 35A CAN BE FITTED HERE Issue 10 Type 400 Controller General Handbook 6.3.5.2 Functions of the Police Manual Panel (Export Only, Hong Kong.) The functions of the controls on the Police manual panel are as follows: Signals ON/OFF Switch In the ON position allows the microcomputer to control the signal lamps supply. With OFF selected, the signal lamps switch off. Manual Control Enable This pushbutton enables the operation of manual step-on mode, provided no higher priority mode is active. Manual Control Disable This pushbutton disables the operation of manual step-on mode. All Red Stage Selection When operated with the manual step-on Pushbutton mode operative the controller will move to an all-red state, i.e. it will move to an all red stage (or stages if parallel stage streams). When coming out of all red the controller will go to the next stage(s) in the sequence following the stage(s) from which it went to all red. Step-On Pushbutton With the manual Step-on mode operative this pushbutton causes the controller to move to the next stage (or group of stages if parallel stage streams are used) in cyclic order. DFM LED As stated at the beginning of this section this LED illuminates when the controller detects a detector failure. A red lens is fitted in the manual access door to make the LED visible externally. Active LED This LED comes on when the manual step-on mode has been enabled. Manual disable switch This is a microswitch which operates when the manual panel door is closed, which if the controller is left in manual step-on mode will return the controller to normal operation. Notes:- The All Red push buttons on the Police manual panel and the internal manual panel are wired in parallel. If running ‘internal’ Manual the Police Manual panel All Red button will have no effect. If running ‘Police’ Manual the internal manual panel All Red switch will also call the All Red stage. A stage(s) may be configured such that while in manual step on it will appear for a fixed period and then step on to the next stage(s) without the step on button being pressed. If the disable button is pressed the facility will be disabled. Similarly, if the manual flap is closed, a magnetic switch operates to disable the facility. 667/HB/20200/000 Page 6-15 Issue 10 Type 400 Controller General Handbook Figure 6.3.5.2 - Police Manual Panel Layout (Hong Kong) DOOR MICROSWITCH CABINET ALARM SIGNALS OFF ON PLESSEY MANUAL CONTROL ACTIVE 667/HB/20200/000 ENABLE ALL RED DISABLE STEP ON Page 6-16 Issue 10 Type 400 Controller General Handbook 6.3.5.3 Internal Manual Panel (Export Only, Hong Kong) Access to the internal manual panel is via the Controllers front door, see Figure 6.3.5.3, and is usually limited to maintenance engineers. It allows a limited control over the operation of the T400, as described below. The functions of the controls and indicators on the internal manual panel are as follows: Mode selection pushbuttons These buttons enable the selection of Manual, VA, CLF, Fixed Time or Normal modes of operation. The VA, Fixed Time or CLF button may be disabled if they are not required. Mode Select Indicators The indicator associated with the button illuminates when the selection is implemented. Override Dim Pushbutton Overrides lamp dimming requested by solar cell or other means, i.e. timeswitch. All Red Selection Push-Button With the manual mode operative causes the controller to change to all red when selection is implemented. Note that this button will also force All Red if Police Manual is active. Stage Selection Buttons 1 to 7 With the manual mode operative causes the associated stage(s) to be selected provided the request does not involve a prohibited change. Stage Indicators These indicators illuminate to indicate the button which is associated with the current stage. LAMP TEST Pushbutton Applies a signal to the microcomputer to illuminate all indicators on the manual panel and lights the cabinet alarm lamp for test purposes. Signals Flash Pushbutton Flashing AMBER/RED TO SELECTED SIGNALS. This will be configured as disabled. AWAITING COMMAND Indicator With manual mode operative (selected on internal manual panel), lights when a manual change is possible, i.e. the associated minimum times have expired. PROHIBITED MOVE Indicator With manual mode operative (i.e. manual selected on internal manuals panel) it 667/HB/20200/000 Page 6-17 Issue 10 Type 400 Controller General Handbook lights indicating the attempted manual stage change is prohibited and will not be implemented. HURRY CALL Indicator Lights when the Hurry Call mode is ACTIVE HIGHER PRIORITY ACTIVE Lights when a mode with a higher priority than manual mode is active. Spare LED Aux 3 This LED is a spare which may be configured for a user-defined function. Figure 6.3.5.3 - Internal Manual Panel Layout (Hong Kong) HURRY CALL (AUX 4) OVERRIDE DIM 6 AUX 3 ALL RED MANUAL CONTROL HIGHER PRIORITY ACTIVE (AUX 5) SIGNALS FLASH 3 7 PROHIBITED MOVE 4 1 5 2 MANUAL NORMAL AWAITING COMMAND MODE SELECT LAMP TEST 667/HB/20200/000 CABLELESS LINK VEHICLE ACTUATED FIXED TIME Page 6-18 Issue 10 Type 400 Controller General Handbook 6.3.5.4 Basic Manual Panel This is equipped with cabinet alarm lamp indicator and signals ON/OFF switch. Figure 6.3.5.4 - Basic Manual Panel Layout CABINET ALARM SIGNALS OFF ON 667/HB/20200/000 Page 6-19 Issue 10 Type 400 Controller General Handbook 6.3.5.5 Optional Pelican Controller Manual Panel This is equipped with all facilities as specified in MCE 0125 and MCE 0145. Figure 6.3.5.5 - Pelican Controller Manual Panel SIGNALS CABINET ALARM OFF ON CONT PED DEMAND CONT VEHICLE EXTEND VA SELECT FIXED VEHICLE PERIOD 667/HB/20200/000 AUX 1 AUX 2 AUX 3 SW 1 SW 2 SW 3 Page 6-20 DFM RESET LAMP TEST Issue 10 Type 400 Controller General Handbook 6.3.6 PCB Module The PCBs are held within purpose built PCB modules. Figure 6.3.6 on the following page shows how different combinations of boards are fitted into the module. The small controller can be fitted with one or two PCB modules. The large controller has space for up to four modules. Figure 6.3.6 - Arrangement Of PCB’s Within Module 2 PCBs Positions 1 & 3 2 PCBs Positions 1 & 5 3 PCBs Positions 1, 4 & 5 4 PCBs Positions 1, 2, 4 & 5 PCB Modules Phase Driver Phase Driver Phase Driver CPU Phase SDE/SA Driver or Exp. IO CPU Exp. IO SDE/SA CPU or Exp. IO Example configuration with 8 to 16 phases Exp. IO SDE/SA CPU or Exp. IO Example configuration for the TCSU 1995 contract Exp. IO CPU (with config change facility) 667/HB/20200/000 Page 6-21 IRM SDE RLM Issue 10 Type 400 Controller General Handbook 6.3.7 Power System Refer to drawing 667/DA/20200/etc. The incoming mains supply is terminated at the Electricity Board cutout then feeds to the Master Switch and fuse which isolates everything in the cabinet. As an option a varistor can be fitted on the incoming line to protect the controller against high voltage surges such as induced voltages produced by nearby lightning strikes. A fused supply feed is taken to the Maintenance Socket via an RCD. The controller switch and fuse follow in series with the RCD, thus allowing the mains supply to the controller to be removed whilst leaving power at the maintenance socket. The controller switch supplies the logic power unit and any additional detector power unit. The lamp supply passes through a 20amp filter, solid state relay, the dimming transformer, the dim/bright relay, the two signals ON/OFF relays and finally the phase drivers. The dimming transformer is an auto transformer with input tappings 200, 210, 220, 230, 240 & 250 volts a.c and output tappings 120, 140 & 160 volts a.c. to lower to the mains voltage, to the signal lamps at night. The solid state relay, through which the mains supply voltage to the dimming transformer is taken, provides a noise free method of disconnecting the mains supply from this circuit, whilst the necessary contactors are switched in or out, during power up or a dim-bright change. The logic supplies are derived from a switched mode power unit operated from the mains supply. This unit has high stability and is very tolerant of mains fluctuations. The power unit provides rail voltages of +5V, +12V, -12V and +24v. 667/HB/20200/000 Page 6-22 Issue 10 Type 400 Controller General Handbook 6.3.8 LED Indicators The functions of the various indicators on the logic rack boards are as follows:• Main Processor LED 1 - System Error (Red) - Illuminates when a fault condition is registered in the controller Fault log. LED 2 - Watchdog Fail (Red) - Illuminates when processor fails to perform normal processing sequence. LED 3 - Power On (Green) - Illuminates to show power supplies to the card. • Phase Drives RED, AMBER and GREENs - Illuminate to indicate state of Phase. 6.3.9 Handsets The majority of timing data held in the T400 is accessible and changeable using one of the handsets described below plugged into the RS232 port on the main Processor board. 667/7/13296/000 This is the black GR Electronics version with an LCD (liquid crystal display) and a touch button keyboard Approx. Size:- 78mm (3”) x 146mm (53/4”) An Epson HX20 portable computer with software to allow it to be used as an intelligent terminal. Note that these are no longer available but are still suitable for use where a customer has them. A Portable IBM-compatible computer with suitable software to act as an intelligent terminal. 6.3.10 300mA Controller Residual Current Detector If required by the customer a 300mA RCD can be fitted to the controller. This kit is added in areas of poor earths and is fitted in the controller mains input. This facility is fitted as standard on the controller for the Tuen Mun - Yuen Long LRT system contract. 667/HB/20200/000 Page 6-23 Issue 10 Type 400 Controller General Handbook 6.4 EXPANDED DESCRIPTIONS OF T400 PCBS The following are descriptions of the facilities and functions found on each PCB in the T400. 6.4.1 Main Processor P.C.B (667/1/20221/000) The main processor board controls and monitors the functioning of traffic controllers and pedestrian controllers. The processor is built around an 80188 (CMOS or NMOS) microprocessor, an enhanced version of the 8088 used in the Type 200 controller. This device incorporates the clock generator, the interrupt controller, three timer/counters, various chip select outputs, and a wait state generator, all housed in a 68 pin PLCC package. The peripheral chip select signals generated by the 80C188 are used to select the on-board peripheral devices. These peripherals are:- a RTC with its own crystal and supported by the on-board battery during power down, this provides all the time and date information required by the processor; a phase driver interface capable of driving four phase driver boards, a total of forty-eight outputs; local I/O interface with eight outputs and sixteen inputs, a manual panel; the terminal port with RS232 output signal levels; a watchdog timer facility; and the green/green conflict monitor. The main processor board controls and monitors the many processes required for correct operation of a T400 controller whether used as a traffic controller or a pedestrian controller. The main processor board controls: • • • • • • the lamp mains supply switching and dimming the traffic signal phase drivers four general purpose relay isolated outputs serial data on the handset port illumination of the LED’s on the manual panel devices on the extended system bus The main processor board monitors: • • • • • • • • • green/green conflicts both using software and dedicated hardware the mains zero-crossing point the phase driver lamp supply present outputs the general daylight illumination to control lamp dimming the manual panel switches the handset port UART the time and date using a dedicated RTC chip sixteen general purpose inputs the extended system bus for any peripheral board activity. 667/HB/20200/000 Page 6-24 Issue 10 Type 400 Controller General Handbook Figure 6.4.1 - Main Processor PCB 10.0mm LEVEL 3 ACCESS BUTTON POWER ON LED (GREEN) WATCHDOG FAIL LED (RED) EXTENDED SYSTEM BUS (40 WAY IDC) SYSTEM ERROR LED (RED) E-H A-D TO MANUAL PANEL (34 WAY IDC) TO PHASE DRIVER BOARDS (34 WAY IDC’S) M-P I-L 25 WAY D-TYPE HANDSET SOCKET 16 INPUTS (26 WAY IDC) 4 SIGNAL LAMP RELAY OUTPUTS AND 4 RELAY OUTPUTS (16 WAY IDC) POWER (10 WAY) 10.0mm FRONT 667/HB/20200/000 REAR Page 6-25 Issue 10 Type 400 Controller General Handbook 6.4.2 4 Phase Driver PCB (667/1/20223/000) The 4-Phase Driver Board acts as an interface between the Main Processor Board and the Mains derived interfaces, all signals to and from the Main Processor being electrically isolated from any Mains connections. The Board is an extended 6U Eurocard with 2 Harting type connectors at the rear (Mains interface) and an IDC Transition Header with 400mm Ribbon Cable terminated with a 34 way IDC Socket at the front (Logic interface). The earthed safety cover, on the component side of the Board, also acts as a Heatsink for the Triacs. The interface between the Main Processor Board and the Mains signals are as follows:Twelve inputs from the Main Processor Board. These logic level signals control the Mains supply to the Signal Lamps. i.e. Red, Amber and Green for four Phases. Eleven outputs from the Board, all to the Main Processor Board. These are:ZXO. Lamp Supply Monitor. Dim Request. 4 off +ve Green Monitors. 4 off -ve Green Monitors. Electrical connections to the Processor Board are made via a 34 way IDC connector. To ensure that, when more than one Phase Driver Board is fitted, the IDC connectors are inserted only in the correct position on the Main Processor Board, a Daisychain connection method is used. 6.4.3 2 Phase Driver PCB (667/1/20225/000) The 2-Phase Driver Board with Red Lamp Monitor acts as an interface between the Main Processor Board and the Mains derived interfaces, all signals to and from the Main Processor being electrically isolated from any Mains connections. The Board is an extended 6U Eurocard with 2 Harting type connectors at the rear (Mains interface) and an IDC Transition Header with 400mm Ribbon Cable terminated with a 34 way IDC Socket at the front (Logic interface). This Board is to be used with the T400 Pedestrian Controller since the monitoring of the Vehicle Red Lamps of a Pedestrian Crossing is a requirement in MCE0125 and MCE0145. 667/HB/20200/000 Page 6-26 Issue 10 Type 400 Controller General Handbook The Vehicle Phase Red Signal Lamps are fed from the Vehicle Red Driver, via Resistors. The potential difference across each Resistor is monitored to ascertain the state of the Lamps. The Audible Signal from the Driver is controlled by the Main Processor. The voltage fed to the Audible Signal Driver is checked against a threshold and the result is output to the Main Processor. The Lamp Drivers, Green Voltage Detect, ZXO, and Dim Request Monitors are identical to those used on the T400 4-Phase Driver Board 667/1/20223/000. The earthed safety cover, on the component side of the Board, also acts as a Heatsink for the Triacs. The interface between the Main Processor Board and the Mains signals are as follows:Seven inputs from the Main Processor Board. Six of these logic level signals control the Mains supply to the Signal Lamps. i.e. Red, Amber and Green for two Phases, and the seventh controls the Audible Signal. Eleven outputs from the Board, all to the Main Processor Board. These are:ZXO. Lamp Supply Monitor. Dim Request. 2 off +ve Green Monitors. 2 off -ve Green Monitors. 4 off Red Lamp Monitor Outputs. 1 off Audible Signal Monitor. (Multiplexed with R L Monitor 1). Electrical connections to the Processor Board are made via a 34 way IDC connector. To ensure that, when more than one Phase Driver Board is fitted, the IDC connectors are inserted only in the correct position on the Main Processor Board, a Daisychain connection method is used. 6.4.4 Manual Panel P.C.B (667/1/20227/000) The Manual Panel consists of a custom membrane type keyboard with LED indicators and a toggle action style signals on/off switch. The Manual Panel interface to the Main Processor Board is a 34-way IDC plug. The LEDs are driven via series resistors from driver ICs on the Main Processor board. The switch matrix is scanned in rows and columns to save on the number of connections. 667/HB/20200/000 Page 6-27 Issue 10 Type 400 Controller General Handbook The membrane switches are all debounced in software to protect against unintentional operation. Because of this, it is necessary to hold down a desired key for about half a second to ensure recognition by the software. 6.4.5 Expansion I/O PCB (667/1/20229/000) The Expansion I/O board provides the type 400 controller with an additional sixteen buffered inputs, and sixteen relay isolated outputs. Up to three of these boards may be used in a system so address decoding is provided to identify each board by means of a BCD switch, and the setting of the switch is visible on the front edge of the board, to guard against boards being set up with the same address in a system. The sixteen buffered inputs use comparators with protection against induced voltages and direct application of mains voltages. The input to the buffer is normally held high by a pull-up resistor. The sixteen relay buffered outputs are clean contacts which are normally open. Changeover relays are used to give some normally-closed outputs, and provision is made for 22Ω contact protection resistors on some outputs in addition to the normal 180Ω contact protection resistors. On power up or Reset all the output relays go to the inactive state. Sixteen buffered inputs and sixteen relay buffered outputs are available. Each of these signal lines can isolate an inadvertent application of mains voltage from the rest of the system even if it results in damage to the circuit associated with that particular signal line. The inputs are capable of meeting the requirements of MCE 0141, MCE 0125, and MCE 0145, and can reject induced mains voltages caused by capacitive coupling between signal cables and adjacent mains cables. There are sixteen relay isolated outputs, which are normally open with 180Ω contact protection resistors. Four of these outputs are configurable; the standard output is a normally open relay contact using a 180Ω contact protection resistor, the two required alternatives are:- a) a normally closed contact using a 180Ω contact protection resistor, and b) a normally open contact able to switch higher currents than the standard output and with a 22Ω contact protection resistor. The selection between the different output configurations is achieved by using different pins in the output connector rather than any links on the board. A standard cable is used with a Berg type socket with individually crimped wires which select the standard normally open contact with the 180Ω protection resistor. By moving the contacts in the header using the appropriate tool the alternative output configurations can be provided. 667/HB/20200/000 Page 6-28 Issue 10 Type 400 Controller General Handbook This board includes an identification byte which specifies this board as an Expansion I/O board. 6.4.6 Expansion I/O PCB (667/1/20229/001) The Expansion I/O board provides the type 400 controller with an additional sixteen buffered inputs, and sixteen relay isolated outputs. Up to three of these boards may be used in a system so address decoding is provided to identify each board by means of a BCD switch, and the setting of the switch is visible on the front edge of the board, to guard against boards being set up with the same address in a system. The sixteen buffered inputs use comparators with protection against induced voltages and direct application of mains voltages. The input to the buffer is normally held high by a pull-up resistor. The sixteen relay buffered outputs are clean contacts which are normally open. Changeover relays in two positions of each group of eight outputs give the option of selecting some normally-closed outputs. 68Ω contact protection resistors are used on all outputs. On power up and whenever the RESET or Watchdog flag lines are active all the output relays go to the output state. Sixteen buffered inputs and sixteen relay buffered outputs are available. Each of these signal lines can isolate an inadvertent application of mains voltage from the rest of the system even if it results in damage to the circuit associated with that particular signal line. The inputs are capable of meeting the requirements of MCE 0141, MCE 0125, and MCE 0145, and can reject induced mains voltages caused by capacitive coupling between signal cables and adjacent mains cables. There are sixteen relay isolated outputs, which are normally open with 68Ω contact protection resistors. Four of these outputs must be configurable; the standard output is a normally open relay contact, the required alternative is a normally closed contact. The selection between the different output configurations is achieved by using different pins in the output connector rather than any links on the board. A standard cable is used with a Berg type socket with individually crimped wires which select the standard normally open contact with the 68Ω protection resistor. By moving the contacts in the header using the appropriate tool the alternative output configuration can be provided. This board includes an identification byte which specifies this board as an Expansion I/O board. 667/HB/20200/000 Page 6-29 Issue 10 Type 400 Controller General Handbook 6.4.7 SDE/SA P.C.B (667/1/20231/000) The SDE/SA processor card is built around an 80C85 microprocessor, a CMOS version of the 8085 used on the T400 SDE/SA board. The design is much the same as that used for the T400 although CMOS and HCMOS components are used throughout to reduce the power consumption substantially. The maximum number of inputs is 32 which allows a maximum of 16 assessors since two loops are required per assessor. All of these inputs are buffered. Unused SDE/SA assessors may be used as ordinary detector inputs to the controller. Communication with the main processor is achieved by the use of a Shared RAM area which is located on the SDE/SA board. The main processor reads and writes to this area via the Extended System Bus. Power for the SDE/SA board is derived from the T400 main power supply. The 5V DC supply comes on board via the Extended System Bus Cable while the 24V DC supply is accessed via the detector input cable. Soundmark type test facilities are provided by using an on board jack socket and a thumbwheel switch to dial up any detector pair. The board is able to run existing T400 SDE/SA software with a few slight alterations reflecting hardware configuration changes. 667/HB/20200/000 Page 6-30 Issue 10 Type 400 Controller General Handbook 6.4.8 Ancillary Processor P.C.B (667/1/21611/000) The Ancillary Processor is a double extended Euro sized PCB which connects to the T400 Main Processor via the Extended System Bus. Configuration information for the Ancillary Processor comes from the Configuration PROM on the T400 Main Processor PCB. Handset access to the Ancillary Processor is via the handset socket on the Main Processor board. 6.4.8.1 Functional Applications • Integral Red Lamp Monitor • Integral TC12 OTU • Integral Lamp Monitor 6.4.8.2 Physical Description Mechanical Construction - The PCB is located within the T400 PCB Module, along side the other T400 Logic PCB’s. It interfaces to the T400 Main Processor PCB via the Extended System Bus ribbon cable, in a similar way to the existing SDE/SA PCB. Current Sensors & Voltage Monitor - There is a connector on the PCB to allow connection of the current sensors and a voltage monitor which are used for Red Lamp Monitoring and/or UTC lamp monitoring. Telephone Line Interface (OTU) - There is a BT style Jack provided to allow 2 or 4 wire leased line connection, when used as an integral OTU. Test Jack Sockets (OTU) - A Jack socket is provided to allow connection of a TC12 Instation Test Set, for use in UTC systems. This permits monitoring of line levels and communication data during installation and maintenance etc. 6.4.8.3 Ancillary Processor PCB Electronics The Ancillary Processor PCB is based on the Intel 80188 microprocessor, which is the same processor as used on the T400 Main Processor PCB. The peripherals to the processor are the: Firmware PROM RAM (battery supported) Shared RAM A to D Converter with Analogue Multiplexer Serial Interface (USART) with integral Modem and Line Interface Watchdog Monitor Facility Status LED Indicators 667/HB/20200/000 Page 6-31 Issue 10 Type 400 Controller General Handbook Figure 6.4.8 - Ancillary Processor PCB Status LED’s PLA 40-Way Extended System Bus Connector LP2 - Carrier Detect LP3 - Transmit Confirm LP4 - Watchdog Fail SK2 - Reply Line Jack Socket SK3 - Control Line Jack Socket ON Push down this side for ‘open’ switch (i.e. ‘0’) Lithium Battery Switch - S2 S1 - 2/4 Wire Selector S3 - Line Level Switch Lithium Battery - B1 Serial No. 600Ω S4 - 600Ω / High Impedance Selector Hi-Z Covered Area SK1 - 6-Way Telecom Socket Cover Fixings 667/HB/20200/000 Page 6-32 PLB 60-Way Connector to LMU Inputs Issue 10 Type 400 Controller General Handbook 7. GUIDE TO T400 SPECIFICATION FORMS 7.1 GENERAL This guide is to assist Traffic Engineers in the completion of the Siemens T400 Controller Specification Forms (667/DJ/15900), to enable Siemens to submit quotations and supply traffic control equipment which provides the desired performance. Where necessary refer to the facilities handbook 667/EB/20200 to assist in the understanding of the information to be given on the forms. The various pages of the forms are numbered in Roman numerals. Only those forms required for a particular installation need to be completed, the sheets are then numbered as required. A set of blank specification forms is contained in Appendix A. Some customers are able to configure their own controller EPROM’s. In order to assist in the understanding of the configuration procedure, reference should be made to the Intersection Configurator 003 user’s handbook (667/HD/15900/000). 667/HB/20200/000 Page 7-1 Issue 10 Type 400 Controller General Handbook 7.2 LIST OF FORMS FORM I FORM II FORM III FORM IV FORM V FORM VI FORM VII FORM VIII FORM IX FORM X FORM XI FORM XII FORM XIII FORM XIV FORM XV FORM XVI FORM XVII FORM XVIII FORM XIX FORM XX FORM XXI FORM XXII FORM XXIII FORM XXIV FORM XXV FORM XXVI 667/HB/20200/000 FRONT SHEET BASIC SITE DATA USE OF PHASES PHASE INTERGREENS USE OF STAGES PROHIBITED AND ALTERNATIVE MOVEMENTS PROHIBITED AND ALTERNATIVE MOVEMENTS DETECTOR AND PUSH BUTTON INPUTS MODE PRIORITY AND DISABLED MODES LIMIT VALUES SPECIAL CONDITIONS FOR STAGE CHANGE SDE/SA EQUIPMENT URBAN TRAFFIC CONTROL URBAN TRAFFIC CONTROL MASTER TIME CLOCK AND CABLELESS LINKING CABLELESS LINKING PLAN DATA ADDITIONAL SWITCHES AND LEDs AND HURRY CALLS LMU EXTEND INTERGREENS EXTEND ALL RED INDEPENDENT INTERGREENS DEFINITIONS OF TIMESWITCH PARAMETERS PEDESTRIAN LINK(S) PRIORITY/EMERGENCY REQUIREMENTS PRIORITY/EMERGENCY TIMINGS NON-UK SIGNAL SEQUENCES MANUAL STEP ON FACILITY Page 7-2 Issue 10 Type 400 Controller General Handbook 7.3 FILLING OUT THE FORMS Form I - Front Sheet Every controller specification should begin with a ‘Front Sheet’ form. This should be completed as far as possible, noting any standard Regional or Local Authority Specification and quotation/order numbers. Form II - Basic Site Data This form should show the basic phase movements for each stage. If Parallel Stage streaming is used then the stream No, should be indicated. One form could show 2 streams as long as they were kept apart i.e. 1st stream using Top 4 boxes and 2nd stream using Bottom 4 boxes, but they would have to be clearly identified. Otherwise use 1 form per stream. The stages in the streams should be numbered consecutively. This form should also be used to indicate which stages correspond to start-up and to All Red. Form III - Use Of Phases An entry should be made for each phase required (including dummies). (a) Condition of Phase Appearance There are 4 types (0 - 3) for the conditions for which a phase can appear. Type 0 - Phase always appears The phase will always appear during its nominated stage(s). This is the normal phase condition. Type 1 - Phase appears only if demand exists at start of interstage Under this type the phase will only appear if a demand exists for it at the beginning of amber leaving of the previous stage. Typical use simple parallel pedestrian phase dependent on pushbutton. Type 2 - Phase appears only if demand exists during the stage or preceding inter-stage Demand dependent phase which can appear at any time during the stage if it is demanded. Typical use is filter green arrow. 667/HB/20200/000 Page 7-3 Issue 10 Type 400 Controller General Handbook Type 3 - Phase appears if demanded at any time during the stage up until the window time expires The demand for a phase of this type can be inhibited by the output of a special timer (‘Window-Time’) which is started when the first phase max time is started. A typical use of this type is for a demand dependent pedestrian phase which does not want to prolong the stage maximum when an opposing demand has been requested. (b) Conditions of Phase Termination The Type 400 Controller provides 3 types (0 - 2) for the termination of a phase. Type 0 Terminates at end of stage This is the standard termination type - the phase showing amber leaving, blackout, flashing green as required. Type 1 - Terminates when associated phase gains Right of Way This type is normally used for left turn filter arrows. Type 2 - Terminates when associated phase loses Right of Way This type is normally used for right turn indicative arrows. (c) Type of Phase Enter a tick in the required column. (d) Conflicting Phase Combinations Enter a ‘C’ for all conflicting phase combinations. (e) Phase Timings Enter required timings. 667/HB/20200/000 Page 7-4 Issue 10 Type 400 Controller General Handbook Form IV - Phase Intergreens This form has four sections. (a) Basic Phase Intergreens An intergreen time (in seconds) should be entered for every conflicting phase. (b) Additional Phase Delays This part of the form is used to detail any additional delay periods that may be required for particular phases. (c) Starting Intergreen Period This is the initial intergreen time period that is provided when the controller is first switched on. The time entered must not include the Amber period leaving time (3 secs) of the phases that show RED in STAGE 1. 667/HB/20200/000 Page 7-5 Issue 10 Type 400 Controller General Handbook Form V - Use Of Stages This form describes the basic stage structure of the controller and comprises four sections. (a) Active Phases in each Stage A ‘tick’ should be inserted in each box to define what the phase/stage relationship is. Use a second Form if more than 7 stages are required re-numbering the stages on the second sheet from 8 to 15. The related stream number, and window time if required should be indicated. All dummy and demand dependent phases should be included. The bottom line of this section (Max Revertive Demand Phase) should be filled in if, a demand for a different phase is required if this Phase is terminated with an extension timer active. Note:- For parallel Stage Streaming each stream should have its own all red stage, if the all red condition is required. (b) Fixed Cycle Time Requirements A. Define Fixed cycle time mode. Use additional sheets for each stream. The fixed time cyclic order of stages should be defined together with the stage time in seconds. One of the stages should be the Start-up stage. OR B. Fixed cycle running to current Max. Tick the box for this mode and tick any phase which is demand dependent. Note all other phases will always appear and vehicle phases will run to max. (c) Arterial Reversion for each Stream Insert the stage number(s) or Phase letter(s) if this facility is required. (d) Manual Selection Complete this section if Manual Stage control is required by indicating which stage(s) are to be associated with each button required. 8 pushbuttons are available, button 0 being allocated to All Red. 667/HB/20200/000 Page 7-6 Issue 10 Type 400 Controller General Handbook Form VI/VII - Prohibited and Alternative Stage Movements Use this form to describe the permissible stage to stage movements for the various modes of operation. For each mode of operation an appropriate movement table should be completed or if modes movement tables are identical indicate which modes each table applies to. In CLF mode due care must be taken to ensure that controller does not run stages for too long during plan changes particularly short filter stages or pedestrian stages. Prohibited moves should not be programmed. They should be changed to alternative moves. More than one mode can apply to one sheet. Form VIII - Detector and Push Button Inputs After defining the detector location, ticks should be inserted in the appropriate boxes to define the detector or push button requirements. Phase letter to be inserted for the demand and extension. Call/Cancel delay periods, LRT Request delay period, detector type, supply voltage and Fault Monitor Time and fault monitor high limit value should also be indicated. Normal Detector inputs close the Relay Contacts and are treated as ‘low’ inputs. If it is required to have Open Circuit Relay Contacts for detection then a tick should be placed in the “Inverted” column on this form. U/D refers to uni-directional detectors that will detect vehicles moving in one direction only. The Call Delay Column refers to Call/Cancel Units used for vehicles. 667/HB/20200/000 Page 7-7 Issue 10 Type 400 Controller General Handbook Form IX - Mode Priority and Disabled Modes This form comprises two sections: (a) Mode Priority The modes under which the controller shall operate need to be defined in this section. Each mode required, should be given a number from 1 to 9 (1 is top priority) or an ‘X’ if it is not required. Particular attention should be paid to the priority of any Manual facilities with regard to Cableless Link operation, such that CLF does not disable Manual. Note CLF should always be requested so that CLF could be added by the Handset. The capabilities of the Manual facility switch, located on the internal Manual panel, should be defined in the bottom boxes if any of the modes defined are not required to be selectable. Box 2 should define if Manual only allowed if:(i) Handset is inserted. (ii) MND is entered on the Handset Note:- a priority state should be entered for either Vehicle Actuated (VA) or Fixed Time (FT) not both. (b) Disabled modes This section of the form allows modes which have been selected to be disabled for certain streams or for all streams for certain conditions. e.g. CLF on one stream allows other streams to still work VA. Also Manual control could be disabled at certain times of day. Note that Part Time and Selected Manual Control modes may only be disabled on all streams simultaneously. 667/HB/20200/000 Page 7-8 Issue 10 Type 400 Controller General Handbook Form X - Limit Values This form details the upper and lower limits for certain timings which limit any handset changes to these timings, see section 2.6 for details. The defaults for all of these range limits are shown on the forms in Appendix A. These can be changed if necessary within the ranges given below :(a) Phase Intergreen Low Value High Value 2 secs for traffic phases (red/amber time) 0 secs for ped. and Green Arrow phases 199 secs (b) Minimum Green Times Low Value High Value 0 secs 255 secs (c) Phase Delay (d) Starting Intergreen Low Value High Value Low Value 0 secs 255 secs 0 secs High Value 255 secs (e) CLF Group Time Low Value High Value 0 secs 255 secs (f) Maximum Green Low Value High Value 0 secs 255 secs (g) Pedestrian Blackout/ Flashing Green Low Value High Value 0 secs 255 secs (h) Green Extension Low Value High Value 0 secs 10.0 secs (i) CLF Offset Time Low Value High Value 0 secs 255 secs (j) Priority 1st Delay Low Value High Value 0 secs 255 secs (k) Priority 2nd Delay Low Value High Value 0 secs 255 secs (l) DFM High Value 254 hrs 667/HB/20200/000 Page 7-9 Issue 10 Type 400 Controller General Handbook Form XI - Special Conditions For Stage Change/Extra Requirements Some Stage to Stage movements may require special conditioning. This form should be used to describe the various input states and phase status that are required for the special condition to be satisfied. The form is also used to list any special extra requirements that have not been specified anywhere else, (e.g. requirements for linking to another controller, Part-Time mode should be configured for Flashing Amber, Parallel Stage Stream influence and cross linking etc). Usually these extra requirements will be ones that require special conditioning. Further sheets should be added for different modes, but if special conditions are identical in certain modes, then these should be listed on the same form. Form XII - Speed Discrimination/Speed Assessment Equipment (SDE/SA) This form need only be completed if the controller is to be used on an intersection having high-speed vehicles. The equipment type (SDE or SA) should be specified together with the number of assessors and their function. If SDE is selected only assessor types 1, 2 or 3 are available. If SA is selected all assessors must be type 4. An Extra-Intergreen period should be specified for every phase that is equipped with an assessor. Following MCK 1057 amendment it is normal for only high speed extensions to provide extra I/G. The right hand box would normally be ticked to prevent X, Y, Z detector extensions from providing extra clearance. Note there is an option to use 12 foot loop spacing if required. 667/HB/20200/000 Page 7-10 Issue 10 Type 400 Controller General Handbook Form XIII - Urban Traffic Control The top left table to be filled in with any control and reply bits that communicate via an OTU. Note any bits to an associated controller should have a ‘*’ by the bit. Where force bits are required to be demand dependent add a # (hash) and fill out the bottom right hand table with the phase demands which are to be considered as requests for that force. This includes both demands originating from the street or from D bits. If there is no hash each force bit will act irrespective of any demands. Demand bits (Dx, D1, D2 etc.) are numbered from 1 upwards and the tables on the right determine their function. The top table determines which phases, or stages, or combinations will be demanded by each bit. Dx is made larger as up to 16 stages and or 16 phases could be required. Similarly in the second table on the right hand side, insert which phases should be extended by each ‘D’ bit. In the third table on the right hand side fill in the stage demands which will cause a reply. (A reply will occur if that stage has a demand). Alternatively specify the phase demands which are required to reply. NOTE:TO AVOID CONFUSION IT IS ESSENTIAL THAT CONTROL AND REPLY BITS ONLY USE THE NOTATIONS ON THIS SHEET. Form XIV - Urban Traffic Control Tick any square which requires the reply bits along the top to be active during the conditions on the left hand side. If the ‘other’ column is used, detail which reply bit this information should be sent on. The controller fault bit is set if an entry is made in any Fault Log Flag except for the flags associated with DFM failure, Priority DFM failure and Lamp Supply failure. For a complete list of Fault Log Flags, refer to the Handset Handbook 667/HH/20200/000. 667/HB/20200/000 Page 7-11 Issue 10 Type 400 Controller General Handbook Form XV - Master Time Clock and Cableless Linking This form need only be completed if time-switch and/or Cableless link facilities are required. First select the ‘Day Type’ (0 - 9) from the list provided, then enter the time that the function is required to operate (use 24 hour clock notation). Last of all define the function that has to be performed, along with a description of it. Add extra sheets as required up to a total of 64 entries. Form XVI - Cableless Linking Plan Data This form need only be completed if Cableless linking is required. For the left hand table indicate the Plan number and influence set used, then allocate a Group time (in seconds) for each group used, (0 seconds if you want it to be skipped, a time may be added using the handset at a later date, see Appendix A). For the right hand table indicate the influence set number, and then allocate a Group Influence and Related Stage for each group required. One Influence set may be used for more than one plan. Note:- With parallel stage streaming indicate Group Influence and Related stage for each stream required, otherwise just for Stream 0. NOTE FOR INFLUENCE 0, 3 AND 7 A STAGE IN THAT STREAM MUST BE ENTERED. Add extra sheets as required for up to 8 plans. 667/HB/20200/000 Page 7-12 Issue 10 Type 400 Controller General Handbook Form XVII - Additional switches and LEDs and Hurry Calls This form comprises four parts :(a) Additional Switches and LEDs There are three spare switches and three spare LEDs on the Manual Panel. This form is used to specify if a function is to be allocated to the switch or LED. The switches and LEDs may all be used independently, but if a toggle action is specified then the associated LED will operate in conjunction with the switch, i.e. press once to turn the switch on and the associated LED illuminates to indicate that the switch is on, press again and the LED will go off to indicate that the switch is off. The default action of the switch is that of a toggle switch. If it is required to use the switch as a momentary switch then a tick should be placed in the “momentary” column against the particular switch. When used as a momentary, the switch will be on while the switch is pressed. If the switch is specified as Momentary or the switch is not used, then the associated LED may be used independently for any purpose. Describe the functions required for the switches and LEDs in the “Use” column. (b) Hurry Call(s) All information relating to any Hurry Calls should be specified in this table. (c) Optional Filter green arrow in Manual This section should be used to indicate whether the Filter green arrow(s) should appear, not appear or be demand dependent during Manual mode. (d) Part Time Mode If this mode is required then the switch off stage should be specified here. Where parallel stage Streaming is used enter one stage for each stream. Any special part time requirements should be detailed on Form XI. 667/HB/20200/000 Page 7-13 Issue 10 Type 400 Controller General Handbook Form XVIII - Red Lamp Monitor This form is used where Red lamp monitoring is used as defined in MCK 1061. Note that if the new enhanced red lamp monitor system is required, the original ‘extend intergreen’ page should be ignored. Form XIX - Extend All Red by Detectors If All-Red Extension facilities are required this form should be completed by indicating the Extend All Red Moves for each unit required, the effect of this facility in certain modes and the All Red extension time (per stream required). Note:- The All Red Maximum time is measured from the point at which the first phase in the new stage would normally start its Red to Green transition period (usually Red Amber). The extension time is measured from the point at which the loop becomes unoccupied. Form XX - Independent Intergreens Fill in any phases which are not to be held by the intergreen of a terminating phase. Form XXI - Definition of Time Switch Parameters This form is used in conjunction with form where a time switch is specified as function 2, (introduce an event time table). Each line of this form represents a switch, (0-15). Facilities are allocated to these switches, as required. The parameters, (0-15) can then be filled out with any combination of the switches, as required. e.g. select Max set B. If this sheet is filled in, it should be included immediately following form XV. 667/HB/20200/000 Page 7-14 Issue 10 Type 400 Controller General Handbook Form XXII - Pedestrian Link This form need only be completed if linking to an adjacent Pedestrian/Pelican controller is required. Form XXIII/XXIV - Priority/Emergency Mode This form need only be completed if LRT and/or Emergency vehicle priority facilities are required. (a) Basic Requirements For each priority unit required its type, related phase and monitoring/gap timings should be specified. The configured conditioning of ‘Priority Demand’, ‘Revertive Priority Demands’, ‘Inhibit Times’ and ‘Priority DFM Self - Reset’ should also be stated. Note:Some ‘Enabled’ states are conditional on other facilities also being enabled. The number(s) corresponding to the priority unit(s), which are required to be inhibited, should be entered into the next box. The next section should specify which demanded phase(s) will be serviced when a move to the priority phase takes place, (if any). The last section specifies which phase(s) will be demanded when a move to the priority phase takes place, (if any). Note:Phase(s) specified in “ENFORCE DEMAND” must also appear in ‘ALLOWED VA DEMANDS’. (b) Time Periods The timings for each priority unit should be specified on this form and the plan type indicated in the section provided. 667/HB/20200/000 Page 7-15 Issue 10 Type 400 Controller General Handbook Form XXV - Non-UK Signal Sequences This form is only applicable to some export requirements. If the signal sequences as shown in the table are required, then a tick should be placed in the box at the top of the page. It is possible to specify two methods of operation for the Signals on/off switch. In both cases, when the signals are switched off, the controller continues cycling as normal, except that the signals are no longer illuminated. If a tick is placed in the box against “Immediate Signals On”, then when the Signals on/off switch is set back to the “on” position, the signals immediately illuminate at whatever point they were, in the controller cycle. If a tick is placed in the box “As Startup” then the controller will go through the startup sequence to illuminate the signals. If the signal sequence specified includes flashing e.g. flashing green in the pedestrian sequence, then unless otherwise specified the flashing on and off times will both be 400ms. If it is required to have different on or off times, then the required value(s) should be entered in the boxes provided on this form. Form XXVI - Manual Step-On Facility This is an alternative to full UK Manual mode operation, where instead of having a different button to select each stage (or pattern of stages in Parallel Stage Streaming), one button makes the controller step through a predefined pattern of stages. In the boxes to the side of “Stream 0”, enter the stage numbers in sequence from left to right, to specify the order in which the stages should appear. If there is more than one stream, repeat this process for the other streams. Stages that appear in the same columns of the form will run together. The same stage may be specified more than once within the Manual cycle if required. This may occur by either double appearance or the same stage in one stream running with two separate stages in another stream. Movement from one stage to the next, or in the case of parallel stage streaming from one pattern of stages to the next, occurs in one of two ways. The first way is by operation of the Manual Step On button. In this case a tick should be placed in the box at the bottom of the column indicating that the Manual Step On button must be operated in order that the controller moves from the stage pattern specified. The second way is to move automatically after the time as defined in the box (instead of entering a tick) onto the next stage, or pattern of stages. 667/HB/20200/000 Page 7-16 Issue 10 Type 400 Controller General Handbook 8. T400 MOD STATE CONTROL AND CONFIGURATION All these details are contained in the document 667/SU/20200/000. A copy of this document is contained in Appendix B. 667/HB/20200/000 Page 8-1 Issue 10 Type 400 Controller General Handbook Appendix A - SPECIFICATION SHEETS Appendix A contains a copy of document 667/DJ/15900/000 follows:- 667/HB/20200/000 Page 1 Issue 10 Type 400 Controller General Handbook Appendix B - MOD STATE CONTROL AND CONFIGURATION Appendix B contains a copy of document 667/SU/20200/000 follows:- 667/HB/20200/000 Page Error! Main Document Only.-1 Issue 10 Type 400 Controller General Handbook Appendix C - 50-0-50 VOLT CONTROLLER C.1 50-0-50 VOLT CONTROLLER Note :- This version of the T400 does not meet DTp specification MCE0141 in respect of dimming voltages and voltage sensing. This is inherent in the 50-0-50 volt output. The 50-0-50 version of the controller does meet the equivalent figures which are specified by (50+50)/240. The 50-0-50 volt controller is a version of the standard so that the voltages on the cables leaving the controller are 50 volts A.C. nominal with respect to earth, rather than the standard 240 volts and are transformer isolated from the incoming mains supply. The voltages on feeds an auxiliary devices such as regulatory signs, microwave detectors, solar cells etc. is nominally 50-0-50 volt rms with the centre tap taken to earth. Low voltage dc supplies for detectors (nominal 24 volts) are unaffected. An additional circuit breaker is provided to enable the 50-0-50 volt feeds to be isolated with a single switch without switching the controller logic off. This also provides protection if either of the 50 volt feeds is shorted to earth. (This does not include the 24 volts intended for supplying external loop detectors.) C.1.1 Signal load limitations The current supplied to the controller is limited compared to the standard 240 volt T400 controllers detailed below. Figures assume 0.614A per lamp. For a large outercase controller fitted with a 1.5 kVA dimming transformer. Maximum load per individual phase Maximum load per phase board Total lamp O/P load per controller - 4 amps (6 lamps on at one time*) 10 amps (18 lamps on at one time) 15 amps (25 lamps on at one time) For a small outercase controller fitted with a 1.0 kVA dimming transformer. Maximum load per individual phase Maximum load per phase board Total lamp O/P load per controller - 4 amps (6 lamps on at one time) 10 amps (18 lamps on at one time) 10 amps (18 lamps on at one time) Note that the regulatory sign load, solar cell load and any other low voltage ac loads such as pedestrian audio, wait box, etc, all form part of the controller load. * These figures assume each lamp transformer (on load) takes 0.614 Amps (worst case). 667/HB/20200/000 Page C.-1 Issue 10 Type 400 Controller General Handbook C.1.2 Miniature Circuit Breaker (MCB) A miniature circuit breaker is used to provide overload protection on the lamp supply outputs. It also protects the outputs to the regulatory signs, MVDs, Solar cells etc. The MCB acts as a switch enabling the maintenance to be carried out on the signals heads etc without stopping the controller logic. Note : When the signals are switched off using the MCB, controller fault log 17 (Lamp supply fail detected) will be set. This should be reset using handset command RFL=1 when the MCB is returned to the normal position. C.1.3 Street Equipment C.1.3.1 Solar Cell A 110 Volt version of the solar cell, derived from the 50-0-50 volt supply, via a transformer mounted in the adjacent signal head. C.1.3.2 High Intensity Signals All signals and pedestrian wait boxes must be modified using transformers designed for 50-0-50 supply. The H.I. have tapped secondaries to compensate for the increased voltage drop that is caused by operating at a lower voltage and higher current. Two taps are available selected on the basis of cable length :- 0 to 60 metres and 61 to 120 metres for distances greater than this 2 cores should be used for each feed. Note a separate return should be used for each head or wait indicator with a separate feed per optic.. C.1.3.3 Regulatory Signs A modification to standard regulatory signs is required, incorporating an auto transformer to step he 50-0-50 up to 110 volts for the fluorescent tube circuits. C.1.3.4 Microwave Vehicle Detectors The microwave vehicle detectors must be the type 110 volt version which allows operation on the 50-0-50 volt supply using the regulatory supply. C.1.4 Dual Solar Cell The solar cell facility on a 50-0-50 controller can be modified to enable two solar cell outputs to be provided. These are connected to the controller via 667/HB/20200/000 Page C.-2 Issue 10 Type 400 Controller General Handbook two relays mounted within the controller. One of the solar cells acts as a ‘master’ causing the controller to change from ‘dim’ to ‘bright’ and ‘bright’ to ‘dim’ in the normal manner. This facility is not available on a 240 volt controller. The two solar cells are then monitored and when of the following two fault conditions occur the signals will be set to the ‘bright’ state. 1. If both solar cells outputs are in different states for more than 16 hours. This is adjustable with the range of 0 to 255 hours using handset command PIR0. The value which is assigned to handset command PIR0 will give required monitor time in hours, with the default setting being 16. 2. If the solar cell outputs are in different states for more than 45 minutes. This is adjustable with the range of 0 to 255 minutes using handset command PIR1. The value which is assigned to handset command PIR1 will give required monitor time in minutes, with the default setting being 45. When either of the above two faults occur the controller fault log 27 will be set as shown below. The fault log will remain set until reset using the handset. While the fault log is active the signals will be held in the nondimmed state. FLF 27 = 1 If the solar cell outputs remain in the same state for more than 16 hours. FLF 27 = 2 If the solar cell outputs are in different states for more than 45 minutes. FLF 27 = 3 If both the above conditions occur. C.2 GAS PLINTH A gas plinth can be fitted below the controller to inhibit any gases from entering the controller, the gas is allowed to escape via the vented plinth. All cables entering the controller must pass through the gas plinth with cable glands being used to seal the cables. There are a maximum number of cables that can enter the controller when a gas plinth is used, as detailed below :Small case controller Large case controller 667/HB/20200/000 - 18 cables (Including electrical supply) 27 cables (Including electrical supply) Page C.-3 Issue 10 Type 400 Controller General Handbook Appendix D - ADDITIONAL REQUIREMENTS FOR TUEN MUN D.1 LAMP DRIVE CAPABILITY Maximum lamp load for total controller (including regulatory signs and red/amber) Maximum lamp load for one phase switch card (4 phases, including red/amber) This is limited by the fuse on the PCB Maximum load for one triac output on a phase switch card Amps Tungsten Halogen Lamps Total Watts 20A 63 4000 10A 19 1200 4A 12 800 N.B. The Lamp and Wattage columns are equivalents for the currents shown, based on a 200 volts supply. Power Factor greater than 0.9 D.1.1 Lamp Load Per Aspect (Watts) Bright Tungsten filament 40 watt Wait Indicator 50 watt High Intensity Regulatory sign 6 42 63 63 Dim 160v 57 32 43 - Dim 140v 38 - Dim 120v 47 22 32 - D.1.2 Dimming Transformer Transformer 120v 140v 160v 120v 140v 160v 120v 140v 160v 1kVA 1.5kVA 2kVA Notes:- Transformer Tap Maximum number of lamps on a controller continuously illuminated 31 28 27 46 41 37 62 55 51 Maximum number of lamps illuminated for a short time#, e.g. Red/Amber 63 63 63 63 63 63 63 63 63 # = Limited by controller lamp supply fuses F5 & F6 which can be a maximum of 20 amps. These figures are based on a 200 volt RMS supply. All figures are for tungsten halogen lamps. 667/HB/20200/000 Page D.-1 Issue 10 Type 400 Controller General Handbook D.1.3 Calculation Of An Intersections Power Requirements The following worked example is based upon a mains supply of 200 volts rms. Firstly the average lamp power for the junction is calculated, this allows the selection of the dimming transformer. Secondly the average lamp power is added to the average controller power to give the total average power which a local authority may use to estimate running costs. Average lamp power is calculated as follows:For every signal head, 1 lamp is illuminated at 63 watts, every wait indicator is illuminated at 42 watts, every regulatory sign is illuminated at 63 watts. Therefore considering our theoretical junction Figure 2.2 we have the following result. a) b) c) 1 lamp per signal head at 63 watts Every wait indicator illuminated at 42 watts Every regulatory sign illuminated at 63 watts 63 x 12 42 x 4 63 x 1 = = = 756W 168W 63W 987W To select the dimming transformer first select the tapping and then choose appropriate power rating from following table. Dimming Voltage 120v 140v 160v 667/HB/20200/000 Power load watts at full voltage load < 1969 1969 < load < 2898 2898 < load < 3906 load < 1764 1764 < load < 2583 2583 < load < 3465 load < 1700 1700 < load < 2331 2331 < load < 3213 Page D.-2 Dimming transformer 1.0K VA 1.5K VA 2.0K VA 1.0K VA 1.5K VA 2.0K VA 1.0K VA 1.5K VA 2.0K VA Issue 10 Type 400 Controller General Handbook The average controller power is calculated as follows:A controller with dimming is 105 watts plus the number of detectors required at 6 watts/board for every Siemens ST detector. Therefore, for our theoretical junction Figure 2.2 the result is as follows:1 x Controller 1 x Siemens ST detector 105 watts 6 watts 111 watts For the total average power to aid electricity authorities with the running cost estimates, the lamp average power must be added to the controller average power. e.g. + 987 watts 111 watts 1098 watts D.1.4 Calculating The Lamp Supply Fuse Required In order to calculate the lamp supply fuse required the worst case red/amber is used, i.e. the red/amber during which the most signal heads are at red/amber. For the theoretical junction Figure 2.2 this is during the move 2 to 1 with 5 signal heads at red/amber. Signal heads at red/amber x 126 watts Signal head with 1 lamp illuminated x 63 watts Every wait indicator illuminated x 42 watts Every regulatory sign illuminated x 63 watts 5 x 126 7 x 63 4 x 42 1 x 63 = = = = 630W 441W 168W 63W 1302W The lamp power is then re-calculated using 126 watts for every signal head at red/amber. This gives us the peak lamp power, e.g. for our theoretical junction Figure 2.2. This is divided by 200 volts to give us the peak lamp current, e.g. 1302 ÷ 200 = 6.5 Amps. Then from the following table we derive our fuses: Peak Lamp Current 0.0A < Current < 6.5A 6.5A < Current < 9.5A 9.5A < Current < 14A 14A < Current < 19A 667/HB/20200/000 Page D.-3 Fuse 7A 10A 15A 20A Issue 10 Type 400 Controller General Handbook D.2 HANDSET RANGE LIMITS, DEFAULT VALUES Unless otherwise stated all controllers will be provided with default timings for the limits as shown below:TUEN MUN a) D.F.M. b) Hurry Call Delay Hurry Call Hold Hurry Call Prevent c) Phase Delay d) Starting Intergreen e) Green Extension f) Maximum Green g) h) Pedestrian Blackout/ Flashing Green C.L.F. Group Time i) Minimum Green Times j) Phase Intergreen Time k) CLF Offset l) Priority First Delay m) Priority Second Delay 667/HB/20200/000 High Value Low Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Low Value High Value Page D.-4 24 hrs 0 hrs 0 secs 180 secs 5 secs 180 secs 0 secs 120 secs 0 secs 20 secs 3 secs 20 secs 0 secs 5 secs 0 secs 100 secs 3 secs 20 secs 0 secs 120 secs 5 secs 20 secs 5 secs 20 secs 0m0s 0 m 120 s 0 secs 120 secs 0 secs 120 secs Issue 10 Type 400 Controller General Handbook D.3 INPUTS AND OUTPUTS The following I/O allocation will be given to all controllers: Port 4 Port 4 Port 7 Port 1 Port 2 Port 3 Port 6 Port 6 Port 6 667/HB/20200/000 Bit 0 Bit 7 All Bits All Bits All Bits All Bits Bit 0 Bit 1 Bit 7 T400 Fault Pedestrian audibles ON/OFF control LRV requests Road detectors Pedestrian pushbutton inputs with DFM Pedestrian pushbutton inputs without DFM Interrogator fault 1 Interrogator fault 2 Audibles permanent/timed Page D.-5 Issue 10 Type 400 Controller General Handbook D.4 ADDITIONAL INFORMATION FOR TUEN MUN SPECIAL SPEC. SHEETS Forms TMLRT1 & TMLRT2 - Controller inputs These forms to be used instead of standard Siemens form VIII. Form TMLRT3 Switching details for DIMMING, AUDIBLES & PED DFM This form is used to specify the times of day that the following facilities are required; Audibles ON, Audibles OFF, Switch to BRIGHT, Switch to DIM, Pedestrian pushbutton DFM ON (active) and Pedestrian pushbutton DFM OFF (inactive). Form TMLRT4 LRT Interface Connections - High Voltage This form is used to indicate the high voltage signals passing through the LRT Interface Unit. These signals will be the Mains voltages to drive the LRT Signals aspects. The T200 terminals that they originate from should be left for Siemens to complete, but the terminals that they are going to should be indicated. (e.g. Post 1, Phase A). Note:- If the partial interface unit is being used then the second terminal block TBE is not fitted. Form TMLRT5 LRT Interface Connections - Low Voltage This form is used to indicate the low voltage signals passing through the LRT Interface Unit. TBA2 to 11 should be used for LRT Request and Fault Signals, indicating the terminals that they originate from. The T200 terminals that they are going to should be left for Siemens to Complete. TBA/12 to 13 are for T200 fault Signals. The terminal that they are going to should be indicated, (e.g. Interrogator/Decoder TB1). TBB is used for the returns to the above mentioned signals. Note:- If the partial interface unit is being used then there are a reduced number of request signals. Form TMLRT6 Record of Amendments This form is to be filled in with the issue, a description of the changes (if not initial issue) the date and initials of author. This helps with the traceability of changes. 667/HB/20200/000 Page D.-6 Issue 10 Type 400 Controller General Handbook Form TMLRT7 Special Conditioning LRT Fault Conditions This form is used to specify what actions are to be taken when a specific LRT fault occurs and under which mode it is applicable. Fault conditions:- Artificial requests being received, Priority DFM timed out, Interrogator fault present. Actions:- Insert maximum extend all red, Use specified max set, Insert permanent demand and/or extension for a phase, Inhibit prevents. 667/HB/20200/000 Page D.-7 Issue 10 Type 400 Controller General Handbook Appendix E - T400 Controller drawings Appendix E contains a copy of those T400 drawings which are referred to throughout this document. 667/HB/20200/000 Page E.-1 Issue 10

Type 400 Controller General Handbook Siemens Traffic Controls Limited Sopers Lane Poole Dorset.

Rating

Date

Size

Views

Categories

Share

Transcript