In default cascaded satellite system configurations, satellite switching commands are not
associated with a user priority level. When a switching command sent from a master site is
received by a satellite, the switch selection can immediately be overridden by operators at the
satellite location who have any priority level.
This situation is more likely to be encountered in 3-tier Satellite systems that do not have a
good distribution of trunk lines (i.e., more between the top level system and the intermediate
level system than there are between the intermediate system and the 3rd tier satellite).
Since dual master configurations support bi-directional communications, it is possible to set
keyboard User Function 41 to use the SAT nnn PRIORITY option for both the top level and
intermediate level master systems. The satellite number assigned to the system that is
currently being programmed must be specified here. This feature will enable use of the
operators user priority to determine if access to a desired satellite camera is provided or not.
For instance, if no trunk lines are available and an operator requesting a satellite camera has a
higher priority than at least 1 of the existing operators, the requested camera will be
switched. If the operator does not have sufficient priority, they will receive an error message
(i.e., error 81) via the satellite communication path, and their camera will switch to the Start-
up camera specified in the Monitor Table.
Alarm Inputs in Satellite Systems
Any alarm inputs to the main site, which have been programmed to activate cameras located
at satellites, will operate normally except when limited by the number of trunk lines available.
The software automatically determines trunk usage depending on the priority level of
operators currently viewing satellite cameras. Alarm inputs applied at a satellite site will not
activate the alarm video at the main site.
If the application requires alarms located at a satellite to activate video at the main site, the
remote alarms must be brought back to the main site. If necessary, the main site’s LTC
8540/00 Alarm Interface unit can be remotely located via an RS-232 link. Since the Alarm
Interface capability is an integral part of the LTC 8300 Series, this is not possible if an LTC
8300 Series system is being used as the main site system. If more than one satellite site
contains alarms, multiple LTC 8540/00 Alarm Interfaces can be remotely located. The number
of alarm interfaces which can be remote is limited only by the capacity of the main site system
to support this capability.
Keyboard
Controller
COM1
COM2
Console
Biphase
LAN
Alarm
1
2
3
4
5
6
7
8
Figure 8.9: Rear Panel View of LTC 8904 Series CPU Bay
8.8
66
en | Satellite System Configuration Installations
LTC 8900 Series
2015.01 | 10.6 |
Installation Manual
Bosch Security Systems, Inc.
