Iec tr 62453 41 2016

This Part of IEC 6 4 3, whic is a tec nical re ort, is an interf ace sp cif i ation f or develo ers of FDT Field Device To l comp nents f or fun tion control an data ac es within a cl en

IEC TR 62453- 41

THIS PUBLICATION IS COPYRIGHT PROT CTED

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

Al r i hts r es r ve Unle s oth r wis s e ifi d, n p r t of this p blc tio ma b r epr od c d or uti z d in a y for m

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 r mis io in wr itin fr om

eith r IEC or IEC's memb r Natio al Commite in th c u tr y of th r eq e ter 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 iry a o t o tainin a ditio al r i 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 f ur th r infor matio

Th Inter natio al Ele tr ote h ic l Commis io (IEC) is th le din glo al or ga iz tio th t pr ep r es a d p bls e

Intern tio al Sta d r ds for al ele tr i al ele tr onic a d relate te h olo ie

A bout IEC publc 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 r e th t y u h v th

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

IEC Catalo u - webstore.e ch/cat alo u

Th st an -alo e a plc at io for c on ult in t he e t ire

biblo ra hic al informat io o IEC Int ern tio al St an ard ,

Te h ic al Sp cific at io s, Tec hnic al R ep rt s a d ot her

d c ume t s A v aia le for PC, Ma OS, A ndroid Ta let s a d

iPa

IEC publc t io s s arch - w w w.e ch/s arch ub

Th a v anc ed s arc h e a le t o fin IEC p blc t io s b a

v riety of c riteria (efere c n mb r, text, t ec hnic l

c mmit t ee,…) It als giv es informat io o projec t s, re lac ed

Ele tro edia - www.ele tro edia.org

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

elec t ric l t erms c ont ainin 2 0 0 t erms a d d finit io s in

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

la g a e A ls k nown a t he Int ern t io al Ele t rot ec hnic l

V oc ab lary (IEV ) o ln

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

6 0 0 elec t rote h ic l t ermin lo y e t rie in En ls a d

Fre c ex t rac t ed fom t he Terms a d Definit io s cla s of

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

c lec t ed fom e rler p blc at io s of IEC TC 3 , 7 , 8 a d

CIS R

IEC Cu t omer Servic Centre - webst ore.e ch/cs

If y ou wis t o giv u your fe d ac k o t his p blc t io or

n e furt her a sist an e,ple s c ont ac t t he Cu t omer Servic

Ce t re: c sc@ie c h

IEC TR 62453- 41

Edit io 2.0 2 16-0

CONTENTS

FOREWORD 12

INTRODUCTION 14

1 Sco e 15

2 Normative ref eren es 15

3 Terms, def i ition , a breviation an con ention 15

3.1 Terms an def i ition 15

3.2 Ab reviation 16

3.3 Con ention 16

4 Implementation con e t 17

4.1 Tec nological orientation 17

4.2 Implementation of a stract FDT object model 17

4.2.1 General 17

4.2.2 FDT Frame Ap l cation (FA) 17

4.2.3 Device Typ Manager (DTM) 18

4.2.4 Presentation o ject 19

4.2.5 FDT-Chan el o ject 19

4.3 Object interaction 19

4.3.1 Parameter interc an e via XML 19

4.3.2 Examples of u age 21

4.4 Implementation of DTM data p rsisten e an s n hronization 2

4.4.1 Persisten e overview 2

4.4.2 Persisten e interf aces 2

4.5 DTM state mac ine 2

5 General con e ts 2

5.1 General 2

5.2 Overview of tas related FDT interf aces 2

5.3 Return values of interface method 2

5.4 Dual interfaces 2

5.5 Unicode 2

5.6 As n hronou vers s s n hronou b havior 2

5.7 ProgId 3

5.8 Implementation of DTM, DTM device typ an hardware identif i ation inf ormation 3

5.8.1 Device identif i ation 30 5.8.2 Protocol-sp cifi tran formation style s e t (x l) 3

5.8.3 Semantic identif i ation inf ormation 3

5.8.4 Device as ig ment 3

5.8.5 Reg lar expres ion sp cif i ation 3

5.9 Implementation of slave red n an y 3

5.9.1 General 3

5.9.2 To olog imp rtexp rt 3

6 Implementation of FDT services: FDT interfaces 3

6.1 Overview of the FDT interfaces 3

6.2 FDT o jects 3

6.2.1 FDT o ject model 3

6.2.2 Avala i ty of interf ace method 3

6.3 Device Typ Manager 4

6.3.1 Interface IDtm 4

6.3.2 Interface IDtm2 51

6.3.3 Interface IDtmActiveXInf ormation 5

6.3.4 Interface IDtmAp lcation 5

6.3.5 Interface IDtmChan el 5

6.3.6 Interface IDtmDoc mentation 5

6.3.7 Interface IDtmDiag osis 5

6.3.8 Interface IDtmImp rtExp rt 6

6.3.9 Interface IDtmInformation 6

6.3.10 Interface IDtmInformation2 6

6.3.1 Interface IDtmOnl neDiag osis 6

6.3.12 Interface IDtmOnl neParameter 6

6.3.13 Interface IDtmParameter 6

6.3.14 Interface IFdtCommu icationEvents 6

6.3.15 Interface IFdtCommu icationEvents2 7

6.3.16 Interface IFdtEvents 73 6.3.17 Interface IDtmHardwareIdentif i ation 7

6.3.18 Interface IDtmSin leDeviceDataAc es 7

6.3.19 Interface IDtmSin leIn tan eDataAc es 81

6.4 DTM ActiveXControl 8

6.4.1 Interface IDtmActiveXControl 8

6.4.2 Init 8

6.4.3 Pre areToRele se 8

6.5 FDT Chan el 8

6.5.1 Interface IFdtChan el 85 6.5.2 Interface IFdtChan elActiveXInf ormation 8

6.5.3 Interface IFdtCommu ication 9

6.5.4 Interface IFdtChan elSubTo olog 9

6.5.5 Interface IFdtChan elSubTo olog 2 101

6.5.6 Interface IFdtChan elScan 101

6.5.7 Interface IFdtFu ctionBloc Data 10

6.6 Chan el ActiveXControl 10

6.6.1 Interface IFdtChan elActiveXControl 10

6.6.2 Interface IFdtChan elActiveXControl2 10

6.7 Bloc Typ Manager 10

6.7.1 Interface IBtm 10

6.7.2 Interface IBtmInformation 10

6.7.3 Interface IBtmParameter 10

6.8 BTM ActiveXControl 1 0

6.8.1 General 1 0

6.8.2 Interface IBtmActiveXControl 1 0

6.9 Frame Ap l cation 1 1

6.9.1 Interface IDtmEvents 1 1

6.9.2 Interface IDtmEvents2 12

6.9.3 Interface IDtmScanEvents 121

6.9.4 Interface IDtmAu itTrai Events 12

6.9.5 Interface IFdtActiveX 12

6.9.7 Interface IFdtBulkData 12

6.9.8 Interface IFdtContainer 131

6.9.9 Interface IFdtDialog 13

