Warsaw 10.01.2013

Mrowcza 243, IV pietro

04-697 Warszawa

tel.: (+48 22) 213-92-69

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

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

www: www.tiger-soft.com.pl

Table of contents

1) Introduction
2) Redundancy
3) Pre-configured hardware solution
4) Installing the I/O driver
5) Software registration
6) Configuring the MODBUS_SCHRACK
7) Configuring a MODBUS client
8) Starting and stopping the MODBUS_SCHRACK

1) Introduction

    The MODBUS_SCHRACK ver. 1.2 is a communication driver which allows to connect BMS system with a fire protection system from Schrack Seconet. The Integral Standard Protocol (ISP) is used by the driver. The computer with BMS system uses a serial port (RS232). Schrack central can use one of the following modules: B3-USI4,B3-LPI,B4-USI. The driver can be connected to BMZ Integral C or BMZ Integral system.

It includes the following features:

1. Very effective method of communication which uses ISP protocol.
2. Works as a service. It works even after logging out from the system.
3. Supports all main commands and events which exist in Schrack.
4. Ability of sending commands to the central from the computer system.
5. Multi-threading which allows to do tasks in a very efficient way, without a heavy load of the processor.
6. Easy connection to BMS system using standard MODBUS protocol.
7. Easy to use configuration.
8. Monitoring of the communication process.
9. Automatically re-running the communication after failure.
10. Possibility of using it in redundant systems. Automatically switch between channels in a case of broken communication.

2) Redundancy

    The MODBUS_SCHRACK ver. 1.2 can be installed on two computers in a redundant configuration. There are two communication channels. Normally when both channels are active (physically connected, with active modbus communication) only one channel receives messages from Schrack panel. The value of Communication point for this channel is 1. Let's call it Primary and the second channel - Secondary. When a Primary communication with Schrack panel is broken the Secondary channel will be set as a basic connection to a panel. When a Primary communication with MODBUS device is broken (connection is broken or there is no device which read information from driver via modbus protocol) the Secondary channel will be set as a basic connection to a panel too.
When a problem with Primary connection is fixed then a communication process will return to Primary channel or stay on Secondary channel if the redundancy register for the Primary channel has a value of 1.
Both drivers are working in the same way. It means that there is no need to specify which driver is Primary, which Secondary. Usually when everything is run at the same time the driver which is connected to a first port in a Schrack panel will became Primary.

3) Pre-configured hardware solution

    The MODBUS_SCHRACK ver. 1.2 can be delivered with dedicated hardware. It is usually small PC computer with Microsoft Windows Embedded operating system. This computer has already MODBUS-SCHRACK installed and registered. So, there is no need to do procedures from point 4 and 5 of this manual. However there is usually a need to change a Configuration.cms file as it was described in point 6. Usually a Schrack panel is connected to COM1 and MODBUS device is connected to COM2. The MODBUS-SCHRACK service is configured to start automatically after an operating system starts. You can connect to a computer by using Remote Desktop. A computer has following default parameters:

Computer name	User	Password	Workgroup	IP address
MSSCHRACK1	Administrator	$tsschrack01	TS	10.10.1.101
MSSCHRACK2	Administrator	$tsschrack02	TS	10.10.1.102

There is also one directory, called Exchange which is a shared folder on each computer.

4) Installing the I/O driver

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

5)Software registration

MODBUS_SCHRACK should be registered after installation using TIGER-SOFT internet service. SOFTWARE REGISTRATION from MODBUS_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.

6)Configuring the MODBUS_SCHRACK

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

# MODBUS_SCHRACK - configuration program

# MODBUS COM parameters
# MODBUS_NR_COM from the range 1-99
# MODBUS_BAUD_RATE [bits/s]. Possible values: 9600,14400,19200,38400,57600,115200
# MODBUS_PARITY N-None,E-Even,O-Odd
# MODBUS_TIMEOUT [s]. Possible values from the range 1-9999 [s]
# MODBUS_SLAVE_ID - ID of the driver. Possible values from the range 1-247

MODBUS_NR_COM=2
MODBUS_BAUD_RATE=57600
MODBUS_PARITY=E
MODBUS_TIMEOUT=10
MODBUS_SLAVE_ID=1

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

NR_COM=1
BAUD_RATE=57600
PARITY=E
TIMEOUT=10

# ISP parameters
# TOKENTIME [ms]. Possible values from the range 30-250 [ms]
# 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-63; Node=0-63; Client=0-7;
# 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 (CTttAaa[sa]). 0 - Sending control commands is not allowed.

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

# Schrack Points
# The list of points, in the following format:
# Rrr.Ttt[st]Aaa[sa], where rr-modbus registry number(2-65535), tt-type(0-16,255,4095), aa-address of the element(1-65535), sa-sub address of the element(0-255)
# or CTttAaa[sa] for control points, sent by the OPC client
# Redundancy register Rrr.B, where rr-modbus register number(2-65535). This register can be written by a MODBUS master device.
# The value of the register equals 1 means that the backup channel has already a communication with central and the communication shouldn't return to this primary channel.

[0.0.0]
R101.T0A101[255]
R102.T0A101[1]
R103.T0A110[1]
R104.T1A101[255]
R105.T1A102[255]
R106.T1A103[255]
R107.T2A1[255]
R108.T2A2[255]
R109.T2A3[255]
R110.T3A1[255]

#Commands
R2.CT5A65535[255]
R3.CT2A65535[255]
R4.CT4095A65535[255]
R11.CT2A1[255]
R12.CT2A2[255]
R13.CT2A3[255]
R14.CT1A101[255]
R15.CT1A102[255]
R16.CT0A101[255]
R17.CT0A101[1]

#Redundancy register
R20.B

7)Configuring a MODBUS client

MODBUS_SCHRACK is an MODBUS slave device with ID configured in SLAVE_ID (Configuration.cms). Every device that can cooperate with MODBUS slave device using Modbus RTU protocol should work fine with MODBUS_SCHRACK. The driver uses holding registers from address 40001.There is a Communication status value in the first register (40001). Next registers contain values of points configured in the Configuration.cms file. The order of modbus addresses is the same like order of points in the Configuration.cms file.

Example:

Schrack point from Configuration.cms	Modbus Address	Holding Register Number
R101.T0A101[255]	40101	101
R102.T0A101[1]	40102	102
R103.T0A110[1]	40103	103
R104.T1A101[255]	40104	104
R105.T1A102[255]	40105	105
R106.T1A103[255]	40106	106
R107.T2A1[255]	40107	107
R108.T2A2[255]	40108	108
R109.T2A3[255]	40109	109
R110.T3A1[255]	40110	110
R2.CT5A65535[255]	40002	2
R3.CT2A65535[255]	40003	3
R4.CT4095A65535[255]	40004	4
R11.CT2A1[255]	40011	11
R12.CT2A2[255]	40012	12
R13.CT2A3[255]	40013	13
R14.CT1A101[255]	40014	14
R15.CT1A102[255]	40015	15
R16.CT0A101[255]	40016	16
R17.CT0A101[1]	40017	17

Following Schrack Points can be configured in the Configuration.cms file.

8) Starting and stopping the MODBUS_SCHRACK

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