Microtronics myDatalogEASY IoTmini, Руководство пользователя, Страница: 29 / 210

Chapter 5 Functional principle
l
Application (device logic)
The firmware of the myDatalogEASY IoTmini only manages the synchronisation of the measurement
data and configurations between the myDatalogEASY IoTmini and myDatanet server. The application
created by the customer must record the measurement values and create the data blocks that are to be
saved. The data blocks, on the other hand, are stored by the firmware of the myDatalogEASY IoTmini
(see "rM2M_RecData()").
l
Data Descriptor
The basic function of the myDatanet server is limited to synchronisation of the measurement data
channels ("histdata0" - "histdata9") and configuration blocks ("config0" - "config9") between the
myDatalogEASY IoTmini and server. The Data Descriptor defined by the customer must divide the
measurement data channels and configuration blocks into the individual data fields.
l
Customer-specific server with web interface for the clients (optional)
It can be used to create an individual web interface for the clients. Two options are possible depending
on which source is used to obtain the data:
l
Customer-specific server that reads its data via the API interface (see "API" on page 187) from
the myDatanet server.
l
Customer-specific server that receives its data via LoRaWAN connection from the
myDatalogEASY IoTmini .
5.1 Recommended procedure
5.1.1 Development of M2M/IoT application
It is recommended to start with the definition of the Data Descriptor (see "Data Descriptor " on page 185)
when developing a M2M/IoT application. It specifies the various data structures (measurement data,
configurations, etc.) that are valid for the Device Logic as well as the myDatanet server. The definitions of the
Data Descriptor also apply for accessing the data of the myDatanet server via the API.
The information type should be taken into consideration when assigning the data to the relevant containers
("histdata0" - "histdata9" or "config0" - "config9"). The "histdata0" - "histdata9" containers should be used for
time series. If there is measurement data that will be generated frequently and data that will only be
generated rarely, it is recommended to use two different containers (e.g. "histdata0" for the frequently
generated and "histdata1" for the rarely generated). Similar also applies to the configuration data, for which
the "config0" - "config9" containers are provided. When it comes to the configuration data, it is recommended
to take a grouping based on logical context into consideration in addition to the frequency of change.
Note: A well thought out selection of the containers helps to reduce the required data volume and
associated costs.
5.2 Functionality of the internal data memory
Structure Circular buffer
Total size 3MB
Number of sectors 8
Sector size 393.216 Byte
Rev. 01 29