PROFIBUS DP-slave/ FLOW-BUS interface · 2016-12-05 · PROFIBUS DP-slave/ FLOW-BUS interface Doc. no.: 9.17.012J Date: 25-07-2011 ... RS485-based fieldbus communication system for

Instruction manual

PROFIBUS DP-slave/ FLOW-BUS interface

Doc. no.: 9.17.012J Date: 25-07-2011

ATTENTION Please read this instruction manual carefully before installing and operating the instrument. Not following the guidelines could result in personal injury and/or damage to the equipment.

.

BRONKHORST HIGH-TECH B.V.


Short form start-up

All necessary settings for this module are already performed at Bronkhorst High-Tech B.V.

To follow next steps carefully is the quickest way to get this module operational in your own Profibus

environment.

1. Build-up your FLOW-BUS system with instruments from Bronkhorst High-Tech B.V. and make

sure the FLOW-BUS is powered.

2. Connect FLOW-BUS to the RJ-45 connector of the converter (default FLOW-BUS address is 1) .

When the green FLOW-BUS status LED is continuously on, communication to FLOW-BUS is OK.

To install the module newly to the FLOW-BUS handle as described in 3.3.1. For error situations

see 3.3.

3. The converter module default will have Profibus station address 2.

If you want to change this, connect the RS232 connector of the converter to any (Windows) PC

by means of serial cable without crossings (one-on-one).

Install FlowFix (a Bronkhorst High-Tech utility program to change fieldbus addresses).

Start FlowFix and select the COM-port where the converter has been connected to.

Wait a moment while FlowFix tries to open communication and following screen appears:

At Address the actual address on the Profibus can be read and changed.

Baudrate settings are not necessary for the converter. It will adapt automatically to the baudrate

of the master.

New address will be valid after pressing OK and after the converter has been reset/powered-up.

This screen can be called again via [Options][Configuration].

Changing the Profibus station address by the master configurator however is not possible.

4. Connect Profibus to the Profibus connector. The default baudrate is set to 12000 kBits/sec.

The blinking green Profibus status LED will burn continuously if communication with Profibus

has been established.

5. Load the GSD-file (HIL_7501.GSD) for the COM_DPS (PRODPS) module on the diskette into your

Profibus master.

6. Start the configuration tool for your Profibus network. Add the COM_DPS (PRODPS) module to

your network configuration. Next configure the COM_DPS (PRODPS) module in the configuration

program.

Depending on the execution form (A...D), several module types are needed for this slave.

If the PRODPS module is configured to use one of the fixed configurations (configuration B is

default), it will contain eight (data) modules (C and D will need different modules).

These data-modules are shown in the following table. Used data-modules are modules without

consistency. See chapter 3 for more detailed information.


Needed modules for configuration B (default)

Module Length Byte/Words Input/Output

1 16 Words Input

2 16 Words Input

3 16 Words Input

4 16 Words Input

5 16 Words Input

6 16 Words Input

7 16 Words Input

8 16 Words Output

See appendix 2, 3 and 4 for module settings for all configurations

7. Program the interface structures for operation of the FLOW-BUS instruments in your Profibus

master. See chapter 4 for detailed information.

NOTE:

If you use execution form A or D, you have to start the FLOW-BUS scan by the converter module.

Just press the switch on the converter and release it when both green and red LED’s are on.

Wait for approx. one minute, and proceed with the next point (see 3.3.2 for more details).

This scan detects the amounts of operable instruments connected to the FLOW-BUS and starts

from address 1 (default). This start address for scanning can be changed via Propar parameter 4

from process 125. See 4.2.3.4 for more details.

8. Your master is ready now to operate FLOW-BUS instruments connected to the Profibus DP-slave

protocol converter. See chapter 3 for available parameters.


Even though care has been taken in the preparation and publication of the contents of this manual, we do not assume legal or other liability for any inaccuracy, mistake, mis-statement or any other error of whatsoever nature contained herein. The material in this manual is for information purposes only, and is subject to change without notice.

Bronkhorst High-Tech B.V. July 2011

Warranty

The products of Bronkhorst High-Tech B.V. are warranteed against defects in material and workmanship for a period of three years from the date of shipment, provided they are used in accordance with the ordering specifications and the instructions in this manual and that they are not subjected to abuse, physical damage or contamination. Products that do not operated properly during this period may be repaired or replaced at no charge. Repairs are normally warranteed for one year or the balance of the original warranty, whichever is the longer. See also paragraph 9 of the Conditions of Sales.

The warranty includes all initial and latent defects, random failures, and indeterminable internal causes.

It excludes failures and damage caused by the customer, such as contamination, improper electrical hook-up, dropping etc.

Re-conditioning of products primarily returned for warranty service that is partly or wholly judged non-warranty may be charged for.

Bronkhorst High-Tech B.V. prepays outgoing freight charges when any part of the service is performed under warranty, unless otherwise agreed upon beforehand. However, if the product has been returned collect to Bronkhorst High-Tech B.V., these costs are added to the repair invoice. Import and/or export charges, foreign shipping methods/carriers are paid for by the customer.



Warranty............................................................................................................................. 5

1 INTRODUCTION .......................................................................................................... 9

1.1 General description ............................................................................................................................. 91.1.1 Technical information ................................................................................................................... 91.1.2 Cables .......................................................................................................................................... 91.1.3 Termination .................................................................................................................................. 9

1.2 Model configuration ........................................................................................................................... 101.3 Power supply ..................................................................................................................................... 101.4 In/output signals................................................................................................................................. 10

1.4.1 RJ45 connector for connection to FLOW-BUS .......................................................................... 111.4.2 D-connector for connection to PROFIBUS................................................................................. 111.4.3 D-connector for connection to RS232 ........................................................................................ 111.4.4 RS232 interface.......................................................................................................................... 12

1.4.4.1 General description ............................................................................................................. 121.4.4.2 Specifications ...................................................................................................................... 121.4.4.3 P.C. board jumper setting ................................................................................................... 12

1.4.5 EMC and cables ......................................................................................................................... 131.4.6 Hilscher GmbH Profibus COM-DPS module.............................................................................. 13

1.5 Specifications .................................................................................................................................... 141.5.1 Housing ...................................................................................................................................... 141.5.2 EMC and housing....................................................................................................................... 141.5.3 Electrical specifications protocol converter ................................................................................ 141.5.4 Specifications of Hilscher GmbH Profibus COM-DPS module .................................................. 14

2 INSTALLATION.......................................................................................................... 15

2.1 General .............................................................................................................................................. 152.1.1 Receipt of equipment ................................................................................................................. 152.1.2 Return shipment ......................................................................................................................... 152.1.3 Service ....................................................................................................................................... 152.1.4 Installation .................................................................................................................................. 152.1.5 Configuration .............................................................................................................................. 162.1.6 Equipment storage ..................................................................................................................... 16

3 Operation................................................................................................................... 17

3.1 General information ........................................................................................................................... 173.2 Hardware installation ......................................................................................................................... 173.3 FLOW-BUS configuration.................................................................................................................. 18

3.3.1 Installation on the FLOW-BUS ................................................................................................... 183.3.2 Switch......................................................................................................................................... 183.3.3 Error/status codes on LED’s....................................................................................................... 19

3.4 Profibus configuration........................................................................................................................ 203.4.1 Profibus address ........................................................................................................................ 203.4.2 Profibus master .......................................................................................................................... 203.4.3 LED’s related to Profibus............................................................................................................ 21

3.5 Instrument parameter information (fixed configuration) .................................................................... 223.5.1 Measure ..................................................................................................................................... 223.5.2 Setpoint ...................................................................................................................................... 223.5.3 Serial number ............................................................................................................................. 223.5.4 Alarm info ................................................................................................................................... 223.5.5 Status ......................................................................................................................................... 223.5.6 Fluid number .............................................................................................................................. 233.5.7 Control mode.............................................................................................................................. 233.5.8 Counter value ............................................................................................................................. 233.5.9 Counter mode............................................................................................................................. 233.5.10 Counter setpoint mode............................................................................................................... 233.5.11 Counter setpoint ......................................................................................................................... 243.5.12 Counter limit ............................................................................................................................... 243.5.13 Sensor type ................................................................................................................................ 243.5.14 Reset .......................................................................................................................................... 243.5.15 Counter output mode.................................................................................................................. 24


3.5.16 Counter unit ................................................................................................................................ 253.5.17 Init/reset (key-parameter) ........................................................................................................... 253.5.18 Analog input................................................................................................................................ 253.5.19 Wink ........................................................................................................................................... 25

4 Protocol converter description................................................................................ 26

4.1 Interface overview.............................................................................................................................. 264.1.1 Configuration .............................................................................................................................. 264.1.2 Fixed configurations ................................................................................................................... 284.1.3 Flexible configuration ................................................................................................................. 29

4.2 Interface structure.............................................................................................................................. 304.2.1 Fixed configurations ................................................................................................................... 30

