In this section you'll find several sets of downloadable files, ranging from simple forms to join PI to executables to help you engineering and commissioning PROFIBUS and PROFINET devices. Much of it is free, although to get some files you'll need to join PI (Become a member) to gain access. The 'key' icon tells you which file needs a password.
For non-members we offer certain documents for sale. Please find our current literature list with official prices and order form here.
If you are looking for a specific order number please use also the full text search in the upper left hand corner of this website to find your documentation or software.
This specification describes how to communicate HART via PROFIBUS DP. The specification defines a HART application layer which guarantees an interoperable access between different applications and different HART Master Devices. The applications can run either on a PC connected directly to PROFIBUS or on a PC communicating via the system or on the controller itself.
The specification defines:
- communication mechanism on PROFIBUS
- PDUs on PROFIBUS
- state machines
- feature functionalities
This specification standardizes the communication between client applications in HART compatible devices via PROFIBUS DP. Furthermore, it standardizes the nomenclature used with HART-capable PROFIBUS DP Slaves, their configuration, and their operation.
This specification includes:
- Definition of Data Type Application Service Elements,
- Definition of HART Application Service Elements,
- Definition of HART Profile Protocol Data Units,
- Coding of HART Profile Protocol Data Units,
- Definition of HART Master Device State Machines and
- Definition of Device Data Base Key Words.
The revision 2.0 at hand extends the previous version by the mapping of HART variables into the cyclic PROFIBUS DP data. It also covers the HART extensions until HART V7 by describing amongst other things the mapping for WirelessHART Devices and HART Device Variables.
The profile 2.0 does not define security extensions for minimizing the potential system vulnerability during the transport of sensible HART configuration data via PROFIBUS like e.g. the Network Join Keys. This must be done manufacturer-specific, unless the PI Project Group “Security” provides an according profile for PROFINET.
Any device claiming conformances must implement all the mandatory features.
Order No.: 3.102