Iec tr 62453 52 31 2017

A Device DTM is resp n ible for providin config ration an p rameterization information for a PROFIBUS master that puts the PROFIBUS slaves in o eration... – Commu ication p rameterizatio

IEC TR 62453- 52- 31

Editio 1.0 2 17-0

Field device t ool (FDT) int er ace specificat ion –

Part 52-31: Communicat ion implement at ion for common language

inf ast ruct ure – IEC 61784 CP 3/1 and CP 3/2

THIS PUBLICATION IS COPYRIGHT PROTECTED

Copyr ight © 2 17 IEC, Ge e a, Switzer la d

Al rig ts r es r ve Unle s oth rwis s e ifi d, n p rt of this p blc tio ma b r epr od c d or uti z d in a y form

or b a y me n , ele tr onic or me h nic l in lu in p oto o yin a d microfim, with ut p rmis io in wr itin from

eith r IEC or IEC's memb r Natio al Commite in th c u tr y of th re u ste If y u h v a y q e tio s a o t IEC

c p r i ht or h v a e q ir y a o t o tainin a ditio al ri hts to this p blc tio , ple s c nta t th a dr es b low or

y ur lo al IEC memb r Natio al Commite for ur th r informatio

Th Intern tio al Ele trote h ic l Commis io (IEC) is th le din glo al org niz tio th t pr ep res a d p bls e

Internatio al Sta d r ds for al ele tri al ele tr onic a d relate te h olo ie

Abo t IEC p blc tio s

Th te h ic l c nte t of IEC p blc tio s is k pt u d r c n ta t r eview b th IEC Ple s ma e s re th t y u h v th

late t e itio ,a c rr ig n a or a ame dme t mig t h v b e p bls e

IEC Cat alo ue - webst ore.e ch/ cat alo ue

Th st an -alo e a plc t io for c n ultin th e tire

biblo ra hic l informat io o IEC Intern tio al Sta d rd ,

Te h ic l Sp cific tio s, Te h ic l R ep rts a d oth r

d c me ts A v aia le for P , Ma OS, A ndroid Ta let s a d

iPa

IEC p blc t i ns s arch - www ie ch/ se rch u

Th a v an e s arc e a le t o fin IEC p blc t io s b a

variety of crit eria (efere c n mb r, t ext, t ec nic l

c mmitt e,…) It als gives informatio o projec t s, re la e

a d wit hdrawn p blc tio s

IEC Just P blshed - webst ore.e ch/ just pu lshed

St ay u to d te o al n w IEC p blc tio s Ju t Pu ls e

d t ais al n w p blc t io s rele s d A v aia le o ln a d

als o c a mo t h b emai

Ele t ro edia - www ele t ro edia.org

Th world's le din o ln dic t io ary of elec t ro ic a d

ele t ric l terms c nt ainin 2 0 0 terms a d d finitio s in

En ls a d Fre c , wit h e uiv ale t t erms in 16 a dit io al

la g a e Als k nown a t he Intern t io al Ele trote h ic l

Vo a ulary (IEV ) o ln

IEC Glos ar y - st d.e ch/ glos ary

6 0 0 elec t rot ec nic l t ermin lo y e t rie in En ls a d

Fre c e t ra te fom t he Terms a d Definitio s cla s of

IEC p blc tio s is u d sin e 2 0 Some e t rie h v e b e

c le te fo m e rler p blc t io s of IEC TC 3 , 7 , 8 a d

CISPR

IEC Cust omer Servic Cent re - webst ore.ec ch/ csc

If y ou wis to giv e u your fe d a k o t his p blc tio or

n e furt her a sista c , ple s c nta t t he Cu tomer Serv ic

Ce t re:c c@ie c

IEC TR 62453- 52- 31

Edit io 1.0 2 17-0

Field device t ool (FDT) int er ace specificat ion –

Part 52-31: Communicat ion implement at ion for common language

inf ast ruct ure – IEC 61784 CP 3/1 and CP 3/ 2

CONTENTS

FOREWORD 6

INTRODUCTION 8

1 Sco e 9

2 Normative ref eren es 9

3 Terms, definition , s mb ls, a breviated terms and con ention 10 3.1 Terms an definition 10 3.2 Symb ls an a breviated terms 10 3.3 Con ention 10 3.3.1 Datatyp names an ref eren es to datatyp s 10 3.3.2 Voca ulary for req irements 10 3.3 3 Use of UML 1

0 4 Bu category 10 5 Ac es to in tan e an device data 1

5.1 General 1

5.2 IO sig als provided by DTM 1

5.3 Data inter aces 1

5.3.1 General 1

5.3.2 Ma pin of PROFIBUS datatyp s to FDT datatyp s 1

5.3 3 SemanticInfo 1

2 6 Protocol sp cif i b haviour 14 6.1 PROFIBUS device model 14 6.2 Con g ration and p rameterization of PROFIBUS devices 15 6.2.1 General 1

5 6.2.2 Monol thic DTM for a mod lar PROFIBUS device 16 6.2.3 Comp site DTM f or a mod lar PROFIBUS device 16 6.3 Sup ort for DP-V0 config ration 17 6.4 PROFIBUS slaves o eratin without a clas 1 PROFIBUS master 17 6.5 PROFIBUS- elated inf ormation of a slave DTM 17 6.5.1 General 17 6.5.2 PROFIBUS Network Data (PND) 18 6.5.3 GSD Information 2

6.5.4 Proces Data Items 2

7 Protocol sp cif i u age of general datatyp s 2

7.1 General datatyp s 2

7.2 Protocol sp cif i han l n of the datatyp STRING 2

8 Network management datatyp s 2

8.1 General 2

8.2 Con g ration 2

8.3 Proces Data Items 2

8.4 Parameterization 2

9 Commu ication datatyp s 2

9.1 General 2

9.2 Prof ibu Ab rtMes age 2

9.3 DP-V0 Commu ication 2

9.3.1 General 2

9.3.3 Dpv0Con ectResp n e 31

9.3.4 Dpv0Dis on ectReq est 3

9.3.5 Dpv0Dis on ectResp n e 3

9.3.6 Dpv0Tran actionReq est 3

9.3.7 Dpv0Tran actionResp n e 3

9.4 DP-V1 Commu ication 4

9.4.1 Dpv1Con ectReq est 4

9.4.2 Dpv1Con ectResp n e 4

9.4.3 Dpv1Dis on ectReq est 4

9.4.4 Dpv1Dis on ectResp n e 4

9.4.5 Dpv1Tran actionReq est 4

9.4.6 Dpv1Tran actionResp n e 4

9.5 Er or information provided by Commu ication Chan el 4

10 Datatyp s f or proces data inf ormation 4

10.1 General 4

10.2 Prof ibu IOSig alInf o 4

1 Device identification 5

1 1 General 5

1 2 Prof ibu DeviceScanInfo datatyp 51

1 2.1 General 51

1 2.2 Datatyp s derived fom Prof ibu BaseScanInf o 5

1 3 Prof ibu DeviceIdentInf o datatyp 5

1 3.1 General 5

1 3.2 Datatyp s derived fom Profibu BaseIdentInfo 5

1 4 Ma pin of Inf ormation Source 5

Bibl ogra h 6

Fig re 1 – Part 5 -31 of the IEC 6 4 3 series

8 Fig re 2 – FDT PROFIBUS Device Model 15 Fig re 3 – Prof ibu NetworkData 2

Fig re 4 – Prof ibu Ab rtMes age 2

Fig re 5 – Dpv0Con ectReq est 31

