996-170-000-1, Issue 1.

0
getting
started
guide
MORLEY-IAS Visualeyez

Table of Contents

1 INTRODUCTION ............................................................................. 1
1.1 THE SYSTEM ...................................................................................................................... 1
1.2 MAXIMUM SYSTEM PARAMETERS .................................................................................. 2
1.3 THREE DIFFERENT VERSIONS ....................................................................................... 2
1.4 THE DONGLE ...................................................................................................................... 2
1.5 UPGRADING SYSTEM ....................................................................................................... 2
1.6 PLUG & PLAY ...................................................................................................................... 3
1.7 INTERFACE CONNECTION ............................................................................................... 3
1.8 EVENTS FROM THE MORLEY PANELS ........................................................................... 4
1.9 DEVICE TEXT ..................................................................................................................... 4
1.10 CONTROLS TO THE MORLEY PANELS FROM VISUALEYEZ ....................................... 5
1.11 THE NUMERIC REFERENCE ............................................................................................ 5

1.12 PASSCODES ....................................................................................................................... 6

2 SETTING UP YOUR SYSTEM ....................................................... 7

2.1 THE BASIC PROCEDURE .................................................................................................. 7
22 MORE ON THE DEFAULT PROGRAMMING .................................................................... 8
2.3 EVENT TYPES .................................................................................................................. 10
2.4 FIELDS ............................................................................................................................... 11
2.5 TEMPLATES ...................................................................................................................... 11
2.6 SOUNDS ............................................................................................................................ 11
2.7 GRAPHICS ........................................................................................................................ 11
2.8 SYMBOLS .......................................................................................................................... 12

3 ADDITIONAL INFORMATION ...................................................... 14

3.1 TESTING YOUR INPUTS ................................................................................................. 14
3.2 CONTROLS & INTERACTIVITY ....................................................................................... 14
3.3 ZONES ............................................................................................................................... 14
3.4 CHOOSING TEXT OR GRAPHICS DISPLAY .................................................................. 14
3.5 HISTORY ........................................................................................................................... 15

4 APPENDIX .................................................................................... 16

4.1 RS232 CONNECTION CABLE ......................................................................................... 16

i Document No. 996-170-000-1, Rev. 1 Getting Started Guide

MORLEY-IAS Visualeyez

1 Introduction

1.1 The System

• Visualeyez is a versatile Alarm Management system and Graphical Display
interface, which interfaces to a network of Morley Visualeyez panels using a
Network Manager Driver program.

• The interface between Visualeyez and the Morley fire Network consists of a
single serial connection that transfers events from all of the panels in the
network to Visualeyez. It will also transfer control and commands back from
Visualeyez to any of the fire panels in the fire network.

• The information in this document is intended to help you set up a system if

you are unfamiliar with Visualeyez. To avoid making this document too big
sometimes there will be references to other documents, or to the Visualeyez
Help system. The Help system is comprehensive and can be accessed from
the Help menu in Visualeyez.

1.2 Maximum System Parameters

Maximum Number of panels in a network 99

Maximum Number of loops per pane 161

Maximum Number of Devices per loop (Apollo) 126

Maximum Number of Devices per loop (System Sensor) 198 (1-99 & 101-199)

1
The sixth loop is used for Morley internal panel ‘inputs’

Page 1 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

1.3 Three Different Versions

• There are three versions of Morley Visualeyez:

Level 1: Basic/Lite

Level 1: Basic/Lite Single panel only

Text and Graphics
No ControlsNo Printing
No History

Level 2: Standard Up to nine panels

Text and Graphics
Fire Panel Controls
Device IsolationsFull History
History Report Printing

Level 3: Advanced Up to 99 panels

Text and Graphics
Fire Panel Controls
Device Isolations
Full History
History Report Printing
Optional connection to additional
systems/networks (at extra cost)

1.4 The Dongle

