Owner's manual

IPDACT-2(UD) - Introduction
I-6
Doc.DM385-I
Rev. 4.0
I - 1.3. Additional features
In order to simplify installation and updating of the registered IPDACT-2(UD)s,
the IP VisorALARM receiver has additional facilities.
To install new IPDACT-2(UD)s, the Teldat VisorALARM possesses
configuration patterns associated to installer passwords. These permit you to
automatically register new IPDACT-2(UD)s in the supported IPDACT-2(UD)
list and at the same time enable the IPDACT-2(UD) to request the necessary
configuration for start up. The device can simultaneously have multiple
patterns; the choice of one or other depends on the installer password used in
the IPDACT-2(UD) to request the service.
In order to maintain and update the registered IPDACT-2(UD)s base, the
Teldat VisorALARM has commands available to remotely update one or
multiple configuration parameters used by the IPDACT-2(UD)s.
Additionally, in order to simplify the IP parameters configuration, something
that is not always easy, the IPDACT-2(UD) has a DHCP client program, which
attempts to automatically obtain all the IP connectivity information (address,
mask and gateway) on startup. To do this, you need to have a DHCP server
in the local network. If the IPDACT-2(UD) does not automatically obtain the
IP address, use the parameters that have been statically configured,
permitting you to make sure that the device operates even when the said
server is down.
The IPDACT-2(UD) allows trouble signaling to be sent to a maintenance
VisorALARM receiver, which is a different device from the main and backup
VisorALARMs. The IPDACT-2(UD) does not discriminate between
sending to one receiver or another depending on the type of signal
(alarm or trouble), but sends the same signal to both the operating
receiver and to the maintenance receiver. It is the receiver’s task to filter
the signals to be sent to the automation software.
Receivers that can be configured as maintenance are those containing
firmware version 10.5.16 and higher. These receivers are characterized as
they do not execute IPDACT-2(UD)s supervision functions, nor carry out any
remote operations over the IPDACT-2(UD)s, nor do they admit IPDACT-2(UD)
registration. These are repeat alarms coming from the IPDACT-2(UD)s and
simply filter the signals, sending only the required signals to the automation
software.