sitrain profibus fms

1. Technical Description

2. PROFIBUS (PB) - Basic Characteristics

3. PB - Bus Access

4. PB - FDL -Frames

5. Configuring FDL - Connections

6. NCM S7 for PB / FMS (Manual)

7. OLE/DDE - Manager

8. Exercises for FMS

9. Solutions for FMS

10. Glossar

Information and TrainingAutomation and Drives

Communication

PROFIBUS-FMS

Course KO-7KFMSAL: N ECCN: N

Export RegulationsAL Number of European resp. German export list.

Goods with labels not equal to N are subject to export authorization.ECCN Number of US export list (Export Control Classification Number). Goods

with labels not equal to N are subject to re-export authorization forexport to certain countries.

Indication Goods labeled with AL not equal to N (here: technical documentations)are subject to European or German export authorization when beingexported out of the EU.Goods labeled with ECCN equal to N (here: technical documentations)are subject to US re-export authorization.Even without a label, or with label AL:N or ECCN:N, authorization maybe required due to the final whereabouts and purpose for which thegoods are to be used.Decisive are the export labels stated on order acknowledgements,delivery notes and invoices.

This document was produced for training purpose.Siemens assumes no responsibility for its contents.The reproduction, transmission or use of this document or its contents is not permittedwithout express written authority. Offenders will be liable to damages. All rights,including rights created by patent grant or registration of a utility model or design, arereserved.

SIEMENS AG 2011

Name: ___________________________Course: from ____________ to ____________Instructor: ___________________________

Infoline Tel: 01805 23 56 11Fax: 01805 23 56 12

Internet: http://www.ad.siemens.de/training

ID-Nr.:Release A5.0 (for STEP7 Version 5.02.x)

date: 27.02.2011file: 7FmsTd.1

SIMATIC NETSiemens AG 1998. All rights reserved.

Information- and Trainings-CenterKnowledge for automation

Technical Description

date: 27.02.2011file: 7Kdp_Ov.1



PROCESSFIELDBUS




Fieldbus system for the lower and mid performance range,according to DIN 19245

Transfer medium: Shielded, twisted two-wire cable Glass or plastic fiber-optic cable

Access procedure: token passing with master/slave Transmission speed 9.6 Kbit/s to 12 Mbit/s Length:

Up to 9 km with a two-wire cable, Up to 90 km with glass fiber-optic cable

Maximum of 127 nodes

The PROFIBUSPROCESSFIELDBUS




Access Procedure(1)

(2)

Token passing between active nodes (1)Master-slave between active and passive nodes (2)

The PROFIBUS PROCESSFIELDBUS




Profiles for All Field Area Applications:

PROFIBUS-FMSFMS interface for universal communication tasks in the field area(DIN 19245 T.2)

PROFIBUS-DPFor fast communication with distributed I/Os(PROFIBUS DP, DIN E 19245, Part 3)

DP Distributed I/OsFMS Fieldbus Message Specification





Communication with PROFIBUS DP Connecting I/O devices to a

programmable logic controller Fast transmission of small

amounts of data because of Cyclic master/slave

communication Mono-master operation Interface with reduced protocol

Data exchange in two frames: Master sends data to the slave. Slave replies with data.

The PROFIBUS

...such asSIMATIC S7with CPU 315-2

for example, SIMATIC ET 200, drives,valve islands, etc.

Slave Slave

Master

Slave

PROCESSFIELDBUS




PROFIBUS DP Interface for fast, cyclic communication with field devices Data transmission rate up to 12 Mbit/s Measured bus reaction time for 10 ET200 stations

with 32 I/Os each: 0.35 ms PROFIBUS-DP standardized as DIN 19245, Part 3 For less exacting response time requirements, operation of

DP and FMS devices on one bus system possible





Communication with PROFIBUS FMS Connecting programmable logic

controllers with each other (cellnetwork)Possible to connect fielddevices

Transfer of larger amounts ofdata

Multi-Master operation:Send authorization passes fromone master to the other

Functionality, not responsetime, is the primary emphasis!


Master

for example,SIMATIC S7 with FMS-CP

MasterMaster

Slave Slave




FMS, the PROFIBUS User Interface User services:

Variable Access(reading and writing variables) Program Invocation(combining domains to form a program and controlling program

execution) Domain Management

(loading logically connected memory areas: domains) Event Management(services for user-controlled interrupt processing)

Management services: VFD Support (services providing information about the device) Object list management (reading/writing the object list) Context Management (establishing, clearing and cancelling a

connection)


VFD= Virtual Field Device




Combimaster Operation FMS and DP interface

in one master module: Transfer of larger amounts of data

between the masters with FMS Connecting I/Os with DP

Reduction of hardware costs DP communication for non-time

critical applications only :Multimaster operation slowsdown DP communication!

The PROFIBUS

Combi-master

DP Slave DP Slave...DP Slave

for example,SIMATIC S7withFMS-CP

for example, SIMATIC ET 200, drives,valve islands, etc.

Combi-masterFMS

DP

PROCESSFIELDBUS