• Visualeyez is always supplied with a dongle. This is a hardware license key.
You need one dongle for each Visualeyez system. It is permitted to install
and run the software on other PCs for training or creating site configura-
tions. However, the Visualeyez will not connect and talk to a Morley master
panel without a dongle fitted to the PC.

• The dongle plugs in to the parallel port of the PC.

1.5 Upgrading Systems

• Basic/Lite version of Visualeyez is always supplied with a dongle. The system
may be upgraded by the use of an ‘upgrade key’. Upgrade keys can increase the
number of panels from 1 to 9 or 99 and remove the “Lite” feature restrictions.

• To enter the keys select Help > About from the Visualeyez menu. Click on
the Upgrade button at the bottom left of the dialog and enter the key that
corresponds with the Visualeyez dongle’s serial number. A message will
appear if the upgrade is successful – then restart the Visualeyez program.

• Please note that there is normally a charge for upgrades.

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 2 of 16

MORLEY-IAS Visualeyez

1.6 Plug & Play

• Visualeyez is supplied with pre-programmed text pages for all five loops on
ZX fire panels 1 to 4 This effectively gives plug and play operation, but of
course the programming may be changed to whatever you want.

• Of course, it is not possible to provide pre-programmed graphic pages, but

the pre-programmed text pages and the Current Event List may be used for
initial testing and setup. Some applications may not require graphics and may
present the information to the customer in text format. If you want to use panel
addresses other than 1 to 4 then it will be necessary to program the pages for
these panels. This can be done quickly, first by adding the new panel as a
Node in the Network window, then using the Input Programming Wizard,
which is available from the toolbar on the Input Programming List window 2.
Please refer to the Help file for further information on using the wizard.

• The pre-programmed pages each contain four contact/instruction Fields.

These Fields are configured via Field programming and they are common to
all pages. Using Fields to hold information such as contact names and
phone numbers means that global changed can be made just by editing the
single Field definition. So, if a contact phone number changes you can just
edit the Field containing the number and all pages that used the Field will be
updated.

• By default Fire pages use contact Fields 1-4, Pre-alarm uses Fields 5-8, and
so on. These Fields will be programmed with different text for each project
and you can add, edit and delete them as necessary. Please refer to the
Help file for more information on Fields.

1.7 Interface Connection

• A single bi-directional serial interface is used to make a connection between
the Morley panels and Visualeyez. RS232 is the default method of
connection, but an alternative - e.g. RS485 or RS422 - may be used with
additional hardware.

• This single connection carries events from (and controls to) all panels within
a Morley Fire Network. The Morley Network will route events and controls to
the correct destinations within the network.

• The Morley EXP-005 RS232 interface is an optional accessory for the

master panel. Only one RS232 interface is needed and this should be fitted
to the ‘Master’ panel.

• The Visualeyez has a separate software module to control communications

with the Morley fire system. This is called the Morley Network Manager.

2
The amount of default programming has been limited to avoid the need for unnecessarily
large backups

Page 3 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

1.8 Events from the Morley Panels

• This is the information that can be extracted from each Morley panel into
Visualeyez. Certain panel combinations may not support some of these
event types.

Note: Visualeyez will reflect the panel operation. For example, if a fault
occurs during a fire condition then the fault is suppressed. In this case
Visualeyez will indicate a Panel Fault status during the fire condition, and
not give details of the fault.

Event Visualeyez Input

Type
Fire per device Per device
Security alarm (if the panel can signal it) Per device
Pre-alarm Per device
Non-fire input (if the panel can signal it) Per device
Isolation Per device 3
Fault Per device
Contamination (or maintenance) Per device
Buzzer Muted Panel Status IP 1
Alarms Silenced Panel Status IP 2
Detector Loop fault Panel Status IP 13
Individual Sounder circuit fault Panel Status IP 14
Panel in test mode Panel Status IP 7
Panel Sounder circuit fault Panel Status IP 12
Panel General Fire Panel Status IP 4
Panel General Fault Panel Status IP 5
Panel General Isolation Panel Status IP 3
Panel General Pre-Alarm Panel Status IP 6
Panel PSU/battery faults Panel Status IP 10
Morley Network fault Panel Status IP 11
Morley panel “offline” (not responding) Panel Status IP 9