4.2.1.1 Modules with input data ...................................................................................................... 304.2.1.2 Modules with output data .................................................................................................... 314.2.1.3 Channel list ......................................................................................................................... 324.2.1.4 FLOW-BUS scan ................................................................................................................ 32

4.2.2 Flexible configuration ................................................................................................................. 334.2.2.1 Global channel list............................................................................................................... 354.2.2.2 Module list ........................................................................................................................... 354.2.2.3 Module parameter list.......................................................................................................... 364.2.2.4 Module channel list ............................................................................................................. 364.2.2.5 Module memory map .......................................................................................................... 374.2.2.6 Example .............................................................................................................................. 38

4.2.3 PROPAR parameters ................................................................................................................. 394.2.3.1 Process 0 ............................................................................................................................ 394.2.3.2 Process 113 ........................................................................................................................ 394.2.3.3 Process 118 ........................................................................................................................ 404.2.3.4 Process 125 ........................................................................................................................ 404.2.3.5 Example .............................................................................................................................. 42

5 TROUBLESHOOTING ............................................................................................... 43

Appendices

1 System configuration example 2 Fixed/default configuration (A+B) 3 Flexible/extended configuration (C) 4 Fixed configuration with variable amount of channels (D) 5 Operating a counter via PROFIBUS 6 Customer system description (if applicable)


9.17.012 page 9

1 INTRODUCTION

1.1 General description

FLOW-BUS is a 3-wire, RS485-based fieldbus communication system for parameter value exchange between digital BRONKHORST HI-TEC products. In this system each instrument/device is equipped with a micro-controller for its own dedicated task but also for exchanging parameter value information with other instruments/devices connected to the same FLOW-BUS system.

1.1.1 Technical information

FLOW-BUS systems may have a minimum of 2 and a maximum of 128 connections. The maximum length between the first and the last connection may be up to approx. 600 meters. Longer distances are only possible in combination with special bus-repeater modules. Each instrument/device connection T-part (stub) must be kept as short as possible (max. 50 cm advised). The baudrate used to transport messages is 187.5 kBaud. FLOW-BUS is a multi-master network with a token ring architecture.

1.1.2 Cables

For connecting instruments to the FLOW-BUS you need shielded cables with at least 3 wires (for data only). Recommended are twisted wire cables for RS485-communications with 100 or 120 Ohm impedance. All Bronkhorst High-Tech FLOW-BUS cables have also integrated power-supply wires. Best to use are Shielded (+Foiled) Twisted Pair patch-cables with RJ45 modular jack connectors (8-pins for data and power-supply connections).

In case of powering instruments or transporting data over longer distances Bronkhorst High-Tech offers also special RS485 FLOW-BUS datacable, with lower voltage-drop. Bronkhorst High-Tech can advise you when to use this special cable, but for most cases the standard patch-cables will do well.

When more cables are used in one system, they have to be connected as a daisy chain. This means that the total FLOW-BUS system has only one begin and one end. For connecting instruments to the bus, Bronkhorst High-Tech offers special drop-cables that enable you to build a daisy-chained network of FLOW-BUS modules.

1.1.3 Termination

For best quality of data transfer FLOW-BUS should be terminated correctly. Termination can be performed with special termination-connectors, offered by Bronkhorst High-Tech B.V.

At the begin of each FLOW-BUS system there always must be a resistor network as showed above. This begin-terminator needs to be part of your system. Bronkhorst High-Tech offers special begin-termination connectors with the resistor network in the drawing.

RS485-A

RS485-B

390 Ω

120 Ω

2K2 Ω

0 Vdc

+15 Vdc

RS485-A

RS485-B100 Ω

FLOW-BUS

Begin-termination End-termination

Connected modules


page 10 9.17.012

This handles correct termination but also gives a defined voltage on the RS485-A and -B line for even more reliability of the FLOW-BUS system.

At the end of the bus a termination resistor is needed. This end-terminator is also offered by Bronkhorst High-Tech and handles correct termination for the FLOW-BUS.

1.2 Model configuration

Standard there is only one model of this type of FLOW-BUS protocol converter available. The model name is:

PROFIBUS-DP/FLOW-BUS interface

1.3 Power supply

The module does not contain any internal power source, but is powered by the FLOW-BUS. The module will automatically switch-on when it is connected to the FLOW-BUS.

1.4 In/output signals

If applicable, connection of cables carrying in- or/and output signals is further explained in the customer system description (see appendices).


9.17.012 page 11

1.4.1 RJ45 connector for connection to FLOW-BUS

The shielded RJ45 modular jack connector has the following pin configuration:

Pinnumber Description

12345678

+ 15 Vdc supply 0 V (ref to +15Vdc ) Shield0 V (ref to +15Vdc ) + 15 Vdc supply 0 V (RS485) RS485 – B RS485 – A

1.4.2 D-connector for connection to PROFIBUS

The female PROFIBUS (x) (subminiature 9-pin) D-connector has the following pin configuration:


123456789

Shieldnot connected RxD/TxD-P not connected DGnd VP(+5V) not connected RxD/TxD-N not connected

1.4.3 D-connector for connection to RS232

The female RS232 (x) (subminiature 9-pin) D-connector has the following pin configuration:


123456789

not connected TXD RXD not connected 0 Vd DTR CTS RTS Shield


page 12 9.17.012

1.4.4 RS232 interface

1.4.4.1 General description

The RS232/FLOW-BUS interface is an interface between the FLOW-BUS and the RS232 V24 serial (computer) port. The converter, just like the normal RS232 interfaces, offers communication with a baudrate up to 38,4 kBaud. However, this RS232 interface on the converter contains only 1 communication buffer and therefore communication between the FLOW-BUS and e.g. FlowDDE will be slower. Also reading measure and alarminfo (broadcasted parameters) is not possible running e.g. FLOWDDE through this interface.

However from FlowDDE V4.28 it is possible to use this interface as a FLOW-BUS/RS232 converter with

limited communication speed. It mainly should be used for configuration purposes on either the interface itself or for other modules on the bus. Best program tool to be used is DLL_TEST.EXE. By means of this program it is possible to read/write parameter values in a process on a node. Also Hyperterminal of Microsoft Windows can be used, or for some parameters: FlowDDE. Ask your local sales representative for advice.

1.4.4.2 Specifications

Baudrate - 4800 Baud (jumper selectable) 9600 Baud 19200 Baud 38400 Baud

Galvanic isolation - FLOW-BUS driver part has been galvanically isolated from RS232 part and Profibus part by means of optocouplers and DC-DC converter

1.4.4.3 P.C. board jumper setting

RS232 Baudrate selection

pos. 1 pos. 2 4800 open open 9600 closed open 19200 open closed 38400 closed* closed*

* Default setting

For other jumpers consult factory/supplier

po

s.

1p

os.

2p

os.

3p

os.

4p

os.

5


9.17.012 page 13

1.4.5 EMC and cables

All system set-ups described in this manual carry the CE-mark. Therefore they have to comply with the EMC requirements as are valid for this kind of equipment.

However compliance with the EMC requirements is not possible without the use of proper cables and

connector assemblies. For good results Bronkhorst High-Tech B.V. can provide standard cables. Otherwise follow the guidelines as stated below. For cables with 9-pin sub D-connectors:

Fold the shield of the cable back over the cable (the shield must be around the cable).

Wind a copper tape around the shield

Solder a black wire on the tape and

connect to pin 9 of connector

copper tape

shielded cable

e.g. LAPP LiYCY

other wires D-connector housing

metalized

connector

8 mm

20 mm

black wire

(shield)

NOTE: For FLOW-BUS SFTP data (patch) cable connection to RJ45 connectors follow the instructions of the supplier. It is important to use shielded twisted pair cables and shielded RJ45 modular jack connectors. In case the system is electrically connected to another device (e.g. I/O connector to PLC), use shielded cables. Be sure not to disturb the integrity of the shielding of the cable; never use open wire terminals.

1.4.6 Hilscher GmbH Profibus COM-DPS module

This protocol converter module makes uses of a standard product of Hilscher GmbH, Germany, which takes care of the Profibus side of the converter. The Hilscher GmbH Profibus DP-slave module (modelnr: COM-DPS) is a certified Profibus product. More information about this product can be achieved at:

Hilscher Geselschaft fuer Systemautomation mbH

Rheinstrasse 78

D-65795 Hattersheim

Germany

Tel: +49 (0) 6190 – 9907 – 0

Fax: +49 (0) 6190 – 9907 – 50

Hotline and advise: +49 (0) 6190 – 9907 – 99

e-mail: [email protected]

web: http://www.hilscher.com


page 14 9.17.012

1.5 Specifications

1.5.1 Housing

1.5.2 EMC and housing

All electronic circuits and modules have been designed to meet the requirements needed to carry the CE-mark.

However compliance with the (EMC) requirements is not possible without the use of properly screened

housings.

1.5.3 Electrical specifications protocol converter

Supply voltage +15 Vdc or +24 Vdc +/-10% (via FLOW-BUS)

Power consumption (both pc-boards of converter together)

