Difference between revisions of "Domnev"

From Teltonika Networks Wiki
 
(223 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
<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>
 +
__TOC__
 +
==Summary==
 +
This article contains instructions on how to send M-Bus data to the server using various protocols.
  
==Introduction==
+
==Configuration overview & prerequisites==
This article contains instructions on how to configure I/O Juggler between two RUT955 routers.
+
Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.
  
==Configuration overview and prerequisites==
+
'''Prerequisites''':
 +
* TRB143;
 +
* M-Bus device;
 +
* Server;
 +
* An end device (PC, Laptop, Tablet, Smartphone) for configuration;
  
Before we begin, let's overview the configuration that we are attempting to achieve and the prerequisites that make it possible. On a RUT1 an I/O Juggler action is created to execute a SMS and Script when Input 1 is being triggered to a state high to change Output state to high on a RUT2.
 
  
# RUT1 Input 1 state changes to a High;
+
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
# RUT1 sends command to RUT2;
+
| series = RUTX
# RUT2 Output(4) state changes to High;
+
}}
  
'''Prerequisites''':
 
* Two RUT955 routers (one of them with SIM card inserted);
 
* 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.
+
==Adding M-Bus devices==
[[File:Basic WebUI Advanced.gif|border|center|class=tlt-border|1004x1004px]]
+
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]]
  
==Via SMS==
+
===Device configuration===
This section contains a detailed guide on how to configure RUT1 and RUT2 devices. When RUT1 Input 1 state changes to a high, a command will send an SMS message to a RUT2 and change the device Output state to a high.
 
===RUT 2===
 
 
----
 
----
RUT2 device configuration.
+
You will be granted to a new window. Configure your M-Bus device accordingly:
====SMS Utilities configuration====
+
 
