GalaXy G2/ G3/ GD

Installation Manual

o Settings GalaXy o Linking with iProtect o Keymap

Doc.nr.:28022018

Publication

February 2018,

Keyprocessor BV

Paasheuvelweg 20

1105BJ Amsterdam, The Netherlands

www.keyprocessor.com

Tel.: +31-20-4620700

This manual reflects the knowledge at the above-mentioned time. Keyprocessor works non-

stop to improve her products. For the most recent technical information please contact your

consultant or dealer.

Content overview

Publication .................................................................................................................... 2 Content overview .......................................................................................................... 2 List of images ............................................................................................................... 3 1 Introduction ................................................................................................... 4 1.1 Sticker i-serie ............................................................................................. 4 1.2 Required version ......................................................................................... 4 2 Settings GalaXy .............................................................................................. 5 2.1 If internal RS232 module.............................................................................. 5 2.2 Programmering interne RS232 module ........................................................... 6 2.3 If external RS232 module ............................................................................. 7 2.4 Programming external RS232 module ............................................................ 9 2.5 Neutralize alarm limitation ........................................................................... 10 3 Settings iProtect ............................................................................................. 11 3.1 Add line .................................................................................................... 11 3.2 Add node................................................................................................... 11 3.2.1 Add alarm point ......................................................................................... 11 3.2.2 Add alarm group ........................................................................................ 12 3.2.3 Add alarm output ....................................................................................... 12 3.2.4 Alarm user Group and admittance ................................................................ 13 3.2.5 Card reader ............................................................................................... 13 4 Visualization alarm system in keymap™ ............................................................ 14 4.1 Placing Widgets .......................................................................................... 14 4.2 Alarm point status ...................................................................................... 15 4.2.1 Physical status ........................................................................................... 15 4.2.2 Logical status ............................................................................................. 16 4.2.3 Calculated status ........................................................................................ 16 5 General ......................................................................................................... 18 5.1 Type statuses ............................................................................................ 18 5.2 Maximum number of items in iProtect ........................................................... 18 5.3 Keymap (Floor plan) ................................................................................... 18 5.4 Event ........................................................................................................ 19

List of images

Figure 1: Firmware table ................................................................................................ 4 Figure 2: Galaxy internal RS232 port ............................................................................... 5 Figure 3: iPU-8 and Polyx connection ............................................................................... 5 Figure 4: Pluto connection .............................................................................................. 6 Figure 5: Menu structure Internal RS232 Module ............................................................... 6 Figure 6: Trigger ........................................................................................................... 7 Figure 7: RS232 module ................................................................................................. 8 Figure 8: Connection ...................................................................................................... 8 Figure 9: J2 - Network device ......................................................................................... 8 Figure 10: DIP settings RS232 module ............................................................................. 9 Figure 11: led status ...................................................................................................... 9 Figure 12: Menu structure Externe RS232 Module ............................................................. 9 Figure 13: Dipswitch 8 (RIO-0) ..................................................................................... 12 Figure 14: Physical status ............................................................................................. 16 Figure 15: Calculated status ......................................................................................... 17 Figure 16: Keymap ...................................................................................................... 18

1 Introduction

1.1 Sticker i-serie

This manual describes the linking between iProtect and the GalaXy intrusion system.

This document is based on iProtect version 8.00. It is possible that some features cannot be

used in older versions of iProtect.

1.2 Required version

Attention: deviations from the specified versions, no guarantee can be given concerning

the operation of the link.

GalaXy G2 G3 Dimension

Type 5.12 5.20 5.20

Firmware version 2.17 5.50 6.02

6.04

6.10

6.70

6.75

Combinable with

iProtect™ version

From 6.01 From 7.02 From 7.02

External RS232

module

Necessary Possible, but not

necessary

NO, internal

RS232 module

NO, internal

RS232 port

Version 1.20

2.00

2.01

1.20

2.00

2.01

Figure 1: Firmware table

2 Settings GalaXy

2.1 If internal RS232 module

Connect the internal RS232 connection to a network device (iPU-8 (PRT2), Polyx (PRT4)

or Pluto using a USB-RS232 converter).

Connection plan:

Figure 2: Galaxy internal RS232 port

Pin

nr.

TIA/EIA-568-B Cable color

RS232 Port

Galaxy RS232

iPU-8/ Polyx

1 White/Orange RTS 1 (CTS)

2 Orange CTS 2 (RTS)

3 White/Green - -

4 Blue RX 4 (TX)

5 White/Blue TX 5 (RX)

6 Green - -

7 White/Brown - -