+15 Vdc : 230 mA +24 Vdc : 150 mA

Operating temperature 0 ... + 50°C

Storage temperature - 20 ... + 60°C

Housing dimensions 160 x 80 x 44 mm

1.5.4 Specifications of Hilscher GmbH Profibus COM-DPS module

Processor 16 bit with timer-interrupt- and DMA controller

Memory 32 Kbytes RAM 128 kBytes FLASH 2 Kbytes dual port-memory

Profibus-DP RS-485, isolated, 12 MBaud 10 pol connector

Profibus-DP Input- and outputdata

Max. 368 bytes for all data

Status signals RDY, RUN, ERR, STA

Operating voltage 5V +/-5% / < 500 mA

Dimensions 63.5 x 77.5 x 13.5 mm


9.17.012 page 15

2 INSTALLATION

2.1 General

2.1.1 Receipt of equipment

Check the outside packing for damage incurred during shipment. Should the packing box be damaged, then the local carrier must be notified at once regarding his liability, if so required. At the same time a report should be submitted to

BRONKHORST HIGH-TECH B.V. RUURLO HOLLAND

Remove the envelope containing the packing list; carefully remove the equipment from the packing box. Do not discard spare or replacement parts with the packing material and inspect the contents for damaged or missing parts.

2.1.2 Return shipment

When returning material always describe problem and if possible the work to be done in a covering letter.

Important: Do clearly note, on top of the package the custom clearance number of Bronkhorst High-Tech B.V., namely:

NL801989978B01

2.1.3 Service

If this equipment is not properly serviced, serious personal injury and/or damage to the equipment could result. It is therefore important that servicing is performed by trained and qualified service personnel. Bronkhorst High-Tech B.V. has a trained staff of servicemen available.

2.1.4 Installation

Before switching on power, please check if all external electrical connections with sensor/controllers and FLOW-BUS are properly connected (consult Customers System Description).

If you receive an interface module including sensor/controllers, the total system has been tested in full operation under the nearest process-conditions.

For the electrical connection between FLOW-BUS modules and interface module it is recommended to use the standard Bronkhorst HI-TEC FLOW-BUS cable, which is an eight conductor shielded cable, complete with RJ-45 connectors (SFTP patchcable).

For electrical connections between Profibus modules and the interface module it is recommended to use the appropriate Profibus cables. We advise to consult your Profibus equipment supplier for this.


page 16 9.17.012

2.1.5 Configuration

All interface modules are factory set, for direct use on the FLOW-BUS. For Profibus you have load the settings of the interface module, which is a slave, in your master. You need the special Profibus device description file (HIL_7501.GSD) and select the modules as described in chapter 3.4.2. The interface structure is described in chapter 3.2.

2.1.6 Equipment storage

The equipment should be stored in its original packing in a cupboard warehouse or similar. Care should be taken not to subject the equipment to excessive temperatures or humidity.


9.17.012 page 17

3 Operation

3.1 General information

The Profibus DP-slave/FLOW-BUS interface consists of 2 pc-boards connected to each other. One general FLOW-BUS interface board, designed by Bronkhorst High-Tech B.V. and one general Profibus module (COM-DPS), designed by Hilscher GmbH, Germany. The main purpose of this protocol converter is to make PROPAR (PROcess PARameter) variables of the FLOW-BUS nodes available on a Profibus network. These variables are used to configure, readout and control the instruments. The converter continuously acquires the PROPAR variables of a set of given channels and puts these in the Dual Port Memory of the COM-DPS module. If requested by a Profibus master, the COM-DPS module sends this data from the DPM to the Profibus master. The COM-DPS puts data received from a Profibus master in the DPM. The protocol converter sends the data from the DPM to the FLOW-BUS nodes.

3.2 Hardware installation

• Connect FLOW-BUS to the RJ-45 connector. • Connect Profibus to the Profibus connector. • Connect a PC to the RS232 connector (only needed for configuration that will be performed

already at Bronkhorst High-Tech B.V.).

Figure 1 Location of the connectors, switch and LEDS

FLOW-BUS

Configuration RS232

Profibus-DP

FLOW-BUS statusProfibus status

Gre

en L

ED

1

Red L

ED

1

Gre

en L

ED

3

Yello

w L

ED

1

Gre

en L

ED

2

Yello

w L

ED

2

Red L

ED

2

Mic

ro-s

witch


page 18 9.17.012

3.3 FLOW-BUS configuration

3.3.1 Installation on the FLOW-BUS

At power up press the switch and release it when green LED 1 is blinking and red LED1 is off. The PRODPS module now installs itself on FLOW-BUS. When green LED 1 is on continuously, the installation has been completed.

NOTE 1: Normally installation on the FLOW-BUS has to be performed only one time. Mostly this will be done at Bronkhorst High-Tech B.V. when your module has been built and tested. The address on the bus for this module will be stored when the module powers-off. At future power-on situations, it will be part of the FLOW-BUS on the same address each time. However, there can be situations you have to install your module on the bus again. For example: 1) When you want to rebuild your FLOW-BUS system. 2) When you want to add this module to another FLOW-BUS system.

3) When, at the check at start-up, the module finds out that its address to be on the FLOW-BUS is occupied already by another module. You will be notified by the light-pattern of the LED’s that you have to re-install the module on the bus. In that case you may press the switch shortly for a few seconds until the green LED is blinking fast and than release it. The interface will search for a free address on the FLOW-BUS now.

3.3.2 Switch

Besides the command ‘install node on FLOW-BUS’ several other commands can be given to the PRODPS module using the switch. The command depends on the time the switch was pressed and if the switch was pressed at power up or during normal operation. The following tables show the commands that can be given, the time that the switch should be pressed and the pattern that appears on green LED 1 and red LED 1.

LED pattern Time switch Command

Red LED 1 Green LED 1 Pressed

Off off 0 - 4 s None

Off blinking fast 1 - 4 s Automatic installation on FLOW-BUS. This command can only be given during normal operation if the node address is occupied.

On off 4 - 8 s Reset the converter.

Off on 8 – 12 s Reset the scan process

On on 12 – 16 s Trigger new scan for nodes connected to FLOW-BUS This option only works in configuration A or D (see chapter 4: configuration)

Table 1 Commands that can be given during normal operation

LED pattern Time switch Command

Red LED 1 Green LED 1 Pressed

Off Off 0 - 4 s None

Blinking fast Off 4 - 8 s Restore the FRAM parameters from the backup copy.

Off Blinking fast 8 - 12 s Automatic installation on FLOW-BUS.

Blinking fast Blinking fast 12 - 16 s Put the converter in remote installation mode.

Table 2 Commands that can be given at power up


9.17.012 page 19

3.3.3 Error/status codes on LED’s

The PRODPS module uses green LED 1 and red LED 1 to display some status and error codes. The following table shows these status and error codes.

Green LED 1 Red LED 1 Status / error code

Off Off Power-off or program not running

On Don’t care Normal running mode

Blinking slow Don’t care FLOW-BUS installation mode, instrument can be installed to FLOW-BUS.

Don’t care Blinking slow Node address occupied. The PRODPS module has to be reinstalled.

Don’t care Blinking fast Error during Profibus communication or error while opening FLOW-BUS communication.

Don’t care On Profibus hardware defect or missing.

Blinking green-red turn by turn

Blinking green-red turn by turn

Wink mode. Using a command send via FLOW-BUS, the PRODPS can wink with the LED’s to indicate its position in a system.

Table 3 Error and status codes


page 20 9.17.012

3.4 Profibus configuration

3.4.1 Profibus address

The Profibus address can be changed by writing PROPAR parameter 10 in process 125, see 4.2.3.4. This should be done in init mode via FLOW-BUS. Default Profibus station address from factory is 2. The utility program FlowFix can be used to change the station address of the converter. This has been described in the short-form start-up.

3.4.2 Profibus master

Start the configuration tool for your Profibus network. Add the PRODPS converter to your network configuration after copying the HIL_7501.GSD into your master configuration program. Insert COM_DPS as a slave into your system. Next configure the COM_DPS (PRODPS) module in the configuration program. If the PRODPS module is configured to use one of the fixed configurations, the PRODPS has 8 modules. These modules are shown in the following table.

Module Length Byte/Words Input/Output

1 16 Words Input

2 16 Words Input

3 16 Words Input

4 16 Words Input

5 16 Words Input

6 16 Words Input

7 16 Words Input

8 16 Words Output

Table 4 Profibus modules when using the fixed configuration

Add these modules in the given order to the configuration of the PRODPS module. Refer to the manual of your Profibus configuration program how to do this.

If the PRODPS is configured to use the flexible configuration, the number of modules and the length of the modules depend on how the PRODPS module has been configured.

Note that the PRODPS module default uses modules without consistency.

NOTE:

Profibus settings for this (slave) module are already performed by Bronkhorst High-Tech B.V.

Only settings for master are to be performed by the user.

For more information about needed modules for different configurations of this Profibus slave, see appendices 2, 3 and 4.


9.17.012 page 21

