
T400 Controller Facilities Manual
667/EB/20200/000 Page 15-1 Issue 9
15. INPUTS AND OUTPUTS
15.1 INPUTS (I/P)
Inputs into the controller may include the following:
(i) Demands and extensions from detectors (VA and Priority).
(ii) Demands from pedestrian push-buttons.
(iii) Extensions from SDE/SA assessors.
(iv) Extensions from all-red detectors.
(v) UTC control bits.
(vi) Links from other controllers.
(vii) Hurry Call requests.
15.2 OUTPUTS (O/P)
Outputs from the controller may include the following:
(i) UTC reply bits
(ii) Links to other controllers
(iii) Monitoring Signals
(iv) Hurry Call Confirmations
(v) Special Outputs to indicate certain states within the controller (e.g.
controller fault output)
15.3 LOGIC CONDITIONS
The logic conditions of the inputs and outputs are shown in below:
NON-UTC UTC
ACTIVE INACTIVE ACTIVE INACTIVE
INPUT1010
OUTPUT1001
The logic conditions of the ports may be read via the handset using the IOP command.
The active and inactive states are configurable for each individual input by choosing
whether or not to invert them. Normally, ‘1’ is an open circuit for vehicle detectors.
15.4 PORTS
The ports of the controller provide a means of connecting the hardware of the input
and output signals to the controller software.
Each port consists of 8 bits (0 to 7) which must be either all inputs or all outputs.
In order to calculate the number of ports that are required, the inputs and outputs are
allocated, where practical, into groups of 8. It is better for configuring if all the
detectors for one phase are on the same port.
UTC inputs must be allocated different ports to detector or other inputs for software
reasons.
Kommentare zu diesen Handbüchern