Installation instructions Modular controller line. Pluto Orion

Transcription

1 Installation instructions Modular controller line Pluto Orion Document date:

2 About this publication July 2018, Keyprocessor BV Paasheuvelweg BJ Amsterdam The Netherlands Tel.: +31 (0) This instruction manual is based on knowledge relevant at the above-mentioned date. Keyprocessor is constantly working towards the improvement of its products. For information on the most recent technical state of affairs, please contact your consultant or distributor. 2 Table of contents About this publication... 1 Table of contents... 2 List of images Introduction General Mounting Power supply connection and tamper contact Stacking connector Pluto Applications Required software versions Connections Status LED Support in offline situation Pluto connection options Connecting with Orion Serial connection (RS-232) Maintenance page Pluto Network settings Orion Applications Required versions Functions and support Orion connected to the Pluto Orion RS485 bus communication (kpbus) Orion functional replacement for the Orbit reader Connections Description imprint Orion Status LED SD-card functionality Inserting the SD card Calamity cards Support in offline situation Orion connection options Connecting with Orion Connecting card reader RS485 card reader Connection of RS485 card reader... 25

3 Wiring requirements Clock- data / Wiegand card reader Connecting the card reader Wiring requirements Bus configuration with card reader Pluto Orion as starting point of kpbus Connection of kpbus Polyx as communication starting point Connection of kpbus Connection via an adapter board Wiring requirements kpsensor bus connection Wiring requirements Default inputs and outputs Monitored inputs (A1 A6) Orion as replacement for the Orbit reader Connecting to a network controller Controller <> Orion PRT1 - RS Wiring requirements Default inputs and outputs Pluto-Orion as replacement for the ipu Diagnostics Initiating Pluto diagnostics Polyx/iPU-8: Connecting across the Console port Initiating ipu-8 diagnostics Initiating Polyx diagnostics Orion as functional replacement for the Orbit reader Multiple Orions on a single data line (bus) How to Installation Pluto New Orion on existing Pluto New RS485 reader on existing Orion New Orion on existing Polyx Replace Polyx for Pluto and Orion Replace Polyx (2x kpbus) for Pluto and two Orions Replace ipu-8 for a Pluto with four Orions Pluto - Make factory default Pluto Removing iprotect data Technical data Pluto Orion Declaration of conformity Pluto Orion controller Technical drawings Pluto/Orion setup with network connection and power supply Pluto/Orion with Sirius RS485 and IO Pluto/Orion with Sirius clock-data/wiegand and I-O Pluto/Orion with IO, Sirius Clock-data/Wiegand and Orbits Pluto with power supply and USB-RS232 converter Pluto/Orion with kpbus Orion with kpsensor bus Pluto Orion stacked with 8x RS485 Sirius-i readers Pluto Orion with clock-data or Wiegand readers Pluto Orion with RS485 readers & kpbus combi Polyx with kpbus

4 List of images Figure 1: Mounting controller... 7 Figure 2: Tamper contact... 8 Table 3: Power supply- and tamper connection... 8 Figure 4: Stacking connector... 8 Tabel 5: Required software version Pluto... 9 Figure 6: Front side Pluto Figure 7: Rear side Pluto Table 8: Pluto connections Table 9: Pluto status LED Table 10: Support in offline situation Figure 11: Example of connection with Orions Figure 12: Pluto serial connection Figure 13: Maintenance page Pluto Figure 14: Networks settings Pluto Table 15: Required versions Orion Table 16: Functions and support Orion-Pluto Table 17: Functions and support Orion-kpBus Table 18: Functions and support Orion as functional replacement unit reader Orbit Figure 19: Orion connections front Figure 20: Orion connections rear Table 21: Port description Orion Figure 22: Imprint Orion rear Figure 23: Imprint Orion front Table 24: Orion reader & IO Table 25: Orion Status-led Figure 26: Inserting the SD-card Table 27: Support in offline situation Orion Table 28: Support in offline situation Orion - Events Table 29: Support in offline situation Orion - INputs Table 30: Support in offline situation Orion - Outputs Table 31: Support in offline situation Orion - Reader Figure 32: Connecting with Orions with Pluto Figuur 33: Connecting with Orions kpbus Figure 34: Pluto with RS485 card reader Figure 35: Polyx with RS485 card reader Table 36: Connection RS485 reader Table 37: Wiring requirement RS-485 card reader Figure 38: Orion with Clock- data / Wiegand reader Table 39Connection clock- data Wiegand card reader Table 40: Wiring requirements card reader Figure 41: Pluto/Orion - kpbus Figure 42: Pluto/Orion - kpbus with Clock- data / Wiegand and RS485 reader Table 43: Connection kpbus (1) Figure 44: Polyx - kpbus Figure 45: Polyx - kpbus with Clock- data / Wiegand and RS485 reader Table 46: Connection kpbus (2) Tabel 47: Wiring requirements kpbus Tabel 48: Connection kpsensor bus Figure 49: Orion - kpsensor connection Table 50: Wiring requirement kpsensor bus Table 51: Default in- and outputs Reader & IO Table 52: Default in- and outputs Reader & IO Table 53: Resistor values monitored inputs Figure 54: ipu-8 with Orions

5 Figure 55: ipu-8 with Orbits Figure 56: Polyx with Orbits Figure 57: Polyx with Orions Table 58: Connection Orion as replacement unit reader Orbit Table 59: Wiring requirements Orion as replacement unit reader Orbit Table 60: Default in- and outputs Orion as replacement unit reader Orbit (1) Tabel 61: Standaard in- en uitgangen Orion als vervanger van de lezer Orbit (2) Figure 62: Pluto and Orion with 2 Orbits Figuur 63: ipu-8 with 2 Orbits Figure 64: Pluto diagnostics (1) Figure 65: Pluto diagnostics (2) Figuur 66: Serial Adapter

6 1 Introduction This instruction manual covers the entire range of Keyprocessor modular controllers. One or more software versions and hardware revisions numbers are specified in every modulerelated chapter. These versions are important when it comes to support for the product. 6

7 2 General 2.1 Mounting Mount on a 35mm DIN rail type O profile. Mount the rail to a wall or inside a secure casing. Place the modular controller against the rail and click it into place. Mounting the modular controller onto the rail. Figure 1: Mounting controller NOTE For every modular controller, note the location, serial number and/or MAC address of the device. This information can be found on top of the device, just below the LED. 7

8 2.2 Power supply connection and tamper contact The controller requires a power feed. For this purpose, use an orange four-pole power terminal or the stacking connector. The tamper contact T must be connected to the GND terminal. T SW-1 Figure 2: Tamper contact Connector D Symbol Description Earth ground GND (digital ground) + 12V 24VDC T Tamper contact Table 3: Power supply- and tamper connection The Pluto can be connected to a 12VDC or 24VDC power supply. Higher input power results in lower power consumption and ensures cost-efficient wiring requirements as smaller-diameter conductors are needed. The power supply must conform to SELV directives. 2.3 Stacking connector The modular controller is fitted with a stacking connector terminal on either side. This connector links together both the power and the communication feeds between the modular controllers. Sections 4.1 and 7.1 specify specific conditions for the use of this connector. Operation: The supplied stacking connector must be inserted according to the below image: Orion side (short pins) Pluto side (long pins) Figure 4: Stacking connector 8

9 3 Pluto The Pluto is an extremely powerful controller with a multicore processor, a secure bootloader (u-boot), and a Linaro release with Linux kernel. 3.1 Applications Depending on the situation, the Pluto can be used in a range of different ways. The Pluto can be used if: More flexibility is required More redundancy is required End-to-End security is required Maximum security is required 3.2 Required software versions In order to guarantee optimum performance, the following software versions are required: Version Supported iprotect Support Linux Ubuntu Rootfs V4.22 Tabel 5: Required software version Pluto 9