6.9.10 Interface IFdtTo olog 13

6.9.1 Interface IDtmRed n an yEvents 141

6.9.12 Interface IDtmSin leDeviceDataAc es Events 14

6.9.13 Interface IDtmSin leIn tan eDataAc es Events 14

6.9.14 Interface IFdtBtmTo olog 14

7 FDT seq en e c arts 14

7.1 DTM p er to p er commu ication 14

7.1.1 General 14

7.1.3 As n hronou con ect f or a p er to-p er con ection 14

7.1.4 As n hronou dis on ect f or a p er to-p er con ection 14

7.1.5 As n hronou tran action for a p er to-p er con ection 14

7.2 Nested commu ication 14

7.2.1 General 14

7.2.2 Generate s stem to olog 15

7.2.4 As n hronou tran action for a s stem con ection 15

7.3 To olog s an 15

7.3.1 Scan network 15

7.3.2 Can el to olog s an 15

7.3.3 Provisional s an res lt notif i ation 15

7.3.4 Scan f or commu ication hardware 15

7.3.5 Man facturer sp cifi device identif i ation 15

7.4 Registration of protocol-sp cif i FDT s hemas 16

7.5 Con g ration of a f ieldbu master 16

7.6 Startin an rele sin a pl cation 16

7.7 Chan el ac es 16

7.8 DCS Chan el as ig ment 16

7.9 Printin of DTM-sp cif i doc ments 16

7.10 Printin of Frame Ap l cation-sp cif i doc ments 17

7.13.2 In tantiation of an existin DTM 17

7.13.3 In tantiation of a DTM ActiveX u er interf ace 17

7.13.4 Rele se of a DTM u er interface 17

7.14 Persistent storage of a DTM 18

7.14.1 State mac ine of in tan e data 18

7.14.2 Savin in tan e data of a DTM 18

7.14.3 Relo d of a DTM o ject f or another in tan e 18

7.14.4 Co y an versionin of a DTM in tan e 18

7.15 Au it trai 18

7.16 Comp rison of two in tan e data sets 18

7.16.1 Comp rison without u er interf ace 18

7.16.2 Comp rison with u er interf ace 18

7.17 Fai safe data ac es 18

7.18 Set or modify device ad res with u er interf ace 18

7.19 Set or modify k own device ad res es without u er interface 18

7.2 Display or modif y al c i d device ad res es with u er interf ace 19

7.21 Device initiated data tran fer 191

7.2 Startin an rele sin DTM u er interface in modal dialog 19

7.2 Parent comp nent han l n red n ant slave 19

7.2 Initial zation of a Chan el ActiveX control 19

7.2 1 General 19

7.2 2 Sup orts IFdtChan elActiveXcontrol2 19

7.2 3 Do s not s p ort IFdtChan elActiveXControl2 19

8.1.2 Comp nent categories 2 1

8.1.3 Registry entries 2 2

8.1.4 In tal ation is ues 2 2

8.1.5 Microsof t’s stan ard comp nent categories manager 2 3

8.1.6 Bui din a Frame Ap l cation-data ase of s p orted devices 2 3

8.1.7 DTM registration 2 3

8.2 Path an f ile inf ormation 2 4

8.2.1 Path inf ormation provided by a DTM 2 4

8.2.2 Path an p rsisten y 2 4

B.3 Presentation o ject services 2 7

B.4 General c an el services 2 7

B.5 Proces c an el services 2 8

B.6 Commu ication Chan el Services 2 8

B.7 Frame Ap l cation Services 2 9

An ex C (normative) FDT XML s hemas 2 2

C.1 General 2 2

C.2 FDTDataTyp sSc ema 2 2

C.3 FDTAp l cationIdSc ema 2 8

C.4 FDTUserInformationSc ema 2 8

C.2 DTMEn ironmentSc ema 2 9

C.2 FDTScanReq estSc ema 2 1

An ex D (inf ormative) FDT XML styles – Doc mentation 310

An ex E (informative) FDT XSL Tran f ormation 314

E.1 Identifi ation tran formation 314

E.2 Hint 314

An ex F (normative) Chan el s hema 316

F.1 FDTBasicChan elParameterSc ema 316

F.2 Template for Chan el Sc ema 317

An ex G (normative) FDT version intero era i ty g ide 318

G.1 Overview 318

G.2 General 318

G.3 Comp nent intero era i ty 318

G.4 FDT typ l brary 3 0

G.5 DTM an device version 3 0

G.6 Persisten e 3 0

G.7 Nested commu ication 3 1

G.7.1 General 3 1

G.7.2 Data ex han e 3 1

G.7.3 Commu ication c an el upgrade 3 1

G.7.4 Scenarios 3 1

G.7.5 OnAd Chi d 3 2

G.8 Implementation hints 3 2

G.8.1 Interfaces 3 2

G.8.2 Persisten e 3 2

An ex H (informative) Implementation with Net tec nolog 3 3

H.1 How FDT s p orts NET b sed develo ment 3 3

H.2 Microsof t NET Framework 1.1 an 2.0 comp tibi ty 3 3

H.3 Side-by-side in tal ation an related pro lems 3 3

H.4 How to avoid comp tibi ty is ues 3 4

An ex I (informative) Trade names 3 5

Bibl ogra h 3 6

Fig re 1 – Part 41 of the IEC 6 4 3 series 14

Fig re 2 − Frame Ap lcation interf aces 18

Fig re 3 − DTM interf aces 18

Fig re 4 − FDT Cl entserver relation hip via XML 19

Fig re 5 − Data ac es an storage 21

Fig re 6 − Commu ication 2

Fig re 7 − Doc mentation 22 Fig re 8 − Parameter verif i ation in case of f ai saf e devices 2

Fig re 9 − State mac ine of a DTM 2

Fig re 10 − Device identif i ation 30 Fig re 1 − Stru tural overview 32 Fig re 12 − Interfaces of FDT o jects – DTM an DtmActiveXControl 3

Fig re 13 − Interfaces of FDT o ject – Frame Ap lcation 3

Fig re 14 − FDT o jects – FDT-Chan el 3

Fig re 15 − FDT o jects – BTM an BtmActiveXControl 3

Fig re 16 − Pe r to p er con ection b twe n DTM an device 14

Fig re 17 − As n hronou con ect (p er to p er) 14

Fig re 18 − As n hronou dis on ect (p er to p er) 14

Fig re 19 − As n hronou tran action (p er to p er) 14

Fig re 2 − Sy tem-to olog 15

Fig re 21 − Generation of s stem to olog by Frame Ap l cation 151

Fig re 2 – Generation of s stem to olog – Particip tion of DTM 15

Fig re 2 – Sy tem con ection (acros commu ication hierarc y) 15

Fig re 2 − As n hronou tran action (s stem con ection) 15

Fig re 2 − Scan network to olog 15

Fig re 2 − Can el to olog s an 15

Fig re 2 − Provisional to olog s an 15

Fig re 2 − Scan f or commu ication hardware 15

Fig re 2 − Man facturer sp cifi device identif i ation 16

