IEC 62453-309:2009 pdf free download

IEC 62453-309:2009 pdf free download Field device tool (FDT) interface specification – Part 309: Communication profile integration – IEC 61784 CPF 9
scope
Communication Profile Family 9 (commonly known as HART@1) defines communicationprofiles based on lEC 61158-5-20 and lEC 61158-6-20.The basic profile CP 9/1 is defined iniEC 61784-1.
This part of lEC 62453 provides information for integrating the HART@technology into theFDT standard (IEC62453-2).
This part of the lEC 62453 specifies communication and other services.
This standard neither contains the FDT specification nor modifies it.
2Normative references
The following referenced documents are indispensable for the application of this specification.For dated references, only the edition cited applies. For undated references, the latest editionof the referenced document (including any amendments) applies
IEC 61158-5-20，Industrial communication networks – Fieldbus specifications – Part 5-20:Application layer service definition – Type 20 elements
IEC 61158-6-20，Industrial communication networks – Fieldbus specifications – Part 6-20:Application layer protocol specification – Type 20 elements
IEC 61784-1,Industrial communication networks – Profiles – Part 1 : Fieldbus profiles
IEC 62453-1:2009，Field Device Tool (FDT) interface specification – Part 1: Overview andguidance
IEC 62453-2:2009，Field Device Tool(FDT) interface specification – Part 2: Concepts anddetailed description
3Terms, definitions,symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document，the terms and definitions given in IEC 62453-1 andlEC 62453-2 and the following apply.
3.1.1
burst mode
mode in which the field device generates response telegrams without request telegram from the master
3.2 Abbreviated terms
For the purposes of this document, the abbreviations given in IEC 62453-1 , IEC 62453-2 and the following apply.
BACK Burst ACKnowledge
UML Unified Modelling Language
3.3 Conventions
3.3.1 Data type names and references to data types
The conventions for naming and referencing of data types are explained in IEC 62453-2,Clause A.1
3.3.2 Vocabulary for requirements
The following expressions are used when specifying requirements.
Usage of “shall” or
“mandatory”
No exceptions allowed.
Usage of “should” or
“recommended”
Strong recommendation. It may make sense in special
exceptional cases to differ from the described behaviour.
Usage of “can’ or “optional’ Function or behaviour may be provided, depending on defined conditions.
3.3.3 Use of UML
Figures in this document are using UML notation as defined in Annex A of IEC 62453-1 .
4 Bus category
IEC 61 784 CPF 9 protocol is identified in the protocolId element of structured data type ‘fdt:BusCategory’ by the following unique identifier (Table 1 ):
5 Access to instance and device data
5.1 Process Channel objects provided by DTM
The minimum set of provided data shall be:
• the first four provided process related values (PV, SV, …) – if available – are modeled as channel references. The referenced channel shall include ranges and scaling.
5.2 DTM services to access instance and device data
The services InstanceDataInformation and DeviceDataInformation shall provide access to at least to all parameters of the Universal and Common Practice commands (as far as the device supports the function).