TOBY-L2 and MPCI-L2 series - System Integration Manual
UBX-13004618 - R07
Advance Information
System description
Page 33 of 158
Figure 15 describes the TOBY-L2 power-off sequence by means of AT+CPWROFF with the following phases:
When the +CPWROFF AT command is sent, the module starts the switch-off routine.
The module replies OK on the AT interface: the switch-off routine is in progress.
At the end of the switch-off routine, all the digital pins are tri-stated and all the internal voltage regulators
are turned off, including the generic digital interfaces supply (
V_INT
), except the RTC supply (
V_BCKP
).
Then, the module remains in power-off mode as long as a switch on event does not occur (e.g. applying a
proper low level to the
PWR_ON
input, or applying a proper low level to the
RESET_N
input), and enters
not-powered mode if the supply is removed from the
VCC
pins.
VCC
V_BCKP
PWR_ON
RESET_N
V_INT
Internal Reset
System State
BB Pads State
Operational
OFF
Tristate / Floating
ON
Operational
→
Tristate
AT+CPWROFF
sent to the module
0 s
~2.5 s
~5 s
OK
replied by the module
VCC
can be removed
Figure 15: TOBY-L2 series power-off sequence description
The Internal Reset signal is not available on a module pin, but the application can monitor the
V_INT
pin
to sense the end of the power-off sequence.
Figure 16 describes the MPCI-L2 power-off procedure with the following phases:
When the AT+CFUN=127 command is issued, the module starts the halt mode setting routine.
The module replies OK on the AT interface: after this, the module is set in the halt mode.
Then, the module remains in the Halt mode and enters not-powered mode if the supply is removed from the
3.3Vaux
pins.
3.3Vaux
PERST#
Internal Reset
System State
BB Pads State
OFF
ON
Tristate / Floating
Operational
AT+CFUN=127
sent to the module
0 s
~2.5 s
~5 s
OK
replied by the module
3.3Vaux
can be removed
Figure 16: MPCI-L2 series power-off procedure description
The duration of each phase in the TOBY-L2 and MPCI-L2 series modules’ switch-off routines can largely
vary depending on the application / network settings and the concurrent module activities.