1.9 Device Text

• The text for each device will be taken from the panels and shown in Visualeyez.

3
In the Morley fire network only the first device isolation is signalled across the network
from each panel, so multiple device isolations at a single panel address will appear as
one Device Isolation and one Part Zone Isolated indication.

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 4 of 16

MORLEY-IAS Visualeyez

1.10 Controls to the Morley Panels from Visualeyez

Control

Isolate individual Devices (and de-isolate)

System Evacuate

Panel Evacuate 4

System reset

Panel reset

System silence alarms

Panel silence alarms

Create/Remove Morley Event Types (both transient and non-transient)

• The standard Fire Panel Controls – i.e. Reset, Evacuate, etc – are available
from Visualeyez’s Management menu. Other controls may be setup in the
Controls window or using buttons on the graphics pages.

1.11 The Numeric Reference

• The numeric reference is a unique number which Visualeyez uses to identify
an “input” – i.e. a device - in the Morley Fire Network. This numeric
reference will appear in many places throughout Visualeyez – e.g. in the
Current Event List, when the mouse cursor hovers over a graphic symbol, in
the history, etc. Therefore it is important to know what it means.

• A typical numeric reference will look like this:

2-1-56/0

• This is the reference of a system input – e.g. a fire detector and is made up
like this:

<Node> - <Loop> - <Input> / <Input Type>

• So, in the example above the numeric reference is specifying an input

where:

Node =2

Loop =1

Device address = 56

Input Type =0

4
Panel controls will affect all panels in the network if ‘shared zones’ is set to True in the
Morley panels

Page 5 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

• The Input Type is used for inputs that can have more than one state, such
as a fire detector where Input Type 0 is fire alarm. The other input types for
the Morley panels can be seen in the tables in Section 1.8.

• Status inputs will always have the Loop number set to 0 and Input Type set
to 15, so a PSU fault from panel 4 will have the reference: 4-0-10/15.

1.12 Passcodes
• The default System Passcode is “9898”. It is strongly recommended that
one or more unique Engineer-level passcodes are set-up at installation and
the default passcode is then deleted.

• There is no ‘back-door’ passcode. You must ensure that all systems have a
known Engineer-Level (top level) passcode with the ability to reprogram
other passcodes. If you lose this ‘master’ passcode you will not be able to
gain access to the system.

• Please refer to the Help file for more information on passcodes.

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 6 of 16

MORLEY-IAS Visualeyez

2 Setting up your System

2.1 The Basic Procedure

• Follow this basic procedure when setting up a system from scratch.

• The system has some default text pages already installed – see Section 2.2.
However, for the rest of this section it will be assumed that there is no
default programming and these notes will show how to set up a blank
system. When you follow these steps you may find some default program-
ming exists. You can keep it, amend it, or delete it.

• In the following list topics which are further explained in the help file will be
highlighted in blue.

1 Set up the PC graphics display for 1024 x 768 pixels Large Fonts. This is
very important. Visualeyez is designed to be run in a resolution of 1024 x
768 Large fonts. The software will run with other resolutions, but you may
have problems with some logos an graphics not displaying correctly. Also, if
you prepare graphics on a machine with one resolution setting and then
transfer them to another machine with a different setting you will have
problems.

2 Install the software on the PC. As a minimum the PC hardware will require
an RS232 port for connection to the Morley master panel’s RS232 interface
and a parallel port for the dongle (license key).

3 Install the dongle. You can run the software without the dongle, but it will
NOT talk to the Morley system if there is no dongle.

4 Connect the PC to the Morley RS232 interface unit. This step can be done
later if you wish to configure the PC and graphics “off-line”.

5 Start the software and log onto the system. The default password is shown
elsewhere in this document. You will want to add new Users with their own
passwords at some time, but you do not need to do this at this stage. Look
in the help file for Users and User Profile for more guidance.

