Bogen UTI312 - Manual (Page 20)

20
AUX Relay Contact
The UTI3
12 allows the installer to program a number of different parameters to control the way in which the
UTI3
12 AUX relay contact activates.The UTI312 allows programming of which input events (Override,Tone Trigger
1 and 2, Page, and Night Ring) it will respond to, whether it will respond to the event only (Event-Driven Mode) or
to a combination of the event and its place in the priority structure (Priority-Driven Mode), and if the contact will
respond during the event (No Delay) or after the event ends (Delay).
Event Enable/Disable
The UTI3
12 monitors for 5 types of input events: Override, Tone Trigger 1, Tone Trigger 2, Page and Night Ring.
When one of these inputs is activated, the UTI3
12 detects that as a particular event. Through programming, the
installer can decide which of these 5 events the UTI3
12 will allow to activate the AUX relay. Setting the event to
Enable allows the AUX contact to respond to that event.
For example, if the application requires that the AUX relay contacts respond only when the Night Ring input is
active, the installer would enable the Night Ring event and disable all other events (Override, Tone Trigger
1 & 2,
and Page).
It is possible to enable multiple events. In this case the events are logically "or'red" together. For example, if the
Override and Tone Trigger
1 events are both enabled, the AUX contacts will activate when the Override input OR
the Tone Trigger input OR both of them become active. If all 5 events were enabled, the contacts would activate any
time the UTI3
12 was doing anything but sitting idle (this is the factory default setting).
Event-Driven/Priority-Driven Mode
There are applications where the AUX relay contacts should activate regardless of what else may be going on in the
UTI3
12 (Event-Driven Mode) and other times when it should activate so long as there is not another higher priority
input active (Priority-Driven Mode).
For example, an application requires that a strobe flash for as long as the Night Ring line rings.This is accomplished
by selecting the Event-Driven Mode and disabling all the events except Night Ring. In this configuration, the AUX
relay contacts will activate whenever the Night Ring line becomes active.This action is independent of whatever else
may be going on in the UTI3
12.Therefore, even though a page may be occurring that suppresses the Night Ring
audio tone, the AUX relay will still cause the strobe to flash.
Likewise, there may be applications where it is desirable to have a higher priority event deactivate the AUX relay
operation even though a lower priority event is still on going. For example, suppose the strobe above was specified
to flash only when the Night Ring audio is produced. This is accomplished by selecting the Priority-Driven Mode
instead of the Event-Driven Mode. In this case if the Night Ring audio is interrupted by a higher priority input, like
the Page input, the AUX relay will be deactivated for the duration of that event.The AUX relay will become active
again if the lower priority (Night Ring) event is still active when the higher priority event finishes.
Delay/No Delay
It is sometimes desirable for the AUX relay to activate immediately after an event rather than during an event. By
selecting the Delay programming option, the contacts activate immediately after the enabled events end. The
contacts will activate for
1 second and then deactivate.
For example, a specification requires that after a tone has been produced an audio message is to be played that is
triggered by a momentary contact closure. To accomplish this, the tone trigger
1/2 event is enabled and the Delay
option is selected. In this configuration the AUX relay contacts trigger the message playback device at the end of
the tone.