3.4.3 LED’s related to Profibus

The following table shows the LED’s related to the Profibus interface.

LED State Description

On Communication running.

Flashing cyclic Ready for communication, no communication with the master.

Green LED 2

Flashing non cyclic / off Not ready for communication.

On Error on communication line. Red LED 2

Off No error on communication line.

On Error on communication line Yellow LED 1

Off No error on communication line

On Profibus hardware has power Green LED 3

Off Profibus hardware has no power / is not present.

On Profibus hardware is ready

Flashing non cyclic Profibus hardware / system error

Yellow LED 2

Off Profibus hardware error

Table 5 LED's related to Profibus


page 22 9.17.012

3.5 Instrument parameter information (fixed configuration)

For each instrument the parameter “setpoint” can be read and written (if instrument is not a controller this parameter will not be used). For each instrument the parameters “measure”, “serial number”, “alarm info” and “status” are read-only.

NOTE: For different configurations of the converter, available parameters and their properties for

Profibus-DP could be different also.

Parameter values will be send with MSB first. Several controllers (also PC’s) expect values with LSB-

first. In that case the sequence of bytes has to be switched by the software driving the master.

3.5.1 Measure

This parameter consists of the measured value of the instrument (flow, pressure or other) and is represented as a percentual value in a range between 0 and 65535, where 0% = 0 and 100% = 32000.

3.5.2 Setpoint

This parameter is the wanted flow, pressure (or other) and has the same range as “measure”.

3.5.3 Serial number

This parameter consists of a 10-byte string with instrument serial number for identification.

3.5.4 Alarm info

This parameter contains 8 bits with information about some (alarm) events in the instrument.

Bit Meaning

0 0 – no error, 1 – Error message in alarm error status register

1 0 – no error, 1 – Warning message in alarm warning status register

2 0 – no error, 1 – Minimum alarm (sensor signal < minimum limit)

3 0 – no error, 1 – Maximum alarm (sensor signal > maximum limit)

4 0 – no error, 1 – Batch counter has reached its limit

5 0 – no error, 1 – Response alarm message (setpoint-measure too much difference) (bit 2 or bit 3 indicate if difference is positive or negative)

6 0 – no error, 1 – Master/slave alarm: master output signal not received or slave factor out of limits (> 100%)

7 0 – no error, 1 – Hardware alarm: check hardware

3.5.5 Status

This parameter is a special byte for monitoring communication between converter and instruments (via FLOW-BUS). It contains 8 bits with information about certain (alarm) events. This parameter is unlike the other parameters not a PROPAR parameter and can not be read via FLOW-BUS but only via Profibus.

Bit Meaning

0 0 - no error in communication with channel, 1 - error in communication

1 0 - no PROPAR process error, 1 - a PROPAR process error has occurred

2 0 - no PROPAR parameter error, 1 - a PROPAR parameter error has occurred

3 0 - no PROPAR type error, 1 - a PROPAR type error has occurred

4 0 - no PROPAR value error, 1 - a PROPAR value error has occurred

5 0 - no error, 1 - a PROPAR process claim or command error has occurred

6 Reserved

7 Reserved

See also 4.2.2. Flexible configuration for location of parameter values in memory


9.17.012 page 23

3.5.6 Fluid number

Fluid number is a pointer to the set of calibration parameters. For each fluid (gas or liquid) several parameters get values in order to store the calibration for a specific fluid. This increases accuracy. Fluid number is an unsigned char parameter (ucFluidnr) in a range of 0...7, where 0 = fluid1 and 7=fluid8. Up to 8 fluids can be stored in one instrument. Default value = 0 (fluid 1).

3.5.7 Control mode

Control mode is used to select the behaviour of the controller on the instrument. Valve could be opened fully (for purge) or closed complete (e.g. for safety). Setpoint could be obtained via the bus or via the analog input (0..5V/0..10V/0..20mA/4..20mA). Several combinations of master/slave control ar possible. Also several special modes for the instrument are available: test/calibration/tuning. An overview of the modes is given below:

Value Description

0 setpoint = FLOW-BUS setpoint (*default)

1 setpoint = analog input

2 setpoint = master output(FLOW-BUS) * slave factor(FLOW-BUS)

3 close valve

4 setpoint idle (no reaction on changes in sensor signal)

5 test mode enable (select subject with other parameter; BHT-only)

6 tuning mode enable (select subject with other parameter; BHT-only)

7 setpoint = 100%

8 purge valve (fully open)

9 calibration mode enable (select subject with other parameter; BHT-only)

10 setpoint = master output(analog in) * slave factor(FLOW-BUS)

11 setpoint = keyboard OR FLOW-BUS setpoint

12 setpoint = 0%

13 setpoint = master output(FLOW-BUS) * slave factor(analog in)

3.5.8 Counter value

Actual counter value in units selected at Counter unit. Value is single float in IEEE-notation.

3.5.9 Counter mode

Value Description

0 off

1 counting upwards continuously

2 counting up to limit (batch counter)

Default value = 0.

3.5.10 Counter setpoint mode

Setpoint change enable during counter limit/batch situation (until reset). Unsigned char. Default = 0.

Value Description

0 no setpoint change at batch limit allowed

1 setpoint change at batch limit allowed


page 24 9.17.012

3.5.11 Counter setpoint

New/safe setpoint at counter limit/batch situation (until reset) (normally = 0%). See measure for range. Normally this value is set to 0%.

3.5.12 Counter limit

Counter limit/batch. in units selected at Counter unit. Value is single float in IEEE-notation. Default setting is 1000000 ln.

3.5.13 Sensor type

Unsigned char used to select proper set of units for certain sensor, together with Counter unit. Default settings is 3.

Value Description

0 pressure ( no counting allowed)

1 liquid volume

2 liquid/gas mass

3 gas volume

4 other sensor type (no counting allowed)

3.5.14 Reset

Unsigned char to reset program, counter or alarms. Default value = 0.

Value Description

0 no reset

1 reset counter value (no mode change) or common reset

2 reset alarm

3 restart batch counter

4 reset counter value (counter off)

5 reset module (soft reset)

3.5.15 Counter output mode

Unsigned char to determine counter relais activity mode when limit/batch has been reached. Default setting is 0.

Value Description

0 no relais activity at batch limit

1 relais pulses after reaching batch limit until reset

2 relais activated after reaching batch limit until reset


9.17.012 page 25

3.5.16 Counter unit

Unsigned char used to select proper a unit from for certain sensor type. Default setting is 0: ln (for sensor type 3).

CntrUnit Sensor type

0 1 2 3 4 5 6 7 8 9 10 11 12 13

0 n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a.

1 l mm3 ml cm3 ul m3 n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a.

2 g mg ug kg n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a.

3 ln mm3n mln cm3n uln dm3n m3n uls mm3s mls cm3s ls dm3s m3s

4 and > n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a.

3.5.17 Init/reset (key-parameter)

Init and reset security key command for network/parameter settings. Unsigned char. Make 64 to enable changing of secured parameters. Make 0 again to reset. Default setting is 0.

Note: when an instrument powers-up this value will be reset to 0 always automatically.

3.5.18 Analog input

Analog input signal, normally used for ext. setp. (100% = 32000). Depending on the type of instrument, this value will be in the range of 0..5Vdc/0..10Vdc/0..10mA/4..20mA. Type: short integer.

3.5.19 Wink

Unsigned char in range 0...9 enables master to let the instrument connected to that channel wink for several seconds for tracing the physical location. Type of winking depends on instrument. This will be either with red and green LED turn-by-turn or with special characters on a display. Default setting = 0.


page 26 9.17.012

4 Protocol converter description

4.1 Interface overview

The main purpose of the protocol converter is to make PROPAR variables of the FLOW-BUS nodes available on a Profibus network. The converter continuously acquires the PROPAR variables of a set of given channels and puts these in the DPM of the COM-DPS module. If requested by a Profibus master, the COM-DPS module sends this data from the DPM to the Profibus master. The COM-DPS puts data received from a Profibus master in the DPM. The protocol converter sends the data from the DPM to the FLOW-BUS nodes.

The amount of available memory in the DPM is limited to 368 bytes, 244 bytes at maximum for input parameters and 244 bytes at maximum for output parameters (see 3). The COM-DPS supports up to 24 modules, which can have a maximum length of 64 bytes or words. A module is a block of I/O data. Because of these limitations, it is not possible to put all FLOW-BUS parameters and all nodes in the DPM. Furthermore more than one parameter has to be put in a module.

The protocol converter is configured using a configuration tool connected to FLOW-BUS or to the RS232 port. The protocol converter supports three types of configuration:

4.1.1 Configuration

There is a list of channels with a relation to node addresses and process numbers of the connected modules. Depending on the setting of parameter 3 of process 125 of the protocol converter this list will be used as follows:

A. A fixed configuration with network scan. At start-up the node scans the network to determine the node addresses and process numbers. The list with channelnumbers will be filled-in each time the converter starts-up. When FLOW-BUS configuration has been changed, the table will also change. Therefore it is recommended to check the identification of the instrument you expect on a channel first before you start to operate it. This is the default configuration (in EPROM). An example of the channel table:

Channel Node address Process number

1 3 1

2 3 2

3 3 3

4 3 4

5 4 1

6 4 2

7 4 3

8 4 4

9 6 1

10 7 1

11 10 1

12 32 1

13 33 1

14 60 1

NOTE:

When the converter is triggered to perform a new FLOW-BUS scan and e.g. node 6 is removed for

service purposes, node 7 will be connected to channel 9, node 10 to channel 10 etc.

So when a node will only be removed temporarily, do not perform new FLOW-BUS scans.


9.17.012 page 27

B. A fixed configuration without network scan. Each channel is pointing to a predefined node address and process number for instrument operation. This is the normally used and factory set configuration.

Channel Node address Process number

1 3 1

2 4 1

3 5 1

4 6 1

5 7 1

6 8 1

7 9 1

8 10 1

9 11 1

10 12 1

11 13 1

12 14 1

13 15 1

14 16 1

C. A flexible configuration, per module two lists are given. The first list contains a set of process and parameter numbers. The second list contains a list of indices in a global channel list. The protocol converter acquires the parameters given in the first list for all channels in the second list. This configuration is for special use only.

D. A fixed configuration with two modules per channel. One module contains all input parameters of the channel, the other all output parameters. Only node addresses and process numbers (channel) can be configured. The maximum number of channels is 11.

The configuration tool configures the following settings:

• use one of the fixed configurations or the flexible configuration • use no chaining, only parameter chaining or both process and parameter chaining in PROPAR

messages • enable or disable the use modify flags to determine if a parameter has changed

All configuration data is stored in the FRAM on the protocol converter. The data in the FRAM is protected with a CRC.

The protocol converter uses the same RS232 protocols as the RS232 host module. If the destination address is 128, the message is not transmitted on the FLOW-BUS network, but it is handled by the protocol converter itself. This can be used by a PC connected to the RS232 port to find out which node address the protocol converter has.


page 28 9.17.012

4.1.2 Fixed configurations

For configurations A and B: To limit the number of parameters and therefore increasing the number of channels a converter can support, only the following PROPAR parameters will be supported:

Name Type Length in bytes

Serial number input (read only) 10

Alarminfo input 1

Status input 1

Measure input 2

Setpoint input 2

Setpoint output (write only) 2

Some parameters are defined twice in this table, once as input and once as output. This is because the COM-DPS only allows modules to be input only or output only. ‘Status’ is not a real parameter read from a channel. It is generated by the protocol converter and gives some status information of the channel.

Per channel 16 bytes input data and 2 bytes output data are needed. The data is distributed over the modules as follows:

• 7 modules of 16 words that contain all inputs of 14 channels. • 1 module of 16 words that contains all outputs of 14 channels.

It is possible to put 14 channels in the DPM. In the next paragraphs the resulting interface will be described.

For configuration D: In configuration D, the following parameters are supported:

Name Type Length in bytes

serial number input (read only) 10

alarminfo input 1

status input 1

measure input 2

counter value input 4

analog input input 2

setpoint output (write only) 2

fluid number output 1

control mode output 1

counter mode output 1

reset output 1

wink output 1

init/reset output 1

counter limit output 4

Per channel, 20 bytes input data and 12 bytes output data are needed. The data is distributed over the modules as follows:

• 1 - 11 modules of 20 bytes that contain all inputs of one channel each. • 1 - 11 modules of 12 bytes that contain all outputs of one channel each.

It is possible to put up to 11 channels in the DPM. The number of actual channels (and modules) depends on the number of nodes found at start-up (or after triggering FLOW-BUS scan by means of the switch again). In the next paragraphs, the resulting interface will be described.


9.17.012 page 29

4.1.3 Flexible configuration

The flexible configuration is based on two lists per module. The first list contains a set of process and parameter numbers. The second list contains indices in a global channel list. The protocol converter acquires the parameters given in the first list for all channels in the second list. So, within a module the same set of parameters is repeated for several channels.

The global channel list contains node addresses and process offsets. This information combined with the process and parameter address from the parameter list gives the complete location of a parameter. The process offset from the channel list is added to the process number from the parameter list.

Per module the length and the type (input or output) are given. Per parameter the following information is given:

• process number • parameter number • type • if the parameter is a string, the maximum length


page 30 9.17.012

4.2 Interface structure

4.2.1 Fixed configurations

4.2.1.1 Modules with input data

The following C structure describes the 16 word modules with input data.

typedef struct

struct

unsigned char ucIdent[10]; unsigned char ucAlarmInfo; unsigned char ucStatus; short iMeasure; short iSetpoint;

InputData[2]; inpmod32;

The following table shows the relation between modules with inputs and channels on the FLOW-BUS network for configurations A and B (note that channel 0 does not identify the FLOW-BUS channel 0, it is the first channel that is being polled by the converter).

Module Length Nodes

1 32 Channel 0 - channel 1







The array InputData gives the input data of the channels in the module.

The following C structure describes the 20 byte modules with input data (configuration D).

typedef struct

unsigned char ucIdent[10]; unsigned char ucAlarmInfo; unsigned char ucStatus; short iMeasure; float fCounterValue; unsigned short uiAnalogInput;

inpmod20;


9.17.012 page 31

The following table shows the relation between modules with inputs and channels on the FLOW-BUS network for configuration D.

Module Length Nodes

1 20 Channel 0

3 20 Channel 1

5 20 Channel 2

7 20 Channel 3

9 20 Channel 4

11 20 Channel 5

13 20 Channel 6

15 20 Channel 7

17 20 Channel 8

19 20 Channel 9

21 20 Channel 10

UcStatus gives the status of the channel. The bits of ucStatus have the following meaning:

Bit Meaning

0 0 - no error in communication with channel, 1 - error in communication

1 0 - no PROPAR process error, 1 - a PROPAR process error has occurred

2 0 - no PROPAR parameter error, 1 - a PROPAR parameter error has occurred

3 0 - no PROPAR type error, 1 - a PROPAR type error has occurred

4 0 - no PROPAR value error, 1 - a PROPAR value error has occurred

5 0 - no error, 1 - a PROPAR process claim or command error has occurred

6 Reserved

7 Reserved

Bit 0 is reset when there is no longer an error in the communication with that channel. Bits 1, 2 and 3 are not reset. Once the corresponding error has occurred once, these bits will remain 1.

4.2.1.2 Modules with output data

The following C structure describes the 32-byte modules with output data (configurations A and B).

typedef struct

short iSetpoint[14]; outpmod32;

In configurations A and B, there is only one module with output data that contains the output data of all channels.

The following C structure describes the 12 byte modules with output data (configuration D).

typedef struct

short iSetpoint; unsigned char ucFluidNumber; unsigned char ucControlMode; unsigned char ucCounterMode; unsigned char ucReset; unsigned char ucWink; unsigned char ucInit; float fCounterLimit;

outpmod12;


page 32 9.17.012

The following table shows the relation between modules with inputs and channels on the FLOW-BUS network for configuration D.

Module Length Nodes

2 12 Channel 0

4 12 Channel 1

6 12 Channel 2

8 12 Channel 3

10 12 Channel 4

12 12 Channel 5

14 12 Channel 6

16 12 Channel 7

18 12 Channel 8

20 12 Channel 9

22 12 Channel 10

4.2.1.3 Channel list

The channels that are acquired are listed in a channel list. This list has the following structure:

Number of channels (N) Node 1 - Node address of first channel Offset 1 - Index on the node of this channel . . Node N - Node address of last channel Offset N - Index on the node of this channel

The channel list is only used if the fixed configuration without network scan is selected (configuration B). The list is written through PROPAR parameter 11 in process 125 (see 4.2.3.4).

4.2.1.4 FLOW-BUS scan

Configuration D consists of a special feature to enable the converter module to map parameters to the master for as many instruments physically connected to the FLOW-BUS, with a maximum of 11 instruments for 1 Profibus-DP slave. The converter module “knows” the amount of instruments connected to the FLOW-BUS by executing a “FLOW-BUS scan”. This will be performed when the switch on the converter is pressed-down and released when both LED’s (red and green) are on. When pressing down the switch, after each 4 seconds the LED’s will have different combinations of on or off. For more details about selecting other functions of the converter, see paragraph 3.3.2. The combination of both LED’s on will appear after pressing-down the switch for 12-16 seconds.

Before this action is performed, the slave has a default table of instruments as follows:

channel node-address (on FLOW-BUS) process (on node-address)

1 3 1

2 4 1

3 5 1

4 6 1

5 7 1

6 8 1

7 9 1

8 10 1

9 11 1

10 12 1

11 13 1


9.17.012 page 33

This “FLOW-BUS scan will start looking for connected instruments from the node-address 1 (default) up to node-address 125 until 11 instruments are found. This could take up to about 1 minute when only a few instruments are connected and the converter needs to check up to node-address 125. Normally it will take a few seconds to find 11 instruments (if there are connected so many).