8 Brown GND 8 (GND) Figure 3: iPU-8 and Polyx connection

Pin

nr.

TIA/EIA-568-B

Cable color

RS232 Port

Galaxy USB-RS232

converter

1 White/Orange 1 (CTS) RTS

2 Orange 2 (RTS) CTS

3 White/Green - -

4 Blue 4 (TX) RXD

5 White/Blue 5 (RX) TXD

6 Green - -

7 White/Brown - -

8 Brown 8 (GND) 8 (GND) Figure 4: Pluto connection

Warning! When a Polyx / iPU-8 is replaced for a Pluto, the connection to the Galaxy panel

needs to be changed!

Note: Maximum cable length is 5m.

Up to 1 intrusion panel connection per Network device (up to one USB-RS232

converter per Pluto).

2.2 Programmering interne RS232 module

In the GalaXy center you can program at menu option 56 “Communication” the internal RS232

module.

Choose at menu 56 option 6 (Internal RS232 1). You get a choice out of the next

options:

Menu structure Internal RS232 Module 01=MODE 1=PRINTER

1=DIRECT

2=MODEM 1=TELEFON NUMBER.

2=Choose type 1=Show 2=Pulse

3=Initialisation string

02=FORMAT 1=SIA CHOOSE SIA NIVO 0(0-4)

1=SIA MESSAGES

1=STATUS 2=BLOCKS

2=Microtech 1=SIA

MESSAGES

1=STATUS

2=BLOCKS

03=CUSTOMER NO

4 to 6 digits

04= COMM

SET-UP

1=Baud Rate

2=Data Bits

3=Stop Bits

4=Parity 1=No parity 2=Uneven parity

3=Even parity Figure 5: Menu structure Internal RS232 Module

Select option 1: Mode=Direct (press then on <ESC>)

Select option 2: Format=SIA (Set here the desired events which have to be received by

iProtect™)

Select option 3: enter the customer number (4 to 6 digits)

Note: If no customer number is entered, no SIA messages will be displayed within iProtect!

Choose SIA Level= 4 (*)

Baud Rate = 38400

Data Bits = 8

Stop Bits = 1

Parity = None

(*) Level 0: (default): Basic event information with 4-digit customer number

Level 1: Equal to Level 0, but with 6-digit customer number

Level 2: Equal to Level 1, but with extra event information

Level 3: Equal to Level 2, but with textual description (highest available level for alarm

room)

Level 4: Equal to Level 3, but with addition of commands which can be received by the

GalaXy. This level cannot be used for the Dutch alarm rooms.

After selection of the SIA level, the first trigger will be displayed with the corresponding

status (see table underneath). The most messages which can be sent to a receiver by a

GalaXy panel are subdivided at the triggers. Use the [A]- or [B]-button or press directly

the number for selecting the desired trigger. Press then on the [ent]-button for

adapting the settings of this trigger.

Nr. Trigger Nr. Trigger

1 Panic 11 Reset

2 Burglary 12 Modules/Comms

3 24-hours 13 230VAC errors

4 Security 14 Menu Access

5 Custom Zones 15 Malfunction

6 Fire 16 Memory Zone

7 Error switching on 17 MAX memory

8 Bypassed 18 Zone repair

9 Sabotage 19 RF Supervision

10 Switching on 20 Error Figure 6: Trigger

Do not the installer menu yet.

2.3 If external RS232 module

Install the GalaXy panel according to the manual. For installer codes etc. see also the

corresponding manual.

Unlink temporarily any possible modem/choosers (if version 1.03 or higher).

Connects the iPU-8/Polyx of the iProtect system with the RS232 connector JP2 of the

RS232 module of the GalaXy panel. See figure 7 and 8.

Figure 7: RS232 module

Position of connection JP2 on the RS232 module of the GalaXy panel

Figure 8: Connection

J2 Network device

DB25F

Pin nr.

Description RJ45

Pin nr.

RS232 iPU-8/Polyx USB-RS232 converter

1

2 TXD 2

3 RXD 3

4 TXD RXD

5 RXD TXD

6

7 GND 7

8 GND GND Figure 9: J2 - Network device

Switch on the net voltage of GalaXy panel. Check at ‘DIP’ of the RS232 module the

correct settings:

Switch 1: Off

Switch 2: Off

Switch 3: Off

Switch 4: Off

Switch 5: Off

Switch 6: On

Switch 7: Off

Switch 8: On Figure 10: DIP settings RS232 module

Check the LED’s of the RS232 module. LED2 (red) must burn continuously. LED1 (red)

states the communication quality.

ON (SEC) OFF (SEC) STATUS