Fig re 6 – Dpv0Con ectRespon e 31

Fig re 7 – Dpv0Dis on ectReq est 3

Fig re 8 – Dpv0Dis on ectRespon e 3

Fig re 9 – Dpv0Re dCon g rationDataReq est 3

Fig re 10 – Dpv0Re dDiag osisDataReq est 3

Fig re 1 – Dpv0Re dInputDataReq est 3

Fig re 12 – Dpv0Re dOutputDataReq est 3

Fig re 13 – Dpv0Re dUserParameterReq est 3

Fig re 14 – Dpv0WriteOutputDataReq est 3

Fig re 15 – Dpv0WriteUserParameterReq est 3

Fig re 16 – Dpv0Re dConfig rationDataResp n e 3

Fig re 17 – Dpv0Re dDiag osisDataResp n e 3

Fig re 18 – Dpv0Re dInputDataResp n e 3

Fig re 2 – Dpv0Re dUserParameterResp n e 41

Fig re 21 – Dpv0WriteOutputDataResp n e 41

Fig re 2 – Dpv0WriteUserParameterResp n e 4

Fig re 2 – Dpv1Con ectReq est 4

Fig re 2 – Dpv1Con ectResp n e 4

Fig re 2 – Dpv1Dis on ectReq est 4

Fig re 2 – Dpv1Dis on ectResp n e 4

Fig re 2 – Dpv1Re dReq est 4

Fig re 2 – Dpv1WriteReq est 4

Fig re 2 – Dpv1Re dResp n e 4

Fig re 3 – Dpv1WriteResp n e 4

Fig re 31 – Profibu IOSig alInf o 5

Fig re 3 – Profibu DeviceScanInf o 51

Fig re 3 – Datatyp s derived f rom Prof ibu BaseScanInfo 5

Fig re 3 – Profibu DeviceIdentInf o 5

Fig re 3 – Datatyp s derived f rom Prof ibu BaseIdentInf o 5

Ta le 1 – Ma pin of datatyp s 1

Ta le 2 – Usage of general datatyp s 12 Ta le 3 – PROFIBUS Network Inf ormation 19 Ta le 4 – Protocol sp cific u age of general datatyp s 2

Ta le 5 – Profibu Ab rtMes age datatyp 2

Ta le 6 – Avaia i ty of services for Master Clas 1 (C1) 3

Ta le 7 – Avaia i ty of services for Master Clas 2 (C2) 3

Ta le 8 – Dpv0Con ectReq est datatyp 31

Ta le 9 – Dpv0Con ectResp n e datatyp 3

Ta le 10 – Dpv0Dis on ectReq est datatyp 3

Ta le 1 – Dpv0Dis on ectResp n e datatyp 3

Ta le 12 – Dpv0Re dCon g rationDataReq est datatyp 3

Ta le 13 – Dpv0Re dDiag osisDataReq est datatyp 3

Ta le 14 – Dpv0Re dInputDataReq est datatyp 3

Ta le 15 – Dpv0Re dOutputDataRequest datatyp 3

Ta le 16 – Dpv0Re dUserParameterReq est datatyp 3

Ta le 17 – Dpv0WriteOutputDataReq est datatyp 3

Ta le 18 – Dpv0WriteUserParameterReq est datatyp 3

Ta le 19 – Dpv0Re dCon g rationDataResp n e datatyp 3

Ta le 2 – Dpv0Re dDiag osisDataResp n e datatyp 3

Ta le 21 – Dpv0Re dInputDataResp n e datatype 4

Ta le 2 – Dpv0Re dOutputDataResp n e datatyp 4

Ta le 2 – Dpv0Re dUserParameterResp n e datatyp 41

Ta le 2 – Dpv0WriteOutputDataResp n e datatyp 4

Ta le 2 – Dpv0WriteUserParameterResp n e datatyp 4

Ta le 2 – Dpv1Con ectResp n e datatyp 4

Ta le 2 – Dpv1Dis on ectReq est datatyp 4

Ta le 2 – Dpv1Dis on ectResp n e datatyp 4

Ta le 3 – Dpv1Re dReq est datatyp 4

Ta le 31 – Dpv1WriteReq est datatyp 4

Ta le 3 – Dpv1Re dResp n e datatyp 4

Ta le 3 – Dpv1WriteResp n e datatyp 4

Ta le 3 – Profibu IOSig alInfo datatyp 5

Ta le 3 – Profibu DeviceScanInf o datatyp 5

Ta le 3 – Datatyp s derived f rom Prof ibu BaseScanInfo 5

Ta le 3 – Profibu DeviceIdentInfo datatyp 5

Ta le 3 – Datatyp s derived f rom Prof ibu BaseIdentInf o 5

Ta le 3 – Profi e sp cific ma pin of identity information 5

INTERNATIONAL ELECTROTECHNICAL COMMISSION

_

Part 52-31: Communication implementation

for common language infrastructure –

IEC 61784 CP 3/1 and CP 3/2

1 Th Intern tio al Ele trote h ic l Commis io (IEC) is a worldwid org niz tio for sta d rdiz tio c mprisin

al n tio al ele trote h ic l c mmite s (IEC Natio al Commite s) Th o je t of IEC is to promote

intern tio al c -o eratio o al q e tio s c n ernin sta d rdiz tio in th ele tric l a d ele tro ic field To

this e d a d in a ditio to oth r a tivitie , IEC p bls e Intern tio al Sta d rd , Te h ic l Sp cif i atio s,

Te h ic l Re orts, Pu lcly Av ia le Sp cif i atio s (P S) a d Guid s (h re fter ref ere to a “IEC

Pu lc tio (s)”) Th ir pre aratio is e tru te to te h ic l c mmite s; a y IEC Natio al Commite intere te

in th s bje t d alt with ma p rticip te in this pre aratory work Intern tio al g v rnme tal a d n n

-g v rnme tal org niz tio s laisin with th IEC als p rticip te in this pre aratio IEC c la orate clo ely

with th Intern tio al Org niz tio f or Sta d rdiz tio (ISO) in a c rd n e with c n itio s d termin d b

a re me t b twe n th two org niz tio s

2) Th formal d cisio s or a re me ts of IEC o te h ic l maters e pre s, a n arly a p s ible, a intern tio al

c n e s s of o inio o th rele a t s bje ts sin e e c te h ic l c mmite h s re re e tatio fom al

intere te IEC Natio al Commite s

3) IEC Pu lc tio s h v th f orm of re omme d tio s f or intern tio al u e a d are a c pte b IEC Natio al

Commite s in th t s n e Whie al re s n ble eff orts are ma e to e s re th t th te h ic l c nte t of IEC

Pu lc tio s is a c rate, IEC c n ot b h ld re p n ible f or th wa in whic th y are u e or f or a y

misinterpretatio b a y e d u er

4) In ord r to promote intern tio al u if ormity, IEC Natio al Commite s u d rta e to a ply IEC Pu lc tio s

tra s are tly to th ma imum e te t p s ible in th ir n tio al a d re io al p blc tio s An div rg n e

b twe n a y IEC Pu lc tio a d th c re p n in n tio al or re io al p blc tio s al b cle rly in ic te in

th later

5) IEC its lf d e n t pro id a y ate tatio of c nformity In e e d nt c rtific tio b die pro id c nf ormity

a s s me t s rvic s a d, in s me are s, a c s to IEC mark of c nformity IEC is n t re p n ible for a y

s rvic s c rie o t b in e e d nt c rtific tio b die

6) Al u ers s o ld e s re th t th y h v th late t e itio of this p blc tio

