1. Trang chủ
  2. » Kỹ Thuật - Công Nghệ

Iec tr 62453 52 90 2017

46 6 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Thông tin cơ bản

Tiêu đề IEC TR 62453-52-90:2017 - Field device tool (FDT) interface specification – Part 52-90: Communication implementation for common language infrastructure
Trường học Unknown University
Chuyên ngành Electrical Engineering
Thể loại Technical Report
Năm xuất bản 2017
Thành phố Geneva
Định dạng
Số trang 46
Dung lượng 1,05 MB

Các công cụ chuyển đổi và chỉnh sửa cho tài liệu này

Nội dung

A DTM s al provide IO sig al information of the device u in the IProces Data interf ace.. A DTM s al provide al device data that is related to the set of Universal Comman s an s ould pro

Trang 1

IEC TR 62453- 52- 90

Editio 1.0 2 17-0

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

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

inf ast ruct ure – IEC 61784 CPF 9

Trang 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

Trang 3

IEC TR 62453- 52- 90

Edit io 1.0 2 17-0

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

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

inf ast ruct ure – IEC 61784 CPF 9

Trang 4

FOREWORD 5

INTRODUCTION 7

1 Sco e 8

2 Normative ref eren es 8

3 Terms, def i ition , s mb ls, a breviated terms an con ention 8

3.1 Terms an def i ition 8

3.2 Symb ls an a breviated terms 9

3.3 Con ention 9

3.3.1 Datatyp names an referen es to datatyp s 9

3.3.2 Voca ulary for req irements 9

3.3.3 Use of UML

9 4 Bu category 9

5 Ac es to in tan e an device data 9

5.1 General 9

5.2 IO sig als provided by DTM 9

5.3 Data interf aces 10 5.3.1 General 10 5.3.2 Ma pin HART datatyp s to FDT datatyp s 10 5.3.3 SemanticInfo 1

5.3.4 Data exp s re u in IDeviceData an I n tan eData inter aces 12 6 Protocol sp cif i b haviour 18 6.1 Sup ort of burst mode 18 6 2 Device ad res in 1

9 6.3 Sup ort of s an in 19 6.4 Sup ort of exten ed comman n mb rs 19 6.5 Sup ort for han l n of commu ication f ai ures an time-outs 19 6.6 Sup ort for han l n of Delayed Resp n es 2

6.7 Sup ort for to ologies with mixed HART protocols 2

6.8 Sup ort for nested commu ication with multiple gateway 2

6.9 Sup ort for to ologies with Wireles HART 2

6.10 Tran p rent gateway 2

6.10.1 General 2

6.10.2 Scenario 1 – Man al to olog cre tion 2

6.10.3 Scenario 2 – To olog s an an ad 21

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

8 Protocol sp cif i common datatyp s 21

8.1 HartDeviceAd res datatyp 21

8.2 HartDeviceIpAd res datatyp 2

8.3 HartDeviceWireles Ad res datatyp 2

9 Network management datatyp s 2

10 Commu ication datatyp s 2

10.1 General 2

10.2 HartCon ectReq est datatyp 2

10.3 HartCon ectResp n e datatyp 2

10.4 HartL n Ad res datatype 2

Trang 5

10.6 HartDis on ectResp n e datatyp 2

10.7 HartTran actionReq est datatyp 2

10.8 HartTran actionResp n e datatyp 2

10.9 HartStatu datatyp 2

10.10 HartAb rtMes age datatyp 2

10.1 HartSubs rib Req est datatyp 3

10.12 HartSubs rib Resp n e datatyp 3

10.13 HartUn ubs rib Req est datatyp 3

10.14 HartUn ubs rib Resp n e datatyp 31

1 Datatyp s for proces data inf ormation 31

1 1 General 31

1 2 HartIOSig alInfo datatyp 3

12 Device identification datatyp s 3

12.1 General 3

12.2 HartDeviceScanInfo datatyp 3

12.3 HartDeviceIdentInfo datatype 3

12.4 Ma pin of inf ormation source 3

Biblogra h 41

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