only S5




Segment Configuration

Bus terminal

Twisted, shielded, two-wire cable

max. 1000 m (RS 485), max. 32 nodes

Bus connector

Repeater

...





Range of a Network Segment (Two-Wire Cable)Data Rate(Kbit/s)

9.619.293.75187.55001500

3,6,12000

100010001000800400200100

Segment Lengthwith nodes (m)





SIMATIC NET PROFIBUS: FO (Fiber Optic) Modular network configuration

Star, bus, and ring structures with Optical Link Modules OLM

Glass fiber-optic cable BFOC (ST) connection technique

Plastic fiber-optic cable BFOC (ST) connection technique for OLM modules HP Simplex connection technique for OLP modules





SIMATIC NET PROFIBUS Properties: FO OLM Modules in block design with the following interfaces:

BFOC (ST) sockets (fiber-optic cable connection) Terminal block with an integrated terminator Sub-D socket (RS 485)

Optical star, bus, and ring configurations Distance between two OLMs:

About 2850 m with glass fiber-optic cable About 50 m with plastic fiber-optic cable Up to 10 or 15 km with OLM/S-1300

CascadingOLM = Optical Link Module





SIMATIC NET PROFIBUS Properties: FO OLM Automatic identification and setting of the data

transmission speed (9.6 Kbit/s - 1.5 Mbit/s), (12 Mbit/s ) Control functions

Connectable echo function, continuous signal monitoring Automatic network test during start-up Operational signalling and error signalling

IP 40 degree of protection Redundant 24V DC supply possible

OLM = Optical Link Module





SIMATICS5-100UP S 9 3 1

V O LT A G ES E L E C TO R

115/230V AC24V DC 2A6ES5 931-8MD11C

21 3 4 5 6

230V

L 1

N

L +

M

115/230V AC

24V DC

CH 1CH 3

CH 2CH 4

PowerSINEC L2FO OLM

CH 1CH 3

CH 2CH 4

SIEMENS

CH 1CH 3

CH 2CH 4

SIEMENS

CH 1

PowerSINEC L2FO OLM

PowerSINEC L2FOOLM

CH 2AB CH 2AB CH 2

AB

SIEMENS

CH 1 CH 1

SIMATIC NET PROFIBUS: FO OLM






SIMATIC NET PROFIBUS: FO OLM - BusConfiguration

CH 3 CH 4 CH 3 CH 4CH 2

CH 1

CH 2

CH 1

CH 2

CH 1

CH 2

CH 1

CH 4 CH 3

OLM/S3 OLM/S4 OLM/S4 OLM/S3






CH 3 CH 4 CH 3 CH 4CH 2

CH 1

CH 2

CH 1

CH 3 CH 4CH 2

CH 1

CH 3 CH 4CH 2

CH 1

OLM/S4 OLM/S4 OLM/S4 OLM/S4

SIMATIC NET PROFIBUS: FO OLM - Double RingConfiguration

Max. distances between two OLMs (max. 7 OLMs cascaded, max. 10 km ring circumference)Trans. speed 9.6 - 187.5 500 1500 Kbit/sDistance 2800 1600 500 m





SIMATIC NET PROFIBUS: FO OLM/S-1300


Modules for bridging greater distances Max. 15 km with monomode fiber between two OLM/S-1300 Max. 10 km with graded-index optical waveguides 50 and62.5 m between two OLM/S-1300


max. 15 km

OLM/S3-1300

max. 15 km

OLM/S3-1300

CH 3CH 3 CH 3

OLM/S4-1300

date: 27.02.2011file: 7Kdp_Tok.1

SIMATIC NETSiemens AG 1998. All rights reserved..


PROFIBUS - Bus AccessTOKEN Management




Overview

ACTIVE stationwith

Bus access control

PASSIVE stationwithout

bus access control

PROFIBUS




Overview Logical Token Ring

TS = 1NS = 2PS = 4

Physicalbusconnection

SA = 2 DA = 3

SA = 3 DA = 4

SA = 4 DA = 1

SA = 1 DA = 2

TOKEN

TS = 2NS = 3PS = 1

TS = 3NS = 4PS = 2

TS = 4NS = 1PS = 3

SA = 2 DA = 3

SA = 3 DA = 4

SA = 4 DA = 1TOKEN

SA = 1 DA = 2

SA = 1 DA = 2TOKEN

TOKEN

TOKEN

TOKEN

TOKEN

TOKEN

TOKEN




Overview

Acyclic Services ("One-Off" services) Send Data with No Acknowledgement (SDN)(Broadcast)

Send Data with Acknowledgement (SDA)

Data

Data

Send and Request Data with Reply (SRD)

DataData with data request

Message Transfer

Acknowl.




Overview Cyclic Service

Cyclic Send and Request Data with Reply (CSRD)

Station n

Station n + 1

Data with data request

Data

Data

Data with data request




TOKEN Management Logical token ring of active stations with direction for token passing

1

5

2 3 4

6 7 8 10

Physical busconnection

Activestations

Passivestations

TS




TOKEN Management Receiving the TOKEN