Fig re 3 − Ad protocol-sp cifi s hemas to Frame Ap lcation s hema s b p th 161

Fig re 31 − Frame Ap lcation re d protocol-sp cif i device identif i ation inf ormation

of DTMDeviceTyp s 16

Fig re 3 − Bu master con g ration 16

Fig re 3 − Startin an rele sin a plcation 16

Fig re 4 − Printin of Frame Ap l cation-sp cif i doc ments 171

Fig re 41 − Re ort generation (Frame Ap l cation style) 17

Fig re 4 − Re ort generation (device ven or sp cif i style) 17

Fig re 4 − Pro agation of c an es 17

Fig re 4 − L c in for non-s n hronized DTMs 17

Fig re 4 − L c in for s n hronized DTMs 17

Fig re 4 − In tantiation of a new DTM 17

Fig re 4 − In tantiation of an existin DTM 17

Fig re 4 − In tantiation of a DTM u er interface 17

Fig re 4 − Rele se of a DTM u er interface 18

Fig re 5 − State mac ine of in tan e data set 181

Fig re 51 – Persisten e states of a data set 18

Fig re 5 − Savin in tan e data of a DTM 18

Fig re 5 − Co y an versionin of a DTM in tan e 18

Fig re 5 − Au it trai 18

Fig re 5 − Comp rison without u er interf ace 18

Fig re 5 − Comp rison with u er interf ace 18

Fig re 5 − Faisafe data ac es 18

Fig re 5 − Set or modify device ad res with u er interf ace 18

Fig re 5 − Set or modify k own device ad res es without u er interface 19

Fig re 6 − Display or modif y al c id device ad res es with u er interf ace 191

Fig re 61 − Device initiated data tran fer 19

Fig re 6 − Modal DTM u er interf ace 19

Fig re 6 − Han l n of a red n ant slave 19

Fig re 6 − Init of Chan el ActiveX with IFdtChan elActiveXControl2 19

Fig re 6 − Init of Chan el ActiveX® without IFdtChan elActiveXControl2 19

Fig re 6 − Savin data f rom a DTM to b upgraded 19

Fig re 6 − L adin data in the re lacement DTM 19

Fig re 6 − Usage of IDtmSin leDeviceDataAc es 19

Fig re 6 − General seq en e of cre tion an in tantiation of bloc s 2 0

Fig re E.1 – XSLT role 315

Ta le 1 – Def i ition of DTM state mac ine 2

Ta le 2 − Tas related DTM interf aces 2

Ta le 3 − Tas related DTM ActiveX® interfaces 2

Ta le 4 − Tas related FDT-Chan el interf aces 2

Ta le 5 − Tas related Chan el ActiveX interf aces 2

Ta le 6 − Tas related BTM interf aces 2

Ta le 7 − Tas related BTM ActiveX interfaces 2

Ta le 8 − Tas related Frame Ap l cation interf aces 2

Ta le 9 − Semantic identif i ation inf ormation 3

Ta le 10 − Reg lar expres ion 3

Ta le 1 − Avai a i ty of DTM method in dif ferent states 3

Ta le 12 − Avai a i ty of Frame Ap l cation interf aces 41

Ta le 13 – Des ription of in tan e data set states 181

Ta le 14 – Des ription of p rsistent states 18

Ta le 15 – Comp nent categories 2 1

Ta le 16 – Combination of categories 2 2

Ta le 17 – Example for DTM registration 2 2

Ta le 18 – FDT-sp cif i Id 2 5

Ta le 19 – Basic data typ s 2 5

Ta le 2 – Help r o jects f or doc mentation 2 6

Ta le B.1 − General services 2 3

Ta le B.2 − DTM services related to in tal ation 2 3

Ta le B.3 − DTM services related to DTM information 2 4

Ta le B.4 − DTM services related to DTM state mac ine 2 4

Ta le B.5 − DTM services related to fun tion 2 5

Ta le B.6 − DTM services related to doc mentation 2 5

Ta le B.7 − DTM services to ac es the in tan e data 2 5

Ta le B.8 − DTM services to ac es diag osis 2 6

Ta le B.9 − DTM services to ac es the device data 2 6

Ta le B.10 − DTM services related to network management inf ormation 2 6

Ta le B.1 − DTM services related to onlne o eration 2 6

Ta le B.12 − DTM services related to FDT-Chan el o jects 2 7

Ta le B.13 − DTM services related to imp rt an exp rt 2 7

Ta le B.14 − DTM services related to data s n hronization 2 7

Ta le B.15 − General c an el services 2 8

Ta le B.16 − Chan el services f or IO related information 2 8

Ta le B.17 − Chan el services related to commu ication 2 8

Ta le B.18 − Chan el services related s b-to olog management 2 9

Ta le B.19 − Chan el services related to fun tion 2 9

Ta le B.2 − Chan el services related to s an 2 9

Ta le B.21 − FA services related to general events 2 9

Ta le B.2 − FA services related to to olog management 2 0

Ta le B.2 − FA services related to red n an y 2 0

Ta le B.2 − FA services related to storage of DTM data 2 0

Ta le B.2 − FA services related to DTM data s n hronization 2 1

Ta le B.2 − FA services related to presentation 2 1

Ta le B.2 − FA services related to au it trai 2 1

Ta le C.1 – Des ription of general XML at ributes 2 2

Ta le C.2 – Des ription of general XML elements 2 7

Ta le C.3 – Device clas if i ation ID 2 9

Ta le C.4 – Device clas if i ation ac ordin to IEC TR 6 3 0:2 0 , An ex G 2 0

Ta le C.5 – Des ription of a pl cationId atribute 2 8

Ta le C.6 – Des ription of a pl cationId elements 2 8

Ta le C.7 – Des ription of u er information atributes 2 9

Ta le C.8 – Des ription of u er inf ormation elements 2 9

Ta le C.9 – Des ription of DTM inf ormation atributes 2 0

Ta le C.10 – Des ription of DTM information elements 2 0

Ta le C.1 – Des ription of fun tion cal atributes 2 4

Ta le C.12 – Des ription of p rameter doc ment atributes 2 4

Ta le C.13 – Des ription of p rameter doc ment elements 2 5

Ta le C.14 – Des ription of doc mentation atributes 2 3

Ta le C.15 – Des ription of doc mentation elements 2 3

Ta le C.16 – Des ription of protocols element 2 5

Ta le C.17 – Des ription of s stem tag at ributes 2 5

Ta le C.18 – Des ription of s stem tag elements 2 5

Ta le C.19 – Des ription of au it trai at ributes 2 7

Ta le C.2 – Des ription of au it trai elements 2 7

Ta le C.21 – Des ription of device statu atribute 2 8

Ta le C.2 – Des ription of device statu elements 2 8

Ta le C.2 – Des ription of fun tion at ributes 2 9

Ta le C.2 – Des ription of fun tion elements 2 0

Ta le C.2 – Des ription of c an el f un tion atributes 2 3

Ta le C.2 – Des ription of c an el f un tion elements 2 4

Ta le C.2 – Des ription of comp rison at ribute 2 6

