Verified device applications using Anybus Communicator gateways

Anybus logo Anybus® Communicator™ - Verifed device listing

Product Type:
Energy meter

Brand & Model nr:
Metrima F4 Heat meter M-bus/RS232

Solution Overview:
The examples show how to connect a Metrima F4 Heat meter with M-bus/RS232 option card V.2 (FC2N) to Profibus. The Anybus Communicator is used to link data between Profibus and the RS232 interface of the Metrima F4.

Solution Brief:
The Metrima F4 has to be configured for serial communication with the baud rate of 2400bps and ID=1 as address with the software Flexserv, prior to connection with the Anybus communicator.
In this example the Metrima F4 serial communication parameters has been programmed as shown below:
Baudrate = 2400
Stop bits = 1
Data bits = 8
Parity = Even
Protocol = RS232

When using the Metrima1.cfg.
An Init command will be sent to the Metrima F4, each time the value in the first Output byte is changed by the Profibus master. The response from the Metrima F4 is available in the first Input byte.
The communicator will send the command, Data request, cyclically once per second. The Output data from the Metrima F4, is received by the Anybus Communicator as a variable data object and the whole response will be available in the input area, second byte and onwards, of the communicator (150 Bytes). The PLC will have to mask out the desired data. See the document “mbusflex Fx Metrima power meters.pdf” for a description of the Metrima F4 response telegram.

When using the Metrima2.cfg.
An Init command will be sent to the Metrima F4, each time the value in the first Output byte is toggled by the Profibus master. The response from the Metrima F4 is available in the first Input byte.
The communicator will send the command, Data request, cyclically once per second.
The response from the Metrima F4, is received by the Anybus Communicator, and filtered as described below:
Input byte 2-3: DIF size and VIF (20 – 21)
Input byte 4-7: Energy (22 – 25)
Input byte 8-11: Volume from water meter (28 – 31)
Input byte 12-15: Volume (35 – 38)
Input byte 16-17: Forward temperature (41 – 42)
Input byte 18-19: Return temperature (45 – 46)
Input byte 20-21: Difference temperature (49 – 50)

RS232 Wiring between Anybus Communicator and Metrima F4:
Anybus Communicator Dsub (Sub-network) to Metrima F4:
1 - +5V Output to A2
2 - RS232 Rx to A1
3 - RS232 Tx to A3
5 – Ground to A4

Comments:
The configurations are made for Anbus Communicator for Profibus, but could be used for any of our other Communicators, e.g. DeviceNet, Profinet etc. With Ethernet versions of the Communicator, It is possible to have up to 10 user defined email files, email_1.cfg, email10.cfg. If the user would like to receive an e-mail that is event triggered, for example if a motor exceeds 1000 rpm, it is possible to set that up. For further information read the User manual, which can be downloaded from: www.anybus.com
Note regarding M-bus, the MBUS init-command SND_NKE is sent to put the Metrima F4 telegram pointer to the first telegram. REQ_UD2 is used to read the F4 meter’s first protocol. Additional REQ_UD2 commands can be sent to read out additional protocols from the F4 meter. This method is used if primary addressing is used. See MBDOC48.pdf

Zip File:
 Metrima F4.zip

Disclaimer
The configuration files shown above are provided as a guide to assist you with your own configuration. HMS takes no responsibility or liability for the usage of these files in your product/network setup.