Sie sind auf Seite 1von 34

GFW

MODULAR POWER CONTROLLERS

MANUAL FOR CONFIGURATION


AND INSTALLATION IN
PROFIBUS NETWORKS

Software version: 1.2x

code: 80959A - 11-2013 - ENG

This document supplements the following:


- Instructions and warnings manual (COD. 80962x)
- Configuration and programming manual (COD. 80963x)

This manual refers to the software version for the Modbus


RTU/CANopen Fieldbus Interface inserted in the GFW as
PORT 2 serial communication port.

ATTENTION!
This document is the property of GEFRAN and may not be reproduced or transferred to third parties without authorization.

This manual is an integral part of the product


and must always be available to operators.
This manual must always accompany the pro-
duct, including in case of sale to another user.
Installers and/or maintenance personnel are
required to read this manual and to precisely follow
the instructions contained in it and in its attachments.
GEFRAN will not be liable for any damage to persons
and/or property, or to the product itself, caused by
failure to follow the instructions and observe the war-
nings given below.

The Customer is required to maintain trade se-


crets; therefore, this manual and its attachments may
not be tampered with or changed, reproduced, or tran-
sferred to third parties without Gefran’s authorization.

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 1
2 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
CONTENTS

INTRODUCTION..................................................................4
USING GFW-PROFIBUS WITH SIEMENS STEP7..........21
ATTENTION.................................................................4
CONFIGURATION......................................................21
PARAMETERISATION...............................................22
BIBLIOGRAPHIC REFERENCES.......................................4
STANDARD SLAVE DIAGNOSTICS AREA...............23
CHANGING THE NODE ADDRESS..........................23
MAIN TECHNICAL CHARACTERISTICS...........................4
TECHNICAL DATA.......................................................5
“Gefran” SW libraries for SIEMENS S7..............24
PROCESS DATA REFRESH TIMES............................6
INSTALLAtion..........................................................24
USER DATA TYPES...................................................26
INSTALLATION....................................................................7
FUNCTION CALL.......................................................29
ELECTRICAL CONNECTIONS TO PROFIBUS
FUNCTION BLOCK....................................................30
NETWORK...................................................................7
NODE ADDRESS SELECTION VIA
ROTARY SWITCH........................................................9
NODE ADDRESS CONFIGURATION VIA
SOFTWARE.................................................................9
SELECTING GFW CONFIGURATION WITH
DIP-SWITCHES...........................................................9

PROFIBUS DP DATA STRUCTURE.................................10


NODE ADDRESS CHANGE TELEGRAM
(SAP 55).....................................................................10
CONFIGURATION TELEGRAM
(SAP 62).....................................................................10
PARAMETRISATION TELEGRAM
(SAP 61)..................................................................... 11
DIAGNOSTICS DATA REQUEST TELEGRAM
(SAP 60).....................................................................15
DATA EXCHANGE (SAP DEFAULT)..........................16

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 3
introduction
The “GFW” series of temperature control modules with PROFIBUS DP Fieldbus interface provides rapid inte-
gration of a large number of compact control units to control temperature and the heating device (up to 372 zones) on
modern automation systems (PLCs, Supervision Systems, etc.) interconnected by means of communication networks
and protocols defined by the standard.
This manual does not describe the “PROFIBUS DP” Fieldbus, we assume that the user is familiar with it, and that he will
refer to the standard or to the official site managed by P.N.O. (Profibus Network Organization): www.profibus.com for
updates.
We also assume that the user is familiar with the technical characteristics of GFW products. Such characteristics
are described in the user manuals enclosed with the product, or may be downloaded from the GEFRAN S.P.A. internet
site www.gefran.com.
To facilitate the installation and configuration of GFWs in a PROFIBUS DP network, we provide “GEFRAN” libraries
of Function Blocks for SIEMENS STEP7®.

ATTENTION

Use the corresponding GSD /3/ file based on the version of the GFW product purchased:

COMPATIBILITY TABLE OF FW VERSIONS AND GSD FILES


FOR GFW-PROFI MODULES “HIGH PERFORMANCE”
N FW “GFX4-PROFI” GSD “GFWH0D76” LIBRERIE STEP7“GEFRAN” MANUALE“PROFIBUS”

Version Date Version Date Version Date Code Date


1 01.20 1-10-2011 01 29-11-2011 2 1-10-2011 80959 01/12
2 01.22 31-08-2012 02 20-05-2013 2:00 21-06-2013 80959A …

BIBLIOGRAPHIC REFERENCES
/1/ IEC 61158, Digital data communications for measurement and control – Fieldbus for use in industrial control system
/2/ PROFIBUS Specification, Normative Parts of PROFIBUS –FMS, -DP, -PA according to the EN 50170
/3/ PROFIBUS Guideline Vol.1 GSD, Specification for PROFIBUS Device Description and Device Integration
/4/ GFW adv 80962x, GFW INSTRUCTIONS AND WARNINGS
/5/ GFW adv 80963x, GFW CONFIGURATION AND PROGRAMMING MANUAL
/6/ GFW_Modbus_V100, GFW - MODBUS MEMORY MAP V.1.00 and subsequent

MAIN TECHNICAL CHARACTERISTICS

The GFW-PROFI Fieldbus Interface module installs in GFW products to expand their communication by pro-
viding them with the PROFIBUS DP protocol. It is a bridge between the PROFIBUS network and the MODBUS RTU
network in the GFW.

• The module has two communication channels:


- the first channel is a serial port with PROFIBUS DP slave protocol and enables connection to a Profibus
Master.
- the second is the serial port with Modbus RTU protocol and enables connection to the GFW on which the
module is installed.
• Control of one to three temperature control zones with monophase, twophase, or threephase GFW.
• Maximum number of GFW temperature control zones controllable by PROFIBUS Master: 372
(124 nodes x 3 zones).
• RS485 serial port galvanically isolated from power supply.
• Profibus DP slave also working in fault condition of the controlling side.
• Address selection by means of HW or SW.

