Template:Networking rutos manual mbus: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
No edit summary
Line 117: Line 117:
     </tr>
     </tr>
</table>
</table>


[[File:Networking_rutos_manual_mbus_client_data_collecting_groups_value_edit.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_client_data_collecting_groups_value_edit.png|border|class=tlt-border]]
Line 229: Line 231:
     </tr>
     </tr>
</table>
</table>


[[File:Networking_rutos_manual_mbus_gateway_configuration_settings_security.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_gateway_configuration_settings_security.png|border|class=tlt-border]]
Line 274: Line 278:
     </tr>
     </tr>
</table>
</table>


[[File:Networking_rutos_manual_mbus_gateway_configuration_settings_advanced.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_gateway_configuration_settings_advanced.png|border|class=tlt-border]]
Line 344: Line 350:
     </tr>
     </tr>
</table>
</table>
The <b>M-Bus Settings</b> section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section:
[[File:Networking_rutos_manual_mbus_mbus_settings_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enable</td>
        <td>off | on; default: <b>off</b></td>
        <td>Enables the service.</td>
    </tr>
    <tr>
        <td>Baud rate</td>
        <td>300 | 600 | 1200 | 2400 | 4800 | 9600 ; default: <b>2400</b></td>
        <td>Specifies the M-Bus server network baud rate.</td>
    </tr>
    <tr>
        <td>Database location</td>
        <td>RAM memory | Flash memory; default: <b>RAM memory</b></td>
        <td>Specifies where the database will be stored..</td>
    </tr>
</table>
==Records==
By default there are no <b>Records</b> instances created. To start configuring, add a new record using the <b>Add New Instance</b> section below.
[[File:Networking_rutos_manual_mbus_records_add_new_instance_v1.png|border|class=tlt-border]]
----
===M-Bus Record===
----
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_v4.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enable</td>
        <td>off | on; default: <b>off</b></td>
        <td>Enables the service.</td>
    </tr>
    <tr>
        <td>Name</td>
        <td>string; default: <b>none</b></td>
        <td>Name used for distinguishing purposes.</td>
    </tr>
    <tr>
        <td>Period</td>
        <td>integer [1..86400]; default: <b>60</b></td>
        <td>Specifies the period how often record data will be collected.</td>
    </tr>
    <tr>
        <td>String before data</td>
        <td>string; default: <b>none</b></td>
        <td>String that will be appended before request data.</td>
    </tr>
    <tr>
        <td>String between data</td>
        <td>string; default: <b>none</b></td>
        <td>String that will be appended between request data.</td>
    </tr>
    <tr>
        <td>String after data</td>
        <td>string; default: <b>none</b></td>
        <td>String that will be appended after request data.</td>
    </tr>
    <tr>
        <td>Failure mode</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>
    </tr>
    <tr>
        <td><span style="color: red;">Store a failure message</span></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>
    </tr>
</table>
===Request Configuration===
----
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_v2.png|border|class=tlt-border]]
====Request Configuration Edit====
----
[[File:Networking rutos manual mbus record request configuration edit v4.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enable</td>
        <td>off | on; default: <b>off</b></td>
        <td>Enables request processing.</td>
    </tr>
    <tr>
        <td>Server address</td>
        <td>int | hexstring; default: <b>none</b></td>
        <td>Address of the server to be inquired.</td>
    </tr>
    <tr>
        <td>Data type</td>
        <td>XML | HEX | BIN | JSON; default: <b>XML</b></td>
        <td>Data type to process the received data.</td>
    </tr>
    <tr>
        <td>Error value</td>
        <td>string; default: <b>none</b></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>
        <td>Reset after read</td>
        <td>off | on; default: <b>off</b></td>
        <td>Resets the device after every read.</td>
    </tr>
    <tr>
        <td>Test configuration</td>
        <td>button; default: <b>-</b></td>
        <td>Tests the current configuration.</td>
    </tr>
</table>
====Test Configuration====
----
Before saving, you can check if your configuration works accordingly by pressing the <b>Test Configuration</b> button. You should see the data in a field below:
[[File:Networking_rutos_manual_mbus_record_request_configuration_edit_test_configuration_v1.png|border|class=tlt-border]]


[[Category:{{{name}}} Services section]]
[[Category:{{{name}}} Services section]]

Revision as of 14:25, 2 July 2024

The information in this page is updated in accordance with firmware version .

Summary

The M-Bus (Meter Bus) 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.

Client

General settings

The M-Bus device configuration section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section:

Field Value Description
Status Inactive | Active Status of service, whether it is currently running. If it is active, it will also show how long it has been running.
Baud rate 300 | 600 | 1200 | 2400 | 4800 | 9600 ; default: 2400 Specifies the M-Bus server network baud rate.

The Devices section is used to configure the general device instance. The figure below is an example of the M-Bus device and the table below provides information on the fields contained in that section:

Devices

Field Value Description
Name String; default: Device 1 Display name of device configuration.
Address type Primary | Secondary ; default: Primary Primary address which will be used when sending requests.
Primary address integer [0..250]; default: empty Primary address which will be used when sending requests.
Secondary address string of 16 symbols; default: empty A unique device identifier which commonly includes the serial number.


Data collecting groups

Before saving, you can check if your configuration works accordingly by pressing the Test Configuration button. You should see the data in a pop-up field.

Field Value Description
Enabled on | off; default: off Button to enable/disable data collecting group.
Period integer [0..86400]|; default: 60 Time duration between data retrievals (in seconds).
Data type JSON | XML | ASCII | Hexadecimal | Binary; default: JSON Data type to process the received data.
Test Interactive button A unique device identifier which commonly includes the serial number.


Field Value Description
Enabled on | off; default: off Button to enable/disable data group value.
FCB toggle on | off; default: off FCB (Frame Count-Bit): One-bit counter for reliable server-client communication. Some devices may have different uses for it.
Manufacturer information on | off; default: off Should manufacturer information be included in the payload.
Selected parameters All | Custom; default: All Should all parameters be saved from device, or a custom subset of them.
Frame number integer [0..15]|; default: 60 Frame number.
Record number integer [0..63]|; default: 60 Record number.
Parameter id | frame | Function | StorageNumber | Tariff | Device | Unit | Value | Timestamp; default: id Parameter.

Gateway

M-Bus device configuration

The M-Bus device configuration section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section:

Field Value Description
Enabled on | off; default: off Button to enable/disable service.
Baud rate 300 | 600 | 1200 | 2400 | 4800 | 9600 ; default: 2400 Specifies the M-Bus server network baud rate.


Configuration settings

Field Value Description
Mode Server | Client | Client+server | Bidirect(legacy mode, not recommended); default: Server
  • Server - launches service in server mode and listens on the selected port.
  • Client - launches service in client mode, which connects to one or several servers with the selected addresses and ports.
  • Client + server - launches service in server and client(s) mode simultaneously.
  • Bidirect(legacy) - launches service in bidirect mode, which means that the service keeps changing between server and client modes. If server mode fails it switches to client mode and vice versa.
Protocol TCP | UDP; default: TCP Select which protocol to use for data transmission.
Listening port integer [1..65535]; default: empty Specify port number for server to listen.


Field Value Description
Use TLS/SSL on | off; default: off Button to use TLS/SSL for connection.
TLS version tlsv1.0 | tlsv1.1 | tlsv1.2 | tlsv1.3 | Support all ; default: Support all Minimum TLS version allowed to be used.
TLS type Certificate based | Pre-Shared-Key based; default: Certificate based Select the type of TLS encryption.
Pre-Shared-Key hexadecimal string of symbols; default: empty The pre-shared-key in hex format with no leading “0x”.
Identity string of symbols; default: empty Specify the identity.
Require certificate on | off; default: on Demand certificate and key from peer and verify them against certificate authority.
Certificate files from device on | off; default: off Choose this option if you want to select certificate files from device.


Field Value Description
Raw mode on | off; default: on Enable to transmit all data transparently.
Remove all zeros on | off; default: off Remove all zero bytes from received data.
Inactivity timeout integer [0..36000] ; default: 300 Specifies period of time in seconds, where server connection must be inactive, to disconnect client. To disable timeout input 0.
Serial timeout integer [0..1000] ; default: empty Specifies the maximum milliseconds to wait for serial data.
Max clients integer [1..32] ; default: 4 Specify (1-32) how many clients are allowed to connect simultaneously.
TCP echo on | off; default: off Software TCP echo.
Close connections on | off; default: off Close TCP connections everytime data is sent or received (might result in serial data loss).
Keep alive on | off; default: off Enable keep alive.


IP filter

Field Value Description
Allow IP IPv4 and IPv6 addresses with or without mask prefix are accepted. E.g 192.168.1.0/24. Allow IP connecting to server, write 0.0.0.0/0 for allowing all

[[Category:{{{name}}} Services section]]

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rutos_manual_mbus&oldid=128417"