Difference between revisions of "Domnev"

From Teltonika Networks Wiki
 
(253 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==
 
==Summary==
−
<b>Inputs</b> and <b>outputs</b> are used for monitoring and controlling a connected device or receiving signals from that device in order to trigger certain events.
+
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 overview 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;
  
−
'''Prerequisites''':
 
−
* Two RUT955 routers (one of them with an active data connection)
 
−
* An end device (PC, Laptop, Tablet, Smartphone)
 
−
* Router's LANs should be in different subnet
 
  
−
==Router configuration==
+
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 +
| series = RUTX
 +
}}
  
−
If you have familiarized yourself with the configuration scheme and have all of the devices in order, you can start configuring your routers using instructions provided in this section.
 
  
−
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</b>. . 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.
  
−
==Via SMS==
+
[[File:Mbus adding new device.png||border|class=tlt-border]]
  
−
===RUT 1===
+
===Device configuration===
 
----
 
----
−
====SMS Utilities configuration====
+
You will be granted to a new window. Configure your M-Bus device accordingly:
−
The SMS Utilities section contains a list of rules that perform certain actions when they are activated by SMS messages.
+
 
−
----
+
# '''Name''': Enter the desired name of the M-Bus device
−
* Log into Router 1 WebUI;
+
# '''Address type''': select which M-Bus address will be used
−
* Go to the '''Services → Mobile Utilities → SMS Utilities''' page;
+
# '''Primary/Secondary address''': specify M-Bus address
−
* Enter desired SMS text command ('''1''') and select action ('''2''');
+
 
−
* Add new instance ('''3''');
+
[[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:
  
−
[[File:SMS utils add.png|border|center|class=tlt-border|1004x1004px]]
+
* If you have specified correct primary/secondary address, you will receive:
 +
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]
  
−
After this you should redirected to configuration page for that rule:
+
* 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:SMS utils SMS config.png|border|center|class=tlt-border|1004x1004px]]
+
[[File:Mbus device not pingable v2.png|border|class=tlt-border|300px]]
  
−
# '''Open General''' tab;
+
Once finished, save the configuration by clicking [[File:Savenapply button.png|Savenapply button.png]].
−
# Check '''Enable''';
 
−
# Action - '''Change I/O state''';
 
−
# State - '''High'''
 
−
# SMS text - Enter your desired '''SMS text''';
 
−
# Save and apply changes;
 
  
−
'''Note:''' Not marked fields can be left as default.
+
===Scanning for available M-Bus devices===
−
===RUT 2===
 
 
----
 
----
−
====I/O Juggler configuration====
+
 