Fig re 2 – Stru tural information for device varia les 16 Fig re 3 – Stru tural information for d namic varia les 17 Fig re 4 – Stru tural information for exten ed device statu 18 Fig re 5 – Device-initiated data tran fer with burst mode 19 Fig re 6 – HartDeviceAd res datatyp 21

Fig re 7 – HartDeviceIpAd res datatyp 2

Fig re 8 – HartDeviceWireles Ad res datatyp 2

Fig re 9 – HartNetworkData datatyp 2

Fig re 10 – HartCon ectReq est datatyp 2

Fig re 1 – HartCon ectRespon e datatyp 2

Fig re 12 – HartDis on ectReq est datatyp 2

Fig re 13 – HartDis on ectResp n e datatyp 2

Fig re 14 – HartTran actionReq est datatyp 2

Fig re 15 – HartTran actionResp n e datatyp 2

Fig re 16 – HartAb rtMes age datatyp 2

Fig re 17 – HartSubs rib Req est datatyp 3

Fig re 18 – HartSubs rib Resp n e datatyp 3

Fig re 19 – HartUn ubs rib Req est datatyp 31

Fig re 2 – HartUn ubs rib Resp n e datatyp 31

Fig re 21 – HartIOSig alInf o datatyp 3

Fig re 2 – HartDeviceScanInf o datatyp 3

Fig re 2 – HartDeviceIdentInfo datatyp 3

Ta le 1 – Output sig al info within IOSig alInfo / HartIOSig alInfo 10

Trang 6

Ta le 3 – SemanticInf o at ributes des ription 12

Ta le 4 – Basic Varia les exp rted in IDeviceData an I n tan eData interf aces 13

Ta le 5 – Basic Varia les exp rted only in IDeviceData interf ace 15

Ta le 6 – Protocol sp cific u age of general datatyp s 21

Ta le 7 – HartDeviceAddres datatyp 2

Ta le 8 – HartDeviceIpAd res datatyp 2

Ta le 9 – HartDeviceWireles Ad res datatype 2

Ta le 10 – HartNetworkData datatyp 2

Ta le 1 – HartCon ectReq est datatyp 2

Ta le 12 – HartCon ectResp n e datatyp 2

Ta le 13 – HartL n Ad res datatyp 2

Ta le 14 – HartDis on ectReq est datatyp 2

Ta le 15 – HartDis on ectResp n e datatyp 2

Ta le 16 – HartTran actionReq est datatyp 2

Ta le 17 – HartTran actionResp n e datatyp 2

Ta le 18 – HartStatu datatyp 2

Ta le 19 – HartAb rtMes age datatyp 2

Ta le 2 – HartSubs rib Req est datatyp 3

Ta le 21 – HartSubs rib Resp n e datatyp 3

Ta le 2 – HartUn ubs rib Req est datatyp 31

Ta le 2 – HartUn ubs rib Resp n e datatyp 31

Ta le 2 – Usage of IOSig alInfo datatyp 3

Ta le 2 – HartIOSig alInfo datatyp 3

Ta le 2 – HartDeviceScanInfo datatyp 3

Ta le 2 – Protocol sp cific ma pin of s an inf ormation 3

Ta le 2 – HartDeviceIdentInf o datatyp 3

Ta le 2 – Protocol sp cific ma pin of identity inf ormation 3

Trang 7

INTERNATIONAL ELECTROTECHNICAL COMMISSION

_

Part 52-90: Communication implementation

for common language infrastructure –

IEC 61784 CPF 9

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 cific tio 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 f ter refer e 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 f ormal 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 form 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 ef forts 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 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 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 nf ormity 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 lde 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 f or 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 o 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 r e 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 for 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 commit e may pro ose the publcation of a tec nical re ort when it has col ected

data of a diff erent kin f rom that whic is normaly publs ed as an International Stan ard, for

example "state of the art"

IEC TR 6 4 3-5 -9 , 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 commite 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

IEC 6 4 3-3 9

Trang 8

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 f ou d in the

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

This doc ment has b en draf ted 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 devic to l (FDT)

