Académique Documents
Professionnel Documents
Culture Documents
f
e
d
c
b
a 13.05.14 BDU PBA Document N°
Rev Date REDIGE / Written by VERIFIE / Checked by Installation Type Incr. L Rev
1 INTRODUCTION ...................................................................................... 3
1 Introduction
This document describes the used way in HE0050 to connect the SCM
equipments to Profinet.
2 PROFINET DESCRIPTON
2.1 Introduction
The purpose of this protocol is to establish a multipoint link for one or more SCM units
on a communication bus with a special interface card. This protocol allows SCM units
to be linked with programmable logic controllers or other higher level supervisors.
Until a communication protocol is standardized and becomes general, we have
implemented the PROFINET protocol, which is one of the most commonly used at
the present time.
This communication protocol is based on the OSI model and uses the following
layers:
2.2 Presentation
The PROFINET protocol is a communication protocol developed by MODICON and
implemented by APRIL and other manufacturers to link together automatic devices.
In most cases, equipment manufacturers provide hardware and/or software
interfaces to handle the complete PROFINET protocol. This means that the user
has only to run the available services in the application layer according to the
provided instructions, the communication is than totally transparent.
In appendix we describe the different hardware and Software devices needed to link
SCM to Controllers from Siemens.
For the users, having to write the complete communication protocol (layers 1, 2
and 7) the complete specification of the protocol can be requested by:
Gould-MODICON
Gould PROFINET protocol, reference PI-MBUS-300 Rev D
2.3 Principle
The PROFINET / SCM interface is of slave type, which means that the SCM will only
respond to an explicit request from the master
The PROFINET protocol is multipoints.
This means that a master (and one only) and several slaves can be interconnected to
a communication network, as long as feasible with the hardware link. Each message
will include a destination address for the master´s request and a source address for the
slave's answer.
4 Data layout
4.1 Principle
The mapping of the data of each slave can be freely edited in the file
xxx.kgr for the weighfeeder machine. These operations are handled
with HASLER Tools distributed on CD ROM.
The mapping of the data, the IN/OUT block size are :
Input block size (64 Bytes)
Output block size (16 Bytes)
A) Main frame
1) The node address corresponds to the basic MB slave address. When the kgr-file is
downloaded to the SCM, this address is set to: SCM address + Node address.
For this, one kgr file can be downloaded to several SCM.
WF D1 Address: 1
IP ADRESS to be set by the MBDP SLAVE ADDRESS: 1+1=2
client
WF2 = 3 , WF3=4
Register size (Word) Example: MB address of the first SCM =27
Node address: 28
An ASR, PSR (Parameter for the process) or ASW (Alarm process) can be affected at
each bit. The chart with all available ASR, ASW is distributed with the HASLERs Tools.
The ASR, ASW data are arranged inside according to the type of machine (Loss in weigh
feeder, Beltweighfeeder).
Single parameters (Flowrate, setpoint,) can be mapped according to the following screen.
The register type can be also edited.
The status of each output of the SCM (Total 16) can be read through a word.
Each bit is affected by a configured output of the SCM.
This outputs are configured with the SDU (output menu). The attributes of bit number is
according to the FE0040 number of the output.
Reading
The status of each input of the SCM (total 24) can be read through a word.
Each bit is affected to one individual word. Each word is set to a configured input of the
SCM.
Writing
It is also possible to modifiy the value of each input. For this, we have to switch off the
internal control of all inputs. We do not recommend to work in this mode.
It means for your application, we cannot check the “feedback run” and “thermal status” of
the machine.
4.3.1 ADDRESS
IP : 172.30.84.0
NetWork maskIP: 255.255.0.0
Default Gateway: 172.30.80.201
4.3.2 POLL
4.4 OUTPUTS
4.4.2 STATUS
4.4.3 STATUS
4.4.4 STATUS
2 21 -----
3 22 -----
3 -----
4 2
5 24 -----
5 -----
6 2
7 26 -----
7 -----
8 2
9 28 -----
10 29 -----
11 210 -----
12 211 -----
13 212 -----
14 213 -----
15 214 -----
16 215 -----
24 223 -----
2 21 -----
3 22 -----
3 FRENQUENCY INVERTER
4 2
AVAILABLE
5 24 -----
6 25 BELTDRIFT
8 27 -----
9 28 -----
10 29 -----
11 210 -----
12 211 -----
13 212 -----
13 -----
14 2
15 214 -----
15 -----
16 2
4.5 INPUTS
4.5.2 COMMANDS