0.1 0.9 Good communication

0.9 0.1 Bad communication

0.2 0.2 No communication

1.5 1.5 not configured/recognized Figure 11: led status

2.4 Programming external RS232 module

In the GalaXy panel you can program at menu option 56 “Communication” the external RS232

module.

Choose at menu 56 option 2 (External RS232 module). You get the choice from these

options:

Menu structure External RS232 Module 01=MODE 1=DIRECT

2=MODEM 1=TELEPHONE NOS

2=Choose type 1=Show 2=Pulse

3=X25 PROT

02=FORMAT 1=SIA CHOOSE SIA NIVO 0(0-3)

1=SIA MESSAGES

1=STATUS 2=BLOCKS

2=Microtech 1=SIA MESSAGES

1=STATUS 2=BLOCKS

03=CUSTOMER NO 4 to 6 digits

04=COPYOVERWRIT 1=Received

Data

1=Start

2=Stop

2=Sent Data 1=Start

2=Stop

3=Data Stored

05=COMM SET-UP Figure 12: Menu structure Externe RS232 Module

Select option 1: Mode=Direct (Press then on <ESC>)

Select option 2: Format=SIA (Set here the desired events which must be received each

by iProtect)

Choose SIA Level= 3

Press then a number of times on <ESC> and leave the Master menu. <Again Master

code + <ESC>

Select option 3: enter the customer number (4 to 6 digits)

Note! If no customer number is entered, no SIA messages will be displayed within iProtect!

2.5 Neutralize alarm limitation

(This is valid for internal and external RS232 module.)

Choose at menu 51 option 48. Set the following three options on “0”:

• Number of alarms

• Switch off limit

• Switch on limit

Note! If you do not execute this setting, it can happen that not all alarms will be displayed.

Exit the installer menu.

3 Settings iProtect

3.1 Add line

For being able to make the correct settings for communication between iProtect and a Galaxy

alarm panel, the configuration of the Galaxy panel, which is set by the installer, must exactly

be taken over in iProtect.

Click in iProtect on the menu item Installation | Hardware | Line.

Right-click in the browse window and select ‘Add line’. The detail window opens.

Enter the following data:

Name: Type a logical name

Type: ‘Network device’

Host type: Default Pluto but is depending on used hardware

Active: (check)

Active with node’ s: (check)

Mode: ‘Keyprocessor’

IP-address: IP-address of the network device

Save the data.

3.2 Add node

Click in iProtect on the menu item Installation | Hardware | Node.

Right-click in the browse window and select ‘Add node’. The detail window opens.

Enter the following data:

Name: Specify a logical name

Type: ‘Galaxy ..…..’

Password: Enter the password ‘543210’ < the Remote Service Code of the Galaxy

panel, by default “543210”>

Baudrate: Set to 38400

Address serial port:

- iPU-8: scc02:

- Polyx: tty02:

- Pluto: Pluto external usb #1

Dipswitch 8 (RIO-0): When active RIO 0 will be used (onboard). See chapter 3.2.1

Check ‘Active’.

Save the data.

3.2.1 Add alarm point

Click in iProtect on the menu item Installation | Hardware | Alarm system | Third Party

| Alarm point.

Right-click in the browse window and select ‘Add alarm point’. The detail window opens.

Enter the following data:

Name: Specify a logical name (Copy of the name of the GalaXy alarm point)

Node: Select the node to which this alarm point belongs

Bypassed: No

Enter the number of the alarm point

Dipswitch 8 (RIO-0): Check if RIO 0 is used (onboard). The alarm point numbers are:

iProtect: Alarm

point number

GalaXy: Alarm

point number

SIA: Alarm

point number

9011 0011 0011

9012 0012 0012

9013 0013 0013

9014 0014 0014

9015 0015 0015

9016 0016 0016

9017 0017 0017

9018 0018 0018 Figure 13: Dipswitch 8 (RIO-0)

Save the data

Note! The name of the alarm point needs to be unique in iProtect. Keep in mind when linking

multiple GalaXy intrusion systems to iProtect.

3.2.2 Add alarm group

Click in iProtect on the menu item Installation | Hardware | Alarm system | Third Party

| Alarm group.

Right-click in the browse window and select ‘Add alarm group’. The detail window

opens.

Enter the following data:

Name: Specify a logical name (Copy of the name of the GalaXy alarm group)

Node: Select the node to which this group belongs

Area: Select an access area. This setting is needed when arming and disarming

the (secured)area, using a card reader.

Number: Enter the desired group number.<Block A1=1, A2=2,.. B1=9…