Prev. station Logical TOKEN ring Next station

Message cycles

PS = 2

Station 3

SA = 2 DA = 3

List of Active Stations(LAS) of Station 3

TS = 3

TSPS

32

Own addressPreviousstation

TOKEN




TOKEN Management TOKEN Sender

Station 4Previous station

Next station

List of Active Stations(LAS) of station

Own address

Nextstation

TS = 4NS = 5

TS 4

NS 5

SA = 4 DA = 5TOKEN




TS = 3PS = 2

TS = 2NS = 3

TOKEN

TOKEN

TOKEN

TOKEN

No bus activity

No bus activity

No bus activity

SA = 2 DA = 3

1st retrySA = 2 DA = 3

SA = 2 DA = 3

SA = 2 DA = 4

2nd retry

Slot time

Slot time

Slot time

Pass TOKEN to active station after next

TOKEN Management TOKEN Sender




Request FDL Status

TS = 1NS = 3

TS = 3PS = 1

TS = 2

TOKEN

RequestFDL Status

Reply

Logical ring

One address is checked each time the token is received. This check is madewith the => Request FDL-Status




LAS List of Active Stations

This list is created in the "Listen-Token" state.(Listening-in phase after power-up)The list contains all the ACTIVE stations in the logical TOKEN ring.

GAPLThe address area for which this ACTIVE station is responsible is mappedto the GAPL.The area extends from the station's own address (FDL address)to the address of the next station (NS).

TOKEN Management Lists in ACTIVE Stations




Lists in ACTIVE StationsTOKEN Management

LAS List of Active Stations

This list is created in the "Listen-Token" state.(Listening-in phase after power-up)The list contains all the ACTIVE stations in the logical TOKEN ring.

GAPLThe address area for which this ACTIVE station is responsible is mappedto the GAPL.The area extends from the station's own address (FDL address)to the address of the next station (NS).




1LAS-

1

2 3 4 5

1 2

T:1-1

T:1-1

1 2 3

1 2 3 4

1 2 3 4 5

T: 1-1 "Ready" for the ringTOKEN from Station 1 to Station 1 Status request

Status req.

Status req.

Status req.

Status req.

"Ready"

"Ready"

"Ready"

"Ready"

T: 1-2T: 2-1T: 1-2

T: 2-3T: 3-1

T: 1-2T: 2-3

T: 3-4T: 4-1

T: 1-2

T: 1-2

T: 2-3

T: 2-3

T: 3-4

T: 3-4

T: 4-5T: 5-1

T: 4-5T: 5-1

Initializing the Logical Token Ring




TOKEN

TOKEN

TOKEN

TOKEN

TOKEN

A: Start of measurement of TOKEN rotation timeB: End of time measurement for executed cycleThe result is the real rotation time TRR .....Measurement of the following rotation times begins immediately.

A

B

TOKEN Management Token Rotation Time

TOKEN




TOKEN Management

If

a station can also execute low-priority messagecycles

TRR < TTR

Real Rotation Time TRRReal Rotation Time TRR

Target Rotation Time TTRTarget Rotation Time TTR




min TTR = na x (TTC + high TMC) + k x low TMC + mt x RET TMC

na = Number of active stationsk = Probable number of low-priority message cycles per token rotationTTC = Token cycle timeTMC = Message cycle time, depending on the frame lengthmt = Number of message retry cycles per token rotationRET TMC = Message retry cycle time

TOKEN Management Example of Calculation of the Operating Parameter

Target Rotation Time TTR :




TOKEN Management Example of Calculation of the Operating Parameter

Target Rotation Time TTR :min TTR = na x (TTC + high TMC) + k x low TMC + mt x RET TMC

na = Number of active stationsk = Probable number of low-priority message cycles per token rotationTTC = Token cycle timeTMC = Message cycle time, depending on the frame lengthmt = Number of message retry cycles per token rotationRET TMC = Message retry cycle time




Send Data with No Acknowledgement:SDN

- Send data to one or all (broadcast)stations without acknowledgement

Send Data with Acknowledgement:SDA

- Send data to one station withimmediate acknowledgement

Send and Request Data with Reply:SRD

- Send data to a station and, at thesame time, request data and expectan immediate reply with data

Acyclic Send / Request ModeSend / Request Mode




Polling is cyclic interrogation of or cyclic sendingof information to passive or active stations in aspecified sequence.

5763919257102108

Station AddressesPolling List

Send / Request Mode Cyclic Send / Request Mode




Send / Request Mode Cyclic Send / Request Mode

Polling is cyclic interrogation of or cyclic sendingof information to passive or active stations in aspecified sequence.

5763919257102108

Station AddressesPolling List




PollingList

Activestation

CSRD Cyclic SRD- Cyclic sending and requesting of data with immediate reply, using a

polling list

Passivestation

Token

Data + data request

Data

Data + data request

Data

Data and data request

Data

CSRD

CSRD

Send / Request Mode

CSRD




LIFE List Structure of the LIFE List