10 3.3 Connections C C D B G E A Figure 7: Rear side Pluto F Figure 6: Front side Pluto Port Description A USB 2.0 port (x2) B Stacking connector for Orions C Status LED D Power input E USB OTG console port F Network port G Stacking terminal (for future use) Table 8: Pluto connections 3.4 Status LED With the RGB LED, the current mode of the Pluto can be determined at a single glance. The Pluto s status LED is described in the table below: Table 9: Pluto status LED Port C Colour of the LED Description Blue No connection Red No active Node manager Yellow Line active, Node(s) inactive (0%) Green Line and Node(s) active (100%) 3.5 Support in offline situation When a Pluto no longer has a network connection with the server, an offline situation arises. In order to guarantee autonomous operation, local data storage is necessary (including cards with 10

11 valid access rights). And in this offline situation, the events of inputs, (lock control) outputs and cards may not be lost. The maximum numbers are described in the table below: Pluto storage (FIFO) Nr. Description: Maximum per Pluto: 1 Cards with valid access rights Events Table 10: Support in offline situation 11

12 4 Pluto connection options The Pluto s various connection options are described in this section. 4.1 Connecting with Orion The right-hand terminal on the Pluto is not designed for use with a controller. Connecting a modular controller (e.g. an Orion) to the LED side of the Pluto will not damage it, however, communication with the device will not be possible. 4x Stacking connector Orion-4 Orion-3 Orion-2 Orion-1 Pluto PRT2 L PRT2 L PRT2 L PRT2 L N Front Figure 11: Example of connection with Orions When it comes to connection, the following conditions are important: when inserting stacking connectors, always ensure the power is off depending on the power feed being used (at least 75W), a maximum of four Orions can be interconnected to one another to the left of the Pluto, using the stacking connector (see Figure 4: Stacking connector) if the stacking connector is used to supply the Orions with power and the door controllers collectively draw more power than 50W, the C (GND) on the last Orion, beside the High- Power output, must be separately wired to the power supply (-). 12

13 4.2 Serial connection (RS-232) If a connection in series is preferred, a USB-to-RS232 converter (recommended by Keyprocessor, part number ) must be used. Only one USB-to-RS-232 converter can be used per Pluto (See chapter 14.5). USB Rear RS-232 Figure 12: Pluto serial connection 13

14 5 Maintenance page Pluto The Pluto has its own maintenance page. This maintenance page includes assistance with network settings as well as system testing. The Pluto s default IP address is In order to access the maintenance page, enter the following into your browser: When the page opens, it will display a login screen. Once the right username and corresponding password have been entered, the system status page will be displayed. Default login: Username: controller Password: Pluto The following page is displayed: Figure 13: Maintenance page Pluto NOTE When iprotect connects to the Pluto, the default password will expire. The new login password will be displayed in the iprotect line in the admin page. 5.1 Network settings Network settings, e.g. IP address settings, can be manually configured. To do so, click on the Network settings button and enter the desired settings into the device field. 14

15 Figure 14: Networks settings Pluto Once saved, the new settings will take immediate effect and the Pluto will only be accessible using the new IP address. 15

16 6 Orion 6.1 Applications The Orion can be used for a range of applications. Extra features include: End-to-End security (RS485 card reader) RS485 communication bus (kpbus) Replacement of existing Orbit reader Additional functionality 6.2 Required versions In order to guarantee optimum performance, the following versions are required: Version Supported Hardware iprotect version Orion firmware Applicatie: Bootloader Functional replacement for Orbit reader; kpbus communication Rev d Rev e 8.03 Applicatie: Bootloader Applicatie: Table 15: Required versions Orion Functional replacement for Orbit reader; kpbus communication; calamity card (SDcard); Sirius Pincode based on Clockdata/ Wiegand protocol; NO/NCoutput behavior; provisioning; connection to Pluto Depending on revision bits, the measured values of the monitored input (ADC) have been changed. Rev d Rev e Rev f Functions and support Depending on the desired application of the Orion, a range of functions are available. Below is a list of functions. 16

17 6.3.1 Orion connected to the Pluto Type of controller Pluto connected: Number Connection Digital input 2 T1, T2 Digital output 8 O1, O2, O3, O4, O5, O6, H1 and H2 Monitored inputs (ADC) 6 A1, A2, A3, A4, A5, A6 Orion override input 1 T Wiegand/ABA card reader 2* LD, D0, D1, C and V+ kpsensor 2** C, S Location buzzer Yes Status LED Yes MicroSD card - RJ45 PRT1 RS485 card reader or Orbit RJ45 PRT2 kpbus communication or RS485 card reader or Orbit Indoor temperature sensor Yes Power supply measurement Yes Power measurement reader Yes Power consumption readers Yes H1 and H2 overload detection Yes Table 16: Functions and support Orion-Pluto Orion RS485 bus communication (kpbus) Type of controller Polyx, Pluto connected: Number Connection Digital input 2 T1, T2 Digital output 8 O1, O2, O3, O4, O5, O6, H1 and H2 Monitored inputs (ADC) 6 A1, A2, A3, A4, A5, A6 Orion override input 1 T Wiegand/ABA card reader 2* LD, D0, D1, C and V+ kpsensor 2** C, S Location buzzer Yes Status LED Yes MicroSD card For emergency card use RJ45 PRT2 kpbus communication Indoor temperature sensor Yes Power supply measurement Yes Power measurement reader Yes Power consumption readers Yes H1 and H2 overload detection Yes Table 17: Functions and support Orion-kpBus 17

18 6.3.3 Orion functional replacement for the Orbit reader Type of controller connected: ipu-8, Polyx or Pluto Number Connection Digital input 8 A1, A2, A3, A4, A5 A6, T1, T2 Digital output 4 H1, H2, O2, O5 Wiegand/ABA card reader 2 LD, D0, D1, C and V+ Status LED Yes RJ45 PRT1 RS422 communication with controller Indoor temperature sensor Internal only Power supply measurement Internal only Power measurement reader Internal only Power consumption readers Internal only H1 and H2 overload detection Internal only Table 18: Functions and support Orion as functional replacement unit reader Orbit * D0 and D1 are shared inputs. If no card reader is used, D0 and D1 can be used as digital inputs. ** Only the combined Temperature & Humidity sensor supplied by Keyprocessor is supported. 18

19 6.4 Connections The connection ports on the Orion are described in this section. Options depend on the application and the method of connection. E F G G F E D H I H C J B K PRT1 Figure 20: Orion connections rear PRT2 Figure 19: Orion connections front A L Port Description A PRT1 B Reader 1 C IO 1 D Power input E Status LED F MicroSD slot G End of line jumper H Stacking connector I RS485 and kpsensor bus J Reader 2 K IO 2 L PRT2 Table 21: Port description Orion 19

20 6.4.1 Description imprint Orion The connection ports and imprints on the Orion are illustrated below: C D B K A Figure 22: Imprint Orion rear L J I L Figure 23: Imprint Orion front Reader & IO-1 Connector: A PRT1 Description Communication port Connector: B Description Connector: C Description C GND (digital ground) A1 Monitored input 1 T1 Digital input (Override card reader) A2 Monitored input 2 LD Card reader LED operation A3 Monitored input 3 D0 DO/Data or Digital input C Digital ground D1 D1/Clock or Digital input H1 High Power output 1 O1 Digital output 1 C Digital ground C GND (digital ground) O2 Digital output 2 +V Power feed card reader O3 Digital output 3 Connector: D Description Earth ground - GND (digital ground) + Orion power input (12-24VDC) T Tamper input 20

21 Connector: I A B C or CC S Description kpbus (RS485) kpbus (RS485) GND (digital ground), for data use only. kpsensor Reader & IO-2 Connector: J Description Connector: K Description C GND (digital ground) A4 Monitored input 4 T2 Digital input (Override card reader) A5 Monitored input 5 LD Card reader LED operation A6 Monitored input 6 D0 DO/Data or Digital input C GND (digital ground) D1 D1/Clock or Digital input H2 High Power output 2 O4 Digital output 4 C GND (digital ground) C GND (digital ground) O5 Digital output 5 +V Power feed card reader O6 Digital output 6 Connector: L Description PRT2 Table 24: Orion reader & IO Communication port NOTE the Orion must not be connected directly to the network. Doing so may result in severe damage to the device, including loss of functions. 6.5 Status LED With the RGB LED, the current mode of the Orion can be determined at a single glance. The Orion s status LED is described in the below table: Colour of the LED Light blue Blue Blue Pink Pink Orange Green Red Red Orange Green Green Table 25: Orion Status-led Port D Description Bootloader : Connecting to iprotect <Checking MD5> Bootloader : Starting Bootloader : Programming firmware (Or violet) Bootloader : No valid application to start Application : Format SD card Application : Checking SD card (initialisation) Application : Calamity mode Application : When using no SD card, the LED will flash red if the device cannot communicate with the network controller. Application : If the LED displays a solid red light, the Orion has detected a surge or short circuit. This also means that the Orion is not communicating with the network controller. Application : If the LED displays a solid amber light, the Orion has detected a surge or short circuit, but is nevertheless communicating with the network controller. Application : The LED will display a solid green light when the Orion is communicating with the network controller and no input or output anomalies are detected. Application : If the location buzzer of the Orion is activated, the green status LED will flash fast. 21

