Protec Digilite DL500 Programming And Pc Configuration Tool Manual

Type
Programming And Pc Configuration Tool Manual
Protec Fire Detection plc, Protec House, Churchill Way, Nelson, Lancashire, BB9 6RT, ENGLAND
+44 (0) 1282 717171 www.protec.co.uk sales@protec.co.uk
DigiLite® DL500
EMERGENCY LIGHTING
SUPERVISORY PANEL
PROGRAMMING AND PC CONFIGURATION
TOOL MANUAL
N93-582-02 Issue 1 NH Page 2 of 28 © Protec Fire Detection plc 2015
Document Revision Details
Issue Modification Details Author Date
1 Document Creation NH 03/02/2015
N93-582-02 Issue 1 NH Page 3 of 28 © Protec Fire Detection plc 2015
Table of Contents
1.0 INTRODUCTION ..................................................................................................................................... 5
2.0 IMPORTANT NOTES – PLEASE READ CAREFULLY ......................................................................... 6
3.0 GLOSSARY OF TERMS ......................................................................................................................... 7
4.0 ITEMS SUPPLIED WITH THE DIGILITE® DL500.................................................................................. 9
5.0 ITEMS AND INFORMATION REQUIRED PRIOR TO COMMISSIONING ............................................. 9
5.1 Site information required to commission the Digilite® DL500 ......................................................... 9
5.2 PC / Laptop Requirements .............................................................................................................. 9
5.3 Software and Hardware Requirements ........................................................................................... 9
5.4 I.T Network Setting Details .............................................................................................................. 9
6.0 PROGRAMMING THE DIGILITE® DL500 ............................................................................................ 10
7.0 LOADING THE DIGILITE® DL500 CONFIGURATION TOOL ONTO A PC ....................................... 10
8.0 CONNECTING AND DISCONNECTING THE DIGILITE® DL500 FROM THE PC ............................. 10
8.10 Connecting the PC to the Digilite® DL500................................................................................. 11
8.20 Disconnecting the PC from the Digilite® DL500 ........................................................................ 11
9.0 OVERVIEW OF DIGILITE® DL500 CONFIGURATION TOOL ENVIRONMENT ................................ 12
9.1 Opening the Digilite® DL500 Configuration Tool .......................................................................... 12
9.2 Licence Agreement ........................................................................................................................ 12
9.3 Overview of the Main Screen ........................................................................................................ 13
9.4 Overview of The File Menu ............................................................................................................ 14
9.5 Overview of The Edit menu ........................................................................................................... 14
9.6 Overview of The View Menu .......................................................................................................... 14
9.7 Overview of The Panel Menu ........................................................................................................ 14
9.8 Overview of The Help Menu .......................................................................................................... 14
10.0 CREATING A SITE FILE ....................................................................................................................... 15
10.1 Creating a Blank Site File .......................................................................................................... 15
10.2 Building a Site File Using the Loop Commissioning Booklet ..................................................... 15
10.3 Creating a Site File by Logging Devices Directly on the Digilite® DL500 ................................. 15
11.0 PROGRAMMING LOOP DEVICE DATA .............................................................................................. 16
11.1 Programming the Device Serial Number ................................................................................... 16
11.2 Programming the Device Type Number .................................................................................... 16
11.3 Programming the Test Group .................................................................................................... 17
11.4 Test Group Programming Requirements for Central System Devices ...................................... 17
11.5 'Voltage' parameter for Loop Devices ........................................................................................ 17
11.6 Programming Maintained and Non-Maintained Monitoring ....................................................... 17
11.7 Programming Sub Circuit Monitoring (SCM) Devices ............................................................... 17
11.8 LDR programming ...................................................................................................................... 17
11.9 Changing the Allocated Address of a Loop Device ................................................................... 17
12.0 PROGRAMMING TEST GROUP OPTIONS ......................................................................................... 18
12.1 Programming the Day of the Month a Group Is Tested ............................................................. 18
12.2 Programming the Time of Day a Test Starts ............................................................................. 19
12.3 Programming the Duration Test Month ...................................................................................... 19
12.4 Programming the Functional Test Time ..................................................................................... 20
12.5 Programming the Duration Test Time ........................................................................................ 20
12.6 Programming Device Functional and Duration Test Times ....................................................... 21
N93-582-02 Issue 1 NH Page 4 of 28 © Protec Fire Detection plc 2015
13.0 EDITING TEXT ...................................................................................................................................... 22
13.1 Entering and editing Loop Device Text ...................................................................................... 22
13.2 Entering and editing Test Group Text ........................................................................................ 23
13.3 Entering and Editing Panel 'Banner' Text .................................................................................. 23
14.0 ENTERING PANEL INFORMATION..................................................................................................... 24
14.1 Changing the User and Engineer Access Codes ...................................................................... 24
14.2 Setting up 'Flash on Poll' for Loop Devices ............................................................................... 24
14.3 Configuring System Normal Display Options ............................................................................. 24
14.4 Configuring the Function of the Control Inputs .......................................................................... 25
14.5 Programming Network Settings ................................................................................................. 25
14.6 IP Address.................................................................................................................................. 25
14.7 Subnet Mask .............................................................................................................................. 25
14.8 Node Number ............................................................................................................................. 25
14.9 Password ................................................................................................................................... 25
15.0 UPLOADING AND DOWNLOADING FILES TO THE DIGILITE® DL500 ........................................... 26
15.1 Downloading a Site File to the Digilite® DL500 ......................................................................... 26
15.2 Uploading a Site File from the Digilite® DL500 ......................................................................... 26
16.0 UPDATING THE DIGILITE® DL500 FIRMWARE ................................................................................ 26
17.0 VIEWING HISTORIC EVENT LOGS ..................................................................................................... 27
18.0 THE HELP MENU.................................................................................................................................. 27
18.1 Viewing Digilite® DL500 Documentation ................................................................................... 27
18.2 Viewing the Version of the PC Configuration Tool..................................................................... 27
N93-582-02 Issue 1 NH Page 5 of 28 © Protec Fire Detection plc 2015
1.0 Introduction
The Protec Digilite® DL500 Emergency Lighting Supervisory Panel has been design to automate required
scheduled testing of emergency lighting fittings in a building, as stipulated in BSEN62034 and BS5288
part 8.
The Digilite® DL500 has been designed and manufactured in the UK using the latest technology and
processes.
The Digilite® DL500 system is designed to be used primarily in conjunction with Digilite® luminaires and
central system modules, however, by using appropriate Digilite® interfaces, third party systems may be
accommodated.
Test results are stored in a non-volatile event log to enable later download and hardcopy printing.
During non test mode the Digilite® DL500 monitors that the batteries in a luminaire are charging in and, if the
address is programmed to be maintained, that the lamp is illuminated.
To automate monthly and annual testing the Digilite® DL500 simulates failure of the local mains supply to
the luminaire and ensures that the lamp remains illuminated and/or the backup battery at the correct Voltage
for the duration of the test.
To ensure that all the emergency lighting is not tested at the same time the Digilite® DL500 provides up to
28 test groups. Individual luminaires may be programmed into any of these groups. The groups can be
programmed to be automatically tested on any day of the month. 20 characters of text may be programmed
per group.
The panel can accommodate up to 500 individual luminaires, and 20 characters of text can be programmed
for each device address.
This manual details the programming of the system with particular focus on the use of the Digilite® DL500
Windows based Configuration Tool.
N93-582-02 Issue 1 NH Page 6 of 28 © Protec Fire Detection plc 2015
2.0 Important Notes – PLEASE READ CAREFULLY
Both the Digilite® DL500 User and Installation and Commissioning manuals
should be thoroughly read and understood before programming is undertaken.
The Digilite® DL500 and its associated connections must be installed,
commissioned and maintained by a suitably trained, skilled and competent
person.
It is assumed that the person installing and commissioning the system is familiar
with Protec Fire Detection plc equipment terminology and terms of reference.
This equipment must be earthed and earth continuity must be preserved on
broken segments of screened cable used anywhere in the system installation.
This equipment is not guaranteed unless installed and commissioned in
accordance with current national standards.
This equipment WILL NOT operate as an automatic testing system when the USB
port is connected and is in commissioning mode.
This equipment is not suitable as part of an I.T type power distribution system as
defined in IEC 60364-3.
It is perfectly normal for sealed lead acid batteries to vent small amounts of
hydrogen when being charged. The Digilite® DL500 is vented to dissipate any
build up of hydrogen. The enclosure must not be not sealed in any way.
A competent person trained to undertake such work MUST carry out any internal
maintenance. There are no user serviceable parts inside the Digilite® DL500.
Opening the PCB housing will immediately invalidate any warranty.
There are no user serviceable parts inside the Digilite® DL500. A competent person trained to
undertake such work MUST carry out any internal maintenance work. A separate installation
and commissioning manual is available.
This equipment has been manufactured in conformance with the requirements of all applicable EU
council directives.
The policy of Protec Fire Detection plc is one of continuous improvement and as such we reserve the right
to make changes to product specifications at any time and without prior notice. Errors and omissions
excepted.
Electrical or electronic devices that are no longer serviceable must be collected separately and
sent for environmentally compatible recycling (in accordance with the European Waste
Electrical and Electronic Equipment Directive). To dispose of old electrical or electronic
devices, you should use the return and collection systems put in place in the country
concerned.
Digilite® is a registered trademark of Protec Fire Detection plc.
N93-582-02 Issue 1 NH Page 7 of 28 © Protec Fire Detection plc 2015
3.0 Glossary of Terms
Panel
The Digilite® DL500 control panel.
Luminaire
Emergency lighting lamp fitting.
Device or Address
A luminaire or interface connected to the Digilite® DL500 communications loop which can be controlled by
and transmits data to the Digilite® DL500.
Test Group or Group
Individual luminaire addresses may be programmed into one of 28 test groups. This is done to ensure that
emergency lighting coverage is maximised when luminaires are being tested (adjacent luminaires are usually
programmed into different groups). Testing is performed on a group basis.
Maintained luminaire
A light fitting which is always illuminated, either from a local mains supply, or from a backup supply if the
local mains supply fails.
Non-maintained luminaire
A light fitting which only illuminates using a backup supply when the mains supply to it is disconnected.
Disablement
When a device, or group is disabled it is prevented from entering test mode and cannot generate faults, or
failed tests.
Historic Event log
A chronological record of salient events on the system (e.g. group tests, luminaire failures etc).
Self Contained
An emergency luminaire which contains its own battery to provide backup power in the event of a local
mains failure.
Central Battery
Central Battery (CB) system in which, rather than each emergency luminaire containing its own battery, they
are fed from a larger central battery.
Sub Circuit Monitor
A device used to monitor local mains circuits, and report back if they fail to the Digilite® DL500. Depending
on programming this may trigger specific loop types to enter emergency mode.
Static Inverter
A centralised power system in which, rather than each emergency luminaire containing its own backup
battery, they are fed from a larger central battery backed power source.
Functional Test
A short term test, performed once a month, to confirm that the lamp is functioning correctly.
Duration Test
A test on the luminaire, performed once a year, to confirm that the lamp is functioning correctly and will
maintain correct output over the rated duration of the product.
Downloading
Refers to the transfer of data from a PC to the Digilite® DL500.
Uploading
Refers to the transfer of data from the Digilite® DL500 to a PC.
N93-582-02 Issue 1 NH Page 8 of 28 © Protec Fire Detection plc 2015
Site-file
Refers to the site configuration data file that is stored the Digilite® DL500, this file contains the data about
loop devices, panel settings, loop device text, group text, panel text and test timing information. When this
file is uploaded using the Windows commissioning software any historic event logs are automatically
appended to it.
Incomplete and complete site files
Some elements of loop device data can only be retrieved when the loop devices are logged
( loop device software version, LDR data and Voltage are examples). A site file that has not yet had this data
stored is termed ‘incomplete'. This type of site file is generally produced when scanning device data from
barcode labels on the devices, an incomplete site file must be downloaded into the Digilite® DL500, the loop
logged and programmed, the file uploaded after which it will be ‘complete’ and can be backed up.
Open Protocol System
If the system is Open Protocol the commissioning software freely connects to the Digilite® DL500 and allows
full access to all programming features. There is no need for a USB dongle.
Managed System
If the system is managed, then a dongle is required ( available from Protec ) to access all features in the
commissioning software. Without a dongle, or with an incorrect dongle fitted, the commissioning software will
not connect to the Digilite® DL500.
Dongle
A piece of hardware used on managed systems which is connected to the PC USB port. Commissioning
software connection is restricted to Digilite® DL500 panels containing a matching code to the Dongle,
therefore limiting panel access to engineers with relevant dongles.
N93-582-02 Issue 1 NH Page 9 of 28 © Protec Fire Detection plc 2015
4.0 Items Supplied with the Digilite® DL500
User manual
Loop commissioning booklet
Digilite® DL500 spares kit
5.0 Items and Information Required Prior to Commissioning
5.1 Site information required to commission the Digilite® DL500
To ensure rapid and trouble-free commissioning the following information should be supplied to the
commissioning engineer in advance of the proposed commissioning date.
Address positions of each loop device, exactly matching the site 'as fit' drawings
Required device types for each address
Address grouping information
Device address text ( 20 characters maximum per device )
Test group text ( 20 characters maximum per group )
Panel text ( 2 lines of 20 characters maximum )
Test group programming information (days of the week for each test group, daily test time etc)
Required Duration test times for central systems
Network settings ( if the installation uses the Digilite® DL500 TCP/IP Interface )
5.2 PC / Laptop Requirements
The PC used to connect to the Digilite® DL500 and run the PC configuration tool must conform to
the following minimum specification.
1 GHz processor
2 GB RAM
1 GB available hard disk space
Two available USB 2.0 communication ports
Windows
®
operating system XP, Vista, Windows
®
7 ( 32 bit or 64 bit ) or
Windows
®
8 ( 32 bit or 64 bit )
Connection to the internet ( if online software updates are required )
5.3 Software and Hardware Requirements
Digilite® DL500 Windows Configuration Tool software package
USB barcode scanner ( CipherLab 1000 CCD, or equivalent )
T15 Torx™ type security tool ( for removal of the Digilite® DL500 enclosure front cover )
USB Lead ( Type A male to Type B male, as illustrated below ). 2 metres maximum length.
5.4 I.T Network Setting Details
If the Digilite® DL500 installation includes a TCP/IP Interface (located in the back-box of the panel),
which enables it to communicate with a Protec graphics package, or host the DigiView® Web-server,
various network settings must be obtained from the I.T management of the installation.
See section 14 for full details of the required settings.
TYPE A TYPE B
N93-582-02 Issue 1 NH Page 10 of 28 © Protec Fire Detection plc 2015
6.0 Programming the Digilite® DL500
It is intended that the Digilite® DL500 be programmed using the Windows based Configuration Tool,
although minor system adjustments can be made on the panel.
It is also possible for the Configuration Tool to be used in isolation from the Digilite® DL500, and for loop
device data, grouping, text and panel configuration to be setup and stored as a 'site-file'. The site-file can
then be downloaded to the Digilite® DL500 at a later date.
7.0 Loading the Digilite® DL500 Configuration Tool onto a PC
The Digilite® DL500 commissioning software is supplied as a single executable file following the naming
convention ‘Digilite DL500 VX.XXX.exe’, no special installation is required and the file is simply copied onto
the desktop of the PC being used for commissioning.
If the PC is connected to the internet the Digilite® DL500 Configuration Tool may automatically check to see
if a newer software version is available. If so, a warning box is displayed asking if an upgrade should be
carried out. Only click ‘yes‘ if you are sure an upgrade to the software is required.
8.0 Connecting and Disconnecting the Digilite® DL500 from the PC
When the front cover of the Digilite® DL500 is removed all system cabling, including mains
cabling and connections are accessible. DO NOT touch any connections or cabling.
The PC connects to the Digilite® DL500 using a standard USB cable ( see section 6.2 ). The USB port on
the Digilite® DL500 is accessed by removal of the enclosure front cover, as shown in figure 8.0.
Figure 8.0. Removal of Digilite® DL500 enclosure front cover, and USB connection to a PC
USB port location
N93-582-02 Issue 1 NH Page 11 of 28 © Protec Fire Detection plc 2015
8.10 Connecting the PC to the Digilite® DL500
The USB communication port is located on the centre left of the Digilite® DL500 PCB housing ( see figure
8.0 ).
Ensuring the Digilite® DL500 is powered up, connect the USB cable to a free USB port on the host PC, then
carefully plug the other end of the USB cable into the USB port on the Digilite® DL500.
Using the menus on the Digilite® DL500 select the CONNECT TO PC USING USB option and press the
key to enter the menu.
When the Digilite® DL500 panel is connected to the PC it WILL NOT operate as a lighting test
panel
At the warning screen press the
key to continue, or to exit press the Escape key.
Note: When the Digilite® DL500 is connected to a PC for the first time the PC must recognise the Digilite®
DL500 and load appropriate software drivers, this can take up to 1 minute. Standard Windows drivers are
used, no special drivers are required. Subsequent connections to the same PC will not require this phase.
Once connected to a PC the Digilite® DL500 will display its PC connection screen, all further control is now
performed using the PC only.
8.20 Disconnecting the PC from the Digilite® DL500
When all commissioning has been completed the following procedure must be followed to correctly
disconnect the PC from the Digilite® DL500.
Close the Digilite® DL500 Configuration Tool.
Disconnect the Digilite® DL500 from the PC by using the Windows
®
‘Safely Remove Hardware ‘
feature.
Carefully remove USB lead from the Digilite® DL500.
The Digilite® DL500 automatically detects the USB lead has been removed and resets. The loop will be
re-powered and a full panel re-initialisation sequence will be instigated.
IMPORTANT. The system must be tested to ensure all aspects function as expected.
N93-582-02 Issue 1 NH Page 12 of 28 © Protec Fire Detection plc 2015
9.0 Overview of Digilite® DL500 Configuration Tool Environment
9.1 Opening the Digilite® DL500 Configuration Tool
Navigate to the Digilite® DL500 Configuration Tool icon (usually located on the desktop of the PC being
used) and double click on it. See figure 9.0
Figure 9.0
9.2 Licence Agreement
The program will prompt for the user to agree to the licensing agreement. Click 'Accept' to agree to the
licence and use the program. Otherwise click 'Decline' to exit and decline use of the program.
Figure 9.2
N93-582-02 Issue 1 NH Page 13 of 28 © Protec Fire Detection plc 2015
9.3 Overview of the Main Screen
The Digilite® DL500 Configuration Tool environment consists of a main screen with several menu options
located at the top left corner. Selecting a menu option brings it to the main screen. Information entered in a
menu option is retained when swapping between menus.
To open the Configuration Tool double click on the Digilite® DL500 icon ( usually present on the PC’s
desktop ). The main screen will open as illustrated in figure 9.3.
Figure 9.03 Main screen and sub option selections
N93-582-02 Issue 1 NH Page 14 of 28 © Protec Fire Detection plc 2015
9.4 Overview of The File Menu
This menu contains the following choices:
New
This option creates a default site file where all aspects of the programming are restored to their default
settings. This must be done before creating a new site file, or before scanning data in from device bar codes.
Load
This option loads a previously saved site file. The user must navigate to the file and open it.
All site files have the .psf file extension.
Import Text
Text previously exported from the Protec Excel text editor can be imported into the site file using this option.
Save / Save As
Allows the site file currently loaded to be saved ( as filename.psf ).
Export
This option allows the Event log, Device Data, Test Data and Text to be exported to a .txt file.
Exit
Exits the program.
9.5 Overview of The Edit menu
This menu contains the following choices:
Enter Site Info
This screen allows information about the site to be entered. The data is then stored in the panel and can be
retrieved at a later date.
Text Editor
The loop device text, group text and panel text can be entered and edited in this screen.
Device Editor
Loop device data and their operational parameters are setup in this screen.
Test Options
The group and system test dates and durations are setup in this screen.
Panel Information
Various system operational parameters are setup in this screen, including User and Engineer access codes,
Control 1 and 2 input function etc.
9.6 Overview of The View Menu
This menu allows the user to view event logs uploaded from a panel, or stored in a site file.
9.7 Overview of The Panel Menu
This menu is used to download and upload site data to and from the Digilite® DL500, or to update the
operating system firmware.
9.8 Overview of The Help Menu
This menu allows the user to check for updates to the commissioning software or download relevant
Digilite® DL500 documentation from the Protec website. The version of the Digilite DL500 Configuration Tool
software can also be viewed here.
N93-582-02 Issue 1 NH Page 15 of 28 © Protec Fire Detection plc 2015
10.0 Creating a Site File
10.1 Creating a Blank Site File
When starting from scratch a blank ( default ) site file must be used. This site file contains default values for
relevant elements of the site data. To create a blank site file click
File -> New
Then select ‘Yes’ when the program requests to Delete Current Settings. A default site file will be loaded into
the program.
10.2 Building a Site File Using the Loop Commissioning Booklet
In some cases it is advantageous to build the site file remotely from the panel ( a site file can be prepared
and saved before visiting site if loop device data, group data and associated text is known before hand ).
All Protec loop devices are supplied with two self adhesive manufacturing barcode labels. During installation
one label remains on the device and the other is removed from the device and affixed at the relevant loop
address in the Digilite® DL500 Loop Commissioning Booklet. This then links that device serial number to the
loop address.
In the Edit -> Device Editor window of the commissioning software the Digilite® DL500 Loop
Commissioning Booklet is then used in conjunction with a barcode scanner to scan the address number in
the booklet followed by the loop device data. This device data is then stored at the relevant address. See
figure 10.0.
The extra device parameters ( Test Group, Maintained, SCM etc. ) can be edited at this point if desired.
Note that when using this method the software 'Version' , 'Use LDR' and 'Voltage' data for the
loop device are not not read from the barcode label ( the site file is incomplete ).
When all devices have been scanned in from the Loop Commissioning Booklet the site file
must saved then downloaded into the Digilite® DL500 and the loop logged and saved, at this
point the software Version , Use LDR and Voltage data are added to the site file ( it becomes a
complete site file ) and it must be uploaded from the Digilite® DL500 for backup purposes.
Figure 10.0
10.3 Creating a Site File by Logging Devices Directly on the Digilite® DL500
The alternate method for creating a site file is to log and allocate actual devices connected on the Digilit
DL500 data loop, then upload the site file into the commissioning software. Any loop device parameters or
panel options may then be edited as required and the file downloaded into the Digilite® DL500. For further
details on this, please refer to the Digilite® DL500 Installation and Commissioning Manual.
Example of device serial
number 0x234456 allocated
to address 1.
N93-582-02 Issue 1 NH Page 16 of 28 © Protec Fire Detection plc 2015
11.0 Programming Loop Device Data
Various operating parameters must be 'attached' to loop device in order to inform the Digilite® DL500 Panel
how to process each device.
The device Serial Number, Type number, Software Version, Voltage and LDR data are programmed into the
loop device when it is manufactured.
The Test Group, Maintained and SCM parameters can be edited (for certain loop device types). This section
details what these parameters are and how to program them appropriately.
Loop device data programming is done in the Edit -> Device editor window, as illustrated in figure 11.0
Figure 11.0
11.1 Programming the Device Serial Number
The serial number of the device is a unique number allocated to the device when it is manufactured. The
Digilite® DL500 uses this data to communicate with the device. To attach a serial number to a loop address
simply click on the Serial number cell for that address and enter the 6 digit serial number (found on the
device manufacturing label).
11.2 Programming the Device Type Number
The type number is used by the Digilite® DL500 in order to process the returned data from the device
appropriately. To select a type number either:
a. Click on the Type cell for the device and choose the relevant type from the option list, as illustrated in
figure 11.1
b. Enter the serial number as an 8 digit number (as opposed to a 6 digit serial number) where the type
number (if know) is pre-pended to the serial number. For example Type F3 (LED DRIVER) with
serial number 452237 would be entered as F3452237.
Figure 11.1
N93-582-02 Issue 1 NH Page 17 of 28 © Protec Fire Detection plc 2015
11.3 Programming the Test Group
The Digilite® DL500 permits each loop address to be programmed in to one of 28 test groups.
Device grouping is offered is to ensure that adjacent luminaires are never tested simultaneously. Adjacent
devices are usually programmed into staggered groups 1 to 28.
This ensures that, even though a group may be in its annual duration test (or re-charging after it), sufficient
emergency lighting cover is still provided by devices programmed into other groups.
To program the test group, click in the Test Group cell for the relevant loop address and enter the required
group number (1 to 28).
11.4 Test Group Programming Requirements for Central System Devices
All loop devices which relate to a central system (central system control interface, central system loop
interfaces and any Sub Circuit Monitors for that system) must be programmed into the same test group.
Multiple central systems can be accommodated by the Digilite® DL500, but each must have its own unique
test group.
11.5 'Voltage' parameter for Loop Devices
The loop device, when logged, returns it's programmed Voltage. This parameter does not apply to all device
types and the software will display 'N/A' if the Voltage parameter for that device type is not applicable.
The Voltage is used by the Digilite® DL500 to correctly process the data returned by the device.
11.6 Programming Maintained and Non-Maintained Monitoring
For LED_DRV or STATIC_LOOP based luminaire device types the Digilite® DL500 can monitor the output
under non test (maintained) conditions. In doing this the system can warn the system maintenance
personnel that attention is required.
If the LED_DRV or STATIC_LOOP at the address is maintained (lit normally, as well as under mains failed
conditions) then click in the Maintained cell for the relevant loop address. This toggles the selection between
'Maintained' and 'Non-maintained.' Set as required.
11.7 Programming Sub Circuit Monitoring (SCM) Devices
STATIC_LOOP device types can be programmed to monitor local mains sub circuits by setting the SCM cell
for the device to 'Yes'.
When they are programmed to do this any central system types matching the group for the device are put
into emergency operation when the Sub Circuit Monitor detects a local mains failure.
Only one Sub Circuit Monitor unit is permitted per test group.
11.8 LDR programming
Some legacy loop device types use light sensors (LDR's) to detect if the lamp in a luminaire is illuminated, or
not. The loop device type, when logged, reports whether it has an LDR fitted or not. This is shown in the
'Use LDR' field for a loop device.
11.9 Changing the Allocated Address of a Loop Device
A loop device may be allocated to another address by simply clicking on the device to be moved and
dragging and dropping onto the empty address required.
If a device is dragged and dropped onto another loop device, they will exchange logical loop address
positions.
N93-582-02 Issue 1 NH Page 18 of 28 © Protec Fire Detection plc 2015
12.0 Programming Test Group Options
Each test group must have various parameters programmed. The values of these parameters depends on
specific site requirements and codes of practice.
Each test group has a line of parameters to be programmed.
Loop device data programming is done in the Edit -> Test Options window, as illustrated in figure 12.0
Figure 12.0 Test Options Screen
12.1 Programming the Day of the Month a Group Is Tested
The day of the month in which devices in a group are tested can be programmed. It is usual to program the
system to make a single group test on a particular day of the month, but the Digilite® DL500 has the
flexibility to change this as required by the commissioning engineer.
Click in the 'Group Test Day' cell for the group being programmed and set this to a day of the month ranging
from 1 to 28.
N93-582-02 Issue 1 NH Page 19 of 28 © Protec Fire Detection plc 2015
12.2 Programming the Time of Day a Test Starts
The time of the day in which a test is started is fully programmable. It is usual to choose a time of day for the
test which will impact the least on the emergency lighting coverage of a premises. The default for the
Digilite® DL500 is 12 o'clock, midnight.
To program the time, double click in the Group Test Time cell for the group being programmed and enter the
start time for the test in 24 hour format. Figure 12.1 illustrates the test time set to quarter past two in the
morning.
Figure 12.1
12.3 Programming the Duration Test Month
Normally a functional test is performed on a group. This is a shorter test (typically 5 minutes) which confirms
that the main operating parameters of the device are within limits. However, annually, this is replaced with a
Duration test, where the fitting is tested for the full rated duration (typically 3 hours).
The month of the year when this occurs is programmable. Top do this double click on the 'Duration Test
month' cell for the group being programmed. A calendar is displayed (illustrated in figure 12.2), select the
required month by clicking on it.
Figure 12.2
N93-582-02 Issue 1 NH Page 20 of 28 © Protec Fire Detection plc 2015
12.4 Programming the Functional Test Time
The time duration, in hours and minutes, which a functional test takes is programmable. The default time is 5
minutes, but may be programmed between 00:00:00 and 04:00:00 as required.
To alter the time, double click on the 'Functional Test Time' cell for the group being programmed, and enter
the time in Hours, Minutes and Seconds. A functional test time of 6 minutes and 30 seconds is illustrated in
figure 12.3.
Figure 12.3
TIP: If you need to set all the groups to the same Functional test time, double click on the main
heading 'Functional Test Time (HH:MM:SS)' and enter the time. All groups will be updated.
12.5 Programming the Duration Test Time
The time duration, in hours and minutes, which a duration test takes is programmable. The default time is
3 hours, but may be programmed between 00:00:00 and 04:00:00 as required.
To alter the time, double click on the 'Duration Test Time' cell for the group being programmed, and enter the
time in Hours, Minutes and Seconds. A functional test time of 2 hours and 30 minutes is illustrated in figure
12.4.
Figure 12.4
TIP: If you need to set all the groups to the same Duration test time, double click on the main heading
'Duration Test Time (HH:MM:SS)' and enter the time. All groups will be updated.
The Duration test time for central systems (static inverter and central battery systems) is usually
specified by the designer of the system. The programmed Duration test time for these systems is
typically set to two thirds the full rated duration, thereby allowing a reserve of power to run the
system after a duration test has completed.
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28

Protec Digilite DL500 Programming And Pc Configuration Tool Manual

Type
Programming And Pc Configuration Tool Manual

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI