webdyn.com
V2.0 subject to changes | Webdyn © by Flexitron Group
64
Example BSON configuration file (converted from JSON):
50 00 00 00 03 43 6F 6E 66 69 67 00 3A 00 00 00
03 52 65 6D 6F 74 65 00 2D 00 00 00 04 4E 54 50
00 23 00 00 00 02 30 00 0F 00 00 00
6E 74 70 2E
67 6F 6F 67 6C 65 2E 63 6F 6D
00 02 31 00 01 00
00 00 00 00 00 00 10 43 52 43 00
00 00 00 00
00
The CRC is then calculated on the whole file and the result of the CRC32 in Little Endian overwrites the 4
CRC 0 bytes. In the example, the CRC32 for the corresponding file is 0x2A0C7BA3.
Example of the BSON file with the updated CRC32:
50 00 00 00 03 43 6F 6E 66 69 67 00 3A 00 00 00
03 52 65 6D 6F 74 65 00 2D 00 00 00 04 4E 54 50
00 23 00 00 00 02 30 00 0F 00 00 00 6E 74 70 2E
67 6F 6F 67 6C 65 2E 63 6F 6D 00 02 31 00 01 00
00 00 00 00 00 00 10 43 52 43 00
A3 7B 0C 2A
00
5.2
The Configuration
The hub allows configurations using a .
Configuration File:
The WebdynEasy W M-Bus hub configuration file is in BSON format and the file name format is as follows:
“<uid>-cfg.bson”
A backup of the current configuration is available on the remote server in the “/CONFIG” directory.
Whether after a local or remote modification of the configuration, the hub sends its new configuration to
the remote server. The configuration file saved on the hub is in BSON format and the file name format is
as follows:
“<uid>-<timestamp>-config.bson”
With:
•
<uid>: Concentrator identifier
• <timestamp>: Number of seconds elapsed since January 1, 1970 at midnight UTC precisely.
Example: 123456-1591083697-config.bson
