Difference between revisions of "Domnev"

From Teltonika Networks Wiki
 
(125 intermediate revisions by the same user not shown)
Line 1: Line 1:
<p style="color:red">The information in this page is updated in accordance with 00.07.03.1 firmware version .</p>
+
<p style="color:red">The information on this page is updated in accordance with the [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.08'''] firmware version .</p>
==Introduction==
+
__TOC__
 +
==Summary==
 
This article contains instructions on how to send M-Bus data to the server using various protocols.
 
This article contains instructions on how to send M-Bus data to the server using various protocols.
  
==Configuration overview and prerequisites==
+
==Configuration overview & prerequisites==
 
 
 
Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.
 
Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.
  
Line 13: Line 13:
 
* An end device (PC, Laptop, Tablet, Smartphone) for configuration;
 
* An end device (PC, Laptop, Tablet, Smartphone) for configuration;
  
If you're having trouble finding any page or some of the parameters described here on your device's WebUI, you should turn on '''"Advanced WebUI"''' mode. You can do that by '''clicking''' the '''"Basic"''' button '''under''' '''"Mode,"''' which is located at the top-right corner of the WebUI.
 
[[File:TRB143 advanced.gif|border|center|class=tlt-border|1004x1004px]]
 
  
==Node-RED installation and setup==
+
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 +
| series = RUTX
 +
}}
  
==Configuration==
 
  
===Data to server===
+
==Adding M-Bus devices==
Data to Server feature provides you with the possibility to set up data senders that collect data from various sources and periodically send it to remote servers.
+
To add a new device to the configuration press [[File:Add Button.png|60x90px]] button which is shown below.
 +
 
 +
[[File:Mbus adding new device.png||border|class=tlt-border]]
 +
 
 +
===Device configuration===
 
----
 
----
====Via MQTT====
+
You will be granted to a new window. Configure your M-Bus device accordingly:
This sections contains information on how to send M-Bus data to the server on Node-RED using MQTT protocol.
+
 
 +
# '''Name''': Enter the desired name of the M-Bus device
 +
# '''Address type''': select which M-Bus address will be used
 +
# '''Primary/Secondary address''': specify M-Bus address
 +
 
 +
[[File:Mbus adding new device configuration v3.png|border|class=tlt-border]]
 +
 
 +
Test if the M-Bus device is reachable by a specified primary/secondary address. To do so click on [[File:Ping_device_option_mbus.png|110x110px]]. You might get on of two outputs:
 +
 
 +
* If you have specified correct primary/secondary address, you will receive:
 +
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]
 +
 
 +
* If you have specified incorrect primary/secondary address, you will receive (if you do not know what address should be used, refer to the Scanning for available M-Bus devices (PRIDET URL) secion:
 +
[[File:Mbus device not pingable v2.png|border|class=tlt-border|300px]]
 +
 
 +
Once finished, save the configuration by clicking [[File:Savenapply button.png|Savenapply button.png]].
 +
 
 +
===Scanning for available M-Bus devices===
 
----
 
----
=====Data to Server configuration=====
+
 
 +
If you are not sure what address your M-Bus devices have, you can try scanning for the available M-Bus devices. To do so click on [[File:Scan button.png]] button.
 +
 
 +
====Scan settings====
 
----
 
----
'''[[File:Mbus data to server MQTT.png|border|class=tlt-border|954x954px]]'''
+
You will be granted to a new window. Configure scan settings accordingly:
  
# '''Enable''' instance;
+
# '''Scan type''': select which M-Bus address will be scanned
# '''Name:''' enter desired instance name;
+
# '''Scan range''': From what M-Bus address scanning will start and M-Bus address until scanning will be performed.
# '''Data source:''' M-bus;
+
[[File:Mbus scan.png|border|class=tlt-border]]
# '''Protocol:''' MQTT;
+
 
# '''JSON format:''' enter what data you would like to send;
+
To start the scan click on [[File:Start scan button.png]] button.
# '''URL/Host/Connection string:''' enter address of server;
+
 
# '''Port:''' enter server port;
+
====Found devices====
# '''Topic''': enter desired topic name;
 
=====M-Bus configuration=====
 
 
----
 
----
[[File:M bus configuration correct.png|border|class=tlt-border|954x954px]]
+
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:
 +
 
 +
[[File:Mbus scanned devices add.png|border|class=tlt-border]]
  
# '''Enable''' M-Bus;
+
You can either [[File:Pencil2.png]] '''(1)''' M-Bus devices primary address or [[File:Add Button.png|60x90px]] '''(2)''' to the M-Bus devices list.
# Enter desired '''instance name''';
 
# '''Add''';
 
  
[[File:M bus instance configuration.png|border|class=tlt-border|954x954px]]
+
==Gathering M-Bus data==
  
# '''Enable''' instance;
+
If the device successfully added to the list, under the General settings you should see that the Status changes to <span style="color:green">Active</span>.
# '''Period''': enter desired period;
 
# BLOGAS - NAME NEREIKIA
 
  
[[File:M bus slave configuration.png|border|class=tlt-border|954x954px]]
+
[[File:Mbus status active v2.png|border|class=tlt-border]]
  
# '''Enable''' request configuration;
+
===Data collecting groups===
# '''Slave address:''' enter desired slave address;
 
# '''Data type:''' select desired data type (this time we will be using '''XML''');
 
# '''Save & apply''' changes.
 
=====Node-RED configuration=====
 
 
----
 
----
Below you can see Node-Red block diagram that is used to receive data:
+
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.
* aedes broker
+
 
* MQTT in
+
[[File:Mbus data collect overview.png|border|class=tlt-border]]
* Debug
+
 
[[File:Node-rs-topology.png|border|center|class=tlt-border|654x654px]]
+
====Data collecting group instance====
 
----
 
----
  
[[File:Node-red-broker-configuration.png|border|left|class=tlt-border|454x454px|left]]
+
Each data collection group contains the following information. Configure device accordingly:
[[File:Node-red-debug-config.png|border|right|class=tlt-border|537x537px|right]]
+
 
<table class="nd-othertables_2" style="display: inline-table;">
+
# '''Enabled''': on
    <tr>
+
# '''Name''': desired name of the instance
        <td width=755; style="border-bottom: 1px solid white;">
+
# '''Period''': desired time duration between data retrievals
# '''MQTT Port''': 1883;
+
# '''Data type''': desired data type to process the received data. Depending on your needs you can select between 5 different data types: '''JSON, XML, ASCII, Hexadecimal''' and '''Binary'''.
# '''WS Bind''': port;
+
 
# '''Done''';
+
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
Everything else can be left as default.
+
 
</td>
+
You can check if your configuration works accordingly by pressing the [[File:Mbus test button.png]] button. You should see the data in a pop-up field:
<td width=755; style="border-bottom: 1px solid white;">
+
 
# '''Output''': msg. payload;
+
[[File:Mbus TEST output.png|border|class=tlt-border]]
# '''To''': debug window;
 
# '''Done''';
 
Everything else can be left as default.
 
</td>
 
    </tr>
 
</table>
 
  
 +
====Group values====
 
----
 
----
[[File:Node-red-subscriber-configuration.png|border|class=tlt-border|1094x1094px]]
+
To reach group values configuration press [[File:Pencil2.png]] button:
 +
 
 +
[[File:Mbus edit group values.png|border|class=tlt-border]]
 +
 
 +
There you can adjust additional settings:
 +
 
 +
# '''Enable''': Enable/disable data group value.
 +
# '''FCB toggle''': FCB (Frame Count-Bit), one-bit counter for reliable server-client communication.
 +
# '''Manufacturer information''': Select to include manufacturer information in the payload.
 +
# '''Selected parameters''': Select to include the all parameters saved from device, or a custom subset of them. If the custom is selected you can specify '''frame''', '''record''' numbers and also a '''paramater'''
 +
 
 +
[[File:Mbus device groupsa.png|border|class=tlt-border]]
 +
 
  
# '''Server''': Server name;
+
==Sending data to the server==
# '''Action''': Subscribe to single topic
+
This section contains information on how to send M-Bus data to the server using MQTT and HTTP protocols.
# '''Topic''': Created topic;
 
# '''QoS''': 0;
 
# '''Output''': auto-detect;
 
# '''Edit''':
 
# '''Server & Port''': Server IP & Port;
 
# '''Update''':
 
# '''Done''':
 
  
=====Results=====
+
===Data to Server configuration===
 
----
 
----
 +
To set up Data to Server, navigate to Services → Data to Server. Enter desired name of the instnace and hit [[File:Add Button.png|60x90px]] button which is shown below.
  
====Via HTTP====
+
[[File:Mbus data to server create.png|border|class=tlt-border]]
This sections contains information on how to send M-Bus data to the server on Node-RED using HTTP protocol.
+
 
 +
===Data configuration===
 
----
 
----
=====Data to Server configuration=====
+
 
 +
[[File:Mbus data to server configuration.png|border|class=tlt-border]]
 +
 
 +
 
 +
Once finished configuring Data configuration tab click on [[File:Mbus data to server collection edit.png|160x160px]] button.
 +
 
 +
===Collection configuration===
 
----
 
----
[[File:mbus data to server http.png|border|class=tlt-border|954x954px]]
 
  
<table class="nd-mantable">
+
[[File:Mbus data to server collection configuration.png|border|class=tlt-border]]
    <tr>
 
        <th class="left">Number</th>
 
        <th class="left">Field</th>
 
      <th class="left">Value</th>
 
    </tr>
 
<tr>
 
      <td class="left">1</td>
 
        <td class="left">'''Enable'''</td>
 
      <td class="left">'''On'''</td>
 
    </tr>
 
<tr>
 
        <td class="left">2</td>
 
      <td class="left"">'''Name'''</td>
 
      <td class="left">'''Your desired name'''</td>
 
    </tr>
 
<tr>
 
        <td class="left">3</td>
 
      <td class="left">'''Data source'''</td>
 
      <td class="left">'''M-Bus data'''</td>
 
    </tr>
 
<tr>
 
        <td class="left">4</td>
 
      <td class="left">'''Protocol'''</td>
 
      <td class="left">'''HTTP(s''')</td>
 
    </tr>
 
<tr>
 
        <td class="left">5</td>
 
      <td class="left">'''JSON format'''</td>
 
      <td class="left">'''What data to send'''</td>
 
    </tr>
 
<tr>
 
        <td class="left">6</td>
 
      <td class="left">'''URL/Host/Connection string'''</td>
 
      <td class="left">'''Server IP address'''</td>
 
    </tr>
 
</table>
 
=====M-Bus configuration=====
 
----
 
[[File:Mbus config HEX data.png|border|class=tlt-border|954x954px]]
 
  
# '''Enable''' request configuration;
+
Once finished configuring Collection configuration tab click on [[File:Mbus data to server server button.png|160x160px]] button.
# '''Slave address:''' enter desired slave address;
 
# '''Data type:''' select desired data type (this time we will be using '''HEX''');
 
# '''Save & apply''' changes.
 
  
=====Node-RED configuration=====
+
===Server configuration===
 
----
 
----
  
=====Results=====
+
====HTTP configuration====
 
----
 
----
  
===MQTT broker===
+
[[File:Mbus data to server HTTP configuration.png|border|class=tlt-border]]
MQTT Broker is an entity that listens for connections on the specified port and relays received messages to MQTT client.
+
 
 +
====MQTT configuration====
 
----
 
----
=====MQTT broker configuration=====
 
----
 
[[File:Mbus MQTT Broker.png|border|class=tlt-border|954x954px]]
 
  
=====M-Bus configuration=====
+
[[File:Mbus data to server MQTT configuration.png|border|class=tlt-border]]
----
+
 
=====Node-RED configuration=====
+
Once finished configuring Server configuration tab click on [[File:Savenapply button.png|Savenapply button.png]] button.
----
+
 
=====Results=====
 
----
 
  
 
==See Also==
 
==See Also==
* [[TRB143_M-Bus|M-Bus]]
+
 
* [[TRB143_Data_to_Server|Data to Server]]
 
* [[TRB143_MQTT#MQTT_Broker|MQTT Broker]]
 
 
==External links==
 
==External links==
 +
[https://flespi.io/#/ Flespi.io]

Latest revision as of 09:32, 22 August 2024

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

Summary

This article contains instructions on how to send M-Bus data to the server using various protocols.

Configuration overview & prerequisites

Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.

Prerequisites:

  • TRB143;
  • M-Bus device;
  • Server;
  • An end device (PC, Laptop, Tablet, Smartphone) for configuration;


If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.

Networking rutos manual webui basic advanced mode 75.gif


Adding M-Bus devices

To add a new device to the configuration press Add Button.png button which is shown below.

Mbus adding new device.png

Device configuration


You will be granted to a new window. Configure your M-Bus device accordingly:

  1. Name: Enter the desired name of the M-Bus device
  2. Address type: select which M-Bus address will be used
  3. Primary/Secondary address: specify M-Bus address

Mbus adding new device configuration v3.png

Test if the M-Bus device is reachable by a specified primary/secondary address. To do so click on Ping device option mbus.png. You might get on of two outputs:

  • If you have specified correct primary/secondary address, you will receive:

Mbus device pingable v2.png

  • If you have specified incorrect primary/secondary address, you will receive (if you do not know what address should be used, refer to the Scanning for available M-Bus devices (PRIDET URL) secion:

Mbus device not pingable v2.png

Once finished, save the configuration by clicking Savenapply button.png.

Scanning for available M-Bus devices


If you are not sure what address your M-Bus devices have, you can try scanning for the available M-Bus devices. To do so click on Scan button.png button.

Scan settings


You will be granted to a new window. Configure scan settings accordingly:

  1. Scan type: select which M-Bus address will be scanned
  2. Scan range: From what M-Bus address scanning will start and M-Bus address until scanning will be performed.

Mbus scan.png

To start the scan click on Start scan button.png button.

Found devices


Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:

Mbus scanned devices add.png

You can either Pencil2.png (1) M-Bus devices primary address or Add Button.png (2) to the M-Bus devices list.

Gathering M-Bus data

If the device successfully added to the list, under the General settings you should see that the Status changes to Active.

Mbus status active v2.png

Data collecting groups


To reach data collecting groups configuration press Pencil2.png button. Add Button.png button lets you to create a new instance.

Mbus data collect overview.png

Data collecting group instance


Each data collection group contains the following information. Configure device accordingly:

  1. Enabled: on
  2. Name: desired name of the instance
  3. Period: desired time duration between data retrievals
  4. Data type: desired data type to process the received data. Depending on your needs you can select between 5 different data types: JSON, XML, ASCII, Hexadecimal and Binary.

Mbus data collect group v2.png

You can check if your configuration works accordingly by pressing the Mbus test button.png button. You should see the data in a pop-up field:

Mbus TEST output.png

Group values


To reach group values configuration press Pencil2.png button:

Mbus edit group values.png

There you can adjust additional settings:

  1. Enable: Enable/disable data group value.
  2. FCB toggle: FCB (Frame Count-Bit), one-bit counter for reliable server-client communication.
  3. Manufacturer information: Select to include manufacturer information in the payload.
  4. Selected parameters: Select to include the all parameters saved from device, or a custom subset of them. If the custom is selected you can specify frame, record numbers and also a paramater

Mbus device groupsa.png


Sending data to the server

This section contains information on how to send M-Bus data to the server using MQTT and HTTP protocols.

Data to Server configuration


To set up Data to Server, navigate to Services → Data to Server. Enter desired name of the instnace and hit Add Button.png button which is shown below.

Mbus data to server create.png

Data configuration


Mbus data to server configuration.png


Once finished configuring Data configuration tab click on Mbus data to server collection edit.png button.

Collection configuration


Mbus data to server collection configuration.png

Once finished configuring Collection configuration tab click on Mbus data to server server button.png button.

Server configuration


HTTP configuration


Mbus data to server HTTP configuration.png

MQTT configuration


Mbus data to server MQTT configuration.png

Once finished configuring Server configuration tab click on Savenapply button.png button.


See Also

External links

Flespi.io