Chapter 14 Data Descriptor
The basic principle of the myDatalogEASY V3 is "storage-2-storage" data transmission. For this type of data
transmission, neither the myDatalogEASY V3 nor the server must know about the logical content of the data
blocks. Therefore, the only aim is to transport a block of data from A to B.
The data transferred from the myDatalogEASY V3 to the sever can therefore be selected freely. There
are1024 Byte available per data record that can be used as required. There are also another 10 independent
memory blocks each with 4000 Byte for the configuration data that can be used as required.
The content of the data block or configuration block must be described on the server so that the data and
configurations received from the myDatalogEASY V3 can also be used within the myDatanet interface
(reports, visualisations, graphics, etc.). The Data Descriptor contains the tool for describing the data as well
as the correct provision of the data for use within the interface.
14.1 Data structure
The following containers are available for the different types of data (measurement data, configurations,
etc. ):
l
Measurement data:
"#histdata0" - "#histdata9"
l
Configurations:
"#config0" - "#config9"
l
Configurations only available on the server:
"#configA" - "#configC"
l
Alarm messages:
#alerts
l
Aloha data:
#aloha
This section describes how the structured measurement data channels ("#histdata0" - "#histdata9"),
configuration memory blocks ("#config0" - "#config9") and the aloha data ("aloha") are split into individual data
fields for use on the myDatanet server. The structure of the alarm messages ("#alerts") is fixed firmly in the
system and does not need to be specified/cannot be changed by the user.
Important note:
If a structured measurement data channel, a configuration block or the aloha data
are to be available on the myDatanet server or via the REST API then all data fields need to be
defined by means of the Data Descriptor .
An extended example, in which most of the available attributes are used, is provided in chapter "Example" on
page 241.
Rev. 05
235
Summary of Contents for myDatalogEASY V3
Page 2: ......
Page 13: ...Chapter 2 Declaration of conformity Chapter 2 Declaration of conformity Rev 05 13 ...
Page 14: ......
Page 42: ......
Page 76: ......
Page 88: ......
Page 102: ......
Page 110: ......
Page 116: ......
Page 234: ......
Page 244: ......
Page 252: ......
Page 254: ......
Page 266: ......
Page 276: ......