Difference between revisions of "Domnev"

From Teltonika Networks Wiki
 
(109 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
 +
}}
 +
 
 +
 
 +
==Adding M-Bus devices==
 +
To add a new device to the configuration press [[File:Add Button.png|60x90px]] button which is shown below.
  
We are going to set up Node-RED in Linux virtual machine. For Node-RED to work, you would need to install Node.js version 14.00 or higher, if you already have Node.js installed, verify Node.js version using this command:
+
[[File:Mbus adding new device.png||border|class=tlt-border]]
<pre>
+
 
node -v
+
===Device configuration===
</pre>
 
If you do not have Node.js installed, run these commands to install it:
 
<pre>
 
sudo apt install curl
 
curl -fsSL https://deb.nodesource.com/setup_14.x | sudo -E bash –
 
sudo apt-get install -y nodejs
 
</pre>
 
Once we have Node.js installed, we can install Node-RED. Use this command to install:
 
<pre>
 
sudo npm install -g –unsafe-perm node-red
 
</pre>
 
Use the command ''node-red'' to start a local server. Here is how the terminal should look like if the server starts correctly:
 
[[File:Server is running node red terminal.png|border|600px|class=tlt-border]]
 
 
----
 
----
Once you have the local server running, use the local IP and port number in your internet browser. In this case, we are using 127.0.0.1:1880:
+
You will be granted to a new window. Configure your M-Bus device accordingly:
[[File:Use server address in web browser.png|border|500px|class=tlt-border]]
 
  
For MQTT usage, we are going to need MQTT-specific nodes. Use the side menu to navigate to Manage Palette section and install these nodes:
+
# '''Name''': Enter the desired name of the M-Bus device
*node-red-contrib-aedes
+
# '''Address type''': select which M-Bus address will be used
*node-red-contrib-mqtt-broker
+
# '''Primary/Secondary address''': specify M-Bus address
  
[[File:Manage palette and download these mqtt nodes.png|border|500px|class=tlt-border]]
+
[[File:Mbus adding new device configuration v3.png|border|class=tlt-border]]
  
==Configuration==
+
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:
  
===M-Bus Data to Server via MQTT===
+
* If you have specified correct primary/secondary address, you will receive:
This sections contains information on how to send M-Bus data to the server on Node-RED using MQTT protocol.
+
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]
====Data to Server configuration====
+
 
 +
* 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===
 
----
 
----
[[File:Mbus data to server MQTT renewed.png|border|class=tlt-border|1094x1094px]]
 
  
# '''Enable''' instance;
+
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.
# '''Name:''' enter desired instance name;
+
 
# '''Data source:''' M-bus;
+
====Scan settings====
# '''Protocol:''' MQTT;
 
# '''JSON format:''' enter what data you would like to send;
 
# '''URL/Host/Connection string:''' enter address of server;
 
# '''Port:''' enter server port;
 
# '''Topic''': enter desired topic name;
 
====M-Bus configuration====
 
 
----
 
----
[[File:M bus configuration correct.png|border|class=tlt-border|954x954px]]
+
You will be granted to a new window. Configure scan settings accordingly:
 +
 
 +
# '''Scan type''': select which M-Bus address will be scanned
 +
# '''Scan range''': From what M-Bus address scanning will start and M-Bus address until scanning will be performed.
 +
[[File:Mbus scan.png|border|class=tlt-border]]
 +
 
 +
To start the scan click on [[File:Start scan button.png]] button.
  
# '''Enable''' M-Bus;
+
====Found devices====
# Enter desired '''instance name''';
+
----
# '''Add''';
+
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:
  
[[File:M bus instance creation.png|border|class=tlt-border|954x954px]]
+
[[File:Mbus scanned devices add.png|border|class=tlt-border]]
  
# '''Enable''' instance;
+
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.
# '''Period''': enter desired period;
 
# BLOGAS - NAME NEREIKIA
 
  
[[File:HEX data type.png|border|class=tlt-border|954x954px]]
+
==Gathering M-Bus data==
  
# '''Enable''' request configuration;
+
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>.
# '''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====
 
----
 
Below you can see Node-Red block diagram that is used to receive data:
 
