Domnev: Difference between revisions
No edit summary |
No edit summary |
||
Line 87: | Line 87: | ||
# '''Name''': desired name of the instance | # '''Name''': desired name of the instance | ||
# '''Period''': desired time duration between data retrievals | # '''Period''': desired time duration between data retrievals | ||
# '''Data type''': desired data type to process the received data. | # '''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 [[File:Mbus test button.png]] button. You should see the data in a pop-up field. | [[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: | |||
[[File:Mbus TEST output.png|border|class=tlt-border]] | |||
====Group values==== | |||
---- | |||
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''' | |||
[[File:Mbus device groupsa.png|border|class=tlt-border]] | |||
==Sending data to the server== | |||
==See Also== | ==See Also== |
Revision as of 13:27, 21 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.
Adding M-Bus devices
To 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:
- 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
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 .
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:
- 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.
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:
- 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.
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:
- 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