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

native rM2M_ReadData(recidx, funcidx);
Reads out a data record saved in the internal flash and then calls up the function for which the index
was transferred.
Parameter Explanation
recidx Index of the data record to be read (-1 = last/current data record, -2 = penultimate
data record, .... )
funcidx Index of the public function that should be called once the data record has been
read from the internal flash memory.
Type of function: public func(const data[], len, timestamp);
Explanation
Return value
l
OK, if the read process has been started
l
ERROR, if an error occurs
native rM2M_CfgInit(cfg, flags);
Sets the configuration for a configuration memory block. Calling the function is only necessary if one of
the configuration flags should be set.
Parameter Explanation
cfg Number of the configuration memory block starting with 0 for the first memory
block. The device comprises 10 independent memory blocks.
flags Configuration flags to be set/deleted
Bit0: Type of storage
0 (default) = stored in FLASH in non-volatile manner
RM2M_CFG_VOLATILE = saved in RAM in volatile manner
Explanation
Return value
l
OK, if successful
l
< OK, if an error occurs (see "Return codes for general purposes" in
chapter "Constants" on page 84)
Note: Additional explanation on the type of storage:
If Bit 0 was not set (default), the non-volatile storage of the configuration memory block in the FLASH is
initiated when the "rM2M_CfgWrite" function is called.
If Bit0 was set (Bit0 = RM2M_CFG_VOLATILE), the configuration memory block is saved in the RAM in
a volatile manner when the "rM2M_CfgWrite" function is called. This option is recommended if the data
in the configuration memory block changes frequently as this will reduce the number of flash write
cycles. The "rM2M_CfgFlush" function must be called so that the configuration memory block is saved
in a non-volatile manner in the FLASH.
92 Rev. 01