int era e sp cific tio , can b f ou 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 "htp:/ we store.iec.c " in the data related to

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

• recon rmed,

• with rawn,

• re laced by a revised edition, or

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

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

that it contains colours whic are consid re 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

Trang 9

This p rt of IEC 6 4 3 is an inter ace sp cification f or develo ers of Field Device To l (FDT)

comp nents for f un tion control an data ac es within a clent server arc itecture The

sp cification is a res lt of an analy is an desig proces to develo stan ard interaces 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 rf ormed In ad ition to fieldbu - 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 inter 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, caled 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 f or

al kin of fieldbu ses an th s me ts the req irements for 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 TR 6 4 3-5 -x series is al g ed in the stru ture of

Trang 10

FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICA TION –

Part 52-90: Communication implementation

for common language infrastructure –

This doc ment neither contain the FDT sp cification nor modifies it

The f ol owin 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 ples For u dated ref eren es, the latest edition of the ref eren ed doc ment (in lu in

an amen ments) a pl es

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

IEC 6 4 3-1:2 16, Fiel d devic t ool (FDT) int era e sp cific tion – Part 1: Overview a d

g id an e

IEC 6 4 3-2:2 16, Field de ic to l (FDT) intera e sp cific t ion – Part 2: Con e ts a d

detail ed description

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

int egration profile – Commo l an u g infastru ture

Communic t ion profil e inte rat ion – IEC 617 84 CP F 9

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

HART ® is th tra e n me of a pro u t s p le b HART Commu ic tio Fo n atio This informatio is giv n

for 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

Trang 11

ISO an IEC maintain terminological data ases f or u e in stan ardization at the fol owin

ad res es:

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

• ISO Onl ne browsin platf orm: avai a le at htp:/www.iso.org/o p

3.2 Symbols a d abbre 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 9, an IEC TR 6 45 -4 a ply

3.3 Conv ntions

The con ention f or namin an ref eren in of datatyp s are explained in IEC 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 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

de en in on defined con ition

A DTM s al provide IO sig al information of the device u in the IProces Data interf ace

To provide al inf ormation req ired to ac es the output sig al information the DTM s al

provide the inf ormation s own in Ta le 1 within its HartIOSig alInf o

Trang 12

Table 1 – Output signal inf o within IOSig al nf o / HartIOSignal nf o

– P : IO sig al a sig e to th P d n mic v ria le

– SV: IO sig al a sig e to th SV d n mic v ria le