List length = 3 to 2n + 1FDL address (DA) of station kStation type (FDL status) kFDL address (DA) of station k + 1Station type (FDL status) k + 1

FDL address (DA) of station nStation type (FDL status) n

1)2)3)4)5)

L)L + 1)

k = First station present; n = max. 126; L = max. 254




active

passive

Appendix 1

One active station and one passive station

Two active stations

Minimum Configuration

active active




Appendix 2TS = 1 TS = 2 TS = 3 TS = 4


TOKEN

2nd retry

TOKEN

2nd retry

TOKEN

1st retry

1st retry

1st retry

2nd retry

SA = 1 DA = 4

SA = 1 DA = 3

SA = 1 DA = 2

SA = 1 DA = 1Example: Station failureTOKEN




TOKEN

TOKEN


Example: Receiving the TOKEN with adifferent SA

SA = 1 DA = 3

SA = 1 DA = 3

Slot time(Wait time to receive) After retry:

PS is set to 1 in theLAS! The TOKENring has changed

Appendix 3 Logical Token Ring

TS = 3NS = 4PS = 2(1)

TS = 4NS = 1PS = 3

TS = 1NS = 3PS = 4




Bus Transmission Time

The bus transmission time depends on the following values:

The data rate set for the bus The TOKEN hold time

(TTR minus TRR) The number of stations and resulting TOKEN rotation time


date: 27.02.2011file: 7Kdp_Fr.1


PROFIBUS - FrameData Link Layer (Layer 2)Fieldbus Data Link ( FDL )




Frame Characters

UART CharactersUniversal Asynchronous Receiver/Transmitter forStart-Stop characters

0 b1 b2 b3 b4 b5 b6 b7 b8 P 1

1 Start bit ST with binary "0" signal8 Information bit I with binary "0" or "1" signal1 Parity bit EVEN P with binary "0" or "1" signal1 Stop bit SP with binary "1 signal

LSB Least Significant BitMSB Most Significant Bit

1 2 3 4 5 6 7 8 9 10 11Bit string onthe lineBit significance (I) 20

LSB27

MSB

Start bit (ST) Stop bit (SP)Parity bit even




Frame Formats with Hamming Distance 4 (HD = 4) Formats with fixed information field length without data unit

SYN SD1 DA SA FC FCS EDL

Format of the request frame:

SCFormat of the short acknowledgement frame):

SYN = Synchronization bits, at least 33 bits idleSD1 = Start delimiter 1, code: 10HDA = Destination addressSA = Source addressFC = Frame controlFCS = Frame check sequence)ED = End delimiter, code: 16HL = Information field length, fixed No. of bytes, L=3SC = Single character, code: E5H

SD1 DA SA FC FCS EDFormat of the acknowledgement frame:

L




Frame Formats with Hamming Distance 4 (HD = 4) Formats with fixed information field length with data unit

SYN SD3 DA SA FC DATA_UNIT EDL

Format of the Send/Request frame:

SD3 DA SA FC DATA_UNIT FCS EDL

Format of the acknowledgement frame:

SYN = Synchronization bits, at least 33 bits idleSD3 = Start delimiter 3, code: A2HDA = Destination addressSA = Source addressFC = Frame control)DATA_UNIT = Data unit, fixed length (L-3) = 8 bytesFCS = Frame check sequence)ED = End delimiter, code: 16HL = Information field length, fixed No.of bytes L=11




Frame Formats with Hamming Distance 4 (HD = 4) Formats with variable information length

SYN = Synchronization bits, at least 33 bits idleSD2 = Start delimiter 2, code: 68HLE = Length, value: 4 to 249LEr = Length repeatDA = Destination addressSA = Source addressFC = Frame controlDATA_UNIT = Data unit, fixed length (L-3), max. 246 bytesFCS = Frame check sequenceED = End delimiter, code: 16HL = Information field length, variable No. of bytes L = 4 to 249

DATA_UNITSD2 LE LEr SD2 DA SA FC FCS EDL

Format of the response frame:

SYN SD2 LE LEr SD2 DA SA FC FCS EDL

Format of the Send/Request frame:DATA_UNIT




Token Frame

Token

SYN SD4 DA SA

SYN = Synchronization bits, at least 33 bits idleSD4 = Start delimiter 4, code: DCHDA = Destination address)SA = Source address)




Length, Address, Frame Control and Frame CheckSequence Bytes

Length bytes LE and LEr

DATA_UNITSYN SD2 LE LEr SD2 DA SA FC FCS EDL

Format of the Send/Request frame, Hd = 4:

27 20

L

b8 b1

Hd=4: L=4 to 249





Address bytes

SYN SD2 LE LEr SD2 DA SA FC FCS EDDATA_UNIT

SA Source address byte EXT 26 20

AddressSA = 0 to 126

b8 b1

DA Destination address byteEXT 26 20

AddressDA = 0 to 127

b8 b1





Address bytes

EXT 26 20

Address

b8 b1

EXT = 0 : No address extension in the DATA_UNITEXT = 1 : Address extension follows in the DATA_UNIT





DAE / SAE bytes in the frame