6 Now you need to add each panel address in Visualeyez’s Network window
(click the Network icon on the main toolbar). Add an entry for each panel in
the Morley Network. Assign either the Morley IAS System Sensor or the
Morley ZX Apollo/Hochiki/Nittan Node Profile as appropriate.

7. Before programming any inputs with text or graphics a pages you need to do
the following:

Page 7 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

a Create your Event Types

b Create your Text Fields (if using text pages)

c Create your Templates (if using text pages)

d Import Sounds

e Import Graphics (maps – if using graphics pages)

f Create Symbols (for showing input/device status of graphics pages)

8. Now you can program the inputs. There are two quick ways of doing this:

a Assign Event Types to Inputs, assign Templates to input alarm pages,

assign Templates to reset pages, Assign Graphics to inputs, place symbols
on the graphic, or…

b Use the Input Programming Wizard.

2.2 More on the Default Programming

• When Visualeyez is installed there is some default programming of text pages
installed along with the program. Obviously it is not possible to have default
graphics pages, as each site will be different, but some of the text pages are pre-
programmed. By default Visualeyez will display text information for each alarm or
fault, but it is very easy to change this to a graphical alarm display when the
graphics have been created.

• Pages have been pre-programmed for nodes (panels) 1 to 4, loops 1 to 5 on

those nodes, and devices 1 to 126 on those loops. If the system uses more
panels then some additional programming will be necessary. This is a quick
operation, using the Input Programming Wizard or other programming
facilities..

• For each of these devices, the following text pages will be installed:

Fire Alarm

Pre-Alarm

Device Disabled

Fault

• There are also default pages for some panel status events – e.g. battery
fault.

• The default mode of display is ‘Tiled Current Event List and Text Page’ – i.e.
to show the list of Current Events on the left of the screen and the text
instructions for the selected event on the right. This display mode can be
changed (globally) for each Event Type – Open the Program screen and
select ‘Event Type Management’ from the Programming menu. This is where
you can choose to display a graphic instead of a text page.

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 8 of 16

MORLEY-IAS Visualeyez

• Events will automatically clear from the display when they reset at the fire
panel (if they have been accepted by a Visualeyez user). The exception is
fire alarms, which have a separate text page to say that they have been
reset. You can choose to have silent events (they just go into the History –
sometimes useful for faults) or to have events automatically accepted at the
Visualeyez by changing the Event Type attributes (see above).

• On most of the pre-programmed text pages there will be a short list of

instructions. When first installed these will default to phrases like “Fire
Instruction #1”. These instructions use Text Fields and by reprogramming
the field you can change every page that uses that instruction in one stroke.

• To do this, enter the programming screen by clicking on the Program icon

on the main toolbar. You will then see that the menu at the top of the screen
has now gained a ‘Programming’ selection. Drop this menu down and click
on ‘Text Field Management’. Click on the tab for Text Fields and find the field
you want to edit. You can then edit the text for the field. If you don’t want an
instruction to appear then please enter a single space as the text – doing
this will retain the field in position on the page and you will then be able to
use it a later date if you want to add an instruction.

• Alarms currently on display will not alter, but the next time an alarm that
uses this field is displayed it will use the new text.

• If you need to extend the programming to incorporate more nodes, loops or

devices then you can add the same text pages to the new inputs using the
Input Programming Wizard:

1 Open the Programming screen and select the node/loop to be

programmed.

2 Call up the wizard with the icon on the program page toolbar.

3 Click on Load Settings and select “Morley IAS.ipw”

4 On the next screen select the inputs to be programmed. It is not

necessary to enter location/description phrases because, in most
cases, Visualeyez will use the text from the panel.

5 Now click next through all the remaining steps. At the end click
finish and the new devices will be programmed.

• It will be necessary to repeat this step for each node and loop to be
programmed. You can also use this procedure to reprogram inputs or add
graphics pages.

• It is strongly advised that you take a backup of the data before making major
changes, as a mistake may overwrite existing programming.