4 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
TECHNICAL DATA

PROFIBUS Port
Protocol Profibus DP V0 (slave)
Function Connects GFW to a
Profibus DP Master
Baud rate Autosynchronization (9.6 ... 12000 kBit/s)
Connector 9 pin D-Type
Node address HW: 1...99 set with rotary switches on the GFW
SW: 1...124 means of specific software message
I/O dimensions Input/Output: depends on configuration:
min. 39 bytes I/O
max. 71 bytes I/O
Msg. supported Data_Exchange, Slave_Diag, Set_Prm, Chk_Cfg, Get_Cfg, Global_Control, Set-Slave-Add
GSD file GFWH0D76.gsd

Modbus Port
Protocol ModBus RTU (master) RS485 serial
Function Connection to GFW instrument
Baud rate 19200 bps
Connector Not accessible from exterior
Node address 1...99 selectable with rotary switches on the GFW

Diagnostics
LEDS: visible only for installers by removing GFW cover
GREEN Led Operative state of PROFIBUS node
Steady off No communication with PROFIBUS Master
Blink 1,00 sec = state “AUTOMATIC BAUDRATE RESEARCH”
“ “ 0,25 sec = state “WAIT FOR PARAMETRIZATION”
“ “ 0,05 sec = state “WAIT FOR CONFIGURATION”
Steady on State “DATA EXCHANGE”

YELLOW Led State of ASIC


Steady off State “DATA EXCHANGE”
Steady on Other operative states

RED Led Communication errors


Steady off No communication error
Blink 1,00 sec = error “State not possible”
“ “ 0,25 sec = error “DP_State not possible”
“ “ 0,05 sec = error “WD_State not possible”
Steady on Module broken

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 5
PROCESS DATA REFRESH TIMES

The Process Data transferred between GFW-PROFI and the PROFIBUS Master PLC via the PROFIBUS
network are refreshed in the GFW controller via periodic reads/writes by the Modbus subnetwork. Therefore, indepen-
dent of the PROFIBUS network communication speed, the actual refresh of such variables depends on the selected
configuration.

READ CYCLES

n. words GFW monophase GFW twophase GFW Threephase


16 50 msec 50 msec 50 msec
32 100 msec 100 msec 100 msec

WRITE CYCLES

n. words GFW monophase GFW twophase GFW Threephase


16 100 msec 100 msec 100 msec
32 100 msec 100 msec 100 msec

Write cycles enter the date scan cycles in read only when the data has changed; data refresh in read is slo-
wed by an acquisition cycle.

6 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
INSTALLATION

See the /4/ manual, enclosed with the products, for a complete description of installation procedures and gene-
ral electrical connections.

ELECTRICAL CONNECTIONS TO PROFIBUS NETWORK

Connector D sub 9 pins female “PROFIBUS”

Internal GEFRAN use

YELLOW LED
RED LED
GREEN LED

Connector S5 Nr. Pin Name Description Note


D-SUB 9 pins male
1 SHIELD EMC protection Connect the terminal resistan-
2 M24V Output voltage - 24V ces as shown in the figure.

3 RxD/TxD-P Data reception/transmission (B) VP (6)

4 n.c. n.c. 390 �

5 DGND Mass of Vp Data line RxD/TxD-P (3)


6 VP Positive power supply +5V

1 2 3 4 5
7 P24V Output voltage +24V 220 �

8 RxD/TxD-N Data reception/transmission (A) Data line


RxD/TxD-N (8)

6 7 8 9 9 n.c. n.c.
390 �

Cable type: Shielded 1 pair 22AWG conforming to PROFIBUS. DGND (5)

When the GFW is the last node of the PROFIBUS network, you have to connect a 220ohm 1/4W termination
resistors between the two “RxD/TxD-P” and “RxD/TxD-N” signals and two 390ohm 1/4W resistors for polarization of
the line between the “VP” signal with “RxD/TxD-P” and between the “DGND” signal with “RxD/TxD-N”.

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 7
In accordance with standard /2/, to guarantee correct communication between PROFIBUS devices, the
shielded cable must have special characteristics:

PARAMETER TYPE “A” CABLE


Impedance in Ω 135...165
Capacity in pF/m < 60
Loop resistance in Ω/Km < 110
Core diameter in mm > 0,64
Core section in mm 2
> 0,34 (AWG22)

By using cables with these characteristics, you can obtain the following line length:

Baudrate in Kbit/sec 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000
Max Length in metres 1200 1200 1200 1200 1000 400 200 100 100 100

GEFRAN S.p.A. supplies PROFIBUS-approved cables and connection systems as accessories for the GFW.

8 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
NODE ADDRESS SELECTION VIA ROTARY SWITCH
The hexadecimal rotary switches on the GFW indicate the
node address of the PROFIBUS network acquired when the unit is
switched on.

The GFW is factory-set with rotary switches in position “0.”


The customer is required to set the correct position (1-99 only).

WHILE THE ROTARY SWITCHES ARE TURNED, THE GREEN


RUN LED STAYS ON STEADILY. IT RETURNS TO NORMAL
FLASHING WHEN THE NEW VALUE IS ACQUIRED (AFTER
ABOUT 5 SECONDS).

NODE ADDRESS CONFIGURATION VIA SOFTWARE


By means of specific telegram PROFIBUS “SET SLAVE ADDRESS”, you can assign the node address (1...124)
deactivating the rotary-switch on the Profibus network, while it maintains its function for the Modbus subnetwork.
To restore the rotary-switch function, transmit the address of node 125 via telegram, the node address is immediately
re-assigned through the rotary-switch.
Thanks to this characteristic, you can expand the number of temperature control zones with a Profibus network up to a
maximum of 124*3= 372.

Note: Make sure the Profibus Master hardware supports transmission of the above-described message.

Example of software configuration:

1. Rotary-Switch “x10” in position 1 and “x1” in position 0.


Profibus network node is 10.
Modbus network node is 10.
2. Address 2 is transmitted to the GFX4 via software.
Profibus network node is 2.
Modbus network node is 10.
3. Rotary-Switch “x10” in position 4 and “x1” in position 0.
Any change in the rotary-switch has significance only for the Modbus subnetwork
Profibus network node is 2.
Modbus network node is 40.
4. Address 125 is transmitted to the GFX4 via software.
The rotary-switch resumes setting the Profibus and Modbus network node.
Profibus network node is 40.
Modbus network node is 40.

SELECTING GFW CONFIGURATION WITH DIP-SWITCHES


The GFW configuration dip-switch, described in manual /4/, “Description of Dip-Switches” chapter, lets you set the
instrument’s operating mode.
Specifically, when Dip “6” is in ON position it lets you reset the factory settings at “POWER ON” for temperature
controller variables and for PROFIBUS communication parameters.

AFTER YOU HAVE REBOOTED THE INSTRUMENT WITH FACTORY PARAMETERS,


REMEMBER TO RETURN DIP “6” TO OFF POSITION.

DIP “7” MUST BE IN OFF POSITION!

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 9
PROFIBUS-DP DATA STRUCTURE

The data exchange structure managed by the GFW-PROFI instruments is based on the type of GFW device
(monophase. twophase, or threephase) and on the consequent configuration selected.
Therefore, the “Configuration Telegram” (SAP 62) has to contain the exact configuration (number of bytes,
format and consistency) of the data exchanged during the “DATA EXCHANGE”(SAP DEFAULT) operating state.
By means of an area of 7 bytes consistent, always present, called Parametric Data, the Master device on the
PROFIBUS network (PLC or Supervisor) can access any parameter of all the GFW connected to the node. By means
of a second area (min. 32 bytes, max. 64 bytes), called Process Data, you can quickly acquire the value of 16 or 32
variables in read and the same number in write of the instrument Modbus map.
With the “Parameterisation Telegram” (SAP 61), the user can select the variables to be attributed to the Pro-
cess Data based on the application.
When the PROFIBUS Master requests diagnostics from the GFW by means of the “Diagnostics Data Request
Telegram” (SAP 60), a packet of 9 bytes is sent, with 7 bytes of standard information and 2 bytes of GFW diagnostics.

NODE ADDRESS CHANGE TELEGRAM (SAP 55)

Class 2 Profibus Masters can change Slave addresses via the “Set_Slave_Add” function

BYTE DESCRIPTION VALUE (hex)


1 New address n
2 ID number (high byte) 0D
3 ID number (low byte) 76
4 Enable (00)\Disable (01) additional changes 00

CONFIGURATION TELEGRAM (SAP 62)

The PROFIBUS Master sends this to all Slave nodes before entering “DATA EXCHANGE” status; in case of
incorrect configuration, the GFW refuses communication with the Master.

There are six possible configurations:

BYTE DESCRIPTION VALUE (hex)


(16 words I/O GFW monophase)
1 7 bytes consistent B6
2 16 words input/output 74

BYTE DESCRIPTION VALUE (hex)


(32 words I/O GFW monophase)
1 7 bytes consistent B6
2 16 words input/output 74
3 16 words input/output 74

BYTE DESCRIPTION VALUE (hex)


(16words I/O GFW biphase)
1 7 bytes consistent B6
2 16 words input/output 74

BYTE DESCRIPTION VALUE (hex)


(32 words I/O GFW biphase)
1 7 bytes consistent B6
2 16 words input/output 74
3 16 words input/output 74

10 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
BYTE DESCRIPTION VALUE (hex)
(16 words I/O GFW threephase)
1 7 bytes consistent B6
2 16 words input/output 74

BYTE DESCRIPTION VALUE (hex)


(32 words I/O GFW threephase)
1 7 bytes consistent B6
2 16 words input/output 74
3 16 words input/output 74

PARAMETERISATION TELEGRAM (SAP 61)

Before entering “DATA EXCHANGE” status, the PROFIBUS Master uses this protocol to identify itself with the GFW PRO-
FIBUS and specify its operating mode.

The telegram consists of fixed data defined by the PROFIBUS standard (10 bytes) and of data of variable length (minimum
70 bytes, maximum 134 bytes), because each module uses a different number of bytes depending on the number of words to be
transferred for each GFW.
The table indicates parameterisation data for modules with 16 I/O words with “A,” and for modules with 32 I/O words with
“B.”
The telegram is composed by the Hardware Configuration Software of the PROFIBUS Master, which reads the information
contained in the “GSD” file.

BYTE BYTE DESCRIPTION DEFAULT VALUE(hex)


