Routing: Non-Latching, Latent Routes; External Faults - ASL INTERCOM VAR8 Product Description

DVAs can be assigned Priorities as described in Section
triggered, DVAs may be overridden by any higher priority DVAs, or other inputs that are routed to the same
output.
A group of route triggers may share a single reset, or each route trigger can have its own
dedicated reset. If multiple DVA routes have been triggered by consecutive triggers in a single
group, the activation of that group's 'reset' line unlatches all the DVA routes associated with that
reset. However, if any of the triggers are still asserted, these DVAs will continue to play, while
the others will be reset.
2.6.1.2.2

Routing: Non-Latching, Latent Routes

Any contact may be configured to trigger a so-called non-latching Latent Route.
When the contact is made, a pre-programmed route is set up. When the contact is released, the route is
cleared, no separate 'reset' input is required.
Application examples are (1) when simple paging is required (not using ASL microphones) or (2) when
background music needs to be routed to selectable areas.
It is possible to use the Latent Route mechanism to allocate any output to any audio input, Mic/Line, DVA, or
Music.
If a Latent Route is used to trigger a DVA, the trigger is configurable for two modes as for a latching route:
•
DVA Full
In the 'DVA Full' mode, when the trigger is de-asserted, the DVA(s) completes its full message cycle
before ending.
•
DVA Part
In the 'DVA Part' mode, when the trigger is de-asserted, the DVA(s) ends immediately even if part way
through a DVA message broadcast.
When a Latent Route is made and the routes set up, any further routes added via the Router user-interface
are automatically added to the existing routes. Similarly routes may be removed via the user interface 'on-
the-fly'. That is to say: it is not necessary to de-assert and then re-assert the Latent Route in order to
recognise changes in the Latent Route set up.
It is possible to configure whether or not a particular Latent Route causes busy indications to be
shown on microphone consoles.
For example, a busy indication would not be desired if the Latent Route mechanism was to be
used for enabling a background music source.
2.6.1.2.3

External Faults

Any contact may be configured as an external fault input.
It is possible to assign an 18-character alphanumerical description to a Contact input when it is configured as
an external fault input.
An active input to the port indicates a 'no fault' condition. An inactive input or open circuit on the port will
cause a fault to be reported and logged. The specific fault that is raised will be identified by the
alphanumerical description.
VAR8 and Variants - Product Description
Issue: 02 complete, approved
Page 20 of 54
"2.3 Audio Input Priority and Override". Once