7) No la i ty s al ata h to IEC or its dire tors, emplo e s, s rv nts or a e ts in lu in in ivid al e p rts a d

memb rs of its te h ic l c mmite s a d IEC Natio al Commite s for a y p rs n l injury, pro erty d ma e or

oth r d ma e of a y n ture wh ts e er, wh th r dire t or in ire t, or f or c sts (in lu in le al f ee ) a d

e p n e arisin o t of th p blc tio , u e of, or rela c u o , this IEC Pu lc tio or a y oth r IEC

The main tas of IEC tec nical commit e s is to pre are International Stan ard However, a

tec nical commite may pro ose the publ cation of a tec nical re ort when it has col ected

data of a diff erent kin fom that whic is normal y publs ed as an International Stan ard, for

example "state of the art"

IEC TR 6 4 3-5 -31, whic is a tec nical re ort, has b en pre ared by s bcommit e 6 E:

Devices an integration in enterprise s stems, of IEC tec nical commit e 6 : In u trial

-proces me s rement, control an automation

Eac p rt of the IEC 6 4 3-5 -x series is inten ed to b re d in conju ction with its

cor esp n in p rt in the IEC 6 4 3-3x series The cor esp n in p rt for this doc ment is

The text of this tec nical re ort is b sed on the f ol owin doc ments:

En uiry draft Re ort o v tin

Ful information on the votin for the a proval of this tec nical re ort can b f ou d in the

re ort on votin in icated in the a ove ta le

This doc ment has b en drafted in ac ordan e with the ISO/IEC Directives, Part 2

The lst of al p rts of the IEC 6 4 3 series, u der the general title Fiel d de ic tool (FDT)

intera e sp cific tio , can b fou d on the IEC we site

The commite has decided that the contents of this doc ment wi remain u c an ed u ti the

sta i ty date in icated on the IEC we site u der "ht p:/ we store.iec.c " in the data related to

the sp cific doc ment At this date, the doc ment wi b

• with rawn,

• re laced by a revised edition, or

A bi n ual version of this publ cation may b is ued at a later date

IMPORTANT – The 'colour inside' logo on th cov r pa e of this publ c tion indic te

that it contains colours whic are consid red to be us f ul f or the cor e t

und rsta din of its conte ts Us rs s ould th ref ore print this doc me t using a

colour printer

This p rt of IEC 6 4 3 is an interace sp cification for develo ers of Field Device To l (FDT)

comp nents f or fu ction control an data ac es within a cl ent server arc itecture The

sp cification is a res lt of an analy is an desig proces to develo stan ard interf aces to

f aci tate the develo ment of servers an cl ents by multiple ven ors that ne d to intero erate

se mles ly

With the integration of f ieldbu es into control s stems, there are a few other tas s whic ne d

to b p rormed In ad ition to f ieldbu - an device-sp cific to ls, there is a ne d to integrate

these to ls into hig er level s stem-wide plan in or en ine rin to ls In p rtic lar, for u e

in exten ive an heterogene u control s stems, typical y in the are of the proces in u try,

the u ambig ou definition of en ine rin interf aces that are e s to u e f or al those

in olved is of gre t imp rtan e

A device-sp cif i software comp nent, cal ed Device Typ Manager (DTM), is s p led by the

f ield device man facturer with its device The DTM is integrated into en ine rin to ls via the

FDT interf aces defined in this sp cif i ation The a pro c to integration is in general o en for

al kin of fieldbu es an th s me ts the req irements f or integratin diff erent kin s of

devices into heterogene u control s stems

Fig re 1 s ows how this p rt of the IEC 6 4 3-5 -x series is al g ed in the stru ture of the

This p rt of the IEC 6 4 3-5 -x series, whic is a Tec nical Re ort, provides information for

integratin the PROFIBUS

The folowin doc ments are ref er ed to in the text in s c a way that some or al of their

content con titutes req irements of this doc ment For dated referen es, only the edition

cited a pl es For u dated referen es, the latest edition of the referen ed doc ment (in lu in

an amen ments) a pl es

IEC 61 31-3:2 0 , P ro ramma l e c nt rol l ers – Part 3: P ro ramming la g a es

IEC 61 5 (al p rts), Ind ustrial c mmu ic t io n tworks – Fieldbus sp cifications

IEC 61 5 -6-3:2 14, Ind ustrial c mmu ic t ion n tworks – Fiel db s sp cificat ions – P art 6-3:

Ap l i at ion layer protoc l sp cific t ion – Type 3 el eme ts

IEC 617 4-1:2 14, Industrial c mmu ic t ion n tworks – P rofil es – P art 1: Field bus profil s

IEC 6 4 3-1:2 16, F iel d devic tool (FDT) intera e sp cific tion – Part 1: Ov rview a d

g id an e

IEC 6 4 3-2:2 16, Fiel d devic tool (FDT) int era e sp cific tion – Part 2: Co c pts a d

detail ed description

IEC TR 6 4 3-4 :2 16, Field d evic tool (FDT) intera e sp cific tion – Part 4 : Object mod el

int egration profile – Commo l an u g infastru ture

IEC 6 4 3-3 3-1:2 0 , Field d evic tool (FDT) intera e sp cific tion – Part 3 3-1:

IEC 6 45 -3 3-1:2 0 /AMD1:2 16

_ _ _ _ _ _

1

PR FIBUS™ is a tra e n me of th n n-profit org niz tio PR FIBUS Nutz rorg nis tio e.V (P O) This

informatio is giv n for th c n e ie c of u ers of this d c me t a d d e n t c n titute a e d rs me t b

IEC of th tra e n me h ld r or a y of its pro u ts Compla c to this d c me t d e n t re uire u e of th

3 Terms, def initions, symbols, a breviated terms and conv ntions

• IEC Electro edia: avai a le at htp:/www.electro edia.org/

• ISO Onl ne browsin platform: avai a le at ht p:/ www.iso.org/o p

3.2 Symbols a d ab re iate terms

For the purp ses of this doc ment, the s mb ls an a breviation given in IEC 6 4 3-1,

IEC 6 4 3-2, IEC 6 4 3-3 3-1, an IEC TR 6 4 3-4 a ply

3.3 Conv ntion

3.3.1 Datatype name a d refere c s to datatype

IEC TR 6 4 3-2:2 16, Clau e A.1

3.3.2 Voc bulary f or re uireme ts

The fol owin expres ion are u ed when sp cifyin req irements

Usage of “s al ” or “man atory” No ex e tion al owed

Usage of “s ould” or

“recommen ed”

Stron recommen ation It may make sen e in sp cial

ex e tional cases to dif fer f rom the des rib d b haviour

Usage of “con itional” Fu ction or b haviour s al b provided, de en in on

defined con ition

Usage of “can” or “o tional” Fu ction or b haviour may b provided, de en in on

defined con ition

3.3.3 Us of UML

The f i ures in this doc ment are u in UML notation as defined in An ex A of

IEC 6 4 3-1:2 16

IEC 617 4 CP 3/1 an IEC 617 4 CP 3/2 protocols are identif ied in the atribute ProtocolId of

the Bu Category element by the identifiers, as sp cif ied in IEC 6 4 3-3 3-1

The s p orted Ph sicalL yer are identified by the Identifier values as sp cified in

IEC 6 4 3-3 3-1

The s p orted Data in L yer are identified by the Identifier values as sp cif ied in

IEC 6 4 3-3 3-1

5 A cces to instanc and device data

The minimum set of data provided by a Device DTM s al b :

– Al device p rameters of the Ph sical Bloc an Out value of the Fu ction Bloc s s al b

