Wireless M-Bus to Wired M-Bus telegram

This part describes how data is mapped from the received wireless M-Bus telegram to the wired M-Bus telegram. The wired secondary address is taken from the M-Field and A-Field from the wireless M-Bus telegram. The wired A-Field is automatically assigned upon installation. The short header information received in the wireless M-Bus telegram is not used on the wired M-Bus interface.

Container

The DIF/VIF Container description is identified by the following DIF/VIF data:

wireless_mbus_container.png

Wireless M-Bus telegrams contained in wired M-Bus container

The wireless M-Bus telegram should be placed in an M-Bus container if one or more of the following criteria are met:

C- and CI-Field are unknown to the product

wireless_mbus.png

Wireless M-Bus telegram

Wired_Mbus_telegram.png

Wired M-Bus telegram

Example 4. Example

080a720369006896151f1b090000000dfd3b2f2e449615036900681f1b7a19002025a057db0548ebc7ec8 4fde94a565d7d34c062c24f190dff14b5ec9f3c9ee7ee470f


Example 5. Example in csv:

wired_mbus_telegram_example_csv.png

M-Bus telegram from CMeX50 and Container

Below follows an example of M-Bus telegram when reading from CMeX50, for more details, please refer to the CMeX50 User Manual.

Wired_mbus_telegram_table.png

Wired M-bus telegram

Example 6. Example in csv:

example_csv_CMeX50.png

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Articles in this section

Comments (0 comments)

Article is closed for comments.