22 6.6 SD-card functionality Additional functionality is available when using an SD card in the Orion. When connecting clock data- or Wiegand card readers to the Orion and when e.g. there is no communication (kpbus) with the network controller, the local operation of the access control will be guaranteed. NOTE! When using RS-485 card readers on a stacked Orion-Pluto combination (See figure 32), the Orion SD card has no function concerns the operation of the card reader. The entire communication is in this case handled by the Pluto Inserting the SD card Part number: Figure 26: Inserting the SD-card 1. Remove the power from the Orion before inserting the SD card. 2. The copper slots of the SD card must be facing inwards for inserting the SD card. The card must be clicked without any pressure. See Figure 26. Note! Inserting the SD card incorrectly could cause serious damage to the Orion or SD card Calamity cards Calamity cards are cards that need access to a door(s) when there is no communication with the Network Controller (offline). In an offline situation, the Orion will function fully independently. If a user has a calamity priority, which is created within iprotect in the card dialog, there will be no noticeable issues for the user. If the Orion communicates with the Network Controller, all events will be sent to iprotect Support in offline situation The following features are supported during the Offline situation: The following table shows the maximum numbers: Storage SD-card Nr. Description: Maximum per Orion: 1 Cards with valid access rights Events Table 27: Support in offline situation Orion 22

23 The following table shows all the events: Events Nr. Description 1 Push button access 2 Push button no access 3 Card access 4 Card no access 5 Card no calamity card 6 Emergency door release activated 7 Emergency door release deactivated Table 28: Support in offline situation Orion - Events The following table shows all the inputs: Inputs Nr. Connection: Description: Reader nr. Invert (NO/NC) 1 A1 Loop (enable) Reader 1 Yes 2 A2 Push button 3 T1 Emegency door release 4 A4 Loop (enable) Reader 2 5 A5 Push button 6 T2 Emegency door release Table 29: Support in offline situation Orion - INputs The following table shows all the outputs: Outputs Nr. Connection: Description: Reader nr. Invert (NO/NC) 1 H1 Door lock Reader 1 Yes 2 O1 Output 3 O2 Alarm 4 O3 Output 5 H2 Door lock Reader 2 6 O4 Output 7 O5 Alarm 8 O6 Output Table 30: Support in offline situation Orion - Outputs The following table shows the reader: Reader Nr. Description: Protocol: Kaartdata interpretation: Pincode function offline 1 Reader 1 Clock data/ Wiegand Max. 1 Pincode 2 Reader 2 Clock data/ Wiegand Max. 1 switched off Table 31: Support in offline situation Orion - Reader Note: It is possible to use combined input or output by a reader. Consider a door with a card reader on both sides. 23

24 7 Orion connection options The Orion s various connection options are described in this chapter. 7.1 Connecting with Orion When it comes to connection, the following conditions are important: When inserting stacking connectors, always ensure the power is off. Depending on the power feed being used (at least 24VDC 75W), a maximum of four Orions can be interconnected to one another by means of stacking connectors. If stacking connectors are used to supply the Orions with power and the door controllers collectively draw more than 2A, the C (GND) on the last Orion, beside the High-Power output, must be separately wired to the power supply (-). When connecting Orion(s) to a Pluto, the kpbus should not be connected externally. See figure 32. When linking only Orions, the kpbus must be connected externally. See figure 33. Stacking connector (communication (USB) and power) Orion-4 Orion-3 Orion-2 Orion-1 Pluto PRT2 L PRT2 L PRT2 L PRT2 L N Front Figure 32: Connecting with Orions with Pluto Stacking connector (power) kpbus Orion-4 Orion-3 Orion-2 Orion-1 A B CC A B CC A B CC A B CC PRT2 X L PRT2 X L PRT2 X L PRT2 X L Figuur 33: Connecting with Orions kpbus Front 24

25 7.2 Connecting card reader RS485 card reader Choosing the option to connect RS485 card readers to the controller offers the following advantages: Key information from the card reader is transferred to the controller. The card reader is always publicly accessible, while the controller is located in a secure and concealed area. This means that the settings required for reading cards are located in the controller instead of in the card reader. Communication between cards and the system can be secured by means of AES encryption. When (the maximum of) four Orions are connected to a Pluto (see figure 32), a maximum of eight RS485 card readers can be connected. Orion X Pluto Polyx PRT2 L N USB A PRT1 N D Max. 4x Orion Front RS485 Rear Max. 4x Orion RS485 RS485 Figure 34: Pluto with RS485 card reader Figure 35: Polyx with RS485 card reader Connection of RS485 card reader Orion PRT1(A)- 2(L) TIA/EIA-568-B Sirius i-serie Figure T-568B Rev. d - e Rev. F Nr. Description Wire color Sticker Description 1 B White/Orange 2 B 2 A Orange 1 A 3 B (Z) White/Green 2 B 4 12VDC 10VDC Blue Vcc Vcc 5 GND White/Blue GND GND 6 A (Y) Green 1 A 7 GND White/Brown GND GND 8 GND Brown GND GND Table 36: Connection RS485 reader 25

26 Wiring requirements The wiring required between the card reader and the Orion is listed below: Cable Communication Remote Communication between protocol UTP Cat5e RS m Orion and Sirius i-series card reader Clock- data / Wiegand card reader Table 37: Wiring requirement RS-485 card reader In virtually all configurations, you have the option of connecting a Clock- data / Wiegand card reader to either side of the Orion, except if an RS485 card reader is connected. It is not possible to connect a second card reader to any one side of the Orion. Orion Pluto J B PRT2 N USB PRT1 Front Rear Clock data Wiegand Clock data Wiegand Figure 38: Orion with Clock- data / Wiegand reader Connecting the card reader Orion reader & IO-1/2 TIA/EIA-568-B Sirius i-serie Rev. d - e Rev. f Description Wire color Sticker Description D0 White/orange 3 D0 - Orange - - D1 White/green 4 D1 V+ (12VDC) V+ (10VDC) Blauw Vcc Vcc LED White/blue 5 LED - Green - - C White/brown GND GND C Brown GND GND Table 39Connection clock- data Wiegand card reader 26

27 Wiring requirements The wiring required between the card reader and the Orion is listed below: Cable Communication Remote Communication between protocol UTP Cat5e Wiegand 120m Orion and Sirius i-series card reader Clock/Data 50m Table 40: Wiring requirements card reader 7.3 Bus configuration with card reader If an Orion is connected in bus configuration (kpbus): communication must be established via the black 4-pole screw connector a maximum of eight Orions per kpbus applies the maximum cable length is 600m the power feed does not run across the kpbus every Orion must be provided with its own power feed the serial number and location of every Orion must be noted (see section 2.1) 27

28 7.3.1 Pluto Orion as starting point of kpbus If the Orion is linked to the Pluto and the relevant Orion is used as the beginning of a kpbus, then: The Orion connected to the Pluto is not included in the number of Orions in the kpbus. A maximum of one kpbus can be established per Orion. So, if four Orions are stacked with a Pluto, four kpbuses can be established (see figure 32). A RS485 card reader cannot be connected to PRT2. A clock data / Wiegand card reader can be connected on both sides of the Orion. if there is no clock data/ Wiegand reader is connected to the "Reader & IO 1" side, a RS485 card reader can be connected to PRT1, see figure 41. EOL Jumper kpbus Orion I A B CC Pluto Max. 32x Orions Max. 32x card readers PRT2 X N I I I A B CC A B CC A B CC Max 8 The last Orion must have an EOL Jumper. X X X PRT2 PRT2 PRT2 Figure 41: Pluto/Orion - kpbus 28