A B
1≈7 1≈7 Conforming to standard EN50170
8 8 Reserved 00
9 9 Reserved 00
10 10 Reserved 00
11 11 Gsd Version 01
12 12 Data Type - -
13 13 Error Behaviour None 00
14 14 Startup Delay (Msb) 3 sec 0B
15 15 Startup Delay (Lsb) B8
16 16 Swap Bytes No 00
17 17 Process Data Input 1 Msb Controller Status_S 05
18 18 Process Data Input 1 Lsb D3
19 19 Process Data Input 2 Msb Control output value 1 04
20 20 Process Data Input 2 Lsb 02
21 21 Process Data Input 3 Msb Active SetPoint value 04
22 22 Process Data Input 3 Lsb 01
23 23 Process Data Input 4 Msb P.V. 04
24 24 Process Data Input 4 Lsb 00
25 25 Process Data Input 5 Msb Analog input value 06
26 26 Process Data Input 5 Lsb 3C
27 27 Process Data Input 6 Msb Analog aux 2 input value 06
28 28 Process Data Input 6 Lsb 5A
29 29 Process Data Input 7 Msb Analog aux 3 input value 06
30 30 Process Data Input 7 Lsb 23
31 31 Process Data Input 8 Msb Analog aux 4 input value 06

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 11
BYTE BYTE DESCRIPTION DEFAULT VALUE(hex)
A B
32 32 Process Data Input 8 LSB 24
33 33 Process Data Input 9 MSB Analog aux 5 input value 06
34 34 Process Data Input 9 LSB 25
35 35 Process Data Input 10 MSB Digital input status 05
36 36 Process Data Input 10 LSB 3D
37 37 Process Data Input 11 MSB Digital output status 06
38 38 Process Data Input 11 LSB 98
39 39 Process Data Input 12 MSB Self/autotuning status 05
40 40 Process Data Input 12 LSB 28
41 41 Process Data Input 13 MSB Ammeter input1 value 1 05
42 42 Process Data Input 13 LSB D4
43 43 Process Data Input 14 MSB Voltmetric input1 f. value 1 05
44 44 Process Data Input 14 LSB 42
45 45 Process Data Input 15 MSB Frequency value 05
46 46 Process Data Input 15 LSB 3B
47 47 Process Data Input 16 MSB Power factor 06
48 48 Process Data Input 16 LSB CC
- 49 Process Data Input 17 MSB Voltage status 06
- 50 Process Data Input 17 LSB BE
- 51 Process Data Input 18 MSB Softstart phase current 1 06
- 52 Process Data Input 18 LSB C5
- 53 Process Data Input 19 MSB Monophase load power 1 06
- 54 Process Data Input 19 LSB CF
- 55 Process Data Input 20 MSB Monophase load imped. 1 06
- 56 Process Data Input 20 LSB ED
- 57 Process Data Input 21 MSB Monophase load voltage 1 06
- 58 Process Data Input 21 LSB EF
- 59 Process Data Input 22 MSB Monophase load current 1 06
- 60 Process Data Input 22 LSB F1
- 61 Process Data Input 23 MSB Load Energy E1 LSW 1 06
- 62 Process Data Input 23 LSB 13
- 63 Process Data Input 24 MSB Load Energy E1 MSW 1 06
- 64 Process Data Input 24 LSB 14
- 65 Process Data Input 25 MSB Load Energy E2 LSW 1 05
- 66 Process Data Input 25 LSB FE
- 67 Process Data Input 26 MSB Load Energy E2 MSW 1 05
- 68 Process Data Input 26 LSB FF
- 69 Process Data Input 27 MSB Dynamic HB Alarm 1 06
- 70 Process Data Input 27 LSB E8
- 71 Process Data Input 28 MSB HB Alarm status 1 06
- 72 Process Data Input 28 LSB 00
- 73 Process Data Input 29 MSB SSR Thermic alarm 06
- 74 Process Data Input 29 LSB 8F
- 75 Process Data Input 30 MSB LOAD Thermic alarm 06

12 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
BYTE BYTE DESCRIPTION DEFAULT VALUE(hex)
A B
- 76 Process Data Input 30 LSB 16
- 77 Process Data Input 31 MSB LINE Thermic alarm 06
- 78 Process Data Input 31 LSB 17
- 79 Process Data Input 32 MSB Derivative Thermic alarm 1 06
- 80 Process Data Input 32 LSB A3
49 81 Process Data Output 1 MSB Controller status_W 05
50 82 Process Data Output 1 LSB 31
51 83 Process Data Output 2 MSB Local SetPoint value 04
52 84 Process Data Output 2 LSB 8A
53 85 Process Data Output 3 MSB SetPoint 1 value 04
54 86 Process Data Output 3 LSB E6
55 87 Process Data Output 4 MSB SetPoint 2 value 04
56 88 Process Data Output 4 LSB E7
57 89 Process Data Output 5 MSB Control output value 1 04
58 90 Process Data Output 5 LSB FC
59 91 Process Data Output 6 MSB Alarm point 1 value 04
60 92 Process Data Output 6 LSB 0C
61 93 Process Data Output 7 MSB Alarm point 2 value 04
62 94 Process Data Output 7 LSB 0D
63 95 Process Data Output 8 MSB Alarm point 3 value 04
64 96 Process Data Output 8 LSB 0E
65 97 Process Data Output 9 MSB Alarm point 4 value 04
66 98 Process Data Output 9 LSB 3A
67 99 Process Data Output 10 MSB Alarm HB input1 value 04
68 100 Process Data Output 10 LSB 37
69 101 Process Data Output 11 MSB No data 05
70 102 Process Data Output 11 LSB CE
71 103 Process Data Output 12 MSB No data 05
72 104 Process Data Output 12 LSB CE
73 105 Process Data Output 13 MSB No data 05
74 106 Process Data Output 13 LSB CE
75 107 Process Data Output 14 MSB No data 05
76 108 Process Data Output 14 LSB CE
77 109 Process Data Output 15 MSB No data 05
78 110 Process Data Output 15 LSB CE
79 111 Process Data Output 16 MSB No data 05
80 112 Process Data Output 16 LSB CE
- 113 Process Data Output 17 MSB SetPoint remote value 04
- 114 Process Data Output 17 LSB FA
- 115 Process Data Output 18 MSB Digital output value 05
- 116 Process Data Output 18 LSB 58
- 117 Process Data Output 19 MSB Analog input1 serial 05
- 118 Process Data Output 19 LSB 5B
- 119 Process Data Output 20 MSB Analog input serial 06

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 13
BYTE BYTE DESCRIPTION DEFAULT VALUE(hex)
A B
- 120 Process Data Output 20 LSB 45
- 121 Process Data Output 21 MSB Analog input2 serial 05
- 122 Process Data Output 21 LSB 5C
- 123 Process Data Output 22 MSB Analog input3 serial 06
- 124 Process Data Output 22 LSB 42
- 125 Process Data Output 23 MSB Analog input4 serial 06
- 126 Process Data Output 23 LSB 43
- 127 Process Data Output 24 MSB Analog input5 serial 06
- 128 Process Data Output 24 LSB 44
- 129 Process Data Output 25 MSB Analog output5 serial 06
- 130 Process Data Output 25 LSB 7F
- 131 Process Data Output 26 MSB Analog output6 serial 06
- 132 Process Data Output 26 LSB 80
- 133 Process Data Output 27 MSB Analog output7 serial 06
- 134 Process Data Output 27 LSB 81
- 135 Process Data Output 28 MSB Analog output8 serial 06
- 136 Process Data Output 28 LSB 82
- 137 Process Data Output 29 MSB No data 05
- 138 Process Data Output 29 LSB CE
- 139 Process Data Output 30 MSB No data 05
- 140 Process Data Output 30 LSB CE
- 141 Process Data Output 31 MSB No data 05
- 142 Process Data Output 31 LSB CE
- 143 Process Data Output 32 MSB No data 05
- 144 Process Data Output 32 LSB CE