Ta le C.2 – Des ription of comp rison elements 2 6

Ta le C.2 – Des ription of fai safe atributes 2 7

Ta le C.3 – Des ription of fai safe elements 2 7

Ta le C.31 – Des ription of to olog s an elements 2 8

Ta le C.3 – Des ription of o eration phase at ribute 2 8

Ta le C.3 – Des ription of o eration phase element 2 8

Ta le C.3 – Des ription of DTM init element 2 9

Ta le C.3 – Des ription of u er mes age at ributes 2 9

Ta le C.3 – Des ription of u er mes age elements 2 0

Ta le C.3 – Des ription of DTM info l st elements 2 1

Ta le C.3 – Des ription of to olog at ributes 2 2

Ta le C.3 – Des ription of to olog elements 2 2

Ta le C.4 – Des ription of device l st at ributes 2 6

Ta le C.41 – Des ription of device l st elements 2 7

Ta le C.4 – Des ription of g i la el element 2 8

Ta le C.4 – Des ription of DTM state element 2 9

Ta le C.4 – Des ription of frame version element 2 9

Ta le C.4 – Des ription of con ect resp n e element 2 0

Ta le C.4 – Des ription of typ req est element 2 0

Ta le C.4 – Des ription of s an req est atributes 2 1

Ta le C.4 – Des ription of s an req est elements 2 1

Ta le C.4 – Des ription of common identifi ation at ributes 2 3

Ta le C.5 – Des ription of common identifi ation element 2 4

Ta le C.51 – Des ription of s an identif i ation at ributes 2 4

Ta le C.5 – Des ription of s an identif i ation elements 2 4

Ta le C.5 – Des ription of device typ identif i ation element 2 6

Ta le C.5 – Des ription of item l st atributes 2 8

Ta le C.5 – Des ription of item l st elements 2 9

Ta le C.5 – Des ription of BTM data typ at ributes 3 3

Ta le C.5 – Des ription of BTM data typ elements 3 4

Ta le C.5 – Des ription of BTM information elements 3 5

Ta le C.5 – Des ription of BTM p rameter elements 3 6

Ta le C.6 – Des ription of BTM init element 3 8

Ta le C.61 – Des ription of BTM info lst element 3 9

Ta le F.1 – Des ription of b sic c an el atribute 316

Ta le F.2 – Des ription of b sic c an el elements 316

Ta le F.3 – Des ription of x x c an el p rameter at ribute 317

Ta le F.4 – Des ription of x x c an el p rameter elements 317

Ta le G.1 − Intero era i ty b twe n comp nents of dif f erent version 319

INTERNATIONAL ELECTROTECHNICAL COMMISSION

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 f i ld 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 cific tio s (PAS) a d Guid s (h re f ter refere 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 for 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 f rom al

intere te IEC Natio al Commite s

3) IEC Pu lc tio s h v th form of re omme d tio s for 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 eforts 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 for 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 iformity, 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 r e 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 rtif i atio b die pro id c nformity

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 rtif i atio 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 fe s) 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

Pu lc tio s

8) Ate tio is drawn to th Normativ refere c s cite in this p blc tio Us of th refere c d p blc tio s is

in is e s ble f or th c re t a plc tio of this p blc tio

9) Ate tio is drawn to th p s ibi ty th t s me of th eleme ts of this IEC Pu lc tio ma b th s bje t of

p te t rig ts IEC s al n t b h ld re p n ible f or id ntifyin a y or al s c p te t rig ts

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 from that whic is normal y publ s ed as an International Stan ard, f or

example "state of the art"

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

This secon edition can els an re laces the f irst edition publ s ed in 2 0 , an con titutes a

tec nical revision

This edition in lu es the f ol owin sig if i ant tec nical c an es with resp ct to the previou

edition:

a) cor ection of sp cif i ation f or bu master con g ration;

b) cor ection of sp cif i ation f or pro agation of c an es;

c) cor ection of des ription of DTM services for onl ne o eration

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

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

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

This publcation has b en draf ted in ac ordan e with the ISO/IEC Directives, Part 2

A l st of al p rts of the IEC 6 4 3 series, u der the general title Field De ic To l (FDT)

intera e s e ific tio , can b f ou d on the IEC we site

The commit e has decided that the contents of this publ cation wi remain u c an ed u ti

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

related to the sp cif i publ cation At this date, the publ cation 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 – Th 'colour in ide' logo on the cov r pa e of this publ c tion indic te

understa ding of its conte ts Us rs s ould therefore print this doc me t usin a

colour printer

This Part of IEC 6 4 3, whic is a tec nical re ort, is an interf ace sp cif i ation f or

develo ers of FDT (Field Device To l) comp nents f or fun tion control an data ac es within

a cl entserver arc itecture The sp cif i ation 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 fieldbu ses into control s stems, there are a f ew other tas s whic

ne d to b p rf ormed In ad ition to f ieldbu - an device-sp cif i 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,

f or 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 def i ition 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 sof tware comp nent, cal ed DTM (Device Typ Manager), is s p l ed by the

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

FDT interfaces defi ed in this sp cifi ation The a pro c to integration is, in general, o en

f or al kin of f ieldbu ses an th s me ts the req irements f or integratin dif f erent kin s of

devices into heterogene u control s stems

Fig re 1 s ows how IEC TR 6 4 3-41 is in orp rated in the stru ture of the IEC 6 4 3

FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 41: Object model integration prof ile –

This p rt of IEC 6 4 3, whic is a tec nical re ort, defi es how the common FDT prin iples

are implemented b sed on the Microsof t

1

COM tec nolog , in lu in the o ject b havior an

o ject interaction via COM interfaces

This p rt sp cif ies the tec nolog -sp cif i implementation of the protocol-sp cifi f un tional ty

This p rt of IEC 6 4 3 is inf ormative, however when this p rt is a pl ed its req irements ne d

to b implemented as sp cif ied

This p rt sp cif ies FDT version 1.2.1

The f olowin doc ments, in whole or in p rt, are normatively ref eren ed in this doc ment an

are in isp n a le f or its a pl cation For dated ref eren es, only the edition cited a pl es For