29 kpbus Orion I A B CC Pluto PRT1 Max. 32x Orions Max. 32x card readers PRT2 X N I I I A B CC A B CC A B CC Max X X X PRT2 PRT2 PRT2 Figure 42: Pluto/Orion - kpbus with Clock- data / Wiegand and RS485 reader Connection of kpbus I Illustration of kpbus connection NOTE PRT2 A B C S X Orion (I) A B C S TIA/EIA-568-B Colour of the cable Orion (I) A B C S B White/orange B A Orange A B White/green B - Blue - - White/blue - A Green A C or CC White/brown C or CC C or CC Brown C or CC Table 43: Connection kpbus (1) If the kpbus begins with an Orion, the start and the end of the kpbus must have an EOL jumper, see Figure 41: Pluto/Orion - kpbus. 29

30 7.3.2 Polyx as communication starting point Polyx Max. 16x Orions Max. 32x card readers kpbus-1 N D Polyx the starting point of kpbus at all times! I A B C I A B C I A B CC A B CC A B A CC B C Max. 8 The last Orion must have an EOL Jumper. X X X PRT2 PRT2 PRT2 Figure 44: Polyx - kpbus Polyx max. 16x Orions max. 32x card readers kpbus-1 N D I I I A B CC A B CC A B CC Max J J J X X X PRT2 PRT2 PRT2 Figure 45: Polyx - kpbus with Clock- data / Wiegand and RS485 reader 30

31 Connection of kpbus When using shielded cable, one end of the cable s metal sheath must be attached to the earth ground connection in the system cabinet. Afbeelding T-568B Polyx PRT1 2 TIA/EIA-568-B Orion (I) A B CC S Nr. Description Wire color 1 RxA White/orange B 2 RxB Orange A 3 TxZ White/green B 4 +12Vdc Blue - 5 Orbit sense White/blue - 6 TxY Green A 7 GND White/brown C or CC 8 GND Brown C or CC Table 46: Connection kpbus (2) I PRT2 A B CC S X Illustration of kpbus connection NOTE! The Polyx is always the starting point of a kpbus. Add an EOL jumper to the end of the kpbus, see Figure 44: Polyx - kpbus Connection via an adapter board If no direct UTP connection between the network controller and the Orion is possible, an adapter board can be used. Possible reasons for the use of an adapter board include: The Orion and the network controller are mounted in different buildings, so the connection cable exits the building The connection cable is not or is not guaranteed to be a ( Cat5e) UTP cable (e.g. if an existing connection cable is being reused) Surge protection is required The adapter board along with the network controller are connected using standard UTP Cat5e cable (plug-in connection). For more information, please refer to the adapter board manual Wiring requirements Recommended cable for communication bus between network controller and Orion(s): Cable Tabel 47: Wiring requirements kpbus Communication protocol UTP Cat5e RS Twisted pairs of 24AWG (at least) copper conductors, shielded Total kpbus distance (metres) 31

32 7.4 kpsensor bus connection The Orion is fitted with a kpsensor bus port. This allows the Orion to measure, for instance, the temperature and humidity in a certain area. Orion TIA/EIA-568-B Sirius i-serie Rev. d - e Tabel 48: Connection kpsensor bus Rev. f Description Wire color Nr. Description D0 White/orange 1 GND - Orange 2 - D1 White/green VDC V+ (12VDC) V+ (10VDC) Blauw 4 kpsensor LED White/blue 5 GND - Green 6 - C White/brown 7 - C Brown 8 - Figure T-568B I A B CC S V+ C S V+ C (GND) PRT2 Illustration of kpbus connection Figure 49: Orion - kpsensor connection NOTE! The Orion only supports one type of kpsensor. It is the combined temperature and humidity sensor (kpsensor: ) Wiring requirements The required wiring between the kpsensor and the Orion is listed below: Connector I Symbol Description Bus length Number of kpsensors Type of cable C GND (reader) 30m 2 UTP S kpsensor V VDC (reader) Table 50: Wiring requirement kpsensor bus 32

33 7.5 Default inputs and outputs The Orion s inputs and outputs are described below. Reader & IO-1: Symbol Description iprotect default T1 Digital input Door in latch mode D0 D0 / Data or Digital input* D1 D1 / Clock or Digital input* O1 Digital output A1 Monitored input 1 Loop / Enable A2 Monitored input 2 Button A3 Monitored input 3 Door mode H1 High Power output Door operation O2 Digital output Alarm O3 Digital output Table 51: Default in- and outputs Reader & IO-1 Reader & IO-2: Symbol Description iprotect default T2 Digital input Door in latch mode D0 D0 / Data or Digital input* D1 D1 / Clock or Digital input* O4 Digital output A4 Monitored input 4 Loop / Enable A5 Monitored input 5* Button A6 Monitored input 6* Door mode H2 High Power output Door operation O5 Digital output Alarm O6 Digital output Table 52: Default in- and outputs Reader & IO Monitored inputs (A1 A6) When using monitored inputs (ADC), a certain state of the input can be determined by one or more resistance values. This includes a detection of tampering or intrusion detector sabotage. Default input types are: - NO - Normally open - NC - Normally closed - Blocked - EOL (End Of Line)* - DEOL (Dual End Of Line)* - DEOL inverted* - TEOL (Triple End Of Line)* - TEOL inverted* * Recommended resistor values: EOL: 4k7 or 5k6 and Masking 22K 33

34 NC NO EOL Sabotage Idle Active Sab. Closed K K Active Idle Idle 7K 60K Sab. Open Resistor values DEOL Sab. Closed Idle 7K Active 15k 60K Sab. Open DEOL inverted Sab. Closed Active 7K Idle 15k 60K Sab. Open TEOL Sab. Closed Idle 7K Active 15k 40K Masking 40k 60K Sab. Open TEOL inverted Sab. Closed Active 7K Idle 15k 40K Masking 40k 60K Sab. Open Input GND Input GND Input GND Input GND Input GND Input GND Input GND Contact Contact Contact Alarm Contact Alarm Contact Anti Mask Contact Anti Mask Contact NC NO EOL Sabotage DEOL DEOL inverted Alarm Contact Alarm Contact Table 53: Resistor values monitored inputs TEOL TEOL inverted 34

35 8 Orion as replacement for the Orbit reader As is the case with the Orbit reader, the Orion also supports Clock- Data / Wiegand card readers. In order to use the Orion as a functional replacement for the Orbit reader: The Orion must be configured within iprotect as node type Orbit(RS422). Different iprotect software versions do not have to be taken into account here. The Orion must be connected to the network across PRT Connecting to a network controller The Orion is functionally compatible with the Orbit reader. All Orbit reader inputs and outputs are available on the Orion. However, the inputs and outputs are different. This must be taken into account (See chapter 8.1.3). Below is an installation illustration. It is possible to combine existing Orbit readers and Orions: ipu-8 ipu-8 RS422 N N PRT1- RS422 Max 8 Max. 8 Orion Orbit 2 Orbit 1 PRT1 A PRT1 A Clock- Data / Wiegand Clock- Data / Wiegand Figure 55: ipu-8 with Orbits Figure 54: ipu-8 with Orions 35

36 Polyx Polyx N D N D RS422 Max. 2 Max. 2 PRT1- RS422 Orion Orbit 2 Orbit 1 PRT1 A PRT1 A Clock- Data / Wiegand Clock- Data / Wiegand Figure 56: Polyx with Orbits Figure 57: Polyx with Orions Controller <> Orion PRT1 - RS422 Figure T-568B ipu-8 PRT 1 8 OR Polyx PRT1 2 TIA/EIA-568-B Orion (A) PRT1 Nr. Description Wire color Nr. Description 1 RxA White/orange 1 B 2 RxB Orange 2 A 3 TxZ White/green 3 Z 4 +12Vdc Blue 4 12Vdc 5 Orbit sense White/blue 5 GND 6 TxY Green 6 Y 7 GND White/brown 7 GND 8 GND Brown 8 GND Table 58: Connection Orion as replacement unit reader Orbit Wiring requirements The cable recommended for use between the Orion and the network controller is listed below: Cable Communication Remote Communication between protocol UTP/STP Cat 3 RS m Network controller and Orion Table 59: Wiring requirements Orion as replacement unit reader Orbit 36