The “GSD Version” value is fixed in the GSD file and cannot be changed. The FW uses it to identify the ver-
sion of the GSD file that the PLC application SW uses to configure the board in order to ensure functional compatibility.

“Data Type” indicates how many Process Data variables are used for that Profibus node. It must match the
number read by the FW during initialisation of the Modbus network, otherwise Profibus communication is not activated
(1=16 words, 2=32 words).

“Error Behaviour” defines how the controller must act if Profibus network communication is interrupted

0 = None Operative state does not change (default for compatibility with previous versions)
1 = Switching Off Switches to “SW OFF” (OFF)
2 = Manual Mode Switches to “Manual” (MAN)
3 = Setpoint SP2 Switches to setpoint 2 (SP2) (activates only if parameter “hd.1” = 1)

At “Power-ON,” the GFW controller goes to the operative state (ON/OFF, MAN/AUTO,SP1/
SP2) it was in at the previous “Power-OFF.”
If communication is interrupted (for example, PLC in “STOP” or broken PROFIBUS cable),
the GFW goes to the required operative state as defined by the Error Behaviour parameter.
If communication is restored without switching off the GFX4s, all of them return to the ope-
rative state defined by “Power-ON.”
If the GFW is shut down while in “Error,” it will remain in this state at the next “Power-On” until
communication with the PLC is restored.

14 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
“Startup Delay” is the delay in msec for sending Output Process Data to the temperature controllers after
switching to “DATA EXCHANGE” state. It prevents the delay in refresh of PLC peripheral variables from transferring
incorrect values to the GFX4s.
It can be set from 0msec to 10000msec (default: 3sec).

The “Swap bytes” parameters lets you invert the position of the MSB byte with LSB in the Process Data to
facilitate the interpretation of values from different PLCs (YES=SIEMENS STEP7).

“Process Data Input..” and “Process Data Output.” configure which temperature controller variables you
want to communicate to the PLC with the “Data Exchange Telegram” (SAP DEFAULT).

DIAGNOSTICS DATA REQUEST TELEGRAM (SAP 60)

When the PROFIBUS Master requests diagnostic information from GFW-PROFIBUS, it responds with 6 stan-
dard information bytes and 3 specific bytes.

BYTE DESCRIPTION VALUE (hex)


1≈6 Conforming to standard EN50170 -
7 Length of external diagnosis 3
8 MSB Diagnostic external GFW xx
9 LSB Diagnostic external GFW xx

In which:

xx TEXT DESCRIPTION
00 - No active alarm
01 DEVICE “n” TIMEOUT No Modbus communication with GFW
02 DEVICE “n” UNKNOWN Instrument unknown
04 DEVICE “n” SETTING Dip switch GFW not correct
08 DEVICE “n” WRITE ERROR Written value not correct

Note. : The PLC must manage the specific diagnostics for each zone (Active alarms, broken input, HB, etc.) by reading
Modbus variables “Instrumentation Status 1” via FB “OPGEFLEX” for Parametric Data or by selecting these variables
in Process Data via the initial configuration.

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 15
DATA EXCHANGE (SAP DEFAULT)

After checking the correct configuration and parameterisation of the GFW-PROFIBUS by means of the tele-
grams seen above, the PROFIBUS Master activates the “DATA EXCHANGE” protocol in which it cyclically sends some
output bytes and reads some input bytes to the PROFIBUS Slaves.
The number of I/O bytes depends on the selected configuration: an area of 7 bytes, always present in all configura-
tions, represents “Parametric Data”, while the “Process Data” area varies from a minimum of 32 bytes to a maximum
of 64 bytes.

DATA OUTPUT (from PROFIBUS Master to Slave)

“REQUEST” PROCESS DATA

PARAMETRIC

DATA WORD 1 WORD 2 WORD 3 WORD 4 WORD 29 WORD 30 WORD 31 WORD 32


LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ≈ 64 65 66 67 68 69 70 71

DATA INPUT (from PROFIBUS Slave to Master)

“REQUEST” PROCESS DATA

PARAMETRIC

DATA WORD 1 WORD 2 WORD 3 WORD 4 WORD 29 WORD 30 WORD 31 WORD 32


LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB LSB MSB

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ≈ 64 65 66 67 68 69 70 71

The “Parametric Data” let you read or write any MODBUS variable, either in bit format or in word format, pre-
sent in the GFX4 devices connected to the PROFIBUS node.

PARAMETRIC DATA

BYTE PARAMETER DESCRIPTION


1 TRG TRIGGER BYTE: must be incremented by 1 with each new Request. The Response will
be correct only when value is equal.
2 ADD SLAVE MODBUS address of GFX4 present on PROFIBUS node
3 FC Function code to specify procedure: Bit/Word Read/Write
4 DATA ITEM 1 Depends on FUNCTION CODE
5 DATA ITEM 2 Depends on FUNCTION CODE
6 DATA ITEM 3 Depends on FUNCTION CODE
7 DATA ITEM 4 Depends on FUNCTION CODE