Page 9 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

2.3 Event Types

• You will need an Event Type for each status of an input. In other words, for
fire detectors you will need an Event Type for Fire, another for Disablement,
etc. This is because the Event Type controls how each different type of
Event is to be handled. For example, you may want a graphic display for a
fire, but just an entry in the Current Event List for a fault.

• Create the Event Types you need. These are used to define how the alarm is
to be displayed, they type of sound that should accompany the alarm etc.
They also define the priority (importance) of the alarm. The text associated
with the Event type is displayed in the Current Event List and the History.

• You can have many different Event Types. In many systems you may have a
single FIRE event type, but if necessary you could have FIRE, HAZARD-
OUS AREA FIRE, and CALL POINT FIRE ALARM.

• To access the Event Types open the Input Programming List from the main
toolbar Program button and then choose Programming > Event Type
Management from the main menu. Refer to the Help file for more informa-
tion.

• These are the default Event Types supplied with the system. The higher in
the list the Event Type is – the higher priority it gets in multi-event situations.

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 10 of 16

MORLEY-IAS Visualeyez

2.4 Fields
• If you are going to use text pages you would be advised to use Fields. They
will make it much easier to make changes later. Fields hold information such
as contact names or phone numbers. This means that global change can be
made to text pages just by editing the Field definition. You should set up the
fields before programming the text pages, as it will be a long job to go to all of
the pages and add them in afterwards. To access Fields Management open
the Input Programming List from the main toolbar Program button and then
choose Programming > Field Management from the main menu. Add Text
Fields as required. Refer to the Help file for more information.

2.5 Templates
• If you are using text pages you will need a different text page for each status
of an input. This is because the text instructions for a fire device in fault will
be different from those for a device in fire.

• Templates may be used to quickly provide common text for many inputs.
Please read about Templates in the Help file.

2.6 Sounds
• Sounds are played when an event occurs. You can have a different sound
for every Event Type, so a fire could have a continuous siren and a fault
could have a single ding-dong sound.

• Visualeyez uses Windows Wave (.WAV) files, so you may add your own
sounds. You can use speech announcements if you wish, recording these in
any Windows program which will record WAV files – e.g. Windows Sound
Recorder. You may also find some additional sounds ready for import if you
select Management > Library Browser from the main menu.

• Sounds are imported in Sound management and assigned to Event Types

in Event Type Management – see the Help file.

2.7 Graphics
• Graphics can be prepared using any CAD or Painting program that is capable
of exporting in native Windows formats – e.g. BMP, JPG, GIF or WMF. They are
then imported into Visualeyez using import in Graphics Management. To
access Graphics Management open the Input Programming List from the main
toolbar Program button and then choose Programming > Graphics Manage-
ment from the main menu.

• We recommend using Windows bitmap (BMP) files. These should be

approximately 1004 (wide) x 556 pixels (high). This area may vary slightly if
the windows scheme does not use the classic layout (like Windows 2000) as
larger Windows title bars will reduce the graphics area. It also will be different
if the system is not using 1024 x 768 Large Fonts (see earlier warning about
the PC’s display resolution).

Page 11 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

• You can export AutoCAD graphics from AutoCAD for use in Visualeyez.
Export them in Windows BMP format. You may need to resize or enhance
them in a painting program – e.g. Photoshop Elements or Paintshop Pro –
before importing them to Visualeyez.

• See the topic Learn About Graphics and Symbols in the Help file.

2.8 Symbols
• Graphics pages are made interactive by adding Symbols or Graphic Buttons
to them. Symbols indicate the status of an input (e.g. a detector) in the
connected system and they can also be used for control – e.g. a detector
symbol can be double-clicked to display a dialog allowing the user to isolate/
disable it.

• See the topic Learn About Graphics and Symbols in the Help file. You will
note that symbols can be Simple or Compound. Compound symbols are
used for inputs with several different states – e.g. fire detectors which can
be in fire, fault, etc. In most cases Visualeyez graphics will need compound
symbols.

