*iProtect™ - Pager charging cabinet - Ooperon / Pager services
Installation Manual | TM-20231129 iProtect Access / Security | Functionalities | Pager charging cabinet Ooperon / Pager services  | 
|
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.
Table of contents
- 1 Table of contents
- 2 1. Introduction
- 3 3. How does it work
- 3.1 3.1 System setup
- 4 4. Support and license
- 5 5. Functionalities
- 6 6. iProtect - pager charging cabinet hardware connection
- 7 7. iProtect - pager charging cabinet implementation
- 7.1 7.1 Phone number
- 7.2 7.2 Person profile and person pager number
- 7.2.1 7.2.1 Freeselect
- 7.2.2 7.2.2 FreeText
- 7.2.3 7.2.3 Dialogue definition
- 7.3 7.3 Event layout for ESPA
- 7.4 7.4 Event format
- 7.5 7.5 Procedure and Action
- 8 Daily use
1. Introduction
This document explains how you can create a connection with a pager charging cabinet delivery by Ooperon or Pager services. To control the programming and issuing of pagers by iProtect
This document provides an overview of the functionalities and steps required to connect the pager charger to iProtect.
3. How does it work
The protocol they use is espa 4.4.4. Iprotect can now send espa message to an espa node with an alarmaction. We send basically a ‘special’ version of the transaction string to the node. You can now define a ‘special’ transaction with the help of the eventlayout and transactionformat dialogue.
3.1 System setup
The connection between iProtect and Pager charging cabinet / is based on RS232.
4. Support and license
Below is an overview of support for both the hardware and the software, including the necessary license:
Version | Protocol | Based on document |
|---|---|---|
Version 10.3.13 | CV4-v4 |
|
Version 10.4.14 | CV4-v7 |
|
Support | Version | Maximum | License/Part number |
|---|---|---|---|
iProtect | >= 10.3.xx |
|
|
|
| ||
Pluto |
|
| IPC-PLUTO |
Orion |
| Max 1 Pager charging cabinet per (USB) Orion (PRT2 only) | IPC-ORION |
Delock converter (item No. 62919) | Delock RS232<>RS485 |
| RS-232 DB9 TO RS-485 |
Ooperon |
|
| Per pager (not implemented in iProtect yet) |
5. Functionalities
A profile is issued when a user logs in/logs in to the TCS start service. A card reader is placed at each loading rack cabinet. By means of an espa 4.4.4. connection between the TCS and the Pager charging cabinet, the TCS will send a message containing the following data occurs in the text field of the ESPA string:
Description | Details |
|---|---|
Overall | The ESPA 4.4.4. iProtect can send ESPA message to an ESPA node with an alarmaction. We send basically a ‘special’ version of the transaction string to the node. We cannot receive messages for e.g. an intrusion- or fire panels. It’s only used for the pager system. |
| After a card is presented on our card reader attached to their cabinet they expect a messages with the following information: |
Profile issuance by TCS |
|
A profile is issued when a user logs in/logs in to the TCS start service. A card reader is placed at each loading rack cabinet. By means of an espa 4.4.4. connection between the TCS and the Pager charging cabinet, the TCS will send a message containing the following data occurs in the text field of the ESPA string: | |
IC nummer | 5 digits preceding zero, end with a comma fixed 00000 (5 zeros; reserved for future applications) |
Desired profile number | 5 digits preceding zero, end with a comma. Number from: 00001 t/m 99999 |
Cabinet number where the user presents the access card | 01-99 |
Person ID | 5 digits preceding zero, end with a comma. Number from: 00001 t/m 99999 |
User name | max 16 chars (justice requirement) |
6. iProtect - pager charging cabinet hardware connection
This chapter explains how the setup can be made in iProtect.
6.1 Orion <> pager charging cabinet connection
The connection to the pager charging cabinet is made by an RS485 connection from an Orion PRT2 (using the connector marked A,B,CC,S) to the pager charging cabinet RS232 connection. The conversion from RS485 <> RS232 is done by the Delock converter,
The cable length between Ooperon and Delock RS232/RS485 converter: Max. 2 Mtr.
The cable length between Orion and Delock RS232/RS485 converter: Max. 30 Mtr.
6.2 Node setup
In iProtect, browse to menu: Installation | Hardware | Node
Right click, add a Node
Field | Content | Comment |
Name | logical name | e.g. Espa Ooperon / pager services /charging cabinet |
Node type | ESPA |
|
Communication | Serial |
|
Baudrate | 9600 (default) | 19200, 38400, 57600, 115200 are supported |
Port Setting | N81 (default) | Other Port settings are not supported |
Disconnect delay (sec) | 2 (default) |
|
Device Id | 2 | Also depended on settings in pager charging rack |
All Other fields are optional.
If more than one connection is needed you can create an extra node.
6.2.1 Cabling Orion <> Delock converter
Orion (RS485) | Cable lenght | Delock converter Screw | Delock RS232 | Cable lenght | pager charging cabinet |
A | Max. 30 meter | T/R- | RS-232 DB9 female with screws | Max. 2 meter | Ooperon / Pager services hardware |
B | T/R+ | ||||
CC | GND |
For A and B use a twisted cable pair.
7. iProtect - pager charging cabinet implementation
This chapter explains how the setup can be made in iProtect.
7.1 Phone number
Create a phone number that is needed for the correct functioning of the system
In iProtect, browse to menu: General | Contact
Right click, add a Contact
Add phone number: 00000
Field | Label text |
|---|---|
Person | “Empty” |
Description | Logical name |
Connect type | Phone number |
Phone number | 00000 |
Default | TRUE |
7.2 Person profile and person pager number
Create a Freeselection- and Freetext for the person dialogue.
Free selection: Profile
Free text: Pager number
Free text: Pager person name (optional also the person name can be used)
Profile: Is taken over from
Programma van Eisen Personenzoekinstallatie / Mobiele alarminstallatie
7216.11.R.001.h.GvdV 24 juli 2023
In the example below, Freeselect-1 and Freetekst -14 / Freeuniquetekst 1 have been used:
In iProtect, browse to menu: Installation | Settings | Custom definition | Field definition
7.2.1 Freeselect
Select in the treeview: PERSON.FREESELECT1
Field | Label text |
|---|---|
English, Dutch, German | Profile |
Right mouse button on saved FREESELECT1, Add option
For the sequence numbers, take over the profilenumbers which have been programmed in the Ooperon / Pager services application. E.g. 12001,12002, etc..
Profiles are created in the “pager charging cabinet”. When using the prescribed connection method, no option is described to synchronize the profiles with iProtect. The profiles must therefore be added manually.
7.2.2 FreeText
Select in the treeview: PERSON.FREETEXT14 (iProtect version 10.3.xx)
Field | Label text |
|---|---|
English, Dutch, German | Pager/ Pmdt number |
Select in the treeview: PERSON.FREEUNIQUETEXT1 (iProtect version 10.4.xx)
Field | Label text |
|---|---|
English, Dutch, German | Pager/ Pmdt name |
7.2.3 Dialogue definition
In iProtect, browse to menu: Installation | Authorization | User group
Select the User group where the fields should be added
Open (+) in the treeview: User group | Dialogue definition | Person | User defined
Field | Content | |
|---|---|---|
Freeselect Position | 1 | |
Item | ||
Table | PERSON | FREESELECT1 |
Properties | ||
Show | Enabled (TRUE) | |
Field | Content | |
|---|---|---|
Freetext Position | 2 | |
Item | ||
Table | PERSON | FREETEXT14 (iProtect 10.3.xx) |
Properties | ||
Show | Enabled (TRUE) | |
7.3 Event layout for ESPA
To enable the special display text for the ESPA Node, an ESPA event layout needs to be created.
In iProtect, browse to menu: General | Settings | Event settings | Event layout
Add Event layout
Field | Label text |
|---|---|
English, Dutch, German | ESPA layout |
Right mouse button on saved event layout, Add event layout
In the example below, a normal subscriber access transaction is used. Based on the person dialogue settings.
Remember, in a normal situation: Person Identification, Profile number, Charging rack cabinet number Pager name / Person name and IC-number.
A fixed number of digits can be determined. For this a ‘minimum field length’ can be used.
In case of Operon: It’s mandatory it’s ‘filled’ with the digit zero (ASCII 48).
7.3.1a Notification data details (iProtect 10.3)
7.3.1.1 Notification 1
Field | Content | Field | Content |
Event: | Access for subscriber card | Number | 1 |
English: | Access pager | Dutch: | Toegang pager |
German: | Zugang auf Pager |
|
|
Table: | PERSON (by) | Column: | Freetext 14 |
Event layout | |||
Minimal field length: | 5 | Filler char(ASCII): | 48 |
Maximal field length |
|
|
|
7.3.1.2 Notification 2
Field | Content | Field | Content |
Event: | Access for subscriber card | Number | 2 |
English: | Profile | Dutch: | Profiel |
German: | Profil | ||
Table: | PERSON (by) | Column: | Freeselect1 |
Event layout | |||
Minimal field length: | 5 | Filler char (ASCII): | 48 |
Maximal field length |
|
|
|
7.3.1.3 Notification 3
Field | Content | Field | Content |
Event: | Access for subscriber card | Number | 3 |
English: | Reader | Dutch: | Lezer |
German: | Leser | ||
Table: | READER (at) | Column: | CODE |
Event layout | |||
Minimal field length: | 2 | Filler char (ASCII): | 48 |
Maximal field length |
|
|
|
'Charge rack cabinet number' Please note that we put this number in the 'code' field of the reader that 'controls' the pager charging cabinet (if code is already used for something else, abbreviation can also be used).
7.3.1b Notification data details (iProtect 10.4)
7.3.1.1 Notification 1
Field | Content | Field | Content |
Event: | Access for subscriber card | Number | 1 |
English: | Profile | Dutch: | Profiel |
German: | Profil |
|
|
Table: | PERSON (by) | Column: | Freeselect 1 |
Event layout | |||
Minimal field length: | 5 | Filler char(ASCII): | 48 |
Maximal field length |
|
|
|
7.3.1.2 Notification 2 (new demand in 7216.11.R.001.h.GvdV 24 juli 2023)
Field | Content | Field | Content |
Event: | Access for subscriber card | Number | 2 |
English: | Name | Dutch: | Naam |
German: | Name | ||
Table: | PERSON (by) | Column: | Freeuniquetekst 1 |
Event layout | |||
Minimal field length: | 2 | Filler char (ASCII): | 48 |
Maximal field length | 16 |
|
|
7.3.1.3 Notification 3
Field | Content | Field | Content |
Event: | Access for subscriber card | Number | 3 |
English: | Reader | Dutch: | Lezer |
German: | Leser | ||
Table: | READER (at) | Column: | CODE |
Event layout | |||
Minimal field length: | 2 | Filler char (ASCII): | 48 |
Maximal field length |
|
|
|
'Charge rack cabinet number' Please note that we put this number in the 'code' field of the reader that 'controls' the pager charging cabinet (if code is already used for something else, abbreviation can also be used).
7.4 Event format
We don’t have ‘free fixed text’ as such in event format but we can do that in the alarmaction. And we also need a ‘event format’ to strip away the extra spaces and headings of a normal transaction.
To enable the special display text for the ESPA Node, an ESPA event layout needs to be created.
In iProtect, browse to menu: General | Settings | Event settings | Event format
Add Event format
Field | Content | Field | Content |
English: | ESPA format | Dutch: | ESPA format |
German: | ESPA format | ||
Other | |||
Show missing items: | Enabled (TRUE) | ||
Note that we need a single ',' with the data separator and item separator and you don't want any extra text when the transaction time is 'guessed'.
Example:
7.5 Procedure and Action
Now a message has to be sent to the ESPA node when an access key has access to an pager charging cabinet. For this, a procedure must be created on the access transaction for 'each' Ooperon cabinet reader:
In iProtect, browse to menu: General | Settings | Procedure
Add procedure
Field | Content | Field | Content |
Name: | ESPA | ||
Subsystem: | Access | Event: | Access for subscriber card |
Table | |||
Table 1: | Reader | At | <Reader at cabinet> |
Table 2: | one of |
|
|
Save this record and link an Action to this procedure.
In treeview, select Action list below the procedure.
Right mouse button, Add action:
Field | Content | Field | Content |
English: | Send ESPA | ||
Long description: | Send ESPA message | ||
Selection | |||
Operation: | Automatic | ||
Action selection: | Send ESPA message to Node | ||
Node: | <Select Node (hardware)> | ||
Phone: | ESPA (Chapter 6.1) | ||
ESPA header: | Call to pager** | ||
ESPA priority: | Reserved | ||
ESPA call type: | Reserved | ||
ESPA long/variable format (hex): | @,00000 (iProtect 10.3.xx) or @ (iProtect 10.4.xx) | ||
Event | |||
Event layout: | ESPA layout (Chapter 6.3) | ||
Event Format: | ESPA format (Chapter 6.4) | ||
Make a note of all 'reserved' settings. Remember we had to add 5 zeros (00000). This can be achieved with the 'ESPA format' field. It works like the intercom field where @ is the placeholder for the event text and here we start with '00000' for that text.
** If Ooperon profile CV4-v4 protocol is used, select by ESPA header <Call to pager>
If this selection is made the output format will as example below
All data is here in the 2 US part (ESPA compliant)
The following units are used for profile issuance:
US (always fixed 00000 - 5 zeros).
US (Person Identification, Profile number, cargo rack number, IC number)
US (always 0 - single zero)
Standard ESPA 4.4.4 protocol is used as described in the attached document ESPA 4.4.4.pdf. The conditions of the data required in the 2 US field for profile issuance, are as follows:
Personal Identification: number 00001 to 99999.
Profile number: number 00001 to 99999
Load draw box: number 01 to 99
IC number: fixed 00000 (5 zeros, reserved for future application)
If Ooperon profile CV4-v7 protocol is used, select by ESPA header <Ooperon profile CV4-v7.>
if this selection is made the output format will as example below (not ESPA compliant)
Standard ESPA 4.4.4 protocol is used as described in the attached document ESPA 4.4.4.pdf. The values of the data required in the US fields for profile issuance, are as follows:
[US] IC number: 10000 to 99999
[US] Desired profile number: 00001 to 99999
[US] User name: 16 characters
[US] Locker number where user presents his/her card: number 01 to 99
Example:
IC number = 12123; Desired profile number = 110001; Name = J. Bastiaansen; Locker = 03 SOH 1 STX 1 US 12123 RS 2 US 11001 RS 3 US J. Bastiaansen RS 4 US 03 ETX CSS
Daily use
Example of person dialog, adding pager number and pager profile to a person.
By adding a beeper number and an pager profile to a person, when presenting an access card to the card reader, an unused pager will be loaded with the matching profile and the pager can be taken out.
In iProtect version 10.5 it is possible to use a unique free (pager) number (range). If the number already exists, you will get an error message.
button (next free number)
manual entry