exp sed via the data interf aces (PROFIBUS PA devices)

– Al proces values avai a le f or the device s al b model ed as Proces Data in lu in the

ran es an s al n , if a pl ca le

– Al network config ration related p rameters s al b exp sed in NetworkData (se

Clau e 8)

5.2 IO sig als provide by DTM

A DTM s al provide IO sig al information for the device u in the IProces Data inter ace

The IO sig als des rib datatyp an ad res p rameters of proces data as detai ed in

5.3.2 Mapping of PROFIBUS datatype to FDT datatype

PROFIBUS u es datatyp s as sp cified in IEC 61 5 for the tran mis ion on the f ieldbu

The FDT interf aces IDeviceData an I n tan eData u e NET datatyp s, whi e PLC

a pl cation u e datatypes defined in IEC 61 31-3 Hen e a ma pin b twe n these thre

typ s stems is defined in Ta le 1

Table 1 – Mappin of datatype

Bit inf ormatio

Numeric inf ormatio with an with ut sig

Printable chara ters (e.g text)

PR FIB S dataty e FDT dataty e IEC 61 31 dataty e

Time inf ormatio

TimeDif fere c with ut Date

The FDT datatyp s are u ed by the <Re d> an <Write method in the interf aces

I n tan eData an IDeviceData

5.3.3 Sema ticInf o

The identifier in SemanticId s al b u iq e an alway referen e the same element This

me n the semantic inf ormation s al b the same whenever the same data is referen ed By

u in this atribute e.g a Frame Ap lcation is a le to get the inf ormation regardin the

me nin an u age of a sin le data stru ture

Table 2 – Us ge of ge eral datatype

Sema ticInfo.Re dParameterAd re s

Sema ticInfo.WriteParameterAd re s

For PR FIBUS, Re dParameterAd re s a d WriteParameterAd re s

are alwa s id ntic l Th a dre s strin s al b c n tru te a c rdin

to th rule of th FDT Sema ticId

PR FIBUS Parameter Ad re s:

Th pro erty ‘Ad re s’ folows th diff ere t d vic mo els th t are

d fin d for PR FIBUS d vic s FDT c re tly s p orts th f olowin

Atrib te De criptio f or us

PR FIBUS PA

Th d vic is re re e te b a d vic ma a eme t stru ture a d a

n mb r of blo k th t pro id dif fere t fu ctio alty (p y ic l blo k,

fu ctio blo k,tra s u er blo k) Th blo k arema p d to slot

a dre s s, b t this ma pin ma v ry d p n in o th d vic ty e

Th Ad re s pro erty is A Ix SLOTy IN EXz

Ac ordin to th PR FIdriv profie[5], a d vic (driv u it) ma b

c mp s d b a n mb r ( ma y) of driv o je ts (DOs) Th DOs ma

h v diff ere t ty e Ea h DO is u iq ely id ntif i ble a d ma a e its

own p rameters Ea h p rameter c n b u iq ely id ntif i d b its

n mb r (P U) Ea h DO h s its own n mb r s a e

A p rameter ma c ntain simple d ta or c mp s d d ta (e.g ara s)

Th d ta of th d vic are a c s ible via a p rameter c a n l (n rmaly

d -id – Driv Obje t ID

p u – ParameterNumb r

x , y , z , d -id, p u are b s d o d cimal format with ut le din ‘0’

Sema ticInfo.Ap lc tio Domain/

Sema ticInfo.Sema ticId

Th Sema ticIDs for PR FIBUS f olow th dif fere t d vic mo els th t

are d f i e f or PR FIBUS d vic s FDT c re tly s p orts th f olowin

Th Ap lc tio Domain is: FDT PR FIBUS D V1

Th d vic mo el is b s d o d vic s th t are c mp s d of slots,

wh re s slots d n t h v to re re e t p y ic l o je ts.Th d ta th t

is c ntain d in th slots are a dre s ble via In e e This d ta ma b

v ria le or c mp s d blo k of d ta

Th Sema ticId f or d vic s n t b s d o a pro le is dire tly b s d o

th PR FIBUS a dre s informatio :

Th Sema ticId is: A Ix SLOTy N EXz

x – A

y – Slot

z – In e

x , y , z are b s d o d cimal format with ut le din ‘0’

Atrib te De criptio f or us

PR FIBUS PA

Th Ap lc tio Domain is: FDT PR FIBUS P

Th d vic is re re e te b a d vic ma a eme t stru ture a d a

n mb r of blo k th t pro id dif f ere t fu ctio alty (p y ic l blo k,

fu ctio blo k,tra s u er blo k) Th blo k arema p d to slot

a dre s s, b t this ma pin ma v ry d p n in o th d vic ty e

Sin e th d vic mo el is b s d o blo k ,th Sema ticId als are

– stru ture p rameters s al b c mbin d with a ‘ ;

– s a e within th pro le d finitio s al b e c a g d with a

Sema ticInfo.Ap lc tio Domain/

Sema ticInfo.Sema ticId)

PR FIdrive

Th Ap lc tio Domain is: FDT PR FIBUS PROFIDRIVE

Ac ordin to th PR FIdriv profie, a d vic (driv u it) ma b

c mp s d b a n mb r ( ma y) of driv o je ts (DOs) Th DOs ma

h v diff ere t ty e Ea h DO is u iq ely id ntif i ble a dma a e its

own p rameters Ea h p rameter c n b u iq ely id ntif i d b its

n mb r (P U) Ea h DO h s its own n mb r s a e

A p rameter ma c ntain simple d ta or c mp s d d ta (e.g ara s)

Th d ta of th d vic are a c s ible via a p rameter c a n l (slot 0,

in e 4 )

Th Sema ticId is: DOd -id.P Up u

d -id – Driv Obje t ID

p u – ParameterNumb r

d -id, p u are b s d o d cimal f ormat with ut le din ‘0’

Figure 2 – FDT PROFIBUS De ic Mod l

DTMs f or PROFIBUS devices s al provide information a out their I/O data to provide

en ine rin s stems k owled e to ac es s c data without the u e of the DTMs

6.2 Configuration a d parameterization of PROFIBUS de ic s

In a GSD-b sed config ration to l, the u er defines the config ration an sets the a pro riate

p rameters for the mod les The config ration to l cre tes the config ration strin an the

p rameter strin that are u ed to set up the slave pro erly

With FDT the config ration an p rameterization of the devices is no lon er exec ted only by

a central piece of software; it moved p rtly into the DTMs A Device DTM is resp n ible for

providin config ration an p rameterization information for a PROFIBUS master that puts

the PROFIBUS slaves in o eration

A Device DTM is u ed to adju t a field device to its sp cif i a pl cation Within PROFIBUS,

IEC

Cla sic l View of PROFIBUS d vic

PROFIBUS notation f om a d vic DTMs p int of view

– Commu ication p rameterization: User Prm Data (u ed in the PROFIBUS service

Set_Prm for set in up the c clc commu ication an the sp cific b haviour of the device);

– Config ration data: Cfg Data (u ed in the PROFIBUS service Ch _Cf g for def i ition of the

format an len th of the input output data that are tran mit ed within c cl c

commu ication);

– Ap l cation p rameterization: a plcation sp cific p rameters ( ran mit ed via ac cl c

re d/write PROFIBUS services)

The a pl cation p rameterization tran mit ed via ac cl c commu ication is not in the s o e of

this doc ment The p rameter data tran mit ed for this purp se is device sp cific Only the

commu ication services that can b u ed by Device DTMs for p rormin s c device sp cific