This start-address can be changed by means of parameter 4 of process 125 (with Bronkhorst High-Tech tooling software). This can be useful when more Profibus-DP slave/FLOW-BUS converters should be connected to one “large” FLOW-BUS system. The first converter will map the first 11 instruments to the Profibus, the next converter will map the next 11 instruments to the Profibus, etc.

When it is possible however, it would be better to split-up all the FLOW-BUS instruments in several “small” systems with not more than 11 nodes. This will improve performance and will not ask for changing parameter 4 of process 125.

It is possible to readout the channel list through parameter 11 of process 125 with Bronkhorst High-Tech tooling software. With DLL_test: select [send][parm string][ask] node: 1, process: 125, parameter: 11 (Hex enabled). Or use Hyperterminal of Microsoft Windows. The response string contains all node-addresses with process offsets (default=0, means process = 1) of all instruments connected to the FLOW-BUS and suitable for Profibus-DP operation.

Note: Only instruments (or likeable) devices connected to the FLOW-BUS can be operated via the Profibus. Not operator modules or PC-interface modules, which are operators themselves.

4.2.2 Flexible configuration

The flexible configuration needs the following lists:

• A list that gives the relation between channel numbers node addresses and channel numbers on the nodes (global channel list).

• A list that gives all information about the modules (module list). • Per module a list with parameters to acquire (parameter list). • Per module a list with channel numbers (module channel list).

These lists are described in the next paragraphs.


page 34 9.17.012

The following figure gives the relation between the lists.

Figure 2 Relation between the lists

The module channel list gives all modules. Coupled to each module are a module parameter list and a module channel list. These lists describe what parameters from which channels are in the module. The protocol converter reads or writes all parameters in the module parameter list for all channels in the module channel list. The actual node address, process number and parameter number of a parameter are determined as follows:

• The module parameter list gives the process number and the parameter number of the parameter (3 in Figure 2).

• The module channel list gives an index in the global channel list (4 in Figure 2). • Using the index read from the module channel list the node address is determined from the global

channel list (1 in Figure 2). The offset from the global channel list is added to the process number.

The lists are built using a configuration program and downloaded to the FRAM of the protocol converter. It is the task of the configuration program to make sure the configuration is valid.

module m

parameter l ists

(per module one)

module channel lists

(per module one)

channel y

channel l ist

module 1

module m

module list

node x, offset x

parmN, proc N

parm2, proc 2

parm1, proc 1

channelMchannel1

node = node x

process = process x + offset x

parameter = parameter x

parm x,

process x


9.17.012 page 35

4.2.2.1 Global channel list

The global channel list (1 in Figure 2) has the following structure (all items are bytes):

Number of channels (N) Node 1 - Node address of first channel Offset 1 - Index on the node of this channel . . Node N - Node address of last channel Offset N - Index on the node of this channel

The index of the channel is added to the process number given in the parameter list. This gives the real process number of a parameter. The global channel list is written through PROPAR parameter 11 in process 125 (see 4.2.3.4).

4.2.2.2 Module list

The module list (2 in Figure 2) gives the number of modules with I/O data, the length of the modules and the type of the modules. The module list has the following structure (all items are bytes):

Number of modules (N) Length module 1 - Length of module 1 Type module 1 - Input or output . . Length module N - Length of module N Type module N - Input or output

The bits in Type have the following meaning:

Bit Meaning

0 0 – module is input, 1 - module is output

1 0 – module consists of bytes, 1 - module consists of words

2 0 – module without consistency, 1 - module with consistency

Length has the following possible values:

Value Length

0 1 Bytes/Words

1 2 Bytes/Words

2 3 Bytes/Words

3 4 Bytes/Words

4 8 Bytes/Words

5 12 Bytes/Words

6 16 Bytes/Words

7 20 Bytes/Words

8 32 Bytes/Words

9 64 Bytes/Words

The module list is written through PROPAR parameter 12 in process 125 (see 4.2.3.4).


page 36 9.17.012

4.2.2.3 Module parameter list

A module parameter list (3 in Figure 2) of a module has the following structure (all items are bytes):

Number of parameters Parameter number 1 - First parameter, includes the parameter type and a flag. Process number 1 - Process number of the parameter.

String length 1 - Expected string length if the parameter is a string. . .

Parameter number N - First parameter, includes the parameter type and a flag. Process number N - Process number of the parameter.

String length N - Expected string length if the parameter is a string.

The parameter byte is encoded as follows:

bit 0 - 4 - parameter number bit 5 - 6 - parameter type, PROPAR encoding bit 7 - extension flag

The process byte is encoded as follows:

bit 0 – 6 - process number bit 7 - init mode is needed to write the parameter

The channel number on the module given in the global channel list is added to the process number given in parameter list. So the process number given in the parameter list is actually the process number the parameter is in for the first channel on the node. If the process number is 0 or greater than or equal to 113, the channel number on the module is not added.

The extension flag is used to define special parameters. Currently only one special parameter is defined. If the extension flag is 1, the parameter type is CHAR and the parameter number is 0, the protocol converter does not request a parameter from the FLOW-BUS network. Instead it inserts the status of the current channel. See 4.2.1.1 for the meaning of the bits in the channel status byte.

The module parameter list is written through PROPAR parameter 13 in process 125 (see 4.2.3.4).

4.2.2.4 Module channel list

A module channel list (4 in Figure 2) of a module has the following structure (all items are bytes):

Number of channels Channel number 1 - Index in the channel list. . . Channel number N - Index in the channel list.

Channels are stored in the module in the same order as in the module channel list. The values given in these lists are indices in the global channel list.

The module channel list is written through PROPAR parameter 14 in process 125 (see 4.2.3.4).


9.17.012 page 37

4.2.2.5 Module memory map

The acquired parameters are placed in a module as follows:

First parameter in the module parameter list for the first channel in the module channel list . . Last parameter in the module parameter list for the first channel in the module channel list . . First parameter in the module parameter list for the last channel in the module channel list . . Last parameter in the module parameter list for the last channel in the module channel list

Depending on the type of the parameter the parameter is aligned on 16 bit boundaries. The following table gives the rules that are used for alignment.

Parameter type Rule

CHAR Parameter is not aligned, except if it is the first parameter of a channel. In this case it is aligned on a 16-bit boundary.

INT Parameter is always aligned on a 16-bit boundary.

LONG/FLOAT Parameter is always aligned on a 16-bit boundary.

STRING Parameter is not aligned, except if it is the first parameter of a channel. In this case it is aligned on a 16-bit boundary.


page 38 9.17.012

4.2.2.6 Example

This paragraph gives an example how to use the different lists. The following table shows the lists used in this example:

List Value Description

Global channel list 2, 3, 0, 4, 1 The global channel list contains two channels: channel 0 on node 3 and channel 1 on node 4.

Module list 2, 2, 6, 3, 1 The module list contains two modules: the first module is an input module with a length of 16 words (32 bytes), the second module is an output module with a length of 2 words (4 bytes).

Module parameter list first module

3, 0x63, 113, 11, 0x20, 1, 0, 0x14, 1, 0

The module parameter list contains three parameters:

• parameter 3, type string in process 113, length 11

• parameter 0, type INT in process 1. The length is zero, because it is only used for string parameters.

• parameter 20, type CHAR in process 1 Note that the channel number from the global channel list is added to the process number in this list if the process number is between 1 and 112.

Module channel list first module

2, 0, 1 The module contains two channels. The first channel has index 0 in the global channel list; the second channel has index 1 in the global channel list.

Module parameter list second module

1, 0x21, 1, 0 The module parameter list contains one parameter: parameter 1, type INT in process 1.

Module channel list second module

2, 0, 1 The module contains two channels. The first channel has index 0 in the global channel list; the second channel has index 1 in the global channel list.

The above configuration leads to following memory map for the first module:

Address (dec) Description

0 Parameter 3 of process 113 on node 3.

11 Fill byte due to alignment of INT / LONG parameters (next parameter) on 16 bit boundaries.



15 Fill byte due to the alignment of channels on a 16-bit boundary.


27 Fill byte due to alignment of INT / LONG parameters (next parameter) on 16 bit boundaries.



The above configuration leads to following memory map for the second module:

Address (dec) Description




9.17.012 page 39

4.2.3 PROPAR parameters

4.2.3.1 Process 0

The parameters in process 0 depend on the node address the request was send to. The following table lists the parameters for the case the request is sent to the real node address of the protocol converter.

Parameter Type R/W Init mode Description

0 CHR R Module ID: DEVICE_PRODPS (24).

0 STR R String with module ID followed by serial number.

0 STR W Wink command. The first character determines the number of seconds.

1 CHR R/W Hard init Primary node address

2 CHR R/W Hard init Secondary node address

3 CHR R/W Next node address

4 CHR R/W Last node address

5 CHR R/W Hard init Arbitration mode

10 CHR R/W Init mode: 0 Stop init mode, do not restart communication. 0x40 Start soft init mode. 0x49 Start hard init mode. 0x52 Stop init mode and restart communication.