16 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
Reading a bit: Function Code 1 or 2
Request bytes

TRG ADD SLAVE FC ADD MSB ADD LSB NB MSB NB LSB


Trigger Slave 1 or 2 Address of Bit Address of Bit Number of bit Number of bit
Address to read to read to read to read
(always 00) (always 01)
Reply bytes

TRG ADD SLAVE FC NB BIT # #


Reply to Confirm Confirm Number of Bit value: Empty Empty
trigger Slave procedure code bytes read 0 o FF
set address 1 or 2 (always 1)

Reading a word: Function Code 3 or 4


Request bytes

TRG ADD SLAVE FC ADD MSB ADD LSB NW MSB NW LSB


Trigger Slave 3 or 4 Address of word Address of word Number of Number of
Address to read to read word to read word to read
(always 00) (always 01)
Reply bytes

TRG ADD SLAVE FC NB WMSB W LSB #


Reply to Confirm Confirm Number of Msb word lsb word Empty
trigger Slave procedure code bytes read value value
set address (always 2)

Writing a Bit: Function Code 5


Request bytes

TRG ADD SLAVE FC ADD MSB ADD LSB BIT 00


Trigger Slave 5 Address of Bit Address of value of bit (always 00)
Address to read bit to write to write
(00 or FF)
Reply bytes

TRG ADD SLAVE FC ADD MSB ADD LSB BIT 00


Reply to Confirm Confirm Address of Address of value of bit (always 00)
trigger Slave procedure code bit written bit written written
set address (00 or FF)

Writing a word: Function Code 6


Request bytes

TRG ADD SLAVE FC ADD MSB ADD LSB W MSB W LSB


Trigger Slave 6 Address of Address of Address of Address of
Address word to write word to write word to write word to write

Reply bytes

TRG ADD SLAVE FC ADD MSB ADD LSB W MSB 00


Reply to Confirm Confirm Address of Address of msb value of lsb value of
trigger Slave procedure code word written word written word written word written
set address

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 17
In case of error, 80 hex plus the request procedure code will be returned in place of the procedure code.

The error code will be shown in the CODE field.

Reply bytes

TRG ADD SLAVE FC CODE # # #


Reply to Confirm Procedure Error code Empty Empty Empty
trigger Slave code + 80hex
set address

1 = Illegal function 3 = Illegal data value 9 = Illegal number data


2 = Illegal data address 6 = Slave device busy 10 = Read only data

18 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
As described above, “Process Data” represent the MODBUS variables configured via the Parameterisation
Telegram. The GFW occupies 16 or 32 words of the Process Data area depending on the selection made.
The table indicates Process Data with 16 I/O words with “A,” and Process Data with 32 I/O words with “B.”

BYTES BYTES INPUT PROCESS DATA OUTPUT PROCESS DATA


A B
8 8 Process Data Input 1 MSB Process Data Output 1 MSB
9 9 Process Data Input 1 LSB Process Data Output 1 LSB
10 10 Process Data Input 2 MSB Process Data Output 2 MSB
11 11 Process Data Input 2 LSB Process Data Output 2 LSB
12 12 Process Data Input 3 MSB Process Data Output 3 MSB
13 13 Process Data Input 3 LSB Process Data Output 3 LSB
14 14 Process Data Input 4 MSB Process Data Output 4 MSB
15 15 Process Data Input 4 LSB Process Data Output 4 LSB
16 16 Process Data Input 5 MSB Process Data Output 5 MSB
17 17 Process Data Input 5 LSB Process Data Output 5 LSB
18 18 Process Data Input 6 MSB Process Data Output 6 MSB
19 19 Process Data Input 6 LSB Process Data Output 6 LSB
20 20 Process Data Input 7 MSB Process Data Output 7 MSB
21 21 Process Data Input 7 LSB Process Data Output 7 LSB
22 22 Process Data Input 8 MSB Process Data Output 8 MSB
23 23 Process Data Input 8 LSB Process Data Output 8 LSB
24 24 Process Data Input 9 MSB Process Data Output 9 MSB
25 25 Process Data Input 9 LSB Process Data Output 9 LSB
26 26 Process Data Input 10 MSB Process Data Output 10 MSB
27 27 Process Data Input 10 LSB Process Data Output 10 LSB
28 28 Process Data Input 11 MSB Process Data Output 11 MSB
29 29 Process Data Input 11 LSB Process Data Output 11 LSB
30 30 Process Data Input 12 MSB Process Data Output 12 MSB
31 31 Process Data Input 12 LSB Process Data Output 12 LSB
32 32 Process Data Input 13 MSB Process Data Output 13 MSB
33 33 Process Data Input 13 LSB Process Data Output 13 LSB
34 34 Process Data Input 14 MSB Process Data Output 14 MSB
35 35 Process Data Input 14 LSB Process Data Output 14 LSB
36 36 Process Data Input 15 MSB Process Data Output 15 MSB
37 37 Process Data Input 15 LSB Process Data Output 15 LSB
38 38 Process Data Input 16 MSB Process Data Output 16 MSB
39 39 Process Data Input 16 LSB Process Data Output 16 LSB
- 40 Process Data Input 17 MSB Process Data Output 17 MSB
- 41 Process Data Input 17 LSB Process Data Output 17 LSB
- 42 Process Data Input 18 MSB Process Data Output 18 MSB
- 43 Process Data Input 18 LSB Process Data Output 18 LSB
- 44 Process Data Input 19 MSB Process Data Output 19 MSB
- 45 Process Data Input 19 LSB Process Data Output 19 LSB
- 46 Process Data Input 20 MSB Process Data Output 20 MSB
- 47 Process Data Input 20 LSB Process Data Output 20 LSB
- 48 Process Data Input 21 MSB Process Data Output 21 MSB
- 49 Process Data Input 21 LSB Process Data Output 21 LSB
- 50 Process Data Input 22 MSB Process Data Output 22 MSB

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 19
BYTES BYTES INPUT PROCESS DATA OUTPUT PROCESS DATA
A B
- 51 Process Data Input 22 LSB Process Data Output 22 LSB
- 52 Process Data Input 23 MSB Process Data Output 23 MSB
- 53 Process Data Input 23 LSB Process Data Output 23 LSB
- 54 Process Data Input 24 MSB Process Data Output 24 MSB
- 55 Process Data Input 24 LSB Process Data Output 24 LSB
- 56 Process Data Input 25 MSB Process Data Output 25 MSB
- 57 Process Data Input 25 LSB Process Data Output 25 LSB
- 58 Process Data Input 26 MSB Process Data Output 26 MSB
- 59 Process Data Input 26 LSB Process Data Output 26 LSB
- 60 Process Data Input 27 MSB Process Data Output 27 MSB
- 61 Process Data Input 27 LSB Process Data Output 27 LSB
- 62 Process Data Input 28 MSB Process Data Output 28 MSB
- 63 Process Data Input 28 LSB Process Data Output 28 LSB
- 64 Process Data Input 29 MSB Process Data Output 29 MSB
- 65 Process Data Input 29 LSB Process Data Output 29 LSB
- 66 Process Data Input 30 MSB Process Data Output 30 MSB
- 67 Process Data Input 30 LSB Process Data Output 30 LSB
- 68 Process Data Input 31 MSB Process Data Output 31 MSB
- 69 Process Data Input 31 LSB Process Data Output 31 LSB
- 70 Process Data Input 32 MSB Process Data Output 32 MSB
- 71 Process Data Input 32 LSB Process Data Output 32 LSB