Modus: Select ‘switched off’ at ‘mode’.

Point changes when group off: Select a time zone (example: Office)

< In other words, during which time zone must iProtect monitor the alarm points

for e.g. displaying these statuses on the Keymap>

Write point events to database: Select a time zone (example: Office)

< In other words, during which time zone must iProtect register the alarm points

for e.g. logging these statuses as event and triggering procedures>

Save the record.

Right-click in the treeview on the “Alarm group”.

Add alarm point. < Select the earlier created alarm points at the correct alarm group.

Corresponding with the programming in the Galaxy panel >

Note! Using a GalaXy G3 or GD, one alarm point can be linked under multiple alarm groups.

Using a GalaXy G2, one alarm point can be linked under one alarm group.

3.2.3 Add alarm output

Click in iProtect on the menu item Installation | Hardware | Alarm system | Third Party

| Alarm output.

Right-click in the browse window and select ‘Add alarm output’. The detail window

opens.

Enter the following data:

Name: Specify a logical name (Copy of the name of the GalaXy alarm output)

Node: Select the node to which this alarm output belongs

Mode: Off

Output number: Enter the number of the alarm output

Test the connection.

Note! It is possible to control via iProtect outputs of the Galaxy panel. In account has to be

taken then that this is not operating in contradiction to the function as given with the Galaxy

panel.

3.2.4 Alarm user Group and admittance

The alarm user Group determines whether the user may arm or disarm the security area.

Open in iProtect the menu item Installation | Hardware | Alarm system | Third party |

Alarm user group. The detail window opens.

Enter the following data:

Name: Specify a logical name

Arm: check if allowed to arm the security area

Disarm: check if allowed to disarm the security area

Save the record.

Click in the browse window and click the plus sign of the ‘alarm user group’ and select

'Area list'. Check the desired areas and save.

Open in iProtect the menu Access | Settings | Admittance to add the Alarm user group

to an existing Admittance

Save the record.

3.2.5 Card reader

Open in iProtect the menu item Installation | Hardware | Reader.

Select a card reader which will be used to arm or disarm the security area. The detail

window opens.

Open the Tab Security Area:

Show security area status on LED: Select a desired security area

< The LED from the card reader will blink when security area is Armed>

Arm security area: Select a desired security area

Disarm security area: Select a desired security area

Open the Tab APB:

Select the undefined access area “Outside for access control” at “From area”.

Select the access area you enter at “To area”.

Save the record.

4 Visualization alarm system in keymap™

4.1 Placing Widgets

Create under General | Settings | Keymap a floor map.

Click in the frame of the detail window and load a picture of the building or from a floor

where detectors are installed. Save the record. The image will now be displayed as a

background image for the alarm visualization.

Loading the background image for the floor map (Dutch working station)

In the treeview underneath the new record of the floor map the record “Widget

positioning” has appeared. Click on this record. The detail window ‘Widget positioning’

opens.

By means of Widgets you can now display each sort status of each / each alarm point.

Repeat for each Widget the next steps:

1. Right-click on the background image and choose ‘Security message (third party)’.

Choose ‘alarm point’ and then the sort status, which you want to have displayed.

See for this the next chapter about ‘alarm point statuses’.

2. The default symbol for the momentary status of a default alarm point appears.

Drag with the mouse the Widget on the desired place and set the size of the

Widget.

3. Click on the tab sheet ‘Widget control’. Select at ‘column value’ the alarm point, of

which the status has to be shown. – You can adapt at ‘column name’ the status

once more (you see here a bigger number statuses and parameters from which you

can choose). On top of this on the tab sheets you can set or determine the size and

position of the Widget exactly, that the status is not displayed with a symbol, but

textual.

Placing Widgets on the background image. In this example three statuses are stated by a symbol (e.g. )

and – on the right - textual (e.g. ‘sabotage closed’).

You can set comparable statuses of alarm groups.

Which default symbols represents which value of a alarm point or alarm group status,

can you view at General | Settings | Keymap | Icon assignment.

Open at General | Overviews the new floor map. Check whether changes at the

detectors are shown in the right way.

4.2 Alarm point status

You can have 3 sorts status of an alarm point (detector) shown:

• Physical status (or ‘point status’ in the detail window of the alarm point)

• Logical status and

• Calculating status (or ‘alarm status’ in the detail window of the alarm point)

4.2.1 Physical status

The physical status states which resistance the system measures in the detector circuit:

Resistance

E.g. Default

icon color ‘Physical status’

message in iProtect™

Description

0Ω or endless

‘Sabotage closed’ Sabotage to detector

