smartlink general handbook

Transcription

SmartLink General Handbook
Siemens Traffic Controls
Sopers Lane, Poole, Dorset, BH17 7ER
United Kingdom
+44 (0) 1202 782000
http://www.siemenstraffic.com/
SmartLink
General Handbook
PREPARED:
Dave Martin/Ruth Davis
FUNCTION:
Product Engineering Manager/Technical Author
Part Number
Issue
Change Ref
Date
667/HB/30400/000
6
N/A
April 2007
THIS DOCUMENT IS ELECTRONICALLY HELD AND APPROVED
© Siemens plc. 2007 All rights reserved.
The information contained herein is the property of Siemens plc and is supplied without
liability for errors or omissions. No part may be reproduced or used except as authorised by
contract or other written permission. The copyright and the foregoing restriction on
reproduction and use extend to all media in which the information may be embodied.
667/HB/30400/000
Issue 6
Page 1
SAFETY WARNING
HEALTH AND SAFETY AT WORK
Safety of Installation Personnel
In the interests of health and safety, when installing, using or servicing this
equipment the following instructions must be noted and adhered to:
(I)
Only skilled or instructed personnel with relevant technical knowledge and
experience, who are also familiar with the safety procedures required when
dealing with modern electrical/electronic equipment are to be allowed to use
and/or work on the equipment. All work shall be performed in accordance with
the Electricity at Work Regulations 1989.
(ii)
Such personnel must take heed of all relevant notes, cautions and warnings in
this Handbook 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.
(c) Before any installation work is carried out, the mains supply to the Pole or
Controller must be isolated/switched off.
(d) All equipment of conductive material installed in these Controllers or Poles
must be bonded to earth e.g. transformers, unless double insulated or
access to it is restricted to use of a tool.
(e) Only trained/competent persons should work on this equipment. All wiring
has basic insulation and should be regarded as hazardous, i.e. hazardous
voltages are accessible if the insulation is damaged.
(f) Any power tools must be regularly inspected and tested.
(g) Any ladders used must be inspected before use to ensure they are sound
and not damaged.
(h) When using a ladder, before climbing it, ensure that it is erected properly
and is not liable to collapse or move. When using a ladder near a
carriageway ensure that the area is properly coned and signed. Personnel
must adhere to the current Method Statement that details procedures
when using a ladder.
(i) Any personnel working on site must wear the appropriate protective
clothing, e.g. reflective vests, etc.
Safety of Road Users
It is important that all personnel are aware of the dangers to road users that could
arise during installation, repair and maintenance of traffic control equipment. Ensure
that the junction area is coned and signed as necessary to warn motorists and
pedestrians of any dangers and to help protect the personnel working on the site.
667/HB/30400/000
Issue 6
Page 2
MAINTENANCE PROVISION (MP)
1.
Product Reference
SmartLink
2.
Specifications
The SmartLink system has been EMC tested to EN50293.
The short-range wireless radio links are designed to meet the following
specifications:
Standards:
EN 300 175 (DECT Common Interface)
ETS 300 651 (Data Services DSP C.2)
Certification: EN 301 406 (TBR6 2nd edition)
EN 60 950/2000 (safety)
ETS 301 489-6 (EMC)
Approval:
ETSI (EU)
3.
Installation and Commissioning
Methods of Installation and Commissioning are detailed in the Siemens Traffic
Controls document:
667/HB/30400/000 SmartLink General Handbook
4.
Spares and Maintenance
All maintenance and repairs should be carried out in accordance with the
Siemens Traffic Controls documents:
5.
Modifications
There are no approved modifications, with the exception of those listed in the
following Siemens Traffic Controls Document:
6.
Warning
Use of components other than those permitted above, or modifications or
enhancements that have not been authorised by Siemens Traffic Controls will
invalidate Type Approval of this product.
667/HB/30400/000
Issue 6
Page 3
TABLE OF CONTENTS
Section 1 – Introduction..............................................................................................7
1.1 Purpose ........................................................................................................7
1.2 Scope............................................................................................................7
1.3 Related Documents ......................................................................................7
1.4 Definitions .....................................................................................................8
1.5 Issue State....................................................................................................8
Section 2 – Overview .................................................................................................9
2.1 General .........................................................................................................9
2.2 User Scenarios ...........................................................................................11
2.3 Security.......................................................................................................19
Section 3 – The Equipment ......................................................................................20
3.1 Local Unit Controller (LUC) – All Scenarios ................................................ 22
3.2 Line Interface Unit (LIU) – Scenario 2 (TC12)............................................. 30
3.3 Radio Head – All Scenarios ........................................................................33
3.4 Remote Unit (RU) – Scenarios 1 & 3 (Remote Detectors/Serial) ................ 35
3.5 Antenna – All Scenarios..............................................................................38
3.6 Repeater Station – Option for all Scenarios................................................ 38
3.7 Technical Specification ...............................................................................39
Section 4 – Site Surveys ..........................................................................................41
4.1 General .......................................................................................................41
4.2 Survey Equipment.......................................................................................42
4.3 Sight Lines ..................................................................................................42
4.4 Mounting poles for Base and Network Radio Heads .................................. 45
4.5 Mounting Poles for Remote Units & Repeaters .......................................... 46
4.6 Space within the Controller ......................................................................... 46
4.7 Co-Located Systems...................................................................................47
4.8 Repeater Node ...........................................................................................48
4.9 UTC Telephone Lines / Gateway LUCs ...................................................... 48
4.10 Equipment List ............................................................................................49
Section 5 – Installation .............................................................................................50
5.1 General .......................................................................................................50
5.2 Order of Installation.....................................................................................53
5.3 Belled Pole – Option for All Scenarios ........................................................ 55
5.4 Local Unit Controller – All Scenarios........................................................... 58
5.5 Line Interface Unit (LIU) – Scenario 2 (TC12)............................................. 59
5.6 Radio Head - All Scenarios.........................................................................62
5.7 Remote Unit – Scenarios 1 & 3 (Remote Detectors/Serial) ........................ 63
5.8 Pole Cap Extension Kit – Option for all Scenarios ...................................... 65
5.9 Mast Fixing – All Scenarios.........................................................................66
5.10 Antennas – All Scenarios............................................................................68
5.11 Attach Unit to the Mast - All Scenarios........................................................ 69
5.12 Raising the Mast – All Scenarios ................................................................ 70
5.13 Repeater Node – Option for all Scenarios .................................................. 73
Section 6 – Commissioning......................................................................................77
6.1 General .......................................................................................................77
6.2 Installation Support Kit ................................................................................78
6.3 Re-Subscription Procedure.........................................................................80
667/HB/30400/000
Issue 6
Page 4
6.4 RU Commissioning – Scenarios 1 & 3 (Remote Detectors/Serial).............. 81
6.5 TC12 Commissioning – Scenario 2 (TC12) ................................................ 84
6.6 Repeater Node ...........................................................................................88
Section 7 – Maintenance..........................................................................................91
7.1 Diagnostic Functions...................................................................................91
7.2 Troubleshooting Guide................................................................................93
7.3 Performance Checking ...............................................................................97
Section 8 – Handset Commands.............................................................................. 98
8.1 General .......................................................................................................98
8.2 Handset Command Responses .................................................................. 98
8.3 Radio Module Error Codes .........................................................................99
8.4 Handset Command List ............................................................................ 100
8.5 GRX Handset Command .......................................................................... 111
8.6 LOG Handset Command .......................................................................... 112
Section 9 – Parts List .............................................................................................115
9.1 Parts List – General .................................................................................. 115
9.2 Parts List – Cables....................................................................................116
9.3 Parts List – Fuses .....................................................................................116
Section 10 – SmartLink Survey Check List ............................................................ 117
Section 11 – SmartLink Survey Equipment Sheet.................................................. 124
Section 12 – SmartLink Configuration Sheet.......................................................... 125
LIST OF FIGURES
Figure 1 – Remote Detector Links............................................................................11
Figure 2 – Controller Linking ....................................................................................12
Figure 3 – TC12 Radio Network...............................................................................13
Figure 4 – TC12 UTC Data Linking ..........................................................................14
Figure 5 – Remote Serial Link.................................................................................. 15
Figure 6 – Integrated Traffic Network .......................................................................18
Figure 7 – SmartLink Connections to a Controller.................................................... 21
Figure 8 – LUC Front Panel and PCB ......................................................................22
Figure 9 – Gateway/Network Configuration.............................................................. 23
Figure 10 – LUC Relays ...........................................................................................26
Figure 11 – LUC OTU Port.......................................................................................27
Figure 12 – LUC OTU Connector to OTU (Cable E) or LIU (Cable H) ..................... 27
Figure 13 – LUC NRH Port Usage ...........................................................................28
Figure 14 – LUC NRH Port Pins............................................................................... 28
Figure 15 – LUC BRH Port Pins............................................................................... 28
Figure 16 – LUC Remote Serial (10W IDC) to 9W D-Type ...................................... 29
Figure 17 – LIU Front Panel and PCB......................................................................30
Figure 18 – Cable E: LUC (OTU) to LIU (RS232) .................................................... 31
Figure 19 – Cable F: LUC (NRH) to LIU (RS485) .................................................... 32
Figure 20 – LIU with Telephone Cable and Cover ................................................... 32
Figure 21 – Radio Head mounted on a Traffic Signal Pole ...................................... 33
Figure 22 – Radio Head Assembly...........................................................................33
Figure 23 – Remote Unit Assembly..........................................................................35
Figure 24 – RU to LUC Detector Mapping................................................................ 36
Figure 25 – Fresnel Zone .........................................................................................44
667/HB/30400/000
Issue 6
Page 5
Figure 26 – Obstacle in Line Of Sight.......................................................................45
Figure 27 – Separation Distance..............................................................................47
Figure 28 – Repeater Configuration .........................................................................48
Figure 29 – BRH and Gateway LUC Wiring Summary ............................................. 51
Figure 30 – Gateway LUC Wiring Summary ............................................................ 51
Figure 31 – NRH and Network LUC Wiring Summary.............................................. 52
Figure 32 – Network LUC Wiring Summary ............................................................. 52
Figure 33 – Belled Pole Assembly – Planted ........................................................... 55
Figure 34 – Mains Unit without Detector (Not Fitted In Pole) ................................... 56
Figure 35 – LUC Backplane Connections ................................................................ 58
Figure 36 – LUC to LIU Cable Connections ............................................................. 59
Figure 37 – Modem Mode Selection Switch – S3..................................................... 60
Figure 38 – Modem Line Level Switch – S1 ............................................................. 60
Figure 39 – Cable G: LIU 24V Power Connections .................................................. 61
Figure 40 – Cables A & C: Radio Head Cables........................................................ 62
Figure 41 – Remote Unit Wiring Summary............................................................... 63
Figure 42 – Remote Unit Wiring Details ................................................................... 64
Figure 43 – Bracket Assembly Kit ............................................................................66
Figure 44 – Bracket Fitting Side View ...................................................................... 66
Figure 45 – Bracket Fitting Either Way Up ............................................................... 67
Figure 46 – Rope .....................................................................................................70
Figure 47 – Mast and Bracket ..................................................................................71
Figure 48 – Cables 1, 2 & 3: Repeater Wiring Summary.......................................... 73
Figure 49 – Repeater Bracket ..................................................................................74
Figure 50 – Repeater Unit (Open) ............................................................................ 75
Figure 51 – Repeater Unit on Mast .......................................................................... 76
Figure 52 – Subscription Cable – LUC to BRH ........................................................78
Figure 53 – Subscription Cable – LUC to NRH (or RU)............................................ 79
Figure 54 – Repeater Arrangement..........................................................................88
Figure 55 – Handset Command Responses ............................................................ 98
Figure 56 – Radio Module Error Codes....................................................................99
Figure 57 – Handset Command List....................................................................... 101
667/HB/30400/000
Issue 6
Page 6
Section 1 – Introduction
1.1
Purpose
The purpose of this handbook is to describe the SmartLink radio network
product.
1.2
Scope
This handbook is written for the SmartLink wireless data link, and is made up
of the sections listed below:
SAFETY WARNING
MAINTENANCE PROVISION (MP)
TABLE OF CONTENTS
LIST OF FIGURES
Section 1 – Introduction
Section 2 – Overview
Section 3 – The Equipment
Section 4 – Site Surveys
Section 5 – Installation
Section 6 – CommissioningError! Bookmark not defined.
Section 7 – Maintenance
Section 8 – Handset Commands
Section 9 – Parts List
Section 10 – SmartLink Survey Check List
Section 11 – SmartLink Survey Equipment Sheet
Section 12 – SmartLink Configuration Sheet
INDEX
1.3
Related Documents
667/SA/28599/001 System Design Specification
667/SU/30400/000 SmartLink Compatibility Document
667/XE/30400/000 SmartLink Configuration Sheet
667/HB/43100/000 TC12 General Handbook
667/HE/43100/000 TC12 Installation, Commissioning and Maintenance
667/HB/30400/000
Issue 6
Page 7
1.4
Definitions
BRH............. Base Radio Head
DECT........... Digital Enhanced Cordless Telecommunications
DFM............. Detector Fault Monitoring
DNR............. DECT serial number
EMC ............ ETSI manufacturer code
FT ................ Fixed Terminal
LIU............... Line Interface Unit
LUC ............. Local Unit Controller
Mast............. For the purposes of this document, the 50mm diameter pole on
top of which the Remote Unit or Radio Head is erected is known
as the ‘mast’ to distinguish it from the traffic signal ‘pole’.
MOVA.......... Microprocessor Optimised Vehicle Actuation
N/C .............. Normally Closed (detector relay contact that ‘opens’ on detect)
N/O .............. Normally Open (detector relay contact that ‘closes’ on detect)
NRH............. Network Radio Head
OTU............. Outstation Transmission Unit
PIN .............. Personal Identity Number
Pole ............. For the purposes of this document, the traffic signal pole or
belled pole on which the bracket that holds the mast is erected
is known as the ‘pole’. See ‘mast’ above.
PT................ Portable Terminal
RF................ Radio Frequency
RH ............... Radio Head
RU ............... Remote Unit
SCOOT........ Split, Cycle, Offset, Optimisation Technique
STC ............. Siemens Traffic Controls
TC12............ Tele-command 12 – STC protocol between UTC Instations and
Outstations
TLC.............. Traffic Light Controller
TR2210........ Specification for Traffic Signal Controllers (Previously TR0141)
UTC ............. Urban Traffic Control
VA................ Vehicle Actuation
VMS............. Variable Message Sign
1.5
Issue State
Pages
Issue
All
6
667/HB/30400/000
Type
Part Number
Meridian 667/HB/30400/000
Issue 6
Page 8
Section 2 – Overview
2.1
General
SmartLink:
¾ Offers revenue and capital cost savings
¾ Eliminates leased lines in many TC12 UTC systems
¾ Replaces expensive cable and ducts in many detector applications
¾ Typical 300m range, extendable using a Repeater configuration
¾ Highly secure communications
¾ Fully compatible with all traffic detection equipment
Siemens’ SmartLink short-range radio system has been developed to save
Local Authorities capital cost on new schemes and deliver major reductions in
communications costs associated with running UTC systems.
Using highly secure DECT technology, SmartLink addresses the
environmental and performance requirements necessary to replace wired
links in traffic control and monitoring applications. From simple linking of
remote detectors to a traffic controller, through to providing a sophisticated
radio network capable of transmitting serial data streams including TC12 UTC
data, SmartLink provides the solution.
Up to now, traffic flow sense equipment has been hard-wired to street-based
traffic light controllers. These were in turn linked to each other and the urban
traffic control centres by standard telephony connections using a low-speed
modem protocol.
SmartLink is the first short-range radio network solution specifically designed
to address UK road traffic issues. Combining multi functionality and high
667/HB/30400/000
Issue 6
Page 9
levels of security, SmartLink delivers cost efficient communications for use in
a wide range of traffic applications.
SmartLink has been developed to deliver capital cost savings on new
installations, whilst achieving major reductions in running costs of established
UTC systems.
SmartLink offers a secure and reliable radio link between remote detectors
and a host Controller or OTU, greatly reducing ducting and street works.
One SmartLink base station is able to support up to four Remote Units that
interface to the detectors. Advanced DECT technology and a sophisticated
transmission algorithm allow many types of detector data to be reliably
transmitted by SmartLink. Applications include VA demands and extensions,
queue loops, MOVA and SCOOT loops. The system is not just limited to the
transmission of detector data. Any digital pulse may be communicated, which
makes SmartLink ideal for linked MOVA applications. However, SmartLink is
able to do much more than just transmit simple digital pulses.
When configured as a radio network, SmartLink is able to manage STC TC12
data. With the ability to network up to seven remote sites, SmartLink offers the
potential to realise an impressive 87% reduction in UTC related
communication charges.
The benefits offered by SmartLink are enhanced by the provision of a serial
data channel offering, for example, short-range communications to signs.
The system consists of four separate units, described in more detail in Section
3:
•
Local Unit Controller (LUC) provides the main processing resources
and resides within the traffic controller
•
TC12 Line Interface Unit (LIU) to connect the LUC to the telephone line
to the TC12 UTC Instation or TC12 OTU.
•
Radio Head (RH) deployed to provide either a Base Radio Head (BRH)
or Network Radio Head (NRH) for the LUC.
•
Remote Unit (RU) used to collect and deliver remote detector and
serial data
667/HB/30400/000
Issue 6
Page 10
2.2
User Scenarios
There are different scenarios for which SmartLink is particularly appropriate,
each discussed separately below.
•
Scenario 1 – Detector wireless linking
•
Scenario 2 – TC12 UTC Data wireless linking
•
Scenario 3 – Other Serial Data over a wireless link
•
Controller linking, using Scenario 1 or 2.
2.2.1 Scenario 1 – Simple Detector Linking
In its simplest form, SmartLink provides a secure and reliable communication
platform for the transmission of remote detector data.
Figure 1 – Remote Detector Links
One SmartLink Local Unit Controller (LUC) is able to provide eight TR2210
compliant detector outputs to the host controller or OTU and support up to
four Remote Units.
The high reliability of the DECT (Digital Enhanced Cordless
Telecommunications) system and advanced transmission algorithms ensure
that typical transmission delays are kept to less than 100ms, at ranges of up
to 300 metres. This allows many types of detector data to be transmitted by
SmartLink. Applications include VA demands and extensions, queue loops,
MOVA loops and SCOOT loops.
667/HB/30400/000
Issue 6
Page 11
The Remote Detector facility is not just limited to the transmission of detector
data.
Any digital pulse can be communicated, which makes SmartLink ideal for
linked MOVA applications where two MOVA sites can be synchronised by the
transmission of a synch pulse from one to the next, without incurring the
expense of ducting cables.
This form of ‘Controller Linking’ is shown below. Other forms of Controller
Linking are discussed in section 2.2.4 on page 18.
N/O
TR2210
DIGITAL
OUTPUT
Base
Radio
Head
(BRH)
Remote
Unit ‘N’
Local Unit
Controller
(LUC)
TR2210
DIGITAL
OUTPUT
TR2210
DIGITAL
INPUT
Traffic
Controller or
MOVA Unit
for example
“N / C”
Traffic
Controller or
MOVA Unit
for example
TR2210
DIGITAL
INPUT
Figure 2 – Controller Linking
Note that the digital output contact labelled Normally Closed (N/C) on the
Local Unit Controller is used, even though digital output used at the original
Traffic Controller (or MOVA Unit, etc.) is a Normally Open (N/O) contact.
This is because the contact labelled “Normally Closed” is actually provided by
the normally open contact on the LUC relay, and for Controller Linking, the
output must show an inactive state (open circuit) should the LUC fail.
The “Normally Closed” contact is labelled such, even though it is provided by
the normally open contact, because the LUC is primarily designed to output
Detector signals and these must show an active state should the LUC fail.
Therefore, although the output is labelled Normally Closed, it is actually
provided by the Normally Open contact of the relay so that it goes active
(open) when the LUC is not powered.
This is subject is also discussed in section 3.1.3 on page 26.
667/HB/30400/000
Issue 6
Page 12
2.2.2 Scenario 2 – TC12 Radio Network
The most significant revenue saving feature offered by SmartLink is its
capability to provide a local, radio-based network for the transmission of
Telecommand 12 (TC12) data for UTC (Urban Traffic Control) applications.
The TC12 UPDL (Upload/Download) protocol is also supported by SmartLink,
although some UPDL modes require an update to the TC12 Instation
Software. Contact Siemens Poole for details.
Existing TC12 UTC systems use ‘multi-drop’ telephone lines between the
TC12 Instation and the TC12 Outstations (OTUs), with several OTUs
effectively connected to each telephone line from the Instation.
SmartLink can provide wireless links to network all the OTUs of a TC12
telephone line from just one OTU still connected to the telephone line (where
the Gateway LUC will be based). This removes the need for the expensive
leased telephone lines to all the OTUs.
Thus, wireless links can fan out from one OTU at one Traffic Light Controller
(TLC) still connected to the TC12 Instation via a telephone line to reach
various other OTUs and TLCs in the local area of the town or city.
The use of DECT enables data to be transmitted around the local network in a
timely way, ensuring there is no appreciable effect on the UTC system as a
whole.
Figure 3 – TC12 Radio Network
667/HB/30400/000
Issue 6
Page 13
In this form, one LUC is designated as the Gateway LUC that interfaces
directly to the central office via a TC12 Line Interface Unit (LIU).
An LIU also allows OTUs at the remote sites to be simply unplugged from
their telephone line connections and plugged into the LUC and the SmartLink
system.
NRH
NRH
Network LUC
Network LUC
OTU
OTU
TLC
TLC
BRH
TELEPHONE LINE
TO TC12 INSTATION
BRH
Gateway LUC
NRH
OTU
TLC
Network LUC
OTU
NRH
BRH
TLC
Network LUC
OTU
TLC
NRH
Network LUC
OTU
TLC
Figure 4 – TC12 UTC Data Linking
Thus, one LUC will connect one TC12 OTU and its TLC to the wireless
network.
The Gateway LUC is connected to the TC12 Instation and broadcasts UTC
data to the Network LUCs through its Base Radio Head (BRH) and their
Network Radio Heads (NRHs).
A Network LUC may also be fitted with a BRH through which it can broadcast
the UTC data on to other Network LUCs.
With a BRH on a Gateway or Network LUC capable of linking to four other
Network LUCs, and with a depth of at least three Network LUCs possible,
many OTUs and their controllers can be linked.
However, since all UTC data must go back to the TC12 Instation on the one
telephone line connected to the Gateway LUC, it is this that limits the number
of OTUs that can be radio linked, not SmartLink.
667/HB/30400/000
Issue 6
Page 14
2.2.3 Scenario 3 – Remote Serial
SmartLink also offers a general usage wireless serial data channel that can
be used, for example, for short-range communications to signs or other similar
equipment.
The remote serial link provides a transparent serial link between the LUC and
one of its Remote Units. Serial data entering the link at one end appears
unmolested at the other, except for inevitable transmission delays, which
should be minimal.
Misc.
Traffic
Equipment
RS232
Local Unit
Controller
(LUC) and
Base Radio
Head (BRH)
RS232
Remote
Unit ‘N’
Misc.
Traffic
Equipment
Figure 5 – Remote Serial Link
SmartLink Remote Serial Link
The SmartLink Remote Serial link facility utilises the DECT radio system to
provide a near-transparent serial link between the Remote Data serial port
connections on an LU and an RU.
Baud Rates and Throughput
The baud rates at either end of a Remote Serial link (LUC or RU) can be
independently configured to any of the following baud rates using the SLB
handset command: 1200, 2400, 4800, 9600, 19200, 38400bps.
The Remote Serial Link supports serial data of the format listed below,
followed by either one or two stop bits. Configuration of the serial data format
is controlled using the SLW, SLP and SLS handset commands (see section
6.4.3).
•
7 data bits with an odd or even parity bit
•
8 data bits without a parity bit
•
8 data bits with an odd or even parity bit
The maximum throughput over the Remote Serial Link is over 9600bps.
Therefore, end-to-end data rates of up to and including 9600bps are normally
achievable with no loss of data or throughput. At higher baud rates,
throughput will be limited. This is controlled by using standard RS232
CTS/RTS ‘hardware flow control’ to limit the data entering the SmartLink
system to ensure no data is lost (see below).
Full duplex serial communications can be accommodated, with the throughput
in one direction only dropping below 9600bps if data is transmitted in the other
direction at the same time. Again, any drop in throughput is handled using
‘hardware flow control’.
667/HB/30400/000
Issue 6
Page 15
The maximum throughput remains above 9600bps even if the Remote Unit is
also providing a Remote Detector Link. However, there may be slight
degradation of performance in the Remote Detector Link while serial data is
transmitted over the Remove Serial Link to or from the same Remote Unit.
This degradation may cause short detector activations (e.g. higher speed or
short vehicles) to be missed.
If all short detector activations need to be reproduced at the same time as
serial data needs to be sent, then two separate Remote Units should be
installed, one to provide the Remote Detector Link and another to provide the
Remote Serial Link.
However, for most installations that require both Remote Detectors and
Remote Serial, such as those near car park signs, only longer detector
activations will be produced from vehicles entering or exiting the car park and
these will appear unaffected by the Remote Serial Link.
RS232 Control Signals
BUFFER
In addition to the transfer of serial data, the RS232 control signals RTS, CTS,
DTR and DSR are also handled by the SmartLink Remote Serial facility.
Miscellaneous Traffic Equipment A
RTS
STOP
DTR
DSR
CTS
TXD
FULL
SmartLink Local or Remote Unit
FULL
SmartLink Local or Remote Unit
FULL
TXD
STOP
CTS
DSR
DTR
RTS
FULL
Miscellaneous Traffic Equipment B
667/HB/30400/000
RXD
Issue 6
BUFFER
STOP
BUFFER
FULL
BUFFER
BUFFER
RXD
BUFFER
STOP
FULL
Page 16
The state of the DTR input signal at one end of the SmartLink Remote Serial
Link is reproduced on the DSR output at the other end within 100ms. The
DTR and DSR signals can for example be used by Equipment A as an
indication that Equipment B has been connected to the ‘other side’ of the
Remote Serial Link.
The state of the RTS input signal at one end of the SmartLink Remote Serial
link is reproduced on the CTS output at the other end typically within 100ms
(unless ‘hardware flow control’ needs to deactivate the CTS output in order to
limit the incoming data stream). The RTS and CTS signals can therefore be
used for hardware flow control between the Equipment at either end of the
Remote Serial Link.
For example, in response to external Equipment A deactivating RTS,
SmartLink will immediately suspend transmission of serial data to Equipment
A. The CTS signal at the other end of the Remote Serial Link will typically go
inactive within 100ms, which should stop transmissions from Equipment B into
SmartLink. SmartLink will buffer any data received from Equipment B before
the CTS signal stopped its transmissions and this data will be transmitted to
Equipment A when Equipment A reactivates RTS. Therefore, no serial data
will be lost.
In addition, the RTS/CTS signals are also used by SmartLink for hardware
flow control for when the data entering the SmartLink Remote Serial Link is
close to overwhelming the throughput and buffering of the radio link. This
provides an error free link even if the baud rates allow data to enter the
SmartLink Remote Serial Link at a higher rate than the radio link can handle,
or there is a short temporary degradation of throughput due to radio
interference for example.
If the external equipment does not support hardware flow control, then the
facility can be disabled using the “SLH R=0” handset command. In this case,
SmartLink will transmit serial data (on RXD) to the equipment regardless of
the state of the RTS input, and therefore the RTS input can be left
disconnected. SmartLink will however continue to control the CTS output. If
the external equipment ignores the state of the CTS signal, then serial data
may be lost.
Data Latency
With any digital communications system there is the question of latency. Put
simply, in any digital system there is a finite delay between data entering the
system at one end and it emerging from the other.
For the SmartLink Remote Serial Link, serial data will normally appear at the
destination within 100ms of entering the system, and typically much quicker
than this. However, several things can affect the latency, for example:
If data needs to be re-transmitted across the radio link because radio
interference corrupted the original transmission, then this could add tens of
milliseconds to the latency.
If baud rates higher than the maximum throughput are used, an inevitable
backlog will build up if large amounts of data are transmitted.
667/HB/30400/000
Issue 6
Page 17
2.2.4 Controller Linking
Traffic Controllers may be linked in various ways to achieve synchronised
operations between them. Some examples are listed below:
¾ CLF – Cableless Linking Facility, which uses local plans that are kept
synchronised purely by the synchronised clocks in the Controllers
¾ UTC – Urban Traffic Control were each Controller is linked back to a
central office via telephone lines
¾ Local Linking – Digital I/O signals are passed from one Controller to a
second nearby Controller
For UTC and Local Linking, the links between the Traffic Controllers can be
provided by SmartLink. For CLF, there is no direct connection between the
Controllers.
For Local Linking, one or more digital outputs from one Traffic Controller (or
MOVA unit for example) can be passed on to a second Traffic Controller (or
MOVA unit). This can be provided by the Remote Detectors feature of
SmartLink. See Scenario 1 which starts on page 11.
For UTC, Scenario 2 (which starts on page 13) should always be used to pass
UTC Control and Reply data between Traffic Controllers. Individual Control
and Reply bits should not be passed from an OTU at one location to a Traffic
Controller at a second location using the Remote Detectors feature of
SmartLink.
2.2.5 Integrated Traffic Network
These three scenarios can be combined within the LUC, providing a highly
sophisticated and integrated radio-based traffic network.
Figure 6 – Integrated Traffic Network
667/HB/30400/000
Issue 6
Page 18
2.3
Security
Security features highly in the SmartLink design. Unlike some less secure
radio networks, SmartLink is not IP based. Data is transmitted around the
network using the DECT transport protocol, which offers a very high degree of
security.
Additionally each RU and LUC/NRH has to be physically subscribed to its
specific LUC/BRH during the installation process. Only subscribed units are
able to communicate data in the system, making it virtually impossible for an
attacker to break in.
To further improve security each Gateway LUC effectively acts as a security
firewall. Only a very limited set of TC12 data messages is passed between
SmartLink and the UTC system. There are no underlying transport layers that
an attacker can hijack and therefore no possibility that an attacker can break
into the SmartLink system and use it as a means to gain access to any
systems further up the chain.
667/HB/30400/000
Issue 6
Page 19
Section 3 – The Equipment
A SmartLink system comprises several components, providing the necessary
radio infrastructure as well as traffic interfaces such as TR2210 compliant
inputs and outputs.
The system consists of four separate units:
•
Local Unit Controller (LUC) provides the main processing resource and
resides within the traffic controller
•
TC12 Line Interface Unit (LIU) to connect the LUC to the telephone line
to the TC12 UTC Instation or TC12 OTU.
•
Radio Head (RH) deployed to provide either a Base Radio Head (BRH)
or Network Radio Head (NRH) for the LUC.
•
Remote Unit (RU) used to collect and deliver remote detector and
serial data
Some of the possible connections are shown in Figure 7 overleaf.
Depending on local conditions, the following additional items of equipment
may also be used at an installation. They are:
•
Repeater station to extend the distance between Remote Units and
Radio Heads, or for use when sight lines are difficult to establish.
•
Belled pole, for use with Remote Units and Repeaters to hold the
power supply and detectors, if required.
•
Pole cap extension kit for sites with insufficient free connections in the
pole cap
667/HB/30400/000
Issue 6
Page 20
The shaded items in Figure 7 are those developed specifically for SmartLink.
The other items are existing STC products.
Any of these four remote links
may be to other LUCs further
from the TC12 Instation
To another LUC
closer to the
TC12 Instation
Remote
Unit
Base
Radio
Head
RS485
Local Unit
Controller
(LUC)
I/O
RS232
Remote Serial Link
(e.g. to/from a VMS)
RS232
Remote
Unit
xxxxx
Maintenance
Handset Port
I/O
xxxxx
Remote
Unit
Traffic Light Controller Roadside Cabinet
RS232
I/O
xxxxx
Network
Radio
Head
xxxxx
Remote
Unit
I/O
Detector
Card(s)
RS232
TC12 Line
Interface
Unit (LIU)
I/O
Remote Serial Link
to/from a VMS for example
(on one Remote Unit only)
OR
Phone
Cable
Other
Detectors
I/O
TC12
Outstation
(OTU)
Inductive Loops
in the Road to
detect Vehicles
OTU
RS232
Daughter
Card
I/O
I/O
Traffic Light
Controller
(TLC)
Figure 7 – SmartLink Connections to a Controller
The connection between the LUC and the OTU may use the OTU’s existing
telephone line cable. Thus, a separate TC12 LIU has been developed that
connects to an RS232 port on the LUC and to the OTU’s existing telephone
line cable.
Alternatively, the OTU can be fitted with an RS232 daughter card and that
RS232 port can be connected directly to the RS232 port on the LUC.
The existing STC handset is used for all configuration work at the Local Unit
Controller (LUC) and the Remote Unit (RU). At both, the user will be able to
plug in the handset to a serial port and communicate with the unit to perform
certain activities. The handset commands are described in Section 8.
667/HB/30400/000
Issue 6
Page 21
3.1
Local Unit Controller (LUC) – All Scenarios
The heart of the SmartLink system, the LUC (also known as the Local Unit or
LU) provides the processing resources necessary to manage the radio
network, and the interfaces to the host traffic controller and TC12 system.
The LUC is located in the Traffic Light Controller cabinet, connected to a
standard detector backplane. Connections on the backplane are described in
the Installation section (5.4.1).
Figure 8 – LUC Front Panel and PCB
Each LUC connects to a Base Radio Head (BRH) that can support four radio
links to other ‘distant’ endpoints, either Remote Units or NRHs connected to
other LUCs. The LUC is connected to the BRH and/or NRH through RS485
links, allowing the Radio Heads to be fitted on any traffic signal pole at the
junction, while the LUC is fitted in the controller cabinet.
The LUC also features three RS232 serial channels for:
•
TR2210 compatible handset port for system configuration
•
Transmission of TC12 data to an OTU
•
Transmission of remote serial data such as sign control messages
667/HB/30400/000
Issue 6
Page 22
3.1.1 Gateway and Network LUC – Scenario 2 (TC12)
In a radio networked TC12 system, there is one Gateway LUC and several
Network LUCs, see Figure 4 on page 14 and Figure 9 below.
NRH Port
RS485
BRH
NRH
BRH
NRH
BRH
RS485
RS485
RS485
RS485
RS485
Gateway
LUC
‘Higher’
Network
LUC
‘Lower’
Network
LUC
RS232
RS232
RS232
SHORT
RS232
CABLE
RS485
SHORT
RS232
CABLE
RS232
RS232
TC12 LIU
TC12 LIU
TC12 LIU
Existing
OTU
INCOMING
TC12
TELEPHONE
LINE
SHORT
PHONE
CABLE
Existing
OTU
SHORT
PHONE
CABLE
Modified or
New OTU
SHORT
RS232
CABLE
TC12 MODEM
INTERFACE
TC12 MODEM
INTERFACE
TC12
MODEM
RS232
INTERFACE
CARD
TC12
OTU
TC12
OTU
TC12
OTU
TRAFFIC LIGHT
CONTROLLER
TRAFFIC LIGHT
CONTROLLER
TRAFFIC LIGHT
CONTROLLER
Figure 9 – Gateway/Network Configuration
The type of LUC is configured using the LUT handset command (page 105),
since there is no physical difference between the types of LUC.
The LUC that acts as the link to the telephone line to the Instation is termed
the ‘Gateway’ LUC (LUT:3). All other LUCs in the radio network are termed
‘Network’ LUCs (LUT:4).
A Network LUC can also pass TC12 data on to other Network LUCs further
‘down’ the network. In this case, the Network LUC closer to the Gateway LUC
is termed the ‘Higher’ Network LUC with respect to the ‘Lower’ Network LUC
further from the Gateway LUC, further ‘down’ the network.
LUCs that are only connected to Remote Units and are not used for TC12 are
termed ‘Isolated’ LUCs (LUT:1, the default). However, both Gateway LUC and
Network LUC may have radio connections to Remote Units.
For Scenarios 1 & 3 (Remote Detectors and Serial), all LUC can be
considered the same, regardless of whether the LUC is a Gateway or Network
LUC in a TC12 system.
667/HB/30400/000
Issue 6
Page 23
3.1.2 LUC LEDs – All Scenarios
The green ‘Status LED’ on the LUC front panel flashes to show the software
running. The small LEDs on the PCB are for engineering use only.
The 8 Red LEDs on the LUC front panel initially (after a power-up) show the
state of the eight relay outputs. The LEDs are automatically extinguished after
a few minutes to save power.
Pressing the ‘LED Enable’ button briefly gives the following information at the
LEDs…
Detector States – State on power-up or first press after LEDs switched off:
1
4
OFF
5
8
ON
This shows the state of the relay detector outputs on the LUC with ON
indicating that a vehicle is present (or detector not used).
The example above shows a vehicle present on detector 1, but not on
detectors 2, 3 and 4. Detectors 5 through 8 are also active which may indicate
vehicles present or that those detectors are not being used.
If an LED is flashing once per second then that detector is being forced active
because the radio link is not working correctly and the detector has entered
‘DFM’. If the link is now working, press and hold the ‘LED Enable’ button for 3
seconds to request a DFM reset. See the handset commands DFT and DFA
for more information.
Note that for Controller Linking, the LED will be off for ‘active’, on for ‘idle’, see
the note on the Remote Unit LEDs on page 37.
Briefly pressing the ‘LED Enable’ button changes the ‘mode’ of the LEDs to
show…
Serial Port Activity
1
4
ON = TX = Transmitting data
5
8
ON = RX = Receiving data
NRH
Port
BRH Remote OTU
Port
Serial
Port
In this ‘mode’, the LEDs illuminate when data is being transmitted or received
on the various serial ports.
In the above example, the LUC is receiving data on the NRH port, transmitting
data on the OTU port, and is both transmitting and receiving data on the BRH
port.
667/HB/30400/000
Issue 6
Page 24
Due to the enhanced protocol between the LUC and the BRH, it is common
for both the ‘transmit’ and ‘receive’ LEDs to illuminate at what appears to be
the same time. This is because any data sent between the LUC and the BRH
is normally followed by an acknowledgement in the opposite direction. To
more clearly see the activity on the BRH serial port, press the ‘LED Enable’
button again to see the activity on the four radio links…
Radio Link Activity
1
4
5
8
Link A
ON = TX = (Attempting to) Transmit data
ON = RX = Receiving data
Link B Link C Link D
In this ‘mode’, the LEDs illuminate when data is being transmitted or received
on the up to four radio links, A to D. In the above example, the LUC is
receiving data from radio links A and B and transmitting data on radio links C
and D.
For radio links to Remote Units, the LUC will normally be receiving a
continuous stream of detector data from the Remote Unit, therefore the
receiving data LED would be on almost continuously.
For radio links to Network LUC, the UTC control message is normally
transmitted on each link simultaneously once a second. Following this, the
UTC reply messages would normally be received. This should be clearly
visible on the LEDs.
To see which OTUs are replying, press the ‘LED Enable’ button again to see
which UTC reply messages are being received…
UTC Reply Messages
UTC Reply from Forth OTU (GAD:3)
1
4
5
8
In this ‘mode’, the LEDs illuminate when UTC reply messages for any of the
first eight OTUs are received. In the above example, the LUC has received
UTC reply messages from the second, third, fourth and fifth OTUs.
On the Gateway LUC, the LED is illuminated when the reply message is
received and is extinguished when it is sent to the Instation. On a Network
LUC, the LED just flashes briefly when the reply message ‘passes through’
that LUC on its way to the Gateway LUC.
If the ‘LED Enable’ button is pressed again, the LEDs are switched off, and
pressing the button again shows the Detector States again.
667/HB/30400/000
Issue 6
Page 25
3.1.3 LUC Relay Detector Outputs - Scenario 1 (Remote Detectors)
The outputs from the Local Unit Controller are changeover relay contacts
providing both Normally Closed and Normally Open connections. See section
5.4.1 on page 58 for the actual connections on the detector backplane.
The installer can then decide to use either the Normally Closed or Normally
Open contacts depending on the requirements of the Traffic Light Controller
or other equipment.
IMPORTANT: Just like a detector card, the LUC normally energises the relays
and releases them for ‘detect’, so that power failure also shows the ‘detect’
state. Thus, the idle ‘no detect’ state is actually the state with the relays
energised. Therefore, the ‘normally open’ logical state actually uses the
‘normally closed’ physical connection on the relay so the output ‘closes’ when
the power fails indicating ‘detect’.
COM
NO
NC
OUTPUT – “Normally Closed”, open for detect
OUTPUT – “Normally Open”, closed for detect
COMMON
Note that, as is the convention, the relay is shown in the non-powered state
Figure 10 – LUC Relays
This does mean however, that for Controller Linking (see Figure 2 on page
12), the output labelled “Normally Closed” is used, so that the ‘normally open’
relay contact is actually used.
667/HB/30400/000
Issue 6
Page 26
3.1.4 LUC OTU Port – Scenario 2 (TC12)
The connection on the OTU RS232 daughter card is an IDC 10-way
connector. This same style connector is used on both the LUC and the LIU,
allowing 10-way IDC plugs and ribbon cables to be used.
OTU
LUC
10
LUC
10
LIU
10
9
10
9
9
9
10
10
10-Way IDC
10-Way IDC
10-Way
IDC
1
1
1
2
1
2
1
2
10-Way
IDC
10-Way
IDC
1
2
10-Way
IDC
Figure 11 – LUC OTU Port
Å (Cable E) OTU to LUC – LUC to LIU (Cable H) Æ
OTU
10W
10
9
8
7
6
5
4
3
2
1
OTU
Signal
RXD
CTS
(DCD)
RTS
TXD
DTR
GND
N/C
N/C
N/C
Direction
Å
Å
Æ
Æ
Æ
N/A
-
LUC
Signal
TXD
RTS
N/C
CTS
RXD
(DSR)
GND
(DTR)
(DCD)
N/C
LUC
10W
10
9
8
7
6
5
4
3
2
1
LUC
Signal
TXD
RTS
N/C
CTS
RXD
(DSR)
GND
N/C
DCD
N/C
Direction
Æ
Æ
Å
Å
Å
N/A
Æ
Å
-
LIU
Signal
TXD
RTS
N/C
CTS
RXD
(DSR)
GND
N/C
DCD
N/C
LIU
10W
10
9
8
7
6
5
4
3
2
1
Figure 12 – LUC OTU Connector to OTU (Cable E) or LIU (Cable H)
Note that although two ‘direction’ columns are shown in the table, the
directions with respect to the LUC are identical in both columns and the pins
have the same function in both cases.
When an LUC is connected directly to the OTU’s RS232 daughter card, the
connection can be thought of as a null-modem connection. Hence, it is
common that the names at the two ends of the connection do not match. For
example, TXD is connected to RXD.
This is not the case for the LUC/LIU connections. Here, for example, the RXD
pin on the LUC is connected to the RXD pin on the LIU. As with all modems,
the RXD pin of the LIU is an output from the modem to the terminal device (in
this case the LUC) so the data can be received on the RXD pin of the device.
667/HB/30400/000
Issue 6
Page 27
3.1.5 LUC NRH Port – Scenario 2 (TC12)
The serial connection to the TC12 LIU (Instation) and the RS485 connection
to the Network Radio Head on an LUC are in fact the same physical port on
the front panel since both connections are never required on the same LUC.
See the diagram below for details.
RS485
RS485
BRH
NRH
BRH
RS485
RS485
RS485
Gateway
LUC
TC12 LIU
INCOMING
TC12
TELEPHONE
LINE
Network
LUC
Same Physical Port
on the LUC
Figure 13 – LUC NRH Port Usage
10
9
8
7
6
5
4
3
2
1
RTS_P
RTS_N
TXD_P
TXD_N
CTS_P
CTS_N
RXD_P
RXD_N
GND
DCD
Figure 14 – LUC NRH Port Pins
The signals RXD, TXD, CTS and RTS are RS485 and are used by the NRH
and the LIU. The DCD signal is only used by the LIU and so is RS232.
3.1.6 LUC BRH Port – All Scenarios
The BRH Port on the LUC is only ever connected to a Base Radio Head.
10
9
8
7
6
5
4
3
2
1
RTS_P
RTS_N
TXD_P
TXD_N
CTS_P
CTS_N
RXD_P
RXD_N
0V
+24V
Figure 15 – LUC BRH Port Pins
Note that the power on pins 1 and 2 should only be used by the BRH
Installation Support Kit described section 6.2. Once installed, see section 5.6
on page 62, a BRH must obtain its power directly from 24V Detector Supply
in the controller cabinet and not through the LUC.
667/HB/30400/000
Issue 6
Page 28
3.1.7 LUC Remote Serial Port – Scenario 3 (Remote Serial)
A straight 9-way IDC cable from the 10-way IDC connector on the LUC can be
fitted with a 9-way D-Type to plug in to the DTE socket at the ‘other’
equipment.
Other Equipment
9-Way D-Type DTE
1
6
2
7
3
8
4
9
5
Signal
(CD)
DSR
RXD
RTS
TXD
CTS
DTR
(RI)
Ground
Direction
Å
Å
Å
Æ
Æ
Å
Æ
Å
-
Used?
No
No
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
LUC
10-Way IDC DCE
10
9
8
7
6
5
4
3
2
1
Figure 16 – LUC Remote Serial (10W IDC) to 9W D-Type
Note that pin 1 of the IDC connector is at the bottom and pin 1 of the D-Type
is at the top, to match their actual positions on rack mounted 3U cards. Use
the 9 pins starting at pin 1 of the 10-way IDC plug so that it is more obvious
when fitting a 9-way cable into the 10-way plug. Pin 10 on the IDC plug and
socket is therefore left open-circuit.
The Remote Serial Port on the LUC is automatically powered down until a
valid RS232 signal is detected, i.e. until equipment is connected.
667/HB/30400/000
Issue 6
Page 29
3.2
Line Interface Unit (LIU) – Scenario 2 (TC12)
The LIU serves a dual purpose within the SmartLink architecture.
Firstly, it allows the SmartLink system to interface directly with a TC12
telephone line and thus acts as the gateway from the UTC system to the radio
network.
Secondly, it allows existing TC12 OTUs (i.e. those without RS232 daughter
cards) to interface to a SmartLink LUC, allowing them to be simply unplugged
from their telephone line connections and plugged into the back of an LIU.
See Figure 9 on page 23.
Figure 17 – LIU Front Panel and PCB
On the front of the LIU are the serial port connections to the LUC, LED
indications and test jacks. The telephone line connection is at the rear.
The LIU is a Modem, modulating transmit data from the serial port onto the
telephone line and demodulating received data from the telephone line to the
serial port.
The serial port can either use RS485 or RS232 signals, but not both, selected
by connecting to the appropriate socket on the front of the LIU.
The test jacks provide the standard interface to the TC12 Instation Test Set.
3.2.1 LIU LEDs
The LED indications show:
•
RED .............Power present
•
YELLOW .....Data being transmitted onto the telephone line
•
GREEN ........Data being received from the telephone line
667/HB/30400/000
Issue 6
Page 30
3.2.2 LIU Connections
On the LIU, two serial port connections are provided:
The first connector allows the OTU port on the LUC to be connected to the
LIU (rather than the LUC connected directly to the OTU). The cable is shown
in Figure 18. This allows the telephone cables of existing OTUs (which do not
have the RS232 capability) to be plugged into the telephone socket on the LIU
and the LUC connected to the RS232 port on the LIU.
10-WAY IDC SOCKETS
(con: 508/4/26119/000)
LUC
(OTU)
LIU
(RS232)
TXD_O
10
10
TXD_O
RTS_O
9
9
RTS_O
NC
8
8
NC
CTS_O
7
7
CTS_O
RXD_O
6
6
RXD_O
DSR_O
5
5
DSR_O
0V
4
4
0V
NC
3
3
NC
DCD_O
2
2
DCD_O
NC
1
1
NC
10-WAY FLAT RIBBON CABLE
667/1/30778/000
60mm
SMARTLINK CABLE E DETAIL
Figure 18 – Cable E: LUC (OTU) to LIU (RS232)
667/HB/30400/000
Issue 6
Page 31
The second connector allows the NRH port on the LUC to be connected
directly to the LIU. This connector, which is shown in Figure 19, uses RS485
for the RXD, TXD, CTS and RTS signals, but RS232 for CD. In this case, the
telephone line from the LIU would be connected to the Instation. An LIU with a
telephone cable and cover is shown in Figure 20.
10-WAY IDC SOCKETS
(con: 508/4/26119/000
strain relief: 508/4/26119/030)
LUC
(NRH)
LIU
(RS485)
RTS_R1_P
10
1
RTS_P
RTS_R1_N
9
2
RTS_N
TXD_R1_P
8
3
TXD_P
TXD_R1_N
7
4
TXD_N
CTS_R1_P
6
5
CTS_P
CTS_R1_N
5
6
CTS_N
RXD_R1_P
4
7
RXD_P
RXD_R1_N
3
8
RXD_N
DSG
2
9
GND
DCD_R1
1
10
DCD
10-WAY FLAT RIBBON CABLE
667/1/30778/001
40mm
SMARTLINK CABLE F DETAIL
Figure 19 – Cable F: LUC (NRH) to LIU (RS485)
Figure 20 – LIU with Telephone Cable and Cover
667/HB/30400/000
Issue 6
Page 32
3.3
Radio Head – All Scenarios
To offer maximum flexibility, optimum performance and ease of connection,
the SmartLink radio components are contained within Radio Heads that can
be installed on convenient traffic poles anywhere around a junction,
communicating with the LUC using RS485 serial channels.
A specially designed bracket attaches the Radio Head on its mast to the traffic
pole. The bracket includes a connector and cable wired into the pole cap.
Figure 21 – Radio Head mounted on a
Traffic Signal Pole
Figure 22 – Radio Head
Assembly
Radio Heads implement DECT protocols and provide the radio interface.
The LED indicators on the PCB are for engineering use only.
667/HB/30400/000
Issue 6
Page 33
3.3.1 Base Radio Head (BRH)
A BRH connected to an LUC is always required in any SmartLink
implementation and is the central point for local communications around an
intersection and for TC12 network links to other intersections.
A BRH connected to an LUC can support a maximum of four radio links, each
of which can be used as either:
•
A remote detector link receiving detector data and/or serial data from a
Remote Unit
•
A network link providing a hop to another LUC equipped with a NRH (see
section 3.3.2).
3.3.2 Network Radio Head (NRH)
A NRH connected to an LUC provides a single TC12 network link that
connects the LUC and controller to another LUC with a BRH.
In a TC12 application, a NRH connected to an LUC is required at the next
remote node in the network to complete the network link. That LUC may also
be fitted with a BRH if it is required to communicate with other nodes ‘further
down’ in the TC12 network; see Figure 4 on page 14.
667/HB/30400/000
Issue 6
Page 34
3.4
Remote Unit (RU) – Scenarios 1 & 3 (Remote Detectors/Serial)
The Remote Unit consists of a DECT radio module on a PCB with a stubby
antenna contained within a weatherproof enclosure set on a mast. A specially
designed bracket attaches the Remote Unit to the pole and provides
connections to the pole cap or terminal block.
Figure 23 – Remote Unit Assembly
A Remote Unit looks identical to a Radio Head from the outside (see Figure
21 on page 33).
Up to four Remote Units may be radio linked to each BRH/LUC. The RU
provides eight TR2210 compliant inputs that may be used to communicate
detector data, together with a serial input/output channel. See section 5.7 for
connections.
The Remote Serial Port on the RU is automatically powered down until a valid
RS232 signal is detected, i.e. until equipment is connected.
667/HB/30400/000
Issue 6
Page 35
3.4.1 RU Detector Inputs
Each Remote Unit has eight detector inputs and each Local Unit Controller
can communicate with up to four Remote Units, making a maximum of 32
detector inputs. However, since each Local Unit only has eight detector
outputs, the inputs from the Remote Units are ‘mapped’ on to these outputs.
Any of the eight Detector Inputs on a Remote Unit can be used, with the state
mirrored on the associated Detector Output on the Local Unit (once
commissioned). However, all eight Detector Inputs on one Remote Unit
should not be used at the same time. At least two must be left open-circuit,
limiting each Remote Unit to a maximum of six Detector Inputs, although
these can be spread over any of the eight Detector Inputs. If more than six
Detector Inputs are required at one location, then two Remote Units should be
installed, with Remote Unit A providing Detector Inputs 1-4 and Remote Unit
B providing Detector Inputs 5-8 for example.
The following diagram (Figure 24) shows the default ‘mapping’ with all eight
detector outputs allocated so two detector inputs are available at each
Remote Unit. Use the command RSA to modify this default allocation if
required.
Detector 1
Detector 2
Detector 3
Detector 4
Detector 5
Detector 6
Detector 7
Detector 8
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
Remote
Unit
Link A
Local Unit
Controller
(LUC)
1
2
3
4
5
6
7
8
Remote
Unit
Link B
Remote
Unit
Link C
Remote
Unit
Link D
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
Detectors 1 & 3
Not Used
Not Used
Detectors 3 & 4
Not Used
Not Used
Detectors 5 & 6
Not Used
Not Used
Detectors 7 & 8
Figure 24 – RU to LUC Detector Mapping
For Remote Detectors, the Remote Unit should always be connected to the
Normally Closed contacts on any detector cards, so the input to the Remote
Unit will go open circuit when a vehicle is detected. Should the connections
between the Remote Unit and the detector card fail, the Remote Unit will
assume that a vehicle has been detected, the ‘safe’ state. The output from the
detector card will also go open-circuit if the detector card loses power.
It also means that both the Remote Unit and the LUC both know the state of
the inputs for ‘detect’, i.e. open-circuit, and so no configuration information is
required to configure the ‘true or inverse’ state of these inputs. The LUC then
provides both Normally Open and Normally Closed relay contacts for each
detector. See section 3.1.3 on page 26 for details.
667/HB/30400/000
Issue 6
Page 36
For Controller Linking, the Remote Unit would normally be connected to
Normally Open contacts of the Controller (or MOVA unit for example), see
Figure 2 on page 12.
3.4.2 RU LEDs
Indicators on the PCB are as follows:
DLP19 (middle of PCB)
Green – flashing shows software running
Other green LEDs
Engineering use only
8 Red LEDs (top right)
Pressing the ‘LED Enable’ button gives the
following information on these LEDs…
Detector States – State on power-up or first press after LEDs switched off:
8
Detector 1
ON
1
This shows the state of the detector inputs on the RU with ON indicating that
a vehicle is present (or input unused and left open circuit).
The LEDs are automatically extinguished after a few minutes to save power.
The above example shows a vehicle present on detector input 1, but not on
inputs 2 through 4. Detector inputs 5 through 8 are all open-circuit and thus
are probably not used.
Note that for Controller Linking, the LED will be off for ‘active’, on for ‘idle’,
since the RU will probably be connected to a ‘Normally Open’ output of a
Traffic Controller (or MOVA unit for example), and not to the ‘Normally Closed’
contacts of a Detector Card.
Serial Port Activity
8
ON = Transmitting to the Radio Module
ON = Receiving from the Radio Module
ON = Transmitting to the Handset Port
ON = Receiving from the Handset Port
1
ON = Transmitting to the Remote Serial Port
ON = Receiving from the Remote Serial Port
In this mode, the LEDs show the activity on each serial port. In the above
example, the RU is transmitting data to the Radio Module (and therefore
probably back to the LUC). It is also transmitting and receiving data on the
Handset Port.
If the ‘LED Enable’ button is pressed again, the LEDs are switched off, and
pressing the button again shows the Detector States again.
667/HB/30400/000
Issue 6
Page 37
3.5
Antenna – All Scenarios
Choosing the right antenna configuration can ensure that best use is being
made of the available signal.
The range and coverage of the system are affected by three main factors:
o Power – How much RF power is delivered to air
o Sensitivity – How sensitive is the receiver system
o Environment – How much the signal is attenuated by the environment
through which it passes.
Power is limited by the DECT standard in order to facilitate multiple re-use of
the spectrum. The quality of the receiver systems is such that most DECT
product is as good as it can be in order to provide the coverage needed and
allow spectrum reuse. The only variables left are the environment and the
antenna systems.
Provided within the RU/Radio Head enclosure is a stubby omni-directional
dipole antenna. This is suitable for use over relatively short distances where
no other units nearby could interfere with the signal.
There is also a more powerful directional antenna for use in certain
applications to improve the quality of the wireless link over longer distances or
where an omni-directional antenna could interfere with the signal from a
nearby unit. Hence, directional antennas are always used at a Repeater node.
SmartLink is based on a point to multi-point architecture. Therefore, the
LUC/BRH must be able to communicate effectively with all its surrounding
RUs and/or NRH/LUCs wherever they are located. Normally, the LUC/BRH
communicates with more than one RU or NRH and it is therefore fitted with an
omni-directional antenna, as standard. However, there are some scenarios, in
particular with respect to repeater configurations, where the LUC/BRH may
require one or more directional antennas.
3.6
Repeater Station – Option for all Scenarios
Where the distance between sites exceeds approximately 300m, or an
obstruction prevents ‘line of sight’ between the sites, a Repeater station is
available to bridge the gap.
The equipment consists of two Radio Head circuit boards, linked by a
crossover cable and contained within one enclosure, and two directional
antennas located on a single mast.
The Repeater needs mains power (for its 24V AC transformer) but no other
external connections.
667/HB/30400/000
Issue 6
Page 38
3.7
Technical Specification
3.7.1 Local Unit Controller (LUC)
Double width 3U card – with standard detector backplane interface
Power supply .................................................................................. 24V AC/DC
Typical current consumption...................................................................112 mA
Number of linked RUs .............................................................................. 4 max
Number of linked NRHs............................................................................ 4 max
Total number of linked RUs and NRHs..................................................... 4 max
Number of remote serial channels.................................................................... 1
Max remote serial channel baud rate ............................................... 38400 bps
Number of TR2210 compliant outputs ............................................................. 8
Typical remote detector delay................................................................. 100 ms
Remote Detector count accuracy ..............................................better than 99%
3.7.2 TC12 Line Interface Unit (LIU)
Double width 3U card
Power supply .................................................................................. 24V AC/DC
Typical current consumption (DSP / Modem variants)................ 37 mA / 62 mA
Line interface .......................................................................... TC12 compatible
3.7.3 Remote Unit (RU)
Enclosure (including antenna) ................................240mm x 130mm x 150mm
Power supply ................................................................................... 24V AC/DC
Typical current consumption.....................................................................46 mA
Number of remote serial channels.................................................................... 1
Max remote serial channel baud rate ............................................... 38400 bps
Number of TR2210 compliant inputs ................................................................ 8
Frequency .................................................................................. 1.88 – 1.9 GHz
Protocol ................................................................................................... DECT
Typical range ............................................................................................. 300m
Typical range (with repeater) ..................................................................... 600m
667/HB/30400/000
Issue 6
Page 39
3.7.4 Radio Heads (BRH and NRH)
Enclosure (including antenna) ................................240mm x 130mm x 150mm
Power supply ................................................................. 24V AC/DC (20V min.)
Typical current consumption.....................................................................44 mA
Frequency .................................................................................. 1.88 – 1.9 GHz
Protocol ................................................................................................... DECT
Typical range ............................................................................................ 300m
Typical range (with repeater) ..................................................................... 600m
667/HB/30400/000
Issue 6
Page 40
Section 4 – Site Surveys
4.1
General
DECT is a low powered radio technology that allows the efficient re-use of the
same radio spectrum. To enable frequency re-use, the power is limited to
250mW, allowing SmartLink to provide an effective range of 300 metres,
subject to line of sight. This range can be extended to 600 metres by use of a
Repeater node.
Other distances may be achievable. For specific requirements please refer to
the Engineering Dept. (Poole).
The traffic detector application introduces the technology to a new
environment that has a particular mix of characteristics:
•
External (Outdoor) – Cold, heat, rain etc.
•
Open – Needs line of sight
•
Cluttered – Buildings, street furniture etc.
•
Traffic – Vehicles moving in the coverage area, maybe obscuring paths.
•
Co-located DECT systems – PBX, Cordless, EPOS, Traffic detectors.
The environment is by its nature dynamic with transient or short-term
environmental, weather and content changes. However, there is also the
possibility that over time significant, permanent changes may occur. These
may be DECT specific, such as the installation of a Cordless PBX, or the
establishment of a wireless data system. There may be changes to the
physical environment such as the construction of new buildings or urban
structures (bridges, gantries etc.), or the erection of advertising hoardings and
other street furniture.
This introduces the need for Site surveys:
o Before an installation:

To assess the best location for new pole(s) and confirm sufficient room
is available on the footway for the new pole(s).

To check the availability of power to the remote detector sites (and
Repeater sites if required).

To confirm coverage is satisfactory for each proposed detector head.

To establish and quantify the existence, or otherwise, of other systems,
and their occupancy of the band. It may require a long-term survey
where data is gathered over a period (say one week) to determine the
existence, or otherwise, of possible sources of interference. (Details to
be confirmed)

To outline the positioning and equipment required.

To quantify possible communication cost savings over existing
systems.
o Post Installation:

To check that coverage and data transfer performance is satisfactory.
667/HB/30400/000
Issue 6
Page 41
To ensure that SmartLink can be installed efficiently and that the installations
perform satisfactorily, it is necessary to undertake a site survey before the
Product can be quoted to a customer.
The Survey is intended to check that the site is suitable from a radio
performance viewpoint, as well as highlighting any installation issues that may
affect the installation costs.
The following issues should be examined and all specifically covered in the
survey report. The SmartLink Survey Check List and Equipment Sheet should
be completed. Copies are enclosed in Section 10 and Section 11.
4.2
Survey Equipment
The following equipment is needed to carry out a site survey:
1. binoculars
2. ladder
4.3
Sight Lines
SmartLink is essentially a line of sight product.
For UTC links, the survey must ensure that suitable traffic poles exist at each
site so that the radios are in line of sight.
For remote detectors, the survey should consider the positioning of the new
poles for the Remote Units to ensure that line of sight back to the BRH is
maintained.
There should be no major obstructions such as signs, streetlights or trees
between radios or in close proximity to any radio. The proximity limits are
outlined below. Where possible, the fewer vehicle turning movements that will
cross the sight lines the better.
Note: Great care should be taken when carrying out a site survey in winter
where trees are nearby. Remember that they will become a much larger
obstacle when in leaf and will probably grow over time.
The effect of hills or significant gradient changes must also be considered.
The maximum range of SmartLink should always be kept in mind. Where
there are no obstructions, the distance between units should be no more than
300 metres. For greater link distances please refer to Engineering Department
(Poole). It is recommended that for distances greater than 200 metres, a
directional antenna should be considered, to ensure maximum possible
reliability.
The hardest part of setting up a radio network is finding a location for the
antennas. The radio signal path must have a clear line-of-sight path and a
clearance, along the line of sight, in order to allow SmartLink to perform to its
maximum capability. This is because the radio waves travel essentially in
straight lines through the atmosphere due to their short wavelengths.
667/HB/30400/000
Issue 6
Page 42
In its simplest form, the Fresnel zone can be described as a tube, by which
the radio signal passes between the two radio units. The table below indicates
the radius of the ‘tube’ with respect to the link distance required.
Link Distance
Fresnel zone clearance
100m
1.00m
150m
1.25m
200m
1.50m
250m
1.75m
300m
2.00m
350m
2.00m
400m
2.00m
Put simply, the best way to try to ensure a good radio signal path is to imagine
a ‘cylinder’ or ‘tube’ centred on the direct straight line between the two
antennas. This tube needs to be of approximately 2m radius (4m diameter)
when the distance between the two antennas is 300m, or greater. This means
that there should be no object closer than 2m to the line of sight.
667/HB/30400/000
Issue 6
Page 43
y
el
0m at
15 xim
o
pr
ap
approximately
1.5m radius
Fresnel Zone
Figure 25 – Fresnel Zone
To ensure a good radio signal path between the two antennas, the Radio
Heads and Remote Units should be located so this ‘tube’ between them is
clear of all obstacles.
The use of a repeater node is recommended where no line of sight is
available.
However, if a clear line of sight is not practical then, as a minimum, over 50%
(half) of the ‘tube’s’ cross-section must be kept clear and there must always
be a direct line of sight between the two antennas. Any obstacle inside the
tube will reduce the performance and reliability of the radio link.
667/HB/30400/000
Issue 6
Page 44
Line of sight between
the antennas must be
kept clear
This obstacle will
reduce the quality
of the radio link
Approximately
2m Radius
Freznel Zone
at 300m Range
Figure 26 – Obstacle in Line Of Sight
In these cases, it is strongly recommended that the NRH and/or the LUC/BRH
units utilize directional antennas, in order to increase the radio link
performance and reliability.
4.4
Mounting poles for Base and Network Radio Heads
Base and Network Radio Heads are normally mounted on existing traffic
poles. This generally offers the most cost-effective installation, as no civil
works are required if the existing ducting can be used. However, the following
must be specifically checked:
•
Radio Heads, with omni-directional antennas, must normally be mounted
with at least 7 metres clearance between them. This means that separate
poles are required for the Network Radio Head and the Base Radio Head,
at the same site. Often this can be used to advantage as it can increase
the effective distance achievable between sites and may provide improved
line of sight in each direction. However, if closer head mounting is
unavoidable then directional antennas must be used. Please refer to
Engineering Dept. (Poole) for specific requirements.
•
The poles must be installed within 300m of the controller cabinet.
However, at distances above 50m, confirmation that the supply voltage, at
the pole cap, is greater than 20V.
•
The chosen poles must have a standard set of traffic signal bracket
mounting holes available. Generally, this means the pole must support
three lanterns or fewer. There must also be safe ladder access to the pole.
•
There must be sufficient free space above the position of the Radio Heads
to allow safe positioning near power cables, etc. LOOK UP!
•
The ducting between the controller cabinet and the pole must be clear to
allow the armoured twisted pair RS485 cable to be pulled through.
667/HB/30400/000
Issue 6
Page 45
•
Duct pits at the base of the traffic signal pole must be free of obstructions,
and there must be suitable access to the bottom of the pole.
•
There must be sufficient terminal positions free within the pole cap to allow
the SmartLink communications and power cables to be terminated (10
block positions). These must not be mixed with the lantern drives for safety
reasons.
Note. If sufficient block positions are not available, the pole-top extension
kit may be used. This extends the Siemens pole cap and adds additional
terminations without the need to disconnect existing connections.
•
The pole cap must be suitable to take an extension kit if one is required.
If an existing pole is not available then costs must be included for the
provision of a special pole or poles for the SmartLink heads.
4.5
Mounting Poles for Remote Units & Repeaters
The Remote Units and Repeaters located at remote sites normally need to be
mounted on new dedicated poles that will contain the remote equipment. The
remote equipment requires mains power.
Remember to check above the chosen position for power cables, etc. that
could prove a hazard for installation engineers or a source of interference for
the radio.
4.6
Space within the Controller
As a minimum, any SmartLink installation requires an LUC to be mounted
within the Traffic Light Controller cabinet. At least two standard width positions
are required in the controller or OTU 3U detector rack for this unit.
For UTC applications, it is also necessary to fit TC12 LIU equipment (2 off LIU
at the Gateway LUC and 1 off LIU at all other sites, less 1 off LIU if an RS232
OTU is to be used.) Each LIU requires two standard width positions and
protrudes beyond the back of the detector rack. It does not connect to a
standard backplane.
Viewed from the front, the LUC needs a single backplane attaching to the rack
with a space on the left for an LIU connected to the Instation on a Gateway
LUC and a gap on the right for an LIU connected to an OTU (unless an
RS232 OTU is used).
If there is insufficient space in the controller detector or OTU racks, additional
rack space must be provided.
The controller also needs to provide power for the SmartLink system (see
section 3.7, starting on page 39, for the approximate current consumption of
each unit).
Check that there is sufficient room on the termination bar (castellated or CET)
for the armoured cable(s) at the base of the controller cabinet for the BRH
and/or NRH.
667/HB/30400/000
Issue 6
Page 46
4.6.1 24V Connections in Controller
Establish where in the controller the connections will be made. E.g. tag block,
pin numbers.
The combined current for SmartLink should be calculated (see section 3.7
starting on page 39) and any auxiliary equipment connected to the 24V, e.g.
detectors, should be included to assess whether the Controller can support
the installation. If not, the 24V AC kit should be used.
Consult the relevant controller handbook for details, for example…
T400 Facilities Manual
667/EB/20200/000
Appendix A
ST800 General Handbook
667/HB/27000/000
Section 2.3.5 “Detector Power Supplies”
ST700 General Handbook
667/HB/27880/000
Section 2.4.4 “Detector Power Supplies”
4.6.2 Terminal Blocks
Terminal block positions in the Controller cabinet should be checked to
ensure that sufficient space is available for the SmartLink connections.
4.7
Co-Located Systems
The minimum separation between a BRH and NRH on the same LUC is
recommended to be seven metres when using the omni-directional antennas.
This prevents co-channel interference between radio units. The same
condition applies if a Remote Unit has to be located close to any another
Remote Unit, BRH or NRH.
7m
p
Se
ar
at
io
n
Figure 27 – Separation Distance
667/HB/30400/000
Issue 6
Page 47
4.8
Repeater Node
Where the distance between sites exceeds 300m, a mains powered Repeater
node can be placed between the sites in order to extend the operational
distance of a SmartLink installation.
The repeater unit should be installed at a location no greater than 200m from
the LUC/BRH. The NRH can be installed at a distance of up to 400m from the
repeater, and will be fitted with a directional antenna.
The following example may assist in planning the link layouts.
NRH / RU
Repeater Node
(directional antenna)
Gateway LUC/BRH
(omni. antenna)
Figure 28 – Repeater Configuration
4.9
UTC Telephone Lines / Gateway LUCs
Since the UTC data from all the OTUs and Network LUCs must go back to the
TC12 Instation via the telephone line connected to the Gateway LUC, all the
OTUs must be configured on the same telephone at the Instation.
This can limit the number of OTUs that can be radio networked.
It is therefore important to check on which telephone line each existing site is
configured. It may then be necessary to re-arrange the configuration at the
Instation to put all the existing OTUs that intend to be radio networked on to
the same telephone line.
Careful consideration must also be given to the location of the Gateway LUC.
Several restrictions effect the location of the Gateway LUC.
The first is the limitation on the ‘depth’ of a radio network. No LUC should be
further from the Gateway LUC than necessary. The more radio ‘hops’ required
to reach a Network LUC, the longer the transmission delays will be, and every
667/HB/30400/000
Issue 6
Page 48
radio hop is susceptible to interference and retransmissions. Therefore, it is
recommended that no Network LUC is more than three or four radio hops
from the Gateway LUC. Note that if a Repeater is used, this will count as two
radio hops, not one.
The second is that all Network LUCs within the radio network (except those at
the end of ‘chains’) require both a BRH and NRH to be installed, and these
should not be closer than 7m. Therefore, if there is an installation in which it is
only possible to find one location for a Radio Head, then this installation could
be made the Gateway LUC so that it only requires a BRH and not an NRH.
Finally, the Gateway LUC needs to be connected to the TC12 Instation via a
telephone line.
4.10
Equipment List
A comprehensive list of the equipment needed should be prepared for each
site, including cable lengths, pole requirements (see sections 4.4 and 4.5) and
the availability of power where required.
A completed Survey Check List and Equipment Sheet will assist in this
process…
Section 10 – SmartLink Survey Check List, which starts on page 117
Section 11 – SmartLink Survey Equipment Sheet, on page 124
667/HB/30400/000
Issue 6
Page 49
Section 5 – Installation
5.1
General
The installation procedure for each of the scenarios described in section 2.2
differs in some detail. Where the instructions are specific to a particular
scenario, this is shown by putting Scenario 1, Scenario 2 or Scenario 3 next to
the appropriate section.
It is recommended that approximately one week after installation, a site visit
be made to make sure that the system is working correctly. The rolling log of
the LUC should be inspected for any signs of problems. The LOG is described
in section 8.6, starting on page 112.
Included with each installation is a SmartLink Configuration Sheet (see the
sample in Section 12 on page 125) that should be completed and kept in the
controller cabinet.
Most installations utilise in-built omni-directional antenna. Where a stronger or
more focused radio signal is required, a directional antenna should be used.
See section 5.10 starting on page 68 for details.
For convenience, the commissioning of Remote Units can be done at the
same place as the LUC and Radio Heads. This would involve part of the
equipment being installed, and then commissioning being carried out,
followed by the remainder of the installation. See section 5.2 for further
details.
TC12 installations can only be commissioned once installation is complete.
The following diagrams summarise all of the connections between the LUC
and its BRH, NRH and LIUs.
Section 5.1.1 covers the connections between an LUC and its BRH, which is
required in all scenarios. However, not all connections are required in all
scenarios. For example, the LIUs and their connections are not required at a
site that only has Remote Units.
Section 5.1.2 covers the connections to a NRH on a Network LUC and
therefore is only applicable to Scenario 2 (TC12).
667/HB/30400/000
Issue 6
Page 50
5.1.1 Base Radio Head – All Scenarios
The following diagrams show a Base Radio Head wired back to an LUC.
The LUC shown is a Gateway LUC with two LIUs and an OTU. These, and
their wiring, can be ignored if Scenario 2 (TC12) is not required.
BRH
TB
H
F
BB
E
LIU
LUC
LIU
Controller
Cabinet
OTU
B
J
BT
D*
A
G
G
Power
Distribution
Traffic
Light
Pole
D
TB
J
C
Figure 29 – BRH and Gateway LUC Wiring Summary
G
POWER
DIST.
LIU
LIU
E
1
1
RS232
1
G
RS485
1
OTU
1
NRH
1
LUC
F
RS232
RS485
BT
LINE
J
D*
D
1
REMOTE
SERIAL
BRH
1
OTU
H
J
A
Terminal
Block
TO
BRH
Figure 30 – Gateway LUC Wiring Summary
Colour Codes for equipment that is only required in Scenario 2 (TC12)…
Green = LIU to TC12 Instation (left) at Gateway LUC only
Blue = LIU to TC12 OTU Outstation (right) at Gateway or Network LUC
Red = Direct RS232 connection to OTU from Gateway or Network LUC
See section 9.2 on page 116 for details of the cables.
667/HB/30400/000
Issue 6
Page 51
5.1.2 Network Radio Head – Scenario 2 (TC12) Only
Note that a Network LUC will also have a BRH fitted if it communicates with
other Network LUCs further ‘down’ the network, or is required to communicate
with one or more Remote Units. In this case, make sure that the appropriate
cables are labelled “NRH” or “BRH” at both ends.
NRH
TB
BB
H
E
A (NRH)
LUC
A (BRH)
B
LIU
OTU
Traffic
Light
Pole
D
Controller
Cabinet
J G
Power
Distribution
J
TB
NRH
TB
BRH
C
TO BRH
(as previous figure)
Figure 31 – NRH and Network LUC Wiring Summary
J
POWER
DIST.
LUC
J
Terminal
Block (NRH)
D
1
1
REMOTE
SERIAL
Terminal
Block (BRH)
1
A
BRH
TO BRH
1
RS232
TO NRH
1
LIU
E
RS485
OTU
NRH
1
G
OTU
H
A
Figure 32 – Network LUC Wiring Summary
See section 9.2 on page 116 for details of the cables.
667/HB/30400/000
Issue 6
Page 52
5.2
Order of Installation
The recommended order in which installation should take place is as follows:
Not all steps are required in all scenarios – refer to the ‘Scn’ column.
Scn
1 123
At
-
Ref Instructions
Pg 2 Read the Safety Warning on page 2
2 1–3
RU
5.3
Install belled pole(s) for Remote Unit(s)
3 123
REP
5.3
Install belled poles for any Repeaters that are required
In the Traffic Controller cabinet…
4 123
LUC
-
Fit new 3U rack in controller (if required)
5 123
LUC
-
Fit new 24V AC kit (if required)
6 123
LUC
5.4
Install the LUC. Make the appropriate connections on
the LUC backplane, i.e. power and detector outputs.
7 –2–
LUC
5.5
Install the LIU. Two may be required at the Gateway.
Install the Base and/or Network Radio Head…
8 123
9 123
LUCRH
LUC
-
5.6
Pull the armoured cable through the ducting between
the Controller cabinet and the pole for the Radio Head.
Connect the Radio Head ribbon cable to LUC and fix
the terminal block in cabinet. Mark the cable BRH or
NRH at both ends.
Wire 24V and 0V to the terminal block and wire the
armoured cable to the other side of the terminal block.
10 123
RH
11 123
RH
5.9.1 Fix bracket to traffic signal pole
12 123
RH
5.9.2
13 123
RH
-
14 123
RH
5.10
Fit directional antenna to the Radio Head (if required)
15 123
RH
5.11
Fit the Radio Head to the Mast
16 123
RH
5.12
Attach the Mast to the Bracket and raise the Mast
17 123
REP
5.13
Install any Repeaters that are required
667/HB/30400/000
5.8
Add pole cap extension kit (if required)
Connect bracket cable and armoured cable using the
terminal block in the pole cap
Refit pole cap
Issue 6
Page 53
Scn
At
Ref
18 1–3
LUC
-
19 1–3
LUC
6.4.1
20 1–3
RU
5.9.1 Fix bracket to belled pole
21 1–3
RU
22 1–3
RU
Open RU and plug its cable into the socket on the
3.4.2 bracket. Check that RU is powered and the detector
LEDs illuminate when vehicles pass over the loops.
23 1–3
RU
5.10
Fit directional antenna (if required)
24 1–3
RU
5.11
Fit the Remote Unit to the Mast
25 1–3
RU
5.12
Attach the Mast to the Bracket and raise the Mast
26 1–3
LUC
p106
At the LUC, check that the radio link is active using
RLS handset command
27 1––
LUC
6.4.2 Commission detector set-up
28 1––
LUC
Check that the appropriate LED(s) on the LUC
3.1.2 illuminate when vehicles pass over the associated
loop(s).
29 ––3
LUC
RU
6.4.3 Commission the Remote Serial link
5.7
Instructions
Scenarios 1 & 3 (Remote Detectors/Serial)…
Power up the Controller
Subscribe the RUs to the LUC/BRH at the LUC. Check
that all radio links are working (RLS command).
At the bottom of the belled pole, wire the bracket’s
cable (which will be connected to the RU on the mast).
Scenario 2 (TC12)…
30 –2–
LUC
31 –2–
LUC
6.5.1
Set up the Gateway or Network LUC for TC12.
6.5.2
32 –2–
LUC
6.5.3 Starting with the Gateway LUC, subscribe the LUCs.
33 –2–
LUC
667/HB/30400/000
-
-
Power up the Controller
Contact the Instation to ensure that all OTUs are
working correctly
Issue 6
Page 54
5.3
Belled Pole – Option for All Scenarios
Bracket
3400mm approx
Ground level
Mains cable
entering
via slot in pole
Planting Depth
Concrete
Figure 33 – Belled Pole Assembly – Planted
Note -
The planting depth must be 600 mm to cover the cable entry slot. Install
under direction from the Civil Engineer, dependent on the ground conditions.
When installing the pole, bear in mind that ladder access will be required to
the two bracket points at the top of the pole, as well as access to the door.
When the electricity board has installed the mains cable, connect the 24V
transformer. See 667/GA/30954/000 for cabling details.
The pole is delivered with the necessary equipment installed inside; there are
two variants, one with a detector card and one without.
667/HB/30400/000
Issue 6
Page 55
Figure 34 – Mains Unit without Detector (Not Fitted In Pole)
667/HB/30400/000
Issue 6
Page 56
5.3.1 Pole for mounting RU/RH
The base of the belled pole should be sealed to prevent the build up of gas
inside.
5.3.2 Pole for mounting Repeater
The base of the pole does not need sealing since gas can escape at the top.
5.3.3 Detector
The detector should be plugged into the factory fitted bracket inside the belled
pole, and connections made into the terminal block as shown in Figure 42 on
page 64.
667/HB/30400/000
Issue 6
Page 57
5.4
Local Unit Controller – All Scenarios
Connections to the front of the LUC are shown in Figure 30 and Figure 32 on
pages 51 and 52.
5.4.1 Detector Backplane Connections to LUC
Detector backplane connections are as follows:
Ref Terminal SmartLink LUC
Detector Card
SK1 Pin
1 TB1 1
2 TB1 2
CH 5 N/Closed
CH 5 N/Open
CH 1 Loop (1)
CH 1 Loop (2)
5a
6b
3 TB2 1
4 TB2 2
CH 6 N/Closed
CH 6 N/Open
CH 2 Loop (1)
CH 2 Loop (2)
12b
13a
5 TB3 1
6 TB3 2
CH 7 N/Closed
CH 7 N/Open
CH 3 Loop (1)
CH 3 Loop (2)
19a
20b
7 TB4 1
8 TB4 2
CH 8 N/Closed
CH 8 N/Open
CH 4 Loop (1)
CH 4 Loop (2)
26b
27a
9 TB5 1
10 TB5 2
CH 1 N/Closed
CH 1 N/Open
CH 1 N/Closed
CH 1 N/Open
1a
3a
11 TB5 3
12 TB5 4
CH 2 N/Closed
CH 2 N/Open
CH 2 N/Closed
CH 2 N/Open
8b
10b
13 TB5 5
14 TB5 6
CH 3 N/Closed
CH 3 N/Open
CH 3 N/Closed
CH 3 N/Open
15a
17a
15 TB5 7
16 TB5 8
CH 4 N/Closed
CH 4 N/Open
CH 4 N/Closed
CH 4 N/Open
22b
24b
17 TB5 9
18 TB5 10
( Reset )
Reset
29a
Relay commons Relay commons 2b,9a,16b,23a
19 TB5 11
20 TB5 12
DC in: 24 Volt
DC in: 0 Volt
24 Volt DC +
24 Volt DC -
30b
32b
21 TB5 13
22 TB5 14
-
Screen
Earth
14b
AC in: 24 Volt
AC in: 0 Volt
24 Volt AC
24 Volt AC
18b
21a
23 TB5 15
24 TB5 16
Figure 35 – LUC Backplane Connections
If 24V AC is used, the connection to Ref 24 must be connected to EARTH
at the transformer. This needs to be confirmed BEFORE the LUC is installed,
because it cannot be guaranteed at existing sites.
The 24V Supply (DC or AC) must come from the Detector Supply in the
Controller; do not use the OTU 24V supply.
For Controller Linking, use the N/Closed outputs, see Figure 2 on page 12.
667/HB/30400/000
Issue 6
Page 58
The LUC detector outputs can be toggled, in sequence, in order to test
operation and wiring to other external equipments, using the DOO handset
command (Reference section 7.2.4).
5.5
Line Interface Unit (LIU) – Scenario 2 (TC12)
The LIU sit alongside the LUC in the controller rack.
Connections between the fronts of the LIU and LUC should be made using
short ribbon cables (E and F) as follows:
Figure 36 – LUC to LIU Cable Connections
Note that in each case, the unused socket on the LIU is covered by the cable
from the LUC.
The LIU on the left is only needed with a Gateway LUC as it connects to the
telephone line to the Instation. This LIU must be fitted with a telephone line
cable and a black cover over part of board, as shown in Figure 19 on page 32.
The LIU on the right has the OTU’s telephone cable plugged into the back of
the LIU. Therefore this LIU is not fitted with a cover to allow access to the
white telephone socket on the back of the LIU, as shown in Figure 17 on page
30.
The LIU on the right can be omitted if the OTU has an RS232 daughter card.
In this case, the IDC Cable H connects the RS232 port on the OTU directly to
the “OTU” port on the LUC.
667/HB/30400/000
Issue 6
Page 59
5.5.1 LIU Switch Settings
The LIU switch settings are as follows. Their function is clearly marked on the
LIU circuit board and on the back of the LIU metal work.
There are individual switches for “2-wire” / “4-wire” and “600 ohms” / “High
Impedance”. The latter is located under the cover.
There are two groups of six switches. These set the mode and line levels, as
shown in the tables below…
Mode
CCITT V.23 M2
1200 BPS Half Duplex
CCITT V23 M2
1200 BPS Half Duplex with equalizer
CCITT V.23 M1
600 BPS Half Duplex
CCITT V.23 M2
1200 BPS Full Duplex
CCITT V.23 M2
1200 BPS Full Duplex with equalizer
CCITT V.23 M1
600 BPS Full Duplex
Switch Number
3
4
5
6
GMM
1
2
0
1
0
0
1
1
6
0
0
0
0
1
1
7
0
1
1
1
0
1
8
0
1
0
0
1
0
22
0
0
0
0
1
0
23
0
1
1
1
0
0
24
0 = Switch open 1 = Switch closed (ON)
1
2
Switch Number
3
4
0 dBm
1
0
0
-3 dBm
1
0
-6 dBm
0
-9 dBm
5
6
0
-
-
0
1
-
-
1
0
0
-
-
0
1
0
1
-
-
-13 dBm
0
0
0
0
-
-
-16 dBm
0
0
0
1
-
-
-42 dBm
-
-
-
-
0
0
-39 dBm
-
-
-
-
0
1
-33 dBm
-
-
-
-
1
0
Settings
for UK
Output
Power
Not permitted in UK
Figure 37 – Modem Mode Selection Switch – S3
Receive
Threshold
0 = Switch open 1 = Switch closed (ON)
Figure 38 – Modem Line Level Switch – S1
667/HB/30400/000
Issue 6
Page 60
“Any 2-wire or 4-wire to Instation” / “4-wire to Outstation”
There are also four closely mounted individual switches under the cover near
the telephone socket, which should all be set in the same position depending
on what the LIU is connected to and whether a 2- or 4-wire system is being
used.
Remember on the Gateway LUC that there could be two LIUs…
Gateway LUC Only: The LIU on the left (looking from the front) will be plugged
into the telephone line to the TC12 Instation and therefore its switches should
be set to “Any 2-wire or 4-wire to Instation”. This is the default position as
delivered from the factory since the switches are located under the cover.
Gateway or Network LUC: The LIU on the right (looking from the front) will be
connected to the OTU, therefore the switches need to be moved if a 4-wire
system is used to select the “4-wire to Outstation” position. If a 2-wire system
is used, the switches can remain in the “Any 2-wire or 4-wire to Instation”
position.
5.5.2 LIU Power Cable
Earth
Bonding
to Rack
Green
1
3 2
3-WAY
3.81mm PLUG
Slate
1
+ 0V 0V
3-WAY
3.81mm
HEADER
on LIU
White
Controller
Power
Distribution
0V
24V
Figure 39 – Cable G: LIU 24V Power Connections
5.5.3 LIU Telephone Cable Mounting
NOTE: The telephone cables to and from an LIU should only be loosely
cable-tied in place, so that they are easy to release.
In the case of an Instation LIU, it allows its telephone cable to be unplugged
from the telephone socket in the cabinet, so that the LIU complete with its
telephone cable can be removed and replaced.
In the case of an OTU plugged into an LIU, the OTU’s telephone cable can be
unplugged from the LIU, allowing the OTU and its telephone cable to be
removed and replaced.
667/HB/30400/000
Issue 6
Page 61
5.6
Radio Head - All Scenarios
The Radio Head is delivered fully assembled with the omni directional
antenna attached inside the enclosure. If a directional antenna is needed, see
section 5.10 for details.
The cable emerging from the bottom of the enclosure should be fed through
the mast ready to plug into the socket on the bracket.
For reference, the cables are connected to the RH PCB PL1 to SK1.
LUC
NRH or BRH
DCD / 24V
GND
RXD N
RXD P
CTS N
CTS P
TXD N
TXD P
RTS N
RTS P
MARK PLUG "NRH" OR "BRH"
1
2
3
4
5
6
7
8
9
10
Terminal
Block
BROWN
BROWN
TAN
TAN
RED
RED
TAN
TAN
ORANGE
ORANGE
TAN
TAN
YELLOW
YELLOW
TAN
TAN
GREEN
GREEN
TAN
TAN
1
2
3
4
5
6
7
8
9
10
11
CABLE A:
5 PAIR TWISTED RIBBON CABLE
Detector
Power
Supply
+24V
SLATE
0V
WHITE
12
MARK TERMINAL
BLOCK WITH
"NRH" OR "BRH"
NO CONNECTION
NO CONNECTION
BROWN / WHITE
WHITE / BROWN
ORANGE / WHITE
WHITE / ORANGE
BLUE / WHITE
WHITE / BLUE
GREEN / WHITE
WHITE / GREEN
SLATE / WHITE
WHITE / SLATE
CABLE C:
ARMOURED CABLE TO
POLE WITH NRH OR BRH
Figure 40 – Cables A & C: Radio Head Cables
Note that the power on pin 1 (of the BRH port on the LUC) should only be
used by the BRH Installation Support Kit, see section 6.2. Once installed, a
BRH must obtain its power directly from 24V Detector Supply and not through
the LUC.
667/HB/30400/000
Issue 6
Page 62
5.7
Remote Unit – Scenarios 1 & 3 (Remote Detectors/Serial)
The Remote Unit is usually mounted on a new belled pole and permanently
connected to the power source and detector equipment.
RU
B
B
BB
CN
TB
667/1/30782/001 Twisted pairs cable, 4m, 10 pairs, foil screened
667/1/30783/101 Twisted pairs cable, 5m, 10 pairs, foil screened
Connector 23-way Plug housing, crimp, clamp and bracket
Terminal Block
CN
BB
New Belled
Pole
TB1
TB2
ST4R
TRANS
FORMER
Figure 41 – Remote Unit Wiring Summary
RU mounted on Belled Pole (667/1/30969/000)
Mains Distribution Unit (667/1/30954/001)
The Remote Unit is delivered fully assembled with the omni directional
antenna attached inside the enclosure. If a directional antenna is needed, see
section 5.10 for details.
The cable emerging from the enclosure should be fed through the mast ready
to plug into the socket on the bracket.
For reference, the cables are connected to the RU PCB as follows:
PL1 to SK1
PL2 to SK2
667/HB/30400/000
Issue 6
Page 63
RU
Wire Colour
Connector
Description
(Base / Band)
SK1 1
24 V AC
GREY /
SK1 2
0V
/ GREY
SK1 3
Detector Input 1 BROWN /
SK1 4
Detector Input 2
/ BROWN
SK1 5
Detector Input 3 ORANGE /
SK1 6
Detector Input 4
/ ORANGE
SK1 7
Detector Input 5
BLUE /
SK1 8
Detector Input 6
/ BLUE
SK1 9
Detector Input 7 GREEN /
SK1 10
Detector Input 8
/ GREEN
SK2 1
24 V AC
GREY / RED
SK2 2
0V
RED / GREY
SK2 3
RXD from RU
BROWN / RED
SK2 4
TXD to RU
RED / BROWN
SK2 5
DTR to RU
ORANGE / RED
SK2 6
GND
RED / ORANGE
SK2 7
DSR from RU
BLUE / RED
SK2 8
RTS to RU
RED / BLUE
SK2 9
CTS from RU
GREEN / RED
SK2 10
N/C
RED / GREEN
Detector
Backplane
Description
Wire colour*
9
Output 1 N/C
BLUE
11
Output 2 N/C
GREEN
13
Output 3 N/C
ORANGE
15
Output 4 N/C
YELLOW
18
Output Common
23
24 V AC
GREY
24
0V
Terminal
Block
To
TB1 1
Transformer
TB1 2
Transformer
TB1 3
Detector
TB1 4
Backplane
TB1 5
Connection
TB1 6
(Below)
TB1 7
(Also see
TB1 8
Section 3.4.1
TB1 9
on page 36)
TB1 10
TB2 1
TB2 2
TB2 3
TB2 4
TB2 5
TB2 6
TB2 7
TB2 8
TB2 9
TB2 10
-
To
Required
RU Input(s)
(See Above)
24
Transformer
Transformer
Figure 42 – Remote Unit Wiring Details
•
* Wire colour selected from 667/1/03887/002 (which comes with Detector Backplane kit)
As with the LUC (see Figure 35 on page 58), the 0V connections to the 24V
AC Transformer must be EARTHED at the Transformer.
667/HB/30400/000
Issue 6
Page 64
5.8
Pole Cap Extension Kit – Option for all Scenarios
Unpack and dismantle the pole cap extension kit and fit the terminal block
assembly to the pole cap with the nuts, bolts and washers supplied.
Connect the earth cable from the terminal block assembly to the earth
connector in the pole.
Secure all cable(s) to the slots on the terminal block assembly using the CET
connector(s) and worm drive hose clip(s).
Note that a suitable allowance must be made for the amount of cable at the
bottom of the pole.
667/HB/30400/000
Issue 6
Page 65
5.9
Mast Fixing – All Scenarios
Figure 43 – Bracket Assembly Kit
Figure 44 – Bracket Fitting Side View
5.9.1 Mount the Bracket
The plastic plugs should be pushed out of the most appropriate top fixing
point on the pole as shown in Figure 44.
667/HB/30400/000
Issue 6
Page 66
Mount the bracket onto the pole using the top fixing position on the pole using
the two M8 fixings provided (do not use a U-bolt). Feed the cable from the
connector on the bracket (if fitted) through the larger hole in the traffic pole.
The bracket can be fitted either way up. This allows the mast to rise from
either side of the pole and pole cap to avoid any equipment already mounted
on the same pole.
Fit the normal traffic signal spacer between the curved pole and flat bracket.
Figure 45 – Bracket Fitting Either Way Up
5.9.2 Connect Bracket Connections to Pole Cap (Not Belled Pole)
Note that a pole cap is not used on a belled pole. Instead, the cable from the
bracket is terminated at the bottom of the belled pole.
As an overview, the complete wiring is shown in:
• Figure 29 (Page 51) for a Base Radio Head
• Figure 31 (Page 52) for a Network Radio Head
• Figure 41 (Page 63) for a Remote Unit
• Figure 48 (Page 73) for a Repeater
If a pole cap extension kit is required, fit it as described in section 5.8.
Make sure that the cable is fed through the entry point in the pole to be
connected to the terminal blocks. Cut off any excess cable and wire into the
terminal block in the pole cap.
SmartLink terminations in the pole cap between the cable from the bracket
and the armoured cable from the LUC in the controller cabinet should be
connected matching colour for colour throughout. For a Radio Head, only 5
pairs (10 wires) are used. For a Remote Unit, 10 pairs (20 wires) may be used
if both Remote Detectors and Remote Serial are required. However, only the
first 5 pairs (10 wires) are fitted for Remote Detector applications.
Reattach the pole cap.
667/HB/30400/000
Issue 6
Page 67
5.10
Antennas – All Scenarios
Refer to section 3.5, on page 38 for more general information on the
antennas. Antenna installation instructions will depend on the antenna type.
These are detailed below.
5.10.1 Omni-Directional Antenna
These aerials are factory fitted inside the RU/RH box. No further installation
details are required.
5.10.2 Directional Antenna
If not already assembled, assemble the antenna bracket and then attach the
directional antenna to the bracket.
Note that the instructions that come with the antenna bracket assembly show
the antenna cable fed up between the back of the antenna and the ‘plate’ on
the bracket that holds the antenna. This is not required for SmartLink. A fully
assembled antenna is shown in Figure 51 on page 76.
Connect the antenna on its bracket to the mast. Each antenna bracket is held
in place with two jubilee type clips that should be tightened until secure. A
hole is drilled in the mast for the antenna cable to be fed through. Figure 51
shows an antenna fitted to a mast.
Open the Remote Unit / Radio Head / Repeater enclosure.
Unscrew the omni-directional antenna.
Attach the antenna cable from the directional antenna to this point in the
enclosure to complete the connection between the radio and the antenna.
Cut away the thinned sections in the bottom of both halves of the
enclosure (near the main cable clamp), which allows the antenna cable
to exit the casing. Failure to comply with this procedure will result in
permanent damage to the antenna cable.
To hold the directional antenna cable in place, feed it around the top of the
head. Push the cable between the plastic supports for the omni-directional
antenna’s plate and the plastic shaft for one of the screws that hold the two
halves of head together.
Note, antennas mounted on a single pole, e.g. repeater nodes, must be
separated by a vertical distance of at least 50cm.
Figure 50 on page 75 shows an open Repeater with its directional antenna
cables connected.
If there is a difference in height between sites, the most convenient way to
align the antenna is while the mast is attached to the bracket in its lowered
position, so that the directional antenna is approximately level with the top of
the pole. Angle the antenna so that it points to the top of the next pole.
Tighten the screw on the articulated arm so that the angle is fixed. There is a
signal spread of about 10°.
667/HB/30400/000
Issue 6
Page 68
Confirm, by eye, that each directional antenna is pointing in the correct
direction, prior to leaving site.
5.11
Attach Unit to the Mast - All Scenarios
If directional antennas are to be fitted with the Unit, then before the Unit is
attached to the mast, the antennas need to be fitted, as described in section
5.10.
Note that Remote Units and Repeaters need to be commissioned before they
are installed on their masts as described in Section 6 – Commissioning, which
starts on page 77.
Two screws should be fitted into the lower holes near the top of the Mast and
left slightly proud (if not already fitted).
Fit the Remote Unit or Radio Head onto the Mast, resting the unit on the
screws so that the screw holes in the enclosure line up with the holes in the
Mast.
Secure the Unit onto the Mast using the two screws provided.
667/HB/30400/000
Issue 6
Page 69
5.12
Raising the Mast – All Scenarios
To raise or lower the mast requires the use of a ladder and working at heights.
Refer to the Safety Warning on page 2.
In all cases, the Mast is attached to the pole using a purpose built Bracket.
Before raising the mast, the Bracket must be correctly attached to the Traffic
Signal Pole or Belled Pole as described in section 5.9, which starts on page
66.
In addition, before the Mast is raised, the unit should be attached to the top of
the Mast as described in section 5.11, on page 69.
5.12.1 Rope
To raise or lower the mast, use the rope shown in Figure 46 below. This
device allows the mast to be raised and lowered safely.
Figure 46 – Rope
5.12.2 Mast Fixings
The Mast is held on to the Bracket using two straps.
On the bracket (see Figure 43 on page 66) are two slots and two studs.
Each strap T’s into a slot in the bracket on one side of the Mast, not shown.
The other end of the strap is then secured on to the stud on the other side, as
shown below…
667/HB/30400/000
Issue 6
Page 70
Figure 47 – Mast and Bracket
Two plastic protectors are provided in the bracket assembly, one for each
stud.
The plastic protector should be fed over the stud, through the hole in the
strap.
The nut and washer should then be loosely fitted to the stud.
The plastic protector prevents the strap from damaging the thread on the stud
as the nut is tightened.
667/HB/30400/000
Issue 6
Page 71
5.12.3 Raising the Mast
1. Attach the end of the chain to the hole at the bottom of the mast. Place the
clamp around the mast just below the Remote Unit or Radio Head and any
directional antennae.
2. Hold the Mast up and hook the clamp over the top edge of the bracket on the
pole.
3. Climb the ladder and fix the bracket’s straps around the mast (as detailed in
section 5.12.2 above). Only do up the nuts loosely to allow the mast to slide.
4. Hook part of the chain onto the top corner of the bracket
5. With the chain now taking the weight of the mast, and the mast now held
against the bracket by the straps, gradually raise the mast, taking up the slack
on the chain every 30cm or so and attaching it to the top corner of the bracket
to keep the mast stable and secure. Each time the mast is raised, lower the
clamp back to the top edge of the bracket.
6. When the mast is at the desired height, as shown in Figure 44 on page 66,
tighten the nuts on the bracket.
7. Plug the RU/RH cable into the socket on the bracket assembly. Push any
excess cable back up the mast and cable-tie the cable to the outside of the
mast as shown in Figure 44. For a Repeater, see section 5.13 on page 73.
8. Remove the clamp and chain and retain for future use.
5.12.4 Lowering the Mast
1. Climb the ladder and unplug the RU/RH cable from the socket on the bracket
assembly.
2. Attach the end of the chain to the hole at the bottom of the mast, and hook
part of the chain onto the top corner of the bracket so that it is tight.
3. Place the clamp around the mast so that it is resting on the top edge of the
bracket, with the two metal posts of the clamp on the other side of the bracket
plate to the mast.
4. With the chain and clamp now taking the weight of the mast, loosen the straps
on the bracket, BUT DO NOT REMOVE THEM AT THIS STAGE. Leave the
straps loose and they will continue to hold the mast against the bracket.
5. Reposition the clamp higher up the mast. Then, taking the weight of the mast,
remove the chain from the top corner of the bracket, lower the mast until the
clamp rests on the top edge of the bracket again, and hook part of the chain
back onto the top corner of the bracket.
6. Repeat the above step until the mast is as low as it will go and the bracket is
resting on the top edge of the bracket again.
7. Remove the straps from around the mast.
8. Unhook the chain from the top corner of the bracket.
9. Descend the ladder.
10. Lift the mast and the clamp off the bracket.
11. Remove the clamp and chain and retain for future use.
667/HB/30400/000
Issue 6
Page 72
5.13
Repeater Node – Option for all Scenarios
To provide a Repeater function, two Radio Head circuit boards are linked via
their RS485 connections and deployed to provide a transparent transit node.
The two Radio Head circuit boards are fitted into one enclosure and supplied
with a belled pole, directional antenna and all necessary fittings.
Cable 1
Repeater
Cable 2
Cable 1 667/1/30964/000 Head to head cable
Cable 2 667/1/30964/001 Bullet connectors both ends
Cable 3 667/1/30964/002 Bullet connectors one end
Bullet
connectors
Cable 3
New Belled
Pole
24V
AC
Figure 48 – Cables 1, 2 & 3: Repeater Wiring Summary
Erect the belled pole as described in section 5.3, starting on page 55.
667/HB/30400/000
Issue 6
Page 73
5.13.1 Repeater Bracket
Install the bracket (667/1/30967/000) onto the pole using the M8 fixings
provided, the same as a normal bracket (section 5.9.1 on page 66).
However, note that a Repeater bracket does not include the round connector
and cable. In this case, the cable from the Repeater is just fed through the
hole in the bracket in to the belled pole.
Figure 49 – Repeater Bracket
The bare ends of Cable 3 should be connected to the 24V transformer as
follows:
RED 24V
BLUE 0V
The end with bullet connectors should be fed through the pole entry point in
the bracket to hang outside until ready for connection.
5.13.2 Repeater Assembly
If two directional antennae are supplied, the directional antennae and Radio
Head circuit boards need to be clearly marked ‘N’ (Network Repeater) or ‘B’
(Base Repeater).
Mark the underside of each antenna so that these will be clearly visible from
the ground when the mast is raised. In addition, mark the free end of the
antenna cable so that the correct antenna can be connected to the correct
Radio Head circuit board (which should also be marked).
If the Repeater is supplied with one Radio Head already fitted with an omnidirectional, then only one directional antenna is to be used and it should be
connected to the other Radio Head circuit board. In this case, the Radio Head
circuit board with the omni-directional antenna will be subscribed as the Base
Repeater. The Radio Head circuit board with the directional antenna will be
subscribed as the Network Repeater.
Attach the directional antenna(s) to the mast and feed the antenna cables up
through the hole(s) drilled in the mast to the top (see section 5.10).
The enclosure should then be unscrewed and the halves separated, leaving
one board in each half.
667/HB/30400/000
Issue 6
Page 74
The cable connecting the Radio Heads (cable 1 in Figure 48) is supplied
already plugged into the sockets on the PCBs; leave this attached.
Figure 50 – Repeater Unit (Open)
Cable 2 should have the bullet connectors. Connect these to the free bullet
connectors on Cable 1, linking GREY to RED (24V) and
to BLUE (0V)
as shown in Figure 50.
The rest of Cable 2 is then fed down through the mast and out of the bottom,
ready to connect to Cable 3.
Screw the enclosure together and then secure the enclosure to the mast
using the screws provided as normal (section 5.11).
It will be necessary to pull the slack in the antenna cable(s) out of the mast as
the enclosure is lowered on to the mast. This slack should then be fed
downward, back in to the mast after the enclosure has been secured to the
top.
667/HB/30400/000
Issue 6
Page 75
The complete Repeater mast assembly is shown below.
Figure 51 – Repeater Unit on Mast
5.13.3 Erecting the Repeater
Raise the mast using the clamp and chain as normal (section 5.12).
Once the mast has been raised, fully tighten the fixings to hold the mast in
place, making sure that the directional antennas are correctly orientated
towards their respective units. If the Repeater is only fitted with one directional
antenna, then it will be the Network Repeater.
The Network Repeater marked ‘N’ should point to the Base Radio Head.
The Base Repeater marked ‘B’ should point to the Network Radio Head or
Remote Unit.
Connect the bullet connectors between Cable 2 and Cable 3 (Red to Red,
Blue to Blue) and feed Cable 3 and the remaining slack in Cable 2 into the
belled pole, as shown in Figure 48 on page 73.
667/HB/30400/000
Issue 6
Page 76
Section 6 – CommissioningError! Bookmark not defined.
6.1
General
Commissioning involves configuring the equipment to function as required,
and ‘subscribing’ the required radios to each other.
The commissioning procedure for each of the scenarios described in section
2.2 differs in some detail. Where the instructions are specific to a particular
scenario, this is shown by putting Scenario 1, Scenario 2 or Scenario 3 next to
the appropriate section.
Commissioning may be done before, during or after installation.
The equipment can be commissioned in the depot before it is installed.
During installation, the equipment can be installed at the convenient step
identified in the Order of Installation (see section 5.2).
Once installed, it may be necessary to re-commission and re-subscribe parts
of the installation after equipment has been replaced for example. Section 6.3
identifies which units need to be re-subscribed after a part is replaced.
Note that Remote Units and Repeaters cannot be commissioned on their
masts. If already installed, they need to be brought down off their masts to be
commissioned or re-commissioned.
When initially installing the equipment, the ‘Order of Installation’ (section 5.2
which starts on page 53) identifies the best time to commission the units
during the installation.
667/HB/30400/000
Issue 6
Page 77
6.2
Installation Support Kit
This kit, consisting of a number of cables, allows a set of equipment to be
subscribed in one place before installation. The kit also includes an LUC for
subscribing a Repeater, see section 6.6.
6.2.1 Subscription Cable – BRH
This 10-way IDC cable allows a Base Radio Head to be plugged directly into
the BRH port on a LUC.
It provides both communications and power down the one cable since the
LUC provides power for subscription on its BRH port.
Base Radio
Head
RTS_R1_P
10
RTS_R1_N
9
TXD_R1_P
8
TXD_R1_N
7
CTS_R1_P
6
CTS_R1_N
5
RXD_R1_P
4
RXD_R1_N
3
DSG
2
24V_IN
1
Local Unit
Controller
CABLE:
667/1/30977/000 3m
TAN
TAN
GREEN
GREEN
TAN
TAN
YELLOW
YELLOW
TAN
TAN
ORANGE
ORANGE
TAN
TAN
RED
RED
TAN
TAN
BROWN
BROWN
10
RTS_R1_P
9
RTS_R1_N
8
TXD_R1_P
7
TXD_R1_N
6
CTS_R1_P
5
CTS_R1_N
4
RXD_R1_P
3
RXD_R1_N
2
24V_AC2
1
24V_AC1
10-WAY IDC SOCKET
(con: 508/4/26119/000
strain relief: 508/4/26119/030)
Figure 52 – Subscription Cable – LUC to BRH
667/HB/30400/000
Issue 6
Page 78
6.2.2 Subscription Cable – NRH or RU
This 10-way IDC cable allows a Network Radio Head to be plugged directly
into the NRH port on a LUC.
Since the LUC does not provide power on this connector, it provides a
separate power socket on its front panel just below the NRH port for this
purpose, see Figure 8 on page 22. The cable includes a power plug that can
be plugged in to this socket on the LUC.
10-WAY IDC SOCKET
(con: 508/4/26119/000
strain relief: 508/4/26119/030)
Network
Radio Head
RTS_R1_P
10
RTS_R1_N
9
TXD_R1_P
8
TXD_R1_N
7
CTS_R1_P
6
CTS_R1_N
5
RXD_R1_P
4
RXD_R1_N
3
24V_AC2
2
24V_AC1
1
Local Unit
Controller
TAN
TAN
GREEN
GREEN
TAN
TAN
YELLOW
YELLOW
TAN
TAN
ORANGE
10
RTS_R1_P
9
RTS_R1_N
8
TXD_R1_P
7
TXD_R1_N
6
CTS_R1_P
5
CTS_R1_N
4
RXD_R1_P
3
RXD_R1_N
ORANGE
TAN
TAN
RED
RED
TAN
TAN
BROWN
BROWN
NC 2
DSG
NC 1
DCD_R1
-
CABLE:
667/1/30978/000 3m
+
1.3mm Power Plug
(531/4/03196/000)
Figure 53 – Subscription Cable – LUC to NRH (or RU)
This same cable can also be used to power an RU during subscription:
¾ DO NOT insert the IDC plug in to the LUC.
¾ Insert the NRH IDC plug in to either socket of the RU.
¾ Insert the power plug in to the front of the LUC.
667/HB/30400/000
Issue 6
Page 79
6.3
Re-Subscription Procedure
When a unit is replaced in an existing SmartLink system, re-commissioning
procedures may need to be carried out as follows:
Re-enter all the configuration data from the Configuration Sheet in
the cabinet (except the SPN PIN number). Then, enter the
following commands:
RMM B=C
LUC
SPN=<PIN> (this MUST be the original PIN number, not the new
LUC serial number)
RLS <A,B,C,D>=A (to activate the radio links)
BUP
Re-subscription is not required since the radio modules in the
BRH, NRH and/or RUs have not been changed.
LIU
Set-up switches as required (5.5.1). No re-subscription required.
BRH
All equipment needs to be re-subscribed to the new BRH.
NRH
Subscribe the new equipment to the LUC/BRH using the existing
SPN number, otherwise units already subscribed to that LUC/BRH
would fail to reconnect.
RU
Repeater Subscribe the Repeater as normal, see section 6.6.
667/HB/30400/000
Issue 6
Page 80
6.4
RU Commissioning – Scenarios 1 & 3 (Remote Detectors/Serial)
6.4.1 LUC / RU Subscription
If a Repeater is to be used, refer to section 6.6.
At the LUC, configure its Base Radio Head…
RMM B=C
Put the BRH into configuration mode
RMT B=F
BRH is a ‘fixed terminal’
RDM B=P
BRH is to use protocol mode
RAT B=2
BRH is to use external antenna
RCL B=OFF
BRH is not to use connectionless links
RSP B=8,N,1,NONE
BRH Serial Port to use 8 bits, no parity, 1 stop bit
and not RTSCTS flow control
HLQ B=1
Adjust BRH window time to allow longer links
At the LUC, enable on-air subscription in the Base Radio Head…
SPN=<PIN>
Enter a personal identification number (PIN) of
eight numerical characters in length. Use the
unique 8-digit STC serial number on the LUC.
Write this number down on the Configuration
Sheet (Section 12) for use at the Remote Units.
ONS ON
Activate the on-air subscription function
Bring the Remote Unit (RU) to the LUC. Power the RU from the LUC using
the subscription cable, shown in section 6.2.2. Connect the power plug into
the front of the LUC and the other end of the cable into either socket of the
RU. Do not plug the other IDC plug into the LUC. Plug a handset into the RU
and begin the subscription process.
RMM=C
RMT=P
RDM=T
RAT=2
RCL=OFF
RSP=8,N,1,NONE
ONS <PIN>
RRN
RMM=A
BUP
667/HB/30400/000
Put the Radio into configuration mode
Radio is a ‘portable terminal’
Radio is to use transparent mode
Radio is to external antenna
Radio is not to use connectionless links
Radio Serial Port to use 8 bits, no parity, 1 stop bit
Subscribe the Remote Unit radio module to the
Local Unit’s Base Radio Head using the SPN
number entered at the Local Unit.
Retrieve the radio numbers from the Remote Unit
radio module
Write these numbers down on the Configuration
Sheet for use for use at the Local Unit Controller
Return the Radio to active mode
Backup configuration data into flash memory
Issue 6
Page 81
If required, repeat the above on each Remote Unit.
Returning to the LUC, switch off on-air subscription…
ONS OFF
Deactivate the on-air subscription function
Configure each Remote Unit link at the LUC…
LIT <A\B\C\D>=R
Link is to an RU
LRN <A\B\C\D>=<RRN> Associate one of the four links with the radio
numbers retrieved from the Remote Unit.
Enter the two numbers retrieved using RRN on
one line separated by a space.
Now activate the Radio links…
RLS <A\B\C\D>=A
Activate the radio link. Wait for the command to
confirm the link is active before proceeding.
Repeat the RLS command for all other links that need to be enabled since all
links were disabled when RMM B=C was entered!
BUP
Backup configuration data into flash memory.
Remember!
If the above procedure has just been used to subscribe the ‘Base Repeater’ to
the Remote Unit, then the Base Repeater must be put in to Transparent Mode
using the RDM handset command after subscription is complete. See section
6.6.2 on page 89.
667/HB/30400/000
Issue 6
Page 82
6.4.2 Remote Detector Set-up – Scenario 1 (Remote Detectors)
Once one or more RU links are subscribed and active (see section 6.4.1), the
remote detector facility can be enabled as follows:
All commands are entered at the LUC
RSA <1-8>=<A\B\C\D>
Configure which RU input (link A, B, C, or D)
controls each LUC output (1-8).
DFT=<seconds>
Configure how many seconds of lost
communications cause a link to enter DFM, i.e.
outputs forced active to indicate vehicle present.
DFA=<N, 1-254, or P>
Configure how the LUC is to react after a DFM trip –
how many minutes to hold the outputs active so that
the Controller’s or OTU’s DFM facility logs a fault for
example.
LIT <A\B\C\D>=R
Link is to an RU.
RSI <A\B\C\D>=A
Activate the remote sensor link.
BUP
Use the LEDs on the front of the LUC to confirm correct operation of each
detector output, see section 3.1.2 on page 24.
NB: Press and hold the ‘LED Enable’ button for 3 seconds to reset the DFM
facility and allow the outputs to return to normal operation.
6.4.3 Remote Serial Link – Scenario 3 (Remote Serial)
Once at least one RU link is subscribed and active (see section 6.4.1), the
remote serial link facility can be enabled as follows:
All commands, except LIT and RDL, need to be entered at both the LUC and
RU, including BUP.
SLB R=<baud rate>
Set up the remote serial port baud rate
SLW R=<7 or 8>
Set up the remote serial port word size
SLP R E=<E or D>
Set up the remote serial port parity (enable/disable)
SLP R T=<O or E>
Set up the remote serial port parity (odd/even)
SLS R=<1,1.5, 2>
Set up the remote serial port stop bits
SLH R=<0 or 1>
Disable (0) or Enable (1) hardware handshaking
LIT <A\B\C\D>=R
Link is to an RU (at the LUC only)
RDL=<A\B\C\D>=<A
or D>
Enable Remote Data on the appropriate link
BUP
667/HB/30400/000
Issue 6
Page 83
6.5
TC12 Commissioning – Scenario 2 (TC12)
6.5.1 TC12 Configuration Set-Up – Gateway LUC
Before following the instructions below, make sure that the switch settings on
the LIU have been set up as described in section 5.5.1.
Convert the NRH Port on the LUC for the TC12 LIU:
LUT=3
Gateway LUC
SLB N=A
1200 baud
NSC C=1
Ensure transmission waits for CTS
NSC R=0
Disable auto RTS function
Either convert the OTU Port on the LUC for the TC12 LIU (default):
OSC C=1
OSC R=0
GRX=0
Receive is to check for Carrier Detect
Alternatively, convert the OTU Port for direct RS232 connection to OTU:
OSC C=0
Transmission should not wait for CTS
OSC R=0
GRX=1
Receive is not to check for Carrier Detect
Set-up the TC12 Configuration Data the same as the OTUs:
GMM=<Modem Mode>
GNO=<Number of OTUs>
GCW <OTU>=<Number of Control Words>
GRW <OTU>=<Number of Reply Words>
Repeat GCW and GRW for every OTU on the telephone line, as you
would do on an OTU, e.g. GCW 0=2, GCW 1=2, etc.
GOE=1 (Enable transmission back to TC12 Instation when
configuration has been set up correctly)
NB: “GAD=<OTU Number>” is not required in the LUC
BUP
Check that the OTU “TX Confirm” LED is lit, and that there are no
communications problems at the Instation.
667/HB/30400/000
Issue 6
Page 84
6.5.2 TC12 Configuration Set-Up – Network LUC
Ensure the NRH port on the LUC is correct:
LUT=4
Network LUC
SLB N=H
115200 baud
NSC C=0
NSC R=0
Either convert the OTU Port on the LUC for the TC12 LIU (default):
OSC C=1
OSC R=0
GRX=0
Receive is to check for Carrier Detect
Alternatively, convert the OTU Port for direct RS232 connection to OTU:
OSC C=0
OSC R=0
GRX=1
Receive is not to check for Carrier Detect
Note that the Network LUC does not need the number of OTUs or the number
of control and reply words configuring.
BUP
667/HB/30400/000
Issue 6
Page 85
6.5.3 LUC / LUC Subscription
Before following the instructions below, make sure that the switch settings
have been set up as described in section 5.5.1, and that the set-up as
described in sections 6.5.1 and 6.5.2 has been carried out.
If a Repeater is to be used, refer to section 6.6.
At the Gateway LUC (or Network LUC closer to the Gateway LUC), i.e. the
‘Higher’ LUC, configure its Base Radio Head…
RMM B=C
RMT B=F
BRH is a ‘fixed terminal’
RDM B=P
BRH is to use protocol mode
RAT B=2
BRH is to use external antenna
RCL B=OFF
BRH is not to use connectionless links
RSP B=8,N,1,NONE
BRH Serial Port is to use 8 bits, no parity, 1 stop
bit and not RTSCTS flow control
HLQ B=1
Adjust BRH window time to allow longer links
Enable on-air subscription in the Base Radio Head…
SPN=<PIN>
Enter a personal identification number (PIN) of
eight numerical characters in length. Use the
unique 8-digit STC serial number on the LUC.
Write this number down on the Configuration
Sheet (Section 12) for use at the NRH/LUC.
ONS ON
Activate the on-air subscription function
Now subscribe each of the Network LUC/NRHs…
RMM N=C
Put the NRH into configuration mode
RMT N=P
NRH is a portable terminal
RDM N=T
NRH is to use transparent mode
RAT N=2
NRH is to external antenna
RCL N=OFF
NRH is not to use connectionless links
RSP N=8,N,1,NONE
Radio Serial Port to use 8 bits, no parity, 1 stop bit
ONS <PIN>
Subscribe the NRH radio module to the Local
Unit’s Base Radio Head using the SPN number
entered at the Gateway (or ‘Higher’ LUC)
RRN N
Retrieve the radio numbers from the NRH.
Write these numbers down on the Configuration
Sheet for use for use at the BRH/LUC.
RMM N=A
Return the Radio to active mode
BUP
667/HB/30400/000
Issue 6
Page 86
Returning to the Gateway (or ‘Higher’ Network) LUC, switch off on-air
subscription…
ONS OFF
Deactivate the on-air subscription function
Now configure each TC12 Network Link…
LIT <A\B\C\D>=N
Link is a TC12 Network link
However, if this procedure is being followed to
subscribe a Network Repeater to this BRH, and
this Repeater will eventually connect an RU to this
BRH, set the Link Type to ‘R’.
LRN <A\B\C\D>=<RRN>
Associate one of the four links with the radio
numbers retrieved from the NRHs.
Enter the two numbers retrieved using RRN on
one line separated by a space.
Now activate the Radio links…
RLS <A\B\C\D>=A
Activate the radio link. Wait for the command to
confirm the link is active before proceeding.
Repeat the RLS command for all other links that need to be enabled since all
links were disabled when RMM B=C was entered!
BUP
Check that the replies to each OTU are being correctly received at the
Instation.
Remember!
If the above procedure has just been used to subscribe a ‘Base Repeater’ to
the NRH of a Network LUC, then the Base Repeater must be put in to
Transparent Mode using the RDM handset command after subscription is
complete. See section 6.6.3 on page 90.
667/HB/30400/000
Issue 6
Page 87
6.6
Repeater Node
A Repeater is situated between a BRH and either a NRH on a Network LUC
or a Remote Unit.
A Repeater is used to replace the one long or awkward radio link with two
shorter radio links. The radios in the middle, i.e. those in the Repeater, just
pass data transparently from one link to the other.
A Repeater node comprises two halves – two identical Radio Head circuit
boards. One half is configured as the ‘Network Repeater’, which
communicates with the BRH. The other half is configured as the ‘Base
Repeater’, which communicates with NRH or Remote Unit.
Repeater
RU
BR
OR
NR
BRH
NRH
LUC
LUC
Figure 54 – Repeater Arrangement
Normally the end-point, i.e. RU or NRH, would be subscribed to the BRH.
However, in this case, the ‘Network Repeater’ must be subscribed to the
BRH, and the RU or NRH must be subscribed to the ‘Base Repeater’, as
though it were a normal Base Radio Head.
The Radio Head circuit boards forming the Repeater are then linked with an
RS485 crossover cable (667/1/30964/000) and the power applied.
For the complete Instation details, see section 5.13, which starts on page 73.
6.6.1 Equipment for Subscribing a Repeater
1 x Radio Head in the Repeater marked ‘B’, the ‘Base Repeater’
1 x Radio Head in the Repeater marked ‘N’, the ‘Network Repeater’
1 x Normal BRH and LUC
1 x Remote Unit or Network LUC and its NRH
1 x LUC used as a subscription aide
1 x BRH Subscription Cable (see section 6.2.1)
1 x NRH Subscription Cable (see section 6.2.2)
667/HB/30400/000
Issue 6
Page 88
6.6.2 Subscription Steps for a RU Repeater Link
If not already done, mark the two Radio Head halves of the Repeater with a
‘B’ and an ‘N’ (as described in the Installation section 5.13.2 on page 74).
Connect the Base Repeater to the BRH port of the Subscription LUC using
the BRH Subscription Cable (6.2.1).
Subscribe the RU to the Base Repeater using the normal LUC/RU
subscription procedure (6.4.1). Use Link A.
Once subscription is successful, switch the Base Repeater from Protocol
Mode to Transparent Mode using the commands:
RMM B=C
RDM B=T
RLS A=A
Put the BRH back into active mode
(this will fail returning RLS:ERROR)
Connect the Network Repeater to the NRH port of the Subscription LUC using
the NRH Subscription Cable (6.2.2).
Subscribe the Network Repeater to the LUC/BRH using the normal LUC/LUC
subscription procedure (6.5.3), but at the end, set the Link Type (LIT) to ‘R’
rather than ‘N’ since there will be an RU at the end of this link through the
Repeater.
LIT <A\B\C\D>=R
Link is (eventually) to an RU
Now the two parts of the Repeater can be connected together and the link
from the LUC/BRH to the RU, through the Repeater should start as normal.
667/HB/30400/000
Issue 6
Page 89
6.6.3 Subscription Steps for a Network LUC Link
If not already done, mark the two Radio Head halves of the Repeater with a
‘B’ and an ‘N’ (as described in the Installation section 5.13.2 on page 74).
At the (‘Lower’) Network LUC, connect its NRH as normal.
Connect the Base Repeater to the BRH port of the Subscription LUC using
the BRH Subscription Cable (6.2.1).
Subscribe the NRH to the Base Repeater using the normal LUC/LUC
subscription procedure (6.5.3). Use Link A.
Once subscription is successful, switch the Base Repeater from Protocol
Mode to Transparent Mode using the commands:
RMM B=C
RDM B=T
RLS A=A
Put the BRH back into active mode
(this will fail returning RLS:ERROR)
At the Gateway (or Higher Network) LUC, connect its BRH as normal.
Connect the Network Repeater to the NRH port of the Subscription LUC using
the NRH Subscription Cable (6.2.2).
Subscribe the Network Repeater to the LUC/BRH using the normal LUC/LUC
subscription procedure (6.5.3).
Now the two parts of the Repeater can be connected together and the link
from the LUC/BRH to the LUC/NRH, through the Repeater should start as
normal.
667/HB/30400/000
Issue 6
Page 90
Section 7 – Maintenance
No routine maintenance is needed. Replacement of items should be carried
out as required. See Section 9 starting on page 115 for part numbers.
Note that if a Radio Head, Remote Unit or Repeater unit needs attention, the
clamp and chain should be used to hold the mast safely before loosening the
fixings on the bracket and lowering the mast. The procedure is described in
section 5.12, starting on page 70.
If the LUC, RU or any Radio Heads (including a Repeater) are replaced, then
the radio link(s) may need to be re-subscribed. See section 6.3 on page 80.
7.1
Diagnostic Functions
7.1.1 Loop Back Test
The link quality can be monitored by using the loop-back test. This will send a
regular test message from the LUC/BRH to an RU or LUC/NRH, which returns
the message. The LUC/BRH will time the response and display the result. The
figure should always be less than 50ms (indicated by the letter A) for single
hops, less than 100mS (indicated by the letter B) for a standard repeater.
Figures that are higher than those indicated may indicate a radio (BRH or
NRH) problem.
To activate:
On an RU link, switch off remote detector data first using RSI <Link AD>=D (deactivate).
On a TC12 NRH link, change the link type to “LIT <A\B\C\D>=R” first,
then return it to a network link when finished “LIT<A\B\C\D>=N”.
LBT <Link A-D>=A (activate)
LBT <Link A-D>=D (deactivate)
Results:
LBT <Link A-D> : <time value A, B, C, etc…>
Where A = 0-50ms, B = 50-100ms, C = 100-150ms, etc…
7.1.2 Radio Signal Strength (RSS)
The radio signal strength can be monitored at the NRH end or the RU end of
a radio link. However, with a RU link, this is only available at the actual RU.
Therefore the unit must be brought down from its mast. This may cause unrepresentative readings.
The RSS value shown by the handset command should remain between 120
and 90, for short and long links respectively. They should remain relatively
constant (only changing by a value of ten).
A consistently low value (e.g. 70) may indicate a problem with one or both
radio units (BRH or NRH), antenna or line of sight.
667/HB/30400/000
Issue 6
Page 91
A randomly changing value may be an indication of a poor antenna
connection, line of sight problem or a refection issue. Look out for a
correlation between traffic movement and RSS value. A correlation may be a
pointer to a major reflection issue.
If signal reflection is suspected, then a directional antenna may be utilised to
mitigate.
Note: As with all radio module commands, the radio must be in configuration
mode (see RMM command, section 8.4.41) before the RSS command will be
accepted.
7.1.3 Radio Head and Remote Unit Power Condition
These procedures may be useful in confirming if the Radio Head or Remote
Unit is or is not powered.
Radio Head
Go to the LUC to which it is connected.
Attempt to put the Radio Head in to configuration mode using the RMM
handset command, e.g. “RMM B=C” to put the Base Radio Head in to
configuration mode.
Enter “RSP B” or “RSP N” to view a configuration setting. If the radio
responds with “8,N,1,NONE” then the radio is powered.
In addition, confirm that the radio has been configured correctly by entering all
the “R––“ commands listed in the appropriate subscription section, e.g. RMT,
RDM, etc…
Return the Radio Head back to active mode by using either “RMM N=A” or
“RLS <A/B/C/D>=A”, as appropriate. These commands are detailed in the
final steps of the appropriate subscription section.
Remote Unit
Check that power is present at the bottom of the belled pole and that the
connections in the bottom of belled pole are correct, as per Figure 42 on page
64.
If the problem is still not located, the Remote Unit must be brought down, with
the following procedures;
Disconnect the RU cable from the socket on the bracket on the pole.
Carefully lower the mast using the clamp and chain (section 5.12, page 70).
Remove the RU from the mast.
Pull the RU’s cable out from within the mast.
Open the RU.
Plug cable from the RU back in to the socket on the bracket on the pole.
Check that the LEDs on the Remote Unit illuminate and that its Detector LEDs
illuminate as vehicles are detected (see section 3.4.2, page 37).
667/HB/30400/000
Issue 6
Page 92
7.2
Troubleshooting Guide
Use the following tables to assist in diagnosing any symptoms. The tables provide a ‘Probable Cause’ and one or more suggested
‘Actions’.
7.2.1 Scenario 1 (Remote Detectors)
Note that the LEDs on the LUC and RU can show the detector states and activity on the various serial ports, see sections 3.1.2
and 3.4.2 (pages 24 and 37).
Symptom
Probable Cause
LUC Status LED is on solid.
LUC Software is not running.
LUC Status LED off.
LUC is not powered.
“RMM B:C” or “RMM B:N”
“RLS: … <link>DD …”
BRH is still in configuration mode.
Radio Link not subscribed.
“RLS: … <link>AD …”
Radio Link is not active.
“RSI <link>:D”
LUC Detector LEDs are
flashing.
LUC Detector LEDs show the
correct detector states.
LUC Detector LED switches
off when vehicles pass of the
loop.
Remote sensors not enabled.
667/HB/30400/000
DFM forcing detectors active.
Wiring to the Controller (etc.) is at
fault.
RU is wired to the wrong ‘side’ of the
detector card (e.g. ST4R) output.
Issue 6
Actions
Check 24V is present and correct.
Attempt to restart the software by powering the LUC
down and back up.
Check backplane connections.
Subscribe the link (section 6.4.1, page 81).
Check the RU is powered.
If there are no working links on this LUC / BRH, also
check the BRH is powered.
Set-up the remote detectors (section 6.4.2, page 83).
Reset the DFM facility (section 6.4.2 page 83) by
holding down the LED Enable button for 3 seconds.
Check the wiring between the LUC and Controller (etc.),
see section 5.4.1 on page 58.
The RU must be wired to the ‘Normally Closed’ side of a
detector output.
Page 93
Symptom
LED Detector LED illuminates
at the wrong time.
Probable Cause
Wrong detector is configured or wired
to this LUC output.
Actions
Check the RU is wired to the detector card correctly.
Check the RSA settings (section 6.4.2, page 83).
7.2.2 Scenario 2 (TC12)
Note that the LEDs on the LUC can show the activity on the various serial ports and radio links (ref. section 3.1.2, page 24).
LIU – General
Symptom
Power LED on LIU not lit.
Probable Cause
LIU is not powered.
LIU - Gateway
Symptom
Probable Cause
In-station LIU “Receive” LED
not flashing.
LIU “Transmit” LED not
flashing.
667/HB/30400/000
Actions
Actions
Check LIU is plugged in to the telephone socket.
No control messages are being received. Check LIU switches/configurations are set correctly
(Ref. 5.5).
Check LUC configurations.
No control messages are being
transmitted by LUC.
Check LUC LIU interconnect cable.
Issue 6
Page 94
LIU - OTU
Symptom
OTU LIU “Transmit” LED not
flashing.
OTU LIU “Receive” LED not
flashing.
Probable Cause
Actions
Check OTU port on the LUC has been set-up correctly
Control message not getting from LUC to (sections 6.5.1 and 6.5.2, starting on page 84).
LIU.
LIU, LUC or cable between the two may be faulty.
Check LIU and OTU switches/configurations are set
Reply message not getting from OTU to correctly (Ref. 5.5).
LIU.
Check LIU to OTU interconnect cable.
LUC – General
Symptom
Probable Cause
LUC Status LED is on solid.
LUC Software is not running.
LUC Status LED off.
LUC is not powered.
“RMM B:C” or “RMM B:N”
“RLS: … <link>DD …”
BRH not subscribed.
Radio Link not subscribed.
“RLS: … <link>AD …”
Radio Link is not active.
667/HB/30400/000
Issue 6
Actions
Attempt to restart the software by powering the LUC
down and back up.
Check backplane connections.
Subscribe the links (section 6.5.3, page 86).
If there are no working links on this LUC / BRH, check
the BRH is powered.
Check Network LUC / NRH is powered (see following
checks).
Page 95
LUC – Gateway
Symptom
Gateway LUC, “NRH RX”
LED not flashing.
Probable Cause
Gateway LUC not receiving control
message from In-station.
Gateway LUC, “NRH TX”
LED not flashing.
Gateway LUC not sending any replies to
the In-station.
LUC - Network
Symptom
Probable Cause
Network LUC, “NRH RX” LED LUC not receiving control message from
not flashing.
Gateway (or higher Network LUC).
Network LUC, “NRH TX” LED
not flashing.
667/HB/30400/000
LUC not sending reply back to Gateway.
Issue 6
Actions
Check Gateway LUC set-up (section 6.5.1, page 84).
LIU, LUC or cable between the two may be faulty.
Check GOE is set to ‘1’ in the Gateway LUC.
Check TC12 commands (GMM, GNO, GCW, etc…) in
the LUC.
Actions
Check NRH port on the LUC has been set-up correctly
(section 6.5.2, page 85).
Put NRH into configuration mode (RMM N=C) and
check radio is present and is set-up correctly (RDM,
RMT, etc. from section 6.5.3, page 86) and then put the
radio active again (RMM N=A).
Check NRH and OTU ports on the LUC have been setup correctly (section 6.5.2, page 85).
Check LIU and OTU switches are set correctly.
Page 96
7.2.3 OTU GCT Error Counts
TC12 error counts are available on the OTU using the GCT handset
command.
Note: To clear the comms log enter the command GCT 0=65535
GCT 0 Good messages
GCT 1 CRC errors
GCT 2 Framing errors
GCT 3 Sync errors
GCT 4 Sync timing errors
GCT 5 Sync byte corrupt errors
GCT 6 4 second time out errors
GCT 7 Upload/Download framing errors
GCT 8 Upload/Download block CRC errors
GCT 9 Upload/Download good blocks
GCT 10 Upload/Download good messages
7.2.4 LUC Detector Outputs
The LUC detector outputs can be toggled, in sequence, in order to test
operation and wiring to other external equipments, using the DOO handset
command.
7.3
Performance Checking
For Remote Detector sites, the traffic equipment’s (Controller, OTU, etc.)
normal DFM function will log problems with a detector.
For TC12 sites, the TC12 In-station will report any spurious communications
problems as transmission (TX) errors or “No reply for 3 seconds”.
For more detailed information, the LUC event LOG is available (ref. section
8.6, page 112).
667/HB/30400/000
Issue 6
Page 97
Section 8 – Handset Commands
8.1
General
The user interface as presented through the Handset port is described in this
section.
The STC handset uses a simple text based interface.
The handset link runs at 1200 baud, 7 data bits, even parity, one stop bit.
A higher alternative speed is possible (using the SLB handset command).
When handset commands refer to the Radio Heads, the letter ‘B’ is used to
refer to the BRH and the letter ‘N’ refers to the NRH. For example, the
command RMM is suffixed by the letter ‘B’ for the BRH and ‘N’ for the NRH.
On an RU, which only has one radio module, no suffix is required on such
commands.
When handset commands refer to the Radio Links, the letters ‘A’, ‘B’, ‘C’ and
‘D’ are used to identify the four radio links.
When handset commands refer to individual serial ports, the following letters
are used: ‘B’ for the BRH port, ‘D’ for the Diagnostic (or handset) port, ‘N’ for
the NRH port, ‘O’ for the OTU port and ‘R’ for the Remote Serial port.
8.2
Handset Command Responses
For any command that is input there are a number of possible error responses
the system can give.
Command
Response
*A
*M
*P
*R
*S
Response Description
Access level for this command has not been enabled.
Three letter command (mnemonic) not recognised
Premature end of line – expecting more data
Range error – Value preceding asterisk is out of range.
Syntax error – Character preceding the asterisk is invalid.
Figure 55 – Handset Command Responses
Command Example:
Input
AB
ABC
ABCC
ABC=5
ABC=2
Output
AB*P
ABC*M
ABCC*S
ABC=5*R
*A
667/HB/30400/000
Description
Incomplete mnemonic entered
Mnemonic not valid
Character preceding asterisk is invalid
Value preceding asterisk is out of range
Access level for command not enabled.
Issue 6
Page 98
8.3
Radio Module Error Codes
The following error codes may be returned by the various handset commands
that access the radio modules in the RU, BRH or NRH:
Code
ERROR 1
ERROR 2
ERROR 3
ERROR 4
ERROR 5
ERROR 6
ERROR 21
ERROR 45
ERROR 46
ERROR 47
Hoft & Wessel Description
Command failed
Command invalid
Command parameter invalid
Subscription table full
N/A
N/A
Invalid character at command start
Unexpected argument
(Get or Information command)
Argument missing
(Set or Delete command)
Wrong argument type
Wrong number of arguments
Internal conversion error
First character of PARK invalid
Second character of PARK invalid
PARK length indicator too big
Wrong character
(Octal digit was expected)
Invalid character in checksum
Wrong checksum
Checksum too long
ERROR 49
SISUA timeout
ERROR 50
SIARI wrong key
ERROR 51
SISUA wrong PIN
ERROR 52
ERROR 90
SISUA other error
Command too long
ERROR 22
ERROR 23
ERROR 24
ERROR 25
ERROR 26
ERROR 41
ERROR 42
ERROR 43
ERROR 44
Comment
Try the command again
Radio Module not in Config Mode
No reply from Radio Module
Try the command again
On-Air Subscription failed.
Has ONS ON been entered at the LUC?
If Yes, try the command again.
The SPN or “ONS <pin>” is incorrect.
Figure 56 – Radio Module Error Codes
667/HB/30400/000
Issue 6
Page 99
8.4
Handset Command List
The table below lists all the commands (mnemonics) in alphabetical order.
Each is described in more detail on the following pages.
Mnemonic
Unit
Section
Description
BUP
DBG
DEM
DFA
DFC
DFM
DFT
DIV
DOO
GCW
GGT
GMM
GNO
GOE
GPD
GRW
LU & RU
LU & RU
LU & RU
LU only
LU only
LU only
LU only
LU only
LU only
LU only
LU only
LU only
LU only
LU only
LU only
LU only
Backup Configuration to Flash Memory (BUP)
Debug Options (DBG)
Demonstration Modes (DEM)
Detector Failure Action (DFA)
Detector Fault Counts (DFC)
Detector Fault Monitor (DFM)
Detector Fault Time (DFT)
Detector Increment Value (DIV)
Detector Output Override (DOO)
UTC Control Words (GCW)
UTC Gap Time (GGT)
UTC Modem Mode (GMM)
UTC Number of OTUs (GNO)
UTC Outstation Enable (GOE)
UTC Propagation Delay (GPD)
UTC Reply Words (GRW)
GRX
LU only
GTR
HLQ
ILR
INI
LBT
LIT
LLR
LLT
LU only
LU only
LU & RU
LU & RU
LU only
LU only
LU & RU
LU & RU
LOG
LU & RU
LRN
LUT
NSC
OFS
OJT
ONS
OSC
PIC
RAT
RCL
RDL
RDM
RIC
RLS
LU only
LU only
LU only
LU & RU
LU only
LU & RU
LU only
LU & RU
LU & RU
LU & RU
LU only
LU & RU
LU & RU
LU only
8.4.1
8.4.2
8.4.3
8.4.4
8.4.5
8.4.6
8.4.7
8.4.8
8.4.9
8.4.10
8.4.11
8.4.12
8.4.13
8.4.14
8.4.15
8.4.16
8.4.17
& 8.5
8.4.18
8.4.19
8.4.20
8.4.21
8.4.22
8.4.23
8.4.24
8.4.25
8.4.26
& 8.6
8.4.27
8.4.28
8.4.29
8.4.30
8.4.31
8.4.32
8.4.33
8.4.34
8.4.35
8.4.36
8.4.37
8.4.38
8.4.39
8.4.40
667/HB/30400/000
UTC RX mode (GRX)
UTC Time of Reply (GTR)
Set Sync Window (HLQ)
IP Layer Retransmissions (ILR)
Initialise LU or RU (INI)
Loop Back Test (LBT)
Link Type (LIT)
Lap Layer Retransmissions (LLR)
Lap Layer Timeout (LLT)
Diagnostic Event Log (LOG)
Link Radio Numbers (LRN)
Local Unit Type (LUT)
NRH Serial Configuration (NSC)
Off Air Subscription (OFS)
OTU Jitter Time (OJT)
On Air Subscription (ONS)
OTU Serial Configuration (OSC)
Program Identity Code (PIC)
Radio Antenna Type (RAT)
Radio Connection-Less Setting (RCL)
Remote Data Location (RDL)
Radio Data Mode (RDM)
Radio Identity Code (RIC)
Radio Link Status (RLS)
Issue 6
Page 100
Mnemonic
Unit
Section
Description
RMM
RMT
RRN
RSA
RSI
RSP
RSQ
RSS
SAC
SDR
SDT
SLB
SLC
SLH
SLP
SLS
SLW
SPN
SQI
SSD
TFC
TOD
TWD
VSV
XXX
LU & RU
LU & RU
LU & RU
LU only
LU only
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
LU only
LU only
LU only
LU & RU
LU & RU
LU & RU
LU & RU
LU & RU
8.4.41
8.4.42
8.4.43
8.4.44
8.4.45
8.4.46
8.4.47
8.4.48
8.4.49
8.4.50
8.4.51
8.4.52
8.4.53
8.4.54
8.4.55
8.4.56
8.4.57
8.4.58
8.4.59
8.4.60
8.4.61
8.4.62
8.4.63
8.4.64
8.4.65
Radio Module Mode (RMM)
Radio Module Type (RMT)
Retrieve Radio Numbers (RRN)
Remote Sensor Allocation (RSA)
Remote Sensor Input (RSI)
Radio Serial Port (RSP)
Radio Signal Quality (RSQ)
Radio Signal Strength (RSS)
Set Automatic Call Control (SAC)
Set Default Retransmissions (SDR)
Set Default Timeout (SDT)
Serial Link Baud rate (SLB)
Serial Link Counts (SLC)
Serial Link Handshaking (SLH)
Serial Link Parity (SLP)
Serial Link Stop Bits (SLS)
Serial Link Word Length (SLW)
Subscription Pin Number (SPN)
Sensor Quality Indication (SQI)
Set Slip Delay (SSD)
Trip Firmware Checksum (TFC)
Time of Day (TOD)
Trip Watchdog (TWD)
View Software Version (VSV)
Direct Communication to Radio Module (XXX)
Figure 57 – Handset Command List
Parameters
Description and remarks
LU
RU
Y
Y
Y
Y
Y
Y
8.4.1 Backup Configuration to Flash Memory (BUP)
Configuration settings need to be saved to flash in case of power failure etc.
Usage: BUP
Backup system configuration to flash memory.
Output:
Backing up...
Backup complete.
8.4.2 Debug Options (DBG)
This command is for engineering use only and its value should not normally be modified.
8.4.3 Demonstration Modes (DEM)
1=Sim Dets 1-4
2=Sim Dets 5-8
8=LEDs stay on
Enables various demonstration facilities on the equipment…
Usage:
DEM=1
Enable simulated vehicle detections on RU inputs 1-4
DEM=2
Enable simulated vehicle detections on RU inputs 5-8
DEM=8
Prevents the Detector LEDs automatically switching off
Output:
DEM:8 (010) Displays the current value (in decimal and octal)
To enable a combination of features, simply add the required number,
DEM=9 enables simulated vehicles on inputs 1-4 and prevents the LEDs from automatically
switching off after several minutes. To disable all demo features enter DEM=0.
The detector simulation automatically switches off if any inputs are connected to ground
(connected but detector inactive). The feature only works if all the inputs are left open circuit.
667/HB/30400/000
Issue 6
Page 101
Parameters
LU
RU
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
8.4.4 Detector Failure Action (DFA)
N = normal
operation
1 to 254 =
number of
minutes to force
active.
P = force active
permanently
When it is apparent a link has failed, the LUC can be configured to respond in various ways. It
can attempt to continue normal operation, i.e. when the link begins working again, the detector
output resume normal operation. It can force detector output active for a configured number of
minutes and then resume normal operation. Alternatively, it can force the detector outputs
active permanently (until manually reset by pressing the LED Enable button for 3 seconds).
Usage: DFA=N
DFA
Output: DFA:N
Operation after link failure is set to normal operation.
Request to view current configured operation after link failure.
Current configured operation after link failure.
8.4.5 Detector Fault Counts (DFC)
Various fault counts on the detector facility are kept by the LUC
DFC <0-3>:Link A-D: Number of DECT Link disconnection notifications
DFC <4-7>:Link A-D: Number of correct sample messages but rx’d late
DFC <8-11>:Link A-D: Number of freezes of the filter due to missing messages
DFC <12-15>:Link A-D: Number of DFM trips - too many missing messages
DFC <16-19>:Link A-D: Number of short/wrong messages
Usage: DFC
Show counts
DFC 0=0
Reset count
Output: DFC 0:0 Number of type 0 counts
8.4.6 Detector Fault Monitor (DFM)
A to D = Links
A = Activate
D = Deactivate
Each of the links A to D can have its DFM facility independently turned on or off.
Usage: DFM B=A Detector fault monitor for link B is set to on.
DFM A Request for the current configured detector fault monitor state of link A.
DFM Request for the current configured detector fault monitor state of all links.
Output: DFM B:A Current configured detector fault monitor state for link B.
DFM A:A B:A C:A D:A Current configured detector fault monitor state for all links.
8.4.7 Detector Fault Time (DFT)
1 to 14400 secs
The length of time a link is ‘down’ before the DFM facility forces the LUC outputs active can be
configured to be anywhere between 1 second and 4 hours.
Usage: DFT=60
Detector fault time is set to 60 seconds.
DFT
Request for the current configured detector fault time.
Output: DFT:60
Current configured detector fault time.
8.4.8 Detector Increment Value (DIV)
1 to 100 =
required
increment value
The increment value of the DFM error count can be configured to allow an adjustable
relationship between good vs. bad transfers to be implemented. E.g. 10 good messages are
required to reset the error count if one message is missed or late.
Usage: DIV=10 Error count increment value is set to 10.
DIV
Request to view current configured error count increment value.
Output: DIV:10 Current configured error count increment value.
8.4.9 Detector Output Override (DOO)
nn = 1 to 8
mm = 0 to 99
pp = 1 to 99
Any number of detector outputs, at the LUC, can be toggled for testing purposes.
Usage: DOO 8 2 3 Test eight detectors at 2 second intervals with a 1:3 mark space ratio.
DOO
Test single loop with current setting.
DOO 3 Test three loops with current settings
8.4.10 UTC Control Words (GCW)
0 to 14 = addr
0 to 3 = no. of
control words
Configure the number of control words for each OTU on this TC12 telephone line.
Usage: GCW
View current values
GCW 0=1
Set OTU #0 to have 1 control word
Output: GCW 0:2 Current configured control words
8.4.11 UTC Gap Time (GGT)
0 to 255ms
Time to wait after a message has been received before it is assumed that the message is
complete, i.e. how long to wait before we assume that it is a gap between messages
Usage: GGT=15
Set message gap time to 15ms
GGT
View currently configured message gap time
Output: GGT:15
Current configured OTU message gap time
8.4.12 UTC Modem Mode (GMM)
6 = 1200 baud
half duplex
22 = 1200 baud
full duplex
Select the TC12 modem mode to either half duplex (normally 2 wire) or full duplex (4 wire). Do
not forget to set up the switches on the LIU as well as setting the mode in the LUC. See
section 5.5.1 on page 60.
Usage: GMM=22 Set modem mode
GMM
View currently set modem mode
Output: GMM:22 Current configured modem mode
667/HB/30400/000
Issue 6
Page 102
Parameters
LU
RU
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
Y
8.4.13 UTC Number of OTUs (GNO)
1 to 15
No. of OTUs on this telephone line to the Instation
Usage: GNO=6
Set the number of OTUs on this telephone line to 6
GNO
Output: GNO:6
The number of OTUs on this telephone line is 6
8.4.14 UTC Outstation Enable (GOE)
0 = Disabled
1 = Enabled
Enable transmission of reply data back to the Instation. Enter GOE=1 once all GNO, GCW,
GRW etc., data has been set up.
Usage: GOE=1
Enable Outstation – LUC can now send any replies back to the Instation.
GOE
Output: GOE:1
8.4.15 UTC Propagation Delay (GPD)
0 to 90ms
The additional propagation delay required on the line to the Instation if normal telephone lines
are not used. See TC12 handbook for more details (section 1.3).
Usage: GPD=10
GPD
Output: GPD:10
8.4.16 UTC Reply Words (GRW)
0 to 14 = addr
0 to 14 = No. of
reply words
Configure the number of reply words for each OTU on this TC12 telephone line.
Usage: GRW 0=6 Set the number of reply words for OTU with address 0 to 6
GRW
Output: GRW 0:6
8.4.17 UTC RX mode (GRX)
0 to 3
Selects whether the serial port to the OTU and the serial port to the TC12 Instation (the NRH
port) are to use the CD signal or not.
Usage: Mode
Instation (NRH) Serial Port
OTU Serial Port
GRX:0
Use CD from LIU
Use CD from LIU
GRX:1
Use CD from LIU
Ignore CD (RS232 to OTU)
GRX:2
Ignore CD (RS232 modem) Use CD from LIU
GRX:3
Ignore CD (RS232 modem) Ignore CD (RS232 to OTU)
See section 8.5 for more details.
8.4.18 UTC Time of Reply (GTR)
0 to 14 = addr
Shows the time (in milliseconds after the sync byte) when the OTU’s reply message should be
sent to the Instation. The command also shows (in brackets) when the LUC received the reply
message from the OTU via the radio network.
Usage: GTR 4
Request when the reply of OTU4 should be returned
Output: GTR 4:456 (750)
OTU 4 reply should be sent to the Instation 456ms after the
control message. The reply was received from the OTU 750ms after the control message
(which should be around 50ms per hop later, plus the OJT time).
8.4.19 Set Sync Window (HLQ)
0 = Remove
time from sync
window
1 to 9 = Add
time to sync
window
This command is used to either set or display the current setting of the synchronisation
window, allowing for adjustment for longer range RF links.
Usage: HLQ <B or N>=<0 to 9> for setting and HLQ <B or N> to display current setting.
Output: HLQ:Set If command successful.
HLQ :Error
An error occurred.
Note: As with all radio module commands, the radio must be in configuration mode (see RMM)
before the command will be accepted.
8.4.20 IP Layer Retransmissions (ILR)
B = Base
N = Network
0 to 255 =
Number of
retransmissions.
The number of retransmissions can be set to between 0 and 255.
Usage: ILR B=<0 to 255>
Set number of IP layer retransmissions to the requested value
for the base radio head at the LU.
ILR N=<0 to 255> Set number of IP layer retransmissions to the requested value for the
network radio head at the LU.
ILR=<0 to 255>
Set number of IP layer retransmissions to the requested value for the
radio head at the RU.
ILR B
Get number of IP layer retransmissions to the requested value for the
base radio head at the LU.
Output: ILR:Set
The IP layer retransmissions number has been set.
ILR:Error(n)
The IP layer retransmissions number has not been set.
667/HB/30400/000
Issue 6
Page 103
Parameters
LU
RU
Use this handset command to re-initialise the unit back to its factory defaults, i.e. to return all
configuration items to their default values.
The unit will be unresponsive for about 10 seconds after entering this command while it erases
its configuration data and restarts.
Note that this does not re-initialise the Radio modules in the Radio Heads or Remote Units.
Usage: INI=1
To re-initialise the unit.
Y
Y
Y
N
Y
N
Y
Y
Y
Y
Y
Y
Y
N
8.4.21 Initialise LU or RU (INI)
8.4.22 Loop Back Test (LBT)
A to D = Links
A = Activate
D = Deactivate
Use this command to test a link. This causes a test message to be sent from the LU every half
second. The message is returned and a time measurement made of the round trip time.
Usage: LBT B=A A loop back test will be performed on Link ‘B’.
LBT B=D
A running Loop back test on Link B will be terminated.
See section 7.1.1 on page 91 for more details on how to use this command.
8.4.23 Link Type (LIT)
A to D = Links
R = remote unit
N = network
Each link a local unit has can be configured independently as either in use as a RU link or
NRH link. NB: Even if there is a repeater between the LUC and the RU, the link type is still ‘R’
for RU.
Usage: LIT B=R
Link type for link B is set to remote unit.
LIT A
Request to view the current configured link type for link A
LIT
Request to view the current configured link type for all links.
Output: LIT B:R
Current configured link type for link B.
LIT A:R B:R C:R D:R
Current configured link type for all links.
8.4.24 Lap Layer Retransmissions (LLR)
B = Base
N = Network
0 to 255 =
Number of
retransmissions.
The number of retransmissions can be set to between 0 and 255.
Usage: LLR B=<0 to 255>
Set number of lap layer retransmissions to the requested value
for the base radio head at the LU.
LLR N=<0 to 255> Set number of lap layer retransmissions to the requested value for the
LLR =<0 to 255>
Set number of lap layer retransmissions to the requested value for the
radio head at the RU.
LLR N
Get number of lap layer retransmissions to the requested value for the
Output: LLR:Set
The lap layer retransmissions number has been set.
LLR:Error(n)
The lap layer retransmissions number has not been set.
8.4.25 Lap Layer Timeout (LLT)
B = Base
N = Network
0 to 25400 =
Number of
timeouts.
The number of timeouts can be set to between 0 and 25400.
Usage: LLT B=<0 to 25400> Set number of lap layer timeouts to the requested value for the
base radio head at the LU.
LLT N=<0 to 25400> Set number of lap layer timeouts to the requested value for the network
radio head at the LU.
LLT =<0 to 25400> Set number of lap layer timeouts to the requested value for the radio head
at the RU.
LLT B
Get number of lap layer timeouts to the requested value for the base radio
head at the LU.
Output: LLT:Set
The lap layer timeout number has been set.
LLT:Error(n)
The lap layer timeout number has not been set.
8.4.26 Diagnostic Event Log (LOG)
Various
Use this command to view a rolling time stamped log of diagnostic information recorded in the
Flash device by the firmware. The timestamp relies on TOD being used to set the date/time in
the unit. See section 8.6 starting on page 112 for more details.
8.4.27 Link Radio Numbers (LRN)
A to D = Links
EMC and DNR
Input the EMC and DNR numbers, separated by a single space character, obtained from the
RU or LUC/NRH using RRN.
Usage: LRN A=322 123456 The EMC and DNR numbers for link A will be changed.
LRN A
List EMC and DNR numbers in config.
Output: LRN A:322 123456 Current configured values of EMC and DNR numbers for link A.
667/HB/30400/000
Issue 6
Page 104
Parameters
LU
RU
The local unit can be configured to be stand alone or part of a network. Within a network, the
LU can also be further configured to be a Gateway or Network. See section 3.1.1 on page 23.
Usage: LUT=1
Local unit type is set to ‘Isolated’.
LUT
Request for the output of current configuration of LU type.
Output: LUT:1
Current configured local unit type.
Y
N
Y
N
Y
Y
Y
N
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
8.4.28 Local Unit Type (LUT)
1 = Isolated
3 = Gateway
4 = Network
8.4.29 NRH Serial Configuration (NSC)
C = Use CTS
R = Auto RTS
1 = On, 0 = Off.
The NRH port can have the options shown set to either on or off.
Usage: NSC C=0 Use CTS for the NRH port is set to off.
NSC C
Request to view current configured use CTS for the NRH port.
Output: NSC C:0 Current configured use CTS for the NRH port.
8.4.30 Off Air Subscription (OFS)
This command is currently not required.
‘On-air’ subscription using ONS is recommended.
8.4.31 OTU Jitter Time (OJT)
0 to 255ms
Configures how long an LUC usually holds on to a UTC message received from the radio
before transmitting it to the OTU to remove any ‘jitter’ caused by the radio links. Jitter is the
term used to describe the fact that messages may take different times to be transmitted
through the radio network.
Changing the value in one LUC does not affect any other LUC in the same network since this
value does not delay when the LUC forwards the UTC message on to other LUCs further down
the network. It only delays when the message is transmitted to the OTU connected to this
LUC.
The value should not need to be changed, but may be increased on a Network LUC that is at
the end of several radio hops. OTU replies will be missed if the UTC Control message takes
more than 100ms (assuming OJT:100) than normal to ‘travel’ over those radio hops. So if poor
radio reception on several of those hops regularly delays the control message causing OTU
replies to be missed, this value can be increased.
Usage: OJT=100 Set OTU jitter time to 100ms
OJT
Request the current value
Output: OJT:100 Current value
8.4.32 On Air Subscription (ONS)
ON = Enable
OFF = Disable
PIN = 8 digit
number
The radio units the RU and LU use to create a wireless data need subscribing to one another
where required. See Section 6.
8.4.33 OTU Serial Configuration (OSC)
C = Use CTS
R = Auto RTS
1 = On, 0 = Off.
The OTU port can have the options shown set to either on or off.
Usage: OSC C=0 Use CTS for the OTU port is set to off.
OSC C
Request current configured use CTS for the OTU port.
Output: OSC C:0 Current configured use CTS for the OTU port.
8.4.34 Program Identity Code (PIC)
View the firmware (program) identity code.
Usage: PIC
Current software version will be output.
Output: PIC <part number><issue>
Current software part number and version (issue).
8.4.35 Radio Antenna Type (RAT)
0 = right
antenna
1 = left antenna
2 = External
3 = enables
diversity (PT
only)
Selects the antenna and mode
Usage: RAT B=2 use external antenna on BRH
RAT N=2
use external antenna on NRH.
RAT=2
use external antenna on RU.
Output: RAT B:2 BRH is using external antenna
8.4.36 Radio Connection-Less Setting (RCL)
B = BRH
N = NRH
ON / OFF
View or change the ‘connection-less’ link setting in the radio module.
Usage:
RCL B=OFF
Switch off ‘connection-less’ link mode on BRH.
RCL N=OFF
Switch off ‘connection-less’ link mode on NRH.
RCL=OFF
Switch off ‘connection-less’ link mode on RU.
Output: RCL:OFF RU is not using ‘connection-less’ link mode.
667/HB/30400/000
Issue 6
Page 105
Parameters
LU
RU
Y
*
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
8.4.37 Remote Data Location (RDL)
A to D = Links
A = Activate
D = Deactivate
Enables the Remote Serial Data on the appropriate radio link.
Usage:
RDL B=A
Activate Remote Data on Link B.
RDL B=D
Deactivate Remote Data on Link B
RDL B
Request the current configured state
Output:
RDL B:A
Remote Data requested on Link B
This format is ready to allow remote serial data on more than one link, although only one radio
link is currently supported. Prior to firmware issue 7, the format of the command was different
(it was “RDL=<A\B\C\D>”) but the remote serial data facility should not have been used on
those versions.
* The command is available on an RU for future use.
8.4.38 Radio Data Mode (RDM)
B = BRH
N = NRH
P = Protocol
T = Transparent
Set any radio head to be in protocol data sub mode or transparent data sub mode.
Usage: RDM B=P Request to set the BRH on the LU to protocol data sub mode
RDM N=T
Request to set the NRH on the LU to transparent data sub mode.
RDM=T
Request the RH on the RU to be in transparent data sub mode
Output: RDM:T
Transparent data sub mode has been selected.
8.4.39 Radio Identity Code (RIC)
B = BRH
N = NRH
View the radio firmware identity code, i.e. firmware version number and build date.
Usage: RIC B
Request to view the firmware number of the BRH
RIC N
Request to view the firmware number of the NRH
RIC
Request to view the firmware number of the RU
Output: RIC B:#23812 May 21 2003
8.4.40 Radio Link Status (RLS)
A to D = Links
A = Activate
D = Deactivate
The four links at the base radio can be activated or deactivated.
Usage: RLS B=A Activate radio link B.
RLS B=D
Deactivate radio link B.
RLS
Display status of radio links.
Output: RLS:AAA BAA CAA DAD
Shows, for each link A-D (first of each group of three letters), the configured state (second
letter) and the actual state (third letter) of the radio link. For example, “BAA” shows link B
configured to be “A” active and its actual state is “A” active. “DAD” shows link “D” is configured
to be “A” active but for whatever reason is “D” deactivated.
8.4.41 Radio Module Mode (RMM)
B = BRH
N = NRH
C = Config
A = Active
The radio modules at the local and remote units can be placed into configuration or active
mode.
Usage: RMM=A
The remote unit radio is to be put into active mode.
RMM B=C
The base radio at the local unit is to be put into config mode.
RMM
Display current mode of radio(s).
Output: RMM:A
Current mode of remote unit radio.
RMM B:A
Current mode of local unit base radio.
RMM B:A N:A
Current mode of radios.
Note: The command “RMM B=A” will be rejected. Using the RLS command to start a radio link
will automatically put the radio in to active mode.
8.4.42 Radio Module Type (RMT)
B = BRH
N = NRH
F = Fixed
P = Portable
The radio units at the local and remote units can be placed into fixed or portable mode, a ‘fixed
terminal’ or ‘portable terminal’.
Usage: RMT
Display current type of radio(s) at RU.
RMT=P
The remote unit radio is to be put into portable mode.
RMT B=F
The base radio at the local unit is to be put into fixed mode.
RMT B
Display current type of base radio at LU.
Output: RMT:SET Current type of radio head.
667/HB/30400/000
Issue 6
Page 106
Parameters
LU
RU
Y
Y
Y
N
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
8.4.43 Retrieve Radio Numbers (RRN)
B = BRH
N = NRH
Retrieve EMC and DNR numbers
Usage: RRN B
Request the EMC & DNR numbers for the base radio head at the LU.
RRN N
Request the EMC & DNR numbers for the network radio head at the LU.
RRN
Request the EMC & DNR numbers for the radio on the RU.
Output:
RRN:<EMC>
e.g. RRN:322
RRN:<DNR>
e.g. RRN:123456
The EMC and DNR numbers for the radio. When entering these numbers into an LUC using
the LRN handset command, enter the two numbers on the same line, separated by a single
space, e.g. “322 123456”.
8.4.44 Remote Sensor Allocation (RSA)
1 to 8 = Outputs
A to D = Links
Each LUC output (1-8) needs to be configured to be controlled from just one of the RUs (A-D).
Usage: RSA 2=B Remote detector 2 is provided by the RU on link B
RSA 2
Request to view the link controlling output 2
Output: RSA 2:B Current configured remote detectors.
See section 3.4.1 on page 36 for more details.
8.4.45 Remote Sensor Input (RSI)
A to D = Links
A = Activate
D = Deactivate
The stream of remote detector data from the remote unit can be turned on or off.
Usage: RSI B
Output the current configured state of remote detector input for link B.
RSI B=A
For link B, request the turning on of the remote detector data stream.
Output: RSI B:A
Output of current configuration for the state of the remote detector data
stream for link B.
8.4.46 Radio Serial Port (RSP)
B = BRH
N = NRH
8 = 8 Data Bits
N = No Parity
1 = 1 Stop Bit
NONE = No
RTS or CTS
control
Configured the radio modules serial port parameters – used to disable CTSRTS control on the
radio modules.
Usage: RSP B
Request settings on the BRH
RSP N
Request settings on the NRH
RSP
Request settings on the RU
RSP=8,N,1,CTSRTS
Enable CTSRTS control
Output: RSP:8,N,1,CTSRTS Current settings displayed
8.4.47 Radio Signal Quality (RSQ)
Obtain counts from the radio showing the radio signal quality.
Usage: RSQ
Output: RSQ:<number of correct frames> <number of incorrect frames>
8.4.48 Radio Signal Strength (RSS)
B = BRH
N = NRH
A = Activate
D = Deactivate
Obtain the radio signal strength from the RU or LUC/NRH. Value is displayed continuously on
the handset and is also represented on the eight LEDs on the RU or LUC. See section 7.1.2
on page 91 for more details on this command.
Usage: RSS=A
Activate display of signal strength
RSS=D
Deactivate display of signal strength
Output: RSS:<RSSI>
8.4.49 Set Automatic Call Control (SAC)
B = BRH
N = NRH
0 or 1 =
Automatic Call
Control is set
Off or ON
Automatic call control can be set or current value displayed, for each radio.
Usage: SAC <B or N> = <0 or 1>
Set the automatic call control to 1 or 0 on the LUC.
SAC <B or N>
Displays current setting for automatic call control on the Base or Network
radio head on the LUC.
SAC
Displays current setting for automatic call control on the RU.
SAC=<0 or 1>
Set the automatic call control to 1 or 0 on the RU.
Output: HLQ:Set If command successful.
HLQ :Error
An error occurred.
667/HB/30400/000
Issue 6
Page 107
Parameters
LU
RU
Y
Y
Y
Y
Y
Y
Y
Y
8.4.50 Set Default Retransmissions (SDR)
B = BRH
N = NRH
The number of retransmissions can be set to default values for each radio.
Usage: SDR B
Set retransmissions to default for the BRH on the LU.
SDR N
Set retransmissions to default for the NRH on the LU.
SDR
Set retransmissions to default for the radio head on the RU.
Output: SDR:Set Retransmissions have been set to default value.
SDR:Error(n)
Retransmissions have not been set to default value.
8.4.51 Set Default Timeout (SDT)
B = BRH
N = NRH
The timeout period can be set to a default value for each radio.
Usage: SDT B
Set timeout period to default for the BRH on the LU.
SDT N
Set timeout period to default for the NRH on the LU.
SDT
Set timeout period to default for the radio head on the RU.
Output: SDT:Set Timeout period has been set to default value.
SDT:Error(n)
Timeout period has not been set to default value.
8.4.52 Serial Link Baud rate (SLB)
O = OTU
N = NRH
B = BRH
D = Diag (h/set)
R = Remote
Serial.
Baud rate
options are
A = 1200,
B = 2400,
C = 4800,
D = 9600,
E = 19200,
F = 38400,
G = 57600,
H = 115200.
Each serial port has the possible baud rate settings shown here.
Note: Remote port has a maximum setting of 38400 (F).
Usage: SLB N=A Serial link baud rate for the network radio head is 1200.
SLB N
Request to view the baud rate for the network radio head port.
Output: SLB N:12 Current configured baud rate for the network radio head. (12 = 1200 bps)
This command can be used to configure an alternative baud rate for the handset (diagnostic)
serial port. The firmware has an “auto-baud” facility on the handset port, which will
automatically detect when the handset connected is communicating at the standard 1200bps
or the speed configured using “SLB D”. To change this from the default of 115200:
Configure your terminal device to work at the standard 1200bps
Connect it to the unit (LU or RU) and press any key to allow the auto baud feature to detect the
baud rate of the terminal device
Enter SLB D={new baud rate}, e.g. SLB D=H for 115200bps
NB: The above command is not acknowledged because it changes the baud rate immediately.
Disconnect your terminal device from the unit.
Configure your terminal device to work at either the standard 1200bps or the newly set baud
rate. Reconnect it to the unit and press any key to allow the auto baud feature to detect the
baud rate of the terminal device.
As with all configuration data, enter BUP to keep this setting.
8.4.53 Serial Link Counts (SLC)
For diagnostic purposes only. The command SLC displays several counts related to the
various serial ports.
Usage: SLC
View first count
Output: SLC 27:100 One hundred bytes have been received on the HCI (handset) port
The index (first number) identifies what is counted and on which serial port. The following table
shows all the indices (0 to 44). Across the top of the table is the serial port to which the count
relates and down the side is what is counted.
Remote
NRH BRH Handset OTU
Serial
0
1
2
3
4
Parity/framing errors, etc
5
6
7
8
9
unexpected interrupt type
10
11
12
13
14
TX interrupt but TX reg not empty
15
16
17
18
19
No. bytes TXd with FIFO disabled
20
21
22
23
24
No. bytes TXd with FIFO enabled
25
26
27
28
29
No. bytes RXd
30
31
32
33
34
TX interrupt after tx complete
35
36
37
38
39
No. bytes RX'd but CD low
40
41
42
43
44
No. of TX starts from task
667/HB/30400/000
Issue 6
Page 108
Parameters
LU
RU
Y
Y
Y
Y
Y
Y
Y
Y
Y
*
8.4.54 Serial Link Handshaking (SLH)
O = OTU
N = NRH
B = BRH
D=
Diag/Handset
R = remote
serial
0 or 1
Whether hardware handshaking (using CTS/RTS) is enabled for each serial device can be
configured.
Usage:
SLH R=0
Remote Serial port is to ignore CTS/RTS
SLH R
Request configured setting for the remote serial port
Output:
SLH R:1
Remote Serial port is to use hardware handshaking.
When enabled (1), the SmartLink unit will only transmit data to the external equipment while
the equipment activates CTS/RTS. When disabled (0), the SmartLink unit will transmit data to
the external equipment regardless of the state of the CTS/RTS input.
Note: The command “SLH N” is equivalent to the comment “NSC C”.
Note: The command “SLH O” is equivalent to the command “OSC C”.
8.4.55 Serial Link Parity (SLP)
O = OTU
N = NRH
B = BRH
D = Diag
R = remote
serial.
E = Enable
E = Enable
D = Disable
The type of each serial device, and whether the parity bit is enabled or disabled can be
configured.
Usage:
SLP O E=E
Serial link parity enable for the OTU is set to enabled.
SLP O
Request to view the current configured parity enable and parity type for the
outstation transmission unit.
Output:
SLP O E:E
Current configured parity enable for the OTU
T = Type
E = Even
O = Odd
8.4.56 Serial Link Stop Bits (SLS)
O = OTU
N = NRH
B = BRH
D = Diag
R = remote
serial.
The length of the stop bit for each serial device can be configured to the settings shown here
Usage: SLS D=2 Serial link stop bit for the diagnostic port set to 2.
SLS D
Request current configured stop bit for the diagnostic port.
Output: SLS D:2 Current configured stop bit for the diagnostic port.
1, 1.5 and 2.
8.4.57 Serial Link Word Length (SLW)
O = OTU
N = NRH
B = BRH,
D = Diag
R = Remote
Serial
The word length for each serial device can be configured to the settings shown here.
Usage: SLW R=5 Serial link word length for the remote device is set to 5.
SLW R
Request current configured word length of remote device.
Output: SLW R:5 Current configured serial link word length of remote device.
5, 6, 7, 8
8.4.58 Subscription Pin Number (SPN)
Pin Number
Set subscription pin number at the LUC. Initially it is suggested that the serial number of the
LUC is used as the pin number, since it is a unique 8-digit number. The same number must be
used to subscribe all the RU and/or LUC/NRH links to this LUC/BRH. Note that leading zeros
are significant; i.e. the PIN number 01234567 is different from 1234567.
Usage:
SPN=<PIN>
Subscription pin number will be changed to the new value.
SPN
Request to view the pin number
Output: SPN:12345678
Note: A request to view the pin number only shows the pin number stored in the LUC. There is
no ability to view the number stored in the radio. If in doubt, put the radio into config mode and
re-enter ‘SPN=<PIN>’.
* The command is available on the RU for future use only.
667/HB/30400/000
Issue 6
Page 109
Parameters
LU
RU
Y
N
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
8.4.59 Sensor Quality Indication (SQI)
A to D = Links
Sensor Quality Indication shows the last computed quality value for each of the radio links.
Over a fixed period, the LUC software monitors the number of detector sensor samples that
have been successfully received from the RU and ‘played back’ on the LUC output relays. This
is then used to compute a percentage where 100% means every sample has been
successfully received in time to be played back.
This information is also recorded in the rolling log; see section 8.6 starting on page 112.
Usage: SQI A
Request the value for Link A
Output: SQI A:99.75%
Detector sensor quality for Link A is 99.75%
8.4.60 Set Slip Delay (SSD)
Slip Delay = 1 to
20.
Set slip delay
Usage: SSD=10
SSD
Output: SSD:10
Set the filter delay to 10 x 2ms ticks. 20ms total slip delay.
List current configured filter slip delay.
8.4.61 Trip Firmware Checksum (TFC)
The test command modifies a safe location within the firmware area so that the background
firmware checksum algorithm (in the following seconds) detects that the calculated checksum
over the complete firmware area is no longer correct and resets the unit
Usage: TFC=1
To trip the firmware checksum
8.4.62 Time of Day (TOD)
DATE
TIME
This command can be used to view or change the date and time in the unit. This is only used
to timestamp entries in the rolling log; see section 8.6 starting on page 112.
Usage: TOD
To view the current date and time in the unit
TOD=19AUG03
To set the date
TOD=0900
To set the time (hours & minutes without a space separating)
Output: 19AUG2003 09:00:00
Due to the way the firmware uses its timers, the TOD command cannot be used to set the
units part of the seconds. If seconds are entered, then the time will be set to within 10 seconds
of the requested time.
The clock is preserved over a power failure or restart, but not incremented. Therefore, the
clock may appear to have ‘lost time’ after a power failure.
8.4.63 Trip Watchdog (TWD)
This test command prevents the firmware from re-triggering the hardware watchdog. It can
therefore be used to show that the hardware watchdog resets the unit when it has not been retriggered for a short period of time. The command can therefore be used to restart an LUC
rather than pulling it out of the 3U rack or switching the detector supply off and on.
Usage: TWD=1
To trip the hardware watchdog
8.4.64 View Software Version (VSV)
View software version.
Usage: VSV
Current software version will be output.
Output: VSV:<part number><issue>
Output of current software version.
This command shows the same information as PIC (8.4.34).
8.4.65 Direct Communication to Radio Module (XXX)
The firmware allows the user to communicate directly and transparently with the radio
module(s) connected to the unit using the normal handset port on the unit. This allows new
settings within the radio to be viewed and possibly modified, without needing a new handset
command adding to the LUC or RU firmware. Refer to the radio modules documentation for
details of the commands used by the radios.
Usage:
XXX
To talk directly to the Radio Module on an RU
XXX B
To talk directly to the Base Radio Head connected to an LUC
XXX N
To talk directly to the Network Radio Head connected to an LUC
XXX
To return to normal handset operations.
Output: **TRANSP.MODE**
667/HB/30400/000
Issue 6
Page 110
8.5
GRX Handset Command
The GRX handset command selects whether the serial port to the OTU and the
serial port to the TC12 Instation (the NRH port) are to use the CD signal or not.
Usage: Mode
GRX:0
GRX:1
GRX:2
GRX:3
Instation (NRH) Serial Port
Use CD from LIU
Use CD from LIU
Ignore CD (RS232 modem)
Ignore CD (RS232 modem)
OTU Serial Port
Use CD from LIU
Use CD from LIU
Note that only if the LUC is the Gateway LUC, i.e. the LUC connected to the TC12
Instation, are values GRX:2 and GRX:3 relevant. The Network LUCs do not have a
direct connection to the Instation but use a Network Radio Head on the NRH serial
port. In this case, the setting for the NRH port will be ignored.
GRX:0 is required if…
An LIU is used between the LUC and OTU, since the LIU will generate a CD signal
to the LUC and the OTU will determine CD itself from the telephone line from the LIU
(OTU will also have GRX:0),
AND
An LIU is connected to the LUC NRH port and a standard telephone line is used
since the CD signal will be available from the LIU (or this is a Network LUC).
The OTU is connected directly to the LUC (using RS232 and not via an LIU) since
the OTU will not generate a CD signal to the LUC (similarly the OTU must also use
GRX:1 since the LUC will not generate a CD signal to the OTU),
AND
An LIU is connected to the LUC NRH port and a standard telephone line is used
since the CD signal will be available from the LIU (or this is a Network LUC).
An LIU is used between the LUC and OTU, since the LIU will generate a CD signal
to the LUC and the OTU will determine CD itself from the telephone line from the
LIU,
AND
A bought-in RS232 modem, e.g. a fibre-optic modem, is connected to the LUC NRH
port and that modem does not provide the required CD signal.
The OTU is connected directly to the LUC (using RS232 and not via an LIU) since
the OTU will not generate a CD signal to the LUC (similarly the OTU must also use
GRX:1 since the LUC will not generate a CD signal to the OTU),
AND
A bought-in RS232 modem, e.g. a fibre-optic modem, is connected to the LUC NRH
port and that modem does not provide the required CD signal.
667/HB/30400/000
Issue 6
Page 111
8.6
LOG Handset Command
The LUC and RU units include a rolling event log that is recorded into Flash memory.
The handset command LOG allows access to this information.
The timestamps recorded in the LOG are only as accurate as the time set using the
TOD handset command, see page 110.
Caution: The log can hold over one megabyte of diagnostic data. Therefore, if it is
required to view the log, it is recommended that a PC be connected to the handset
port and used to store this information to a file for later viewing. The auto baud
feature (see SLB on page 108) should also be used to allow the handset port to use
a higher baud rate (115200bps is the default) than the standard 1200bps.
COMMAND
LOG
LOG ALL
LOG CLR
LOG ON
LOG OFF
LOG – N
LOG D
ddmmmyyyy
LOG M text
LOG U
LOG H
LOG S
LOG T
LOG Z
667/HB/30400/000
RESULT
Displays the most recent event.
Will also cease a LOGALL report in midstream.
Dumps entire contents of flash log to the handset port.
Erases the Log (takes several seconds to complete).
Causes the information being logged to flash to be displayed on
the handset as well.
Stops the action caused by LOGON, i.e. ceases reporting of live
reporting to the handset. Events continue to be logged to flash.
Displays the last ‘N’ lines from the log. If not enough lines exist, it
will return the entire LOG anyway, as though LOGALL had been
entered. Note that the maximum value for ‘N’ supported is 15000.
Displays all the events since the given date.
Note: Pre-issue 6 software will use the command LOG D ddmmm
Software from issue 6 on can accept either input. If a year is not
specified, the current year is shown.
Adds a ‘manual’ or ‘memo’ event to the log. Will add all characters
(up to 132 at a time) following the LOGM command to the log.
Displays ‘up-time’; how long the unit has been continuously
powered (with the application running). Displays days, hours and
minutes – up to a maximum of 65535 days (~180 years!!).
For Engineering Use Only…
Reports the start and end pointers of the Handset output buffer.
Shows start and end pointers (addresses) of main flash log
storage area, also the size of the data in the buffer (in bytes)
Shows address in flash where next timestamp will be written
Displays minimum and maximum passes through the main
scheduler loop in any of the fixed 10-second intervals elapsed
since power-up.
Issue 6
Page 112
Here are examples of the events recorded in the LOG…
Most events start with a four-digit millisecond count. The first digit is therefore whole
seconds, with three digits holding milliseconds in the range 000 to 999. Coupled with
the preceding date and time stamp, it gives the exact time (to the nearest
millisecond) that the event was logged, e.g.
21OCT2003 19:39:50
1234: {EVENT}
Thus, “19:39:50” and “1234” mean that the entry was logged at “19:39:51.234”.
Note that the absolute time is only as accurate as that set by the TOD handset
command. Nevertheless, the relative time between events is always accurate to
within a few milliseconds.
1234: Handset disconnected
2070: Handset connected
7214: Handset @ 1200bps
These events record when a handset was unplugged from the unit (disconnected),
plugged in (connected) and what baud rate is being used. See the SLB handset
command on page 108 for instructions on how to select a baud rate higher than the
default of 1200bps.
1234:+Reply0 resume (255 missed)
In UTC events, "Reply0" means "Reply from the OTU with address 0". In this case
the event indicates that replies from that OTU have just resumed after a number
were missed (maximum is 255, which implies more than 254 seconds worth of reply
messages have been missed).
1264:+OTU Sync - L=-001 S=-1 N=1364 (New Sync)
Events similar to the above indicate a change in when the LUC sends the UTC
control message to the OTU. The L, S and N number are for engineering use only.
However, the text in brackets indicates the reason for the event.
In this example, this is a New Synchronisation point, probably because the radio link
has just been started and this is when the first control message was received.
If these ‘OTU Sync’ events regularly indicate “(Late)”, then this implies poor radio
reception is regularly delaying when the control message arrives. If the radio
reception cannot be improved, try increasing the ‘jitter time’ using OJT on page 105
to allow more time for the control message to arrive.
4762:+LA HDLC rxd: con_ind
In many events are the abbreviations "LA", "LB", etc., that mean "Radio Link A",
"...B", etc.
The “HDLC” task in the LUC handles the protocol that allows up to four radio links. In
this case, the HDLC task has received (RXD) from the radios a connection indication
(CON_IND) for radio link A.
667/HB/30400/000
Issue 6
Page 113
4786:+LA HDLC req: est LAP
4814:+LA HDLC LAP Est
4814:+RLS:AAA BDD CDD DDD
In this example, the HDLC task in the LUC has been requested by the rest of the
software in the LUC to establish the Link Application Protocol for link A. Then, shortly
afterwards, the HDLC task indicates to the rest of the software that the LAP has
been established, i.e. that link A is now active and ready. Finally, the same event as
appears on the handset is also logged, i.e. that the Radio Link Status for link A has
changed to active. The handset command RLS is described on page 106.
2794:+LB S031 I02 Start Rem Dets
In many events relating to the remote detector facility, the events include S- and INumbers that are for engineering use only. However, the text following these will
indicate information such as ‘starting the remote detector facility’, in this case on link
B (“LB”).
1000: SQI LB:99.60% (+/-0.25%)
Events such as the above record the quality of Remote Detector links, i.e. how many
samples were successfully transferred from the RU to the LUC over the proceeding
few minutes. See the SQI handset command on page 110 for more details.
To avoid filling the LOG unnecessarily, new SQI events are only logged if there is a
change outside the ± range specified. So taking the above example, if the next SQI
value calculated is within 0.25% of 99.60%, i.e. between 99.35% and 99.85%, then a
new event will not be logged implying no significant change since the last event.
667/HB/30400/000
Issue 6
Page 114
Section 9 – Parts List
Listed below are the part numbers for the SmartLink wireless data link and
associated equipment. See the warning on page 3 regarding the use of parts other
than those listed. See also Section 11 – SmartLink Survey Equipment Sheet.
9.1
Parts List – General
Part Number
Description
667/1/30971/000
DECT radio module and antenna cable
667/1/30985/001
Directional antenna kit
667/1/30985/000
Directional antenna kit including mast
667/1/30945/000
Pole cap extension kit grey
667/1/30945/001
Pole cap extension kit black
667/1/30939/000
RU/RH housing kit
667/2/30943/000
Bracket for pole to pole mounting
667/1/30960/000
Pole to pole mounting kit (including mast, bracket, fixings and cable)
667/2/30969/000
Belled pole
667/1/30954/000
Mains distribution unit
667/1/30954/001
Mains distribution unit and detector
667/1/27853/001
24V Transformer kit
667/1/30965/000
Radio Head assembly (including radio module, enclosure, cables and internal
antenna)
667/1/30990/000
Repeater kit (including radio head assembly, enclosure, cables, mounting kit and 2
off directional antennas)
667/1/30421/000
Radio Head PCB
667/1/30970/000
Remote Unit assembly (including radio module, enclosure, cables and internal
antenna)
667/1/30423/000
Remote Unit PCB
667/1/30997/000
Local Unit Controller kit (including detector backplane kit)
667/1/30775/000
Local Unit Controller assembly
667/1/30425/000
Local Unit Controller PCB
667/1/30950/000
Line Interface Unit (to Instation) rack assembly
667/1/30950/001
Line Interface Unit (to OTU) rack assembly
667/1/29044/001
Line Interface Unit PCB (to OTU)
667/1/29044/002
Line Interface Unit PCB (to Instation)
667/1/30999/000
Installation support kit
The Parts List continues overleaf…
667/HB/30400/000
Issue 6
Page 115
9.2
Parts List – Cables
The references to “Cable A”, “Cable B”, etc., appear in several diagrams in this
handbook, for example in Figure 29 on page 51.
Cable
Part Number
Description
Cable A
667/1/30784/000
10-way twisted-pair ribbon cable assembly – LUC NRH or BRH port
Cable B
667/1/30782/000
20-way twisted-pair Remote Unit cable (RU serial channel)
Cable B
667/1/30782/001
10-way twisted-pair Radio Head or Remote Unit cable assembly
Cable BB
667/1/30783/100
20-way twisted-pair bracket assembly cable (RU serial channel)
Cable BB
667/1/30783/101
10-way twisted-pair bracket assembly cable
Cable C
998/4/88326/000
20-way twisted-pair armoured cable (controller to pole cap)
Cable D
-
Telephone cable from OTU (part of OTU assembly)
Cable D*
-
Telephone cable from LIU (part of Instation LIU assembly)
Cable E
667/1/30778/000
60mm 10-way ribbon cable (LUC OTU port to LIU to Outstation)
Cable F
667/1/30778/001
40mm 10-way ribbon cable (LUC NRH port to LIU to Instation)
Cable G
667/1/30951/000
LIU power cable
Cable H
667/1/30778/002
1m 10-way ribbon cable (LUC OTU port to RS232 OTU)
Cable J
-
Cable 1
667/1/30964/000
Repeater cable assembly – RH to RH
Cable 2
667/1/30964/001
Repeater cable – pole to RH
Cable 3
667/1/30964/002
Repeater cable – 24V to pole
9.3
Slate & White for LUC & RH power (part of LUC Backplane Kit)
Parts List – Fuses
Part Number
Description
518/4/97061/001
SMC fuse slow blow 500mA 125V (Radio Head/RU/LUC/LIU)
518/4/97061/004
SMC fuse slow blow 1.5A 125V (LUC)
518/4/90285/004
Quick blow fuse 500mA 250V (LUC/RU)
516/4/97053/000
Fuse holder and 5A fuse (mains distribution unit)
667/HB/30400/000
Issue 6
Page 116
Section 10 – SmartLink Survey Check List
The expectation is that the following checks will be made and data collected during a
site survey for each proposed implementation of SmartLink.
This section should be read in conjunction with Section 4, which starts on page 41.
For each Intersection at which SmartLink equipment is to be installed, with typically
one LUC at each Intersection in the scheme, complete one copy of each sheet.
Several copies of the RU/Repeater sheets will be required if more than one RU or
Repeater is required.
Sheet 1
General Intersection details…
Identifies the Intersection.
Checks on and records the space and equipment in the Controller cabinet.
Sheet 2
BRH Mountings…
Checks and records the pole chosen for the BRH (if required).
Sheet 3
Links from the BRH…
Checks and records the links from this BRH (if required).
Sheet 4
RU or Repeater…
Checks and records the position chosen for the RU or Repeater.
Complete one sheet for each RU or Repeater needed at this installation.
Sheet 5
NRH (or RU or Repeater)…
Checks and records the pole(s) chosen for the NRH, RU or Repeater.
Complete one sheet for the NRH at this Intersection (if required).
Complete one sheet for each RU or Repeater that is to be installed on a
Traffic Signal Pole at this Intersection rather than a Belled Pole.
Sheet 6
Sketch Intersection…
Complete a sketch of the Intersection to identify the location of the poles,
cabinet and ducting, unless a marked up CAD drawing of the intersection
can be provided.
The Equipment List in Section 11 on page 124 should also be completed to identify
the equipment required at each site.
Initially for schemes involving more than two links, a DECT radio survey is required.
For this please see engineering at Poole for details on how to perform this and loan
of the equipment.
667/HB/30400/000
Issue 6
Page 117
SmartLink Survey Check List – Sheet 1
SmartLink Installation at Intersection
Ref
Junction Name
Location
SCN Ref
Local Authority Site Ref
What is to be installed at this Intersection and powered from this cabinet?
(Exclude RU and Repeaters that are to be mounted on belled poles)
LUC RU Repeater
Is there room for the LUC and LIU in an existing 3U rack?
YES NO NA
Is there room for an additional 3U rack?
YES NO NA
Is there room for the LIU to Instation (Left of LUC)?
YES NO NA
Is there room for the LIU to local OTU (Right of LUC)?
YES NO NA
Is there room for the 12 Way Terminal block for BRH?
YES NO NA
Is there room for the 12 Way Terminal block for NRH (or RU)?
YES NO NA
Is there a controller base to re-seal?
Is there an existing TC8 or TC12 OTU at this Intersection?
YES NO NA
Is a new TC12 OTU required at this Intersection?
YES NO NA
If ‘NO’, is a new 24V AC supply kit required?
667/HB/30400/000
TC8 TC12 NO
Is this OTU on the same telephone line as the others?
Is there a 24V supply available and capable of supporting SmartLink?
Comments
YES NO
YES† NO
YES NO NA
† It is recommended that a separate small 24V AC supply is installed and used solely for SmartLink
Issue 6
Page 118
Mountings for the BRH…
Ref
Reference number of pole on which the unit is to be mounted
Cable distance from this pole to the Controller Cabinet (maximum 300m)
Has pole chosen standard signal head mounting holes available?
Has pole chosen sufficient free space above?
(Minimum 5 Metres above radio head, i.e. existing traffic pole x 3)
Is ducting known to be available and free from obstruction?
(From the pole all the way to and into the controller cabinet)
M
YES NO
YES NO
YES NO
Are draw pits clear of obstructions / useable?
YES NO
Are spare ELV terminals available in the Pole Cap for ten RH connections?
YES NO
If ‘NO’, is the Pole Cap of a suitable type for a Pole Cap Extension?
YES NO
If the answers to any of the previous are NO, what actions are going to be taken?
Mounting Holes to be drilled?
New standard traffic pole to install?
Ducting to be checked for obstructions?
By Customer or Siemens Traffic?
New Ducting to install?
Draw pits to be cleared?
New draw pits to be installed?
Are there any special installation considerations e.g. cherry picker required, traffic management, etc…
667/HB/30400/000
Issue 6
Page 119
Links from the BRH…
Link A
To:
Link Type (Tick):
Range
TC12 UTC
Linking
Any obstacles in Fresnel zone?
YES NO
Co-Location; all other radios more than 7m from the radios of this link?
YES NO
YES NO
To:
TC12 UTC
UPDL*
M
Serial
Detectors
Linking
Will a Repeater be required on this link?
YES NO
YES NO
YES NO
Is Line of Sight clear?
YES NO
To:
Link Type (Tick):
Range
TC12 UTC
UPDL*
M
Serial
Detectors
Linking
YES NO
YES NO
YES NO
YES NO
To:
Link Type (Tick):
Range
Detectors
YES NO
Range
Link D
Serial
Link Type (Tick):
Link C
UPDL*
M
Link B
Ref
TC12 UTC
UPDL*
M
Serial
Detectors
Linking
YES NO
YES NO
YES NO
667/HB/30400/000
YES NO
Issue 6
Page 120
RU or Repeater
Ref
Is this a Remote Unit?
On BRH Link:
Or a Repeater?
A
B
C
D
Junction Ref & Name of
BRH/LUC Intersection
If unit is a Repeater,
Location of NRH/RU
This unit’s location
Belled Pole to be installed?
YES NO
If ‘NO’ and a standard traffic pole is to be used, complete an “NRH/RU/Repeater” sheet (Sheet 5).
Only complete the following if a Belled Pole is to be installed…
Range
M
Will a Directional Antenna be required on this unit?
YES NO
YES NO
YES NO
YES NO
Is there sufficient free space above the proposed position of this pole?
(Minimum 5 Metres above radio, i.e. traffic pole x 3)
YES NO
Is there room for the Belled Pole available on the pavement?
YES NO
Is Mains available for the Belled Pole?
YES NO
Sketch location of the Belled Pole and add any comments…
667/HB/30400/000
Issue 6
Page 121
NRH (or RU or Repeater)
Ref
If RU/Repeater is to be mounted on a Belled Pole, use Sheet 4 instead.
On BRH Link:
Is this a NRH?
Or an RU?
Or a Repeater?
A
B
C
D
Junction Ref & Name of
BRH/LUC Intersection
If unit is a Repeater,
Location of NRH/RU
Range
M
Will a Directional Antenna be required on this unit?
YES NO
YES NO
YES NO
YES NO
Mountings for NRH (or RU / Repeater) on Traffic Signal Pole
Reference number of pole on which the unit is to be mounted
Cable distance from this pole to the Controller Cabinet (maximum 300m)
Has pole chosen standard signal head mounting holes available?
Has pole chosen sufficient free space above?
(Minimum 5 Metres above radio head, i.e. existing traffic pole x 3)
Is ducting known to be available and free from obstruction?
(From the pole all the way to and into the controller cabinet)
M
YES NO
YES NO
YES NO
Are draw pits clear of obstructions / useable?
YES NO
Are spare ELV terminals available in the Pole Cap for ten RH connections?
YES NO
If ‘NO’, is the Pole Cap of a suitable type for a Pole Cap Extension?
YES NO
If the answers to any of the previous are NO, what actions are going to be taken (see Sheet 2).
Are there any special installation considerations e.g. cherry picker required, traffic management, etc…
667/HB/30400/000
Issue 6
Page 122
Sketch Intersection
Ref
Draw a rough sketch of the Intersection, highlighting:
The controller cabinet
The location of the poles to be used, and what is fitted to each pole
The proposed route of the ducting for the armoured cable(s)
The rough directions of all the SmartLink radio links to and from this site
667/HB/30400/000
Issue 6
Page 123
Section 11 – SmartLink Survey Equipment Sheet
Quantity
Part Number
Item Description
667/1/30997/000
Local Unit Controller – LUC
667/1/30950/000
LIU to Instation (at Gateway LUC)
667/1/30950/001
LIU to Local OTU (at Gateway or Network LUC)
667/1/30778/002
RS232 cable (see page 116)
667/1/30965/000
Radio Head Assembly (BRH or NRH) (requires mast)
667/1/30970/000
Remote Unit Assembly (requires mast, pole, mains distribution kit)
667/1/30782/000
20 way cable for remote serial link from Remote Unit
667/1/30990/000
Repeater Kit (requires mast, pole, mains distribution kit)
667/1/30960/000
Radio Head and Remote Unit Pole Mounting Kit (requires mast)
667/2/30941/000
2 Metre 50mm mast (not recommended at present)
667/2/30941/001
3 Metre 50mm mast
667/1/30985/000
Directional Antenna Kit
667/1/30945/000
Pole cap extension kit – grey
667/1/30945/001
Pole cap extension kit – black
667/2/30969/000
Belled pole to accept mains distribution for a Repeater or Remote Unit.
667/1/30954/000
Mains Distribution Kit (Not Detector mountings)
667/1/30954/001
Mains Distribution Kit with Detector mountings
667/1/27663/000
Four Channel ST4R Detector Card
667/1/27853/001
24V Power Supply Kit
667/1/20690/001
19 Inch 3U Detector Rack
For a complete list of part numbers, see Section 9 – Parts List.
998/4/88326/000 – Armoured Cable
Total Number of ‘Runs’
Total Distance of all ‘Runs’
667/HB/30400/000
Issue 6
M
Page 124
Section 12 – SmartLink Configuration Sheet
The following page contains an example of the SmartLink Configuration sheet that is
included with every installation. This sheet should be completed at the time the
equipment is installed and subscribed, and kept in the Controller cabinet.
Further copies of this form may be obtained by quoting the reference part number
667/XE/30400/000.
667/HB/30400/000
Issue 6
Page 125
SmartLink Configuration Sheet
667/XE/30400/000
Junction Number / Name / Location
RRN/LRN
<EMC> <DNR>
Link
LIT
R/N
RSI
A/D
RLS
A/D
RU or LUC/NRH Location
A
B
C
D
LUT – LUC Type
1=Just RUs, 3=Gateway, 4=Network
SPN Pin No.
(LUC Serial No.)
TC12 CONFIGURATION
LUT
3
4
OTU
Phone
Line
RS232
Direct
GRX
0
1
OSC C
1
0
NRH Term Ref.
SLB N
1200
115200
BRH Term Ref.
NSC C
1
0
REMOTE DETECTORS
RSA
A-D
Det
Detector Name
GNO
GMM
6=Half
22=Full
GRX
GOE
1
1
2
3
OTU
4
0
5
1
6
2
7
3
8
4
GCW
GRW
Notes
5
DFT
DIV
DFA
6
REMOTE SERIAL
SLB
SLW
SLP
7
SLS
RDL
8
LU
9
RU
10
Subscription Summary:
LUC/BRH:
RMM B=C, RMT B=F, RDM B=P, RAT B=2, RCL B=OFF, HLQ B=1, RSP B=8,N,1,NONE, SPN=<PIN>, ONS ON
RU or LUC/NRH: RMM (N)=C, RMT (N)=P, RDM (N)=T, RAT (N)=2, RCL (N)=OFF, RSP (N)=8,N,1,NONE, ONS <PIN>, RMM (N)=A
LUC/BRH:
ONS OFF, LIT <A-D>=R/N, LRN <A-D>=<EMC> <DNR>, RLS <A-D>=A, BUP
667/HB/30400/000
Issue 6
Page 126
SMARTLINK GENERAL HANDBOOK
INDEX
Antenna
Description: 39
Installation: 69
Radio Antenna Type (RAT): 106
Separation Distance: 48
Sight Lines / Position: 43
Base Radio Head: See Radio Head
Belled Pole
Installation: 56
Survey: 47
Bracket
Installation: 67
Repeater: 75
Cable 1: 74, 76, 117
Cable 2: 74, 76, 117
Cable 3: 74, 75, 117
Cable A: 53, 63, 117
Cable B: 53, 64, 117
Cable BB: 64, 117
Cable C: 53, 63, 117
Cable D: 53, 117
Cable E: 28, 32, 53, 60, 117
Cable F: 33, 53, 60, 117
Cable G: 53, 62, 117
Cable H: 28, 53, 117
Cable J: 53, 117
Cables, Subscription: 79
Co-Located Systems: 48
Commissioning: 78
Configuration Sheet: 126
Controller Linking
Connections: 13, 27, 38, 59
Description: 13, 19
LEDs: 25, 38
Directional Antenna: See Antenna
667/HB/30400/000
Equipment
Description: 21
Equipment List: 50
For Survey: 43
Survey Equipment Sheet: 125
Error Codes
Handset Command – ‘*S’ etc.: 99
Radio Module – ‘ERROR 2’ etc.: 100
Fuses: 117
Gateway LUC: See Local Unit
Controller
Handset
Command Error Codes: 99
Command List: 101
Introduction: 99
Health and Safety: 2
Installation: 51
Recommended Order: 54
Support Kit: 79
Integrated Traffic Network: 19
Line Interface Unit
Description: 31
Installation: 60
Survey: 47
Technical Spec.: 40
Link Interface Unit
Switch Settings: 61
Link Quality Test: 92
Linking: See Controller Linking
LIU: 33
Local Unit Controller
Commissioning: 78
Description: 23
Detector Backplane Connections: 59
Issue 6
Page 127
SMARTLINK GENERAL HANDBOOK
Detector Outputs: 27
Gateway and Network LUCs: 24
Installation: 59
Local Unit Type (LUT): 24, 106
Remote Serial Port: 30
Survey: 47
Technical Spec.: 40
LOG – Event Log: 113
Loop Back Test: 92
Maintenance: 92
Maintenance Provision: 3
Mast
Attaching RU or RH: 70
Bracket Fixing: 67
Definition: 8
Fixings to Bracket: 71
Raising and Lowering: 71
Network LUC: See Local Unit
Controller
Network Radio Head: See Radio Head
Omni-Directional Antenna: See
Antenna
Order of Installation: 54
Part Numbers: 116, 125
Pole Cap Extension Kit: 66
Radio Head
Commissioning: 78
Description: 34
Error Codes: 100
Installation: 63
Signal Strength: 92
Survey: 46
Technical Spec.: 41
667/HB/30400/000
Wiring Summary: 52
Remote Detector
Commissioning: 82, 84
Description: 12, 37
Installation: 51
Remote Serial
Commissioning: 82, 84
Description: 16
Installation: 51
Remote Unit
Commissioning: 78
Description: 36
Installation: 64
Survey: 47
Technical Spec.: 40
Repeater
Description: 39
Installation: 74
Subscription: 89
Survey: 49
Rope: 71
Scenarios: 12
Security: 20
Sight Lines: See Antenna
Site Survey: See Survey
Spares: 116
Subscription Cables: 79
Survey
Checklist: 118
Details: 42
TC12
Commissioning: 85
Installation: 51
OTU Error Counts: 98
Radio Network Description: 14
Technical Spec.: 40
Terminal Blocks: 48, 52
Issue 6
Page 128