Elv
Elv
Traffic Solutions
Sopers Lane, Poole, Dorset, BH17 7ER
United Kingdom
+44 (0)1202 782000
www.siemens.co.uk/traffic
ST750 ELV
General Handbook
PREPARED:
Andy White
FUNCTION:
Engineering Manager
Change History
Issue
Change Ref
Date
Initial Draft
16 October 2008
Second Draft
28 October 2008
Third Draft
11 November 2008
Fourth Draft
21 November 2008
Fifth Draft
04 December 2008
Sixth Draft
04 December 2008
First Issue
04 December 2008
27 February 2009
27 February 2009
SAFETY INFORMATION
HEALTH AND SAFETY AT WORK
DISCONNECT ALL POWER TO THE CABINET BEFORE REMOVING OR
INSTALLING ANY EQUIPMENT INTO THE CABINET.
Safety of Maintenance Personnel
In the interests of health and safety, when using or servicing this equipment the
following instructions must be noted and adhered to:
(i)
(ii) Such personnel must take heed of all relevant notes, cautions and warnings
in this Handbook and any other Document or Handbook associated with the
equipment including, but not restricted to, the following:
(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 any protective covers or working on any
part from which the protective covers have been removed.
(iii) Any power tools must be regularly inspected and tested.
(iv) Any ladders used must be inspected before use to ensure they are sound and
not damaged.
When using a ladder, before climbing it, ensure that it is erected properly and
is not liable to collapse or move. If using a ladder near a carriageway, ensure
that the area is properly coned and signed.
(v) Any personnel working on site must wear the appropriate protective clothing,
e.g. reflective vests, etc.
In the event of any person working elsewhere on the junction, it is recommended
that the Mains Supply to the controller be switched off and the master switch locked
in the off position.
WARNING
If you are not certain that the entire system is ELV, you must switch off
the Mains Supply to the controller and lock the Master Switch in the off
position.
In countries where both sides of the incoming supply are above earth potential, the
Master Switch or Circuit Breaker should be opened.
When re-commissioning signals, the following sequence is recommended:
1.
2.
3.
More specific safety information is given in the text of the handbook, where it relates
to particular activities or situations.
WARNING
There are various RJ45 connectors used to connect to LSLS and I/O
cards in the ST750 ELV cabinet. These are not Ethernet ports and
should not be connected to other equipment, including PCs.
WARNING
To isolate the equipment, the Master Switch must be in the
Off position.
Removal of the Electricity Board Fuse or Switching the
Controller switch or the Manual Panel Signals On/Off
switch to Off does not guarantee isolation of the
equipment.
WARNING
These (this) controller(s) require specific configuration to
enable them (it) to function correctly when installed.
The configuration process is a complex activity and
should only be carried out by persons who are adequately
trained, have a full understanding of the needs of the
county or region were the controller is to be used and are
experienced in the tasks to be undertaken.
Do not connect any device that has not been specifically designed or
tested for compatibility with the ST750 ELV system. If in doubt, contact
Siemens Poole for further information.
WARNING
TABLE OF CONTENTS
1.
INTRODUCTION ........................................................................................... 13
1.1
1.2
1.3
PURPOSE .......................................................................................................................... 13
CONTACT US .................................................................................................................... 13
REFERENCE DOCUMENTS .............................................................................................. 13
1.3.1
Non-Essential Documents Intersection Design........................................................ 13
1.3.2
Essential Documents Controller.............................................................................. 13
1.3.3
Essential Documents Cabling ................................................................................. 14
1.3.4
Essential Documents Ancillary Equipment .............................................................. 14
1.4 PRE-REQUISITES ............................................................................................................. 14
1.4.1
Qualifications ............................................................................................................ 14
1.4.2
Required Tools .......................................................................................................... 15
1.4.3
Spares ...................................................................................................................... 15
1.5 DEFINITIONS ..................................................................................................................... 15
1.6 ABBREVIATIONS ............................................................................................................... 16
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
11.1
11.2
11.3
11.4
11.5
Tables
TABLE 1 TYPES OF PEDESTRIAN CROSSINGS ....................................................................... 21
Figures
FIGURE 1 THEORETICAL CROSSING (ST750 ELV) .................................................................. 27
FIGURE 2 SYSTEM OVERVIEW ................................................................................................. 40
FIGURE 3 ST750 ELV CONTROLLER SMALL CABINET INTERNAL VIEW ............................. 42
FIGURE 4 ST750ELV CONTROLLER LARGE CABINET INTERNAL VIEW ............................. 43
FIGURE 5 ST750 ELV RACK ASSEMBLY ................................................................................... 44
FIGURE 6 ST900 ELV CPU CARD (REAR / BOTTOM VIEW) ..................................................... 46
FIGURE 7 MAIN PROCESSOR CARD......................................................................................... 47
FIGURE 8 PROCESSOR CARD LEDS ........................................................................................ 48
FIGURE 9 PHS DAUGHTER CARD ............................................................................................. 50
FIGURE 10 PHS CARD LEDS ..................................................................................................... 50
FIGURE 11 PROCESSOR CARD LINK SETTINGS ..................................................................... 52
FIGURE 12 LSLS CARD PLUGGED IN TO ST750 ELV ............................................................... 53
FIGURE 13 PSU / I/O CARD FRONT PANEL LEDS ....................................................................... 57
FIGURE 14 I/O CARD (SHOWING 16-OUTPUT VARIANT) ......................................................... 59
FIGURE 15 I/O CARD ADDRESS SWITCH AND LEDS ............................................................... 59
FIGURE 16 INTELLIGENT DETECTOR BACKPLANE (REAR VIEW).......................................... 61
FIGURE 17 LOOP TERMINATION BOARD .................................................................................... 63
FIGURE 18 BACKPLANE RACK ASSEMBLY SHOWING CONNECTIONS FOR SINGLE
DETECTOR BACKPLANE ....................................................................................................... 64
FIGURE 19 SINGLE DETECTOR BACKPLANE CONNECTIONS ................................................ 65
FIGURE 20 - OTU MOUNTED IN CABINET.................................................................................... 66
FIGURE 21 - DETECTOR SWING FRAME ASSEMBLY, SMALL CABINET ................................... 67
FIGURE 22 GEMINI2 IN 11 SWING FRAME, SMALL CABINET ................................................. 68
FIGURE 23 GEMINI2 IN 19 SWING FRAME, LARGE CABINET ................................................. 68
FIGURE 24 - GEMINI LAMP MONITOR CONNECTION ................................................................. 69
FIGURE 25 - IRM/IMU CARD MOUNTED IN RACK ........................................................................ 70
FIGURE 26 - IRM/IMU MODEM PANEL.......................................................................................... 71
FIGURE 27 - IRM/IMU +24V POWER CONNECTIONS .................................................................. 71
FIGURE 28 STAND-ALONE PEDESTRIAN CONTROLLER MANUAL PANEL............................. 73
FIGURE 29 AUDIBLE DRIVER MODULE..................................................................................... 75
FIGURE 30 AUDIBLE DRIVER MODULE CONNECTIONS LOUD ONLY.................................. 77
FIGURE 31 DUAL LEVEL AUDIBLE DRIVER MODULE CONNECTIONS.................................... 78
1.
INTRODUCTION
1.1
Purpose
Note
1.2
Ongoing development means that some of the delivered items may differ in
detail from the information included in this handbook.
Contact Us
If you have any comments on this handbook, or need any further information, you
can contact us at trafficwebmaster.stc@siemens.com.
1.3
Reference Documents
Publisher
Siemens
Reference Number
667/DS/20664/048
2.
Siemens
667/HE/31699/000
3.
Siemens
667/DZ/32750/000
Document Title
Traffic Signal Junction Cable Design &
Certification for ELV Systems
Loop Inductance and Turns Calculation
Spreadsheet
ST750 ELV Family Tree
Publisher
Siemens
Reference Number
667/SU/32900/000
5.
6.
7.
Siemens
Siemens
Siemens
667/HH/32900/000
667/HB/32900/000
667/HB/32750/000
8.
9.
10.
Siemens
Siemens
Siemens
667/DA/33743/000
667/GA/32750/ETC
667/CC/32750/000
Document Title
ST900/750 ELV Firmware and Hardware
Configurations
ST900/750 Family Handset Handbook
ST900 General Handbook
ST750 ELV General Handbook (This
document)
ST750 ELV UK Power Circuit Diagram
ST750 ELV Controller Cabinet Cabling
ST750 Family Controller Configuration
Publisher
Siemens
Reference Number
667/HE/20664/000
12.
Siemens
667/HE/20663/000
Document Title
Installation and Commissioning
Handbook - Installation Testing
(General)
Loop Detector and Cable Terminations
Installation and Commissioning
Publisher
Siemens
Reference Number
667/HE/20662/000
14.
Siemens
667/HE/20665/000
15.
16.
17.
18.
19.
Siemens
Siemens
Siemens
Siemens
Siemens
667/HB/43100/000
667/HB/32600/000
667/HB/27663/000
667/HB/22380/000
667/HB/30000/000
1.4
Pre-Requisites
Document Title
Installation & Commissioning Signals
& Poles
Installation and Commissioning
Handbook 5 - Above Ground Detectors
TC12 General Handbook
Gemini 2 Traffic Outstation Handbook
ST4R/ST4S Loop Detector Handbook
TCSU/TfL IMU Handbook
Helios General Handbook
667/2/20234/000
4/MC 289
667/4/13296/001
667/4/13296/000
667/4/13296/002
667/4/13651/000
Terminal Tool
WAGO 210-658
1.4.3 Spares
See Appendix A.2 for a full list of spares that are necessary when carrying out a site
visit to the controller, whether for installation, commissioning or maintenance.
1.5
Definitions
Bit
Byte
Eight bit data array (i.e. bits 0-7, and 8-15 are bytes)
Configuration data
(Customer Data)
and site
specification
Configuration
EPROM
EM
CIC
Firmware EPROM
STS
(Site to Scale)
Word
Works
Specification
1.6
Abbreviations
2.
The ST750 ELV is a Pedestrian Controller and Small Non-UK Traffic Controller and
can be supplied in either small or large single-door outer cases.
When the ST750 ELV is supplied without an outer case it is known as an ST750 ELV
Cuckoo Kit (See section 5)
The Specification that follows is for the ST750 ELV Cabinet Assembly. Where
appropriate it also applies to the ST750 ELV as supplied for installation in another
Cabinet.
Small Non-UK specifications are detailed where they differ from standard UK
specifications.
The ST750 ELV can be supplied as
Single Pedestrian controller (2 Phase)
Dual Pedestrian Controller (4 Phase)
Small Non-UK Controller (8-10 Phase)
Generally it comes as a fully fitted Cabinet Assembly with its own equipment, mounting
stool, mains distribution, power supplies, electronic control and phase switching
The essential differences between the ST700 Controller and the new ST750 ELV
Controller are:
The controller allows direct termination of street cabling without resorting to the
use of additional terminal blocks and soft wire conversion kits. Additional kits, if
used, follow the same approach.
The Mains-powered 2, 4 or 6 Phase Drive PCB has been replaced with either a
16 output (Single Pedestrian) or a standard (ST900 ELV) 32 output (Dual
Pedestrian / Small Non-UK Intersection) - ELV lamp switch card (LSLS) that
drives and monitors the 48V LED aspects, 48V tactiles and audible driver
modules. The LSLS card is mounted directly in the ST750 ELV Rack Assembly.
The standard 10-24V dc sounders (section 2.8.8) are now driven via Audible
Driver modules. One Audible Driver Module is built in as standard, with a
second available as a separate kit if required.
A new combined PSU / I/O card distributes the 48V lamp supply from the Lamp
Supply Transformer, incorporates the Dim/Bright, A and B relays and I/O
circuitry for 24 inputs and 4 outputs. The card also contains the circuitry for the
built-in Audible Driver and Solar Cell supply. The PSU / I/O card is mounted
directly in the ST750 ELV Rack Assembly.
The ST750 ELV uses the standard ST900 CPU card to provide high-speed
serial connection to the LSLS card, PSU / I/O card and Intelligent Detector
Backplanes (if fitted). Use of this card also provides the ability to change the
The ST750 ELV supports existing Siemens equipment such as Gemini, Gemini2,
Tele12 OTU, IRM/IMU Card and ST4S.
The controller conforms to the UK Highways Agency specification TR2500A.
2.1
The ST750 ELV Single Pedestrian Controller consists of one vehicle phase and one
pedestrian phase with fixed phase outputs including 5 vehicle RLM channels and
dedicated Audible and Tactile Outputs. Sufficient I/O is provided to perform all the
functions of a 2 phase Pelican, Puffin or Toucan. These consist of 24 buffered inputs
and 4 isolated relay outputs.
Expansion may be achieved by adding combinations of the following equipment:
Input/Output PCB
Either of the ST900 family IO boards may be added to expand the inputs/outputs
as follows:
24 Inputs / 4 Outputs or
24 Inputs / 16 Outputs
Detectors
These can be any detector, with isolated relay outputs, compliant with TR2512. Up
to 8 units can be accommodated in the ST750 ELV cabinet, each unit having four
detector channels.
Note
Ancillary Equipment
OTU Outstation Transmission Unit for Urban Traffic Control.
OMU Outstation Monitoring Unit for Remote Monitoring System.
UTMC OMU UTMC compliant Outstation Monitoring Unit
2.2
The ST750 ELV Dual Pedestrian Controller consists of two vehicle phases and two
pedestrian phases with fixed phase outputs, including 5 vehicle RLM channel per
vehicle phase. Sufficient I/O is provided to perform all the functions of 4 phase
Pelican, Puffin or Toucan. These consist of 24 buffered inputs and 4 isolated relay
outputs.
2.3
The ST750 ELV Small Non-UK Controller provides an 8-10 Phase Traffic Intersection
Controller. It is similar to the Pedestrian controllers, except in the following areas:
It has 8 10 phases, with LSLS outputs freely configured in IC4
A label is fixed to the termination backplane to identify the correct phase
terminal designations as created by IC4.
2.4
A number of different types of pedestrian crossings are available on the ST750 ELV.
The following table lists the different types of stand-alone pedestrian crossings
detailed in TR2500A:
Type of
Crossing
Ped. Signal
Position
Pelican
Far-side
Puffin
Near-side
Pedestrian
Far-side
Toucan
Far-side
Toucan
Near-side
Pedestrian to Vehicle
Clearance Period
Vehicle Flashing Amber
Pedestrian Flashing
Green
Vehicle Red
Pedestrian Red
Vehicle Red
Pedestrian Blackout
Vehicle Red
Pedestrian Blackout
Vehicle Red
Pedestrian Red
Control
Main Microprocessor
Firmware Storage
Working Data Storage
Motorola 68340
PROM (27C4002)
Static RAM ( 512K)
(Battery Backed)
Secondary Microprocessor
Firmware Storage
Working Data Storage
Inter-Processor Communications
Intel 80C32
PROM (27C512)
Internal to Microprocessor Device
Dual Port RAM 71321 (2K x 8)
Lamp Switching
FET
Conflict System
Self Testing
2.6
MAINS SUPPLY
Voltage:
Frequency:
Break:
Mains Fail:
Battery Support:
Nominal Lamp
Supply
48V rms
Dimming Voltage:
27.5V rms
The solar cell enables the ST750 ELV to identify the light level and thus dim the
signals when it is dark. There is an optional time switch that can be used to regulate
dimming control if required
Note
2.7
Electrical Noise
2.8
This section describes the method used to determine that the controller can supply the
total lamp load required and how to determine the overall power used for estimation of
site running costs.
In order to do this, the power taken by the lamps needs to be calculated. Use the
following table to determine the average power taken by the different types of lamps.
Bright
48V
Dim
27.5V
7W
12 W
3.5 W
7W
2.5 W
18 W
3W
6W
1.2 W
8A
384W
32
2A
96W
Output Type
Helios ELV (vehicular or far-side ped)
Siemens Red/Green Nearside
AGD Red/Green Nearside
3,4
Maximum
Lamp
Quantity 1
Monitoring
Yes
Yes
No 2
Yes
Yes
No
No
Note that the Backplane only provides terminations for 4 street cores. Also see
section 2.8.11 starting on page 31 for details of number of cores required for long
cable runs.
Signals cannot yet be monitored refer to Siemens Poole for the latest information.
4 Tactile Units and 1 Audible Driver Module (8 sounders) or 2 Tactile Units and 2
Audible Drivers (16 sounders) can be simultaneously driven from one LSLS output.
Note that O/P 16 (ADRV) is internally connected to one audible driver module
(built in) so account must be taken of this when calculating the maximum load for
this output.
- Note that only product fitted with a clear ELV label may be connected to the LSLS.
Although the part numbers of these products have not changed, the internal
circuitry has - so on no account must a unit without the relevant label be connected
or damage to the LSLS will result.
Warning
Nearside, Wait or Demand units without an attached ELV label must not be
connected to the LSLS. Damage to the LSLS will result if this is done. This
applies to units of either Siemens or AGD manufacture
See section 7.19 for further details
When outputs are required to be lamp monitored, output types must not be mixed.
Specifically, when lamp monitoring Nearside Signals, it is not allowed to connect
Tactile Units or Audible Driver Modules in parallel to the Nearside Signals. In this case,
two or more LSLS Outputs must be specified for the pedestrian green aspect in the IC4
Configuration (Phase Type and Conditions screen), with lamp monitoring disabled on
the outputs used by the Tactile Units or Audible Driver Modules.
Note
When output types are NOT lamp monitored, it is permissible to mix output types.
Specifically, it is permissible to connect 2 Tactile Units, 2 Green Nearside Signals
(either AGD or STC) and one Audible Driver Module (8 sounders) in parallel
across one LSLS output. Lamp monitoring can be disabled on particular sensors
using the KLT Handset command.
A
B
B
A
C
C
D
D
C
C
144W
28W
172W
144W
28W
172W
29W
6W
35W
172W
Controller power
35W
207W
If it is 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
Lamp Power
Bright
Lamp Power
Total
Reg. Signs
Total Average
Controller Power
0W
35W
3.5 W
12 W
Note
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.
Siemens ST4R/ST4S
(2.4W / 100mA per detector)
Sarasota MTS36Z or MTS38Z (or any
mix)
-24V DC 50VA /
2.0A
667/1/33705/000
-24V DC 2.0A
In-built
Detectors are normally powered from the in-built detector supply, which provides
rectified and earthed -24V rms at 2.0A DC. If more current is required, to power
additional detectors, then an additional -24V 2A (50VA) detector power supply kit may
be fitted. The maximum number of each type of detector that can be supported by each
power supply is shown in the table below.
20
20
16
16
Note
If powering AGDs in addition to Loop Detector Cards from the supplies above, the
current drawn by the AGDs must be taken into consideration when calculating the
number of loop detector cards that can be powered.
Note
Space limitations within the cabinet mean that it is only possible to fit one additional
2A Detector Supply Kit.
The ST750 ELV running standard pedestrian configurations provides one dedicated
audible drive output per pedestrian phase.
Audible sounders used must operate correctly over the voltage range 10 to 24V DC.
The audible units recommended and supplied by Traffic Solutions, which meet this
requirement, are: Highland Electronics type SC628P (was Sonalert Mallory SC628P),
Roxborough type SPCI535A4 and Askari (Tone 22 variable volume)
2.8.9 ELV Tactile Units
The ST750 ELV provides up to 3 dedicated outputs for driving tactiles per pedestrian
phase, see section 7.14.7 for full details.
The ELV tactiles obtains their power directly from the pedestrian green drive on the
LSLS via tracking on the termination backplane. For output drive capability, therefore,
see Table 4 LSLS Output Capability on page 24.
2.8.10 ELV Regulatory Sign Expansion Kit
If it is required to drive regulatory signs from the ST750 ELV then a Regulatory Signs
Expansion Kit must be fitted. See section 7.14.8 for full details.
The ELV Regulatory Sign Expansion Kit derives power from the controller 6A Aux MCB
in the Master Switch assembly fitted to lower right hand side of cabinet.
ELV Regulatory Signs must operate from 33 to 58VDC rectified supply, measured at
the ELV Regulatory Sign terminal block. For power budget calculations, ELV
,Regulatory Sign Extension Kit loading is 7 Watts per sign.
2.8.11
Cabling
When estimating cable core and controller equipment requirements for the ST750 ELV
Controller the maximum cable lengths defined in the following tables must be complied
with.
The voltage drop in the installation must be no more than 4% of the incoming supply.
The tables should be consulted to ensure that the voltage drop is lower than this
maximum for the selected core size and loading. If the voltage drop exceeds 4% the
cores / conductors must be paralleled up to reduce it.
In addition the following guidance should be observed:
1. Where multiple cores are required due to long cable runs it must be noted that
this may require additional LSLS Outputs (in the Small Non-UK controller only)
in order to accommodate the additional terminations in the Termination
Backplanes.
Note that when using the Standard Configurations provided for Pedestrian
Controllers all outputs are pre-defined.
2. If common ground return connections were used it is possible for the failure of a
ground return connection to cause unexpected signal displays, where one or
more signals within a given signal head are incorrectly illuminated
simultaneously. This lack of ground return connection is not detectable by the
controller because the signal voltage presented at the controller terminals does
RAG traffic signal drive cables: 12W at 100 metres = 1 core each (x3)
RA + Reg Sign Common return cable: 19W (12W+7W) at 100 metres = 1
core.
Green return cable: 12W at 100metres = 1 core
It should be noted from looking at the table that above 100 metres, 2 cores
would be required for the 19W common return, and above 160 metres, 2 cores
would also be required for each 12W signal drive cable.
6. Tactile units are to be provided with a separate drive and return core. Tactile
units driven from the same phase green can share a common drive and return
core. For the purposes of assessing acceptable cable run lengths using the
table, each tactile unit should be considered to be a 12W load.
If required to reduce core usage, tactile units may share a return core with any
Red/Amber LED signal return core on the same pole (NOT Green as this must
always have its own return). If this option is exercised each tactile should be
considered to be a 45W load for the purposes of assessing acceptable cable
run lengths using the table. This figure is much higher than their normal running
power, but is typical of the power consumed if the tactile device is physically
held, stopping the motor.
7. The ELV solar cell should be provided with a drive and return core for
connection of the solar cell supply and signal. The solar cell return can be
commoned with the LED signal return. Its effect on the voltage drop is so small
that it can be ignored.
8. Returns for digital inputs (for above ground detectors and pushbuttons etc on
the same pole) may be commoned together, but must remain separate from the
LED signal returns.
9. Audible units must be provided with a separate drive and return core. Audible
units on the same Audible Driver Module (Consider the built-in circuitry as one
Audible Drive Module for the purposes of cabling) may share a common drive
and return core (up to 250m) if required to reduce core usage, but must remain
separate from the LED signal returns and digital input returns.
Note
NO MORE than 3 cores should be connected in parallel. The numbers in the cells within the tables indicate the number of cores
required to meet the voltage drop requirement.
10m
15m
20m
25m
30m
35m
40m
45m
50m
60m
70m
80m
90m
100m
110m
120m
130m
140m
160m
180m
200m
225m
250m
275m
300m
325m
350m
375m
400m
7W
10 W
12 W
18 W
20 W
25 W
30 W
35 W
40 W
45 W
50 W
60 W
80 W
100 W
120 W
5m
Lamp Load (Watts)
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
1
1
1
1
1
1
1
1
1
1
1
2
2
2
3
1
1
1
1
1
1
1
1
1
1
1
2
2
2
3
1
1
1
1
1
1
1
1
1
1
2
2
2
3
3
1
1
1
1
1
1
1
1
1
2
2
2
2
3
3
1
1
1
1
1
1
1
2
2
2
2
2
3
3
1
1
1
1
1
1
2
2
2
2
2
3
3
1
1
1
1
1
1
2
2
2
2
2
3
1
1
1
1
1
2
2
2
2
2
3
3
1
1
1
1
1
2
2
2
2
3
3
3
1
1
1
1
2
2
2
2
3
3
3
1
1
1
2
2
2
2
3
3
3
3
1
1
1
2
2
2
2
3
3
3
1
1
1
2
2
2
3
3
3
1
1
1
2
2
2
3
3
1
1
2
2
2
3
3
1
1
2
2
2
3
3
1
2
2
2
3
3
1
2
2
3
3
1
2
2
3
3
2
2
2
3
3
2
2
2
3
2
2
3
2
2
3
2
2
3
10m
15m
20m
25m
30m
35m
40m
45m
50m
60m
70m
80m
90m
100m
110m
120m
130m
140m
160m
180m
200m
225m
250m
275m
300m
325m
350m
375m
400m
7W
10 W
12 W
18 W
20 W
25 W
30 W
35 W
40 W
45 W
50 W
60 W
80 W
100 W
120 W
5m
Lamp Load (Watts)
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
1
1
1
1
1
1
1
1
1
1
1
2
2
2
3
1
1
1
1
1
1
1
1
1
2
2
2
2
3
3
1
1
1
1
1
1
1
1
2
2
2
2
3
3
1
1
1
1
1
1
1
2
2
2
2
2
3
3
1
1
1
1
1
1
1
2
2
2
2
2
3
1
1
1
1
1
1
2
2
2
2
2
3
3
1
1
1
1
1
1
2
2
2
2
2
3
1
1
1
1
1
2
2
2
2
2
3
3
1
1
1
1
1
2
2
2
2
3
3
3
1
1
1
1
2
2
2
2
3
3
3
1
1
1
2
2
2
2
3
3
3
3
1
1
1
2
2
2
2
3
3
3
1
1
1
2
2
2
3
3
3
1
1
1
2
2
3
3
3
1
1
2
2
2
3
3
1
1
2
2
2
3
3
1
2
2
2
3
3
1
2
2
3
3
3
1
2
2
3
3
1
2
2
3
3
2.9
Outercase
The ST750 ELV Outer case is a single sided access cabinet with the following
dimensions:
Small outer case Height
1200mm
Width
466mm
Depth
370mm
47Kg
1157mm
Width
730mm
Depth
426mm
50Kg
Note
The key lock should not be operated unless the screw locks are tight, i.e. Unlock
the case before undoing the screw lock and only lock the case after tightening the
screw locks.
The lock used on the Manual Panel is a small Yale lock with a 900 pattern barrel.
2.10
Environmental Conditions
2.10.1 Temperature
The ST750 ELV in small or large grey outer case is designed to operate in external
ambient temperatures of -25 C to +60 C.
Use in countries where high levels and long periods of solar radiation are expected
may impose restrictions on ST750 ELV hardware configuration. Contact Engineering
at Poole for more details on hardware restrictions.
PHASES
The ST750 ELV Pedestrian Controller supports either 2 Real Phases for a single
pedestrian crossing or 4 Real Phases for a dual pedestrian crossing.
The ST750 ELV Small Non-UK Controller can support up to 8-10 Real Phases.
The ST750 ELV software can support up 32 phases, which can be any combination
of real and software phases.
2.12
STAGES
The ST750 ELV software supports up 32 stages. Note that Stage 0 is normally ALL
RED.
2.13
TIMINGS
All ST750 ELV timings are transferred to battery supported RAM during initialisation.
Once in RAM, most timings can be varied by handset commands. Once the
configuration data has been loaded into the ST750 ELV, the same configuration
cannot be loaded again. This prevents the accidental overwriting of any
configuration data that may have been set up using the handset.
In the UK some timings considered to be fixed timings cannot be changed by
handset. These are typically the Amber and Red/Amber periods. These timings can,
however, be specified as alterable at configuration time to suit other signal
sequences, export requirements etc.
Some timings considered to be safety timings can only be changed by a person at
the ST750 ELV operating the write enable level 3 push button, e.g. minimum green,
intergreen, blackout timings, etc.
The default timings for the ST750 ELV standard Pedestrian configurations are given
in their IC4 printouts (Special Instructions). These printouts also show the handset
commands that are used to change each of the timings. Some of these timings are
described in Section 3.
A summary of all the timings available within the ST750 ELV Small Non-UK
intersection controller is contained in the ST900 General Handbook (see
Section 1.3.2 for details). It also shows their upper and lower limit values and,
where applicable, the configurable limits.
2.13.1
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 200ms to
the time.
If the result of the above timings is required to change the signal lamps, a further
error may occur up to a maximum of 21ms.
The set-up accuracy of the real time clock and the accuracy of any offsets
calculated from it will be 1 second.
2.14
2.15
Number of plans:
Number of plan influence tables:
Number of groups per plan:
Number of group influences:
16
16
32
10 types
MODES OF OPERATION
The following modes are available on the ST750 ELV Pedestrian controller, and are
described fully in Section 6:
Stand Alone Pedestrian V.A.
Stand Alone Pedestrian V.A. with pre-timed maximum period
Stand Alone Pedestrian Fixed Vehicle Period
Backplane
Handset
24 + 4 I/O Card
I/O - RS422
+24V DC
PSU
1- 8
4x
Torroid
Signal
Return
12 x Phase
Output
12 or 20 Phase
Output Option
Wiring
Loom
White T/Blocks
3U
DIN41612
OR
1 to 8
Generic relay Output 4
Channel Loop Detector
Single Detector
Backplane(s)
8 Maximum
Loop Detector
Termination Board
Loop Terminals
3U
-24V DC
IDC
+24V
DC
IMU
RJ45
Intelligent Detector
Backplane
(2 Maximum)
RJ45
ELV
Dimming
Transformer
230V AC
IDC
RJ45
Power In
I/O Card
Expansion
RJ45
6U
Power Out
Expansion limited
to one I/O card
DIN41612
Power Supply
(LPU + HPU + A/B/Dim/
Bright Relays + Audible)
Detector Outputs
Modem
24 x Input
PSU
DIN41612
RJ45
4x
Output
I/O - RS422
RJ45
ST900 CPU
+
PHS
IMU or OTU
RJ45
LSLS - RS422
Detector
-24VDC
6U
Manual Panel
RJ45
ESB
RJ45
ESB
DIN41612
LSLS
ARM7 CPU
12 Switch O/Ps
Audible
Drive
Manual
Panel
Lamp
Supply
Monitor
Solar
Cell
DIN41612
HFF
Option
DIN41612
3.
3.1
Figure 3 shows the ST750 ELV controller fitted into a small outer case (Cabinet),
Figure 4shows the Large case option.
The Rack assembly is mounted on the rear panel of the cabinet at a suitable
height to provide easy access to the street cable termination area.
An optional, hinged, frame may be mounted on the left hand side of the
cabinet to house a Gemini unit and / or up to 4 Loop Detector Cards (Small
cabinet option only).
Up to one I/O card may be mounted on the rear panel of the cabinet, above
the Rack Assembly
Detector Power Expansion kit, Audible Driver Kit or Regulatory Signs
Expansion kit may be mounted on the rear panel of the cabinet in an area
underneath the Rack Assembly.
CET bars are installed in the base of the cabinet.
The Master Switch Panel, with associated maintenance sockets, is mounted
on the right hand side panel of the cabinet.
The Lamp Supply Transformer is mounted on the left hand side panel of the
cabinet.
For certain equipment configurations it is necessary to fit an 11 (Small Cabinet
option) or 19 (Large Cabinet option) swing frame into the cabinet, hinged on the left
hand side. This frame can be swung open to enable access to the rear of the frame
and to the cards and components installed in the cabinet. If this frame is fitted, then
the small hinged frame accommodating the Gemini and /or loop detector cards in
the Small Cabinet option cannot be fitted. In this instance both the Gemini and Loop
Detector cards are mounted in the swing frame.
If it is required to fit either a Gemini or loop detectors in the Large Cabinet then it is
necessary to fit the 19 Swing frame. In this instance both the Gemini and Loop
Detector cards are mounted in the swing frame.
Manual
Panel
Card Rack
LSLS Return
+
Maintenance
Termination
Sockets
Backplane
Street Cable
terminations
Easy access
to top &
bottom of
cards
Options:
Loop Termination
Board(s)
(Maximum of 2)
Optional 2nd Audible
driver board
Optional Reg signs
Board
Street Cable
(Maximum
of 1)
Terminations
Assembly
Gemini
Option
Maintenance
Sockets
Loop
detecto
r
Option
ELV
Transformer
Master
Switch
19 Swing
Frame
Street Cable
Terminations
Assembly
19 Detector
Rack kit
Assembly
Transformer
position,
Transformer
(not shown)
Gemini
Option
Master
Switch
Unit
3.2
Expansion
Board
Mounting
Points
CPU
Board
Street cable
retaining area
The left hand slot of the left hand bay allows for one expansion card to be
fitted either of
o Outstation Transmission Unit (OTU)
o TfL Integral Monitoring Unit (IMU)
If either of these cards are fitted they are connected to the CPU card using an
Extended System Bus cable across the rear (bottom) of the cards.
The cards are held in by a retaining strip along the upper front edge. To release the
cards, loosen the clamping screws and move the retaining strip clear of the card
guides.
To the right of the card bays is the street cable termination area.
For Single and Dual Pedestrian Controllers all terminals are identified on the
silk screen of the backplane.
For Small Non-UK Controllers the phase connections are identified using an
adhesive label fixed adjacent to the phase termination terminal block in a
similar manner to ST900 ELV controllers. This label is generated by IC4 as
part of the configuration process. All other terminals are identified by the silk
screen on the backplane.
A number of cable tie points are incorporated in the metalwork of the Rack
Assembly, in the street cable termination area, to permit street cabling to be neatly
and securely tied off once installed.
4.
This section describes the main components of the ST750 ELV system.
4.1
The Lamp Supply transformer provides the high current 48V supply to the ELV
signal heads. It additionally provides a low voltage AC supply for the operation of
the LSLS card logic and a 24V rms rectified DC supply for powering Loop Detectors,
AGDs and the solar cell.
Issue 3 (and lower) Lamp Transformer has primary taps for
220/230/240V operation and 110/120V operation
Note
Issue 4 (and higher) Lamp Transformer has an additional primary
tap for 250V operation
For details on how to connect the Lamp Supply Transformer and select the correct
tappings refer to section 7.11 of this document.
4.2
The ST750/900 ELV main processor card is paired with the PHS daughter card. The
two are bolted together and should not be separated. In case of failure, both cards
should be replaced as a single unit (in order to ensure compatibility between the
firmwares fitted to each card).
The main processor card is the heart of the controller. It holds the controller
configuration and performs the function of configuration, control and management.
The primary external data interfaces of the main processor card are an Extended
System Bus interface to OTU cards, interface to the Manual Panel and a front-panel
serial interface to handset or Gemini2.
The PHS daughter card accepts parallel control data from the main processor card
and converts this into high speed serial data. The PHS also acts as a second
processor, providing independent safety monitoring of the controller functions.
Three high-speed serial channels are available on 3 separate RJ45 sockets on the
PHs.
The RJ45 socket marked LSLS on the PHs must be connected to the RJ 45
socket marked LSLS (SK10) on the ST750 ELV backplane.
The two remaining RJ45 sockets are identical and both marked IO One of
these is connected to the RJ45 socket marked IO (SK11) on the ST750ELV
backplane and the other to either a second IO cards or Intelligent Detector
Backplane (if fitted) It is not important which connector on the PHS is used for
connection to the backplane and which is used for second IO card / Intelligent
Detector Backplane.
Figure 7 shows the location of the configuration PROM, firmware PROM(s) and
selection switches on the main processor board.
Pins 1, 2, 31 & 32
of socket not used
Position of the
Configuration
PROM in the
Configuration
PROM Socket
RAM
Chips
Phase Bus
Processor
Phase Bus
Connector
Phase Bus
Firmware
(PB815)
(PB820)
EPLD1
32
32 pin
16
Extended System
Bus Connector
17
Configuration
PROM socket
Modem Port
FRONT
Status LEDs
PP
SE
BE
WD
(PB821)
EPLD2
Main Processor
Firmware (PB801)
Hardware fail
flash selection
Power fail
signal source
Manual Panel
Connector
PHS
Connector
Main
Processor
RS232 Handset
port
Handset Fuse (500ma)
Power Connector
PP - Power Present
(Heartbeat)
LP3 - Red
SE - System Error
LP2 - Red
BE - Bus Error
LP1 - Red
WD - Watchdog
LED
Function
No Fault State
PP Green
Power
Present
SE - Red
System
Error
Off
BE - Red
Bus Error
Off
WD - Red
Watchdog
Off
PP
SE
BE
WD
Indicated State
Flash
Off
Off
Off
Flash
On
Off
Off
On
On
Off
On
On
On
Off
Off
On
On
On
On
10-way header
not used in the
ST750 ELV
Status LEDs
PP
SE
HW
SW
FF
HB
RJ-45 High-Speed
serial comms to
LSLS cards
RJ-45 High-Speed
serial comms to I/O
and Backplane cards
LP6 - Green
HB - Heartbeat
LP5 - Yellow
FF Fail Flash
LP4 - Red
SW Software Fault
LP3 - Red
HW Hardware
Watchdog Fail Latched
LP2 - Red
SE System Error
LP1 - Green
PHS CARD
PP Power Present
LED
Function
HB
Green
Heartbeat
No Fault State
Flashes giving an
indication that the
PHS software is
running normally.
FF
Yellow
Fail Flash
Off.
SW
Red
Software
Fault
Off
On
LED
HW
Red
SE
Red
PP
Green
Function
Hardware
Watchdog
Fail
Latched
System
Error
Power
Present
No Fault State
Off
On
Off
On
On
Note
While the Controller is shut down or while the Main Processor card is held
reset due to (for example) a problem with the power supply, the PHS card
will be held reset. In this state, all LEDs except FF will be illuminated and
will not flash.
Note
X3
X3
4.3
LSLS Card
The LSLS card provides either 16 or 32 current and voltage monitored switched
outputs to the ELV signal aspects.
For Small Non-UK Intersection Controllers IC4 is be used to print self-adhesive
labels for the LSLS backplane to identify the phase and colour of each street
termination. In the case of Single and Dual Pedestrian controllers the phase outputs
are marked on the termination backplane silk screen.
Each of the outputs has an associated LED showing the status of that output. The
LED is tri-colour and should be the appropriate colour assigned to the output
(except during Self Test when all LEDs illuminate yellow on Small Non-UK
Intersection Controllers only, on Pedestrian Controllers the LEDs illuminate with the
correct lamp colour)).
LED Output 1
To
LED Output 32
LED B
LED A
See section 2.8.3 of this document for information on the number and
combinations of devices that can be connected to an LSLS output.
4.3.2 LSLS Status LEDs
The LSLS has two tri-colour status LEDs as shown in Figure 12 which are used to
indicate various conditions as follows. Conditions other than those identified should
not occur and so can be treated as faults.
LED A
LED B
Yellow
Yellow
Meaning
Reset
Possible Cause
Start up (if brief)
Comms lost to main processor (if brief)
Hardware fault (otherwise)
Red
continuous
any
Major fault
Alternate green
Peripheral
download
Off
Awaiting start
LSLS powered up
Red flash
Yellow
flash
Downloading
Off
Green
flash
Normal operation
Lamp Supply with Bright & Dim Taps of 48V and 27.5V
24V fully rectified AC for the detector supply and solar cell supply
38V AC for logic supply generation
The power supply is split into the various load types as follows:
Supply
Lamp Supply bright -48V DC rms
nominal 8A rms
Lamp Supply dim -27.5V DC rms
+5V Smooth DC Logic Supply 2A
+24V Smooth DC IO Supply 1.5A
-24V Loop Detector supply -24V DC
rms nominal 2A rms
-24V Smooth DC Solar Cell Supply
25mA
Measures as
(Note 2)
-44.6V DC
-25.4V DC
+5V DC
+24V DC
-20.9V DC
-24V DC
Note
The 48V DC Lamp supply, 48V DC Regulatory sign supply (if fitted) and
24V DC Loop Detector Supplies are all negative with respect to ground i.e.
the positive side of each of these supplies is grounded.
Note
Note
Note
LP1
LP2
LP3
LP4
Audible
LED
(LP1)
Comms
Active LED
(LP2)
System
LED
(LP3)
Watchdog
LED
(LP4)
State
Yellow
Yellow
Off
Processor Reset
Yellow
Yellow
Red
Watchdog Failure
Off
Green
Steady
Off
Performing Start Up
Red
Green
Flash
Off
Awaiting Start
Green
Toggle on
Receipt of
Message*
Green
Flash
Off
Communications Active
Off
Green /
Red
Alternatin
g
Off
Invalid Address
(As above
depending
on state)
Red Flash
Off
Green
Audible enabled
Off
Audible Off
The I/O card provides a rugged interface for up to 24 digital inputs and up to 16
changeover outputs for the connection of pushbuttons and above ground detectors,
or to provide a free-standing UTC Interface or for linking between controllers.
A sub-equipped variant of this card is also available, fitted with only 4 changeover
outputs. If the IC4 Configuration requires the 24 in / 4 out variant but one is not
available, then a 24 in / 16 out card can be fitted in its place.
The I/O card connects to the PHS via a high-speed serial cable through which the
card also obtains its logic power supply.
Note
Watchdog LED
(LP3)
State
Yellow
Yellow
Off
Processor Reset
Yellow
Yellow
Red
Watchdog Failure
Off
Green Steady
Off
Performing Start Up
Red
Green Flash
Off
Awaiting Start
Green Flash
Off
Communications
Active
Off
Green / Red
Alternating
Off
Invalid Address
Red Flash
Off
Major Fault
Detected
4.6
State
Off
Yellow
Yellow
Processor Reset
Red
Yellow
Yellow
Watchdog Failure
Off
Green Steady
Off
Performing Start Up
Off
Green Flash
Red
Awaiting Start
Off
Green Flash
Communications
Active
Off
Green / Red
Alternating
Off
Invalid Address
Off
Red Flash
Major Fault
Detected
Pair 1
Rack Assembly and pin 18 of the Single Backplane, using white wire. The four
inductive loop activation signals will be connected to the appropriate channels/pins
on the Single Back plane. Please refer to SLD4 Inductive Loop Detector Handbook
(667/HB/45200/001), or ST4S/ST4R Inductive Loop Detector Handbook
(667/HB/27663/000), for the necessary information.
-24 VDC
power for
Detector
Backplane
Detector
Loop
Activation
Common
Power
Return
3
4
5
6
7
8
Loop
Activation
Output
Signals
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
AC
Input
nc
nc
ST4S
The Loop Detector cards pick up the Loop Detector Power from SK7 on the
Intelligent Detector Backplane Card that they are plugged into.
Further information regarding ST4S Loop Detector Cards is available in the
following document:
667/HB/27663/000 ST4S/ST4R Loop Detector Handbook
4.9
TC12 OTU
The TC12 OTU card is located in the left hand most slot of the left hand, vertical,
card bay.
OTU
4.10
The normal mounting for a Gemini2 and up to four loop detectors in a Small Cabinet
utilises the additional ST750 Detector Mounting Bracket Assembly Swing Frame
on the lower left hand side of the cabinet.
WARNING
11 Detector Rack
Assy
11 Swing Frame
Mounting
space for
Loop
Detectors
19 Detector
Rack Assy
WARNING
When fitting a Gemini2 in a swing frame care must be taken to ensure that
the internal lead acid battery terminals point UPWARDS to prevent
leakage. For the Gemini2 installed as shown in Figure 22 and Figure 23
the battery must be re-moved and re-fitted BEFORE installation as when
supplied from the factory the battery will be fitted in the opposite
orientation. Alternatively, the Gemini2 can be installed the other way up in
the rack. Refer to 667/HB/32600/000 for full details.
If it is required for the Gemini to monitor the lamp supply a connection is made to
PL12 on the termination backplane.
PL12
Note
Current Gemini products do not have the correct interface levels to monitor
ELV lamp supplies. A change is currently in process to correct this.
Contact Siemens Poole for further information.
4.11
IRM/IMU
The IRM/IMU card is located in the left hand most slot of the left hand vertical card
bay.
IRM/IMU
Note
The AUX Supply is positive of Ground, and MUST NOT be taken outside the
cabinet under any circumstances in order to maintain the ELV integrity of the
site.
4.12
Manual Panel
The Manual Panel provides a direct means of manually controlling the crossing in a
safe manner. The card connects directly into the rear of the CPU as shown in Figure
6 on page 46.
SIGNALS
CABINET
ALARM
OFF
SIEMENS
ON
AUX 1
PED 2
PED 1
CONT
PED
DEMAND
CONT
PED
DEMAND
CONT
VEHICLE
EXTEND
CONT
VEHICLE
EXTEND
VA
VA
SELECT
SELECT
FVP
FVP
AUX 2
AUX 3
DFM
RESET
LAMP
SW 1
SW 2
SW 3
TEST
For near-sided pedestrian crossings (i.e. those showing red during the clearance
period), an artificial on-crossing detect is inserted as required by TR2500 to extend
the clearance period to its maximum.
4.12.2 Continuous Vehicle Extend
These buttons can be used to insert continues vehicle extensions on the first
(PED1) or the second (PED2) stand-alone pedestrian stream. Pressing the button
toggles the state of the associated indicator. While the indicator is illuminated, the
vehicle phase is artificially extended up to its maximum green period.
4.12.3 Select VA or FVP
These buttons can be used to switch the two stand-alone pedestrian streams (PED1
and PED2) between Vehicle Actuated mode and Fixed Vehicle Period.
Pressing the button toggles the states of the associated indicators. Note that
indicators just show the requested mode, they do not necessarily show the actual
mode that is running. The handset command PEV can be used to disable VA mode,
enable VA mode (allowing these buttons to select the mode) or force VA mode
(ignoring the state requested by these buttons).
4.12.4 Other Buttons and Indicators
The remaining buttons and indicators provide the same function as on an
Intersection Manual Panel.
4.12.5 Other Manual Panel Variants
A panel with only Cabinet Alarm and Signals On/Off Switch is also available with the
ST750ELV
4.13
In order to drive audible indicators for an optional second stream, an Audible Driver
Module Kit of Parts (KOP) is required Siemens part number 667/1/32955/000.
The module is powered from the Audible Driver phase Green of the second
pedestrian stream of the LSLS card (ST750ELV motherboard SK3 row 32) and
provides a regulated 12V DC to the audible indicators.
The module is also connected to the ST750ELV motherboard SK4 (row 6) to allow
operation to be inhibited when required, and to allow switching from Loud to Quiet
audible indicators.
The Audible Driver Module will operate at both dim and bright lamp voltages.
CAUTION
Do not touch components on the Module:
voltages of up to 81V peak could be present,
and components could be hot.
Quiet PP LED
Loud PP LED
Audible -ve
Output link
There are separate Power Present (PP) LEDs on the module, for Loud and Quiet
outputs, which light when the audibles are being driven. It is recommended that all
audibles connected to an Audible Driver Module are the same type.
Audible indicators recommended are:
Sonalert Mallory SC682P
Askari (Tone22 variable volume)
The above indicators are functional equivalents. Any audible indicator that operates
from a nominal 12V DC supply and takes a maximum of 18mA may be used as an
alternative to the above.
The Audible Driver Module is mounted on the rear panel in the controller cabinet
using the screws supplied in the KOP. When Loud/Quiet switching is not required,
the Audible Driver Module is connected as shown in Figure 30 below.
In order for the Audible Driver Module to operate, the EN (Enable) + and COM
connections on the Audible Driver Module must be connected to the EN and COM
connections of the AUD2 section of SK4 (row 6) on the ST750ELV motherboard.
When it is desired to switch audibles from Loud to Quiet operation (eg at different
times of day), the Output Link (R40) must be cut, and Quiet audibles must be
connected to Quiet Output + (QU O/P+) with Loud audibles connected to Loud
Output + (LO O/P+). The LQ input + and COM must then be connected to the
LQ and COM connections of the AUD2 section of SK4 (row 6) on the ST750ELV
motherboard (a single COM wire, to either LQ COM or EN COM on the Audible
Driver, is sufficient).
Note
Audible Driver
Module
Loud
Audible 1
Loud O/P+
Audible COM
SK3 row 32
nd
ADRV 2 stream
LSLS I/P
Return
LSLS Return
R40
O/P+ LINK
FITTED
(8 Loud outputs)
LQ COM
LQ +
+
Quiet O/P+
Audible COM
EN COM
Loud
Audible 8
EN +
No
connection
No
connection
ST750ELV
SK4 (row 6)
COM
Mon COM
Output
EN
Mon MQ
Mon COM
Mon ML
Input AUD_ML2
Input
Output monitoring
Return
4.13.1
Connections for Dual Level Audibles
The recommended technique for connecting Dual Level Audibles is shown in Figure
31. Link R40 must be cut. Although only 4 outputs are provided for each type of
Audible, the Module is capable of driving up to 8 Audibles at Quiet or 8 Audibles at
Loud (for example, using a white terminal strip to expand the wire connections).
Separate monitoring of Loud and Quiet outputs is provided by the Audible Driver
Module, but only one wire interconnecting the motherboard Input Return pins and
the Audible Driver Module Mon COM pins is required.
Note that Special Conditioning is required to perform the monitoring. If more than
one Audible Driver Module is connected, the monitor outputs from each module
must be taken to separate digital inputs and utilise separate blocks of Special
Conditioning code.
SK3 row 32
Audible
Driver Module
Loud
Audible 1
Loud
Audible 4
Loud O/P +
Audible COM
Loud O/P +
Audible COM
nd
LSLS I/P
ADRV 2 stream
LSLS Return
Return
R40
O/P+ LINK
NOT FITTED
Quiet
Audible 1
Quiet O/P +
Audible COM
ST750ELV
SK4 (row 6)
EN
EN +
COM
EN COM
Outputs
Quiet
Audible 4
Quiet O/P +
Audible COM
LQ COM
Optional: EN COM
to COM wire covers
LQ also
LQ
LQ +
Mon ML
Input AUD_ML2
Return
Mon COM
Variant /002 with output
monitoring is supplied
as standard.
Mon COM
Mon MQ
Optional
Return
Inputs
Input AUD_MQ2
recommended that the same physical input numbers are used, allocating them using
the IOA command.
4.14
the green drive period. This prevents non-sighted pedestrians from starting to cross
near the end of the pedestrian phase green period. The enable input of the tactile
must be cabled back to the Normally Open output of the IO card in the cabinet.
When the IO card output is closed, the tactile will run when the green drive is on.
When the IO card output is open circuit, the tactile will not run, even if the green
drive is on.
When running a tactile with input enable facility, if the facility is not to be cabled
back to the controller cabinet, then the enable inputs of the tactile must be shorted
together using a short wire link. Without this link, the tactile will not run even if the
green drive is on.
Some manufacturers tactiles (e.g. Radix Traffic ITE220, BIC B0302) also have a
fault output that can be wired back to an input of a digital IO card in the controller
cabinet. This fault output has the following functionality:
ITE220 Function
Fault Output
Open-circuit
Open-circuit
Open-circuit
Closed-circuit
4.15
The ELV Solar Cell (light sensor) connects directly to terminal block SK4 on the
termination backplane.
The solar cell is powered from -24V DC from the PSU / I/O Card.
For detailed connection information see section 7.14.4
4.16
AGDs provide detection for pedestrians and vehicles. The power for AGDs is taken
from terminal block SK4 on the termination backplane or, if more current is required
than this supply can support (2.0A) then a separate -24V DC supply (2A) can be
fitted.
The AGD outputs connect directly to the I/O card inputs. See documentation
relevant to the particular AGD devices being used.
For detailed connection information see section 7.14.5.1
4.17
The regulatory sign expansion kit is required whenever it is required to connect ELV
regulatory signs to an ST750 ELV controller. It consists of a separate transformer
and pcb module for powering up to 12 signs. Lamp monitoring is performed (if
required) by two external monitor input channels, connected to SK5 on the
termination backplane.
The number of detectors which can be powered from the ST750 ELV may be
extended by the addition of a 50VA additional power supply kit.
For detailed connection information see section 7.15
5.
The controller rack may be fitted into enclosures other than the single sided ST750
ELV cabinet. In the UK, the controller may only be fitted into an HA-approved
enclosure.
The procedure for fitting an ST750 ELV controller into an alternative enclosure is
very dependent on the type of enclosure and the type and position of existing
equipment. For this reason it is not possible to define in detail exactly what needs to
be done but generally the procedure follows that described in sections 6 and 8.4.
Cuckoo kits for the following cabinets only are available:
T400L T500L Cabinets
T400S T500S Cabinets
ST800PL Cabinet
Microsense Pelican
Note
5.1
Each cuckoo kit is supplied complete with a ST750ELV Controller EMC Kit Assy
667/1/33780/000. In order to comply with the conditions of CE marking on the
ST750ELV it is essential that this kit is installed in the cabinet.
If this kit is not installed then the EMC performance of the controller will NOT comply
with EN50293 as required by the conditions of CE marking in the UK
5.2
Some cuckoo kits re-use the mains distribution arrangement of the existing cabinet.
If this is the case it is essential to ensure that, as a minimum, the controller is
protected by a fuse of similar type and rating to that used in the ST750ELV Mains
distribution panel.
See section 11.5A.2.1 for details of suitable fuse (Master Switch Fuse)
5.3
Non-UK Racks
For Non-UK supply, the ST750ELV is available as a basic rack only ((ST750ELV
BASIC NON UK RACK ASSY SMALL INT).
This rack, on its own, must NOT be installed in countries requiring CE marking. If
CE marking is a requirement then, in addition to the Rack Assy the following kit must
be called up and installed in addition to the Rack Assy:
667/1/33780/000 ST750ELV CONTROLLER EMC KIT ASSY
6.
PEDESTRIAN FACILITIES
6.1
Red
Red
3
Flashing Amber
Green
PAR
MIN
Red
Flashing Green
PIT n 0
PIT n 1
Green
PIT n 2
Red
Red
3
Red
Green
PAR
MIN
Green
R/A
PBT
CDY0 2
IPX
Gap Change
On-Crossing Detector:
Max Change
R/A Green
Red
Red
CMX
CDY1
On intersections, the appearance of the vehicle phase will be delayed further if the
IGN intergreen time is larger than PBT plus the red/amber period.
6.1.3 Far Sided Pedestrian Crossing
The vehicle to pedestrian intergreen on a stand-alone crossing is controlled by PAR.
However if the far-sided pedestrian phase is part of an intersection stream, then this
period is controlled solely by the IGN intergreen command.
The pedestrian to vehicle blackout clearance period consists of:
a minimum period governed by PBT p,
an extendable period limited to a maximum governed by CMX p,
a gap clearance delay CDY p 0*, or
a max clearance delay CDY p 1
where p is the pedestrian phase letter.
Following this blackout clearance period, there is a clearance all-red period CRD p.
0 The gap clearance delay CDY p 0 is usually set to zero and hence is not shown
on the following diagram.
Red
Red
3
Green
PAR
MIN
Green
R/A
Red
Blackout
PBT
CRD 2
IPX
Gap Change
On-Crossing Detector:
Max Change
R/A Green
Red
Red
Blackout
CMX
CDY1 CRD 2
If a fixed black-out period is required, i.e. with no on-crossing detectors, then CMX
should be set to zero so that the black-out period is controlled solely by PBT:
Red
Red
3
PAR
R/A
Green
Blackout
MIN
PBT
Green
Red
CRD 2
On intersections, the appearance of the vehicle phase will be delayed further if the
IGN intergreen time is larger than PBT plus CRD plus the red/amber period whether
CMX is zero or non-zero. But for backwards compatibility, if CMX and CRD are both
zero, then the intergreen is controlled solely by IGN even if PBT is set longer.
6.1.4 On-Crossing Detectors
On-Crossing Detectors are above ground detectors that are used to determine
whether pedestrians are still crossing. While pedestrians are still crossing, the
extendable clearance period is extended, up to its configured maximum (CMX in the
above diagrams).
The on-crossing detector inputs are configured using IC4 and the extension times
are configured on an input basis (i.e. IPX).
If an on-crossing detector is unused, i.e. where several have been configured by
default on a stand-alone controller, it can be de-allocated using IOA. If no
extendable clearance period is required on a particular phase, then the clearance
maximum time (CMX) can be set to zero. If all of the on-crossing detectors for a
phase are de-allocated but the clearance maximum time is non-zero, then the
clearance period is extended up to its maximum.
Also note that if the Continuous Ped Demand (CPD) button on the manual is
pressed, then the red clearance of near-sided signals will be extended to its
maximum as required by TR2500A.
If an on-crossing detector has not been activated from the end of the preceding
pedestrian clearance period to the end of the current pedestrian steady green
period, then the clearance period is forced to run to its maximum.
A fault will not be recorded if this occurs, instead the controller will wait until the
normal DFM time-outs confirm and report a fault.
6.2
A stand-alone pedestrian crossing can run any of the following modes of operation:
6.2.1 Fixed Vehicle Period
The vehicle phase appears at green for at least a fixed period. No vehicle detection
equipment is required.
If the pedestrian phase is demanded while this period is still running, the vehicle
phase remains at green. When the period expires, the vehicle phase loses right of
way and the pedestrian phase subsequently appears at green.
If the pedestrian phase is demanded after this fixed vehicle period has expired, then
the vehicle phase immediately (subject to the pedestrian demand delay see section
6.3.3) loses right of way and the pedestrian phase subsequently appears at green.
When the pedestrian phase has completed its green period and the controller has
executed the required pedestrian to vehicle clearance period (see section 6.1), the
vehicle phase returns to green.
The fixed vehicle period is specified by the handset commands MEX, MFX, MGX
and MHX allowing four different times to be called up at different times of the week.
6.2.2 Vehicle Actuated
This mode requires vehicle detection equipment, either inductive loops cut into the
roads surface or above ground detectors (usually microwave detectors) mounted
on the signal poles. Activations on these inputs start (or restart) the extension time
for the phase and while this is active, the vehicle phase will (normally) remain at
green.
The vehicle phase appears at green for at least a minimum period specified by the
MIN handset command.
If the pedestrian phase is demanded while this period is still running, the vehicle
phase remains at green until at least this period has expired.
If the pedestrian phase is demanded after this minimum period has expired and no
vehicles are present, then the vehicle phase loses right of way immediately.
If the vehicle detectors indicate that vehicles are present, then the vehicle phase will
remain at green until the vehicles are no longer present. This is referred to as a gap
change since the vehicle phase loses right of way to service the pedestrian demand
when a gap in the traffic appears.
However, when the pedestrian phase is demanded, the vehicle phases maximum
green timer is started. If vehicles continue to be present, keeping the vehicle phase
at green, the vehicle phase will lose right of way when this timer expires, even if
vehicles are still present. This is referred to as a max change since the vehicle
phase loses right of way when its maximum green time expires.
The maximum green time is specified by the handset commands MAX, MBX, MCX
and MDX allowing four different times to be called up at different times of the week.
When the pedestrian phase has completed its green period and the controller has
executed the required pedestrian to vehicle clearance period (see section 6.1), the
vehicle phase returns to green.
6.2.3 Vehicle Actuated with Pre-Timed Maximum (PTM)
This mode is very similar to normal vehicle actuated mode, except that the vehicle
phases maximum green timer is started as soon as the vehicle phase appears at
green, regardless of whether there is a demand for the pedestrian phase.
The option is enabled using the PTM handset command.
Therefore, if the vehicle phase has already been at green for longer than its
configured maximum green time when a push-button is pressed, the vehicle phase
loses right of way immediately subject to the pedestrian demand delay (see section
6.3.3) or the pre-timed maximum extra period.
Compare this to the normal vehicle actuated mode, where the pedestrian would
have to wait for up to the maximum green time (if vehicles continue to be present)
before the vehicle phase loses right of way.
6.2.4 Linked Operation
With the controller running any of the above three modes, the operation controller
can be further modified by various linking options.
These options hold the vehicle phase at green until a specific time when the
pedestrian phase is allowed to appear. During this window vehicle extensions are
removed to ensure that any pending demand for the pedestrian phase is serviced.
This is often required, for example, when the pedestrian controller is close to an
intersection where it is beneficial to keep the pedestrian controller at vehicle green
during certain stages of the intersection controller to help the traffic entering and/or
leaving the nearby intersection.
Cableless Link Using the controllers Master Time Clock and CLF facilities, the
controller can be given one or more windows during the CLF cycle when it is
allowed to service the pedestrian demands. For the rest of cycle, the vehicle phase
remains at green.
UTC The PV control bit from the instation holds the vehicle phase at green.
When the PV bit is de-activated for a short period, the controller will service any
pending demand for the pedestrian phase.
Local Link The PV1 input from an adjacent controller holds the vehicle phase at
green. When the PV1 bit is de-activated for a short period, the controller will
service any pending demand for the pedestrian phase.
6.3
6.3.1 Introduction
In addition to pedestrian push buttons, the controller can be configured with cycle
detectors and kerbside detectors. The controller firmware treats cycle detectors
and push-button inputs the same and both should be configured to demand the
phase in the usual way.
Kerbside detectors allow the controller to cancel the demand (and switch off the
wait / demand indicator) if the pedestrian crosses before the pedestrian phase gains
right of way, see section.
A push button input can be associated with a specific kerbside input in order to
determine the type of pedestrian demand inserted. A kerbside input can be
associated with one or more push button inputs, or it can be associated with none in
which case it is only used to hold and cancel the demand.
SPECIAL
CONDITIONING
READ/WRITE
ACCESS
PUSHBUTTON
ACTIVE
(ENG 254)
OR
NOT
SET
DEMAND
BUT NOT
KERBSIDE
KERBSIDE ACTIVE
ROW
CLR
KBSACT
OR
x4
LATCHED
PUSHBUTTON
PBNLAT
(ENG 284)
(ENG 255)
ALL KERBSIDES
INACTIVE
PUSHBUTTON &
KERBSIDE LATCH
SET
PBKLAT
(ENG 256)
LATCHD
1WTCTRL
(ENG 197)
CLR
OR
ROW
VARIOUS
FACILITIES
UNLPUF
PDX
OR
NOT
IPX
AND
PEDBUT
OR
(ENG 29)
OR
PHASE
DEMAND
PROCESSING
OR
WAIT /
DEMAND
INDICATOR
PBNACT
AND
PDD
IPX
DEMAND AND
KERBSIDE
INPUTS
KERBSIDE
DEMAND
In VA mode, if no real phases in the same stream are at right of way, the delay is
introduced, so delaying the appearance of the pedestrian green after a quiescent
all-red period, for example.
In all other modes, the delay will always be introduced. This is to cater for cases
such as fixed vehicle period mode, UTC inserting a demand dependant force for
the pedestrian phase, or CLF introducing a demand dependant move just after
the push-button is pressed. Introducing the delay prevents these cases making a
stage move shortly after the push-button is pressed. In most other cases, the
demand delay will have little or no effect.
Note that special conditioning can always be written to short-circuit the pedestrian
demand delay if required under certain circumstances by putting in an unlatched
demand for the phase if the wait indicator is lit.
6.3.4 Pedestrian Demand Cancel (PDX)
The unlatched phase demand is cleared when all kerbside detectors and their
extensions for the phase have been inactive for the configured pedestrian demand
extension time for the phase (PDX). The wait / demand accepted indicator will be
extinguished if there are no other demands present for the phase.
Note that the phase may still appear at green if the controller has already started the
move to the stage in which the phase appears.
6.3.5 Kerbside Detector (Mat) Testing
Kerbside detector testing can be performed by the firmware to check the operation
of kerbside mat detectors.
Every 60 seconds, if there are no pedestrian phase demands active and no pushbutton (or cycle) inputs active, the controller outputs a 500ms (50ms) test pulse on
a configured output. If the output is de-allocated using IOA, no kerbside testing will
be performed.
This output is connected to all the kerbside detectors and should result in all of the
kerbside inputs going active during the pulse.
Therefore, the test is not performed while a pedestrian demand exists since this will
extend the pedestrian demand if the kerbside input has just gone inactive and the
controller is timing off the kerbside and demand extension periods.
Nor is the test performed while any push-button or cycle inputs (or their extensions)
are active since the kerbside test will activate the kerbside inputs even though noone may be present and allow these inputs to produce a demand for the pedestrian
phase.
Each configured kerbside detector is sampled twice and if either sample on a
particular kerbside detector indicates the detector is inactive*, the detector is logged
as faulty, the DFM indicator is illuminated and the detector input forced active
(regardless of the setting of the DFM forcing action command DFA).
* Note that for the input to be seen inactive at the 200ms processing rate, all ten
20ms samples must have been inactive.
Thereafter, the force is only removed after 5 consecutive tests of the detector have
passed, but the fault log entry remains set and the DFM indicator remains
illuminated, until RFL=1 is entered.
If the maintenance engineer enters RFL=1, the controller will automatically perform
a test. If a kerbside detector which was reported as faulty passes this test, even if
this is the first test that it has passed, the fault log entry for that detector is cleared
and the detector is assumed to be working. This means that when the maintenance
engineer fixes a kerbside detector, they do not have to wait for 5 automatic tests
before they can clear the fault, they just need to enter RFL=1.
7.
This section details the procedure for installing and commissioning of the ST750
ELV pedestrian controller in both the small and large controller cabinet
arrangements.
Refer to section 5 for instructions on installing and commissioning of the ST750 ELV
Rack Assembly into other traffic controller cabinets.
7.1
Pre-installation checks
The following checks should be carried out at the service centre and again on site,
with the exception of the pre-installation self-test which can only be carried out at
the service centre.
The controller cabinet should be visually inspected to check for any damage that
may have occurred in transit. Check the security of all internal wiring, PCBs/boards,
racks and fixings.
7.1.1 Hardware check
Check against the Works Specification that:
-
the correct boards and kits (including the Firmware PROMs and PLD) have been
supplied and fitted correctly.
the correct interconnection cabling has been installed within the controller
cabinet, e.g. Detectors to Rack Assembly, OTU to Rack Assembly, etc.
if the on site incoming main supply voltage is known, you should select the
correct transformer tapping from Table 14 section 7.12.
Once the hardware has been checked as above, it is recommended that a selftest is run (see section 11 ) before leaving the service centre.
7.2
The controller cabinets are normally delivered from the manufacturing department in
a fully assembled and tested state. However to aid installation, the internal
equipment has been designed to be readily removable. All of the electronics should
be removed from the cabinet if:
-
7.3
the controller cabinet is un-powered and will suffer from condensation, moisture
ingress and animal/insect infestation.
there is a risk of the equipment being damaged by the contractor.
the controller cabinet will be left un-powered for a prolonged period.
Site suitability
The ST750 ELV controller cabinet is installed to suit local conditions, but subject to
the following limitations:
(i)
The position of the controller cabinet is as shown on the relevant site plan,
STS.
(ii)
No part of the Cabinet is less than 457mm (18 inches) from the kerbside
unless agreed with the customer.
When it is necessary to site the controller cabinet less than 2 metres from the
outer edge of the kerb, the access panels should not open toward the
carriageway. Where no pedestrian guard rails are fitted, a clearance of at
least 600mm should be left between the cabinet and the kerb edge so that
guard rails may be installed at a later date without the need to disturb the
cabinet installation.
(iii)
Any person having control over the junction, whether manual control or test
box simulation, MUST have a good view of the intersection.
(iv)
7.4
The following list details the order in which it is recommended that an ST750 ELV
installation take place in the ST750 small case, generally known as the ST400S
case.
It should be noted that the ST750S case is not designed to have the
controller stool removed. If the two parts are separated the stool will
WARNING flex and once concreted in the ground it may NOT be possible to refit
the controller cabinet to the stool or it may result in the case
becoming distorted.
The following list details the order in which it is recommended that an ST750 ELV
installation take place.
7.5
The following list details the order in which it is recommended that the ST750 ELV
installation take place.
-
Telecom or fibre cable by installing a suitable size flexible duct. This duct
itself may then be sealed with expanding foam sealant.
7.5.1 Remove the controller cabinet from the stool
Remove the stool by removing its four fixing nuts and bolts and lift the controller
cabinet off the stool.
7.5.2 Install the stool
A hole should be excavated and a flagstone at least 900mm x 600mm embedded
securely at the bottom of the hole. Refer to Figure 31 for the general method of
installation and dimensions.
If the ST750 ELV controller cabinet is being installed on a slope, allowance must be
made for ground level clearance of the door to the uphill side.
The stool is placed in the centre of the flagstone with the top surface between 50
and 75 mm above the final ground level. It is essential that the stool be fitted the
correct way round with the single centre edge holes to the front and the CET
fixing holes on the right, as shown in Figure 31. Adjustment may be required to
ensure that the top of the stool is horizontal; this should be checked using a spirit
level.
Mix up a stiff mixture of concrete (mix: 1 cement, 3 sand, 4 coarse aggregate
(20mm) with no excess water) and cover the flagstone to a height approximately
100mm (4) above the bottom of the stool. The concrete must be sloped to provide a
run up for the cables. Any cables that already enter the pit must be held away from
the wet concrete. Where there is a risk of freezing, a suitable antifreeze additive
should be incorporated in the concrete mix to ensure proper curing.
All cables into the ST750 ELV controller cabinets should be fed through the ducts
and into the stool/base as close to the controller termination positions as possible.
This is to prevent unnecessary damage being caused should any cables need to be
moved once they are in place. Care must be taken not to obstruct the Electricity
Supply Company cut-out with any cabling.
The outer sheathing must be stripped to expose the armouring. It is suggested that
between 55mm and 65mm of the inner sheathing is left above the Hose Clip and
stripped armour (see Figure 1), which is more than normally required for other
Cabinet Assemblies. This is due to the height of the CET bar and its staggered
fixing nature. The additional height ensures that double insulation is provided where
the cable rests against the metal items. Sufficient further conductor length must also
be allowed to reach the terminal blocks via the proper routing.
The cable is inserted in the CET ring and the armoured wires are bent outwards and
down against the ring. A hose clip is then placed over the armoured wires and
tightened up. The armouring must be stripped, leaving a small amount (approx. 0 to
2mm) below the level of the CET ring.
The inner sheathing is removed to expose the individual cores that are connected to
associated terminals, leaving sufficient spare length for re-making off the ends
should this become necessary. Unused cores should be left with sufficient length to
enable them to be connected to any terminal should this subsequently become
necessary.
The ST750S ELV, controller cabinet (Small outer-case) has 2 CET bars and the
CET bars are mounted directly to the controller cabinet. Each bar has 8 holes for
fixing cables; 4 upper and 4 lower fixing positions. This allows the CET rings and
hose clips to overlap each other. The cables must be identified as to their
destinations and additional Idents may be required on specific contracts.
The ST750L ELV controller cabinet (Large outer-case) has 2 CET bars as standard,
but can be expanded to accommodate additional cables, and the CET bars are
mounted directly to the controller cabinet stool. Each bar has 6 holes on each side
for fixing cables. These holes are staggered to allow the CET rings and hose clips to
overlap each other. The cables must be identified as to their destinations and
additional Idents may be required on specific contracts.
SIDE VIEW
Mounted at CET Lower Fixing Position
Cores
Inner Insulation
Ident
55mm
to
65mm
Higher CET
Fixing Position
Lower CET
Fixing Position
Stud
Hose Clip
Nut
Ident
(Alternative position)
CET Bar
Incoming Cable
CET Ring
(Earthing Band)
PLAN VIEW
Earthing Band
667/2/02348/000
7.7
When all the cables have been terminated onto the CET bar they should be
checked and tested as defined in the General Installation and Commissioning
Handbook 667/HE/20664/000
7.8
If the controller cabinet was not installed with the mounting stool then it should be
done as follows:
Clean the top surface of the stool and the lower surface of the cabinet that will be in
contact when the cabinet is fitted.
The cabinet is installed by lowering it onto the stool and fitting the four retaining
bolts.
When fitting the cabinet onto the stool, make sure that all the cables are in their
correct position with regard to the CET bar. Once the cabinet has been secured,
moving of the cables could cause damage.
7.9
On completion of the cable tests the controller cabinet and stool can be back-filled
by the civils team using the appropriate material for the site layout. Once the backfill is completed in-fill with kiln dried sand as per Figure 30 and 31, taking care that
the compacted sand is at ground level when finished.
If any of the cables were replaced or moved during the installation of the controller
cabinet then the kiln dried sand in-filling must be made good before the sealing
compound is introduced.
NOTE: The back-fill must be brought to a level such that once the decorative top
surface is completed that the finish is at the surrounding ground level. The site
should be finished to the requirements listed in section 7.3 particularly paying
attention to any hardstanding around the controller base.
7.10
To prevent condensation and infestation in the controller cabinet the base MUST be
sealed as soon as possible after the controller has been installed. If any of the
cables were replaced or moved during the installation of the controller the kiln dried
sand in-filling must be made good before the sealing compound is introduced.
NOTE: The in-filling, kiln dried sand, must be brought to ground level or above and
compacted. Make sure that the kiln dried sand is level or slightly sloped down where
it meets the cables so it will not prevent the sealant meeting the cable.
The sealant should be poured all around the cables and to a height which, when the
sealant is set, gives a total covering not less than 6.5mm thick over the base of the
controller cabinet base. Use between 2.0 to 3.0 litres of approved epoxy resin for
the large controller cabinet base and 2.0 Litres for the small controller cabinet base
this will give an adequate and even cover.
This will act as a preventative barrier against the ingress of moisture and
animal/insect infestation.
A concrete fillet around the outside of the stool may be completed before or after the
epoxy sealing to suit site conditions.
Refer to Figure 31 and 32 for general method of in-fill, kiln dried sand, sealing and
concrete fillet.
WARNING
7.11
Should the controller cabinet base/stool NOT be in-filled with kiln dried
sand and sealed with an approved epoxy resin the controller
electronics/electrical circuits may be damaged.
With a suitable multimeter set to read AC volts, measure the incoming mains supply
voltage and select the transformer tapping according to the table below:
Issue 3 (and lower) Lamp Transformer has primary taps for
220/230/240V operation and 110/120V operation
Note
Issue 4 (and higher) Lamp Transformer has an additional primary
tap for 250V operation
Measured
Voltage
Select Transformer
Tapping:
245V to 276V
235V to 244V
240V
225V to 234V
230V
187V to 224V
220V
115V to 138V
120V
94V to 115V
110V
Note
250V
240V
230V
230V
220V
120V
120V
110V
0V
Earth
Connections to the transformer are made in accordance with Figure 37 to Figure 42.
Live in
Neutral in
Earth
250V
240V
230V
230V
220V
120V
120V
110V
0V
Earth
Live in
Neutral in
Earth
250V
240V
230V
230V
220V
120V
120V
110V
0V
Earth
Live in
Neutral in
Earth
250V
240V
230V
230V
220V
120V
120V
110V
0V
Earth
Note that there are two inputs marked 230V either may be used when connecting
to a 230V mains supply
Live in
Neutral in
Earth
250V
240V
230V
230V
220V
120V
120V
110V
0V
Earth
Live in
Neutral in
Earth
250V
240V
230V
230V
220V
120V
120V
110V
0V
Earth
Live in
Neutral in
Earth
7.12
The Master Switch assembly is located on the lower right hand side of the cabinet.
As part of the assembly, two RCD protected maintenance sockets are provided
mounted above the Master Switch unit itself.
The Master Switch unit includes the following
WARNING
With the controller switch in the OFF position the AUX supplies and
maintenance sockets will REMAIN powered
Connection
to Aux
Equipment
WARNING
The incoming mains connections are made to the bottom of the Master Switch,
being careful to observe correct polarity
Connection to the AUX supply is made on the top of the relevant MCB (Live) and the
adjacent neutral block (Neutral).
WARNING
7.13
The following guidelines apply when the ST750 ELV Rack Assembly is installed in
the ST750 ELV Cabinet Assembly or any other controller cabinet.
All intersection cables and their wires must be run up the rear panel of the cabinet,
directly in line with the street cable termination area on the backplane and secured
to it the rear panel and /or Rack Assembly with cable ties.
If Intelligent Detector Backplanes are used to house Loop detector cards, the loop
tails must be run directly to the appropriate Loop Termination board on the rear
panel of the cabinet and secured with cable ties.
If single detector backplanes are used to house Loop detector cards, the loop tails
must be run directly to the appropriate white terminal block on the rear panel of the
cabinet and secured with cable ties. A twisted pair soft-wire connection is then
made to the appropriate detector backplane and secured with cable ties.
Connections between the detector backplane and controller IO will be defined by
IC4 and will either involve connection to the street cable termination area of the
Rack assembly backplane (inbuilt IO) or to the additional IO card if fitted.
Note: No wire runs or looms should be positioned directly in front of or above the
ST750 ELV Rack Assembly, in such a way as to prevent removal of either the cards
or Rack Assembly for maintenance or replacement. Securing holes are provided to
secure cables along the top and bottom edges of the Rack assembly.
Wiring runs should be made neatly and routed to allow enough spare cables for
possible changes/additions at a later date.
Spare cores are to be bundled and routed to a convenient position clear of mains.
The ends are to be insulated to make the loom secured. If it is required to terminate
spare cores they may be connected to spare positions in the Returns terminal block
in the street cable termination area of the Rack Assembly backplane.
If cable idents are required then these are fitted to cores before termination.
Signal and Detector terminations to the ST750 ELV Rack Assembly should be as
per the Works Specification, leaving sufficient spare wire to enable joints to be
remade when necessary. The Pair cable used for connection from the loops should
be terminated using the appropriate kit.
7.14
For installation in an ST750 ELV Cabinet, wire the intersection cables directly to the
specified terminal in the following sections on the Terminal Backplane Assembly.
Note
WARNING
7.14.1
Function
10
11
12
13
14
15
16
4 wire connections
per output
Output
Designation
Function
10
11
12
13
14
15
16
17#
18#
19
20
21
22
23
24
25
26
27
28
29
30
31
32
All connections
go to Ground on all
four tiers
Note
Termination
Backplane
Input connection
(I/P 6 shown)
Return connection
(I/P 6 shown)
Bottom Tier
Mid Tier
Top Tier
Output 1 Normally
Open
Output 1 Common
Output 1 Normally
Closed
Output 2 Normally
Open
Output 2 Common
Output 2 Normally
Closed
Output 3 Normally
Open
Output 3 Common
Output 3 Normally
Closed
Output 4 Normally
Open
Output 4 Common
Output 4 Normally
Closed
NO
Connection
(O/P 2
shown)
NC
Connection
(O/P 2
shown)
Common
Connection
(O/P 2
shown)
Figure 51 - Relay Output Connections SK4
Mid Tier
Top Tier
SK4
SOL
COM
SOL
-24V
Red/Black
Black
White
SIG
ELV Solar
Cell
Note
24V DC Loop Detector Supplies are negative with respect to ground i.e.
the positive side of the supplies is grounded.
Top Tier
Ground (Positive)
-24V DC
Ground (Positive)
-24V DC
Ground (Positive)
-24V DC
Ground (Positive)
-24V DC
Ground (Positive)
-24V DC
Ground (Positive)
-24V DC
Ground (Positive)
-24V DC
Ground (Positive)
-24V DC
Ground
(Positive)
-24V DC
+
AGD
Mid Tier
Top Tier
1-4
Audible 1Loud
Drive Output
Positive
Monitor Common
Audible 1 Loud
Monitor Output
Loud
Connection
Positive (+)
Quiet
Connection
Positive (+)
Common
Return
Negative (-)
LO
Connection
s to 6
Audibles
(Loud)
SK4
COM
Returns
from 6
Audibles
(Loud)
If it is required to test the voltages applied to the audibles, the following procedure
should be used:
Note
Connect negative of meter to one of the COM connections on SK4 (note that they
are all connected together)
Connect positive of meter the relevant LOUD (LO) or QUIET (QU) output on SK4 to
be checked
When the sounder is supposed to be ON a voltage reading of approximately 12V
should be obtained.
SK4
SK6
Note
See section 4.13 and 4.13.1 for details of installation. Illustrations of the relevant
ST750ELV motherboard connections (AUD2 COM/EN/LQ and Digital Inputs 22 and
23) are also available in section 7.14.6.1 above.
If it is required to test the voltages applied to the audibles, the following procedure
should be used:
Note
Connect negative of meter to one of the AUDIBLE COM connections on the Audible
Driver Module (note that they are all connected together).
Connect positive of meter to the relevant LOUD (LO O/P+) or QUIET (QU O/P+)
output on the Audible Driver Module to be checked.
When the sounder is supposed to be ON a voltage reading of approximately 12V
should be obtained.
7.14.7
Tactile Connections
The ST750 ELV supports 2 pedestrian phases. Each of the two pedestrian phases
has 3 separate outputs (marked TACT on backplane) for tactiles. Each output can
be fitted with a maximum of 4 tactiles in parallel.
.
Note
Warning
Note
Do not try to use a single common return between the tactile and the
IO card (ie do not link the IO card Input Common to Output
Common)
7.14.8
PCB
Position
Transform
er
Position
Mains Transformer
48
1
48
0
5
white
Green/yellow
Blue/white
TB2
Blue/slate
TB2
slate
Power Input terminals on PCB
Figure 65 ELV Regulatory Signs Expansion Kit Power Wiring
Monitor connection 1
Monitor group
1
(REG1
REG6)
Feed to sign
Monitor group
2
(REG7
REG12)
Return
Monitor connection 2
10
Top Tier
Toroid 1 common
Toroid 1 signal
(blue)
(green)
Toroid 2 common
Toroid 2 signal
(blue)
(green)
Green
From PL1
Blue
Green
From PL2
Blue
Figure 67 - Reg Sign Monitoring Inputs SK5
Note
Take care to observe the polarity of the connections when terminating the
cable on the termination backplane. The blue wire of each pair must be
closest to the pcb.
7.15
The number of detectors which can be powered from the ST750 ELV may be
extended by the addition of a 50VA additional power supply kit.
Detector
Supply
Output
Mains Input
to
Transformer
7.16
Fuses
Fuses are mounted in two areas on the termination backplane that are easy to
access.
Note
Fuses should only be replaced with the correct type and rating
Type / Rating
FS1
Protects Lamp
Monitor Supply
connection via
PL12
500 mA Quick
Blow Ceramic 20 x
5mm
FS2
6.3mm
FS3
Detector Supply
Fuse
5A Anti Surge
ceramic 20 x 5mm
FS4
500 mA Quick
Blow ceramic 20 x
5mm
FS5
5A Anti Surge
ceramic 20 x 5mm
7.17
TC12 OTU
Retaining bar
and screw
ESB Cable
7.18
Gemini
A Siemens Gemini unit can be fitted into the ST750 ELV cabinet in a variety of
ways.
For the Small cabinet, the preferred method is to use the Gemini and Detector
Swing Frame Assembly as shown in Figure 74
There are two versions of this swing frame
667/1/33770/000 will accommodate the Gemini unit only
667/1/33775/000 will accommodate the Gemini unit plus up to four Loop
Detector cards (shown in Figure 74)
As an alternative, it is possible to fit an 11 swing frame kit to the cabinet along with
an 11 Detector Rack to rack mount the Gemini unit and/or Loop detector cards. For
appropriate part numbers see Appendix A.
For the Large cabinet, a 19 swing frame kit and detector rack may be fitted to rack
mount the Gemini unit and / or Loop Detector cards. . For appropriate part numbers
see Appendix A.
Mains power for the Gemini unit can be obtained from the AUX MCB supply on the
Master Switch Assembly. See section 7.12
Warning
When fitting the Gemini unit it is important that the internal battery is
correctly oriented. See Gemini Product Handbook for full details.
7.19
Lamp monitoring of Nearside, Wait, Demand units requires that ELV compatible
units have been fitted and that they contain p.c.b. assemblies which are ELV
compatible.
Compatible units are clearly marked with ELV labels both externally and internally.
However, p.c.b. assemblies can become swapped during servicing which may then
cause lamp monitoring failures. The Siemens Nearside and Wait/Demand units are
only fully compatible with ELV controllers when fitted with p.c.b. issues as shown in
the table below.
Nearside Unit
Nearside Aspects
LED Wait
LED Call Demand
PCB Assembly
667/1/30695/001
667/1/30695/002
667/1/30695/003
667/1/30695/004
667/1/30695/005
667/1/30695/006
667/1/30211/001
667/1/30680/001
ELV Compatible
Issue 9 and above.
Issue 9 and above.
Issue 9 and above.
Issue 10 and above.
Issue 9 and above.
Issue 10 and above.
Issue 4 and above.
Issue 3 and above.
8.
Note
8.1
Service-Centre Testing
Power the cabinet on and run the self-test (see Section 11)
Using the handset command CIC ensure that the number reported agrees with the
CIC printed on the IC4 printout
Using the handset command CRC ensure that the CRC reported agrees with that
printed on the IC4 printout.
Finally, before the cabinet leaves the Service Centre:
-
Note
8.2
On Site Testing
Once delivered to site and with reference to the Works Specification, check that:
-
Note
Open the Manual Panel door and set the SIGNALS ON/OFF switch to OFF
Switch the controller on
Via the serial handset, using the TOD command, enter the current date and
time into the controller
Switch the Controller off.
E30751
E30752
E30753
These configurations are available on the IC4 CD. The configuration data for an
ST750 ELV stand-alone pedestrian crossing is loaded through the handset port from
a PC running IC4, or by using a configuration PROM generated by IC4.
Other configurations may be produced by Siemens Poole in order to meet the
particular requirements of an area or of one particular site.
These configurations need to be customised for particular installations using the
handset using the information in the special instructions of the configuration
printout.
The commands to customise the ST750 ELV are described in the Handset
Handbook and in the Special Instructions. These allow facilities such as kerbside
and on-crossing detectors and speed discrimination/assessment to be enabled or
disabled. However, the fundamental lamp sequence (i.e. flashing green-man, redman or blackout clearance periods) cannot be changed using the handset and is
fixed in each of the default configurations.
The configuration data could be loaded while the ST750 ELV is still in the depot
rather than using a PC on the street. Provided the battery isolators are removed, the
configuration data will still be present in the battery backed-up RAM when the
ST750 ELV is installed.
The procedure for loading the configuration data is given in the Handset Handbook.
Once the configuration data has been loaded, ensure the Signals ON/OFF switch on
the manual panel is in the off position and connect a suitable handset to the 25-way
D-type connector on the ST750 ELV CPU PCB.
Warning!
Ensure that the signals are switched OFF and run the controller self-test (see
section 11). This illuminates each colour on each phase in turn for approximately 40
milliseconds. If there is any short in the cables the outputs are protected against
damage.
Following this test, use the LMP command to cause each colour on each phase to
come up in turn whilst other persons are checking the aspects.
Remove the power to the controller, switch the SIGNALS ON/OFF switch to ON and
power the controller up normally.
8.2.6 Solar Cell Testing
If the solar cell is fitted, carry out the following test:
Cover the solar cell for at least one minute to exclude any light and check that
the signals are dimmed as requested. Remove the cover from the solar cell
and the signals should revert to the bright condition.
8.2.7 Lamp Monitor Testing
Use the handset commands KLR=1 and KML=1 to force the controller to learn the
lamp loads and force demands for all phases (including bright/dim changes)
The handset will indicate COMPLETE once all lamp loads have been learned.
Use the KEL command to display the learned lamp load in Watts and verify that the
loads are as expected.
8.2.8 Junction System Testing
Using the detect lights on the AGDs, ensure that all AGDs (Kerbside and OnCrossing) are functional and have the required zone of detection.
Using the handset command IOP check that all road detector loops, AGDs
demand pushbuttons etc are correctly connected.
Clear all faults in the log and allow the junction to run normally. Periodically check
the log and ensure that no faults are raised. Verify that the controller has the correct
date and is keeping correct time.
8.3
Customer Acceptance
8.4
Leaving Site
Note
The key lock should not be operated unless the screw locks are tight, i.e. Unlock
the case before undoing the screw lock and only lock the case after tightening
the screw locks.
9.
This section contains a list of checks that must be performed on an ST750 ELV
controller on a regular basis (normally annually).
WARNING
The information in this section only refers to the controller. Testing of other
site equipment may be necessary. Refer to appropriate, country specific,
information for equipment installed on street.
For installations in the UK refer to 667/HE/20664/000 Installation and
Commissioning Handbook Installation Testing (General)
These instructions override any others that may exist. If a Site PI exists for the
specific site, it may contain instructions that should be carried out in addition to
those detailed below.
WARNING
9.1
Note
The key lock should not be operated unless the screw locks are tight, i.e. Unlock
the case before undoing the screw lock and only lock the case after tightening
the screw locks.
Inspect the main door seal and Manual Panel gasket, ensuring they are intact and in
the correct position. Replace as necessary ensuring that the surface is clean before
fitting.
Check the Manual Panel for any damage and replace if necessary. Check that all
functions operate correctly. Press the lamp test keypad and check that all LEDs are
operational.
Check the termination panel(s) and master switch panel within the controller and
ensure that there are no loose fixings, or damage to these panels. Tighten any loose
fixings and carry out any repairs that are necessary.
Check the Rack assembly and other assemblies within the controller are securely
fixed. Retighten loose fixings as necessary.
Ensure that no fault indications are showing. If any faults are revealed refer to the
fault-finding procedures in section 10.
WARNING
Test the 300mA RCD (if fitted) by pressing the test button. The breaker should
operate immediately.
Check that all fuses are secure in their holders. It is strongly recommended
that the controller supply is isolated before any fuses are checked.
Check wiring and cable forms, particularly ribbon cables for damage. Repair or
replace if necessary.
The battery on the Main Processor card must be replaced if it has failed. Any
replacement battery should be suitably marked with an appropriate date label.
Having done this, the controller records should be updated accordingly.
Note
The following tests require the controller to be powered and running normally.
With the handset, check that all inputs used are operating correctly.
Test the maintenance socket RCD by pressing the test button. The breaker
should operate immediately.
The following checks should be carried out before leaving the site.
Check the cabinet door seals are intact and in the correct positions. Replace as
necessary ensuring the surface is clean before fitting.
Inspect the cabinet base seal. If damaged, the affected area should be filled with
sand and re-sealed. For details see 667/HE/20664/000 Installation and
Commissioning Handbook Installation Testing (General)
9.2
Check that the real time clock is set correctly. If the controller is required to run CLF,
use the time of day (TOD) command to check that the real time clock is running the
correct time.
A true measurement of the accuracy of the real time clock can only be gained if the
clock with which it is compared has been accurately set up.
It is essential that the time be compared with an adjacent controller using a clock
that has been synchronised to that controller within the last 30 minutes.
10.
FAULT FINDING
Site Visits
When a fault report is received it is recommended that the following are checked:
(a) Is the fault a repeat one; i.e. is the fault and its cause known from previous visit.
Why was the controller left faulty? Can it now be cleared? I.e. are the resources
now available to clear it; if so go to site. If not, make an appropriate note in the
fault recording system, or on your fault report.
(b) If the report is DFM, i.e. detector fault, check to see if a fault is known to exist on
the site, especially if the fault is reported by an OMU as it may be a repeat alarm
for a reported fault. Because, unlike the controller, most OMUs cannot be made
to ignore faulty loops which have already been reported and, therefore, continue
to raise the alarm.
(c) If the controller is under UTC control, check with UTC centre to ensure that the
fault report is not a result of any problem with the UTC, e.g. OTU may be out of
action or faulty.
(d) If the Signal State is reported as being All Out, All Red or not giving right-of-way
to one approach try and check with the local authority/police as to whether they
know of a requirement for the signals to be in this state.
(e) Check that after clearance of the fault the controller may be re-commissioned
and switched on again; in some cases the local authority may require the
signals left off.
10.1.2
Before leaving for a site visit, it is recommended that the following be checked:
(a) Check that you have the correct equipment and sufficient spares to do the job
you are going out to do. See the spares list in section A.2.
(b) Check that all your spares are good; i.e. check that the replacement cards have
labels with test and inspection stamps on them. Ensure that none of the cards
have labels on them that would indicate they are suspect or have been removed
from a faulty site.
10.1.3
10.2
The following is a list of indicators in the ST750 ELV controller that assist in the
location and diagnosis of a fault. The state of each of these indicators should be
noted on arrival at a site before doing anything else.
10.2.1
The LED (behind the manual access door) is normally lit when the controller has
identified a detector fault, and flashes when the Controller has detected a red lamp
fault.
In some installations, the Cabinet Alarm may also be lit for other reasons - refer to
the Works Specification.
10.2.2
Master Switch
This removes the mains supply from the entire controller when opened, i.e. switched
off. Depending on cabinet installation this is normally mounted on a panel at the
bottom of the controller.
10.2.3
This is included in the Master Switch panel and removes power from the equipment
rack and equipment powered from it. This is a single pole MCB so does not provide
safety isolation. Also note that the maintenance socket is still powered when the
controller MCB is off.
10.2.4
If the SE light is on, then the processor will have shut the system down and logged a
fault check the fault log.
If the BE light is on, then the processor card has a major fault and cannot start. In
this condition it is unlikely that the card will communicate with the service terminal.
Power the system off, remove the card and check the firmware PROM is correctly
seated in the socket and the PHS card is correctly assembled to the main processor.
If the BE light lights when the processor is powered on again, replace the main
processor and PHS.
10.2.5
Fuse FS5 may be blown, if so replace wit the correct type and rating of fuse
If the fuse is intact, then suspect the PSU / I/O card has failed and replace it.
The green Audible LED on will only illuminate when the built in audible indicators
are being driven
10.2.8
correct, or link R40 is still fitted, check the polarity of the audible connections to the
module and re-test. Measure across the O/P + and Audible COM connections of
the module - the module will present approximately 12V DC when driving the
audibles. If this is present, then suspect the connection between the module and the
audibles and check that the audibles are not faulty by substituting a known working
audible.
Note that since Special Condition code for audible monitoring is included, the
monitoring function must be enabled (typically using CFE6=1) in order to enable the
audible output. If monitoring is not enabled, there will be no audible output and the
green PP LEDs will not light.
With monitoring enabled, faults in the circuit such as output short circuit will trigger a
system error, which will extinguish all the signals (with fault SCF1 in the fault log).
If this occurs, before conducting the fault tests described below, it would be
necessary to temporarily short EN+ to EN COM with a wire link. Audible
monitoring would then need to be disabled for the duration of the fault-finding tests
below (e.g. CFE6=0).
If the PP LED on the module fails to illuminate when the audibles should sound,
short EN+ to EN COM with wire. If a PP LED illuminates (and audibles sound) when
the LSLS output is on, suspect a faulty connection between the audible module and
SK4 or a faulty controller configuration causing the I/O function to inhibit the audible
module or a faulty PSU/ I/O card.
If the PP LED on the module still did not illuminate with EN+ shorted to EN COM,
remove all audible connections to the module. If the PP LED on the module now
illuminates when the audibles should sound, check for a short-circuit on one of the
audible connections either inside or outside the cabinet. Reconnect each audible
one at a time to find the faulty one. The module is protected indefinitely against
short-circuits on the output and will not be damaged.
If the PP LED on the module still does not illuminate with EN+ shorted to EN COM
and audible connections removed, then measure the voltage across the LSLS I/P
and LSLS RET pins of the connector. This should be at lamp supply potential (48V DC or -27.5V DC) when the module is being driven. If not, then suspect the
connection between LSLS and the module or the controller configuration or faulty
LSLS output.
If link R40 is cut and the wrong PP LED lights, check whether the LQ+ input is open
circuit or shorted to LQ COM. Open circuit should cause the Loud PP LED to light,
and short circuit should cause the Quiet PP LED to light. If the module functions
correctly (using a local wire link for this test if necessary) then suspect a faulty
connection between the audible module and the SK4 or a faulty controller
configuration causing the I/O function to request the wrong state or a faulty PSU/ I/O
card.
Finally, having shown that the module is getting power from the LSLS output AND
that the Enable input is shorted to enable operation AND that there isnt a short-
circuit on the audible output AND the loud/quiet input is driven correctly, replace the
Audible Driver module and re-test.
10.3
WARNING
Having first recorded any fault indications in the controller visit log, proceed with the
following.
Below is a list of symptoms produced by controller faults. Against each one of them
is the number of the subsection to which you must refer for the relevant fault finding
procedure.
Signals Lighting Incorrectly:
See sub-section
10.3.1
10.3.2
10.3.3
10.3.4
10.3.5
10.3.6
10.3.7
10.3.8
)
)
) see
) also
) 10.3.1
)
)
)
10.3.9
10.3.10
10.3.11
10.3.12
)
) see
) also
) 10.3.1
10.3.13
10.3.14
10.3.15
10.3.16
10.3.17
) see
) also
) 10.3.1
10.3.18
10.3.1
10.3.1.1 This procedure should be followed if, on arrival at the site, the fault
symptoms described in the fault report are no longer apparent or no
positive fault has been found after having followed another fault
procedure.
Check the contents of the Historic Fault Log (LOG handset command) for
faults that have been set and recently cleared. Refer to the ST900 Family
Handset Handbook for further details.
10.3.1.2 Have you just followed another fault-finding procedure, which has
resulted in no positive fault being found?
YES - Continue at 10.3.1.4
NO Proceed to the next point
10.3.1.3 Are there any LEDs on the Main Processor or PHS cards illuminated
which would indicate the controller has detected a fault?
YES - It is recommended that you move to section 10.2 and continue to
fault find starting from the fault indications.
NO - Proceed to the next point
10.3.1.4 Check the signal sequence on the street and on the LSLS LEDs
looking for irregularities.
10.3.1.5 Check that the controller operates correctly for the particular mode
that it is in. If the controller is capable of working VA but is not
currently in VA mode, then it is recommended that, if possible, it
should be tested in the VA mode to check that it is responding to
demands correctly and serving all phases.
10.3.1.6 Perform the electrical test specified in section 9.1.
10.3.1.7 Inspect the controller to ensure that all of the retrospective
modifications required on the controller and facilities have been
carried out.
Check all of the following:
Main Rack Assembly / Racking
All Cards
ELV Audible Module
Regulatory Signs Module
10.3.2.1 Are there any of the LEDs on the Main Processor card illuminated?
YES - It is recommended that you move to section 10.2 and continue to
fault find starting from fault indications.
NO - Proceed to the next point
10.3.2.2 Check to see if there are any indications of power on the controller.
Are there any LEDs on (illuminated)? Press the lamp test button on the
Manual Panel, do any of the Manual Panel indicators illuminate or does
the cabinet alarm lamp illuminate?
YES - There is power/mains supply reaching the controller, move to
10.3.2.4
NO - There is no power, Proceed to the next point.
10.3.2.3 Locate reason for loss of supply
Check the following:
(a) All DC supplies.
(b) Local area to see if there is a general power failure. (NB: This may
have been checked before on receipt of the fault report).
(c) Master switch and controller switch to see if either has been switched
OFF or tripped (in the case of an MCB). If either is OFF, then check as to
why they are OFF.
(d) If an RCD is fitted in series with the controllers power supply, check to
see if it has tripped. If it has then look for reason for trip, this may require
an insulation test to be carried out with respect to earth.
(e) Mains supply continuity throughout the controller referring to
667/DA/33743/000, and using a meter set to measure the relevant mains
supply voltage. If any fuses are ruptured investigate the reason for their
rupture in the following manner:
Switch off the mains supply switch which immediately precedes the
ruptured fuse. Using a meter set to measure resistance check for a low
resistance between live and neutral or live and earth. If a low resistance is
found then referring to 667/DA/33743/000, disconnect circuits until the
elimination fault is found.
If no low resistance can be found, check for signs of arcing within power
supply and wiring on termination panel.
10.3.2.4 Locate reason for signals off when mains supply on
Check the following:
(a) Lamp supply
NB: Normally if lamp supply has failed there is the fault log entry FLF17: If
there is no entry in FLF17 it is unlikely that lamp supply is at fault.
To check lamps supply further, do as follows. Using a meter set to
measure mains supply voltage and Power Circuit Diagram
667/DA/33743/000, check for supply at various points.
(b) See if the Signals ON/OFF switch on the Manual Panel is in the OFF
position.
If it is, check to see if there is any reason for the signals to be OFF (e.g.
road works, previous cable fault, or local emergency).
Do not switch the signals ON until any reason for them to be OFF is
cleared or no reason can be found.
When everything above has been checked, switch the signals ON and
observe signal operation.
(c) Is the controller part-time working? If it is, check to see if the
conditions for switching to part time (signals OFF) are being satisfied.
Example: Real time clock may be incorrect or loop detectors may not be
working.
(d) See if there is any special conditioning which can switch the signals
OFF.
(e) See if the conditions for switching the signals OFF are specified
correctly and are being satisfied.
(f) If signals are OFF and signals ON/OFF switch is requesting them to be
ON, check using Self Test (see section 11). Then check for faulty switch or
wiring (wiring from switch to Manual Panel card and Manual Panel to Main
Processor card).
10.3.3
displayed by these codes do not change for the particular port and bit
then it is either set permanently active or inactive.
(c) Check the configuration data/works specification to ensure that correct
input is being checked and demand that is expected is actually
configured. Make sure that CRC is the same as the printed
specification.
10.3.3.11 Lamp Switch cards indicate that lamp should be illuminated.
Check the following:
(a) See if the LSLS card is working, e.g. using a meter set to measure DC
volts, measure across the LSLS output and RETURN. The voltage
reading should be -44.6V (bright) or -25.4V (dim). If lower than this,
check for shorts on aspect wiring.
(b) The continuity of the wiring from the output of the Lamp Switch card to
the signal heads.
(c) The pole top connections.
(d) The signal heads.
Warning
10.3.4
Care must be taken when conducting tests on a controller with mains supply
connected to it. Where possible a test method should be used which does not
require mains connected to the controller.
10.3.4.1 Are there any of the LEDs on the Main Processor card illuminated
which would indicate the controller has detected a fault?
YES - It is recommended that you move to section 10.2 and continue to
fault find starting from the fault indications.
NO - Proceed to the next point
10.3.4.2 Do the LEDs on the relevant LSLS card(s) indicate that the lamp(s)
should be on:
YES - Continue at 10.3.4.5.
NO - Proceed to the next point
10.3.4.3 Is the fault all aspects of a certain colour stuck `ON' or `OFF' (i.e. all
ambers ON or OFF) when they should not be, possibly whilst other
aspects are switching normally?
AND
Is the controller configured for part-time/Standby mode?
NO - Proceed to the next point
YES - See also 10.2.
10.3.4.4 Disconnect all external wires from the relevant phase output
terminal(s), (care must be taken because, if it is a cable fault, then the
cable cores may be at mains supply potential). Using a meter set to
measure volts DC measure the voltage between the relevant phase
output terminal(s) and RETURN. Does the voltage permanently exceed
-15V (NB: 15V rms is considered to be the voltage at which a signal is
visible and deemed to be ON).
YES - Continue at 10.3.4.6.
NO - Proceed to the next point
10.3.4.5 Possible cable fault
(a) Check pole top connections and external cables for short circuits
and/or poor insulation. With the controller disconnected from the mains
supply (i.e. master switch open), short circuits may be found using a
meter set to measure resistance and checking core to core.
The insulation should be tested.
(b) Also check the connectivity/continuity of the return cables for the
particular poles/signal heads. A visual inspection of pole top
connections etc. is also worthwhile.
10.3.4.6 Replace the LSLS card, reconnect the external cables and check that
the lamp is no longer permanently lit and is lighting at the required
point in the signal sequence.
10.3.4.7 The Lamp Switch card is showing that the lamp should be on.
Check the configuration data and works specification to see if there is a
valid reason for the lamp(s) to be permanently lit, e.g. same phase in every
stage, special conditioning requires it to be permanently illuminated, etc.
10.3.5.1 Are there any of the LEDs on the Main Processor card illuminated
which would indicate that the controller has detected a fault?
YES - It is recommended that you move to 10.2 and continue fault-finding
starting from the fault indications.
NO - Proceed to the next point
10.3.5.2 Do the LEDs on the LSLS show the correct signal sequence?
YES - Continue at 10.3.5.4.
NO - Proceed to the next point
10.3.5.3 Check the configuration data and works specification. Is the sequence
being shown the correct one and/or is it the required sequence?
YES - No fault
NO - Proceed to the next point
10.3.5.4 Replace the LSLS card and check as to whether or not the fault has
been cleared.
10.3.5.5 Is the fault all aspects of a certain colour flashing (i.e. All ambers
flashing) when they should not be, possibly whilst other aspects are
switching normally?
AND
Is the controller configured for part-time/standby mode?
NO - Proceed to the next point
YES - Continue at 10.2.
10.3.5.6 Disconnect all external wires from the relevant phase output
terminal(s). (Care must be taken because if it is a cable fault, then the
cable cores may be at mains supply potential). Using a meter set to
measure volts DC measure the voltage between each of the
disconnected cable cores and RETURN. Does the voltage ever exceed
10.3.6.1 Are there any of the LEDs on the Main Processor card illuminated
which would indicate that the controller has detected a fault?
YES - It is recommended that you move to 10.2 and continue fault finding
starting from the fault indications.
NO - Proceed to the next point.
10.3.6.2 Check handset commands DOV and KDP. Check MPA to see if dim
override has been assigned a button on the Manual Panel.
10.3.6.3 Is dimming being overridden by UTC or Manual Panel dim override
switch?
If a UTC facility is provided, check the works specification to see if a dim
override facility is provided. If so check the state of the dim override bit
using the handset and the `IOP' command to examine the appropriate input
port.
To determine if dimming is being overridden by the Manual Panel switch
check condition of appropriate `dim/bright confirm' LED on Manual Panel.
Is dimming being overridden by UTC or Manual Panel dim override switch?
YES - Continue at 10.3.6.6.
NO - Proceed to the next point.
10.3.6.4 Run Self Test to check Dim/Bright relay.
A meter set to measure resistance may be used to prove continuity if
controller is isolated from mains supply; check using circuit diagram
667/DA/33743/000.
10.3.6.5 Check the siting of the solar cell to ensure that light from street
lighting does not prevent solar cell operating.
10.3.6.6 If dimming is being overridden by UTC, inform UTC centre (this may
be a requirement of the UTC centre or an OTU fault).
To further check the UTC dim override input, see section 10.3.13.
If dimming is being overridden by Manual Panel dim override switch then
check the following to see if there is a reason:
(a) Solar cell connections to the Termination Backplane.
(b) Does controller permanently dim if override removed? If it does, see
section 10.3.7 for fault finding. Clear fault before returning Manual
Panel dim override switch to normal position.
(c) Check controller visit log book to see if details of any previous visits
have a bearing on the situation.
CLF
UTC
FT
Priority hurry call
continue at 10.3.9.10
continue at 10.3.9.11
continue at 10.3.9.12
continue at 10.3.9.13
(c) Replace PSU / I/O Card (or I/O card if fitted) and re-check to see if
controller is now cycling.
(d) If, after having checked (a) to (c) above, the controller is still not
cycling, continue at 10.3.9.5.
10.3.9.12 FT Mode:
Do the following:
(a) Check fixed time timings. Excessively long times may make the
controller appear to lock up. Any timings which differ from the works
specification should be noted in the controllers `visit log book' if a
visiting engineer changed them.
Any timings over which there is doubt should be checked with the
customer to ensure they are as required.
(b) If, after having checked (a) above, the controller is still not cycling
continue at 10.3.9.5.
10.3.9.13 Priority/Emergency Vehicle and Hurry Call mode
Do the following:
(a) Check timings associated with the particular mode. Excessively long
times may make the controller appear to lock up.
Any timings which differ from the works specification should be noted
in the controller `visit log book' if a visiting engineer has changed
them.
Any timings over which there is doubt should be checked with the
customer to ensure they are as required.
Continue at 10.3.9.4.
10.3.9.14 Are permanent priority demands and/or permanent hurry calls being
received?
YES: Continue at 10.3.13. Check to see if the input is faulty
NO: Continue at 10.3.9.5. Check to see if there are any other reasons for
the controller to lock.
10.3.10
continue at 10.3.11.3
continue at 10.3.11.4
continue at 10.3.11.5
continue at 10.3.11.6
If after having completed checks for the mode of operation, no fault can be
found, check through the general reasons for slow signal response.
Continue at 10.3.11.7.
10.3.11.3 VA Mode:
The controller is in the VA mode and cycling too slowly.
Do the following:
(a) Check to see if any phases have permanent extension, using the
handset command SPH.
Note `SPH' only shows the extension timing whilst the phase is at green. If
this is insufficient then determine from the works specification which
signals provide extensions (e.g. AXYZ extends phase A) and to what input
port and bit the signals have been allocated. The `IOP' command can then
be used to view the status of the input ports to see if any of the inputs are
permanently active.
If any phases have permanent extensions, check appropriate input, see
section 10.3.13.
(b) Check to see if any phases are not receiving demands from the
appropriate call detectors. If a particular call detector is not inserting
demands, check appropriate input, see section 10.3.13.
(c) Check extension and maximum green times. If any times seem
excessive or are different from the works specification, check in
controller visit log book to see if timing has been changed and/or
check with customer to see if timing is as required.
10.3.11.4 CLF Mode:
The controller is in CLF mode and cycling too slowly.
Do the following:
(a) Check to ensure that, for all stages to which there are demand
dependant moves, all phases in those stages are receiving demands
from the appropriate detectors, using the handset command SPH.
However, if it is preferred, the input port which has the detector inputs
which create the demands can be examined using the IOP command
to check that the inputs are being operated when a vehicle crosses the
demand loops.
If any demand dependant stages have phases that are not receiving
demands, check appropriate input. See section 10.3.13.
(b) Check group times. If any seem excessive or are different from the
works specification, check in controller visit log book to see if timing
(d) Is the hurry calls prevent timer running, thus preventing the hurry call?
If the input is operating correctly, check the status of the hurry call, use a
handset and the command `SHC' for the appropriate hurry call, i.e. 0 or 1.
Below are the possible status displays and their meaning.
0 = Either input not going active or if input is going active, then hurry must
be prevented by hurry call prevent timer.
3 = Timing hurry call delay period
1 = Requesting hurry call stage but not yet in hurry call stage.
(Note: If hurry call status remains = 1 for a long time, the controller may be
in a higher priority mode which the hurry call mode cannot override.
Alternatively, a higher priority Hurry Call (Hurry Call 0) may be operational
if Hurry Call status being viewed is for Hurry call 1 as Hurry Call 1 cannot
override Hurry Call 0).
2 = Timing hurry call hold period
Therefore, if input operates correctly but hurry call status remains at 0 then
hurry call prevent timer active.
(e) Check hurry call delay timers. If either delay times seem excessive or
are different from the works specification, check in controller `visit log
book' to see if timing has been changed by an engineer and/or check
with customer that timing is as required.
10.3.11.7 General Reasons for Slow Signal Changing:
(a) Check minimum green times and inter-green times. If any seen
excessive or are different from the works specification, check in
controller visit log book to see if timing has changed and/or confirm
with customer that timing is as required.
(b) Extend all red: Check as to whether or not an extend all red facility is
provided on the controller. If it is then check to see if controller is
always running to maximum all red and/or receiving permanent
extensions which make it run to its maximum.
To check to see if there is a permanent hold inter-green request, use a
handset and the engineering code for the mnemonic `HLDREQ'. This
displays 255 or FF if a hold inter-green request is present.
Refer to the ST900 Family Controller Handset Handbook for more details.
Similar to above, the engineering code for the mnemonic `HLDON' can be
used to determine if there are any hold inter-greens currently being
applied.
(c) Phase delays: Check to see if there are any phase delays during the
stage to stage move(s) which may explain delay in changing. Check
timings for delays.
A check to see if there are phase delays occurring can be performed using
a handset and the `SPH' command.
(c) SDE/SA facility: Check as to whether or not an SDE or SA facility is
provided on the controller. If it is, check to see if extra clearance period
is always being inserted.
To check to see if an extra clearance period is being inserted, use a
handset and the command `SCI'.
There is also an `SCR' command that indicates if requests are present for
the extra clearance period, and provides as display as above.
(d) If possible try and determine what mode the controller was expected to
be in when fault was reported. It is possible that the slow response may
be due to the controller being in a higher mode than that expected, e.g.
if UTC was higher than VA a motorist may be reporting a slow response
to their approaching the signals due to UTC sequence.
It is also possible that the reason for introducing the mode is not occurring,
i.e. it is not reaching the expected mode because:
UTC bits are not being actioned
Hurry Calls are not being actioned
Emergency vehicle demands are not being actioned
Real Time Clock is not introducing CLF
etc.
If the intended mode is known, any reasons for not attaining the mode
should be investigated.
10.3.12
continue at 10.3.12.3
CLF
FT
Priority/Hurry Call
continue at 10.3.12.4
continue at 10.3.12.5
continue at 10.3.12.6
If after having completed checks for the mode of operation no fault can be
found, check through the general reason for quick signal changing
continue at 10.3.12.7.
10.3.12.3 VA Mode:
The controller is operating in the VA mode and cycling too quickly.
Do the following:
(a) Check to see if any phases are not receiving extensions when their
associated extension loops are occupied.
To check to see if any phases have extensions use the handset and the
`SPH' command.
Note `SPH' only shows the extension timing whilst the phase is at green. If
this is insufficient, then determine from the works specification which
signals provide extensions (e.g. AXYZ extends phase A) and to what input
port and bit the signals have been allocated. The `IOP' command can then
be used to view the status of the input ports to see if any of the inputs are
not responding to vehicles crossing the loops. Continue at section 10.3.13
to fault-find an input.
If any are not receiving extensions, check appropriate input. See
section 10.3.13.
(b) Check extension times. If any times seem too short or are different
from works specification, check in controller `visit log book' to see if
timing has been changed and/or check with customer to see if timing is
as required.
10.3.12.4 CLF Mode:
The controller is operating in the CLF mode and cycling too quickly. Do the
following:
(a) Check Group times. If any seem too short or are different from the
works specification, check in the controller `visit log book' to see if
timing has been changed and/or check with customer to see if timing is
as required.
10.3.12.5 FT Mode:
The controller is operating in the FT mode and cycling too quickly.
(a) Check fixed times. If any seem too short or are different from the works
specification, check in the controller `visit log book' to see if timing has
been changed and/or check with customer to see if timing is as
required.
10.3.12.6 Priority/Hurry Call mode:
The controller is in Priority or Hurry Call mode and cycling too quickly.
(a) Are priority extensions being received? If not check appropriate input,
see section 10.3.13.
To check to see if priority extensions are being received is a difficult
task as generally a special unit is required to insert priority demands or
extensions. If one such unit (usually attached to the underside of a
vehicle) is available insertion of extensions can be checked, by
passing the unit over the loop of a priority detector unit and checking
with the handset and command `PDS' that the demand/extension is
being entered.
(Note: The commands `PVU & PVP' may also be used, but these only
give the status information for a single priority input/phase respectively
and, therefore, the operation of all priority units cannot be seen all at
once).
(b) Check priority extension times. If any seem too short or are different
from the works specification, check in the controller `visit log book' to
see if timing has been changed and/or check with customer too if
timing is as required.
(c) Check Hurry Call hold time, to ensure that it is running and is of
correct duration. If either hurry call hold period seems too short or is
different from the works specification, check in the controller `visit log
book' to see if timing has been changed and/or check with customer to
see if timing is as required.
10.3.12.7 General reasons as to why signals might change too quickly:
(a) Check minimum green times and inter-green times. If any seem too
short or are different from the works specification, check in the
controller `visit log book' to see if timing has been changed and/or
check with customer that timing is as required.
(b) Extend all red: Check as to whether or not an extend all red facility is
provided on the controller. If it is, check to see if extension requests
are being received (e.g. when extension loops are occupied). If not
check all red extension time and maximum time, also check
appropriate input. See section 10.3.13.
Faulty Input
10.3.13.1 Check input using handset and `DET' command for appropriate
input, if set to `1' or `0' then permanently activated or disabled, if set
to `2' then normal operation.
Is input permanently activated or disabled?
YES - Continue at 10.3.13.11.
NO - Proceed to the next point.
10.3.13.2 Is the input permanently active?
YES - Continue at 10.3.13.9.
NO - Proceed to the next point.
10.3.13.3 Is the input permanently inactive?
YES - Continue at 10.3.13.6.
NO - Proceed to the next point.
(e) If input is standard I/O then replace appropriate PSU / I/O card or I/O
card and re-check to see if input(s) now operating correctly.
10.3.13.11 Input is either permanently disabled or enabled.
Check to see if there is a reason for input to be permanently enabled or
disabled. Check in controller visit log book.
(NB: If input is a detector input and input is set = `1' then there may be a
loop fault as this is a method of getting the controller to function normally if
a detector is inoperative).
If reasons for input being permanently disabled or enabled is no longer
valid, e.g. loop has been repaired, then set input to `Normal' operation and
re-check to see if input is now operating correctly.
10.3.14
Faulty Output
(d) Check for intermittent connections all associated cables and their
attendant joints by gently flexing cables and connectors..
10.3.14.9 All outputs on controller faulty or all on one I/O card faulty.
Do the following:
(a) Replace the PSU / I/O card or I/O card and re-check to see if the
output is now in forced state.
(b) Check for intermittent connections all associated cables and their
attendant joints by gently flexing cables and connectors..
10.3.14.10 Output can be forced to operate correctly so fault must be in
function driving it.
Do the following:
(a) If output is driven from special conditioning, check conditioning to see
if conditions are met. If conditions are not true, try to make the
conditions true and check that output operates as required.
(b) If output is driven by a controller function, e.g. UTC green confirm
reply bits check controller functions which operates the output.
10.3.14.11 Outputs have been set either permanently short circuit or open
circuit using handset command `DET'.
This is unusual and it should be checked that there is no valid reason for
this situation. If no valid reason can be found set output to `Normal'
operation (appropriate `DET' command = 2) and check that output
performs as required.
10.3.14.12 Fault is between controller output terminal and receiving unit.
Check cabling between controller and receiving unit for short circuits and
intermittent connections.
10.3.15
Reasons for being in a particular mode are given in 10.3.16.3 (i.e. reasons
for overriding another mode).
Reasons for not being in a mode are given in 10.3.16.4.
10.3.16.3 (a) If the controller is in the VA mode check mode indicated on
Manual Panel.
(b) If the controller is in the FT mode check mode indicated on Manual
Panel.
(c) If the controller is in CLF mode, check time of day, i.e. real time clock.
If incorrect reset the real time clock.
(d) If the controller is in UTC mode, check for force bits present. Check
inputs (see 10.3.13).
(NB Force bits may be applied from special conditioning. Therefore,
checks conditioning if no force bits are being applied from OTU etc).
(e) If the controller is in priority mode, check for priority demands present.
Check inputs (see 10.3.13).
(NB Priority demands may be applied from special conditioning.
Therefore, checks conditioning if no priority demands are being
applied from external source).
(f) If the controller is in Emergency Vehicle mode, check for emergency
vehicle demands present. Check inputs (see 10.3.13).
(NB Emergency vehicle demands may be applied from special
conditioning. Therefore, checks conditioning if no priority demands are
being applied from external source).
(g) If the controller is in hurry call mode, check for hurry call request
present. Check inputs (see 10.3.13).
(NB Hurry call requests may be applied from special conditioning.
Therefore check conditioning if no hurry call requests are being
applied from external source).
(h) If the controller is in the Part time mode, check real time clock. If it is
incorrect reset the real time clock. If part time is controlled by special
conditioning (e.g. flow and queue detectors) check condition required
to switch to part time (Signals OFF).
10.3.16.4 (a) If the controller is not in the VA mode then:
Check the operation of the mode select buttons if using them.
Check to see if VA is being overridden, i.e. that current mode of
operation has a higher priority than VA.
check to see if any Hurry call requests are present, i.e. check inputs
10.3.13.
check to see if Hurry call mode is being overridden, i.e. that current
mode of operation has a higher priority than Hurry call mode.
check to see if either Hurry call prevent timers are running.
(h) If the controller is not in part time mode then:
check real time clock. If it is incorrect reset the real time clock.
If part time is controlled by special conditioning (e.g. flow and queue
detectors) then:
check that conditions required to switch to part time are present, if they
are not, take any necessary corrective actions.
10.3.17
If a site has an intermittent fault or a fault which keeps repeating then first the
appropriate procedure for the fault should be followed as most paths have more
than one suggested area to check for the fault.
If the fault is still intermittent, do the following:
(a) Gently - try and move/flex each card whilst in situ to check for any
intermittent connections.
If any intermittent connections are found, replace appropriate card.
(b) Gently move cables and wiring looms to check for any intermittent
connections.
(c) Switch controller off and withdraw all cards. Check security of any ICs
mounted in sockets; namely firmware PROM and configuration PROM
on the Main Processor card.
Re-fit cards and re-check operation of controller.
10.3.18
10.3.18.1 If the handset does not operate correctly when plugged into the
handset port on Main Processor card, do the following:
(a) Check that there is a +5V supply on pins 9 and 10 of the handset
socket (0V is on pins 1, 7, 18 and 19). With the handset plugged in
check the ripple voltage on 5V supply.
(This supply powers those handsets that do not have their own
supplies.)
To fully investigate may require the use of an oscilloscope.
(b) Switch off controller and withdraw Main Processor card. Check
security of ICs mounted in sockets of the above card. If no loose ICs
are found, replace Main Processor card.
(b) Replace Main Processor card and re-check to see if handset now
operates correctly.
10.4
Replacement of Cards
This section covers removal and fitting of cards in the ST750 ELV cabinet. Also
described are procedures to ensure that the card functions correctly when fitted
(e.g. PROM fitting).
10.4.1
WARNING
Safety Requirements
Before replacing any fuses, cards etc., IT IS ESSENTIAL THAT THE
POWER TO THE CONTROLLER IS ISOLATED. See the Safety Warning
on page 2 for details.
Failure to isolate the supply before changing parts may result in damage to
the Controller.
10.4.2
General Requirements
When replacing cards, the original card should be inspected and the following
points checked:
(a) Check the connectors on the card. Are any pins bent, broken or damaged in any
way? If there are, make a note of the card and pin number in the Controller Visit
Logbook as the backplane may have been damaged.
(b) Check any ICs that are mounted in sockets and ensure they are the correct ones
for the position and are securely fitted. Refer to the works specification for the
correct version and type of firmware and configuration PROM. Refer to Figure 7
for the PROM location.
A problem with a loose fitting IC or use of an incorrect one can usually be
rectified easily without having to fit a replacement card.
(c) Do not forget to record the replacement in the Controller Visit Logbook.
(d) Complete a fault label and return the faulty card for repair.
10.4.3
The cards in the right hand half of the Rack assembly have all their connections
made on rear mounted PCB connectors which mate with similar connectors on the
Termination Backplane. The cards are retained in position by a card retaining strip
on the top edge. Loosen the screw on this strip and move sideways to enable the
cards to be removed / re-fitted. After re-fitting cards ensure that the card retaining
strip is set to retain the cards and the retaining screw tightened.
The cards in the left hand half of the Rack Assembly have connectors at their rear
(bottom) edge linked to various parts of the system and most need disconnecting
here as well as the front of the card. If a Gemini is fitted in the cabinet, more room to
access the connections on the bottom of the cards may be gained by swinging the
Gemini swing frame out.
Exercise care when withdrawing cards so as not to damage either the boards or any
cables attached as they are removed.
WARNING
10.4.4
In case of failure, the entire unit, consisting of the main Processor AND PHS cards,
should be replaced.
The controller should be powered down before disconnecting any RJ45 connector.
Disconnect any cables connected to the top and bottom edges of the card, taking
care to note their positions for correct re-connection to the replacement card.
Disconnect the serial (RJ45) cables from SK10 and Sk11 on the Termination
Backplane leaving the cables attached to the PHS on the Main Processor card.
Gently lift the card upwards to remove from the Rack Assembly.
If a third serial (RJ45) cable is connected to the PHS (TO EXTRA i/o CARD OR
Intelligent Detector Backplane card (s)), this can be disconnected from the PHS as
the card is lifted up to remove it, without the need to untie the serial cable from any
strain relief points within the cabinet.
The type and position of the configuration PROM and the software identification
number printed on the PROM label should be checked. Refer to the Works Order
Specification for details.
When fitting replacement card remember to connect serial (RJ45) cable to the PHS
as the card is lowered into place (if disconnected as described above)
Be careful to connect the serial (RJ45) cables to the correct sockets on the
Termination Backplane:
PHS PL1 (LSLS) to SK10
PHS PL2 (IO) or PL4 (IO) to SK11
10.4.5
Pull the LSLS card from the Rack Assembly using the handle on the top edge.
Replace with the new LSLS card by reversing the above procedure.
10.4.6
Pull the PSU / I/O card from the Rack Assembly using the handle on the top edge.
Replace with the new PSU / I/O card by reversing the above procedure.
10.4.7
The controller should be powered down before disconnecting any RJ45 connector.
I/O card, if fitted, is situated on the rear panel of the controller cabinet. Disconnect
the cables which are held in place with two screws each, then the serial cables and
the six mounting screws. Remove the card and replace with the new one. Reverse
the procedure to connect the new card.
10.4.8
The controller should be powered down before disconnecting any RJ45 connector.
The Detector Backplane card(s) is/are situated on the small swing frame on lower
left hand side of cabinet or in 11 or 19 racks, depending on the build of the
controller .
Generally speaking, only the Intelligent Detector Backplane card will need replacing,
although the replacement kit includes the passive Detector Backplane. They are
supplied together to protect delicate components and connections.
Remove the three nuts holding the card in place and pull away from the passive
backplane. Replace with the new card and tighten the nuts.
Reassemble and return the kit including the defective card to Siemens Poole.
10.4.9
First unplug the cable connecting the panel to the Main Processor card (Rear
connector).
The panel is retained by a number of screws to the main cabinet assembly.
(Mounting methods may vary in different cabinets).
After removal of these screws the panel may remain stuck in place by the gasket.
Ease the panel away from the housing, gradually working from one corner taking
care not to scratch or otherwise damage it.
The replacement panel should be mounted with a new gasket to prevent water
ingress. After fitting, reconnect the cable to the Main Processor card.
Note that when fitted in the factory the ribbon cable to the Manual Panel may be
fitted behind the Termination Backplane. This is unlikely to be possible when fitting
a replacement so a suitable route for the ribbon cable, along either the top or bottom
edges of the Rack Assembly should be chosen. Ensure that the ribbon cable is
securely fixed and not left unsupported.
10.4.10
Removal of these cards may be done individually after disconnection of the rear
expansion bus ribbon cable from the Processor Card and the Berg input/output
connectors.
10.4.11
When replacing any components (including cards) only approved spares may be
used. Use of any other components may invalidate the Type Approval of the
equipment. See APPENDIX A for details of approved spares.
10.5
Every controller should have a Controller Visit Log Book. It should be a small book,
usually stored in the document pocket inside the controller door. On every visit the
visiting Engineer should write down in the log book the date, his/her name, reason
for visit and actions taken. For example, the reasons for the visit may be a fault
report, routine inspection, fitting of new equipment, adjustment of timings, etc. The
actions taken may be card or unit replaced, timing adjusted, new equipment fitted,
etc. This information is essential for the next Engineer who may visit the site so that
he/she can see what has happened previously and helps to reduce duplication of
effort.
The requirement to fill in the visit log book also applies to Local Authority Staff. The
maintenance organisation cannot be held responsible for any problems arising from
neglect of this responsibility.
11.
11.1
Introduction
The Self-Test facility can be used to check the hardware fitted to the controller, even
without a configuration loaded. It has been designed for use in production and on
the street by installation / maintenance engineers.
Self-Test is initiated by holding down the level 3 access button while switching the
controllers power on. The button must be released once the green heartbeat LED
starts to flash.
The green heartbeat LED continues to flash during the Self-Test unless a fault is
detected, when the red system error LED illuminates.
A 20 character by 4 line handset connected displays information about the checks it
is performing, such as the firmware issue and the lamp supply voltage, both dim and
bright, and details any faults found.
Self-Test performs the checks detailed on the following pages and reports the error
messages shown if faults have been detected.
While the Self-Test is running, the Manual Panel can be checked. Pressing each
button on the panel should illuminate the associated LED. To distinguish this from
normal operation, the LED flashes at a fast rate while the button is pressed. Note
that the Lamp Test button flashes all the LEDs on the Manual Panel.
To test the signals ON/off switch and the cabinet alarm LED, switching the switch to
the signals ON position flashes the cabinet alarm LED. Switching it to the off
position extinguishes the cabinet alarm indicator. The Signals On/Off Switch does
not affect the Self-Test in any other way.
11.2
The following shows typical information output by Self Test during Part One, and
summarises the tests it performs:
Controller SelfTest
===================
Q: Pause Display
After 4 Lines? [YN]
PIC:PB801 ISS 7
PLD:000 LMU
RAM Size.....512KB
CPU Speed....16MHz
PHS CPU......Found
PHS:32931 ISS 3
LSLS Cards...----1
One 16-Output LSLS
VLS 1:32941 ISS 5
VLS 2:VLS 3:VLS 4:VLS 5:VLS 6:P/Bus CPU....Found
SIC:PB815 ISS 4
ZXO From.....PHS
Mains Freq...50.0Hz
PHS Init.....Passed
L/Supply Off=0V
V/Mons Off...Passed
All Cards Working?
On power-up, the Self-Test facility checks the integrity of the Main
Processor Card:
RAM FAULT
DPR RAM FAULT
PRG PROM FAULT
XTL FAULT
DPR R/W FAULT
All the above faults point to problems internally on the Main Processor card.
Checks communications with the Phase Bus Processor:
PHS CPU......
If the Processor on the PHS daughter card cannot be detected, the Self-Test waits
indefinitely at this point with the red system error LED illuminated. Check that the
PHS Card is fitted correctly.
11.3
WARNING
The following shows a typical information output by Self Test during Part Two, and
summarises the tests it performs:
All Cards Working?
**** IMPORTANT ****
All LED Signals to
be covered before
continuing...
Starting Pass 0001
V/Mons Off...Passed
Lamp Supply..48V
M/V Test.....Passed
Dim L/Supply=27V
LSLS Outputs:1-10
Relay A Test=Ok
LSLS Outputs:11-20
Relay B Test=Ok
LSLS Outputs:21-32
LSLS Outputs:Passed
Checking Lamp
Supply Arrangement:
RelayB:All Sigs Off
RelayA:All Sigs Off
Controller Set-Up:
'Fail To Black-Out'
Exp'n Cards..Found
IOx1
===================
Pass 0001 Complete.
===================
Run Time = 00:00:30
Self-Test switches ON the lamp supply and then checks that the voltage
monitors still indicate that the signals are switched off:
V/Mons Off...Failed
32:1000000000000000
16:0000000000010000
........87654321
If any of the voltage monitors appear to be detecting voltages, it would imply that
those LSLS Outputs are stuck ON (short circuit) and thus that LSLS card should be
replaced. See section 11.4 for details of this format of error message.
L/Supply Failure
LSLS not on..-----1
No lamp supply has been detected on the LSLS Cards identified. Check the lamp
supply circuits relays, fuses, etc.,.
Checks that each lamp supply relay can switch off the lamp supply
independently:
Relay A Fault
Relay B Fault
Failure of any of these tests implies that the relay is not switching off, i.e. that it is
either stuck closed or the control signals from the Main Processor card are stuck
active.
Checks that the dimming relay is functioning:
Dimming Fault
A fault is only detected with the dimming relay if the dim lamp supply is more than
75% of the normal lamp supply, i.e. that the dimming relay seems to have no effect
on the lamp supply. If dimming is not required, then the dim and bright lamp supplies
must not be connected together. If dimming is configured as not present, i.e. KDP is
set to zero, then the controller simply never attempts to switch to dim.
Note that this test does not fail if there is no dim lamp supply. Therefore, the dim
voltage should be checked manually, e.g.
Dim L/Supply=28V
No Voltages On
32:1000000000000000
16:0000000000010000
........87654321
A fault is also logged if no voltages were detected, e.g. when the output switch on
the LSLS Card will not switch ON.
Checks the Lamp Supply arrangement:
The Self-Test checks the lamp supply arrangement of the controller after checking
each lamp supply relay and each output and monitor circuit.
With Relay B switched OFF but with Relay A switched ON, it pulses a selection of
outputs to check that the lamp supply to all of the cards has been removed:
Checking Lamp
Supply Arrangement:
RelayB:All Sigs Off
If any voltage monitors detect lamp supply during this test then the Self-Test shuts
down and displays the fault on the handset since this relay should remove the lamp
supply from the LSLS Card, e.g. if LSLS#1 still appears to be powered:
Relay B Off But . .
32:1000000000000000
16:0000000000010000
........87654321
With Relay B switched ON and Relay A switched OFF, it again pulses a selection of
outputs and checks which cards, if any, still have lamp supply present.
From this, the controller can determine whether the link on the controller is set-up
for fail to black-out or for fail to flashing. Note that fail to flashing is not
supported by the ST750ELV controller.
If the Controller is set-up for fail to black-out then Relay A also switches off the
lamp supply to all the LSLS Cards, If this is the case, then this result is displayed on
the handset and the Self-Test continues:
Checking Lamp
Supply Arrangement:
RelayB:All Sigs Off
RelayA:All Sigs Off
Controller Set-Up:
'Fail To Black-Out'
If the link on the CPU Card is set to Fail to Flashing, then Self-Test aborts and
displays the following error message since tthis feature is not available on the
ST750ELV controller
Fail to Flashing
Not yet available
On ST750ELV; check
Link on CPU card.
At the end of the test, the Self-Test switches OFF the lamp supply and displays a
scrolling pattern on the LSLS card LEDs to show that all the tests have passed
successfully.
It also illuminates a number of amber LEDs on the first lamp switch card to show
some of the expansion cards detected by the Self-Test. See the following picture.
1
2
CPU Card
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
23
24
25
26
27
28
If I/O cards (Serial I/O Cards or Detector Backplanes) with addresses higher than 3
are fitted, use the handset to confirm how many I/O cards have been detected, e.g:
Exp'n Cards..Found
IOx5, OTU
It is also clear on the I/O cards themselves whether or not they have been
recognised by the Controller because their status LEDs will indicate that they have
been configured.
After a few seconds, Self-Test repeats Part Two, allowing the controller to be soaktested.
If one or more expansion cards detected during Pass 1 are not detected on a
subsequent pass, the self-test aborts and displays the following error message:
Exp'n Cards Failed!
Found this time:
IOx4, OTU
11.4
11.5
The following error messages can be displayed at any time during the Self Test.
Other error messages not shown here may be displayed shortly after power-up and
before Self-Test begins if there is a fundamental problem with the Main Processor
Card. See the details of the start-up sequence in the Handset Handbook for details.
ZXO Synchronisation
If the Controller loses synchronisation with the zero-crossing points of the mains
supply, the following error message will be displayed and Self-Test will abort.
ZXO Sync Lost
This fault is displayed when the mains power to the controller is switched OFF or
there has been a short interruption to the mains supply. If the problem persists and
the mains supply is thought to be good, check the connections between LSLS#1 and
the PHS. Then try replacing LSLS#1, the PHS and the Main Processor Card.
PHS Faults
If communications between the Main Processor and the PHS fail, the following error
messages can be displayed:
PHS Msg Timeout
PHS Stopped!
Replace the Main Processor Card if the problem persists.
PHS Fault Code N
The PHS has confirmed a serious fault and shutdown the controller. The code
number N displayed is the same as that shown in the FLF 2 fault flag; see the
ST900 Handset Handbook for details.
Unexpected Correspondence Faults
If the LSLS Cards indicate that signals appear ON at times when the Self-Test is not
expecting any signals to be illuminated, then either of the following error messages
will be displayed:
Unexp Corr Fault
Unexp PHS Corr Flt
If the fault occurs within a few seconds of the PHS Init step in part one of the
Self-Test (see section 11.2), then it implies that outputs appear to be ON even
though the lamp supply is still OFF.
This can be caused by faulty voltage monitors on the LSLS Cards. Try removing all
but LSLS#1 and repeating the Self-Test. If it still fails, then replace LSLS#1. If it
passes, remove LSLS#1 and replace it with just one of the other LSLS Cards and
repeat the test. Repeat this to test each LSLS Card in turn.
It can also be caused by stray voltages on the street cables. Carefully check all the
street cables to ensure that no voltages are present from external sources.
Configuration Download Sequence
If the configuration download sequence to the PHS, or an LSLS or Serial I/O Card
fails, then one of the following error messages is displayed. The * will be replaced
by the card address.
PHS DOWNLOAD FAIL
LS* DOWNLOAD FAIL
SIO* DOWNLOAD FAIL
Check the connections to the card and if the fault persists, replace the card.
LSLS Card Failures
If low power is confirmed by one or more LSLS Cards, then the following error
message is displayed. The * will be replaced by the address of the first card to
report it.
LSLS* POWER LOW
Carefully check the mains supply voltage to the Controller and the taps on the lamp
supply transformer (which also provides the logic power to the LSLS Cards). If the
fault persists, change the LSLS Card. Also see the description of FLF 9:255 LSPF
in the handset handbook.
If communication to one or more LSLS cards has been lost, then the following error
message is displayed. The * will be replaced by the address of the first card that
disappears.
LSLS* COMMS FAIL
Check the cable connections between the PHS and that LSLS Card. Also see the
description of FLF 43:255 LSLS in the handset handbook.
If a Major Fault is reported by an LSLS Cards, then the following error message is
displayed. The * will be replaced by the address of the LSLS Card.
LSLS* MAJOR FAULT
The LSLS Card will probably need to be replaced. For more information, see the
description of FLF 42:255 LSMF in the handset handbook.
WARNING
A.1.1 UK Only
ST750ELV UK SINGLE PED IN 400S CAB-GREY
ST750ELV UK SINGLE PED IN 400S CAB-BLK
667/1/32750/010
667/1/32750/011
667/1/32750/020
667/1/32750/021
667/1/32750/014
667/1/32750/015
667/1/32750/024
667/1/32750/025
667/1/32750/513
667/1/32750/523
667/1/33710/001
667/1/33710/002
667/1/33710/005
667/1/33770/000
667/1/33775/000
667/1/32750/150
667/1/32750/154
667/1/32750/653
667/1/33710/005
667/1/33770/000
667/1/33775/000
667/1/27118/000
667/1/26271/000
667/1/27056/301
667/1/27004/000
667/1/32600/000
667/1/15990/003
667/1/15854/000
667/1/27007/000
667/1/33780/000
667/1/21384/000
667/1/21498/000
667/1/21923/001
667/7/27129/000
667/4/04026/023
992/4/00216/000
667/1/32918/000
667/1/32915/000
667/1/32917/000
998/4/88351/002
998/4/88351/005
998/4/88351/010
998/4/88351/020
998/4/88351/030
667/1/20296/002
667/1/33047/000
667/1/27056/010
667/1/12800/000
667/1/12815/000
667/4/04785/000