DA SA FC DAE FCS EDDATA_UNIT

EXT=1 EXT=0

DA SA FC SAE FCS EDDATA_UNIT

EXT=0 EXT=1

DA SA FC DAE SAE FCS EDDATA_UNIT

EXT=1 EXT=1





Address extension byte

DA SA FC DAE SAEDATA_UNITEXT=1 EXT=1

EXT TYP 25 20

Address

b8 b1b7 b6

b7 identifies the type

b8 indicates an additional address extension





Link Service Access Point (LSAP)

LSAPs = Layer 2 connectionSSAP (source) DSAP (destination)

SSAP (source)DSAP (dest.)FDL User 2FDL User 1

Associationsbetween the stations

PROFIBUS

SA

SADA

DA

DAE

SAE

SAE

DAE

Station 1 Station 2





Service Access Points (SAP)

LSAPLSAPLinkServiceAccessPoint

LinkServiceAccessPoint

SSAPSSAPSourceServiceAccessPoint

SourceServiceAccessPoint

DSAPDSAPDestinationServiceAccessPoint

DestinationServiceAccessPoint





Frame control byte, FC

Stn-Type: (Station Type and FDL Status)b6 b50 0 = passive station0 1 = active station not ready1 0 = active station ready for the logical token ring1 1 = active station in the logical token ring

FCB = Frame Count Bit: 0/1. Alternating call sequence bitFCV = Frame Count Bit valid

0 = alternating function of the FCB invalidFCV 1 = alternating function of the FCB validb6 b5FCB FCV0 0 = do not evaluate FCB (b6)x 1 = evaluate FCB (b6), X=0 or 11 0 = save FCB (b6)

1 FCB FCV 23 20

0 Stn-Type

b8 b1b7 b6 b5 b4

Res Frame Function

Res: Reserved (IEC-TC 57,P.5-2)

Frame Type:1 = (Send and/or Request; Primary)0 = (Acknowledgement/Response; Secondary)

Function:Transmission function





Frame Count Bit, FCB

Send/Request 1

Acknowledgement/Response

Send/Request 2


Send/Request 3


Save SA + FCBSA = 1FCB = 1

Evaluate FCBFCB = 0

Evaluate FCBFCB = 1SA = 1

SA = 1

SA = 1

FCV = 0FCB = 1FC byte



The frame count bit prevents duplication or loss of messages

Station 1active

Station 2active/passiveFC

Send/Request frame

FC = Frame Control

TS = 1 TS = 2





Frame Count BitFCB, FCV at the responder

FCB FCV Condition Meaning Action0 0 DA = TS/127 Call without acknowledgement

Call FDL Status / Ident/LSAP StatusDelete lastacknowledgement/response

0 / 1 0 / 1 DA TS Call to the other responder Delete last acknowl./response1 0 DA = TS Initial call FCBM := 1 SAM := SA

Delete last acknowl./response0 / 1 1 DA = TS

SA = SAM FCB FCBM

New call FCBM := FCBDelete last acknowl./responseKeep acknowl./response inreadiness for repetition

0 / 1 1 DA = TS SA = SAM

FCB FCBMCall repetition FCBM := FCB

Repeat acknowl./response andcontinue to keep in readiness

0 / 1 1 DA = TS SA SAM

New Initiator FCBM := FCB SAM := SAKeep acknowl./response inreadiness for repetition

-- -- Token Telegram Delete last acknowl./response

1 FCB FCV 23 20b8 b1b7 b6 b5 b4

Res Frame FunctionFCBM = Saved FCBSAM = Saved SA





Transmission function codeAufruf-Telegramme

Function Abkrzung Code Nr.IEC-TC 57, P.5-2, FC-Code 0-2 0-2Send Data with Acknowledge low SDA low 3Send Data with No Acknowledge low SDN low 4Send Data with Acknowledge high SDA high 5Send Data with No Acknowledge high SDN high 6Reserved / Req. Diagnosis-Data 7IEC-TC 57, P.5-2, FC-Code 8 8Request FDL-Status with Reply FDL-Status 9Reserve 10Reserve 11Send and Request Data low SRD low 12Send and Request Data high SRD high 13Request and Ident with Reply Ident 14Request LSAP-Status with Reply(Code Nr. 14 und 15: FMA 1/2)

LSAP-Status 15





Transmission function codeSend/Request frame; Primary)

b4 b3 b2 b1 Code Nr.0 0 0 0 00 0 0 1 10 0 1 0 20 0 1 1 30 1 0 0 40 1 0 1 50 1 1 0 60 1 1 1 71 0 0 0 81 0 0 1 91 0 1 0 101 0 1 1 111 1 0 0 121 1 0 1 131 1 1 0 141 1 1 1 15

Res 1 FCB FCV23 22 21 20

Function

b8 b1b7 b6 b5 b4 b3 b2

Frame control byte (FC)

Send/Request frameFrameTypeb7 = 1





Transmission function codeQuittungs-Telegramme

Function Abkzung Code Nr.ACKnowledgement positive OK 0 *ACK negativeFDL/FMA 1/2 - User Error