p rameterization are defined Within this doc ment the term p rameterization re resents

commu ication p rameterization (Set_Prm)

6.2.2 Monol thic DTM f or a modular PROFIBUS de ic

A monol thic DTM is one sin le DTM that re resents the complete device with its Bu

Inter ace Mod le (BIM) an its I/O mod les In general, s c a DTM of fers a config ration

u er interace (presentation o ject that al ows definition of the u ed BIM an mod le typ s

Not al PROFIBUS devices req ire a config ration u er interace That is wh not al DTMs

provide the con g ration fu ction (Ap lcationID: Config ration) This is val d only for non

-mod lar PROFIBUS devices if the User Prm Data can ot b c an ed

The con g ration dialog s al alow c an in the data only in off line mode if the data set can

b loc ed

6.2.3 Composite DTM f or a modular PROFIBUS de ic

Se arate DTMs re resent the BIM (Comp site Device DTM) an the p rtic lar I/O mod les

(Mod le DTMs) The eff ort develo in s c a mod lar DTM is normal y hig er than in the

case of a monol thic DTM, b cau e:

– a private protocol s al b implemented b twe n BIM an I/O mod les to en ure that only

a Mod le DTM can b ad ed to the BIM DTM This req ires an own FDT protocol ID an

the ada tation/cre tion of FDT commu ication datatyp s

Implementin a Mod lar DTM res lts in the f ol owin ad antages:

– the project to ology re resents the device stru ture,

– the u er is a le to ac es mod le- elated information directly as a fu ction of the Mod le

DTM,

– IEC 6 4 3 def i es a mec anism to identify DTMs With these mec anisms it is p s ible to

provide s p ort f or s an in the mod les b low the BIM an generate the to olog

automatical y,

– s p ortin a new typ of BIM or I/O mod le req ires an ad itional DTM “only” an do s

not aff ect existin comp nents This may res lt in red ced test ef fort that can also simplfy

the certification proces

The config ration data to set up the PROFIBUS config ration of a mod lar PROFIBUS device

s al b provided by the Device DTM re resentin the BIM This config ration data may b

generated fom inf ormation of the in tantiated Mod le DTMs an by u in a config ration

dialog

Mod lar DTMs can b provided f or mod lar devices (e.g a plant o erator may ad /remove

mod les) Monol thic DTMs can b u ed to re resent devices that s ow no mod larity (e.g

6.3 Support for DP-V0 conf iguration

A PROFIBUS slave u ual y commu icates c cl cal y via PROFIBUS DP-V0 with a clas 1

master (DPM1) In ad ition to this the slave may s p ort DP-V1 commu ication This s ould

b in icated by setin the Slave lagDpv1Slave pro erty (se 6.5.2.2.2 Slave bu p rameter

set to true

A Gateway DTM f or a PROFIBUS slave do s not have to provide DP-V0 commu ication An

example is a remote I/O s stem with HART

2

mod les It may have a Gateway DTM that

req ires the DP-V1 protocol an provides the HART protocol This ena les HART Device

DTMs to commu icate with their devices via the Gateway DTM an via a Commu ication DTM

f or DP-V1 Folowin the sp cif i ation the Gateway DTM del vers proces data items f or b th

protocols DP-V1 an HART The ProtocolId is a memb r of NetworkDataInfo datatyp

The Proces Data Info of a Device DTM s al contain data items for DP-V0 in lu in al

information to al ow integration into the control s stem (e.g Dpv0IOSig alInf o of the I/O value

if avai a le)

6.4 PROFIBUS sla e operating without a cla s 1 PROFIBUS ma ter

In most cases, a PROFIBUS slave is config red an p rameterized by a PROFIBUS clas 1

master device So a ru nin master device in the network is required

Some slaves (marked via Slave lagDpv1Slave) are a le to al ow ac cl c commu ication

without c cl c master to slave commu ication Esp cial y in the case of gateway fu ctionalty

this al ows the p rameterization of ield devices con ected to them by u in a clas 2 master

So in trument sp cial sts are a le to work with f ield devices also in case the control er is not

yet workin

If a master starts commu ication, these devices start to detect bu sp ed to re ct pro erly

This may take some time A commu ication DTM or gateway DTM s al take this into ac ou t

an adju t internal time uts ac ordin ly

In the fol owin , two examples f or pro lems regardin detectin devices are des rib d that a

u er may ke p in min when workin with s c devices

EX MPLE 1:

Th u er p rorms a n twork s a Th Commu ic tio DTM trie to re d dia n stic d ta via a

Dp 0Re dDia n sis Re u st b t d e n t re eiv a re p n e Th d vic is n t d te te b th Commu ic tio

DTM This o c rs mo tly wh n th d vic h s a low PR FIBUS a dre s Th re s n is th t th d vic h s n t

c mplete b s s e d d te tio wh n it wa a k d for its dia n stic d ta Th work ro n is to a sig th s

d vic s a hig er PR FIBUS a dre s

EX MPLE 2:

Th u er trie to c n e t a field d vic ln e to a g tewa th t s p orts D -V1 with ut a ru nin c clc ma ter

This c n le d to a eror me s g b c u e th g tewa d vic h s n t c mplete b s s e d d te tio wh n it is

a k d for a c n e tio Co s q e tly, th u er h s to try to c n e t a ain This h p e s o ly in v ry rare

situ tio s

6.5 PROFIBUS-relate information of a sla e DTM

The information u ed by a c clc master device to set up the PROFIBUS network pro erly an

al ow c cl c commu ication b twe n control s stem an slave devices s al b provided by a

DTM in

_ _ _ _ _ _

2

H RT ® is th tra e n me of a pro u t s p le b H RT Commu ic tio Fo n atio This inf ormatio is giv n

f or c n e ie c of u ers of this d c me t a d d e n t c n titute a e d rs me t b IEC of th pro u t

– PROFIBUS Network Data,

– GSD inf ormation,

– Proces data items

A DTM of a PROFIBUS slave s al del ver these p rts of PROFIBUS- elated information to get

integrated into a Frame Ap l cation In the next s bclau es, a more detai ed des ription is

given on how to generate an how to provide this information The actual inf ormation de en s

on the kin of DTM (se 6.2 Config ration an p rameterization of PROFIBUS devices)

6.5.2 PROFIBUS Network Data (PND)

6.5.2.1 PND introd ction

The PND of a sin le DTM in tan e des rib s the actual p rameter an config ration data of

the cor esp n in PROFIBUS slave Eac DTM re resentin a PROFIBUS slave device s al

provide PROFIBUS Network Data The PND is the PROFIBUS sp cific NetworkDataInf o

datatyp This inf ormation is o tained by cal n the service GetNetworkDataInfo

The PND in lu es inf ormation a out the con g ration an the p rameters f or initial zation of

the slave The PND is provided by the DTM an is req ired in order to generate the bu

master config ration

The PND contain data whic mig t b c an ed d rin master config ration That me n that

the PND may b tran fer ed b c to the slave DTM by cal n SetNetworkData A Slave DTM

s al ac e t the new information an recompute the config ration/internal p rameters to

matc the new PND

The Slave DTM s al c ec whether the new values are ac ordin to the ca a i ties of the

device The cal to SetNetworkData s al b refu ed (by throwin an ex e tion of typ

Fdt.FdtIn al dValueEx e tion) if the device can ot han le the new values

6.5.2.2 Cre ting the PND

The PND may b generated fom the GSD information of a PROFIBUS device This s bclau e

explain the me nin of the in ivid al elements of the PND in detai The explanation

referen e the PROFIBUS sp cif i ation an u e the GSD keyword

6.5.2.2.2 Sla e bus parameter s t

Al values are provided by the Slave DTM It is the resp n ibi ty of the Slave DTM to b

comp tible with the Slave GSD The Master DTM can overwrite some of these initial values

sent by the Slave DTM if they de en on the ca a i ties of the master

EX MPLE:

Within th GSD f ile, it is state th t a d vic s p orts th Fre z Mo e b th k yword “Fre z _Mo e_s p ” Th

ma ter s ts th v lu “PrmDataFre z Mo e” within th Sla e Bu Parameter Set b c u e o ly th ma ter k ows

wh th r it s p orts this mo e

Ta le 3 explain whic comp nent is the source of the p rameter values ( Information source

” Some of the values can b c an ed by the s stem or by u er interaction If p s ible, the

default values for the p rameters are defined ( Default Value”

Table 3 – PROFIBUS Network Inf ormation

Path refere c to GSD f ile

f als – ma ter s al a k owle g alarms via SA 51

tru – ma ter s al a k owle g alarms via SA 5

f als – D sla eCFG d ta of EN 5 17

tru – D sla e CFG d ta of DP-V1

f als – sla e d e n t s p ort D -V1

tru – sla e d e s p ort D -V1

f als – n p bls er s p ort

tru – DP sla e s p orts p bls er f un tio alty

fals – pro e s th a to cle r fu ctio

tru – ig ore th a to cle r f un tio

Ma AlarmL n Byte L n th of th alarm stru ture, s e IEC 61 5 -6-3:2 14, Ta le 5

Sla e DTM, Co ditio s: On of GSD k yword :-

Dia n stic_Alarm_s p – Pro e s_Alarm_s p –

Pul_Plu _Alarm_s p – Statu _Alarm_s p – Up ata_Alarm_s p –

Ma ufa turer_ p cific_Alarm_s p OR – Alarm_ y e_Mo e_s p

Is c lc late o th b s of th diff ere t GSD

v lu s

Ma Ch n elData e Byte Sla e DTM: This f i ld d fin s h w mu h d ta c n b tra sfer e

b twe n sla e a d ma ter In this c s th ma imum of th s v lu s

s al b c lc late a d s t b th sla e DTM Rule for c lc latio :

Ma _Data_L n or C1_Ma _Data_L n plu 4 Byte (Fu ctio Num,

Slot_Numb r, L n th)

Valu within Sla e GSD

PrmDataWdOn Bo le n Ma ter d fin s th t watc d g is u e or n t If watc d g is e a le ,

th ma ter als s al s t WD_ a t_1 a d WD_ a t_2

0

PrmDataFre z Mo e Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Fre z _Mo e_s p within GSD

PrmDataSy cMo e Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Sy c_Mo e_s p within GSD

PrmDataGro pId nt Byte In ic te to wh t gro p th d vic b lo g It is s t b th ma ter 0 (n t a sig e to a y gro p)

f als – watc d g time b s is 10 ms

tru – watc d g time b s is 1 ms

PrmDataFaiSafeRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is e p cte to s p ort

this f eature

Fai_ afe_re uire within GSD

tru – ma ter s al s p ort fai s fe mo e

PrmDataCh c Cf gMo e Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Ch c _Cf g_Mo e within GSD

PrmDataUp ateAlarmRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is re uire to s p ort

this f eature

Up ate_Alarm_re uire within GSD

tru – ma ter s al s p ort u d te alarm

fals – u d te alarm is o tio al

If s t to tru , th n PrmDataUp ateAlarm s al b s t to tru to

PrmDataUp ateAlarm Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Up ate_Alarm_s p within GSD

PrmDataStatu AlarmRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is re uire to s p ort

this f eature

Statu _Alarm_re uire within GSD

tru – ma ter s al s p ort statu alarm

fals – statu alarm is o tio al

If s t to tru , th n PrmDataStatu Alarm s al b s t to tru to

PrmDataStatu Alarm Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Statu _Alarm_s p within GSD

PrmDataMa ufa turerSp cificAlarmR

tru – ma ter s al s p ort ma ufa turer s e if i alarm

fals – ma uf acturer s e if i alarm is o tio al

If s t to tru , th n PrmDataMa ufa turerSp cificAlarm s al b s t to

tru to

PrmDataMa ufa turerSp cificAlarm Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Ma ufa turer_ p cific_Alarm_s p within GSD

PrmDataDia n sticAlarmRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is re uire to s p ort

this f eature

Dia n stic_Alarm_re uire within GSD

tru – ma ter s al s p ort dia n stic alarm

f als – dia n stic alarm is o tio al

If s t to tru , th n PrmDataDia n sticAlarm s al b s t to tru to

PrmDataDia n sticAlarm Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Dia n stic_Alarm_s p within GSD

PrmDataPro e sAlarmRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is re uire to s p ort

this f eature

Pro e s_Alarm_re uire within GSD

tru – ma ter s al s p ort pro e s alarm

f als – pro e s alarm is o tio al

If s t to tru , th n PrmDataPro e sAlarm s al b s t to tru to

PrmDataPro e sAlarm Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Pro e s_Alarm_s p within GSD

PrmDataPulPlu AlarmRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is re uire to s p ort

this f eature

Pul_Plu _Alarm_re uire within Sla e GSD

tru – ma ter s al s p ort p l plu alarm

fals – p l plu alarm is o tio al

If s t to tru , th n PrmDataPulPlu Alarm s al b s t to tru to

PrmDataPulPlu Alarm Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Pul_Plu _Alarm_s p within Sla e GSD

PrmDataBlo kStru ture Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Prm_ lo k_ tru ture_s p within GSD

PrmDataBlo kStru tureRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is e p cte to s p ort

this f eature

Prm_ lo k_ tru ture_re within GSD

tru – ma ter s al s p ort blo k stru ture

fals – blo k stru ture is o tio al

If s t to tru , th n PrmDataBlo kStru ture s al b s t totru to

PrmDataIs c ro Mo e Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte Is c ro _Mo e_s p within GSD

PrmDataIs c ro Mo eRe uire Bo le n Sla e DTM s ows with this bit th t th ma ter is e p cte to s p ort

this f eature

Is c ro _Mo e_re uire within GSD

tru – ma ter s al s p ort is c ro e mo e

f als – is c ro e mo e is o tio al

If s t to tru , th n PrmDataIs c ro Mo e s al b s t to tru to

PrmDataPrmCmd Bo le n Sla e DTM s ows with this bit th t th f eature is s p orte PrmCmd_s p within GSD

Calc late b th Commu ic tio DTM

a

If this d ta is n t a plc ble to th d vic (ie.th s rvic is n t s p orte ), th n th ByteAra h s z ro le gth

6.5.2.3 Modific tion of the PND

6.5.2.3.1 Propa ation of c a ge

The PND in lu es p rameter an con g ration data The slave DTM or the Frame Ap l cation

may modify the PND

The s stem s al en ure that the Commu ication Chan el re resentin the PROFIBUS

master is aware of these c an es This is ac ieved by sen in the event

NetworkDataInfoChan ed f om the Slave DTM to re ort the c an e of the PND Al c an es

s ould b re orted as so n as p s ible, but not b fore the c an es are p rsistent The Frame

Ap lcation informs the Parent DTM via NetworkDataInfoChan ed event that p rameters of a

c i d have b en c an ed Then the Commu ication DTM can get the new PND of the Slave

If a Slave DTM wants to c an e p rameters in onlne mode it s al u e DP-V0 or DP-V1

tran action req ests If there is no way of c an in the p rameters by tran action req ests,

the DTM s al disa le config ration an p rameterization in the onl ne state

6.5.2.3.3 Parameter data

If the u er c an es User Parameters of the BIM or of one mod le (e.g via u er interace) an

this af fects the PND, con eq ently the DTM s al update the PND In ad ition to this, it s al

req est a save an inf orm the Frame Ap lcation via NetworkDataInf oChan ed The Frame

Ap lcation s al distribute the information to al relevant comp nents

6.5.2.3.4 Configuration data

Con g ration data wi c an e every time if the u er ad s/removes mod les or c an es the

mod le typ , etc

In the case of the mod lar DTM, the BIM wi b inf ormed when the u er ad s or removes

mod les via the service <ChidAd ed> an service <Chi dRemoved> Chan es of the

p rameters in a mod le wi b re orted by service NetworkDataInf oChan ed

The monol thic DTM or the BIM DTM update their PND data, req est a save an inf orm the

Frame Ap l cation via NetworkDataInfoChan ed

Chan es that af fect the PND often take eff ect on the internal to olog an the Proces Data

Items This information s al b updated by the DTMs to

Commu ication DTM s al not c an e the con g ration data an the u er p rameters p rts of

the PND

6.5.2.4 Spe ial c s s relate to the PND

6.5.2.4.1 DP-V1 s p ort

In the GSD fi e there are two flag regardin DP-V1 At first, the “DPV1_Slave” value: This

me n that the slave has the p s ibi ty to work as a DP-V1 slave If this value exists an the

value is “1”, then the Slave lagDpv1Slave s al b set to true For older s stems, there

s ould also b the p s ibi ty to work as a DP-V0 slave

Only the Commu ication DTM k ows that its master device is a le to provide ac cl c services

Af ter bui din the Slave Bu Parameter Set, the Commu ication DTM wi receive the slave’s

initial PND If the Slave lagDpv1Slave is set to true, the Master DTM s al set the hig est bit

in the first byte of Exten ed DP-V1 Statu Now the slave work as a DP-V1 slave

6.5.2.4.2 Exte de DP-V1 status

Al the PrmData > bits are set by the Commu ication DTM f or the master A Slave DTM

s al ac e t these setin s an ada t its f un tionalty if neces ary

6.5.3 GSD Inf ormation

The GSD inf ormation is not stored with sin le slave in tan es or in a glo al ac es ible fi e It

is provided by the DTM via the PND in the service GetNetworkDataInfo

Some existin DCS u e the GSD fi e directly to o tain information a out the p s ible

config ration an p rameters of a DP Slave This b haviour is not recommen ed for

develo in future DCS

Besides, the inf ormation a out mod les an its p rameters, a GSD fi e contain ad itional

inf ormation a out the slave, s c as the s p orted b u rates

This information is u eful f or a DCS s stem to config re an entire network ac ordin to the

ca a i ties of diff erent slaves

In order to s p ort DCS, a DTM of a PROFIBUS device s al provide a se arate GSD fie It

DeviceDes riptionReferen e pro erty of the PND

6.5.3.2 GSD f or gatewa de ic s

6.5.3.2.1 Type of PROFIBUS gatewa de ic s

There are two typ s of gateway devices

– The visible gateway devices work as a PROFIBUS slave (with a PROFIBUS station

ad res ) an to the u derlyin network they act as a master Slave devices b hin s c a

visible gateway have a se arate ad res sp ce an are ad res ed by exten ed

ad res in f rom the PROFIBUS master

– The tran p rent gateway devices ju t tran f orm the PROFIBUS network to the u derlyin

network Slave devices b hin an in isible gateway s are the ad res sp ce with the

devices on the rest of the PROFIBUS segment They are ad res ed via normal station

ad res by the PROFIBUS master

For b th typ s of devices there is a ne d f or sp cial GSD f iles to s p ort legac DCS as

mentioned b fore

6.5.3.2.2 Visible gatewa de ic s

Visible gateway devices are s ip ed without a GSD fie In te d they have a pro rietary

software s ite that config res an p rameterizes it or they are s ip ed with a to l that cre tes

a GSD for p rameterization software The GSD to l cre tes a GSD for the gateway device

de en in on the u derlyin network config ration or bu set in s (e.g b u rates)

The DTMs f or s c visible gateway devices (Gateway DTM) s ould provide the f un tional ty of

the GSD to l If the GSD is con g ration-de en ent, the DTM could cal service

GetNetworkDataInf o for e c of its c i dren, extract the GSD inf ormation an create

config ration-de en ent GSD information in the same way the to l do s After initial zation of

the DTM, it s ould del ver PND ac ordin to the l n in device itself Every time a c i d is

ad ed or removed, this le d to a c an e in the network data or proces data or b th of the

Gateway DTM

If the GSD de en s on bu set in s, a DTM’s con g ration or p rameterization dialog could

b u ed to c an e bu set in s Based on these set in s, updated GSD information can b

in erted in the DTM information Here again the DTM has to req est a slave an raise a

Proces DataChan ed event if proces data was c an ed an a NetworkDataInfoChan ed

event if network data was c an ed

6.5.3.2.3 Tra spare t gatewa de ic s

There are tran p rent ln in devices on the market (e.g PROFIBUS FMS/DP an PROFIBUS

PA) p rormin a b u rate tran f ormation This req ires a sp cial han l n of the slave

sp cific GSD f iles There are to ls avaia le whic are a le to ada t existin GSD f iles

ac ordin to the hig er b u rate (so caled ‘GSD Con erter’)

The GSD inf ormation s al b del vered by the DTM f or the device In order to s p ort this

kin of l n in devices, a slave DTM s al exp se the GSD f ile on hard drive

6.5.4 Proc s Data Items

A device can off er a n mb r of proces values de en in on the actual config ration

Inf ormation a out these values is provided via Proces Data Items The protocol sp cific

clas es for this purp se are des rib d in Clau e 10 Datatyp s for proces data inf ormation

If the proces data is also ac es ible as Device Data Inf o or there is a relation to a

commu ication c an el (f or in tan e f or gateway DTMs), these relation s al b made

avai a le as IOSig alRefs

7 Protocol specif ic usage of ge eral dataty es

IEC TR 6 4 3-4 alre d defines a set of datatyp s that can b u ed to identify a device an

to provide device information Ta le 4 s ows how general datatyp s are u ed with

IEC 617 4 CP 3/1 an CP 3/2 devices

Table 4 – Protocol spe if ic us g of ge eral d tatype

e ample in PR FIBUS P : Ph sic l Blo k In e 10:

DEVICE MA _ID

7.2 Protocol spe if ic ha dl n of th datatype STRING

PROFIBUS u es strin s in the f orm of c aracter ar ay These ar ay u ual y have a fixed

len th For interaction with FDT, the fol owin rules s al a ply:

– le din sp ces are left trimmed;

– ar ay s al b fi ed with sp ce c aracters (0x2 );

– non-printa le c aracters in VisibleStrin s s al b re laced by '?'

The data ne ded f or management of the network are exp sed by the Device DTM in the

INetworkData inter ace (se Fig re 3)

The datatyp s sp cified in this s bclau e are u ed in the folowin services:

– GetNetworkDataInf o service;

– SetNetworkData service

The datatyp Profibu DeviceAd res is u ed f or def i in the network ad res of a device

The protocol sp cific datatyp s are b sed on def i ition given in IEC 617 4 an IEC 61 5

(as des rib d for e c data typ ) Furthermore, they contain ad itional information a out the

device that is ne ded by s stems to config re CPF 3 l n s an to esta l s commu ication

b twe n the CPF 3 master device an the CPF 3 slave devices

8.2 Configuration

The con g ration of the device itself is done with the aid of the DTM’s GUI Downlo din the

config ration into the slave device is p rormed via the CPF 3 master device To do that an

in order to set up the bu commu ication, the master ne d inf ormation f rom the DTM as

there is:

– GSD f ile

The GSD information is typ -sp cific information an not in tan e-sp cific (with the

ex e tion of certain gateway devices as des rib d e rl er) It is not stored with sin le

slave in tan es or in a glo al ac es ible fie

The master device can u e the general typ -sp cific inf ormation fom the slave’s GSD

information lke bu timin parameters, s p orted b ud rates, etc

– CFG strin (Cfg Data)

The CFG strin provides the in tan e-sp cific information a out the c r ent config ration

of the device It defines the stru ture of the data f ames that wi b tran mit ed on the

PROFIBUS This stru ture de en s on the mod les that are actual y config red

The DTM provides the CFG strin within the pro erty Cf gData that is p rt of the PROFIBUS

Network Data avai a le via service GetNetworkDataInfo

The master device u es this information to set up commu ication with the slave device

8.3 Proc s Data Items

In case of CPF 3 protocols, a FDT Proces Data Item is a re resentative for a sin le date or a

proces value that can b ac es ed f rom a Frame Ap l cation via the master device The

inf ormation avaia le at services f or I/O related information des rib s how to ac es a data

item via a PROFIBUS DP-V1 comman or how to ad res a data item within a PROFIBUS DP

f rame for c cl c I/O Besides al man atory elements (whic in lu e id, BitPosition an

BitL n th) it is hig ly recommen ed that the DP-V1 ad res information is provided This

inf ormation (DP-V1 Slot is u ed by some f rames to manage the PROFIBUS device mod le

inf ormation

8.4 Parameterization

There are two o tion to write p rameters set f rom the DTM’s GUI to the CPF 3 slave device

in the field:

– User Parameters

User Parameters are p rt of the PROFIBUS-DP Slave-Bu -Parameter Set They contain

man facturer sp cific data to c aracterize the DP slave The DTM stores the User

Parameters in pro erty PrmDataUsrPrmData of the PROFIBUS Network Data The User

Parameters are stored with the master device d rin PROFIBUS master con g ration an

are automatical y sent to the slave d rin set up of bu commu ication

NOT This pro e s is PR FIBUS-s e if i For d tais, s e IEC 61 5 s rie

When c an in User Parameters at ru time, the DTM s al u e a DP-V0 con ection an

the a pro riate DP-V0 comman s f or p rameter ex han e as des rib d in the datatyp s

– Writin Parameters with DP-V1 services (MSAC2 primitives)

The DTM may u e DP-V1 tran p rt services to sen its p rameters to the slave device

For that, it has to u e a DP-V1 con ection an the cor esp n in commu ication

comman s Durin setup of commu ication, DP-V1 services are not sent automatical y

The Frame Ap lcation or a DTM s al in oke a downlo d of p rameters via DP-V1

For detai s on the dif ferent b haviour of slaves de en in on the kin of p rameterization,

refer to the IEC 61 5 series

DP-V1 con ection an commu ication comman s can also b u ed to exec te comman s at

the slave For detai s on the u e of DP-V1, se also the IEC 61 5 series

The datatyp s contain the ad res information an the commu ication data req ired to

exec te the resp ctive req est or to tran p rt the resp n e inf ormation

9.2 Prof ibusAbortMe s ge

This is the PROFIBUS sp cific implementation of the a stract Ab rtMes age clas (se

Fig re 4)

Det ais : Fdt List <Abort Det ais

Commu ic at io R efere c e : Guid

The pro erties of the Prof ibu Ab rtMes age datatyp are des rib d in Ta le 5

Table 5 – Profibu Ab rtMe s ge d tatype

Commu ic tio Refere c Id ntifier f or a c mmu ic tio ln to a d vic

Detais Detais a o t th c u e a d s urc of th Ab rt

9.3 DP-V0 Communic tion

Not al defined services are s p orted if the Master is not in c cl c data ex han e with the

slaves In s c cases, the fol owin b haviour is exp cted:

If a Commu ication Chan el receives a req est that cannot b s p orted, the

Er orInf ormation pro erty of the Tran action resp n e s al b set to "NotSup ortedFe ture"

De en in on the bu master typ an on the returned Con ectStatu , the f ol owin services

are avai a le (se Ta le 6)

Table 6 – Av i abi ity of s rvic s for Ma ter Cla s 1 (C1)

O:th s rvic is o tio al a d c n b a aia le, d p n in o th c p bi tie of th u d rlyin ma ter d vic

For Master Clas 2 (C2), not al con ect states are avaia le, se Ta le 7 b low

Table 7 – Av i abi ity of s rvic s for Ma ter Cla s 2 (C2)

Re dUs rParameter

O:th s rvic is o tio al a d c n b a aia le, d p n in o th c p bi tie of th u d rlyin ma ter d vic

If the Master Clas 2 commu ication comp nent s p orts DP-V1 an DP-V0 an has

esta l s ed a DP-V1 con ection to the device, a cal to service Con ect f or DP-V0 s al return

the statu “DeviceInDataEx han e” even if the device is not in statu DataEx han e

If no DP-V1 con ection is esta l s ed, the Master Clas 2 commu ication comp nent s al

verify the avai a i ty of the device (at le st by service Life ist prior to returnin the res lt

9.3.2 Dpv Conne tRe ue t

This is the PROFIBUS DP-V0 sp cif i implementation of the a stract clas Con ectReq est

(se Fig re 5)

Dt mSy st e Ta : Guid

Co nne ctRe que s t

Prot oc old : GuidDpv 0Co ne t R eq e t

Profib sDevic Addre s1

The pro erties of the Dpv0Con ectReq est datatyp are des rib d in Ta le 8

Table 8 – Dpv Conn ctRe ue t datatype

Bu Ad re s Statio a dre s inf ormatio a c rdin to th PR FIBUS s e if i atio

Proto old Uniq e id ntif i r of th PROFIBUS D -V0 proto ol

DtmSy temTa Uniq e id ntif i atio of th DTM in th Frame Ap lc tio

9.3.3 Dpv Conne tRe p ns

This is the PROFIBUS DP-V0 sp cific implementation of the a stract clas Con ectResp n e

(se Fig re 6)

Com u ic at ionR efere c e : Guid

Co nne ctRe sp ons e

Dp 0Co n ct R esp nse

Profib sDe icA ddres1

Table 9 – Dpv Conne tRespons datatype

Bu Ad re s Ad re s inf ormatio a c rdin to th PR FIBUS s e if i atio

Commu ic tio Refere c Id ntifier f or a c mmu ic tio ln to a d vic

Co n ctStatu De crib s th c n e tio statu e ta ls e b th c mmu ic tio c mp n nt

9.3.4 Dpv Dis onne tRe ue t

This is the PROFIBUS DP-V0 sp cific implementation of the a stract clas

Dis on ectReq est (se Fig re 7)

Abort Pe din Tra sac tio s : b ol

Commu ic at io R efere c e :GuidDis co nnectRe que s t

The pro erties of the Dpv0Dis on ectReq est datatyp are des rib d in Ta le 10

Table 10 – Dpv Dis onne tRe u st datatype

Commu ic tio Refere c Id ntifier f or a c mmu ic tio ln to a d vic

Ab rtPe din Tra s ctio s In ic te wh th r p n in tra s ctio s s al b a orte