P/N PM000223A • Rev. 1 • ISS 9 August 2017
4
Installation Manual
NU-Series Hardware
Introduction
Legend
(1) Gateway II (NGGTWY2)
(2) Hallway bus power
(3) Hallway bus data
(4) Passive Bus Concentrator (NUPBC)
(5) NU-series active dome light (NUDL4S)
(6) Passive room bus
(7) Active room bus
(8) NU-series passive light (NUCL4P)
Caution: The Telligence system is an electrically supervised system, except for the
passive devices connected to the passive room buses.
1.4.1 Hallway Bus
The hallway bus is controlled by the Gateway II control equipment. The Gateway II sends
data and voice via a Cat 5/5e/6/7 cable and it sends power via a separate wire pair to a
combination of active NU-series dome lights and NUPBCs, which are connected to the
hallway bus. These devices, in turn control the room buses and communicate with the NU-
series active room modules connected to the dome lights and existing passive HC-series
Telligence room modules connected to the NUPBCs. The following graphic illustrates the
system setup using a dome light to communicate with active modules and a NUPBC to
control passive modules.
Figure 3 Hallway bus with Gateway II in combination with NUPBC and dome light
Legend:
(1) Gateway II
(2) Power from Gateway II to hallway devices
(3) Daisy-chained hallway bus
(4) Passive Bus Concentrator (NUPBC)
(5) Dome Light (NUDL2S/NUDL4S)
The Gateway II supplies 36VDC (2x100W) hallway power to dome lights and NUPBCs
through 16 AWG single pair cables connected to separate Port A (100W) or Port B (100W)
output screw terminal blocks on the rear panel.
The Gateway II supports 40 devices on the hallway bus (dome lights or NUPBCs). A
Telligence extension license extends the support to 80 devices (40 devices Port A, 40
devices Port B).
Each NU-series dome light and NUPBC has six DIP switches for hallway bus addressing.
This allows for replacement of broken devices without affecting the configuration.
Alternatively, a serial number-based configuration is possible with the use of the Software
Configuration Tool. However, when replacing broken devices that were addressed using
the Software Configuration Tool, the new device must also be addressed using the
Software Configuration Tool.
