Date: Fri, 29 Mar 2024 08:27:09 +0100 (CET)
Message-ID: <1431776553.111544.1711697229617@srvdoc.doc.ipesoft.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_111543_899993225.1711697229617"
------=_Part_111543_899993225.1711697229617
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Supported device types and=
versions
Literature
Document revisions
Suppo=
rted device types and versions
HART protocol is not directly implemented in D2000 yet. To communicate w=
ith a HART device it is possible to use one of the HART/Modbus converters b=
y Papouch (www.papouch.com):
- HART RS - HART to Modbus RTU converter (RS485 interfac=
e)
- HART ETH - HART to Modbus TCP converter (ethernet inte=
rface)
A HART communication with an Endress + Hauser Proline t-mass A 150 heat =
flow meter has been deployed into production. The device communicated using=
a HART protocol version 6 with the HART ETH converter, on the D2000 side u=
sing the MODBUS Client pr=
otocol on the TCP/IP-T=
CP line. Following commands were implemented:
- HART command 0 - read a unique identifier - a 5-charac=
ter command whose only parameter is a short device identifier (0-15). The d=
evice response includes, inter alia, data about the supported version of HA=
RT protocol, Manufacturer ID, Manufacturer Device Type, and a 3-byte Device=
Identification Number.
By combining the Manufacturer ID + Manufacturer Device Type + Device Ident=
ification Number, a 5-byte Unique Identifier is created, which is used in v=
ersion 5 for all other commands. Using a Unique Identifier protects against=
communication with a wrong device (which can occur when HART loops are con=
nected and daisy-chained).
- HART command 1 - read the primary variable - reads one=
value (32-bit real number) from the device. A Unique Identifier (obtained =
by command 0) must be used to address the device.
- HART command 3 - read the current and four dynamic var=
iables - reads the value of the current and four preconfigured dynamic vari=
ables (32-bit real numbers) as well as their units from the device. A Uniqu=
e Identifier (obtained by command 0) must be used to address the device.
The flow meter sent values of the mass flow rate, the total flow volume, a=
nd the temperature of the measured gas.
The HART ETH converter from Papouch works as follows:
- Using the MODBUS protocol, it is possible to write the HART packet that=
we want to send, to the converter (to the registers starting at address 52=
). Writing can be done with one or more Modbus write operations by the func=
tion 16 - Write Multiple Registers. According to the manufacturer's documen=
tation, the packet begins with a start byte and does not contain an introdu=
ctory preamble (3 or more 0xFF characters for synchronization of the partie=
s).
- Subsequently, HART communication is triggered by writing the value 0x01=
00 to the converter's register 50. The converter will send the HART packet =
and wait for the answer.
- It is necessary to read the value of the register 50 until it is change=
d from 0x0100 to 0x0200 (successful HART communication) or 0x0000 (error/ti=
meout).
- If the communication was successful, the HART device response can be re=
ad from the registers at address 308 and above. This response must be parse=
d and interpreted.
The composition of HART commands, parsing of HART responses, and reading=
values into user variables were programmed by the means of ESL language.
If interested in this protocol and the relevant ESL scripts, please contac=
t the D2000 development department.
Literature
Document revisions
- Ver. 1.0 - August 21st, 2017 - Document creation.
------=_Part_111543_899993225.1711697229617--