![Ublox TOBY-R2 Series Скачать руководство пользователя страница 14](http://html2.mh-extra.com/html/ublox/toby-r2-series/toby-r2-series_system-integration-manual_3187483014.webp)
TOBY-R2 series - System integration manual
UBX-16010572 - R10
System description
Page 14 of 151
1.4
Operating modes
TOBY-R2 series modules have several operating modes. The operating modes are defined in
and described in detail in
, providing general guidelines for operation.
General Status Operating Mode
Definition
Power-down
Not-powered Mode VCC supply not present or below operating range: module is switched off.
Power-off Mode
VCC 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 4: TOBY-R2 series modules operating modes definition
Mode
Description
Transition between operating modes
Not-Powered Module is switched off.
Application interfaces are not
accessible.
When VCC supply is removed, the modules enter not-powered mode.
When in not-powered mode, the modules cannot be switched on by
PWR_ON, RESET_N or RTC alarm
When in not-powered mode, the modules can be switched on by
applying VCC supply (see
) so that the modules switch from
not-powered to active-mode
Power-Off
Module is switched off: normal
shutdown by an appropriate power-off
event (see
Application interfaces are not
accessible.
When the modules are switched off by an appropriate switch-off
event (see
), the modules enter power-off mode from
active-mode.
When in power-off mode, the modules can be switched on by
PWR_ON, RESET_N or an RTC alarm.
When in power-off mode, the modules enter not-powered mode by
removing VCC supply.
Idle
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
) reducing current
consumption (see
The CTS output line indicates when the
UART interface is disabled/enabled due
to the module idle/active-mode
according to power saving and HW flow
control settings (see
Power saving configuration is not
enabled by default: it can be enabled by
AT+UPSV (see the u-blox AT commands
manual
The modules automatically switch from the active-mode to low power
idle-mode whenever possible if power saving is enabled (see sections
, AT+UPSV
command).
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
Automatic periodic enable of the UART interface to receive / send
data, with AT+UPSV=1 (see
Data received over UART, according to HW flow control (AT&K)
and power saving (AT+UPSV) settings (see
RTS input set ON by the host DTE, with HW flow control disabled
and AT+UPSV=2 (see
DTR input set ON by the host DTE, with AT+UPSV=3 (see
USB detection, applying 5 V (typ.) to VUSB_DET input (see
The connected USB host forces a remote wakeup of the module as
USB device (see
The connected u-blox GNSS device forces a wakeup of the module
using the GNSS Tx data ready function over GPIO3 (see
The connected SDIO device forces a wakeup of the module as
SDIO host (see
A preset RTC alarm occurs (see u-blox AT commands manual
AT+CALA)