----
+
# '''Name''': Enter the desired name of the M-Bus device
The [[RUT955_Mobile_Utilities#SMS_Utilities|SMS Utilities section]] contains a list of rules that perform certain actions when they are activated by SMS messages.
+
# '''Address type''': select which M-Bus address will be used
 +
# '''Primary/Secondary address''': specify M-Bus address
  
* Log into Router 2 WebUI;
+
[[File:Mbus adding new device configuration v3.png|border|class=tlt-border]]
* Go to the '''Services → Mobile Utilities → SMS Utilities''' page and scroll down for '''Add new rule''';
 
* Enter '''desired SMS text''' command ('''1''') and '''select action''' ('''2''');
 
* '''Add''' new '''instance''' ('''3''');
 
  
[[File:SMS utils add.png|border|center|class=tlt-border|1004x1004px]]
+
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:
  
After this you should redirected to configuration page for that rule:
+
* If you have specified correct primary/secondary address, you will receive:
[[File:SMS utils SMS config.png|border|center|class=tlt-border|1004x1004px]]
+
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]
  
# '''Open General''' tab;
+
* 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:
# Check '''Enable''';
+
[[File:Mbus device not pingable v2.png|border|class=tlt-border|300px]]
# Action - '''Change I/O state''';
 
# I/O - '''Output(4)''';
 
# State - '''High'''
 
# SMS text - Enter your desired '''SMS text''';
 
# '''Save''' and '''apply''' '''changes''';
 
  
'''Note:''' Not marked fields can be left as default.
+
Once finished, save the configuration by clicking [[File:Savenapply button.png|Savenapply button.png]].
  
===RUT 1===
+
===Scanning for available M-Bus devices===
 
----
 
----
RUT1 devices configration.
 
  
====I/O Juggler 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====
 
----
 
----
The [[RUT955_Input/Output#I.2FO_Juggler|I/O Juggler]] is a feature that provides the possibility to create automated rules that perform certain actions based on Input state changes and other conditions.
+
You will be granted to a new window. Configure scan settings accordingly:
  
=====Actions configuration=====
+
# '''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.
 +
 
 +
====Found devices====
 
----
 
----
The [[RUT955_Input/Output#Actions|Actions section]] is used to manage and create new Actions that can be executed by the I/O Juggler Rules. The figure below is an example of the Actions section, which is empty by default.
+
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:
  
* Log into Router 1 WebUI and go to the '''Services → Input/Output → I/O Juggler → Actions (1)''' page;
+
[[File:Mbus scanned devices add.png|border|class=tlt-border]]
* '''Enter''' the desired action '''instance name (2)''' and select '''desired action type (3)''';
 
* Click '''add (4)''';
 
[[File:IO juggler action sms.png|border|center|class=tlt-border|1004x1004px]]
 
  
This will open a new configuration page:
+
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.
[[File:IO juggler action sms1.png|border|center|class=tlt-border|1004x1004px]]
 
  
# Type - '''SMS''';
+
==Gathering M-Bus data==
# Text message - '''RUT2 password''' and the '''[https://wiki.teltonika-networks.com/wikibase/index.php?title=Domnev&oldid=97995#SMS_Utilities_configuration SMS rule]''' that have been created on RUT2;
 
# Recipient's phone number - RUT2''' SIM cards number''';
 
# '''Save''' and '''apply changes''';
 
  
'''Note:''' Not marked fields can be left as default.
+
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>.
  
=====General configuration=====
+
[[File:Mbus status active v2.png|border|class=tlt-border]]
 +
 
 +
===Data collecting groups===
 
----
 
----
The General section is used to Input Trigger rules, which can perform a specified user-configured action when the Input state changes
+
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.
  
* Once I/O Juggler Action tab is configured, open '''General''' tab ('''1''') and '''enable''' it ('''2''');
+
[[File:Mbus data collect overview.png|border|class=tlt-border]]
* Add '''new instance''' role ('''3''');
 
* Click Add ('''4''');
 
  
[[File:IO juggler general config.png|border|center|class=tlt-border|1004x1004px]]
+
====Data collecting group instance====
 +
----
  
After that, you will be prompted to edit an instance:
+
Each data collection group contains the following information. Configure device accordingly:
  
[[File:IO_Juggler_general_input_config.png|border|center|class=tlt-border|1004x1004px]]
+
# '''Enabled''': on
# Check '''Enable''';
+
# '''Name''': desired name of the instance
# Trigger - '''Raising''';
+
# '''Period''': desired time duration between data retrievals
# Add actions - '''Action name''' that was created previously;
+
# '''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'''.
  
'''Note:''' Not marked fields can be left as default.
+
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
  
==Via Public IP using a script==
+
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:
For this configuration you will need a Static or Dynamic Public IP address. You can read up more on this in our article on [[Private_and_Public_IP_Addresses|Private and Public IP Addresses.]] When RUT1 Input 1 state changes to a high, action will execute a script that contains a curl -X command which will change RUT2 Output state to a high via RUT2 Public IP.
 
  
===RUT 2===
+
[[File:Mbus TEST output.png|border|class=tlt-border]]
 +
 
 +
====Group values====
 
----
 
----
This section contain information on how to configure RUT2 device. A guide on how to [https://wiki.teltonika-networks.com/wikibase/index.php?title=Domnev&oldid=97979#SMS_Utilities_configuration configure SMS Utilities] can be found above.
+
To reach group values configuration press [[File:Pencil2.png]] button:
  
====Remote access configuration====
+
[[File:Mbus edit group values.png|border|class=tlt-border]]
----
 
The Access Control page is used to manage remote and local access to device.
 
  
* Navigate to '''System → Administration → Access Control'''
+
There you can adjust additional settings:
* Open '''General''' tab ('''1''') and locate the '''WebUI section'''('''2''');
 
* '''Enable''' remote '''HTTP''' ('''3''') and '''HTTPS''' access ('''4''');
 
* '''Save''' and '''apply''' '''changes''';
 
  
[[File:Access control rutos1.png|border|center|class=tlt-border|1004x1004px]]
+
# '''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'''
  
====Post/Get configuration====
+
[[File:Mbus device groupsa.png|border|class=tlt-border]]
----
 
Post/Get allows you to perform action requests by writing them in the URL after your device’s IP address.
 
  
* Go to the '''Services → Mobile Utilities → SMS Gateway page → Post/Get (1)''';
 
* '''Enable''' Post/Get '''(2)''';
 
* '''Set a username (3)''' and '''password (4)''';
 
* '''Save''' and '''apply changes (5)''';
 
  
[[File:SMS post get1.png|border|center|class=tlt-border|1004x1004px]]
+
==Sending data to the server==
 +
This section contains information on how to send M-Bus data to the server using MQTT and HTTP protocols.
  
===RUT 1===
+
===Data to Server configuration===
 
----
 
----
This section contain information on how to configure RUT1 device. A guide on how to [https://wiki.teltonika-networks.com/view/Domnev#I.2FO_Juggler_configuration configure I/O Juggler] can be found above.
+
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.
  
=====Actions configuration=====
+
[[File:Mbus data to server create.png|border|class=tlt-border]]
 +
 
 +
===Data configuration===
 
----
 
----
Navigate to '''Services → Input/Output → I/O Juggler''' and create an Action instance.
 
  
[[File:IO juggler script conf.png|border|center|class=tlt-border|1004x1004px]]
+
[[File:Mbus data to server configuration.png|border|class=tlt-border]]
  
# Type - '''Script''';
 
# Specify path - you can choose between '''specifying''' the '''script path''' or '''uploading''' a '''script file''' directly;
 
# Script file - depending on what you have chosen in the field above, you will be asked to enter a '''script directory''' or '''upload a script''' file;
 
# Save and apply changes
 
  
'''Note:''' Not marked fields can be left as default.
+
Once finished configuring Data configuration tab click on [[File:Mbus data to server collection edit.png|160x160px]] button.
  
====Script====
+
===Collection configuration===
 
----
 
----
Script example can be seen below:
 
<pre>#!/bin/sh
 
  
curl -X GET "http://84.25.189.15/cgi-bin/sms_send?username=name&password=password&number=0037066081843&text=admin01 outputon"
+
[[File:Mbus data to server collection configuration.png|border|class=tlt-border]]
  
exit 0</pre>
+
Once finished configuring Collection configuration tab click on [[File:Mbus data to server server button.png|160x160px]] button.
  
More information about '''curl -X''' command syntax can be found [[RUT955_Mobile_Utilities#Post.2FGet|here]].
+
===Server configuration===
 +
----
  
==Via RMS VPN using a script==
+
====HTTP configuration====
For a more secure alternative, RMS VPN could be used to execute a curl -X script.
 
===RMS VPN configuration===
 
 
----
 
----
Go to [http://rms.teltonika-networks.com rms.teltonika-networks.com], log into your RMS account and create a RMS VPN Hub. A guide on how to set up a RMS VPN Hub can be found [https://youtu.be/dfAudZR2wPY here].
 
  
[[File:RMS VPN config IO.png|border|center|class=tlt-border|604x604px]]
+
[[File:Mbus data to server HTTP configuration.png|border|class=tlt-border]]
  
Please make sure that both RUT1 and RUT2 have been added to RMS VPN Hub.
+
====MQTT configuration====
 +
----
  
====Script====
+
[[File:Mbus data to server MQTT configuration.png|border|class=tlt-border]]
----
 
  
Adjust the script accordingly to the RMS VPN Hub assigned IP to RUT2. The script that been used in this example can be found [https://wiki.teltonika-networks.com/wikibase/index.php?title=Domnev&oldid=97995#Actions_configuration_2 here].
+
Once finished configuring Server configuration tab click on [[File:Savenapply button.png|Savenapply button.png]] button.
  
==Results==
 
If configured correctly you should be able to see that when RUT1 Input 1 state is being changed to high, RUT2 Output state changes to a high as well.
 
  
[[File:IO state.gif|border|center|class=tlt-border|1004x1004px]]
+
==See Also==
  
[[File:Output state.gif|border|center|class=tlt-border|1004x1004px]]
+
==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