• New symbols can be created. You will need a picture for each status of a
symbol, and a picture for the quiescent (off) state. These pictures should all
be the same size and they will normally have the same picture in different
colours. For example, a fire detector symbol may be coloured red for fire,
yellow for fault, white for quiescent, etc. You can specify that the symbol
flashes for some conditions – e.g. fault could use a yellow picture and
disabled could use the same yellow picture, but flashing.

• Symbols can be any sensible size, typically between 16 and 100 pixels.
They do not have to be square, they can be rectangular. Pictures for each
state of the symbols should be the same size. Normally the pictures should
be in BMP format, but if you want to have irregularly shaped symbols – e.g.
circular – then you will need to save the pictures as GIF files with a
transparent background.

• Symbols created on one machine may be exported for use on other

machines.

• When a symbol is placed on a graphics page a dialog is displayed.

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 12 of 16

MORLEY-IAS Visualeyez

This allows you to specify:

1 The input associated with the symbol – i.e. the input (detector) whose state
the symbols will indicate. Note that symbols can be associated with (bound
to) an input (detector), a loop, a node, or a list of inputs. These are specified
in the two top left panels.

2 The location text displayed in the symbol tooltip (when the mouse hovers
over a symbol). Normally this will be left blank and then the text from the
panel will be used.

3 The Zoom Out and Zoom In graphics. Theses are the graphics which the
user can zoom in or out to when they right-click on a symbol.

4 The Controls Type. This is the type of Control dialog – e.g. fire panel control
– which is displayed when the user double-clicks on a symbol.

Page 13 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

3 Additional Information

3.1 Testing Your Inputs

• When you have programmed your inputs you can test them without
connecting to a panel by using the test box in the Morley Network Manager,
which is accessed via the Engineer’s menu on the AMX1.

• Set the node (panel), loop, and device number. Then set the Input Type
(refer to the list in section 1.8). Then click on ON to initiate a test of that
input’s programming.

• The Test Box has a different appearance in the demo and full versions of
Visualeyez.

3.2 Controls and Interactivity

• There are many ways of sending controls to the Morley panels. There are
basic control dialogs available from the Management menu. Pre-pro-
grammed controls can be defined in the Controls window. You can program
symbols on the graphics pages to send controls. See the Help file for more
information on these.

• You can also place graphic control buttons onto the graphics pages. These
are very versatile and a single button can initiate up to 255 actions in the
connected panel(s).

3.3 Zones
• Visualeyez uses the panel (node), loop and input (device) number to
reference devices in the fire panels. Sometimes a customer wants to have a
zone symbol. This can be achieved using a List symbol.

3.4 Choosing Text or Graphics Display

• Some systems will require text alarms displays, some will require graphics
displays, and some may require a mixture of both.

• The type of alarm display is set for each event type. It is a simple matter to
change it. Just go to Event Type management and edit the Event Type you
wish to change. Click on the Alarm Display tab and select the require type of
initial display.

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 14 of 16

MORLEY-IAS Visualeyez

• If you add graphics pages to the default text programming you may wish to
change the display format to the option shown above.

3.5 History
• The History is a very powerful feature and it is recommended that you
explore its features. From the History you can print reports and search for
information on incidents. When commissioning a system all of your tests will
be stored in the History. These can be classified as Test of Commissioning
events and you can produce a report of your tests.

• There is no setting up required for the History, but make sure that the PC
has been set correctly to use the UK date and time format, or else events
may be files incorrectly in the database.

Page 15 of 16 Document No. 996-170-000-1, Rev. 1 Getting Started Guide

Visualeyez MORLEY-IAS

4 Appendix

4.1 RS232 Connection Cable

Getting Started Guide Document No. 996-170-000-1, Rev. 1 Page 16 of 16

Charles Avenue T: +44 (0) 1444 235 556
Burgess Hill F: +44 (0) 1444 254 410
W. Sussex E: [email protected]
RH15 9UF www.morley-ias.co.uk