20 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
USING GFW-PROFIBUS WITH SIEMENS STEP7

CONFIGURATION
The “GFWH0D76.GSD” file contains the information needed to manage a GFW Slave PROFIBUS DP node. This
file must be installed in SIEMENS Step7 programming environment in order to insert the GFW in the PROFIBUS network
hardware configuration.

1. Open the hardware configuration for the project


2. Select Station/Close on the menu
3. Select Tools/Install new GSD file
4. In the window that appears, look for the file on the device where it is saved (Floppy or Hard Disk)
5. Press Open.
6. A new device named “GFW HIGH PERFORMANCE” has now been added to the Catalogue
7. Reopen the configuration of the project station
8. Expand the “Profibus DP” folder in the “Catalogue” area, then “Additional devices from field,” then “Control-
ler,” identifying our instrument
9. Drag the icon of the device and drop it on the line of the Profibus bus of the project. A new Profibus slave will
be created.
10. Assign the PROFIBUS node to the new slave. The PROFIBUS node must be consistent with the one set
with the rotary switch on the GFW
11. Based on the number of expansions linked to the same GFW-PROFIBUS node, drag the “GFW Module”
with the required number of words to the “Connector Position” area of our device. The peripheral memory
areas use by our device for process data exchange will automatically be assigned.

“CATALOG” AREA

GFW
HIGH PERFORMANCE

“CONNECTOR
POSITION” AREA

GFW Module

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 21
UTILIZZO GFW-PROFIBUS CON SIEMENS STEP7
The first 7 I/O bytes (ID 182), called “Consistency” in the figure, correspond to addresses PEB 256 ... PEB 262;
PAB 256 ... PAB 262 and represent “Parametric Data.”
The next 64 bytes (ID 127) (PEB263..PEB326 e PAB263..PAB326) represent “Process Data.”

Always check that the Hardware configurator gives contiguous memory addresses for all the rack zo-
nes. In case of “holes” or jumps, manually assign the first address to a zone known to be free.
The E addresses (inputs) must be the same as the A addresses (output).
During the GFW hardware configuration it is useful to reserve the memory area for a maximum of 16
usable zones for each rack.

PARAMETERISATION

UTILIZZO GFW-PROFIBUS CON SIEMENS STEP7


On the hardware configuration page, by selecting the properties of the DP slave, you can also select the Pro-
cess Data preferred by the user.

As seen above, you can attribute a variable of the Modbus Memory Map on the pull-down menu to each of the
16 or 32 I/O words available for each GFW device.
These data are cyclically shown in the assigned data block by using FC3 CFG-GFX4-HP (see specific chap-
ter).

INPUT AREA data are cyclically read by the GFWs, while OUTPUT AREA data are written in the
controller only if a data item is changed.

22 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
STANDARD SLAVE DIAGNOSTICS AREA

UTILIZZO GFW-PROFIBUS CON SIEMENS STEP7


Click on properties of the slave to identify the standard slave diagnostics area.

This area is legible with SFC 13 “DPNRM_DG”. See the Siemens Step 7 manual for operating instructions.
In addition to standard bytes, the slave provides extended diagnostic data with a word.

CHANGING THE NODE ADDRESS

UTILIZZO GFW-PROFIBUS CON SIEMENS STEP7


On the home page of the “SIMATIC Manager,” select the “PROFIBUS” function on the “PLC” menu to access
the “Assign Profibus address” command, with which you can change the address of the Profibus Slave.
Attention: check that the hardware installed for communication with the Profibus Master supports this function.
If you are not certain of your network configuration, connect one Slave at a time and change their address.

Current PROFIBUS address:


You can select one of the existing nodes by means of this field.
New PROFIBUS address:
The new address is assigned to the above-selected node by means of this field.

Address “125” resets the assignment of the node address via reading of the rotary switch.

Connect the cable of the work station (PC or PG) directly to the GFW to which the address will be
assigned, without connection to the PROFIBUS Master PLC.

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 23
“Gefran” SW LIBRARIES FOR SIEMENS S7

INSTALLATION

GEFRAN S.p.A. supplies a series of library files to facilitate the installation and management of process data for
GFW products in SIEMENS STEP7 environment.
These libraries are contained in a compressed file (Gefran.zip) on the CD enclosed with the products or downlo-
adable from www.gefran.it.
After launching “SIMATIC Manager,” select the “Retrieve” command on the “File” pull-down menu and open the
“Gefran.zip” file from the folder to which it was copied.