15 CHR R/W PROPAR communication time out in 2 ms steps. Do not use this parameter; use parameter 24 and 25 instead.

18 CHR R Number of channels on this node: 0.

19 CHR R/W Global modify flag.

20 CHR R Module function: DEVICE_TYPE_INTERFACE (1).

24 INT R/W PROPAR Tx time-out in msec.

25 INT R/W PROPAR Rx time-out in msec.

26 CHR R/W Number of message buffers for communication with the PC (1).

27 CHR R/W Number of RS232 errors since the last time this variable was read.

The column “Init mode” gives the init mode that is minimally needed to change the parameter. “Soft init” means that the parameter can be changed in hard and soft init mode. “Hard init” means the parameter can only be changed in hard init mode.

4.2.3.2 Process 113

The following table gives all parameters in process 113.


1 STR R Device type (“PRODPS”).

2 STR R/W Soft init Model number

3 STR R/W Hard init Serial number

4 STR R/W Soft init Manufacturing configuration information string ("Converter").

5 STR R Version (“V1.03”)

6 STR R/W User tag.

7 STR R Hardware version (“V1.00”).

10 STR R/W Hard init Service number.

11 STR R/W Hard init Service date.

12 CHR R/W Hard init Identification number (DEVICE_PRODPS - 24).

19 CHR R/W Modify flag.


page 40 9.17.012

4.2.3.3 Process 118

The following table gives all parameters in process 118.


11 CHR W Restore/backup FRAM: 1 Backup FRAM data 2 Restore FRAM data 3 Clear entire FRAM


4.2.3.4 Process 125

The following table gives all parameters in process 125. This process contains the settings of the Profibus interface and the settings for scanning FLOW-BUS.


1 CHR R/W Soft init Chaining mode: 0 - no chaining, 1 - only parameter chaining, 2 - both process and parameter chaining.

2 CHR R/W Soft init 0 - do not use modify flags, 1 – use modify flags

3 CHR R/W Hard init 0 - fixed configuration with network scan, 1 - fixed configuration with channel list from FRAM, 2 - flexible configuration.

4 CHR R/W Soft init Start address of FLOW-BUS scan for configuration A.

First node for configuration D. 1 ≤ address ≤ 126.

10 CHR R/W Soft init Profibus address.

11 STR R/W Hard init Channel list. This is the only list used by both the fixed and the flexible configuration (configurations B and C). The format of the string is identical to format of the channel list given in 4.2.1.3 and 4.2.2.1.

12 STR R/W Hard init Module list. The format of the string is identical to format of the module list given in 4.2.2.2. Only used for configuration C.

13 STR R/W Hard init Parameter lists. The format of the string is described below. Only used for configuration C.

14 STR R/W Hard init Module channel lists. The format is described below. Only used for configuration C.

15 CHR R/W Hard init Consistency fixed configuration: 0 – use modules without consistency in fixed configuration, 1 – use modules with consistency in fixed configuration.


Changes to parameters 1 and 2 are effective immediately after changing these parameters. Changes to the other parameters are effective after restarting the scanning of the FLOW-BUS nodes.

When reading the string parameters 11 - 14, the string length should be zero. In the answer, the protocol converter sets the length to the length of the string containing the list.


9.17.012 page 41

The format of the string with the parameter lists is as follows:

Number of modules (M) Number of parameters (N1)

Parameter number 1 Process number 1

String length 1 . . Parameter number N1

Process number N1

String length N1

. .

Number of parameters (NM)Parameter number 1

Process number 1 String length 1 . . Parameter number NM

Process number N1

String length NM

The maximum length of PROPAR messages (256 bytes) limits the maximum total length of the parameter lists. The format of the string with the module channel lists is as follows:

Number of modules (M) Number of channels (N1)

Channel number 1 . . Channel number N1

. .

Number of channels (NM)Channel number 1 . . Channel number NM

The maximum length of PROPAR messages also limits the maximum total length of the module channel lists.


page 42 9.17.012

4.2.3.5 Example

This following table shows the strings that should be written to parameters 11 – 14 of process 125 to program the protocol converter for the configuration used as an example in 4.2.2.6.

Parameter String Value PROPAR command

11 2, 3, 0, 4, 1 1, 125, 0x6B, 5, 2, 3, 0, 4, 1

12 2, 2, 6, 3, 1 1, 125, 0x6C, 5, 2, 2, 6, 3, 1

13 2, 3, 0x63, 113, 11, 0x20, 1, 0, 0x14, 1, 0, 1, 0x21, 1, 0

1, 125, 0x6D, 15, 2, 3, 0x63, 113, 11, 0x20, 1, 0, 0x14, 1, 0, 1, 0x21, 1, 0

14 2, 2, 0, 1, 2, 0, 1 1, 125, 0x6E, 7, 2, 2, 0, 1, 2, 0, 1

Note that parameter 3 of process 125 should have value 2 to select the flexible configuration.


9.17.012 page 43

5 TROUBLESHOOTING

• No reaction at LEDS Check connection to FLOW-BUS and make sure the power is on in this bus segment

• Green LED is on and red LED is blinking slow FLOW-BUS node address is occupied, re-install

• Green LED is on and red LED is blinking fast Error on either FLOW-BUS or Profibus communication

• No communication with Profibus possible Check if station address of converter is already in use by other module on the Profibus and change this address if necessary

Make sure the Profibus master is correctly programmed with information about the converter (slave)

• It is not possible to read/write any parameter from FLOW-BUS instruments

Make sure the Profibus master has been programmed correctly with instrument parameter structures. These structures are stacked in the memory module blocks and give the exact location of each parameter in the memory of the slave.

• No communication via RS232 Check cable, COM-port and Baudrate

• Bad communication with FLOW-BUS Check power, cables, cable parts and termination

• One or more FLOW-BUS modules have red LEDS blinking fast

Wait for a few minutes, if LEDS are still blinking than try to re-install the converter. If problem still exists, check power, cables, cable parts and termination.

• Profibus problems Check all settings at Profibus side and master settings. Master and slave settings for use of memory modules must be the same. Some masters have problems using “large” memory modules with consistency. Therefore we chose to use modules witout consistency for default.

Check address of interface (slave) on “live-list”

Try to reset the interface and/or restart your master.

Make sure all settings for your slave are downloaded to your master (otherwise it won’t work).

In configuration D a FLOW-BUS scan should be performed one time at very first start-up with complete FLOW-BUS system connected or when permanant changes are made to FLOW-BUS configuration. Only after this scan is ready, per channel 1 input and 1 output module should be added in your master-configurator. Make sure FLOW-BUS scan starts at wanted address (default = node 3). Can be changed with par 4 from process 125 via BHT-tooling program connected to config.-RS232. (Or using Hyperterminal of Microsoft Windows).

Contact Profibus sales representative or service department.

• Other (FLOW-BUS) problems Contact Bronkhorst High-Tech local sales representative or send e-mail describing your

problem to: csd@bronkhorst com

See also tables with LED indication described in 3.3.3.


page 44 9.17.012

APPENDIX 1: System configuration example

PRODPS: PROFIBUS-DP slave/FLOW-BUS converter

Profibus

master

slave

slave

FLOW-BUS

Local operation

possible

Profibus/FLOW-BUS

converter for

operation of up to 14

instruments

slave


9.17.012 page 45

APPENDIX 2: Fixed/standard configuration (A+B)

In this configuration for the slave following modules have to be selected from the HIL_7501.GSD file in the

configuration software of the master:

1. 16 word input module







8. 16 word output module

Slave module can only be configured for all 14 possible available instruments, independent if they are physically connected to the FLOW-BUS.

Following structures describe how input and output parameters of instruments connected to the

FLOW-BUS are mapped in the memory of the master.

For input data area all bytes are stacked in following order:

typedef struct struct bytes:

unsigned char ucIdent[10]; 10 /* serial number */

unsigned char ucAlarmInfo; 1 /* alarm info byte */

unsigned char ucStatus; 1 /* status byte from converter itself */

short iMeasure; 2 /* measured value: 0...32000 = 0...100% */

short iSetpoint; 2 /* setpoint in range 0...32000 = 0...100% */

16 total InputData[2];

inpmod32; (16 word input module without consistency)

Each structure represents 2 channels, so totaly 7 structures are stacked in the memory for input.

For output data area all bytes are stacked in following order:


short iSetpoint; 2 /* setpoint in range 0...32000 = 0...100% */

OutputData[14]; outpmod32; (16 word output module without consistency)

This structure represents 14 channels, so totaly 1 structure is stacked in the memory for output.

Note:

iMeasure and iSetpoint are short integer (2 byte) parameters.

They have a range of 0…32000, where 32000 = 100 %.


page 46 9.17.012

APPENDIX 3: Flexible/extended configuration (C)

In this configuration for the slave following modules have to be selected from the HIL_7501.GSD file in the

configuration software of the master:




4. 64 word output module

