N93-572-88 Issue 12 NH Page 30 of 52 © Protec Fire Detection plc 2020
7.16 Programming the coverage volume of Visual Alarm Devices (VADs)
The coverage volume of EN54-23 compliant VADs may be set up on a device specific basis by
appropriate programming in the Windows PC software.
This feature allows the individual coverage requirements of loop VADs to be tailored for the specific
installation environment, which results in optimised system operating currents.
7.17 Logging and Mapping Loop Devices
Logging and mapping loop devices is the process the 6100 uses to work out how many, and what
type of devices are connected to the loop, and where they are in relation to each other.
Before logging always ensure there are no loop faults on the panel
Logging and mapping could take up to 6 minutes, depending on the loop
configuration
The 6100 WILL NOT detect fires during the logging and mapping phase
Logging
During the logging phase the 6100 drives the loop from sides A and B, all relevant devices connected
to the loop are logged and stored in memory ( devices will not be logged if the 6100 does not support
the device type, or the software version of the device is not supported by the 6100 ).
When the 6100 has logged a loop device it searches the existing panel loop device data to see if the
loop device is already logged and allocated on the system, if it is, the software version of the loop
device is updated in memory. By doing this site files that have been created using a device serial
number barcode scanner ( which does not contain the device software version ) and downloaded using
the PC commissioning software are completed. The resulting ‘complete’ site file must always be
uploaded from the panel to the PC and stored for backup.
Mapping
During the mapping phase the loop drives from side A only. Loop isolators on devices are sequentially
closed and each group of devices between isolators are allocated an ‘isolator node number’. As
devices are sequentially mapped, data stored during the logging phase is checked, if the mapped
device was not logged originally the mapping process will fail. Device loop isolators are closed
sequentially until all logged devices have had their isolators closed, after which the panel has complete
information of how the system is configured.
Please note, even if the mapping process fails, the logging data stored in memory may still be used to
allocate loop devices onto the 6100, even though the isolator node data may not be present.
At the LOG LOOP DEVICES menu press the
¿
key to begin the loop logging sequence ( as shown
in figure 7.1 and 7.2 )
Line 1 of the display indicates the logging and mapping progress, and has the following sections.
RESETTING LOOP
Displayed when the 6100 is resetting the loop to make sure all loop devices are ready to be logged.
LOGGING LOOP
Displayed when the 6100 is logging the loop devices.
LOGGING COMPLETE
Displayed when the 6100 has finished logging the loop devices and is preparing to map the loop
devices. Logged device data is now in temporary memory.
MAPPING LOOP
Displayed when the 6100 is mapping the sections of the loop separated by loop isolators.