Domnev: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
No edit summary
 
(48 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 set up BACnet on Teltonika Networks devices.
==Summary==
 
This article contains instructions on how to send M-Bus data to the server using various protocols.
BACnet provides a standardized way for devices from different manufacturers to communicate with each other and integrate seamlessly into a building automation system. This allows building managers and operators to monitor and control various building systems from a central location, optimizing energy efficiency, reducing operating costs, and improving occupant comfort and safety.
==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''':
* Two RUT955;
* TRB143;
* Controller;
* M-Bus device;
* BACnet Server;
* Server;
* An end device (PC, Laptop) for configuration;
* An end device (PC, Laptop, Tablet, Smartphone) for configuration;
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = RUTX
}}
 
==Adding M-Bus devices==
The '''[[TRB143_M-Bus|M-Bus Settings]]''' section is used to configure the general service functionality. To set up a new M-Bus instance, go to '''Services → M-Bus → Client'''. 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:


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.
# '''Name''': Enter the desired name of the M-Bus device
[[File:Networking rut9 manual webui basic advanced mode.gif|border|center|class=tlt-border|1102x52px]]
# '''Address type''': select which M-Bus address will be used
# '''Primary/Secondary address''': specify M-Bus address


'''Note''': This is additional software that can be installed from the '''Services → [[RUT955_Package_Manager|Package Manager]]''' page.
[[File:Mbus adding new device configuration v3.png|border|class=tlt-border]]


== BACnet/Ethernet 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:


[[File:BACnet Topology 1.png|border|center|class=tlt-border|800x260px|]]
* If you have specified correct primary/secondary address, you will receive:
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]


The controller is directly connected to RUT955 via RS485; The router forwards the data from the controller to the BACnet server to the PC.
* 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:
=== BACnet ===
[[File:Mbus device not pingable v2.png|border|class=tlt-border|300px]]
----
Install the BACnet package on RUT955 and navigate to '''Services → BACnet''' and '''enable''' the '''instance'''. Everything else can be left as is or changed to suit your needs.


[[File:BACnet enable instance.png|border|center|class=tlt-border|818x210px]]
Once finished, save the configuration by clicking [[File:Savenapply button.png|Savenapply button.png]].


=== Server ===
===Scanning for available M-Bus devices===
----
----
For the server, Yet Another BACnet Explorer (YABE) is used. YABE is an open-source BACnet Explorer that is designed to be lightweight, fast, and easy to use.


Open the software and '''click''' on the '''green plus sign (top left)''' to add a new device. Then a new window will pop up; there, select the '''local endpoint IP address '''and click '''Start'''. Everything else can be left as is or changed to suit your needs.
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.


[[File:Yabe configuration add device fixed.png|border|center|class=tlt-border|639x203px]]
====Scan settings====
----
You will be granted to a new window. Configure scan settings accordingly:


Select the newly created communication node and right-click on it to '''send''' '''WhoIs''' request (application  might send these automatically).
# '''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]]


[[File:Yabe whois.png|border|center|class=tlt-border|364x126px]]
To start the scan click on [[File:Start scan button.png]] button.


=== Results ===
====Found devices====
----
----
In cases of success, you see the connected BACnet device and its parameters.
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:


[[File:Yabe successful connection.png|border|center|class=tlt-border|914x530px]]
[[File:Mbus scanned devices add.png|border|class=tlt-border]]


== BACnet/IP via LTE configuration ==
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.
Bacnet BBMD – stands for "BACnet Broadcast Management Device." A BBMD is a device that manages the routing of BACnet broadcast messages across different IP subnets. When a BACnet device sends a broadcast message, it is typically sent to all devices on the same subnet, but not to devices on other subnets. However, sometimes it is necessary for broadcast messages to be sent to devices on multiple subnets. This is where a BBMD comes in.


[[File:BACnet Topology 2.png|border|center|class=tlt-border|876x321px]]
==Gathering M-Bus data==


In this topology, there are two RUT955 routers - RUT1 and RUT2. RUT1 is connected to the server via LAN, and RUT2 is connected to the controller via RS485. RUT2 transmits data to RUT1, which then forwards it to the BACnet server.
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>.


For this configuration, you must have a public IP address. You can read more on this in our article on '''[[Private and Public IP Addresses]]'''.
[[File:Mbus status active v2.png|border|class=tlt-border]]


=== Router 1 ===
===Data collecting groups===
----
----
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.


