IEC PAS 62453-4:2006 pdf download Field Device Tool (FDT) interface specification – Part 4: HART communication
Scope
This part of lEC 62435 provides information for integrating the HART1 protocol into the FDTinterface specification (IEC 62453-1) This PAS neither contains the FDT specification normodifies it.
Normative references
The following referenced documents are indispensable for the application of this PAS. Fordated references, only the edition cited applies. For undated references, the latest edition ofthe referenced document (including any amendments) applies
EC 62453-1: Field Device Tool (FDT) interface specification – Part 1: Concepts and detaileddescription
3 Provided data
3.1Interface IDtmParameter
The minimum set of provided data should be.
The first four provided process related values (PV, SV, …) – if available – are modeled aschannel references. The referenced channel must include ranges and scaling
3.2 SingleDataAccess interfaces
At least all parameters of the Universal and Common Practice (as far as the device supportsthe function) commands must be exposed via the interfaces lDtmSingleDeviceDataAccessand IDtmSinglelnstanceDataAccess.
Furthermore the Response Byte 0 and the Response Byte 1 for each command must beexposed.
4 Protocol specific usage of XML attributes
The following Table 1 shows how general attributes are used with HART devices
5 Bus category
HART protocol is identified by the following unique identifier in busCategory attributes within XML BusCategory elements.
6 FDT sequence charts
6.1 HART burst mode subscription
A subscription of device initiated data transfer can be requested by sending a TransactionRequest with SubscribeRequest content (see Figure 1 ). The Communication Channel may detect if the device is already in Burst Mode. In HART 5 this can be detected only when HART Burst frames are received from the device. In HART 6 the Burst mode can be detected using HART command 1 05. The Communication Channel answers on a SubscribeRequest by calling OnTransactionResponse with a SubscribeResponse content. If HART Burst frames are received, the device is in Burst mode and burstModeDetected value is set to TRUE. This means that device DTM will start to receive Burst messages via OnTransactionResponse mechanism. In case no burst messages were received, burstModeDetected value is set to FALSE. It is up to device DTM to set device into Burst mode. Then device DTM may call TransactionRequest with SubscribeRequest content again in order to receive Burst messages.
In order to unsubscribe, the device DTM sends a TransactionRequest with a UnsubcribeRequest. The Communication Channel answers by calling OnTransactionResponse with a SubscribeResponse where burstModeDetected value is set to FALSE. Device DTM will not receive any more Burst information via OnTransactionResponse mechanism. The Communication Channel does not switch off the Burst Mode in the device. The device DTM may switch Burst Mode on or off by using normal TransactionRequests (HART command 1 09). This is independent of the subscription.
IEC PAS 62453-4:2006 pdf download
PS:Thank you for your support!