re s n to oth r FDT v rsio s (e.g

IEC TR 6 4 3-41 , this v ria le c uld b s t to th

v lu 2 2 th t sta d for “u k own”

5.3 Data interfa e

Within HART, several comman sets are defined As p rt of the comman set def i ition,

HART provides a precise namin con ention that is doc mented within the sources of the

stan ard EDD l braries The data provided by the ac es data interf aces s ould b named

ac ordin to the HART namin con ention F r b c ward comp tibi ty, the semantic IDs as

defined in previou version of FDT s ould also b provided by the DTM

A DTM s al provide al device data that is related to the set of Universal Comman s an

s ould provide al device data related to Common Practice Comman sIf the device s p orts

ad itional comman sets, lke device f ami y profi es, those data s ould also b exp rted u in

the namin con ention as defined in the HART EDD l braries an as s own in Fig re 2 an

Fig re 3

5.3.2 Mapping HART datatype to FDT datatype

For a b t er u a i ty of data provided by the data ac es interf aces IDeviceData an

I n tan eData, al data f rom the device s al b con erted into datatyp s that are common to

FDT The ma pin of b sic datatyp s is defined in Ta le 2

_ _ _ _ _ _

Trang 13

Table 2 – Mappin of ba ic datatype

HCF stan ardized the ac es to device sp cific data u in stru tures with the stan ard EDD

imp rt l braries f or HART The stru ture u es ARRAY an COL ECTION con tru ts that s al

b reu ed when exp sin data within FDT in IDeviceData an I n tan eData interf aces with

elements of typ Stru tDataGroup

When con ertin a COL ECTION into a Stru tDataGroup, the DataItems s al b identical to

the COL ECTION memb rs with:

DataItem Name = COL ECTION memb r identif ier

DataItem L b l = COL ECTION memb r la el

When con ertin an ARRAY into a Stru tDataGroup, the DataItem s al b identical to the

ARRAY element with:

DataItem Name = ARRAY element in ex as strin

DataItem L b l = ARRAY element la el

An example for s c a stru ture is presented in Fig re 2 an Fig re 3

5.3.3 Sema ticInf o

The SemanticInfo for HART protocol related p rameters is directly related to the protocol

sp cification The definition of the HART comman s is the b se f or the p rameter addres

ParameterWriteAd res an SemanticId of the SemanticInf o datatyp

The s ntax of the p rameter ad res inf ormation is as folows:

CMD<x>[Q(<r>)]B<y>B<z> <n>

The [Q(<r>)] p rtion only is req ired to define req est data

Trang 14

Table 3 – Sema ticInf o at ribute de cription

< > d cimal inte er c mma d n mb r in th ra g of 0 to 2 5

< > d cimal inte er in e of th start b te in th re p n e d ta s ctio (start in e = 0)

< > d cimal inte er in e of th start bit in th b te ref ere c d b < >

< > d cimal inte er le gth of th v lu in bits

Ac ordin to 6.4, comman s with exten ed comman n mb r s al b des rib d u in

“CMD31Q<r>…” wherein the f irst two byte of the req est data section s al contain the

The pro erty SemanticInfo.Ap lcationDomain s al contain ‘FDT_HART’ for al p rameters in

Ta le 4 an Ta le 5

5.3.4 Data e pos re using IDe ic Data a d I nsta c Data interf ac s

5.3.4.1 Export of ba ic de ic parameters

Usin the HART datatyp ma pin rules introd ced in the precedin section b sic device

p rameters defined within the Universal an Common Practice Comman sets can b

exp rted

Basic p rameters that are not ac es ed u in in ex information in the req est p rt s ould f or

comp tibi ty re son provide ad itional y the SemanticInfo information sp cified in previou

version of FDT Varia les are identif ied by their stan ard identifier in HART In Ta le 4, al

varia les are l sted that s al b exp rted in the related data inter aces when s p orted by the

device HART identif ier s al b as ig ed to the pro erty Data d

Varia les with identifiers starting with “PV.”, ”SV.”, ”TV.” an ”QV.” s al b se n as s ort c ts

to varia les that s al b avai a le to , u in the stru tured exp s re of device varia les as

defined in 5.3.4.2.1

Trang 15

Table 4 – Ba ic Variable e porte in IDe ic Data a d I n ta c Data interfa e

s ctio 6)

NOT Th inf ormatio fom CMD0 is als a aia le

via IHardwareId ntific tio interf ac

re u st_pre mble CMD0B3B0 8 Minimum n mb r of Pre mble re uire f or th re u st

me s g f rom th Ma ter to th Sla e This n mb r

in lu e th two pre mble u e in a y c ro o s