==== BACnet ====
[[File:Mbus data collect overview.png|border|class=tlt-border]]
 
====Data collecting group instance====
----
----
Bacnet BBMD – stands for "BACnet Broadcast Management Device." A BBMD is a device that manages the routing of BACnet broadcast messages across different IP subnets. When a BACnet device sends a broadcast message, it is typically sent to all devices on the same subnet, but not to devices on other subnets. However, sometimes it is necessary for broadcast messages to be sent to devices on multiple subnets. This is where a BBMD comes in.


Navigate to '''Services → BACnet''', there:
Each data collection group contains the following information. Configure device accordingly:
#'''Enable''' BACnet
#'''Enable''' BBMD
#'''BBMD interface''' - select LAN interface
#'''Enable Port forward''' - this will automatically create a port forward rule.
[[File:BACnet router1.png|border|center|class=tlt-border|746x222px]]Also, change the BIP form to a port of Yabe. There are two ways of finding the port of YABE, one way is to look through the traffic with Wireshark on your PC or TCP dump on RUT1 or RUT2


# '''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'''.


Bacnet BIP - Bacnet devices can use BIP to communicate with each other over local area networks (LANs), wide area networks (WANs), and the internet. BIP defines how BACnet messages are encapsulated within IP packets and transmitted between BACnet devices over IP networks.
[[File:Mbus data collect group v2.png|border|class=tlt-border]]


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:


'''Note''': If you restart the YABE software or delete and recreate a new communication device, YABE may use a different port number, in which case you must change the port forward configuration in the router connected to your PC.  
[[File:Mbus TEST output.png|border|class=tlt-border]]


==== Firewall ====
====Group values====
----
----
By enabling the port forward in the BACnet configuration, you created the port forward rule. Nevertheless, the rule requires some modification. To do that, open the RUT1 WebUI and navigate to '''Network → Firewall → Port Forwards'''. Create a port forward rule to forward UDP packets from RUT2 WAN to the RUT1 LAN address port.
To reach group values configuration press [[File:Pencil2.png]] button:


[[File:Router1 firewall port forward.png|border|center|class=tlt-border|797x617px]]
[[File:Mbus edit group values.png|border|class=tlt-border]]


# '''Enable''' instance
There you can adjust additional settings:
# '''Name''' - enter desired name
# '''Protocol''' - UDP
# '''Source zone''' - WAN
# '''External port''' - YABE port
# '''Internal zone''' - LAN
# '''Internal IP address''' - PC LAN IP
# '''Internal port''' - YABE port


