Chapter 5 Functional principle
5.4.1 Connection abort in "online" mode
A single direct connection attempt is made if the connection is lost in "online" mode. If it is not possible to
establish a connection, 2 further attempts of the standard retry sequence are made at intervals of 2min. . If the
connection was not established during the last retry, the device remains offline until the next connection
attempt is triggered via the "rM2M_TxStart()" function.
5.4.2 Connection abort during a Device Logic download
The device reacts to a connection abort during Device Logic download with the standard retry sequence (2
connection attempts at intervals of 2min. ). In addition to this, the "SCRIPT_ERR, SCRIPT UPDATE
ERROR" log entry is entered in the device log as soon as the device has detected the connection abort. As
the existing Device Logic is located in the RAM, it can continue to be executed until the next PowerOn. It can
no longer be executed following a PowerOn and the "SCRIPT_ERR, NO SCRIPT" error is entered in the
device log. The reason for this is that the area in the flash memory where the Device Logic is located is
deleted at the start of the Device Logic download.
5.5 Automatic selection of the GSM network
The GSM network to which the device should register must be selected, as the myDatalogEASY V3 is
equipped with a SIM chip that provides a mobile connection via a variety of international service providers
(see www.microtronics.com/footprint ). This is completed automatically by the device.
5.6 Determining the GSM/UMTS/LTE signal strength
The internal update rate of the measurement value for the GSM/UMTS/LTE signal strength is dependent on
the type of connection selected via the "rM2M_TxSetMode()" function:
l
Interval: Updated during connection establishment
l
Interval & Wakeup: Updated every 30 seconds
l
Online: Updated every 5 seconds
The "rM2M_GSMGetRSSI()" function can be used to read the last determined value from the system.
5.7 Determining the GSM position data
An internal flag is set by the firmware every 24h , which ensures that the GSM position data is also
determined the next time the "rM2M_TxStart()" function is called up. The positioning can however also be
suppressed by setting the "RM2M_TX_SUPPRESS_ POSUPDATE" flag when calling up the function. It is
also possible to trigger the determination of the GSM position data by setting the "RM2M_TX_POSUPDATE"
flag when calling up "rM2M_TxStart()". If "Interval & Wakeup" connection mode was activated on the
myDatalogEASY V3 , the previously described internal flag is set by the firmware and the connection
establishment is triggered by the receipt of a Wakeup SMS (i.e. via the myDatanet server), the determination
of the GSM position data is definitely executed and cannot be suppressed. The GSM position data cannot be
generated if "online" connection mode is active.
Rev. 05
35
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: ......