37 8.1.3 Default inputs and outputs When replacing an Orbit reader with an Orion, the below table can be used: Orbit 2 Reader 1 Description of connection Orion Reader & IO-1 iprotect default +5V 200mA MAX Reader voltage +V GND GND (digital ground) C D1 / CLK D1 / Clock D1 D0 / DAT D0 / Data D0 LED LED LD Earth ground Inputs 1 Inputs 1 Input/Output IN0 Digital input A1 Loop COM 0+1 GND (digital ground) C C IN1 Digital input A2 Button IN2 Digital input A3 Door mode COM 2+3 GND (digital ground) C IN3 Digital input T1 Door in latch mode Outputs 1 Outputs 1 0 Digital output H1 Door operation GND GND (digital ground) C 1 Digital output O2 Alarm Table 60: Default in- and outputs Orion as replacement unit reader Orbit (1) Orbit 2 Reader 2 Description of connection Orion Reader & IO-2 iprotect default +5V 200mA MAX Reader voltage +V GND GND (digital ground) C D1 / CLK D1 / Clock D1 D0 / DAT D0 / Data D0 LED LED LD Earth ground Inputs 2 Inputs 2 Input/Output IN0 Digital input A4 Loop COM 0+1 GND (digital ground) C C IN1 Digital input A5 Button IN2 Digital input A6 Door mode COM 2+3 GND (digital ground) C IN3 Digital input T2 Door in latch mode Outputs 2 Outputs 2 0 Door Output H2 Door operation GND GND (digital ground) C 1 Alarm output O5 Alarm Tabel 61: Standaard in- en uitgangen Orion als vervanger van de lezer Orbit (2) 37

38 9 Pluto-Orion as replacement for the ipu-8 A Pluto in combination with the Orion can serve as a functional replacement unit for the Stellar or ipu-8 Network Controller. When an existing ipu-8 with 8 Orbits installation needs to be replaced, a Pluto with 4 stacked Orions will suffice. Each Orion can be linked with maximal two Orbits. The type of Orbit is in this case not relevant (Orbit-1, Orbit-2 or Obit-IO). NOTE The existing UTP cabling of the Orbit is connected to the S2M cable. This must be connected to the Orion. The cable length between ipu-8 and Orbit or between Orion and Orbit remains unchanged. In the picture below there is an example of replacing an ipu-8 for a Pluto and Orion: ipu-8 Orbit-2 N Max 8 Clock- Data / Wiegand Orbit-2 Orbit-1 S2M cable to PRT1 Orion Pluto X Clock- Data / Wiegand Figuur 63: ipu-8 with 2 Orbits PRT2 N Front side S2M cable to PRT2 Orbit-1 Clock- Data / Wiegand Figure 62: Pluto and Orion with 2 Orbits 38

39 10 Diagnostics The Orion can be fully tested before communicating with iprotect through a diagnostic program on the Network Controller Initiating Pluto diagnostics NOTE System diagnostics are only possible if there is no communication between the Pluto and iprotect. Navigate to the Pluto s IP address and perform the following steps: Click on the Hardware button and activate diagnostics. Reader manager: The connected RS485 card readers will automatically be retrieved and a (scroll-down) list will appear. Figure 64: Pluto diagnostics (1) Node manager: The connected Orions will automatically be retrieved and a (scroll-down) list will appear. Figure 65: Pluto diagnostics (2) Select the Orion in question according to its serial number All inputs will be displayed All outputs will be displayed by selecting an output, it can also be switched 39

40 The on-board sensors will be displayed When an access card is presented to a reader, the card number will be displayed 10.2 Polyx/iPU-8: Connecting across the Console port System diagnostics can be carried out with the help of a PC / laptop. For the purpose of diagnostics, every Controller has a diagnostics menu. All that is required to do this is a series connection between the Controller and the PC or laptop. However, Terminal software must be used. A range of software, such as Teraterm (or hyperterminal) can emulate a VT100 terminal on a PC. Such software must therefore be in place or must promptly be installed. Connect the PC to the Console port of the Polyx. To do this, use the adapter listed below (available from Keyprocessor BV). Figuur 66: Serial Adapter Run the terminal software and establish a connection using the following settings: Select the COM port for the connected controller. If an ipu-8 controller is used: o Set the baud rate to 9600, Data to 8 bit, Stop to 1 bit, Parity to None and Hardware control to None If a Polyx controller is used: o Set the baud rate to , Data to 8 bit, Stop to 1 bit, Parity to None and Hardware control to None Initiating ipu-8 diagnostics ipu-8 diagnostics can be accessed by pressing on any key when the following text is displayed: Hit any key within 5s to run diagnostics The main menu will appear, containing the following options 40

41 --- ipu-8 diagnostics V ) Environment settings 2) Test serial ports (loopback) 3 Test Profi-device communications 4) Test Profi-device functionality 5) Show board revision and test diag LEDs & inputs 6) Test Power 7) Test EEPROM 8) Test RTC 9) Test Watchdog q) Start application r) Restart system Enter menu option: Screen 1: ipu-8 diagnostics main menu When it comes to testing the Orion, only options 2 and 3 apply for use by the installer. Option 3: Profibus communication test If option 3 - Test Profi device communications - is selected from the main menu of the ipu-8 Diagnostics software, the Profibus DP communication test screen will appear. Here, it is possible to specify per port whether a Profibus device is connected and, if so, which slave it is. Communication mode indicates whether communication has been established (connected/disconnected). The identification number of the relevant device is displayed, along with the hardware and software version numbers. --- Profibus DP communication test --- Comm. status Ident no. Hw/Sw version ) Profi slave 1 Connected 0xfffd IE-ORBRD2 V1.03 2) Profi slave 1 Connected 0xfffd KP-ORION V1.00 3) Profi slave 1 Connected 0xfffd IE-ORBRD2 V1.03 4) No profi-dev. Disconnected 5) No profi-dev. Disconnected 6) No profi-dev. Disconnected 7) No profi-dev. Disconnected 8) No profi-dev. Disconnected 1..8) : toggle device type S) : toggle start/stop Q) : Quit Screen 2: Profibus communication test If option 4 - Test Profi device functionality - is selected from the main menu of the ipu-8 Diagnostics software, correct performance of the connected devices can be tested. Firstly, the port to which the test device is connected must be entered. This will bring up a list of the various types of devices that may be connected. 41

42 In the menu, an Orion corresponds to an Orbit-2 (Profi DP reader*2). In the following example, option 2, Profi DP reader-2, has been selected: Enter the device to test 1..8) : 1 1) Profi DP reader-1 2) Profi DP reader-2 3) Profi DP io --- Device functionality test --- Enter the device type : Profi DP reader-2 Enter slave no. 1)..4) (CR=1): 1 MT interface or Wiegand interface [M/W] for reader 1? : M MT interface or Wiegand interface [M/W] for reader 2? : M Continue [Y]? : Screen 3: Device functionality test On this screen, entry of the slave number is requested. This value must be set to 1. The right type of interface must be chosen for both reader inputs. Once all entries have been confirmed as correct, the options and mode relevant to the selected device are displayed: --- Profibus DP orbit reader test, no Label Orion 1) Output R1-0: On : (H1) 2) Output R1-1: On : (O2) 3) Output R2-0: On : (H2) 4) Output R2-1: On : (O5) 5) RdrLED R1 6) RdrLED R2 Input R1-0: Off 128 : (A1) Input R1-1: Off 128 : (A2) Input R1-2: Off 128 : (A3) Input R1-3: Off 128 : (T1) Input R2-0: Off 128 : (A4) Input R2-1: Off 128 : (A5) Input R2-2: Off 128 : (A6) Input R2-3: Off 128 : (T2) Reader : R1: State : Data exch. 1)... : toggle output state or flash reader LED S) : stop Screen 4: Device functionality test, options and mode of an Orion as an Orbit reader On the above screen, the inputs and outputs can be tested. The outputs can be activated or deactivated using keys 1 to 4. Keys 5 or 6 can be used to test the card reader LEDs (rapidly press 5 times to turn on or off). When a card is presented to one of the card readers, the relevant card information will be displayed after the Reader field. Here, R1 indicates that card reader 1 has read a card. R2 indicates that card reader 2 has read a card. The number after the scanned card number (08 in this instance) indicates the number of characters in the card number. 42

