![]() ![]() Parameters allow the user to customize Commissioning Files for multiple use cases by referring to them from within the Commissioning File. Name: Modbus/TCP Example Commissioning File We will just use the following set of information for this lesson: description: >Ĭybus Learn - How to connect and integrate an Modbus/TCP server Regarding the metadata, only the name is required while the rest is optional. You can give a short description and add a stack of metadata. These sections contain more general information about the commissioning file. The Commissioning File is in the YAML format, perfectly readable for human and machine! We will now go through the process of defining the required sections for this example: To get started, open a text editor and create a new file, e.g. To understand the file’s anatomy in detail, please consult the Reference docs. It contains information about all connections, data endpoints and mappings and is read by the Connectware. The Commissioning File is a set of parameters which describes the resources that are necessary to collect and provide all the data for our application. | double | 64 bit | IEEE 754 | IEEE 754 | Writing the Commissioning File In the documentation there is also a table defining the size and range of the terms used in the column Format, which we will need for specifying our endpoints. | 19050 | float | _G_FREQ | Hz | Measured frequency | | 19048 | float | _G_COS_PHI | - | CosPhi U元 I元 (fundamental comp.) | | 19046 | float | _G_COS_PHI | - | CosPhi UL2 IL2 (fundamental comp.) | ![]() | 19044 | float | _G_COS_PHI | - | CosPhi UL1 IL1 (fundamental comp.) | | 19040 | float | _G_QLN | var | Reactive power 元 (fundamental comp.) | | 19038 | float | _G_QLN | var | Reactive power L2 (fundamental comp.) | | 19036 | float | _G_QLN | var | Reactive power L1 (fundamental comp.) | | 19032 | float | _G_SLN | VA | Apparent power 元-N | | 19030 | float | _G_SLN | VA | Apparent power L2-N | | 19028 | float | _G_SLN | VA | Apparent power L1-N | | 19024 | float | _G_PLN | W | Real power 元-N | | 19022 | float | _G_PLN | W | Real power L2-N | | 19020 | float | _G_PLN | W | Real power L1-N | | 19016 | float | _G_ILN | A | Apparent current, 元-N | | 19014 | float | _G_ILN | A | Apparent current, L2-N | | 19012 | float | _G_ILN | A | Apparent current, L1-N | We also find the following addresses representing frequently required readings: | Address | Format | Designation | Unit | Remarks | | 12 | short | _WEEKDAY | | Weekday, (0=Sun. | 4 | int | _SYSTIME | sec | Time (UTC) | | 0 | long64 | _REALTIME | 2 ns | Time (UTC) | Examining the Modbus adress-list for UMG 604-PRO, we find the following addresses representing the date and time: | Address | Format | Designation | Unit | Remarks | Although there is such a lot of interesting data, we assume that we just want to know the actual day of month, which is also provided and the real powers of L1-元 as well as the utility frequency. This device offers a lot of power analysis data you can access via Modbus, ranging over some thousands of address points. This is a device for measuring and analyzing the electric power quality, which is equipped with a Modbus/TCP server. ![]() Example Setupįor this example we presume that we have a device of the type Janitza UMG 604-EP PRO installed on our Ethernet network. The Commissioning Files used in this lesson are made available in the Example Files Repository on GitHub.
0 Comments
Leave a Reply. |