Bogen Telephone UTI1 User Manual

0

Out of 0 Ratings

Owner's of the Bogen Telephone UTI1 gave it a score of 0 out of 5. Here's how the scores stacked up:

  • Reliability

    0 out of 5

  • Durability

    0 out of 5

  • Maintenance

    0 out of 5

  • Performance

    0 out of 5

  • Ease of Use

    0 out of 5
of 20
 
15
AUX Relay Contact
The UTI1 allows the installer to program a number of different parameters to control the way in which the AUX
relay contacts activate.The UTI1 allows programming of which input events (Override,Tone Trigger, 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 UTI1 monitors for 4 types of input events: Override,Tone Trigger, Page, and Night Ring.When one of these
inputs is activated, the UTI1 detects that as a particular event.Through programming, the installer can decide which
of these 4 events the UTI1 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 and page).
It is possible to enable multiple events. In this case the events are “OR’d” together. For example, if the override and
tone trigger 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 4 events were enabled,the contacts would activate any time the UTI1
was doing anything but sitting idle (this is the factory default condition).
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
UTI1 (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 UTI1.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 any other higher priority event will deactivate the AUX relay for the
duration of that event.The AUX relay will become active again if the lower priority 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 occur. 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 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.
What about the Event- or Priority-Driven setting? Only the override input is a higher priority setting than the tone
trigger and thus could interrupt the tone. Setting it to Event-Driven Mode will cause the audio message to trigger
at the end of the tone duration, even if the override is suppressing the tone itself. However, setting it to Priority-
Driven Mode may lead to multiple pulses being produced since the UTI1 will consider the tone trigger completed
when the override suppresses it and will produce the pulse. If the tone is still in progress when the override is
removed, then a second pulse will be produced at the actual end of the tone duration.

   Find Your Products By Category