43 Initiating Polyx diagnostics Depending on the function and the method of connection (PRT1 or PRT2 from Orion), it is possible to use certain sections of the diagnostics menu. Diagnostics for both connection methods are described in the below paragraphs Orion as functional replacement for the Orbit reader ipu-8 diagnostics can be accessed by pressing on any key when the following text is displayed: Hit any key within 5s to run diagnostics The main menu will appear, containing the following options Polyx Diags version V ) Environment settings 2) Test onboard I/O 3) Test RS422 devices (loopback) 4) Test profi-device Communications 5) Test profi-device functionality 6) Test Orion-device Communications 7) Test Orion-device functionality 8) Clean nodemgr 9) Test Watchdog a) Clean system b) Clean /etc/rc.d/* to /etc/save.d/* v) Version p) Polyx menu q) Start application r) Restart system Enter menu option: Screen 1: Polyx diagnostics main menu When it comes to testing the Orion, only options 4 and 5 apply for use by the installer. Option 4: Profibus communication test If option 4 - Test Profi device communications - is selected from the main menu of the Polyx Diagnostics software, the Profibus DP communication test screen will appear. Here, it is possible to specify per port whether a Profibus device is connected and, if so, which slave it is. Communication mode indicates whether communication has been established (connected/disconnected). The identification number of the relevant device is displayed, along with the hardware and software version numbers. --- Profibus DP communication test --- Comm. status Ident no. Hw/Sw version ) Profi slave 1 Connected 0xfffd IE-ORBRD2 V1.03 2) Profi slave 1 Connected 0xfffd KP-ORION V ) : toggle device type S) : toggle start/stop Q) : Quit Screen 2: Profibus communication test If option 5 - Test Profi device functionality - is selected from the main menu of the Polyx Diagnostics software, correct performance of the connected devices can be tested. Firstly, the port to which the test device is connected must be entered. This will bring up a list of the various types of devices that may be connected. In the menu, an Orion corresponds to an Orbit-2 (Profi DP reader*2). 43

44 In the following example, option 2, Profi DP reader-2, has been selected: Enter the device to test 1..8) : 1 1) Profi DP reader-1 2) Profi DP reader-2 3) Profi DP io --- Device functionality test --- Enter the device type : Profi DP reader-2 Enter slave no. 1)..4) (CR=1) : 1 MT interface or Wiegand interface [M/W] for reader 1? : M MT interface or Wiegand interface [M/W] for reader 2? : M Continue [Y]? : Screen 3: Device functionality test On this screen, entry of the slave number is requested. This value must be set to 1. The right type of interface must be chosen for both reader inputs. Once all entries have been confirmed as correct, the options and mode relevant to the selected device are displayed: --- Profibus DP orbit reader test, no ) Output R1-0: On : (H1) 2) Output R1-1: On : (O2) 3) Output R2-0: On : (H2) 4) Output R2-1: On : (O5) 5) RdrLED R1 6) RdrLED R2 Input R1-0: Off 128 : (A1) Input R1-1: Off 128 : (A2) Input R1-2: Off 128 : (A3) Input R1-3: Off 128 : (T1) Input R2-0: Off 128 : (A4) Input R2-1: Off 128 : (A5) Input R2-2: Off 128 : (A6) Input R2-3: Off 128 : (T2) Reader : R1: State : Data exch. 1)... : toggle output state or flash reader LED S) : stop Screen 4: Device functionality test, options and mode of an Orion as an Orbit reader On the above screen, the inputs and outputs can be tested. The outputs can be activated or deactivated using keys 1 to 4. Keys 5 or 6 can be used to test the card reader LEDs (rapidly press 5 times to turn on or off). When a card is presented to one of the card readers, the relevant card information will be displayed after the Reader field. Here, R1 indicates that card reader 1 has read a card. R2 indicates that card reader 2 has read a card. The number after the scanned card number (08 in this instance) indicates the number of characters in the card number. 44

45 Multiple Orions on a single data line (bus) ipu-8 diagnostics can be accessed by pressing on any key when the following text is displayed: Hit any key within 5s to run diagnostics The main menu will appear, containing the following options 1) Environment settings 2) Test onboard I/O 3) Test RS422 devices (loopback) 4) Test profi-device Communications 5) Test profi-device functionality 6) Test Orion device 7) Clean nodemgr 8) Test Watchdog 9) Clean system c) Clean /etc/rc.d/* to /etc/save.d/* v) Version p) Polyx menu q) Start application r) Restart system Enter menu option: Screen 1: Polyx diagnostics main menu Polyx Diags version V3.0.5 When it comes to testing the Orion, only option 6 applies for use by the installer. (Polyx diags version V3.06 required) Option 6: Orion device functionality If option 6 - Test Orion device - is chosen from the main menu of the Polyx Diagnostics software, the Polyx communication port to which the Orions are connected (PRT2 (1) PRT3 (2) must be selected. --- Device functionality test --- Enter the interface to test 1..2) : Scanning done, please select an Orion device: 1) Orion snr: , V ) Orion snr: , V ) Orion snr: , V ) Orion snr: , V ) Orion snr: , V ) Orion snr: , V ) Orion snr: , V ) Orion snr: , V Enter the device to id to test 1..8) : 1 Screen 2: Device functionality test In the above example, PRT2 (1) of the Polyx has been selected for the detection and scanning of connected devices. Device serial numbers and firmware versions are displayed once detected. By making a selection between 1 and 8, the next screen is displayed and a specific Orion can be tested. In the following example, the device in question is Orion 1 with serial number

46 --- Orion test >> snr: , V Reader & IO Input A1: off 128 (15939ohm) 1) Output O1: On/Off Input A2: off 128 (15939ohm) 2) Output 02: On/Off Input A3: off 128 (15939ohm) 3) Output O3: On/Off general ---- Input T1: Off 128 4) Output H1: On/Off B)Buzzer : Off Input D0: off 128 5) RdrLED R1 toggle Input D1: Off 128 Input T :off 128 Input(v) :26.58V Reader & IO-2 Reader(v):12.00V Reader(a): 0.05A Input A4: off 128 (15939ohm) 6) Output O4: On/Off Temp(K) : 240.0K Input A5: off 128 (15939ohm) 7) Output 05: On/Off Input A6: off 128 (15939ohm) 8) Output O6: On/Off Input T2: Off 128 9) Output H2: On/Off Input D0: Off 128 A) RdrLED R2 toggle Input D1: Off 128 Reader [1 or 2] (ABA) > B).. : toggle output state F) change format S) : stop Screen 3: Device functionality test, options and mode of an Orion On the above screen, the inputs and outputs can be tested. Using keys 1 to 9 or A and B, the outputs can be activated or deactivated. Keys 5 or a can be used to test the card reader LEDs (rapidly press 5 times to turn on or off). When a card is presented to one of the card readers, the relevant card information will be displayed after the Reader field. Option F changes the way in which analogue input information is displayed (Ohms or raw data). 46

47 11 How to 11.1 Installation Pluto Configuring the Pluto: 1. Make sure all connections are in accordance with the technical drawing and connect the Pluto to the network. See chapter Open the Explorer and browse to the following address: The login screen appears. 3. Enter controller as username. The default password is Pluto. 4. On the maintenance page select Network settings and enter the desired information like IP address and IP address gateway. 5. Select Hardware and activate Diagnostics. Diagnostics enables automatic detection of devices connected to the Pluto and testing of it. Deactivate diagnostics after successful test. 6. Select Tools and verify the connection with iprotect by entering the IP address of the iprotect server together with port number at Netcat and press the Test button. Configuration in iprotect : 1. Open menu Installation > Hardware > Line 2. Click on the Search button. 3. Make a right mouse click in the tree view (left side). Add line appears and click on this popup. The line dialog will be opened. 4. Enter a logical description of the line in the field Name. 5. Enter the correct IP address in the field IP address. 6. Under communication select Active and Active (with nodes). 7. Click on the Save button. 8. Press the button Send new Keystore. When having the connection between iprotect and the Pluto in place, automatically the latest software update will be installed on the Pluto. This may take a few minutes. When finished, the Current status will be Idle. NOTE After the Pluto has communicated with iprotect, the standard password will be changed. The new password will be displayed in the Line details screen. 9. The nodes and readers connected to the Pluto can be automatically detected and configured in iprotect by clicking on the Read in button at the Line details screen. 10. To activate the readers, an access card needs to be presented twice at each reader. As soon as the LED of the reader is blinking when the card is presented, the correct card data will be stored in iprotect. 11. Assign a reader group, e.g. All card readers to the new card reader. 12. Finally assign a card, having the correct access profile to a person and verify if access in granted. In case of access, the LED on the reader turns green for a period of 5 seconds. 47

48 11.2 New Orion on existing Pluto Configuring the Orion: 1. Make sure all connections are in accordance with technical drawing, see chapter 13.2, 13.3 or 14. Configuration in iprotect : 1. Open menu Installation > Hardware > Line 2. Click on the Search button. 3. Select the correct Pluto. 4. The nodes and readers connected to the Pluto can be automatically detected and configured in iprotect by clicking on the Read in button at the Line details screen. 5. To activate the readers, an access card needs to be presented twice at each reader. As soon as the LED of the reader is blinking when the card is presented, the correct card data will be stored in iprotect. 6. Assign a reader group, e.g. All card readers to the new card reader. 7. Finally assign a card, having the correct access profile to a person and verify if access in granted. In case of access, the LED on the reader turns green for a period of 5 seconds New RS485 reader on existing Orion Configuring the RS485 reader: 1. Make sure all connections are in accordance with technical drawing, see chapter 14. Configuration in iprotect : 1. Open menu Installation > Hardware > Line 2. Click on the Search button. 3. Select the correct Pluto. 4. The nodes and readers connected to the Pluto can be automatically detected and configured in iprotect by clicking on the Read in button at the Line details screen. 5. To activate the readers, an access card needs to be presented twice at each reader. As soon as the LED of the reader is blinking when the card is presented, the correct card data will be stored in iprotect. 6. Assign a reader group, e.g. All card readers to the new card reader. 7. Finally assign a card, having the correct access profile to a person and verify if access in granted. In case of access, the LED on the reader turns green for a period of 5 seconds. 48

49 11.4 New Orion on existing Polyx Configuring the Orion: 1. Make sure all connections are in accordance with technical drawing, see chapter 14. Configuration in iprotect : 1. Open menu Installation > Hardware > Line 2. Click on the Search button. 3. Select the correct Line and click on the plus in front of the line. The nodes appear. 4. To open the Node details, click on the node. 5. To create a new node, click on the button New. 6. Enter a logical description of the line in the field Name. 7. Select Node type Orion. 8. Enter the correct port number at Serial port address. 9. Select Node online. 10. Click on the Save button. The Orion will be automatically signed-up when connected in the KP-Bus and the serial number will appear. 11. To activate the readers, an access card needs to be presented twice at each reader. As soon as the LED of the reader is blinking when the card is presented, the correct card data will be stored in iprotect. 12. Assign a reader group, e.g. All card readers to the new card reader. 13. Finally assign a card, having the correct access profile to a person and verify if access in granted. In case of access, the LED on the reader turns green for a period of 5 seconds Replace Polyx for Pluto and Orion Configuration in iprotect : 1. Open menu: Installation > Hardware > Line. 2. Select the correct Line which need to be replaced. 3. Under communication deselect Active. 4. Save this record. Configuring the Pluto: 1. Switch off the power supply 2. Write down all connections and disconnect it from the Polyx. 3. Install a Pluto in combination with an Orion. Pluto and Orion are connected by using the stacking connector. See chapter Connect the Pluto according to drawing and connect the Pluto to the network. See chapter Connect the IO contacts to the Orions. See chapter Connect the card readers to PRT1 and / or PRT2 of the Orion. 7. Switch on the power supply. 8. Open the Explorer and browse to the following address: The login screen appears. 9. Enter controller as username. The default password is Pluto. 10. Select Hardware and activate Diagnostics. Diagnostics enables automatic detection of devices connected to the Pluto and testing of it. Deactivate diagnostics after successful test. 11. On the maintenance page select Network settings and enter the desired information like IP address and IP address gateway. Configuration in iprotect : 49

50 1. Open menu: Installation > Hardware > Line. 2. Select the correct Line which need to be replaced. 3. Under communication select Active. 4. Press the button: Send new KeyStore. When having the connection between iprotect and the Pluto in place, automatically the latest software update will be installed on the Pluto. This may take a few minutes. When finished, the Current status will be Active. NOTE After the Pluto has communicated with iprotect, the standard password will be changed. The new password will be displayed in the Line details screen. 5. Open menu: General > Overviews > Last events and check the operation Replace Polyx (2x kpbus) for Pluto and two Orions Configuration in iprotect : 1. Open menu: Installation > Hardware > Line. 2. Select the correct Line which need to be replaced. 3. Under communication deselect Active. 4. Save this record. Configuring the Pluto: 1. Switch off the power supply 2. Write down the connections and disconnect it from the Polyx. 3. Install a Pluto in combination with two Orions (per Orion one kpbus). The Pluto and the two Orions are connected by using the stacking connector. See chapter Connect the first kpbus (PRT2 of the Polyx) to PRT2 of the 1st Orion (this Orion is to the left of the Pluto). 5. Connect the second kpbus (PRT3 of the Polyx) to PRT2 of the 2nd Orion. 6. Connect the Pluto according to drawing and connect the Pluto to the network. See chapter Switch on the power supply. 8. Open the Explorer and browse to the following address: The login screen appears. 9. Enter controller as username. The default password is Pluto. 10. On the maintenance page select Network settings and enter the desired information like IP address and IP address gateway. Configuration in iprotect : 1. Open menu: Installation > Hardware > Line. 2. Select the correct Line which need to be replaced. 3. Under communication select Active. 4. Press the button: Send new KeyStore. When having the connection between iprotect and the Pluto in place, automatically the latest software update will be installed on the Pluto. This may take a few minutes. When finished, the Current status will be Active. NOTE After the Pluto has communicated with iprotect, the standard password will be changed. The new password will be displayed in the Line details screen. 50

51 5. Press the button: Discover. Both kpbus lines are converted. 6. Open menu: General > Overviews > Last events and check the operation Replace ipu-8 for a Pluto with four Orions Configuration in iprotect : 1. Open menu: Installation > Hardware > Line. 2. Select the correct Line which need to be replaced. 3. Under communication deselect Active. 4. Save this record. Configuring the Pluto: 1. Switch off the power supply 2. Write down the connections (PRT1 8) of the ipu-8 and disconnect it. 3. Install a Pluto in combination with four Orions. The Pluto and the four Orions are connected by using the stacking connector. See chapter Connect an S2M-cable to each Orion on PRT1 and to PRT2. 5. Connect the first Orbit-cable (ipu-8 PRT-1) to the S2M-cable connected to PRT1 of the 1st Orion (this Orion is to the left of the Pluto). Orbit cable-3 (ipu-8 PRT-3) comes on the S2Mcable from PRT1 of the 2nd Orion, etc. 6. Connect the Pluto according to drawing and connect the Pluto to the network. See chapter Switch on the power supply. 8. Open the Explorer and browse to the following address: The login screen appears. 9. Enter controller as username. The default password is Pluto. 10. On the maintenance page select Network settings and enter the desired information like IP address and IP address gateway. Configuration in iprotect : 1. Open menu: Installation > Hardware > Line. 2. Select the correct Line which need to be replaced. 3. Under communication select Active. 4. Press the button: Send new KeyStore. When having the connection between iprotect and the Pluto in place, automatically the latest software update will be installed on the Pluto. This may take a few minutes. When finished, the Current status will be Active. NOTE After the Pluto has communicated with iprotect, the standard password will be changed. The new password will be displayed in the Line details screen. 5. Open menu: General > Overviews > Last events and check the operation Pluto - Make factory default When it is necessary to bring the Pluto back to Factory default, complete the following steps: Configuration in iprotect : 1. Open menu: Installation > Hardware > Line. 2. Click on the Search button. 3. Select the correct Pluto. 51

52 4. Under communication deselect Active. 5. Copy the password of the line. 6. Save this record. Configuration in Pluto: 1. Browse to the maintenance page of the Pluto. 2. Login with username controller and the line password, generated in iprotect. 3. Select the menu Advanced. 4. Press on Reboot. Login into the maintenance page of the Pluto after 2 minutes. 5. Select the menu Advanced. 6. Press on Make factory default. The Pluto will automatically reboot after 5 minutes. Note: The password, configurations and iprotect data will be removed. The IP-address will not be changed. 7. Login into the maintenance page of the Pluto. Login with username controller and the password Pluto Pluto Removing iprotect data When it is necessary to remove the iprotect data, complete the following steps: Configuration in iprotect : 1. Open menu: Installation > Hardware > Line. 2. Click on the Search button. 3. Select the correct Pluto. 4. Under communication deselect Active. 5. Copy the password of the line. 6. Save this record. Configuration in Pluto: 1. Browse to the maintenance page of the Pluto. 2. Login with username controller and the line password, generated in iprotect. 3. Select the menu Advanced. 4. Press on Reboot. Login into the maintenance page of the Pluto after 2 minutes. 5. Select the menu Advanced. 6. Press on Make clean. The following message appears: "enabling apache" Note: The password ad ip-address will not be changed. Configurations and iprotect data will be removed. 7. The Pluto can be linked with iprotect again. See chapter

53 12 Technical data 12.1 Pluto Housing Measurements: 110,0 x 47,0 x 93,0 mm (L x W x H) Weight 0.25 Kg Materials Material Covers ABS Type Terluran GP22 Rev. b0 c2 Wraps Chromated aluminum Frontplate Chromated aluminum Lightguide PC clear UL94 Material Covers ABS Type Terluran GP22 Rev. c3 Wrap PA6-GB30 Altech PA6 A 3030/109 GB30 Frontplate Lightguide SBC Styrolux 656 C Connector Contact Pin Copper alloy Insulating PA 6.6 Mounting Dinrail 35mm DIN rail type O profile Specifications CPU CPU Name Freescale i.mx6 CPU Type Dual ARM Cortex -A9 Core 1.0 GHz Networking Ethernet Gigabit Ethernet Controller, RJ-45 x 1 Connectivity SD SDHC SAM optional USB 2.0 Host / Device 2 USB OTG 1 RTC Yes Electronic specifications Supply voltage 12-24V DC Power average 2 Watt Inputs / Outputs Tamper 1 Indicators Visual RGB-LED Sound Multi-tone buzzer Certifications CE compliant EN :2011 EN 55022:2011 Environment Usage Indoor Temperature 0 to 60 C Humidity 20 ~ 90% RH non-condensing Storage temperature -40 ~ +80 C Storage humidity 10 ~ 95% RH 53

54 12.2 Orion Housing Measurements: x 47.0 x 93mm (L x W x H) Weight: 0,25 Kg Material Material Covers ABS Type Terluran GP22 Rev. d - e Wraps Chromated aluminum Frontplate Chromated aluminum Lightguide PC clear UL94 Material Covers ABS Type Terluran GP22 Rev. f Wrap PA6-GB30 Altech PA6 A 3030/109 GB30 Frontplate Lightguide SBC Styrolux 656 C Connector Contact Pin Copper alloy Insulating PA 6.6 Specifications Communication PRT1 RJ45 socket, RS422/RS485 PRT2 RJ45 socket, RS485 Pin out Pin 1 = RX1B Pin 5 = GND Pin 2 = RX1A Pin 6 = TX1A Pin 3 = TX1B Pin 7.8 = GND Pin 4 = Rev. d - e Pin 4 = Rev. f 12VDC 10VDC Pin out Pin 1 = B Pin 5 = GND Pin 2 = A Pin 6 = A Pin 3 = B Pin 7.8 = GND Pin 4 = Rev. d - e Pin 4 = Rev. f 12VDC 10VDC Card reader Reader power (+V) Voltage Rev. d and e Rev. f 12.0V DC 10.0V DC Current 500mA (one Polyfuse for both readers) 500mA Interface Clock/Data depending of used cable and card reader Wiegand Power supply & consumption Voltage (+) 12,0 24V DC Power Average 0.48W (no load) Digital I/O Tamper Switching to GND Digital output Rev. d and e O1, O2, O3, O4, O5, O6 Max. Voltage 28V; Open collector output; sink current. Max. current 300mA (Polyfused) High power output H1, H2 Switching to GND, max. 2.5A Digital input T1, T2 Switching to GND, <20K ohm Digital input D0/D1 Switching to GND, <20K ohm Reader IO-1 Rev. f Max. Voltage 28V; Open collector output; sink current. Max. current 500mA 54

55 Digital input D0/D1 Reader IO-2 Switching to GND, <20K ohm Monitored inputs A1, A2, A3, A4, A5, A6 Value 0-60K ohm. Response time <250ms Switching to GND, <2K ohm. Response time 20ms Environment sensor kpsensor Sensor kpsensor 2 Type Temperature/Humidity Indicators Visual RGB-LED Sound Multi-tone buzzer MicroSD MicroSD Type: SDHC End of line jumper End Of Line resistor 120 ohm Environment Usage Indoor Temperature -20 C to +70 C Humidity 20 ~ 90% RH non-condensing Storage temperature & -40 ~ +85 C, 10 ~ 95% RH humidity Polyfuse Type PTC Fuse Case style Thermal derating At -10 C the hold current will increase to 130% At +25 C no derating At +60 C the hold current will reduced to 60% Certifications CE compliant EN 55022:2010 EN :

56 13 Declaration of conformity 13.1 Pluto DECLARATION OF CONFORMITY (DoC) Keyprocessor B.V. Paasheuvelweg BJ Amsterdam The Netherlands Declare under our sole responsibility that the product: Pluto Controller The above mentioned product complies with the essential requirements, which are specified in the directive 2014/30/EU on the approximation of the laws of the Member States relating to electromagnetic compatibility. The product of the declaration described above is in conformity with the requirements of the following specifications: Documents-No.: EN 55022: European limits and methods of measurement of radio disturbance characteristics of information technology equipment EN : Alarm systems -- Part 4: Electromagnetic compatibility - Product family standard: Immunity requirements for components of fire, intruder, hold up, CCTV, access control and social alarm systems Date: 2 November 2017 Dr. W. B.J.M. Janssen CTO Keyprocessor B.V. Paasheuvelweg BJ Amsterdam The Netherlands 56

57 13.2 Orion controller DECLARATION OF CONFORMITY (DoC) Keyprocessor B.V. Paasheuvelweg BJ Amsterdam The Netherlands Declare under our sole responsibility that the product: Orion Controller The above mentioned product complies with the essential requirements, which are specified in the directive 2014/30/EU on the approximation of the laws of the Member States relating to electromagnetic compatibility. The product of the declaration described above is in conformity with the requirements of the following specifications: Documents-No.: EN 55022: European limits and methods of measurement of radio disturbance characteristics of information technology equipment EN : Alarm systems -- Part 4: Electromagnetic compatibility - Product family standard: Immunity requirements for components of fire, intruder, hold up, CCTV, access control and social alarm systems Date: 2 November 2017 Dr. W. B.J.M. Janssen CTO Keyprocessor B.V. Paasheuvelweg BJ Amsterdam The Netherlands 57

58 14 Technical drawings Pluto/Orion setup with network connection and power supply 58

59 Pluto/Orion with Sirius RS485 and IO 59

60 Pluto/Orion with Sirius clock-data/wiegand and I-O 60

61 Pluto/Orion with IO, Sirius Clock-data/Wiegand and Orbits 61

62 Pluto with power supply and USB-RS232 converter 62

63 Pluto/Orion with kpbus 63

64 Orion with kpsensor bus 64

65 Pluto Orion stacked with 8x RS485 Sirius-i readers 65

66 Pluto Orion with clock-data or Wiegand readers 66

67 Pluto Orion with RS485 readers & kpbus combi 67

68 Polyx with kpbus 68