OPC_SCHRACK ver. 4.7 MANUAL

Warsaw 20.11.2020

OPC_SCHRACK VER. 4.7

MANUAL

Zwolenska 22/27

04-761 Warszawa

tel./fax: (+48 22) 615-89-84

e-mail: tiger-soft@tiger-soft.com.pl

Table of contents

1) Introduction
2) Installing the I/O driver
3) Software registration
4) Configuring the OPC_SCHRACK
5) Configuring an OPC client
6) Starting and stopping the OPC_SCHRACK

1) Introduction

The OPC_SCHRACK ver. 4.7 is a communication driver which allows to connect BMS system with several fire protection systems from Schrack Seconet via RS232 or ETHERNET channels. The Integral Standard Protocol (ISP) is used by the driver. The computer with BMS system uses a serial port (RS232) or ETHERNET network card. Schrack central can use one of the following modules: B3-USI4,B3-LPI,B4-USI for a RS232 or network cards like B5-NET2-FXM for an ETHERNET. The driver can be connected to BMZ Integral IP, Integral C or Integral system.

It includes the following features:

Very effective method of communication which uses ISP protocol.
Works as a service. It works even after logging out from the system.
Devices from Schrack-Seconet can be connected via RS232 or ETHERNET.
Supports all main commands and events which exist in Schrack.
Ability of sending commands to the central from the computer system.
Multithreading which allows to do tasks in a very efficient way, without a heavy load of the processor.
Possibility of working with several Schrack units simultaneously.
Very effective connection to BMS system using OPC.
Easy to use configuration.
Monitoring of the communication process.
Automatically re-running the communication after failure.

2) Installing the I/O driver

Run OPC_SCHRACK_INSTALL.EXE.Installation software will put OPC_SCHRACK files into the C:\Program Files\TIGER_SOFT\OPC_SCHRACK_4_7 directory or another directory chosen by the user. Shortcuts to the manual and registration software exist in the group OPC_SCHRACK ver. 4.7 (access from the Start menu). The driver is installed as a service.

3) Software registration

OPC_SCHRACK should be registered after installation using TIGER-SOFT internet service. SOFTWARE REGISTRATION from OPC_SCHRACK group should be started first. This program generates file gen_lic.lic and saves it in the main driver directory. Then you have to connect to http://www.tiger-soft.com.pl/Registration/registration.html, fill the form and receive the registration code. This code should be put to the editable field in the SOFTWARE REGISTRATION. Press OK to finish registration process.

4) Configuring the OPC_SCHRACK

The file - Configuration.oes is used for the driver configuration. It exists in the same directory like the OPC_SCHRACK.exe. An example of the file is presented below.

# OPC_SCHRACK - configuration program

# CHANNEL - channel number
# ACTIVE - channel activation. Possible values YES,NO
# RS232_ETH - RS232 (COM) or ETHERNET connection. Possible values 0-RS232 1-ETH

# COM parameters
# NR_COM from the range 1-99
# BAUD_RATE [bits/s]. Possible values: 9600,14.70,19200,384.7,57600,115200
# PARITY N-None,E-Even,O-Odd

# ETH parameters
# CL_IP is a local driver ip address
# SCHRACK_IP is a Schrack-Seconet central ip address
# USER is an user name defined in a central
# PASSWORD is an user password defined in a central

# ETH parameters
# CL_IP is a local driver ip address
# CL_PORT is a local driver port address
# SCHRACK_IP is a Schrack-Seconet central ip address
# USER is an user name defined in a central
# PASSWORD is an user password defined in a central

# TIMEOUT [s]. Possible values from the range 1-9999 [s]

# ISP parameters
# CENTRAL - Address of the central unit has the following structure Subnet.Node.Client, where Subnet=0-63; Node=0-63; Client=0-7;
# CLIENT - Address of the client has the following structure Subnet.Node.Client, where Subnet=0-62; Node=0-61; Client=0-5;
# TOKENTIME [ms]. Possible values from the range 30-250 [ms]
# SS=1 - Additional status will be sent in the older byte of the word.0 - will be always 0
# AS=1 - Driver allows to send commands to the fire alarm central unit (XccCTttAaa[sa]). 0 - Sending control commands is not allowed.
# AG=1 - Driver will set group status to alarm when an element from this group has alarm status.

# OPC points
# The list of points, configured in the OPC client in the following format:
# XccTtt[st]Aaa[sa], where cc-channel number, tt-type(0-16,255,4095), aa-address of the element(1-65535), sa-sub address of the element(0-255)
# or XccCTttAaa[sa] for control points, sent by the OPC client

#******************** 1 ********************

CHANNEL=1
ACTIVE=YES
RS232_ETH=1

#RS_232
NR_COM=1
BAUD_RATE=19200
PARITY=E

#ETH
CL_IP=192.168.1.53
CL_PORT=11113
SCHRACK_IP=192.168.1.71
USER=Tiger-Soft
PASSWORD=Tiger-Soft

TIMEOUT=30

CENTRAL=0.0.0
CLIENT=0.0.1
TOKENTIME=250
SS=1
AS=1
AG=1

# OPC points

X01T0A101[255]
X01T0A101[1]
X01T1A101[255]
X01T2A1[255]
X01T2A2[255]
X01T2A3[255]
X01CT5A65535[255]
X01CT2A65535[255]
X01CT4095A65535[255]

#******************** 2 ********************

CHANNEL=2
ACTIVE=YES
RS232_ETH=1

#RS_232
NR_COM=2
BAUD_RATE=19200
PARITY=E

#ETH
CL_IP=192.168.1.54
CL_PORT=11113
SCHRACK_IP=192.168.1.72
USER=Tiger-Soft
PASSWORD=Tiger-Soft