UE 1

ACK negativeno Resource for Send Data (& no Response FDL-Data)

RR 2

ACK negativeno Service activated

RS 3

Reserve 4 -7Response FDL/FMA 1/2-Data low (& Send Data ok) DL 8ACK negativeno Response FDL/FMA 1/2-Data (& Send Data ok)

NR 9 *Response FDL-Data high (& Send Data ok) DH 10Reserve 11Response FDL-Data lowno Resource for Send Data

RDL 12

Response FDL-Data highno Resource for Send Data

RDH 13

Reserve 14, 15





Transmission function codeAcknowledgement / Response frame; Secondary)

b4 b3 b2 b1 Code Nr.0 0 0 0 00 0 0 1 10 0 1 0 20 0 1 1 30 1 0 0 40 1 0 1 50 1 1 0 60 1 1 1 71 0 0 0 81 0 0 1 91 0 1 0 101 0 1 1 111 1 0 0 121 1 0 1 131 1 1 0 141 1 1 1 15

Frame control byte (FC)

Acknowledgementframe

FrameTypeb7 = 0

Res 023 22 21 20

Function

b8 b1b7 b6 b5 b4 b3 b2

Stn Type





Frame check sequence (FCS)

DATA_UNITSYN SD2 LE LEr SD2 DA SA FC FCS EDFormat of the Send/Request frame

27 20b8 b1

FCS byte

SYN SD1 DA SA FC FCS EDFormat of the Request frame




Data Unit

Address partmax. 4 address extension bytes

Data unit, Hd=4max. 246 bytes

SYN SD2 LE LEr SD2 DA SA FC FCS EDDATA_UNIT

DAE / SAE

Address part Data part

DATA_UNIT




Data Unit

Data part for Ident remote management service

SD2 LE LEr SD2 DA SA FC FCS EDDATA_UNIT

LE_VN LE_CT LE_HR LE_SR Vendor_name

Controller_type HW_release SW_release

Ident data part

Ident data part

Response frame




Data Unit Data part for LSAP Status remote management service

LSAP Status data part

SD2 LE LEr SD2 DA SA FC FCS EDDATA_UNIT

Response frame

AccessAddress-Extension

Role_in_service Service_type

Role_in_service Service_type

b8 b1b5 b4Byte 1

Byte 6

Date: 23.04.99File No.: 7KDP_AG.1

SIMATIC NETSiemens AG 1998. All rights reserved

Information and Training CenterKnowledge for Automation

Configuring FDL Connections(PLC-PLC)

PLC 1 PLC 2

CP CP

PROFIBUS




SIMATIC S7 / PROFIBUSCommunication

TaskA certain amount of data is to be transmitted from a data block (DB11) in PLC 1 to a vacantspace in a data block (DB12) in PLC 2.

PLC 1 PLC 1

CP

Senddata

CP

PROFIBUS

Receivedata

Data sourceDB11

Data destinationDB12

Data

Transmission direction




OverviewCommunication

PROFIBUS

Data Data

FC"RECEIVE"

FC"SEND"

PLCCPU

CPCommuni-cationsprocessor

CPCommuni-cationsprocessor

PLCCPU

PROFIBUS

CP 342-5 CP 342-5




Communication PLC - PLC Connections

PROFIBUS

S7 - 300

CP342-5

Conn Conn1 2 Conn 2

S5- 95U

S5S5-115U/135U/155U

CP 5431 FMS

Conn 1

DATA

DATA

DATA

DATA

"FDL connection"

"FDL connection"




Communication PROFIBUS: Transmitting data via an FDL connection

FCSEND

240-bytedata

source240-bytedata

destination

FCRECEIVE

Programin the CPU

Programin the CPUCP342-5 CP342-5

DATA FRAME

SIMATIC PLC 1 SIMATIC PLC 2

Acknowledgement




Communication Configuring, drawing a "wiring diagram"

PLC 2 PLC 3 PLC 4 PLC 5

PLC 1CP342-5

CP342-5 CP342-5 CP342-5 CP342-5

Conn = PROFIBUS FDL connection

PROFIBUS

Conn 1Conn 2

Conn 3

Conn 9Conn 4

Conn 5Conn 6 Conn 7 Conn 8




Communication Communication relationships

FC-SENDID-1

User program

PLC 1

CP342-5

CPU

Communication relationshipsIDID-1ID

SConnection xConnection yConnection z

FC-RECEIVE

ID-1

User program

PLC 2

CPU

Communication relationshipsIDID-1ID

Connection xConnection yConnection z

R

PROFIBUS CP342-5

Communication system"connections"

x

y

z




Communication Example: FDL connection between 2 PLCs

LSAPs for FDL connections

Station 1 (TLN1) Station 5 (TLN5)Example:

SSAP: 6DSAP: 2 SSAP: 2DSAP: 6

LSAP 6 LSAP 2PROFIBUS connection

DSAP Local PROFIBUSremote SAP = station address

+ 1

