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

5.4 Error handling
The following transmission mechanisms have been integrated in the firmware to ensure that problems with
the Device Logic can be diagnosed and resolved remotely. In the event that there is no Device Logic, a
connection to the myDatanet server is established every 24h . This backup interval is set to 1h if an existing
Device Logic has been deactivated due to an error being detected by the system. The "Interval & wakeup"
connection type is activated in both cases, which enables a connection to be initiated via the interface of the
myDatanet (see "myDatanet Server Manual " 805002).
5.5 Registration memory blocks
In addition to 4 1kB blocks, that are saved in the flash, another one, that is saved in the RAM, can optionally
be initialised via the "rM2M_RegInit()" function. Its size can be specified during initialisation, although it is
limited to a maximum of 1kB . The registration memory blocks provide the option of storing device-specific
data and synchronising it with the myDatanet server. The blocks only differs with regard to their access
options and storage location. This results in predefined intended uses that are described in the following
table:
Memory block Access Memory Purpose
System-specific data
REG_SYS_OTP
1)
readable: Device Logic,
myDatanet server
FLASH System information that is written once as
part of the production process
REG_SYS_FLASH
1)
readable: Device Logic,
myDatanet server
FLASH System information that must be able to be
changed during operation
Application-specific data
REG_APP_OTP readable: Device Logic,
myDatanet server
writeable: Device Logic
FLASH Application-specific information that is
written once as part of the production
process (recommendation, writing it multiple
times is not prevented by the firmware)
REG_APP_FLASH readable: Device Logic,
myDatanet server
writeable: Device Logic
FLASH Application-specific information that must be
able to be changed during operation
Application-specific, volatile data
REG_APP_STATE
2)
readable: Device Logic,
myDatanet server
writeable: Device Logic
RAM Application-specific information that must be
able to be changed during operation and
that does not require non-volatile storage in
the flash (e.g. current device status).
1)
Writing data in these two memory blocks is reserved for the manufacturer.
2)
This memory block is only available if it was initialised via the "rM2M_RegInit()" function.
Note: It is also possible to write in the memory blocks as part of the production process via the local
interfaces (USB and both UART). However, an agreement must be reached with the manufacturer to
receive information about this (see "Contact information" on page 209).
32 Rev. 01