Normal (operative

low)

4.700Ω ‘Loop closed’ Detector changes resistance – regular detector operation

Open (operative

9.400Ω ‘Loop opened’ Detector changes resistance – regular detector operation

high)

unknown Figure 14: Physical status

Example values are valid for a DEOL 4k7k

The physical status can be separated thus into 3 groups:

• Extreme resistance values which can only be explained by sabotage of the

detector (‘Sabotage closed’/ ‘Sabotage opened’), this alarm situation will be

notified with the highest priority – independent of e.g. the detector operation

• Unusual resistance values which cannot be explained by normal detector

operation and e.g. can hint on cable contact (‘Low resistance’/‘High resistance’)

• Resistance values, which the detector can assume at regular function (‘Normal’/

‘Open’)

4.2.2 Logical status

The logical status is a first interpretation of the resistance value based on the sort detector and

entered parameters (e.g. ‘bypassed’ on ‘yes’):

• Idle: the detector does not notice an insecure situation

• Active: the detector notices an insecure situation, but his alarm group does not

stand on ‘armed’

• Alarm: the detector notices an insecure situation and his alarm group stands on

‘armed’

• Bypassed: the messages of this detector will be ignored by the system

• Sabotage: e.g. someone opens the housing of the detector without permission

• Local alarm

• Hold-up alarm

• Unknown

4.2.3 Calculated status

The calculated status is a combination of the logical status of the detector and the en de

arming of the alarm group of the alarm point:

• Idle: the alarm group of the alarm point is not standing anymore on “armed’ and

the alarm point does not send an alarm message

• Activated: the alarm group of the alarm point stands on “armed’ and the alarm

point sends no alarm message

• Active: the alarm group of the alarm point does not stand on ‘armed’, the alarm

point has passed an alarm message and the alarm group has not been reset

• Alarm: the alarm group of the alarm point stands on armed’, the alarm point has

passed an alarm message and the alarm group has not been reset

• Bypassed: the alarm group of the alarm point stands on ‘bypassed’

Overview:

Calculated status Alarm group armed? Message of alarm point?

REST NO NO

SWITCHED ON YES NO

ACTIVE NO YES

ALARM YES YES

BYPASSED BYPASSED/NO NO

BYPASSED/ SWITCHED ON BYPASSED/YES NO

BYPASSED/ACTIVE BYPASSED/NO YES

BYPASSED/ALARM BYPASSED/YES YES Figure 15: Calculated status

5 General

5.1 Type statuses

Physical status (the real loop status)

• Open (resistance value)

• Closed (resistance value)

Logical status (the translation of the physical status to an alarm situation)

• Switched on,

• in alarm,

• tamper,

• etc

Calced status

• The translation of [physical + logical] in combination with the (alarm-) status of the

group in which the zone sits. At switching off the block the point which has been in

alarm, will automatically be reset.

5.2 Maximum number of items in iProtect

The numbers are determined by iProtect. See iProtect; Installation; Database; Table

information:

- Alarmgroup

- Alarmpoint

- Alarmgroupalarmpoint

- AlarmExternal

5.3 Keymap (Floor plan)

Keymap Widgets

Alarm External (MODE) 0) Off; 1) On

Alarm External (STATUS) 0) Off; 1) On

Alarm Group (STATUS) 0) Switched off; 1) switched on; 2) Partly

switched on

Alarm Group (MODE) 0) Switch off; 1) switch on; 2) switch

partly on

Alarm Group (ALARM) 0) Normal; 1) Alarm

Alarm point (CALCEDSTATUS)

0) Rest; 1) Switched on; 2) Active; 3)

Alarm; 4) Bypassed; 5) Bypassed/switched

on; 6) Bypassed/Active; 7)

Alarm/Bypassed

Alarm point (LOGICALSTATUS) 1) Sabotage; 2) Alarm; 3) Normal 4) hold-

up alarm; 5) Local alarm; 7) bypassed;

10) Active

Alarm point (MODE) 0) No; 1) Yes

Alarm point (PHYSICALSTATUS) 1) Sabotage closed; 3) Loop closed; 5)

Loop opened (alarm); 6) Sabotage opened Figure 16: Keymap

5.4 Event

Go to the menu: General Settings Event.

Click in the search window on ‘Search’.

Within iProtect the next event types can be used:

• Alarm point: Status changed

• Alarm point: Bypass status changed

• Alarm point: Mode changed

• Alarm output: Status changed

• Alarm output: Mode changed

• Alarm group: Status changed

• Alarm group: Mode changed

• Alarm group: Alarm changed