GFW MANUAL FOR CONFIGURATION AND INSTALLATION IN PROFIBUS …
Transcript of GFW MANUAL FOR CONFIGURATION AND INSTALLATION IN PROFIBUS …
180959B_MSW_GFW-PROFIBUS_07-2019_ENG
ATTENTION!
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.
MANUAL FOR CONFIGURATIONAND INSTALLATION IN PROFIBUS NETWORKS
Software version: 1.3x
code: 80959B - 07-2019 - ENG
GFWMODULAR POWER CONTROLLERS
Thi
s do
cum
ent i
s th
e pr
oper
ty o
f GE
FR
AN
and
may
not
be
repr
oduc
ed o
r tr
ansf
erre
d to
third
par
ties
with
out a
utho
rizat
ion.
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.
2 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
380959B_MSW_GFW-PROFIBUS_07-2019_ENG
CONTENTS
CONTENTS ���������������������������������������������������������������������������������3
INTRODUCTION �������������������������������������������������������������������������4
ATTENTION ............................................................................4
BIBLIOGRAPHIC REFERENCES ����������������������������������������������4
MAIN TECHNICAL CHARACTERISTICS ����������������������������������4
TECHNICAL DATA ..................................................................5
PROCESS DATA REFRESH TIMES .....................................6
INSTALLATION ���������������������������������������������������������������������������7
ELECTRICAL CONNECTIONS TO PROFIBUS NETWORK ..7
NODE ADDRESS SELECTION VIA ROTARY SWITCH .........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
PARAMETERISATION TELEGRAM (SAP 61) ....................11
DIAGNOSTICS DATA REQUEST TELEGRAM (SAP 60) ....15
DATA EXCHANGE (SAP DEFAULT) ...................................16
USE OF THE GFW-PROFIBUS WITH SIEMENS STEP7 – TIA PORTAL ������������������������������������������������������������������������������������21
CONFIGURATION ................................................................21
PARAMETRIZATION ............................................................24
STANDARD SLAVE DIAGNOSTICS AREA ..........................25
FUNCTION BLOCKS ............................................................26
4 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
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® and - TIA Portal.
ATTENTION
Use the corresponding GSD /3/ file based on the version of the GFW product purchased:
COMPATIBILITY TABLE OF FW VERSIONS AND GSD FILESFOR 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/122 01.22 31-08-2012 02 20-05-2013 2:00 21-06-2013 80959A …3 01.30 07/05/2017 02 20/05/2013 02 21/06/2013 80959B 10/2018
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.
580959B_MSW_GFW-PROFIBUS_07-2019_ENG
TECHNICAL DATA
PROFIBUS PortProtocol Profibus DP V0 (slave)
Function Connects GFW to aProfibus 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 GFWSW: 1...124 means of specific software message
I/O dimensions Input/Output: depends on configuration:min. 39 bytes I/Omax. 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 PortProtocol 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
GREEN LedSteady off
LEDS: visible only for installers by removing GFW cover Operative state of PROFIBUS nodeNo 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
6 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
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 CYCLESN. words GFW Monophase GFW twophase GFW Threephase
16 50 msec 50 msec 50 msec32 100 msec 100 msec 100 msec
WRITE CYCLESN. words GFW Monophase GFW twophase GFW Threephase
16 100 msec 100 msec 100 msec32 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.
PROCESS DATA REFRESH TIMES
780959B_MSW_GFW-PROFIBUS_07-2019_ENG
Connector D sub 9 pins female “PROFIBUS”
Internal GEFRAN use
YELLOW LEDRED LEDGREEN LED
Connector S5D-SUB 9 pins male
Cable type: Shielded 1 pair 22AWG conforming to PROFIBUS.
Nr. Pin
123456789
Name
SHIELDM24V
RxD/TxD-Pn.c.
DGNDVP
P24VRxD/TxD-N
n.c.
Description
EMC protectionOutput voltage - 24V
Data reception/transmission (B)n.c.
Mass of VpPositive power supply +5V
Output voltage +24VData reception/transmission (A)
n.c.
Note
Connect the terminal resistan-ces as shown in the figure.
390 �
Data line
Data line
390 �
220 �
RxD/TxD-P (3)
RxD/TxD-N (8)
VP (6)
DGND (5)
1 2 3 4 5
6 7 8 9
INSTALLATION
See the /4/ manual, enclosed with the products, for a complete description of installation procedures and gene-ral electrical connections.
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”.
ELECTRICAL CONNECTIONS TO PROFIBUS NETWORK
8 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
In accordance with standard /2/, to guarantee correct communication between PROFIBUS devices, theshielded cable must have special characteristics:
By using cables with these characteristics, you can obtain the following line length:
GEFRAN S.p.A. supplies PROFIBUS-approved cables and connection systems as accessories for the GFW.
PARAMETER TYPE “A” CABLEImpedance in Ω 135...165
Capacity in pF/m < 60
Loop resistance in Ω/Km < 110Core diameter in mm > 0,64
Core section in mm2 > 0,34 (AWG22)
Baudrate in Kbit/sec 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000Max Length in metres 1200 1200 1200 1200 1000 400 200 100 100 100
980959B_MSW_GFW-PROFIBUS_07-2019_ENG
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 SELECTION VIA ROTARY SWITCH
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.
NODE ADDRESS CONFIGURATION VIA SOFTWARE
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!
10 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
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.
Class 2 Profibus Masters can change Slave addresses via the “Set_Slave_Add” function
BYTE DESCRIPTION VALUE (hex)1 New address n2 ID number (high byte) 0D3 ID number (low byte) 76 4 Enable (00)\Disable (01) additional changes 00
NODE ADDRESS CHANGE TELEGRAM (SAP 55)
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(16 words I/O GFW monophase)
VALUE (hex)
1 7 bytes consistent B62 16 words input/output 74
BYTE DESCRIPTION(32 words I/O GFW monophase)
VALUE (hex)
1 7 bytes consistent B62 16 words input/output 743 16 words input/output 74
BYTE DESCRIPTION
(16words I/O GFW biphase)VALUE (hex)
1 7 bytes consistent B62 16 words input/output 74
BYTE DESCRIPTION
(32 words I/O GFW biphase)VALUE (hex)
1 7 bytes consistent B62 16 words input/output 743 16 words input/output 74
CONFIGURATION TELEGRAM (SAP 62)
1180959B_MSW_GFW-PROFIBUS_07-2019_ENG
BYTE DESCRIPTION(16 words I/O GFW threephase)
VALUE (hex)
1 7 bytes consistent B62 16 words input/output 74
BYTE DESCRIPTION(32 words I/O GFW threephase)
VALUE (hex)
1 7 bytes consistent B62 16 words input/output 743 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 009 9 Reserved 00
10 10 Reserved 0011 11 Gsd Version 0112 12 Data Type - -13 13 Error Behaviour None 0014 14 Startup Delay (Msb) 3 sec 0B15 15 Startup Delay (Lsb) B816 16 Swap Bytes No 0017 17 Process Data Input 1 Msb Controller Status_S 0518 18 Process Data Input 1 Lsb D319 19 Process Data Input 2 Msb Control output value 1 0420 20 Process Data Input 2 Lsb 0221 21 Process Data Input 3 Msb Active SetPoint value 0422 22 Process Data Input 3 Lsb 0123 23 Process Data Input 4 Msb P.V. 0424 24 Process Data Input 4 Lsb 0025 25 Process Data Input 5 Msb Analog input value 0626 26 Process Data Input 5 Lsb 3C27 27 Process Data Input 6 Msb Analog aux 2 input value 0628 28 Process Data Input 6 Lsb 5A29 29 Process Data Input 7 Msb Analog aux 3 input value 0630 30 Process Data Input 7 Lsb 2331 31 Process Data Input 8 Msb Analog aux 4 input value 06
12 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
BYTE BYTE DESCRIPTION DEFAULT VALUE(HEX)A B
32 32 Process Data Input 8 LSB 2433 33 Process Data Input 9 MSB Analog aux 5 input value 0634 34 Process Data Input 9 LSB 2535 35 Process Data Input 10 MSB Digital input status 0536 36 Process Data Input 10 LSB 3D37 37 Process Data Input 11 MSB Digital output status 0638 38 Process Data Input 11 LSB 9839 39 Process Data Input 12 MSB Self/autotuning status 0540 40 Process Data Input 12 LSB 2841 41 Process Data Input 13 MSB Ammeter input1 value 1 0542 42 Process Data Input 13 LSB D443 43 Process Data Input 14 MSB Voltmetric input1 f. value 1 0544 44 Process Data Input 14 LSB 4245 45 Process Data Input 15 MSB Frequency value 0546 46 Process Data Input 15 LSB 3B47 47 Process Data Input 16 MSB Power factor 0648 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
1380959B_MSW_GFW-PROFIBUS_07-2019_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 0550 82 Process Data Output 1 LSB 3151 83 Process Data Output 2 MSB Local SetPoint value 0452 84 Process Data Output 2 LSB 8A53 85 Process Data Output 3 MSB SetPoint 1 value 0454 86 Process Data Output 3 LSB E655 87 Process Data Output 4 MSB SetPoint 2 value 0456 88 Process Data Output 4 LSB E757 89 Process Data Output 5 MSB Control output value 1 0458 90 Process Data Output 5 LSB FC59 91 Process Data Output 6 MSB Alarm point 1 value 0460 92 Process Data Output 6 LSB 0C61 93 Process Data Output 7 MSB Alarm point 2 value 0462 94 Process Data Output 7 LSB 0D63 95 Process Data Output 8 MSB Alarm point 3 value 0464 96 Process Data Output 8 LSB 0E65 97 Process Data Output 9 MSB Alarm point 4 value 0466 98 Process Data Output 9 LSB 3A67 99 Process Data Output 10 MSB Alarm HB input1 value 0468 100 Process Data Output 10 LSB 3769 101 Process Data Output 11 MSB No data 0570 102 Process Data Output 11 LSB CE71 103 Process Data Output 12 MSB No data 0572 104 Process Data Output 12 LSB CE73 105 Process Data Output 13 MSB No data 0574 106 Process Data Output 13 LSB CE75 107 Process Data Output 14 MSB No data 0576 108 Process Data Output 14 LSB CE77 109 Process Data Output 15 MSB No data 0578 110 Process Data Output 15 LSB CE79 111 Process Data Output 16 MSB No data 0580 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
14 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
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.
1580959B_MSW_GFW-PROFIBUS_07-2019_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).
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 38 MSB Diagnostic external GFW xx 9 LSB Diagnostic external GFW xx
In which:
xx TEXT DESCRIPTION00 - No active alarm01 DEVICE “n” TIMEOUT No Modbus communication with GFW02 DEVICE “n” UNKNOWN Instrument unknown04 DEVICE “n” SETTING Dip switch GFW not correct08 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.
DIAGNOSTICS DATA REQUEST TELEGRAM (SAP 60)
16 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
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 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 DESCRIPTION1 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 node3 FC Function code to specify procedure: Bit/Word Read/Write4 DATA ITEM 1 Depends on FUNCTION CODE5 DATA ITEM 2 Depends on FUNCTION CODE6 DATA ITEM 3 Depends on FUNCTION CODE7 DATA ITEM 4 Depends on FUNCTION CODE
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
1780959B_MSW_GFW-PROFIBUS_07-2019_ENG
Reading a bit: Function Code 1 or 2Request bytes
TRGTrigger
ADD SLAVESlave
Address
FC1 or 2
ADD MSBAddress of Bit
to read
ADD LSB Address of Bit
to read
NB MSB Number of bit
to read(always 00)
NB LSB Number of bit
to read(always 01)
Reply bytes
TRGReply totrigger
set
ADD SLAVEConfirmSlave
address
FCConfirm
procedure code1 or 2
NBNumber ofbytes read(always 1)
BIT Bit value:
0 o FF
# Empty
# Empty
Reading a word: Function Code 3 or 4Request bytes
TRGTrigger
ADD SLAVESlave
Address
FC3 or 4
ADD MSBAddress of word
to read
ADD LSB Address of word
to read
NW MSB Number of
word to read(always 00)
NW LSB Number of
word to read(always 01)
Reply bytes
TRGReply totrigger
set
ADD SLAVEConfirmSlave
address
FCConfirm
procedure code
NBNumber ofbytes read(always 2)
WMSB Msb word
value
W LSB lsb word
value
# Empty
Writing a Bit: Function Code 5Request bytes
TRGTrigger
ADD SLAVESlave
Address
FC5
ADD MSBAddress of Bit
to read
ADD LSB Address ofbit to write
BIT value of bit
to write (00 or FF)
00 (always 00)
Reply bytes
TRGReply totrigger
set
ADD SLAVEConfirmSlave
address
FCConfirm
procedure code
ADD MSBAddress ofbit written
ADD LSB Address ofbit written
BITvalue of bit
written(00 or FF)
00 (always 00)
Writing a word: Function Code 6Request bytes
TRGTrigger
ADD SLAVESlave
Address
FC6
ADD MSBAddress of
word to write
ADD LSB Address of
word to write
W MSBAddress of
word to write
W LSB Address of
word to write
Reply bytes
TRGReply totrigger
set
ADD SLAVEConfirmSlave
address
FCConfirm
procedure code
ADD MSBAddress of
word written
ADD LSB Address of
word written
W MSBmsb value ofword written
00 lsb value ofword written
18 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
Reply bytes
TRGReply totrigger
set
ADD SLAVEConfirmSlave
address
FCProcedure
code + 80hex
CODEError code
# Empty
# Empty
# Empty
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.
1 = Illegal function
2 = Illegal data address
3 = Illegal data value
6 = Slave device busy
9 = Illegal number data
10 = Read only data
1980959B_MSW_GFW-PROFIBUS_07-2019_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 DATAA B8 8 Process Data Input 1 MSB Process Data Output 1 MSB9 9 Process Data Input 1 LSB Process Data Output 1 LSB10 10 Process Data Input 2 MSB Process Data Output 2 MSB11 11 Process Data Input 2 LSB Process Data Output 2 LSB12 12 Process Data Input 3 MSB Process Data Output 3 MSB13 13 Process Data Input 3 LSB Process Data Output 3 LSB14 14 Process Data Input 4 MSB Process Data Output 4 MSB15 15 Process Data Input 4 LSB Process Data Output 4 LSB16 16 Process Data Input 5 MSB Process Data Output 5 MSB17 17 Process Data Input 5 LSB Process Data Output 5 LSB18 18 Process Data Input 6 MSB Process Data Output 6 MSB19 19 Process Data Input 6 LSB Process Data Output 6 LSB20 20 Process Data Input 7 MSB Process Data Output 7 MSB21 21 Process Data Input 7 LSB Process Data Output 7 LSB22 22 Process Data Input 8 MSB Process Data Output 8 MSB23 23 Process Data Input 8 LSB Process Data Output 8 LSB24 24 Process Data Input 9 MSB Process Data Output 9 MSB25 25 Process Data Input 9 LSB Process Data Output 9 LSB26 26 Process Data Input 10 MSB Process Data Output 10 MSB27 27 Process Data Input 10 LSB Process Data Output 10 LSB28 28 Process Data Input 11 MSB Process Data Output 11 MSB29 29 Process Data Input 11 LSB Process Data Output 11 LSB30 30 Process Data Input 12 MSB Process Data Output 12 MSB31 31 Process Data Input 12 LSB Process Data Output 12 LSB32 32 Process Data Input 13 MSB Process Data Output 13 MSB33 33 Process Data Input 13 LSB Process Data Output 13 LSB34 34 Process Data Input 14 MSB Process Data Output 14 MSB35 35 Process Data Input 14 LSB Process Data Output 14 LSB36 36 Process Data Input 15 MSB Process Data Output 15 MSB37 37 Process Data Input 15 LSB Process Data Output 15 LSB38 38 Process Data Input 16 MSB Process Data Output 16 MSB39 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
20 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
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
2180959B_MSW_GFW-PROFIBUS_07-2019_ENG
USE OF THE GFW-PROFIBUS WITH SIEMENSSTEP7 – TIA PORTAL
CONFIGURATION
The “GFWH0D76.GSD” file contains the information necessary to manage a GFW Slave PROFIBUS DP node. This file must be installed in the SIEMENS Step7 programming environment in order to insert the GFWs in the hardware configuration of the PROFIBUS network.
Open the hardware configuration of the project
Select “Options/Manage GSD” to install the new GSD file.
In the window that appears, search for the file on the medium where it is stored (USB KEY or Hard Disk).
A new device has now been added to the catalog under the name “GFW HIGH PERFORMANCE”. Open project station configuration again.
GSD FILE INSTALLATION
MENU
SELECTING NEW GSD FILE
22 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
In the “Catalog” area, expand the “Other field device” / “PROFIBUS DP” / ”PLC” / “GEFRAN spa” / “GFW HIGH PERFORMANCE” folder and identify the instrument in question.
Use the mouse to drag the icon corresponding to the device in question onto the row corresponding to the project PROFIBUS. A new Profibus slave will be created.
Assign the PROFIBUS node to the new slave. The PROFIBUS node must be consistent with the one set with the rotary switches on the GFW.
“CATALOG” AREA
GFW HIGH PERFORMANCE
SELECTING ADDRESS AND BAUDRATE GFW module
2380959B_MSW_GFW-PROFIBUS_07-2019_ENG
Enable the “Device view” folder and, depending on the number of expansions connected to the same GFW-PROFIBUS node, use the mouse to drag the “GFW Module” with the desired number of words to the “Device overview” area on the device. The peripheral memory areas used by the instrument to exchange process data will be assigned automatically.
The first 7 bytes of I/O are referred to as “Consistence”, and in the figure these correspond to the addresses 256... 262 and represent “Parametric Data”. The next 64 words, at addresses 263..326 in our example, represent “Process Data”.
Always check that the hardware configurator has assigned adjacent addresses in memory for all rack zones. If there are “gaps” in the addresses, manually assign the first address in an area you know is free. The E addresses (inputs) must be the same as the A addresses (output). During GFW hardware configuration, it is useful to reserve an area in memory for the maximum number of zones that may be used on each rack (16).
ASSIGNED MEMORY AREA
24 80959B_MSW_GFW-PROFIBUS_07-2019_ENG
PARAMETRIZATION
When the properties of the DP slave are selected in the “Device overview” window, the specific properties of the DP slave appear and the user can select the preferred Process Data.
As we have seen, a variable may be assigned in the Modbus Memory Map appearing in the drop-down menu to each of the 16 or 32 input and output words available for each GFW instrument. The data are cyclically reported in the assigned data block.
The data in the INPUT AREA is read cyclically by the GFWs, while the data in the OUTPUT AREA is written in the controller only if the data is changed.
CONFIGURABLE PROCESS DATA
2580959B_MSW_GFW-PROFIBUS_07-2019_ENG
STANDARD SLAVE DIAGNOSTICS AREA
When “Slave_1” is selected in the “Device overview” window, the general properties appear, and it is possible to identify the address of the slave’s global diagnostics area.
This area may be read with SFC 13 “DPNRM_DG” . Refer to the Siemens Step 7 manual for information on how to use it.The slave supplies not only the standard bytes but extensive diagnostics data in a word.
CONFIGURABLE PROCESS DATA
26 80959B_MSW_GFW-PROFIBUS_07-2019_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 completed. A bit is normally set to enable the branch (EN) and reset with the bit rise front “Done”.
FB1 “OPGFW”
Manages the basic operations of “Parametric Data” for GFW configuration.
The block requires 5 input parameters and responds with 4 output parameters.
Input parameters:
1. DBNr (INT) is the data block number associated with the rack containing the GFW we wish to query or command. 2. SlaveNr (INT): the MODBUS address of the GFW we want to work with. 3. OPCode (INT): the operation code that allows the function to find out if we want to read or write a word or a
bit. The operation codes are: • 1 = Reading Operation Code bit • 3 = Reading Operation Code word • 5 = Writing Operation Code bit • 6 = Writing Operation Code word
4. Address (INT): the address of the word or bit we want to read or write. (Refer to manual /6/ to identify the MODBUS addresses of words and bits)
5. INValue (INT): the value we want to write in the selected word or bit. When writing a bit, the value must of course be either 1 or 0. This parameter is ignored in reading operations.
Output parameters:
1. Done (BOOL): value is 1 when the reading operation has been completed2. OUTValue (INT): the value read in the specified word or bit. In writing operations, 1 is written if the action is
successfully completed, or 0 if it concludes in an error 3. Error (BOOL): the value is 1 when the operation concludes in an error. 4. ErrCode (INT): the code of the error encountered:
1 Illegal function
2780959B_MSW_GFW-PROFIBUS_07-2019_ENG
2 Illegal data address 3 Illegal data value 6 Slave device busy 9 Illegal number data 10 Read only data 20 Communication timeout 21 Input value error
GEFRAN spavia Sebina, 74
25050 Provaglio d’Iseo (BS) ItalyTel. +39 0309888.1
Fax +39 [email protected]
http://www.gefran.com