u dated ref eren es, the latest edition of the referen ed doc ment (in lu in an

IEC 617 4 (al p rts), I nd ustrial c mmu ic tio n twork – P rofil s

GUI comp nent tec nolog b sed on the Microsof t Comp nent Object Model (COM/DCOM)

Note 1 to e try: Former sta d rd wa OLE c ntrols (OC )

3.1.2

a y c ronous f unction

non-bloc in f un tion in whic the cal n proces contin es exec tion whi e the f un tion is

exec ted in the b c grou d

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

as wel as the f ol owin a ply

GUID Glo aly Uniq e Id ntifier (aUUID)

3.3 Conv ntions

The con ention f or UML notation u ed in this doc ment are defi ed in IEC 6 4 3-1

4 Implementation c nc pt

The ActiveX tec nolog introd ced by Microsoft makes it p s ible to def i e interfaces whic

contain not only data but also fun tion These p s ibi ties have alre d b en s c es f ul y

u ed in conju ction with OPC (originaly: OLE f or Proces Control) def i ition

Within this tec nical re ort, implementation of FDT-only u er interf aces in ActiveX

tec nolog are sp cif ied f or the en ine rin comp nents of f ield devices If the en ine rin

s stem implements the cor esp n in interfaces, the ActiveX tec nolog provides the

automatic integration of the comp nents an takes care of the interaction b twe n the

en ine rin s stem an the sof tware comp nents of the devices Furthermore the FDT

interf ace sp cif i ation alows the integration of device comp nents with integrated u er

interf aces as wel as the emb d in of ActiveX controls provided by the device comp nent

f or sp cial en ine rin tas s

The implementation of FDT´s cl ent server arc itecture def i ed in this tec nical re ort is

b sed on Microsof t COM

This p rt of IEC 6 4 3 sp cif ies COM interf aces (what the interfaces are), not the

implementation ( he “how” of the implementation) of those interfaces It sp cif ies the b havior

that the interfaces are exp cted to provide to cl ent a pl cation that u e them The F

DT-sp cif i ation neither sp cifies the implementation of DTMs nor the implementation of Frame

Ap l cation

In lu ed are des ription of arc itectures an interf aces whic se m most a pro riate for

those arc itectures Like al COM implementation , the arc itecture of FDT is a cl ent-server

model where DTMs are the server comp nents managed by the Frame Ap l cation

4.2 Impleme tation of abstra t FDT obje t model

The FDT o jects are implemented as COM o jects The general exp ctation is that these

o jects may b implemented as inproc as wel as outproc servers The Frame Ap l cation is

resp n ible f or organizin the exec tion of the o jects in a distributed s stem (b sed on a

ven or sp cif i implementation)

4.2.2 FDT Frame Appl c tion (FA)

From a DTM p int of view, al tas - elated interfaces for the interaction with Frame Ap l cation

are avai a le via the main interface IFdtContainer of the Frame Ap l cation (se Fig re 2)

FrameA pplc tio

F t Chan el

IFdt Co t ain r

Sta dard intera e for storage a d eve ts

O ptio nal task-related intera e

Fig re 2 − Frame Appl c tion interfa e

In a complex plant en ironment, there are also complex commu ication network for l n in

the proces devices No DTM s ould ne d an information a out the to olog of a s stem

network So it is up to the Frame Ap l cation to organize the routin for ac es in a device

The Frame Ap l cation has to provide in e c case a p er to-p er con ection (ph sical or

logical) So its up to the Frame Ap l cation to manage the multi u er ac es to a device

Sta dard intera e for sto rage

O ptio nal task-related intera e

The interfaces IDtm an IDtmInformation have to b implemented by e c DTM (se 5.2)

These interfaces provide the services an information for control n a DTM From a Frame

Ap l cation’s p int of view, al tas - elated interfaces for the interaction with the device

f un tional ty are avai a le via these interf aces Whic tas related interf aces are provided

de en s on the ca a i ty of the DTM an the cor esp n in device Eac interf ace is

des rib d in detai in the a pro riate s bclau e

The BTM implements simi ar interf aces to those sp cif ied f or a DTM Bloc -sp cif i s hemas

BtmInf ormationSc ema re laces DTMInformationSc ema

4.2.4 Pre e tation obje t

A presentation o ject as def i ed by this sp cif i ation may b an ActiveX o ject (al ows

integration into GUI of FA) or a stan alone program, that may b integrated by a DTM

IEC TR 6 4 3-61 provides a style g ide for a common lo k an f eel of ActiveX u er

interf aces

4.2.5 FDT-Cha nel obje t

The FDT-Chan el o ject implements at le st the IFdtChan el interf ace that gives ac es to

al p rameters of the c an el whic des rib s the c an el itself

If the device provides commu ication f un tional ty, l ke a fieldbu ada ter or a gateway, the

FDT-Chan el o ject s al implement f urther interfaces f or the commu ication via this c an el

(Commu ication Chan el) Eac interface of the FDT-Chan el o ject is des rib d in detai ,

se the a pro riate s bclau e

As def i ed in IEC 6 4 3-2, Commu ication Chan els re resent the gateway from the F

IFdtCommu ication s al b implemented f or Commu ication Chan els

IFdtCommu ication alway provides the commu ication fun tional ty for DTMs to ac es their

fieldbu devices Al action that b lon to the ph sical fieldbu s al b done by u in this

interf ace

4.3 Obje t intera tion

4.3.1 Parameter interc a ge via XML

Data ex han e b twe n o jects is implemented b sed on tran p rt of XML doc ments (XDR

f ormat via COM interf aces One example for this data ex han e is the p rameter interc an e

via XML is to provide a way to ex han e inf ormation b twe n Frame Ap l cation an DTMs

(se Fig re 4) Typical y, in proces control s stems, multiple u e cases lke o servin ,

c an el as ig ment, or master con g ration, ne d inf ormation a out the con g ration of a

device

XML is not me nt to re lace pro rietary formats; it is me nt to provide ac es to data that is

stored in a pro rietary format It is recommen ed that data is stored local y in the f as ion that

makes the most sen e XML provides an exten a le stan ard to con ect FDT comp nents

The data ex han e is done via XML doc ments Within these doc ments XML tag are u ed

to del mit pieces of data XML le ves the interpretation of the data to the a pl cation that

re d it To get a common u derstan in of the ex han ed data FDT u es XML s hemas f or

val dation For the data ac es are stan ardized to ls l ke the DOM (W3C's doc ment o ject

XML s hemas are val d XML s ntax themselves an are u ed to val date XML data They

al ow the val dation of the doc ment stru ture an the data typ s of the elements

W3C's doc ment o ject model (DOM) is a stan ard internal re resentation of the doc ment

stru ture It aims to make it e s for programmers to ac es comp nents an delete, ad , or

edit their content, atributes an style In es en e, the DOM makes it p s ible f or

platf orms Whi e programmers may ne d to u e dif f erent programmin lan uages, they do not

ne d to c an e their programmin model

An XML p rser u ual y generates the DOM Microsof t provides s c an XML p rser So the

It is recommen ed that the FDT develo er alway work with the DOM b cau e

• the XML p rser generates the DOM f rom the tran fer ed XML data,

• the s hemas en ure a val d DOM with wel defi ed elements,

• the DOM s p les stan ard tre - an colection-method for data ac es ,

• the DOM can generate the XML data f or the data tran fer

The val dation of a XML doc ment en ures that the content of an atribute is vald ac ordin

to the XML s hemas

• Non strin data typ s (Ui4,en meration,etc.): Empty or in al d at ribute values wi b

detected d rin the val dation of the doc ment

• Data typ s ‘strin ’ an ‘bin.hex’(hexadecimal digits re resentin octets): Empty values are

p s ible No p rsin er or is generated

To avoid intero era i ty pro lems develo ers s ould con ider f ol owin b sic rules

To en ure a ro u t implementation, develo ers s ould b aware that XML doc ments with

empty atributes of typ ‘strin ’ or ‘bin.hex’ could b received FDT comp nents s ould b

ca a le to han le this in a pro er way

• Providin XML doc ments:

Empty o tional atributes s ould b avoided general y, b cau e they are a p tential cau e

of intero era i ty pro lems an a waste of resources Also o tional XML elements s ould

b removed if they contain no information Ex e tion: Empty ‘strin ’ at ributes can make

sen e in some cases (as s own in the example b low)

If a Frame Ap l cation can not provide information a out login location an ses ion

des ription, the cor esp n in atributes s ould b removed

If a Frame Ap l cation can not provide atribute values, the atributes s ould not b provided

Ne ativ Ex mple:

<FDT xmln ="x-s h ma:FDTUs rInformatio Sc ema.xml" xmln :fdt="x-s h ma:FDTDataTy e Sc ema.xml">

<FDTUs rInformatio proje tName "Proje t1 u erName "ThisUs r u erL v l="mainte a c "

Po itiv Ex mple:

<FDT xmln ="x-s h ma:FDTUs rInformatio Sc ema.xml" xmln :fdt="x-s h ma:FDTDataTy e Sc ema.xml">

<FDTUs rInformatio proje tName "Proje t1 u erName "ThisUs r u erL v l="mainte a c "/>

</FDT>

If the ses ion des ription is general y avai a le, but the u er has not typ d in somethin , then

it makes sen e to u e an empty atribute

Ac e ta le Ex mple:

<FDT xmln ="x-s h ma:FDTUs rInformatio Sc ema.xml" xmln :fdt="x-s h ma:FDTDataTy e Sc ema.xml">

<FDTUs rInformatio proje tName "Proje t1 u erName "ThisUs r u erL v l="mainte a c "

s s io De criptio =" />

</FDT>

Parameter interc an e b twe n DTM an Frame Ap l cation is done via XML doc ment

Object oriented ac es to data is provided when u in an XML p rser that generates an in

-memory re resentation of the XML data (e.g a DOM) In tan e data to b stored

(p rsisten e) can also b han led as an XML doc ment to simpl f y the DTM develo ment an

to have a homogene u data han l n within a DTM But also if the data are stored as XML

the content of these data is only k own by DTM (se Fig re 5)

Figure 5 − Data a c s a d stora e

The XML doc ment for commu ication in lu es device data an the neces ary information f or

routin to esta l s p er to-p er con ection b twe n DTM an f ield device (se Fig re 6)

"publc" parametersof DTM for Frame Ap lc tio

" private " parameters of DTM

IEC

Figure 6 − Communic tion

Here the DTM only k ows the ad res information for a p er to-p er con ection The Frame

Ap l cation ad s d rin ru time al neces ary routin information

For doc mentation of f ield devices within the project doc mentation an f ield device-sp cif i

doc mentation XML is u ed in conju ction with XML style s e ts (XSL) for layout (se

Fig re 7) A def ault style s e t is s p orted by the Frame Ap l cation

Fig re 7 − Doc me tation

In case of f aisafe f ield devices the in tan e data that are stored in the control er (e.g PLC)

af ter uplo d f rom the field device s al b verif ied by the DTM (se Fig re 8) The interc an e

format of this data is also an XML doc ment

IEC

Figure 8 − Parameter v rific tion in c s of f ai s f e de ic s

The s n hronization of the DTM data set is done via the interf ace IFdtContainer

To u e the storage comp nent of the Frame Ap l cation, a DTM has to implement the

stan ard COM-interf aces IPersistPro ertyBag an IPersistStre mInit It is not determined how

the DTM p rf orms the storage or whic kin of private data of a DTM is stored

The Frame Ap l cation req ests the storage of private data of a DTM A DTM s al b a le to

re-esta l s its complete state when this is req ested by the Frame Ap lcation This is done

by cal n the f un tion IPersistXXX: L ad of the DTM Some DTMs do not s p ort relo d of a

DTM o ject by cal n IPersistXXX: L ad several times With an IPersistXXX:Save req est a

DTM s al store its private data within the storage provided by the Frame Ap lcation A DTM

o ject for a new in tan e s al b initial zed if the IPersistXXX: nitNew method is cal ed by the

Frame Ap l cation

DTMs u in ad itional own data storage s al provide al data whic are neces ary f or

commis ionin via the IPersistXXX interf ace Private data not provided via the IPersistXXX

IDtmImp rtExp rt interface Also an IStre m o ject is u ed to store an retrieve s c imp rt

an exp rt data

In order to simpl f y the DTM develo ment, it is up to a DTM to implement one of the def i ed

p rsistent interf aces (IPersistStre mInit or IPersistPro ertyBag) ac ordin to the Microsof t

stan ard The Frame Ap l cation s al b a le to han le b th

Ref eren es to DTMs do not b lon to the in tan e data of a DTM A DTM s al not store an

ref eren es to other DTMs A DTM can get information con ernin its p rents or c i d via

IFdtTo olog : GetParentNodes( an IFdtTo olog : GetChi dNodes(

DTM s ould re ort data lo d er ors via stan ard COM er or mec anism (HRESULT not eq al

to S_OK) Optional y, DTM can write further h man re da le er or inf ormation to stan ard

COM glo al er or inf o (Win3 SetL stEr or method)

FB-Data

routin

Field d vic

4.4.2 Persiste c interf ac s

For detai ed inf ormation a out IPersistStre mInit an IPersistPro ertyBag ple se ref er to the

stan ard Microsof t doc mentation lke MSDN®

The fol owin state mac ine s ows the diff erent states of a DTM (se Fig re 9) The state

mac ine is b sed on the general state mac ine as def i ed in IEC 6 4 3-2 It is exten ed to

ac ommodate the sp cif i ne d of COM b sed implementation

Table 1 – Def inition of DTM state ma hine

Rele s Commu ic tio (

OnPre are ToRele

s (

ID Start state E d state Trig er Co ditio Actio

13 Zombie <No Existin > Rele s (

This clau e provides general information a out the FDT interf aces, an some b c grou d

information a out how the desig ers of FDT exp ct these interfaces to b implemented an

u ed

5.2 Ov rview of ta k relate FDT interf ac s

Al FDT interf aces are tas related Eac o ject s al implement a man atory set of interf aces

exp cted by al other o jects By implementin o tional FDT interf aces an o ject is a le to

s p ort ad itional f un tional ty, f or example a DTM may provide doc mentation in XML f ormat

or sp cial diag ostic , a f rame-a pl cation may provide au it trai f un tional ty

Eac o ject is a le to determine the avaia i ty of s c o tional interfaces of other o jects

d rin ru time

Al def i ed FDT interf aces are f i ed an wi never b c an ed Ad itional f uture exten ion

wi b b sed on ad itional o tional interf aces A DTM or frame-a pl cation is then a le to ad

a hig er FDT version s p ort by implementin or u in s c ad itional FDT interfaces

De en in on the fun tional ty of a DTM, ad itionaly to the default set of man atory

interf aces an extra set of interf aces may b man atory to s p ort (se Ta le 2)

Table 2 − Ta k relate DTM interf ac s

Devic Type Manager Avaiabi ty Us r

IDtmHardwareId ntif i atio Optio al

The man atory interfaces of a DTM ActiveX are s own in Ta le 3

Table 3 − Ta k relate DTM Activ X® interf ac s

DTM ActiveX co trol

Avaiabi ty

De en in on the f un tional ty of a c an el, ad itionaly to the man atory default interf ace an

extra set of interfaces may b man atory to s p ort (se Ta le 4)

Table 4 − Ta k relate FDT-Cha nel interf ac s

IFdtCh n elActiv XInformatio Optio al Ma d tory

The man atory interfaces of a Chan el ActiveX are s own in Ta le 5

Table 5 − Ta k relate Cha n l Activ X interf ac s

FDT Chan el ActiveX co trol

Avaiabi ty

The man atory interfaces of a BTM are s own in Ta le 6

Table 6 − Ta k relate BTM interf ac s

IDtmSin leDe ic DataAc e s Ma d tory

IDtmSin leIn ta c DataAc e s Ma d tory

The man atory interfaces of a BTM ActiveX are s own in Ta le 7

Table 7 − Ta k relate BTM Activ X interf ac s

De en in on the fun tional ty of a Frame Ap lcation, not al interf aces def i ed for a Frame

Table 8 − Ta k relate Frame Appl c tion interf ac s

Furthermore, the pref i es FDT, DTM an BTM are reserved f or identifiers an names defi ed

in the FDT sp cif i ation This prevents con icts of f urther rele ses with private exten ion of

interf aces or defi ition

In general, al FDT interf aces are desig ed with f ieldbu - an man f acturer neutral method

Exten ion f or a new f ieldbu are done via new XML s hemas Fu ctional exten ion for new

tas s wi b provided by new interf aces

5.3 Return v lue of interf ac method

Interface method in icate s c es or fai ure of a method cal by wel defi ed return values

(marked as [out, retval]) COM er ors (HRESULT) s al not b u ed to return FDT f un tion

related er ors, ex e t if it is stated in the sp cif i ation If no return value is def i ed (e.g for al

event method ) it is as umed that the method alway s c e d

5.4 Dual interf ac s

Al interfaces def i ed within the FDT sp cif i ation are implemented as d al interfaces This

7

develo ment lan uages The f un tional ty of an o ject is implemented in se arate tas

oriented interfaces, so that only the default interface is ac es ible via the disp tc interf ace

This prevents mars al n of the extra interf aces to disp tc -only cl ents, but the extra

interf aces can b made avai a le for a disp tc only-cl ent via a wra p r that hold the other

interf aces as pro erties or merges al method to a sin le interf ace

Due to the b ter p rf orman e, the develo er s ould u e the c stom interf ace However, in

general the disp tc interf ace can b ac e ted, b cau e the mars al n time of most of the

FDT method can b neglected comp red with the ru time of e c method

5.5 Unicode

Al strin p rameters to the FDT interf aces are BSTRs an are theref ore UNICODE strin s

Microsof t MIDL Version 3.0 or later is req ired to cor ectly compi e the IDL code an generate

prox /stub sof tware Microsof t Win ows NT 4.0 (or later), or Win ows 9 with DCOM s p ort

is req ired to pro erly han le the mars al n of FDT p rameters

Note that in order to implement FDT sof tware that wi ru on b th Microsof t Win ows NT an

Microsof t Win ows 9 , it is neces ary f or these comp nents to test the platf orm at ru time In

the case of Microsof t Win ows 9 , u ual y the con ersion of an strin s to b p s ed to

impl citly

The only l mitation within this doc ment is that a NUL c aracter (i.e 0) is only al owed as the

last c aracter of an BSTR method p rameter to prevent con ersion er ors (UNICODE

<->ANSI up ercase ->lowercase, etc.) within the data ase

In general e c fun tion cal is s n hronou Within FDT there are two sp cial cases of

• Af ter startin the u er interface of a DTM, the DTM work as n hronou to the Frame

Ap l cation As n hronou in this case me n that the u er work with the DTM an the

Frame Ap l cation is the server for commu ication an data ac es This state en s by a

notif i ation to the Frame Ap l cation, when the DTM closes the u er interf ace

• Whi e a DTM has o ened its u er interface, the DTM u es the as n hronou b havior at

the commu ication interf ace The time a commu ication f un tion cal ne d to return

secon s Dividin a commu ication f un tion cal to a req est an a resp n e f un tion

cau es a non-bloc in b havior without the p in of multi-thre din implementation The

DTM sen s its req est or several req ests without b in disturb d by in omin resp n es

When a resp n e is avaia le, the DTM gets a notif i ation an can receive the resp n e

f rom the commu ication comp nent Due to this mec anism, on one han a DTM s ould

not implement a time ut control an on the other han the commu ication has to provide a

resp n e f or e c req est Only a resp n e can contain the time ut inf ormation

5.7 ProgIds

The u age of progId is l mited to 3 c aracters This decision was made to s p ort C+ ,

Vis al Basic, Java an other COM complant develo ment lan uages

5.8 Impleme tation of DTM, DTM de ic type a d hardware ide tific tion inf ormation

5.8.1 De ic id ntif ic tion

Fig re 10 s ows how the identity information provided by the DTM an the identity information

provided as a s an res lt is con erted an u ed for comp rison

Figure 10 − De ic ide tif ic tion

identif i ation inf ormation of s an ed ph sical devices with identif i ation information of a

DTMDeviceTyp These f iles s al b con erted to a f ieldbu in e en ent f ormat u in a

fieldbu -sp cifi XSL tran f ormation

Protocol spe cific

DTMI de ntifica tio Sche ma

Co mpa re d vice id ntifica tio n

Protool spec ific

device iden fic at i n

c ont ent

Protool spec ific

device iden fic at i n

c ont ent

Protool spec ific

device iden fic at i n

Fig re 1 s ows, how protocol-sp cifi s hemas are integrated in the FDT sp cif i ation an

u ed by Frame Ap l cation an DTMs (HART® example is s own):

Figure 1 − Structural ov rview

IEC

5.8.2 Protocol-spe if ic tra sf ormation style s e t (x l)

As s own in the stru tural overview Fig re 1 , the protocol-sp cif i FDT sp cifi ation

exten ion covers a tran f ormation style s e t (.x l) in ad ition to s hemas This x l is to b

u ed by a Frame Ap l cation in order to con ert the protocol-sp cifi f ormats in lu ed in the

identif i ation (s an an DTM) XML doc ments into strin s The res lt s al b val dated

DTMDeviceTyp IdentSc ema) The output can b u ed by a Frame Ap l cation to comp re

ph sical device typ s by in lu in reg lar expres ion In order to identif y a matc in

DTMDeviceTyp , a Frame Ap l cation s al implement a p t ern matc in ac ordin to the

reg lar expres ion s ntax def i ed in 5.8.5

5.8.3 Sema tic ide tif ic tion inf ormation

Ta le 9 lsts identifi ation elements, whic have to b provided by the s an an DTM

identif i ation mec anism Af ter x l tran formation, the fol owin values s al b avai a le in

DTMDeviceTyp IdentSc ema

Table 9 − Sema tic ide tif ic tion inf ormation

IdSof twareRe isio To l rele a t v rsio of th p y ic l d vic –

Firmware v rsio

IdSerialNumb r In ord r to g t a c mmo d f i itio for al kin of

proto ols, a s rial n mb r is d fin d to b o ly

u iq e for o e ma ufa turer a d d vic ty e

For world wid u iq e id ntif i atio this atrib te

s al alwa s b c mbin d with ma uf acturerID a d

(p) o tio al b t ma b d fin d ma d tory for a s e if i proto ol (s e p rts 3 y)

If a semantic element can ot b def i ed f or a fieldbu protocol, the value s al b set to

’NOT_APPLICABLE’

The comp rison of the s an res lt with DTM device identif i ation inf ormation an the device

as ig ment is done by the Frame Ap l cation b sed on its internal rules

Eac element from the s an doc ment can b comp red with the DTM device identif i ation

information

The element of the DTM device identif i ation doc ment s al matc to the value within the

s an doc ment

5.8.5 Re ular e pre sion spe ific tion

If the element of the DTM device identifi ation doc ment contain a p tern, the Frame

information (se Ta le 10)

Table 10 − Re ular e pre sions

[ ] In ic te ac ara ter cla s Matc e a y c ara ter in id th bra k ts (or e ample, [a c]

matc e "a", "b", a d "c"

^ If this meta h ra ter o c rs at th start of a c ara ter cla s, it n g te th c ara ter cla s

A n g te c ara ter cla s matc e a y c ara ter e c pt th s in id th bra k ts (or

e ample, [^a c] matc e al c ara ters e c pt "a", "b", a d "c" If ^ is at th b gin in of

th re ular e pre sio , it matc e th b gin in of th in ut (or e ample, ^[a c] wi o ly

? , + , *? No -gre d v rsio s of ?, +, a d*.Th s matc a ltle a p s ible, u lk th gre d

v rsio s whic matc a mu h a p s ible Ex mple: giv n th in ut "< b > d f>", <.*?

matc e "< b >" whie <.*> matc e "< b > d f>"

( ) Gro pin o erator Ex mple: ([0-9]+,) [0-9]+ matc e alst of n mb rs s p rate b

c mma (s c a " " or " ,2 ,4 6"

\ Es a e c ara ter: interpret th n xt c ara ter lteraly (or e ample, [0-9]+ matc e o e or

more digits, b t [0-9]+ matc e a digit folowe b a plu c ara ter Als u e for

a bre iatio s (s c a \a for a y alp a umeric c ara ter; s eta leb low)

If \ is f olowe b a n mb r n, it matc e th nth matc gro p (startin fom 0) Ex mple:

5.9.2 Top log import/e port

A Frame Ap l cation not aware of DTMs han l n red n ant slaves is not a le to provide

red n an y information within a FDT to olog exp rt file

element at Chan elNodes if the a pro riate DTM in tan e has not b en ad ed to to olog by

element of the to olog doc ment s ould contain a Bu Information element containin the

red n ant ad res inf ormation

6 Implementation of FDT services: FDT interf aces

6.1 Ov rview of the FDT interf ac s

The FDT interf ace sp cif i ation in lu es the f ol owin :

• Presentation o jects

• FdtChan elActiveXControl

• FdtChan el

The b havior of these o jects an their interf aces are des rib d in detai in this clau e

Develo ers bui din FDT o jects for DTMs or p rts of Frame Ap l cation l ke storage or

commu ication o jects s al implement the fun tional ty def i ed in this clau e

This clau e also referen es an defi es exp cted b havior of b th stan ard COM interfaces

an FDT-sp cif i interf aces that FDT compl ant o jects s al implement

6.2 FDT obje ts

6.2.1 FDT obje t model

These FDT o jects an at le st the interfaces re resent the tas s f or the integration of a field

-device-a plcation into a Frame Ap l cation Al interfaces of a DTM, of a BTM, of a c an el

as wel as the interf aces of the Frame Ap l cation are implemented by one COM o ject so that

a cl ent can ac es them by cal n QueryInterface on one of these interf aces of a server

o ject So, a cl ent is a le to detect avaia i ty of o tional interf aces of e c o ject d rin

ru time

The interfaces provided by DTM, ActiveX an Frame Ap l cation are s own in Fig re 12 an

Fig re 13 Af ter the ActiveX is cre ted by the Frame Ap l cation, the DTM co p rates with

the ActiveX o ject

Pr a ToReleseCom u niction()

ReleseCo mmunictio n()

Pr a ToD elete()

SetL gu a ()

G etFu nctions()

Inv eFu nctio nRequ est()

PrivateD ialoEn led()

O nChidPa meteCha ged()

O nPa meteCh ged()

FrameA pplctio

O pe D ialo ctiveX ontro lReq u est()

O pe Ch nlActiveXontro lReq u est()

Clo seCh nlActiveXontro lReq u est()

O pe D ialoCh n lActiveXo ntrolRequ est()

«int erac e»

IFtA ct iv eX 2

O nAdedRedu ndatChid()

O nRemo vedRedu ndatChid()

IDt mSinleDevicDataA cc sEent s

O nInsta eIemListCha ged()

O nAp lctio nClosed()

O nFu nctionChaged()

O nCh nlFu nctio nCh nged()

O nPrint)

O nNavigation()

O nO nlnStateCha ged()

O nPr a dToRelese()

O nPr a dToReleseCom u niction()

O nInv edFu nctionFinished()

IDt mA udit TraiEent s

OpeActiveXontro lReq u est()

CloseActiveXontro lReq u est()

Figure 13 − Interf ac s of FDT obje t – Frame Appl c tion

resp n es by the interface IFdtCommu icationEvents A hierarc y of c an els an DTMs is

u ed to provide nested commu ication

Init2()

«interac e»

IFt ChanelA ctiveXCot rol2

ScaReq uest()

IF t Chan elSb oolo y 2

Ft ChanelA ct iv eX Cot rol

Init)

Pr a ToRelese()

«int erac e»

IF t ChanelA ctiv eXCo t rol

G etCh nlActiveX u id()

G etCh nlActiveXroId()

G etCh nlFu nctions()

«interac e»

IF tChan elA ct ieX Informat in

G etCh nlPath()

G etCh nlPa metes()

SetCh n lPa metes()

«int erac e»

IFt Chanel

Sc Req u est()

ValdateAdChid()

ValdateRemoeChid()

Disco nn tRequ est()

Tr sactio nRequ est()

The interfaces related to a BTM are s own in Fig re 15

GetPa ntNoes()

GetChidNo des()

in ic te interf ac s s e ific for u e with B Ms

Figure 15 − FDT obje ts – BTM a d BtmActiv XControl

6.2.2 Av labi ty of interfa e methods

The avai a i ty of interface method of the dif ferent o jects may de en on the state of a

DTM in tan e This de en en y is def i ed in Ta le 1 an Ta le 12

Ta le 1 def i es the interf aces of a DTM whic can b u ed by a Frame Ap l cation at the