'''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 RUT1 or RUT2)
# '''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'''


If you restart the YABE software or delete and recreate a new communication device, YABE may use a different port number, in which case you must change the port forward configuration in the router connected to your PC.  
[[File:Mbus device groupsa.png|border|class=tlt-border]]


=== Router 2 ===
 
==Sending data to the server==
The '''[[TRB143_Data_to_Server|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. This section will walk you through configuring the Data to Server to send M-Bus data to the desired HTTP or MQTT server.
 
===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.


==== BACnet ====
[[File:Mbus data to server create.png|border|class=tlt-border]]
 
===Data configuration===
----
----
Navigate to '''Services → BACnet''', there:


# '''Enable''' BACnet
Each data collection group contains the following information. Configure device accordingly:
# '''Enable''' BBMD
# '''BBMD interface''' - select the interface with Public IP.
# '''Enable Port forward''' - this will automatically create a port forward rule.


[[File:BACnet_enabled_BBMD_fixed.png|border|center|class=tlt-border|797x234px]]
# '''Name''': desired name of the instance
# '''Type''': M-Bus data
# '''Format''': custom or JSON depending on a need.


Everything else can be left as default or changed according to your needs.
[[File:Mbus data to server configuration.png|border|class=tlt-border]]


==== Firewall ====
 
Once finished configuring Data configuration tab click on [[File:Mbus data to server collection edit.png|160x160px]] button.
 
===Collection configuration===
----
----
If you would like manually creating a port forward rule, navigate to '''Network → Firewall → Port Forwards'''.


[[File:BACnet firewall router2.png|border|center|class=tlt-border|864x620px]]
[[File:Mbus data to server collection configuration.png|border|class=tlt-border]]


# '''Enable''' instance
Once finished configuring Collection configuration tab click on [[File:Mbus data to server server button.png|160x160px]] button.
# '''Name''' - enter desired name
# '''Protocol''' - UDP
# '''Source zone''' - WAN
# '''External port''' - 47808
# '''Internal zone''' - LAN
# '''Internal IP address''' - Router LAN IP
# '''Internal port''' - 47808


=== Server ===
===Server configuration===
----
----
Open the software and '''click''' on the '''green plus sign (top left)''' to add a new device. Then a new window will pop up; there, select the '''local endpoint IP address ''' and click '''start'''. Everything else cane be left as default or changed according to your needs.
This section contains information on how to configure MQTT and HTTP servers information.


[[File:Yabe configuration add device fixed.png|border|center|class=tlt-border|639x203px]]
====HTTP configuration====
----


Then select the node and go to '''Meniu → Functions → IP services → Foreign device registration''' and enter the public IP address of RUT2 (the one connected to controller).
# '''Type''': HTTP
# '''Server address''': desired server address


[[File:Yabe IP services.png|border|center|class=tlt-border|414x163px]]
'''Note''': not specified fields are optional.


=== Results ===
[[File:Mbus data to server HTTP configuration.png|border|class=tlt-border]]
 
====MQTT configuration====
----
----
In case of success, you see the device connected via gateway.
[[File:Yabe 2 successful.png|border|center|class=tlt-border|925x501px]]


==BACnet/IP via RMS VPN configuration==
# '''Type''': MQTT
If having a public IP is not an option, RMS VPN could be used as an alternative to access your device over the internet. [https://teltonika-networks.com/lt/about-us/introducing-rms-vpn-service/ RMS VPN] is a service designed for remote efficient, low-cost management of large-scale networks. In contrast to point-to-point VPN services, RMS VPN enables the instant creation of encrypted VPN tunnels for secure access to multiple endpoints.
# '''Server address''': desired server address
# '''Topic''': MQTT topic to be used for publishing the data.


===RMS VPN===
'''Note''': not specified fields are optional.
----
A guide on how to set up an RMS VPN hub can be found [https://youtu.be/dfAudZR2wPY here].


[[File:RMS VPN BACnet fixed.png|border|center|class=tlt-border|995x500px]]
[[File:Mbus data to server MQTT configuration.png|border|class=tlt-border]]


Both RUT1 and RUT2 have to be added to the RMS VPN Hub.
Once finished configuring Server configuration tab click on [[File:Savenapply button.png|Savenapply button.png]] button.


=== RUT1 & RUT2 ===
===Results===
----
----
Once RMS VPN Hub is set up, follow the RUT1 and RUT2 configuration described above.
== See also ==
[[RUT955_BACnet|BACnet]] on RUT955
[[RUT955 Firewall#Port Forwards|Port-forward]] on RUT955


== External links ==
[[File:Mbus data received v2.png|border|class=tlt-border]]
[https://sourceforge.net/projects/yetanotherbacnetexplorer/ Yabe]


[https://rms.teltonika-networks.com/|Teltonika RMS]
'''Note''': received data formating depends on the settings you apply under Data to Server and M-Bus configurations.

Latest revision as of 07:20, 25 October 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.

Adding M-Bus devices

The M-Bus Settings section is used to configure the general service functionality. To set up a new M-Bus instance, go to Services → M-Bus → Client. Add a new device to the configuration press button which is shown below.

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

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

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

  • 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:

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 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.

To start the scan click on button.

Found devices

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

You can either (1) M-Bus devices primary address or (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.

Data collecting groups

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

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.

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

Group values

To reach group values configuration press button:

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


Sending data to the server

The 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. This section will walk you through configuring the Data to Server to send M-Bus data to the desired HTTP or MQTT server.

Data to Server configuration

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

Data configuration

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

  1. Name: desired name of the instance
  2. Type: M-Bus data
  3. Format: custom or JSON depending on a need.


Once finished configuring Data configuration tab click on button.

Collection configuration

Once finished configuring Collection configuration tab click on button.

Server configuration

This section contains information on how to configure MQTT and HTTP servers information.

HTTP configuration

  1. Type: HTTP
  2. Server address: desired server address

Note: not specified fields are optional.

MQTT configuration

  1. Type: MQTT
  2. Server address: desired server address
  3. Topic: MQTT topic to be used for publishing the data.

Note: not specified fields are optional.

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

Results

Note: received data formating depends on the settings you apply under Data to Server and M-Bus configurations.

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