9,567
edits
Changes
Template:Networking rutos manual mbus (view source)
Revision as of 12:09, 24 October 2023
, 12:09, 24 October 2023Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}"
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
| name = {{{name}}}
==Summary==
==Summary==
The <b>M-Bus (Meter Bus)</b> is a cost-effective fieldbus communication protocol for transmitting energy consumption data. A central master – in this case {{{name}}} – communicates via a two-wire bus (up to max. 250 slaves per segment) with bus devices (e.g., heat meter, water meter, electric meter, gas meter).
The <b>M-Bus (Meter Bus)</b> is a cost-effective fieldbus communication protocol for transmitting energy consumption data. A central client – in this case {{{name}}} – communicates via a two-wire bus (up to max. 250 servers per segment) with bus devices (e.g., heat meter, water meter, electric meter, gas meter).
This manual page provides an overview of the M-Bus functionality in {{{name}}} devices.
This manual page provides an overview of the M-Bus functionality in {{{name}}} devices.
<tr>
<tr>
<td>Baud rate</td>
<td>Baud rate</td>
<td>300 | 600 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400; default: <b>2400</b></td>
<td>300 | 600 | 1200 | 2400 | 4800 | 9600 ; default: <b>2400</b></td>
<td>Specifies the M-Bus slave network baud rate.</td>
<td>Specifies the M-Bus server network baud rate.</td>
</tr>
</tr>
<tr>
<tr>
The <b>M-Bus Record</b> section is used to configure the general record instance. The figure below is an example of the M-Bus Record and the table below provides information on the fields contained in that section:
The <b>M-Bus Record</b> section is used to configure the general record instance. The figure below is an example of the M-Bus Record and the table below provides information on the fields contained in that section:
[[File:Networking_rutos_manual_mbus_record_mbus_record_demo_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_record_mbus_record_demo_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Period</td>
<td>Period</td>
<td>integer [1..86400]; default: <b>none</b></td>
<td>integer [1..86400]; default: <b>60</b></td>
<td>Specifies the period how often record data will be collected.</td>
<td>Specifies the period how often record data will be collected.</td>
</tr>
</tr>
<tr>
<tr>
<td>Failure mode</td>
<td>Failure mode</td>
<td>Never | Any requests failed | All requests failed; default: <b>Never</b></td>
<td>Never | <span style="color: red;">Any requests failed</span> | <span style="color: red;">All requests failed</span>; default: <b>Never</b></td>
<td>Specifies when whole record is considered as failure.</td>
<td>Specifies when whole record is considered as failure.</td>
</tr>
</tr>
<tr>
<tr>
<td>Store a failure message</td>
<td><span style="color: red;">Store a failure message</span></td>
<td>off | on; default: <b>off</b></td>
<td>off | on; default: <b>off</b></td>
<td>Select whether to store a failure message in the database or do nothing on failure.</td>
<td>Select whether to store a failure message in the database or do nothing on failure.</td>
===Request Configuration===
===Request Configuration===
----
----
In this section, you can configure requests from slaves. By default there are no instances created. To add a new instance and start configuring press the <b>Add</b> button.
In this section, you can configure requests from servers. By default there are no instances created. To add a new instance and start configuring press the <b>Add</b> button.
[[File:Networking_rutos_manual_mbus_record_request_configuration_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_record_request_configuration_v2.png|border|class=tlt-border]]
====Request Configuration Edit====
====Request Configuration Edit====
----
----
[[File:Networking_rutos_manual_mbus_record_request_configuration_edit_v1.png|border|class=tlt-border]]
[[File:Networking rutos manual mbus record request configuration edit v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
</tr>
</tr>
<tr>
<tr>
<td>Slave address</td>
<td>Server address</td>
<td>int | hexstring; default: <b>none</b></td>
<td>int | hexstring; default: <b>none</b></td>
<td>Address of the slave to be inquired.</td>
<td>Address of the server to be inquired.</td>
</tr>
</tr>
<tr>
<tr>
<td>Data type</td>
<td>Data type</td>
<td>XML | HEX | BIN; default: <b>XML</b></td>
<td>XML | HEX | BIN | JSON; default: <b>XML</b></td>
<td>Data type to process the received data.</td>
<td>Data type to process the received data.</td>
</tr>
</tr>
<td>string; default: <b>none</b></td>
<td>string; default: <b>none</b></td>
<td>Changes request data to this value if request fails.</td>
<td>Changes request data to this value if request fails.</td>
</tr>
<tr>
<td>FCB toggle</td>
<td>off | on; default: <b>on</b></td>
<td>FCB (Frame Count-Bit): One-bit counter for reliable server-client communication; some devices have special uses for it.</td>
</tr>
</tr>
<tr>
<tr>
[[File:Networking_rutos_manual_mbus_record_request_configuration_edit_test_configuration_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_record_request_configuration_edit_test_configuration_v1.png|border|class=tlt-border]]
[[Category:{{{name}}} Services section]]