TIMEOUT=30

CENTRAL=0.0.0
CLIENT=0.0.1
TOKENTIME=250
SS=1
AS=1

# OPC points

X02T0A101[255]
X02T0A101[1]
X02T1A101[255]
X02T2A1[255]
X02T2A2[255]
X02T2A3[255]
X02CT5A65535[255]
X02CT2A65535[255]
X02CT4095A65535[255]

5) Configuring an OPC client

OPC_SCHRACK is an OPC server. Every software that can be an OPC client should work fine with OPC_SCHRACK. ProgID is TS.OPC_SCHRACK.
ItemID can be set like this:

ItemID	Description	Types	Addresses	Returned values
XccCommunication	Presents the status of the communication between OPC_SCHRACK and SCHRACK central unit, where cc - channel number.			Value 1 means that communication is OK, 0 there is no communication.
XccTttAaa[sa]	Shows the status of a zone or an element, where cc - channel number; tt - type; aa - address; sa - sub address. Example: X01T2A1[105], reads information from central connected to channel number 1, about the status of the sub element 105 from group 1, type 2.	tt 0 - zone 1 - input 2 - output 3 - external 4 - printer 5 - CI 6 - battery 7 - net 8 - module active 9 - module passive 10 - delay layer 11 - FBP fire brigade panel 12 -SCU 13 - intervention 14 - connection 15 - master system 16 - loop 17 - flooding zone 18 - remote access 255 - general	sa 0-254 - sub address of an element 255 - for a zone	status 0 - idle ss=0-general 1 - alarm ss=0; 1-simulation; 2-smoke; 3-temperature; 4-sabotage; 5-check; 6-unconfirmed ss=(ss or 80hex) for a group, when AG=1 and an element from this group has alarm status 2 - revision alarm ss=0; 2-smoke; 3-temperature; 4-sabotage 3 - fault ss=0; 1-short circuit; 2-open circuit; 3-simulation; 4-external; 5-overload; 6-not present; 7-earth fault; 8-switch 2; 9-configuration; 10-startup; 11-connection; 12-mapping 4 - revision fault ss=0; 1-short circuit; 2-open circuit;5-overload; 6-not present; 7-eartch fault; 8-switch 2;9-configuration; 10-startup; 12-mapping 5 - disablement ss= 0;1-key switch; 2-automatic; 3-FBP; 4-emergency 6 - internal disablement ss=0 7 - revision ss=0 8 - activation ss= 0;1-automatic; 2-external; 3-FBP 9 - deactivation ss= 0;1-FBP 10 - hard alarm ss=0 11 - enabled ss=0; 1-level 1; ... 255-level 255; 12 - active (pollution active in the case of a zone) ss=0; 1-simulation; 2-automatic 13 - revision active ss=0 14 - warning ss=0 15 - explore ss=0 16 - terminated ss=0 17 - revision activation ss=0; 1-automatic; 2-external; 3-FBP 18 - paper feed ss=0 19 - silent alarm ss=0; 1-simulation; 2-smoke; 3-temperature; 4-sabotage 20 - preactivation ss=0 21 - release ss=0; 1-external 22 - preactive ss=0; 1-simulation 23 - revision preactive ss=0 24 - low battery ss=0
XccCTttAaa[sa]	Allows to sent an control command to a group or an element, where cc - central number; tt - type; aa - address; sa - sub address. Example: X01CT2A1[105], control commands for central connected to channel number 1, sub element 105 from group 1, type 2.	tt 0 - zone 1 - input 2 - output 3 - external 4 - printer 5 - CI 6 - battery 7 - net 8 - module active 9 - module passive 10 - delay layer 11 - FBP fire brigade panel 12 - SCU 13 - intervention 14 - connection 15 - master system 16 - loop 17 - flooding zone 18 - remote access 255 - general	sa 0-254 - sub address of an element 255 for a zone	commands 0 - switch off 256 - turn off acoustic buzzers 512 - turn off fire protection equipment controllers 1024 - emergency operation, disable elements in alarm state 1 - switch on 257 - turn on acoustic buzzers 513 - turn on fire protection equipment controllers 1025 - emergency operation, turn on elements that were turned off 2 - set 3 - reset 259 - alarm reset 515 - acoustic reset 771 - page number reset 1027 - message number reset 4 - revision mode 5 - test 6 - simulate alarm 7 - simulate fault 8 - simulate active 9 - internal switch off 10 - reactivate 266 - reactivate acoustic 11 - initialize 12 - adjust top of page 13(000D hex) - switch to level 0 269(010D hex) - switch to level 1 ... 3853(0F0D hex) - switch to level 15 781 - switch to level 3 14 - mapping 15 - startup stop 16 - simulate pre active
XccCT5A65535[255]	Allows to sent the internal acoustic off command.			commands 3 - reset
XccCT2A65535[255]	Allows to sent the external acoustic off command.			commands 515 - acoustic reset
XccCT4095A65535[255]	Allows to sent the summary alarm reset command.			commands 259 - alarm reset

6) Starting and stopping the OPC_SCHRACK

The driver can be run from the service manager on Windows. Second way is to use command line with commands: OPC_SCHRACK -s for starting and OPC_SCHRACK -z, for stopping it. The service OPC_SCHRACK can be also configured to start automatically after operating system is started.

WARNING!!! Additional parameters, concern security of the service and DCOM component have to be set. In order to do it dcomcnfg.exe should be run. User of the service should be chosen from computer users (for example system administrator). The same user should be set for DCOM TIGER-SOFT OPC_Schrack (Identity).