LSAP=Link Service Access Point (Layer 2 , Link Layer)SSAP=Source Service Access PointDSAP=Destination Service Access Point (BUFFER pointer)





Advantages:

- Simple parameter assignmentand programming

- Minimum negotiation

- PROFIBUS frame typealready defined (SDA)

CP 342-5

PLC 1

CP 342-5

PLC 2FDL connection





CP 1LocalLSAP:6

"Mailbox""House number"PROFIBUS ADDR:1

CP 2LocalLSAP:2

"Mailbox""House No."PROFIBUSADDR: 5

PROFIBUS

FDL connectionDataData





PROFIBUS ADDR: 1PLC 1 CP 1

SSAP: 6 (SAP 2...33)DSAP: 2 (SAP 2...33)

1

1

SEND

RECEIVE

1FCSEND1

FCRECEIVE

ID

ID

PROFIBUS ADDR:5PLCCP 2

SSAP: 2 (SAP 2...33)DSAP: 6 (SAP 2...33)

1

1SEND

RECEIVE1

1

FCRECEIVE

ID

ID

FCSEND

Example of anFDL connection

Sending and receivingvia an LSAP

DATA

DATAAcknowledgement

Acknowledgement

LSAP 6 LSAP 2





OB 1 SEND

RECEIVE

FC

FC

CP 342-5CPU

FDL protocol firmware

Connectionlocal ID

1

Connectionlocal ID

n

Connection table

Network parametersHSA , baud rate , profile

PROFIBUS station address

PROFIBUS





PGNCM S7 forPROFIBUSpackage

CP 342-5

CPUPG

STEP 7package

1. Assign parameters to CP

2. Program CPU




Communication Appendix

Data transmission via FDL connections using FCs

User UserFCs FCsCP 342-5(1) CP 342-5(2)PROFIBUS

Source

Trigger: SEND

Trigger: SEND

Source

SEND

SEND Destination

Destination

RECVPROFIBUSheader

PROFIBUSheader

PROFIBUSheader

PROFIBUSheader

SDA low

SDA low

Short ACK

Short ACK

TOKEN

TOKEN

TOKEN

TOKENRECV




Communication Appendix

User UserFCs FCsCP 342-5(1) CP 342-5(2)PROFIBUSTrigger: SEND

Trigger: SEND

SEND

SEND

PROFIBUSheader PROFIBUSheader

SDA low

SDA low

Short ACKPROFIBUSheader

PROFIBUSheader

ACK neg (RR)SDA low

SDA lowStation failure

Data transmission via FDL connections using FCs (special cases)

Source

Source

SENDTrigger: SEND

TOKEN

TOKEN

TOKEN

Source

TOKEN




Configuring Networks with NETPRO

Open NETPRO

Insert station

Define new node




Configuring FDL ConnectionsInsert connection

Remote stationSelect




Setting Connection Properties




Compiling and Downloading the Configuration DataSave and Compile

Download




AG_SEND/AG_LSEND Blocks (FC 5/FC50)




AG_RECV/AG_LRECV Blocks (FC 6/FC 60)

N




Exercise 1:PLC - PLC Communication

date: 27.02.2011file: 7ProNcm2.1



NCM S7 for PROFIBUS / FMS

date: 27.02.2011file: 7ProNcm2.2



CLIENT SERVERCreate a new FMS Connection Create a new FMS Connection

Configuring Connections Configuring Connections

Configure FMS Communicationvariables (create OD)

STEP 7- SYMBOL EDITOR

Create Function Blocks(READ, WRITE...)

LAD/STL/FBD-Editor

date: 27.02.2011file: 7FmsOle.1



SIMATIC NETOLE/DDE Manager




General Information - OLE/DDE ManagerWindows95Windows 3.xWindowsNT

PG770PG760PG740AT-compatible PCs

16-bit or32-bit version

OLE 2.0 (Object Linking and Embedding)DDE (Dynamic Data Exchange)

S7FMSDPTF

Fully compatible with theFMS/DDE Manager




General Information - OLE/DDE Manager

16-bit or32-bit version




Profibus oder Industrial-Ethernet

Funktionsprinzip des OLE/DDE-Managers

PC / PG

Standard Windows-Applikationen,die ber OLE2.0 oder DDE

verfgen (und freigegeben sind)

SIMATIC NETOLE/DDE-Manager

(OLE2.0/DDE)

Protokoll /Software

CP fr den PC / PG

Wind

ows

Standard Windows-applicationswith OLE2.0 or DDE

Protocol /Software

Method of operation of OLE/DDE - Manager




OLE / DDEWindows communication mechanisms:

OLE = Object Linking and EmbeddingDDE = Dynamic Data Exchange




DDE

Application Topic Item| !




Warm link

Hot link

Cold link for static data

for dynamicdata

for dynamicdata

DDE




Example of a DDE Conversation (hot link)

PC / PGPC / PGPC / PGCliente.g. Excel 7.0

ServerOLE/DDE Manager

WM_DDE_INITIATE (Application, topic)WM_DDE_ACK1 1

2 2

3 3

4 4

5 5