Then select the destination folder in “..STEP7/S7Proj.”


When file extraction is done, select “Open project” on the “File” pull-down menu and open the “Libraries” folder
to see the “GEFRAN” library, with contains the historical file of libraries for GEFLEX devices and for GFWs.

24 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
The version that manages GFW is “GFW_v0_1”.
It contains Function Blocks, Data Blocks, and Functions:

OBJECT NAME DESCRIPTION


FB1 OPGeflex Function block to manage GFW parameters
FB15 GFXRcp Function block to manage GFW parameter recipes
FC3 CFG-GFX4-HP Management of GFW process data area
UDT9 GFX_RCP Data type for recipe management with FB15
UDT10 GFX4-HP_16x1 Data type for managing GFW process data 16words
UDT11 GFX4-HP_32x1 Data type for managing GFW process data 32words
DB109 RCPadd Example of data block for managing recipes from UDT9

Insert OB82 (even if empty) in the project to manage peripheral diagnostics.


The GFW uses standard Profibus slave diagnostics; without OB82, if diagnostics messages are pre-
sent, the CPU will stop.

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 25
USER DATA TYPES

UDT9 “GFXRcp”

The resulting “DBx” data block contains the recipe name and the list of MODBUS addresses corresponding to the GFW
variables to be saved:

26 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
80959A_MSW_GFW-PROFIBUS_11-2013_ENG 27
UDT10, UDT11 “GFX4-HP_nnxn”

Use the “User Data Type” corresponding to the selection made in HW configuration; the “DBx” data block will
have a different composition based on the selection.
For example, the following table shows block corresponding to UDT10 “GFX4-HP_32x1”:

28 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
80959A_MSW_GFW-PROFIBUS_11-2013_ENG 29
FUNCTION CALL
FC3 “CFG-GFW-HP”

This function provides the entire area of process data exchange between PLC and GFW in the data block crea-
ted with UDT3 described above.

FC3 is called in OB1 without conditions so that each scan will refresh the data.

Four input parameters are required:


1. FirstByte (INT) first memory address assigned to GFW rack in HW configuration.
2. GFX4Nr (INT) always 1
3. WordNr (INT) number of process words configured for each node (16 or 32)
4. DBNr (INT) number of data blocks created with UDT to contain entire data exchange area

First Byte

30 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
FUNCTION BLOCKS

All Function Blocks require a freely assignable instance DB. They must be called only on request and kept
active until the operation is done.
Typically, you set a Bit that enables the branch (EN) and is reset with the rising edge of the “Done” bit.

FB1 “OPGeflex”

This controls fundamental Parametric Data operations for configuring GFWs.

The block requires 5 input parameters and replies with 4 output parameters.

Input parameters:

DBNr (INT) data block number assigned to the rack containing the GFW to be interrogated or controlled.
1.
SlaveNr (INT): MODBUS address of the slave to be operated.
2.
OPCode (INT): operation code that tells the function if we want to read or write a word or a bit.
3.
The operation codes are:
• 1 = Bit read Operation Code
• 3 = Word read Operation Code
• 5 = Bit write Operation Code
• 6 = Word write Operation Code
Address (INT): address of word or bit to be read or written (see manual /6/ for identification of MODBUS
4.
addresses of words and bits).
INValue (INT): value to be written in the selected word or bit.
5.
Obviously, when writing a bit, only values 1 and 0 are allowed. This parameter is ignored in read operations.

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 31
Output parameters:

Done (BOOL): value is 1 when read operation is done


1.
OUTValue (INT): value read in specified word or bit.
2.
In write operations, 1 is written if action finishes correctly or 0 if it finishes with an error.
Error (BOOL): value is 1 when operation finishes with an error.
3.
ErrCode (INT): error code:
4.
1 Illegal function
2 Illegal data address
3 Illegal data value
6 Slave device busy
9 Illegal number data
10 Read only data
20 Timeout Communication
21 Input value error

FB15 “GFX_RCP”

Stores a set of parameters from a GFX4 in a DB or sends a set of parameters contained in a DB to a GFW.

32 80959A_MSW_GFW-PROFIBUS_11-2013_ENG
Input parameters:

DB_GFX (INT) indicates the number (only the number in figures or an INT variable containing its value) of DB
1.
assigned to rack of GFWs to be operated.
DBIST (BLOCK_DB): indicates the name (use symbolic name of DB or in full the indication “DBxx” ) of instance
2.
DB of FB1 “OPGeflex” assigned to this rack of GFWs.
GFXNr (INT): address of GFW to be operated.
3.
RCP_DB (INT): number of DB in which you want to write or from which you want to read the data set.
4.
Funct (BOOL): specifies the type of operation to be done:
5.
False = Store (saves GFW parameters in DB)
True = Load (downloads parameters saved in DB into GFW)
ParamNr (INT): number of parameters to be saved/read.
6.
ParamListDB (INT): number of DB in which modbus address of parameters to be read/written is specified
7.
on each line.

Output parameters:

Done (BOOL): value is 1 when operation is done.


1.
Error (BOOL): value is 1 when an error occurs during write operation.
2.
ErrCode (INT): error code is given in case of error
3.

1Illegal function
2 Illegal data address
3 Illegal data value
6 Slave device busy
9 Illegal number data
10 Read only data
20 Timeout Communication
21 Input value error

4. ErrorParamNr (INT): in case of error, the ordinal number of the DB is given, with a list of addresses of the
parameter that caused the error.

80959A_MSW_GFW-PROFIBUS_11-2013_ENG 33
GEFRAN spa
via Sebina, 74
25050 Provaglio d’Iseo (BS) Italy
Tel. +39 0309888.1
Fax +39 0309839063
info@gefran.com
http://www.gefran.com

Das könnte Ihnen auch gefallen