*Pluto/Orion Modular controller line

Owned by Tom Polman
Last updated: Apr 20, 2023 by Mickael van der Schoot
26 min read

Installation Manual | IM-20210309-TP-44

Access Control | Controllers | Pluto/Orion Modular controller line |

 

This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.

1 Introduction

This instruction manual covers the entire range of TKH Security modular controllers.
One or more software versions are specified in every module-related chapter. These versions are important when it comes to support for the product.

2 General

2.1 Wiring

This document assumes standard T-568 color coding of the cables.

Picture T-568B

2.2 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.

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.

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.

2.3 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.

2.4 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:

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.v

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:

3.3 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:

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 valid access rights). And in this offline situation, the events of inputs, (lock control)outputs and cards may not be lost.

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.

When it comes to connection, the following conditions are important:

  • when inserting stacking connectors, always ensure the power is off

  • when placing the controllers on a DIN rail use end brackets on both sides. This is to prevent losing the connection between the controllers which will cause irreparable damage

  • 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 3: 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 (-)

Always prevent the coupled controllers from becoming detached from each other when the system is powered. This will cause irreparable damage to the controller(s)!

4.2 Serial connection (RS-232)

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 192.168.1.195. In order to access the maintenance page, enter
the following into your browser: https://192.168.1.195
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:

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.

Once saved, the new settings will take immediate effect and the Pluto will only be accessible using the new IP address.

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 software versions

In order to guarantee optimum performance, the following software versions are required:

6.3 Functions and support

Depending on the desired application of the Orion, a range of functions are available. Below is a list of functions.

* 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 TKH Security is supported.

***  Hardware version depended.

6.3.1 Orion – connected to the Pluto

 

6.3.2 Orion – RS485 bus communication (kpBus)

6.3.3 Orion – functional replacement for the Orbit reader

6.4 Connections

The connection ports on the Orion are described in this section. Options depend on the application and the method of connection.

6.4.1 Description imprint Orion

The connection ports and imprints on the Orion are illustrated below:

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:

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.
This functionality is available from:

  • iProtect version 8.04 or higher

  • Orion application version 1.4.37 or higher

  • Orion bootloader version 2.3.0.14 or higher

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.

6.6.1 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 12.

Note! Inserting the SD card incorrectly could cause serious damage to the Orion or SD card.

6.6.2 Local card storage (system offline)

Local card storage is needed to guarantee access in an offline situation (offline means when there is no communication with the network controller).

The Orion will function completely independently in an offline situation. If a user has a priority for local card storage (always, employee or visitor), no problems will arise for the user during a malfunction. When the communication failure with the Network controller has recovered, all events will be sent to iProtect.

6.6.3 Support in offline situation

The following features are supported during the Offline situation:
The following table shows the maximum numbers:

The following table shows all the events:

Note: It is possible to use combined input or output by a reader. Consider a door with a card reader on both sides.

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 13.

  • When linking only Orions, the kpBus must be connected externally. See figure 13a.

7.2 Connecting card reader

7.2.1 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 13), a maximum of eight RS485 card readers can be connected.

7.2.1.1 Connection of RS485 card reader

7.2.1.2 Wiring requirements

The wiring required between the card reader and the Orion is listed below:

7.2.2 Clock- data / Wiegand 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.

7.2.2.1 Connecting the card reader

7.2.2.2 Wiring requirements

The wiring required between the card reader and the Orion is listed below:

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)

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 13).

  • 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 18.

7.3.1.1 Connection of kpBus

NOTE If the kpBus begins with an Orion, the start and the end of the kpBus must have an EOL jumper, see Figure 18: Pluto/Orion - kpBus.

7.3.2 Polyx as communication starting point

7.3.2.1 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.

NOTE the Polyx is always the starting point of a kpBus. Add an EOL jumper to the end of the kpBus, see Figure 20: Polyx - kpBus.

7.3.3 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.

7.3.3.1 Wiring requirements

Recommended cable for communication bus between network controller and Orion(s):

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.

NOTE the Orion only supports one type of kpSensor. It is the combined temperature and humidity sensor (kpSensor: 571-1013).

7.4.1 Wiring requirements

The required wiring between the kpSensor and the Orion is listed below:

7.5 Default inputs and outputs

The Orion’s inputs and outputs are described below.

7.5.1 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

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 PRT1.

8.1 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:

8.1.1 Controller <> Orion PRT1 - RS422

8.1.2 Wiring requirements

The cable recommended for use between the Orion and the network controller is listed below:

8.1.3 Default inputs and outputs

When replacing an Orbit reader with an Orion, the below table can be used:

9 Pluto-Orion as replacement for the iPU-8

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:

10 Diagnostics

The Orion can be fully tested before communicating with iProtect ™ through a diagnostic program on the Network Controller

10.1 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.

  • Node manager: The connected Orions will automatically be retrieved and a (scroll-down) list will appear.

  • 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

  • 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

  • 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 “115200”, Data to “8 bit”, Stop to “1 bit”, Parity to “None” and Hardware control to “None”

10.2.1 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

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.

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.

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:

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:

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.

10.2.2 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.

10.2.2.1 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

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.

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).

In the following example, option 2, Profi DP reader-2, has been selected:

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:

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.

10.2.2.2 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

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.

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 140025.

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).

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 14.

  2. Open the Explorer and browse to the following address: https://192.168.1.195. 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 20100 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.

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.

11.3 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.

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.

11.5 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 14.

  4. Connect the Pluto according to drawing and connect the Pluto to the network. See chapter

  5. Connect the IO contacts to the Orions. See chapter 7.5.

  6. 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: https://192.168.1.195. 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™:

  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”.

11.6 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 14.

  4. 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

  7. Switch on the power supply.

  8. Open the Explorer and browse to the following address: https://192.168.1.195. 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. Press the button: “Discover”. Both kpBus lines are converted.

6. Open menu: “General” > “Overviews” > “Last events” and check the operation.

11.7 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 14.

  4. 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 4.1

  7. Switch on the power supply.

  8. Open the Explorer and browse to the following address: https://192.168.1.195. 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.

11.8 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.

  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, the O.S. settings and IP address will be set to default. The  configurations and iProtect data will not be removed

7. Login into the maintenance page of the Pluto. Login with username “controller” and the password “Pluto”.

11.9 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 and ip-address will not be changed. Configurations and iProtect data will be removed.

7. The Pluto can be linked with iProtect again. See chapter 11.1.

12 Technical data

12.1 Pluto

12.2 Orion