WM_DDE_ADVISE (Item)WM_DDE_ACK

WM_DDE_DATA (Item)WM_DDE_ACK

WM_DDE_UNADVISE (Item)WM_DDE_ACK

WM_DDE_TERMINATEWM_DDE_TERMINATE




OLESIMATIC NET OLE CONTROLS Provide methods and properties Can be integrated, for example, in:

MS Visual C++MS Visual BasicMS ExcelMS AccessMS FoxProBorland Delphi

COM (Component Object Model) Language-independent object model Specification for developing software components




OLE OLE is constantly being extended and improved OLE 2.0 is the central architecture concept of today'sversions of MS Windows

OLE 2.0 is a collection of interfaces, internal conceptsand services, the central feature of which is theComponent Object Model

The Component Object Model defines concepts andcomponents for creating objects and for communicationbetween them

Communication can take place between Windows objectsin different processes and in future versions of Windows willalso be possible between objects on different computers

Network capability will also be implemented in the future OLE-Automation: programmable access.




OLEOCX Control

= OLE Custom Control

E.g. for OLE/DDE Manager, 32-bit version,FMS protocol:

sfmsct32.ocx




The OLE/DDE Manager as aDiagnostics Component

SIMATIC NET Navigator

(SIMATIC NET DDE Diagnostics)

Trace




The OLE/DDE Manager as a Diagnostics ComponentSIMATIC NET Navigator




The OLE/DDE Manager as a Diagnostics ComponentSIMATIC NET Navigator - Open Connection / Variables




The OLE/DDE Manager as a Diagnostics ComponentSIMATIC NET DDE Diagnostics




The OLE/DDE Manager as a Diagnostics ComponentSIMATIC NET Trace




The OLE/DDE Manager as a Diagnostics ComponentConfiguring the SIMATIC NET Trace

date: 27.02.2011file: 7FmsEx.1



Exercises




Exercise 1: Creating Projects for FMSCommunication

Step Action Result

1Delete any existing projects withthe name "FMS.........".

2Create a project named"FMS_Client" (or "FMS_Server")in the path d:\course\7profi.

The project is created

3Create a hardware station withthe components in yourconfiguration.

The hardware station is created

4Insert the partner station in yourproject.

Partner station is inserted as"Other Station_............




Exercise 2: Inserting and Testing an FMS Connection

Step Action Result1 Insert an FMS connection in your

project.2 Parameters for this connection:

Station profile: CP 343-5 Connection profile: SIMATICNET

Standard B LSAP local and remote:34 Services: READ

WRITE3 Test this connection using NCM

Diagnostics.Connection status should be:"Ready for data transmission"You are enthusiastic!

UEB_UPP




Exercise 3a: For Server (READ)Configuring the Communication Variables

Step Action Result

1Create a data block, DB50, withthe symbolic name "Motoren".

2Configure the communicationvariables as shown below.

3Select the following indexes: FMS Base Index : 101 Number of reserved Indexes:1




NotizblattsichtNotizblattsicht




NotizblattsichtNotizblattsicht

Exercise 3b: For ClientProgramming a Write Job

Step Action Result

1Copy the "READ FB" (FB3)from the SIMATIC_NET_CPlibrary into your user program.

2Write (in OB1, for example) theprogram for reading the servervariable with index 106("DrehzahlM3") to MW50 andthen saving it in DB20.

MW50 and DB20 should containthe integer value "3333".If not --> Error

3Test your communication(VATs, Block Status, NCMDiagnostics)




Exercise 4a: For Server (WRITE)Configuring the Communication Variables

Step Action Result

1Create a data block, DB51, withthe symbolic nameWRITE_from_Client.

2Configure the communicationvariables as shown below.

3Select the following index:FMS Base Index : 110




Exercise 4b: For ClientProgramming a Write Job

Step Action Result

1Create a DB30("WRITE_Source") with thevariable "W rite" and theassigned value W#16#AFFE.

2Copy the "WRITE FB" (FB6)from the SIMATIC_NET_CPlibrary into your user program.

3Write the program for storingthe contents of the variable"W rite" in DB51 on the server.

DB51 contains the hexadecimalvalue "AFFE".You've done it right again!

4Test your communication(VATs, Block Status, NCMDiagnostics)




Exercise 5: REPORT

Step Action Result1 Report the variable written in

Exercise 4 to the client with aREPORT job.

The hexadecimal value "AFFE" isreported to the client.

2 Output one byte of the reportedvariable in output byte QB4.




Well Done

Thankyou for com

ing

Have a safe journ

ey home

Diploma

date: 27.02.2011file: 7FmsSol.1



Solutions




Communication properties - Server

Datum: 09.09.98Datei.Nr: Glossar.1


Informations- und Trainings-CenterWissen fr Automatisierung

Glossar




FMS_capa.pdfFMS_1.pdfFMS_2.pdfFMS_3.pdfFMS_4.pdfFMS_5.pdfFMS_6.pdfFMS_7.pdfFMS_8.pdfFMS_9.pdfFMS_10.pdf

sitrain profibus fms

Documents