Examples Of Lamp Monitor Unit Configuration Using The Handset - Siemens TC12 Installation, Commissioning And Maintenance Handbook

ENG 203 - 210 0 to 255
OTUSRx - Integral OTUs shared RAM sections 0-7
These eight codes can be used to display any byte within the shared RAM
interface between the Integral OTU and the controller. For ease of use, it is
recommended that the 'ENO' command is used rather than this one.
For example, to access byte number 234 (hex):
2XX requires OTUSR2, i.e. ENG 205
34 hex is 52 in decimal, therefore the command will be:
ENG 205 52

6.4.3 Examples of Lamp Monitor Unit Configuration Using the Handset

The LMU is configured via the handset and there are several example
configurations detailed on the following pages. The main items of data to be
entered and their associated handset commands are listed below:
- Define the type of output to be monitored by each current sensor (KPT)
- Allocate an aspect drive identity to each current sensor (KAD)
- Select normal lamp monitoring (i.e. NOT Red Lamp Monitoring) for each vehicle
phase (KRE)
Depending on the controller configuration, the following additional data may need
to be entered:
- If the controller does not have dimming fitted, disable dim/bright checking (KDP)
- If the controller enters a flashing red/amber mode (export only), define the input
to disable monitoring during the flashing period (KFD)
- To monitor 50-0-50 lamps, select low voltage operation (KLV)
Example 1 - Simple 2 phase controller
Description: This is an intersection controller with 2 vehicle phases and lamp
dimming.
The configuration commands are detailed below.
Enable LMU write access:
AMB = 35
NEC = 249
Allocate function of each current sensor:
KPT 1 = 1
666/HE/43100/000
TC12 Installation, Commissioning & Maintenance Handbook
:current sensor 1 monitors a vehicle phase
Page 185 Issue 10