Integration Manual

Table Of Contents
TOBY-L2 and MPCI-L2 series - System Integration Manual
UBX-13004618 - R26 System description
Page 21 of 162
1.4 Operating modes
TOBY-L2 and MPCI-L2 series modules have several operating modes. The operating modes are defined in Table 5
and described in detail in Table 6, providing general guidelines for operation.
General Status
Operating Mode
Definition
Power-down
Not-Powered Mode
VCC or 3.3Vaux supply not present or below operating range: module is switched off.
Power-Off Mode
VCC or 3.3Vaux supply within operating range and module is switched off.
Normal Operation
Idle-Mode
Module processor core runs with 32 kHz reference generated by the internal oscillator.
Active-Mode
Module processor core runs with 26 MHz reference generated by the internal oscillator.
Connected-Mode
RF Tx/Rx data connection enabled and processor core runs with 26 MHz reference.
Table 5: TOBY-L2 and MPCI-L2 series modules operating modes definition
Operating Mode
Description
Transition between operating modes
Not-Powered
Mode
Module is switched off.
Application interfaces are not accessible.
When VCC or 3.3Vaux supply is removed, the module enters
not-powered mode.
When in not-powered mode, TOBY-L2 modules cannot be switched
on by PWR_ON, RESET_N or RTC alarm and enter active-mode
after applying VCC supply (see 1.6.1).
When in not-powered mode, MPCI-L2 modules cannot be switched
on by RTC alarm and enter active-mode after applying 3.3Vaux
supply (see 1.6.1).
Power-Off Mode
Module is switched off: normal shutdown by
an appropriate power-off event (see 1.6.2).
Application interfaces are not accessible.
MPCI-L2 modules do not support Power-Off
Mode but halt mode (see 1.6.2 and u-blox AT
Commands Manual [3], AT+CFUN=127
command).
When the module is switched off by an appropriate power-off event
(see 1.6.2), the module enters power-off mode from active-mode.
When in power-off mode, TOBY-L2 modules can be switched on by
PWR_ON, RESET_N or an RTC alarm.
When in power-off mode, TOBY-L2 modules enter the not-powered
mode after removing VCC supply.
Idle-Mode
Module is switched on with application
interfaces temporarily disabled or suspended:
the module is temporarily not ready to
communicate with an external device by
means of the application interfaces as
configured to reduce the current
consumption.
The module enters the low power idle-mode
whenever possible if power saving is enabled
by AT+UPSV (see u-blox AT Commands
Manual [3]) reducing current consumption
(see 1.5.1.5).
With HW flow control enabled and
AT+UPSV=1 or AT+UPSV=3, the UART CTS
line indicates when the UART is enabled (see
1.9.2.3, 1.9.2.4).
With HW flow control disabled, the UART CTS
line is fixed to ON state (see 1.9.2.3).
Power saving configuration is not enabled by
default: it can be enabled by the AT+UPSV
command (see the u-blox AT Commands
Manual [3]).
The modules automatically switch from active-mode to low power
idle-mode whenever possible if power saving is enabled (see
sections 1.5.1.5, 1.9.1.4, 1.9.2.4 and u-blox AT Commands Manual
[3], AT+UPSV).
The modules wake up from low power idle-mode to active-mode in
the following events:
Automatic periodic monitoring of the paging channel for the
paging block reception according to network conditions (see
1.5.1.5)
The connected USB host forces a remote wakeup of the
module as USB device (see 1.9.1.4)
Automatic periodic enable of the UART interface to receive /
send data, with AT+UPSV=1 (see 1.9.2.4)
Data received over UART, with HW flow control disabled and
power saving enabled (see 1.9.2.4)
RTS input set ON by the host DTE, with HW flow control
disabled and AT+UPSV=2 (see 1.9.2.4)
DTR input set ON by the host DTE, with AT+UPSV=3 (see
1.9.2.4)
The connected SDIO device forces a wakeup of the module as
SDIO host (see 1.9.4)
A preset RTC alarm occurs (see u-blox AT Commands Manual
[3], AT+CALA)