Slave module can only be configured for all 7 possible available instruments, independent if they are physically connected to the FLOW-BUS.




Channel 0...3 : typedef struct struct bytes:

unsigned char ucIdent[10]; 10 /* serial number */ unsigned char ucAlarmInfo; 1 /* alarm info byte */ unsigned char ucStatus; 1 /* status byte from converter itself */ short iMeasure; 2 /* measured value: 0...32000 = 0...100% */ short iSetpoint; 2 /* setpoint in range 0...32000 = 0...100% */ unsigned char ucFluidnr; 1 /* selector for gas (fluid) calibration set: 0...7 */

unsigned char ucControlMode; 1 /* control mode for instrument, see 3.5 */ single dCounterVal; 4 /* counter value as IEEE float */ unsigned char ucCounterMode; 1 /* mode for counter, see appendix 5 */ unsigned char ucCounterSetpointMode; 1 /* setpoint mode for batch counter */ short iCounterSetpoint; 2 /* setpoint when batch has been reached */ single dCounterLimit; 4 /* batch for batch counter */ unsigned char ucCounterUnit; 1 /* counting unit for counter */ unsigned char ucSensorType; 1 /* type of sensor connected (needed for units) */ 32 total InputData[4];


Channel 4...5 : typedef struct struct

bytes: unsigned char ucIdent[10]; 10 /* serial number */ unsigned char ucAlarmInfo; 1 unsigned char ucStatus; 1 short iMeasure; 2 short iSetpoint; 2 unsigned char ucFluidnr; 1 unsigned char ucControlMode; 1 single dCounterVal; 4 unsigned char ucCounterMode; 1 unsigned char ucCounterSetpointMode; 1 short iCounterSetpoint; 2 single dCounterLimit; 4 unsigned char ucCounterUnit; 1 unsigned char ucSensorType; 1 32 total InputData[2];



9.17.012 page 47

Channel 6 :

typedef struct struct

bytes: unsigned char ucIdent[10]; 10 /* serial number */ unsigned char ucAlarmInfo; 1 unsigned char ucStatus; 1 short iMeasure; 2 short iSetpoint; 2 unsigned char ucFluidnr; 1 unsigned char ucControlMode; 1 single dCounterVal; 4 unsigned char ucCounterMode; 1 unsigned char ucCounterSetpointMode; 1 short iCounterSetpoint; 2 single dCounterLimit; 4 unsigned char ucCounterUnit; 1 unsigned char ucSensorType; 1 32 total InputData;


For output data area all bytes are stacked in following order:

Channel 0...6 :


short iSetpoint; 2 /* setpoint in range 0...32000 = 0...100% */ unsigned char ucFluidnr; 1 /* selector for gas (fluid) calibration set: 0...7 */ unsigned char ucControlMode; 1 /* control mode for instrument, see 3.5 */ unsigned char ucReset; 1 /* reset for counter or instrument , see 3.5 */ unsigned char ucCounterMode; 1 /* mode for counter, see appendix 5 */ unsigned char ucCounterSetpointMode; 1 /* setpoint mode for batch counter */ unsigned char ucCounterOutputMode; 1 /* relay/TTL output mode for batch counter */ unsigned char ucCounterSetpoint; 2 /* setpoint when batch has been reached */ single dCounterLimit; 4 /* batch for batch counter */

unsigned char ucCounterUnit; 1 /* counting unit for counter */ unsigned char ucInitReset; 1 /* special key parm. for secured parameters,

see below */ 16 total OutputData[7];

outpmod128; (64 word output module without consistency)

For information about the parameters see chapter 3.5.

Note:

iMeasure and iSetpoint are short integer (2 byte) parameters.

They have a range of 0…32000, where 32000 = 100 %.

ucFluidnr is an unsigned char parameter in a range of 0…7, where

0 = fluid number 1 and 7 = fluid number 8.

All output parameters, except for setpoint, fluidnumber and controlmode are secured.

If you want to change such a parameter value you first have to write value 64 to parameter InitReset to force the

instrument in a special mode. To get the instrument back to normal mode write value 0 to parameter InitReset or

power-up the instrument.


page 48 9.17.012

APPENDIX 4: Fixed configuration with variable amount of channels (D)

In this configuration for the slave, for each instrument connected to the FLOW-BUS (max. 11), following modules

have to be selected from the HIL_7501.GSD file in the configuration software of the master:

1. 20 bytes input module

2. 12 bytes output module

Slave module can be configured for as many instruments physically connected to the FLOW-BUS, with a maximum of 11 instruments for 1 Profibus-DP slave. The converter module “knows” the amount of instruments connected to the FLOW-BUS by executing a “FLOW-BUS scan”. This will be performed when the switch on the converter is pressed-down and released when both LED’s (red and green) are on. This “FLOW-BUS scan will be started from node-address 1 (default). This start address for scanning can be changed via Propar parameter 4 from process 125. See 4.2.3.4 for more details. For information about the parameters see chapter 3.5.

Note: When pressing down the switch, after each 4 seconds the LED’s will have different combinations of on or off. For more details about selecting other functions of the converter, see paragraph 3.3.2. The combination of both LED’s on will appear after pressing-down the switch for 12-16 seconds.




Channel 0...11 (depending on FLOW-BUS scan) : struct bytes:

unsigned char ucIdent[10]; 10 /* serial number */ unsigned char ucAlarmInfo; 1 /* alarm info byte */ unsigned char ucStatus; 1 /* status byte from converter itself */ short iMeasure; 2 /* measured value in range 0...32000 = 0...100% */ single dCounterVal; 4 /* counter value as IEEE float */ short iAnalogInput 2 /* analog input in range 0...32000 = 0...100% */ 20 total

(20 byte input module without consistency)

struct

short setpoint ; 2 /* setpoint in range 0...32000 = 0...100% */ unsigned char ucFluidNr; 1 /* selector for gas (fluid) calibration set: 0...7 */ unsigned char ucControlMode; 1 /* control mode for instrument, see 3.5 */ unsigned char ucCounterMode; 1 /* mode for counter, see appendix 5 */ unsigned char ucReset; 1 /* reset for counter or instrument */ unsigned char ucWink; 1 /* seconds instrument should wink with LED’s: 1..9 */ unsigned char ucInitReset; 1 /* special key parm. for secured parameters, see below */ single dCounterLimit; 4 /* limit/batch for counter in batch count mode */ 12 total

(12 byte output module without consistency)

Note:

iMeasure and iSetpoint are short integer (2 byte) parameters. They have a range of 0…32000, where

32000 = 100 %. ucFluidnr is an unsigned char parameter in a range of 0…7, where 0 = fluid number 1 and 7 = fluid

number 8.

All output parameters, except for setpoint, fluidnumber, wink, reset and controlmode are secured.

If you want to change such a parameter value you first have to write value 64 to parameter InitReset to force the

instrument in a special mode. To get the instrument back to normal mode write value 0 to parameter InitReset or

power-up the instrument.

For more information about using the counter, see appendix 5.


9.17.012 page 49

APPENDIX 5: Operating a counter via Profibus

Using the counter will take three steps: 1. Preparing the instrument (setting correct values for mode, limit etc.) 2. Monitoring the alarm info byte (gives info which alarm has occurred) 3. Resetting the counter (will re-initialize the counter and set output to normal values again)

All settings needed are secured parameters. These parameters can only be changed if a key-parameter value has been send first to get the instrument in a soft-init mode. It will stay in this mode until a new power-up situation.

• Using a batch counter

The measured signal will be integrated in time and there will be a check on a certain limit set by the user.

Example: You have an instrument with a range of 1 ln/min. Setting the batch to be reached on 1000 ln. Relay/TTL output (presence depends on type of module) should give a pulse when batch has been reached. New setpoint wanted at reaching the limit is 0% (valve should be closed). Reset should be enabled via FLOW-BUS or by means of keyboard/micro-switch.

Send following parameter values:

Parameter Value

init/reset key parameter 64

counter limit 1000.0

counter output mode 1

counter setpoint mode 1

counter new setpoint 0

counter reset enable * 5

counter mode 2

*) Default all reset inputs are enabled, so this command isn’t really necessary Note:Now the counter will be active.

Alarm/counter status can be monitored by means of parameter alarminfo

Resetting the counter will need following command:

Parameter Value

reset 1

To inactivate the counter, put it in counter mode “off”. This will also reset your outputs. This can be done sending command:

Parameter Value

counter mode 0

Note:

For use of batchcounter, it is necessary that the counter setpoint has been enabled. This is not possible in

configuration D and should be performed from factory or by means of Bronkhorst High-Tech tooling software.

- Write value 64 to parameter 10 of process 0 of the node-address of the instrument in question, then

- Write value 1 to parameter 5 of process 104 of the node-address of the instrument in question.

Documents

PROFIBUS DP-slave/ FLOW-BUS interface · 2016-12-05 · PROFIBUS DP-slave/ FLOW-BUS interface Doc. no.: 9.17.012J Date: 25-07-2011 ... RS485-based fieldbus communication system for