Ph sic l L y rs (alo g with th Delmiter to d te t th

start of me s g

u iv rs l_re isio CMD0B4B0 8 H RT Proto ol Major Re isio Numb r impleme te b

this d vic For H RT Re isio 7, this v lu s al b

th n mb r 7

tra smiter_re isio CMD0B5B0 8 De ic Re isio L v l ( efer to th H F Comma d

Summary Sp cific tio )

s f tware_re isio CMD0B6B0 8 Software Re isio L v l of this d vic L v ls 2 4 a d

2 5 are re erv d

h rdware_re isio CMD0B7B3 5 (Mo t Sig ific nt 5 Bits) Hardware Re isio L v l of

th ele tro ic in this p rtic lar d vic Do s Not

d vic ma uf acture with a giv n De ic Ty e

re p n e_pre mble CMD0B12B0 8 Minimum n mb r of pre mble to b s nt with th

c n g_c a g _c u ter CMD0B14B0 16 Co f i uratio Ch n e Co nter

e te d d_f l _d vic _statu CMD0B16B0 8 Exte d d Field De ic Statu (s e [7], s b e tio

5.17)

ma uf acturer_id CMD0B17B0 16 Ma uf acturer Id ntific tio Co e (s e [7], s b e tio

5.8)

priv te_la el_distrib tor CMD0B19B0 16 Priv te L b l Distrib tor Co e (s e [7], s b e tio 5.8)

p l n _a dre s CMD7B0B0 8 Pol n Ad re s of De ic (efer to [13], s b e tio

P S NSOR_ ERIAL_NUMB R CMD14B0B0 2 Tra s u er Serial Numb r

P DIGITAL_UNIT CMD14B3B0 8 Tra s u er Limits a d Minimum Sp nUnits Co e

(efer to [7], s b e tio 5.2)

P U PER_ ENSOR_LIMIT CMD14B4B0 3 Up er Tra s u er Limit

P LOWER_ ENSOR_LIMIT CMD14B8B0 3 L wer Tra s u er Limit

Trang 16

Identif ier SemanticInf o De criptio

P ALAR _CODE CMD15B0B0 8 P Alarm Sele tio Co e (s e [7], s b e tio 5.6) Th

Alarm Sele tio Co e in ic te th a tio ta e b th

d vic u d r eror c n itio s For tra smiters,th

c d in ic te th a tio ta e b th L o Cure t

For Actu tors, th a tio ta e b th p sitio er is

in ic te

P TRA S ER_ U CTION CMD15B1B0 8 P Tra sfer Fu ctio Co e (s e [7], s b e tio 5.3)

Th Tra sf er Fu ctio Co e s al return "0", Lin ar, if

tra sfer f un tio s are n t s p orte b th d vic

P RA GE U IT CMD15B2B0 8 P Up er a d L wer Ra g Valu s Units Co e (efer

to [7], s b e tio 5.2)

write_prote t CMD15B15B0 8 Write Prote t Co e (s e [7], s b e tio 5.7) Th Write

Prote t Co e s al return "2 1 , No e, wh n write

prote t is n t impleme te b a d vic

P A ALOG_C A NEL_ LAGS CMD15B17B0 8 P An lo Ch n el Fla s (s e [7], s b e tio 5.2 )

fin l_a s mbly_n mb r CMD16B0B0 2 Fin l As embly Numb r

P DIGITAL_UNIT CMD1B0B0 8 Primary Varia le Units ( ef er to [7], s b e tio 5.2)

SV.DIGITAL_UNIT CMD3B9B0 8 Se o d ry Varia le Units Co e (efer to [7], s b e tio

re l_time_clo k_f l g CMD9 B15B0 8 RTC Fla s (efer to [7], s b e tio 5.4 )

Ta le 4 contain data that can also b re d via other inter aces In this case, the DTM s al

take care a out the con isten y of the data E.g the varia les whic are related to CMD0

s al b identical to the HartDeviceScanInf o data, whic can b re d via the IHardwareScan

interace

Ta le 5 lsts al b sic device varia les that s al b exp rted only within IDeviceData interf ace

if s pp rted by the device

Trang 17

Table 5 – Ba ic Variable e porte only in IDe ic Data interfa e

(empty)

De ic statu informatio tra sfere with e c re ly Du to th

fa t th t d vic _statu is a c s ible b sta d rd me n in e c

tra s ctio , th s ma tic inf o is empty

P DIGITAL_V LUE CMD1B1B0 3 Primary Varia le

P A ALOG_V LUE CMD2B0B0 3 Primary Varia le L o Cure t (u its of mi i amp re )

P PERCENT RA GE CMD2B4B0 3 Primary Varia le Perc nt of Ra g (u its of p rc nt)

P DIGITAL_V LUE CMD3B5B0 3 Primary Varia le

SV.DIGITAL_V LUE CMD3B10B0 3 Se o d ry Varia le

TV.DIGITAL_V LUE CMD3B15B0 3 Tertiary Varia le

QV.DIGITAL_V LUE CMD3B2 B0 3 Qu tern ry Varia le

5.3.4.2 Export of structural information

5.3.4.2.1 De ic variable

Beside of the d namic c aracteristic of d namic varia les, there exists data in the device

that is related to the d namic varia le (e.g ran e information, l ne rization fu ction ) In

HART, several categories of s c data information are def i ed an stan ardized me n are

avai a le that al ow to doc ment s c relation hips in a way that a cl ent can ac es an

analy e the stru ture without device sp cific k owled e This information s al b exp rted in

the IDeviceData an I n tan eData interf aces u in Stru tDataGroup elements as mentioned

in 5.3.2

The DTM s al exp se inf ormation in the stru ture as s own in Fig re 2 an Fig re 3

Trang 18

Figure 2 – Structural information f or de ic v riable

IE C

Dev ic eDat aIt ems[

DataIt ems[

:DataInfo

Id : st rin = “DV 1.TR A NS R_FU CTIO “

Name : st rin = “TR A NS R_FUCTIO “

L el : st rin = “Tranfer Fuction“

:Dat a

Name : st rin = "1“

L el : st rin = "Devic e V ariale 1"

:St rutDataGro

Dat aIt ems[

Name : st rin = "DEV ICE_V ARIA BL“

L el : st rin = "Dev ic e V ariale 1"

:St rutDataGro

Id : st rin = “DV 1.DIGITAL_V A LUE“

Name : st rin = “DIGITAL_V A LUE“

L el : st rin = “Digit al Value“

Id : st rin = „DV 1.LOW ER_RANGE_V ALUE"

Name : st rin = "LOW ER_R A NGEVALUE“

L el : st rin = "Lwer Rane"

Dat aIt ems[

Dat aIt ems[

DataIt ems[

Id : st rin = “DV 1.DIGITAL_UNIT“

Name : st rin = “DIGITAL_UNIT“

L el : st rin = “Digit al Unit s“

: UnitData

DataIt ems[

DataIt ems[

Id : st rin = “DV 1.MINIM M_ AN“

Name : st rin = “MINIM M_ AN“

L el : st rin = “Minimu S n“

: Dat a

DataIt ems[

Id : st rin = “D1.ANALO _VALUE“

Name : st rin = “ANALO _V ALUE“

L el : st rin = “Analog Value“

:Dat a

Id : st rin = “D1.ALARM_CO E “

Name : st rin = “ALARM_COE “

L el : st rin = “Alarm Code“

:Dat a

Id : st rin = “D1.ANALO _CHANNE_FLA GS“

Name : stin = “ANALO _C ANNE FA GS“

L el : st rin = “Analog Chanel Flag“

L el : st rin = "Dynamic V ariale 5"

:Strut Dat aGro

Name : st rin = "devic e_variales“

L el : st rin = "Dev ic e V ariales"

c orespdin d v ic e v aria le

This it e sh uld b proid d

if a a alo o t put is

asig e t o t his Deic e

V aria le

Trang 19

Fig re 3 – Structural information for dy amic v riable

Future c an es to the stru ture s al b reflected simi arly

5.3.4.2.2 De ic spe ific status

HART s p orts two typ s of statu inf ormation:

• device statu

This statu is commu icated with the resp n e of e c comman an contain some flag

that des rib the state of the device

This statu is alre d exp sed in IDeviceData with varia le “device statu ”

• additional device statu

This statu inf ormation contain device sp cific inf ormation Us al y it is presented in

HART comman 4 when the “ad itional statu avai a le” f lag is set in the device statu

varia le

To exp se ad itional device statu information via the IDeviceData inter ace a new identifier

is introd ced here The data is exp sed with DataGroup “ad itional_device statu ” Elements

of this data group are referen es to varia les that contain device sp cific statu information

l ke s own in Fig re 4

IE C

Dev ic eDat aIt em ]

:DataInfo

Id : st rin = “PV DYNA MIC_VA R IA BLE S IGNME T“

Name : st rin = “P DY NA MIC_V A R IA LEA SSIGNME T“

L el : st rin = “PV Dynamic V ariale a ig me t “

: Dat a

Dat aIt em ]

Id : st rin = “SV DYNA MIC_VA R IA BLE S IGNME T“

Name : st rin = “SV.DY NA MIC_V A R IA LEA SSIGNME T“

L el : st rin = “SV Dynamic V ariale a ig me t “

: Dat a

DataIt em ]

Name : st rin = "dy namic_v ariale_a igmets“

L el : st rin = "Dynamic V ariale A ssigmet s"

:St rutDat aGroup

Dat a it em prov ides t he

coresp n in value of HART

Com an 5

Trang 20

Fig re 4 – Structural information f or e te de de ic status

SemanticInfo information s al b provided for al varia les referen ed in this group, al owin

external to ls to req est statu information without in tantiation of the DTM

5.3.4.2.3 Exte d d burst a d e e t information

HART 7 introd ced new f eatures in burst information in lu in event notification Data

Pro agation u in these new burst an event management can b config red with stan ard

me n as defined by HART The content of burst mes ages (esp cial y for s b devices) can

b evaluated u in the exp rted stru tural information as presented in the precedin section

Sup ort of this new han l n is not defined in this doc ment It is o en to the DTM develo er

to exp rt ad itional inf ormation with the me n introd ced a ove

6 Protocol specif ic behaviour

6.1 Support of burst mode

Sup ort f or burst mode defined in IEC 6 4 3-3 9:2 16, 6.2 s al b implemented as f ol ows

ISubs ription: <Subs riptionInitial zation( > The Commu ication Chan el may detect if the

device is alre dy in burst mode In HART 5 this can b detected only when HART burst

f rames are received fom the device In HART version 6 or later the burst mode can b

detected u in HART comman 10 If HART Burst f rames are received, the device is in burst

mode an BurstModeDetected pro erty of HartSubs rib Resp n e is set to TRUE This

me n that device DTM wi start to receive burst mes ages via Subs riptionCal b c

mec anism In case that no burst mes ages were received, BurstModeDetected pro erty is

set to FALSE It is up to the device DTM to set the device into burst mode Then the device

DTM may cal ISubs ription: <Subs riptionInitial zation( > again in order to receive burst

Id :st rin = “Dev ice_Spc ificSt a s“

Name : st rin = “Dev ic e_SpcificSt a s“

: Dat a

Dat aIt e s[

Id :st rin = “Ex t en dDev ice_St a s“

Name : st rin = “Ex t en dDev ice_Sta s“

Id :st rin = “Dev ice_Oprat in Mo “

Name : st rin = “Dev ic e_Oprat in Mo “

Trang 21

In order to u s bs rib , the device DTM cal s ISubs ription: <Subs riptionTermination( >.

Device DTM wi not receive an more burst information via Subs riptionCal b c mec anism

The Commu ication Chan el do s not switc of the burst mode in the device The device

DTM may switc burst mode on or of f by u in normal Tran actionReq ests (HART comman

DTMs s al s p ort the IScan in inter ace

DTMs s al s p ort the exten ed comman n mb rs as def i ed in IEC 6 4 3-3 9:2 16, 6.4

6.5 Support for ha dl ng of commu ic tion fai ure a d time-outs

DTMs s al s p ort the han ln of commu ication f aiures an time-outs as defined in

Com u ict i n

Ch n elProx y

gt Su sc ript io int erac e

g t Su sc ript io int erae

<Su script ioInit ialzt io (>

<Susc ript io Init ialzt io (> eec ut io result s

HART Burst Frame

Su script io Calb ck(t ra sac t io Respnse)

<Su script io Termin t io (>

<Su script ioTermin t io(> eec ut io result s

: De ic

Su script ioCalb c k (t rasat ioResp nse)

St arw at chin for

HART Burst Frames

<Su script io Init ialzt io (>

<Su script io Init ialzt io(> eeut io result s

<Su script ioTermin t io(>

<Su sc ript ioTermin t io(> eec ut io result s

Trang 22

6.6 Support for ha dl n of Dela e Re p ns s

DTMs s al s p ort the han l n of Delayed Resp n es as defined in IEC 6 4 3-3 9:2 16,

6.6

6.7 Support for topologie with mix d HART protocols

DTMs s al s p ort to ologies with mixed HART protocols as def i ed in IEC 6 4 3-3 9:2 16,

6.7

The implementation for the protocol c ec f or the method Val dateAd Chi d( is:

• If no cor elation can b fou d in the sp cif i bu categories, the p rent DTM s al an wer

the En Val dateAd Chi d( cal with FALSE

• If a cor elation can b fou d, the En Val dateAd Chi d( cal s al b an wered with

TRUE Durin the Chi dAd ed( cal, the p rent DTM sets the ActiveProtocols pro erty in

the Chi d DTM

6.8 Support for ne te communic tion with multiple gatewa s

DTMs s al s p ort nested commu ication with multiple gateway as def i ed in

IEC 6 4 3-3 9:2 16, 6.8

6.9 Support for topologie with Wirele sHART

DTMs s al s p ort to ologies with Wireles HART as defined in IEC 6 4 3-3 9, 6.9

6.10 Tra spare t gatewa s

HART s p orts variou typ s of ph sical layers l ke HART FSK, HART over Ethernet, HART

over 4 5, HART over Inf rared, etc Becau e of this ran e of ph sical layers, it can b p s ible

that a HART Network contain a gateway device whic con ects nodes s p ortin diff erent

ph sical layers One example for s c gateway device is the Wireles Ada ter whic al ows

con ectin HART FSK devices in a Wireles HART network

Another example for s c gateway device is a HART Inf rared Ada ter, whic may con ect a

HART FSK device to a HART Inf ared Network

It is p s ible that some ada ters a p ar to b tran p rent, i.e they do not act as HART

Nodes on the network They act as ph sical layer ada ter, imp rsonatin the device they are

con ected to Althou h, c r ently there are no Tran p rent Gateway in the market, the HART

protocol do s not restrict the p s ibi ty of s c Tran p rent Gateway /Con erters in the

network

IEC TR 6 4 3-4 req ires that s c tran p rent gateway /ada ters are re resented by a

DTM

With the def i ition of new protocol Id for e c of the HART typ s in order to cre te a

to ology, it is req ired that DTMs are avai a le for e c of the p rticip tin nodes in the

HART network

The f ol owin s enarios explain the b haviour of s c gateway devices in a FDT To olog

6.10.2 Sc nario 1 – Ma ual top logy cre tion

Durin man al to olog cre tion, the HART Inf rared Commu ication DTM only s p orts

Trang 23

To olog , there s al b a Gateway DTM (HART Infared to HART FSK DTM), thou h, the

ada ter is tran p rent

It is man atory that every p rticip tin node in the ph sical network s al have a DTM

avai a le Without this, it is not p s ible to cre te a val d to olog

6.10.3 Sc nario 2 – Topology s a a d a d

In case of s an to olog , the Commu ication DTM may not detect the ada ter (as it is

tran p rent , an hen e the s an res lt wi not return the ada ter In te d, the s an res lt

contain the HART FSK Device However, the HART FSK device can ot b ad ed to the

to ology d e to dif ferent Protocol Id

In s c s enario, u les the ada ter acts as a HART node in the network, it is not p s ible to

cre te the network to ology

7 Protocol specif ic usa e of ge eral dataty es

Ta le 6 s ows how general datatyp s are u ed with IEC 617 4 CPF 9 devices

Table 6 – Protocol spe if ic us ge of ge eral datatype

Fig re 6 an Ta le 7 des rib the datatyp for ad res in information u ed with protocol ID

HART_Basic, HART_ SK, HART_ Wireles , HART_RS4 5 an HART_Inf rared

Us d in:

INetworkData: GetAd res Inf o(

INetworkData: SetDeviceAd res (

ICommu ication: BeginCon ect )

ICommu ication: En Con ect )

IScan in : En ScanReq est )

IEC Hart Dev icA ddres

Pro to colDeviceAdress

Ln A ddres

Hart Lo gA ddres

11

Ngày đăng: 17/04/2023, 11:50

TÀI LIỆU CÙNG NGƯỜI DÙNG

TÀI LIỆU LIÊN QUAN