Difference between revisions of "Domnev"

From Teltonika Networks Wiki
 
(66 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 [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.03.4'''] 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__
−
This article contains instructions on how to setup BACnet on Teltonika Networks devices.
+
==Summary==
−
 
+
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.
  
 
'''Prerequisites''':
 
'''Prerequisites''':
−
* RUT955;
+
* TRB143;
−
* BACnet controller;
+
* M-Bus device;
 
* Server;
 
* Server;
 
* 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:Networking rutx manual webui basic advanced mode.gif|border|center|class=tlt-border|1004x1004px]]
 
  
−
'''Note''': It is a additional software that can be installed from the '''Services → [[RUT955_Package_Manager|Package Manager]]''' page.
+
{{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.
 +
 
 +
[[File:Mbus adding new device.png||border|class=tlt-border]]
 +
 
 +
===Device configuration===
 +
----
 +
You will be granted to a new window. Configure your M-Bus device accordingly:
 +
 
 +
# '''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===
 +
----
 +
 
 +
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====
 +
----
 +
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.
  
−
== BACnet MS/TP configuration ==
+
====Found devices====
−
Master - Slave Token Passing (MSTP) is most commonly used to connect field devices to controllers / routers / control applications. The physical layer uses RS485 which allows up to 128 devices to be installed on a single network.
+
----
 +
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:
  
−
=== BACnet ===
+
[[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==
 +
 
 +
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>.
 +
 
 +
[[File:Mbus status active v2.png|border|class=tlt-border]]
 +
 
 +
===Data collecting groups===
 
----
 
----
−
Install the BACnet package on RUT955 and navigate to '''Services → BACnet''' and '''enable''' the '''instance'''. Everything else can be left as default or changed according to your needs.
+
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.
  
−
<<SCREENSHOT>>
+
[[File:Mbus data collect overview.png|border|class=tlt-border]]
  
−
=== Server ===
+
====Data collecting group instance====
 
----
 
----
−
For the server, Yet Another BACnet Explorer (YABE) is used. Open the software and '''click''' on '''add device'''
 
  
−
<<SCREENSHOT>>
+
Each data collection group contains the following information. Configure device accordingly:
  
−
Then select local endpoint IO address and leave everything else as default or change according to your needs.
+
# '''Enabled''': on
 +
# '''Name''': desired name of the instance
 +
# '''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'''.
  
−
<<SCREENSHOT>>
+
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
  
−
Select newly created communication node and right - click on it to send '''WhoIs''' request (application  might send these automatically).
+
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:
  
−
<<SCREENSHOT>>
+
[[File:Mbus TEST output.png|border|class=tlt-border]]
  
−
=== Results ===
+
====Group values====
 
----
 
----
−
In case of success you see the connected BACnet device and its parameters.
+
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'''
  
−
<<SCREENSHOT>>
+
[[File:Mbus device groupsa.png|border|class=tlt-border]]
  
−
== BACnet/IP configuration ==
+
 
−
This is the most commonly used type of BACnet, which is designed to work over Ethernet networks using the Internet Protocol (IP). It supports both IPv4 and IPv6 addressing.
+
==Sending data to the server==
−
=== BACnet ===
+
This section contains information on how to send M-Bus data to the server using MQTT and HTTP protocols.
 +
 
 +
===Data to Server configuration===
 
----
 
----
−
Install the BACnet package on RUT955 and navigate to '''Services → BACnet''' → '''enable''' the '''instance''' and '''BBMD'''. Everything else can be left as default or changed according to your needs.
+
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.
  
−
<<SCREENSHOT>>
+
[[File:Mbus data to server create.png|border|class=tlt-border]]
  
−
=== Firewall ===
+
===Data configuration===
 
----
 
----
−
The configuration will also require you to add port forward rule in the firewall configuration. To do that, open Router1 WebUI and navigate to '''Network → Firewall → Port Forwards'''. Create a port forward rule to forward UDP packets from Router2 WAN to Router1 LAN address port.
 
  
−
<<SCREENSHOT>>
+
[[File:Mbus data to server configuration.png|border|class=tlt-border]]
  
−
'''Note''': When YABE sends registration packets you will need to find out which port YABE is using (One way is to look through the traffic with wireshark on your PC or TCP dump on router 1 or router 2)
 
  
−
If you restart YABE software or delete and create new communication device, YABE might use different port number, and you will need to change port forward configured in router connected to your PC.  
+
Once finished configuring Data configuration tab click on [[File:Mbus data to server collection edit.png|160x160px]] button.
  
−
=== Server ===
+
===Collection configuration===
 
----
 
----
−
Open YABE and create IP communication node by click on '''add device'''.
 
  
−
<<SCREENSHOT>>
+
[[File:Mbus data to server collection configuration.png|border|class=tlt-border]]
  
−
Then select the node and go to '''Meniu → Functions → IP services → Foreign device registration''' and enter public IP address of Router2 (the one connected to controller).
+
Once finished configuring Collection configuration tab click on [[File:Mbus data to server server button.png|160x160px]] button.
  
−
<<SCREENSHOT>>
+
===Server configuration===
 +
----
  
−
=== Results ===
+
====HTTP configuration====
 
----
 
----
−
In case of success you see the device connected via gateway.
 
  
−
<<SCREENSHOT>>
+
[[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]]
 +
 
 +
Once finished configuring Server configuration tab click on [[File:Savenapply button.png|Savenapply button.png]] button.
 +
 
  
−
== See also ==
+
==See Also==
−
[[RUT955_BACnet|BACnet]] on RUT955
 
  
−
== External links ==
+
==External links==
−
[https://sourceforge.net/projects/yetanotherbacnetexplorer/ Yabe]
+
[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"