−
The 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 can learn more about it [[RUT955_Input/Output#I.2FO_Juggler|here]].
+
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====
 
----
 
----
−
=====Actions tab=====
+
You will be granted to a new window. Configure scan settings accordingly:
−
The 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. You can learn more about it [[RUT955_Input/Output#Actions|here]].
+
 
 +
# '''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====
 
----
 
----
−
Log into Router 2 WebUI and go to the '''Services → Input/Output → I/O Juggler''' page; Then navigate to '''Actions''' and '''create a new instance'''.
+
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:
−
[[File:IO juggler action sms.png|border|center|class=tlt-border|1004x1004px]]
+
 
 +
[[File:Mbus scanned devices add.png|border|class=tlt-border]]
 +
 
 +
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.
 +
 
 +
==Gathering M-Bus data==
  
−
# '''Enter''' the desired action '''instance name''';
+
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>.
−
# Select '''desired type''';
 
−
# Click '''add''';
 
  
−
This will open a new configuration page:
+
[[File:Mbus status active v2.png|border|class=tlt-border]]
−
[[File:IO_juggler_SMS_config_new.png|border|center|class=tlt-border|1004x1004px]]
 
  
−
# Type - '''SMS''';
+
===Data collecting groups===
−
# Text message - enter your '''Router 2 password''' and the '''SMS rule''' that you have created;
+
----
−
# Recipient's phone number - enter Router '''2 SIM cards number''';
+
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.
−
# Save and apply changes
 
  
−
'''Note:''' Not marked fields can be left as default.
+
[[File:Mbus data collect overview.png|border|class=tlt-border]]
  
−
=====General tab=====
+
====Data collecting group instance====
 
----
 
----
  
−
[[File:IO juggler general config.png|border|center|class=tlt-border|1004x1004px]]
+
Each data collection group contains the following information. Configure device accordingly:
  
−
# Open '''General''' tab ('''1''') and enable it ('''2''');
+
# '''Enabled''': on
−
# Add '''new instance''' role ('''3''');
+
# '''Name''': desired name of the instance
−
# Click Add ('''4''');
+
# '''Period''': desired time duration between data retrievals
 +
# '''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'''.
  
−
After that, you will be prompted to edit an instance:
+
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
  
−
# Check '''Enable''';
+
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:
−
# Trigger - '''Raising''';
 
−
# Add actions - Select the action you have created;
 
−
[[File:IO_Juggler_general_input_config.png|border|center|class=tlt-border|1004x1004px]]
 
  
−
==Via Public IP==
+
[[File:Mbus TEST output.png|border|class=tlt-border]]
−
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.]]
 
  
−
===RUT 1===
+
====Group values====
 
----
 
----
−
====Remote access====
+
To reach group values configuration press [[File:Pencil2.png]] button:
−
----
+
 
−
Navigate to '''System → Administration → Access Control''':
+
[[File:Mbus edit group values.png|border|class=tlt-border]]
  
−
[[File:Access control rutos.png|border|center|class=tlt-border|1004x1004px]]
+
There you can adjust additional settings:
  
−
# Open '''General''' tab ('''1''') and locate the '''WebUI section''';
+
# '''Enable''': Enable/disable data group value.
−
# '''Enable''' remote '''HTTP''' ('''2''') and '''HTTPS''' access ('''3''');
+
# '''FCB toggle''': FCB (Frame Count-Bit), one-bit counter for reliable server-client communication.
−
# Save and apply changes ('''4''');
+
# '''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'''  
  
−
'''Note:''' Not marked fields can be left as default.
+
[[File:Mbus device groupsa.png|border|class=tlt-border]]
−
====SMS Gateway configuration====
 
−
----
 
−
Go to the '''Services → Mobile Utilities → SMS Gateway page''';
 
  
−
[[File:SMS post get.png|border|center|class=tlt-border|1004x1004px]]
 
  
−
# Open '''Post/Get''' tab;
+
==Sending data to the server==
−
# Check '''enable''';
+
This section contains information on how to send M-Bus data to the server using MQTT and HTTP protocols.
−
# Enter desired '''username''';
 
−
# '''Password''';
 
−
# '''Confirm password''';
 
−
# Save and apply changes;
 
  
−
===RUT 2===
+
===Data to Server configuration===
 
----
 
----
−
=====Actions tab=====
+
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.
 +
 
 +
[[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''';
+
Once finished configuring Data configuration tab click on [[File:Mbus data to server collection edit.png|160x160px]] button.
−
# 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
 
  
−
Script example can be seen below:
+
===Collection configuration===
−
</b><br><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></li>
+
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 [[RUT955_Mobile_Utilities#Post.2FGet|here]].
+
===Server configuration===
 +
----
  
−
==Via RMS VPN==
+
====HTTP configuration====
 +
----
 +
 
 +
[[File:Mbus data to server HTTP configuration.png|border|class=tlt-border]]
 +
 
 +
====MQTT configuration====
 +
----
  
 +
[[File:Mbus data to server MQTT configuration.png|border|class=tlt-border]]
  
−
==Results==
+
Once finished configuring Server configuration tab click on [[File:Savenapply button.png|Savenapply button.png]] button.
  
−
If configured correctly all of your internet traffic now should go through VPN server.
 
  
−
[[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

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Domnev&oldid=131099"