* aedes broker
 
* MQTT in
 
* Debug
 
[[File:Node-rs-topology.png|border|center|class=tlt-border|654x654px]]
 
----
 
  
[[File:Node-red-broker-configuration.png|border|left|class=tlt-border|454x454px|left]]
+
[[File:Mbus status active v2.png|border|class=tlt-border]]
[[File:Node-red-debug-config.png|border|right|class=tlt-border|537x537px|right]]
 
<table class="nd-othertables_2" style="display: inline-table;">
 
    <tr>
 
        <td width=755; style="border-bottom: 1px solid white;">
 
# '''MQTT Port''': 1883;
 
# '''WS Bind''': port;
 
# '''Done''';
 
Everything else can be left as default.
 
</td>
 
<td width=755; style="border-bottom: 1px solid white;">
 
# '''Output''': msg. payload;
 
# '''To''': debug window;
 
# '''Done''';
 
Everything else can be left as default.
 
</td>
 
    </tr>
 
</table>
 
  
 +
===Data collecting groups===
 
----
 
----
[[File:Node-red-subscriber-configuration.png|border|class=tlt-border|1094x1094px]]
+
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.
  
# '''Edit:Configure''' MQTT-Broker node;
+
[[File:Mbus data collect overview.png|border|class=tlt-border]]
# '''Name''': Enter desired MQTT-Broker nodes name:
 
# '''Server''': 127.0.0.1 as we will be using Node-RED as MQTT-Broker;
 
# '''Port''': 1883;
 
# '''Update''': Save the changes;
 
# '''Server''': Select MQTT-Broker that you have just created;
 
# '''Action''': Subscribe to single topic;
 
# '''Topic''': Enter the topic that you have set in Data to Server configuration;
 
# '''Qos''': 0;
 
# '''Output''': Auto-Detect;
 
  
====Results====
+
====Data collecting group instance====
 
----
 
----
If you have taken all of the steps described above, the configuration is done. Below you can see M-Bus data output in HEX format.
 
[[File:MQTT broker HEX data.png|border|class=tlt-border|554x554px]]
 
  
===M-Bus Data to Server Via HTTP===
+
Each data collection group contains the following information. Configure device accordingly:
----
 
This sections contains information on how to send M-Bus data to the server on Node-RED using HTTP protocol.
 
====Data to Server configuration====
 
----
 
[[File:Mbus HTTP data to server config.png|border|class=tlt-border|954x954px]]
 
  
====M-Bus configuration====
+
# '''Enabled''': on
----
+
# '''Name''': desired name of the instance
[[File:Mbus XML data type.png|border|class=tlt-border|954x954px]]
+
# '''Period''': desired time duration between data retrievals
 +
# '''Data type''': desired data type to process the received data. You can choose from JSON, XML, ASCII, Hexadecimal and Binary formats.
  
# '''Enable''' request configuration;
+
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.
# '''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====
+
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
----
 
  
====Results====
 
----
 
If you have taken all of the steps described above, the configuration is done. Below you can see M-Bus data output in XML format.
 
[[File:XML data Mbus.png|border|class=tlt-border|404x404px]]
 
===MQTT broker===
 
This sections contains information on how to send M-Bus data to the server on Node-RED using Teltonika router as a MQTT Broker.
 
----
 
=====Data to Server configuration====
 
----
 
[[File:MQTT broker data to server config.png|border|class=tlt-border|954x954px]]
 
=====MQTT broker configuration=====
 
----
 
[[File:Mbus MQTT Broker.png|border|class=tlt-border|954x954px]]
 
  
=====M-Bus configuration=====
 
----
 
[[File:Mbus BIN data type.png|border|class=tlt-border|954x954px]]
 
=====Node-RED configuration=====
 
----
 
=====Results=====
 
----
 
If you have taken all of the steps described above, the configuration is done. Below you can see M-Bus data output in BIN format.
 
[[File:MQTT BIN data.png|border|class=tlt-border|404x404px]]
 
 
==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 14:06, 24 July 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. You can choose from JSON, XML, ASCII, Hexadecimal and Binary formats.

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 data collect group v2.png


See Also

External links

Flespi.io