User's Manual

BL652
Datasheet
Embedded Wireless Solutions Support Center:
http://ews-support.lairdtech.com
www.lairdtech.com/bluetooth
20
© Copyright 2016 Laird. All Rights Reserved
Americas: [phone]
Europe: [phone]
Hong Kong: [phone]
that are enabled stay on and may re-awaken the chip. Depending on active peripherals, current
consumption ranges from ~1.2 µA to 270 uA (when UART is ON). See individual peripherals current
consumption data in the Peripheral Block Current Consumption section. smartBASIC runtime engine
firmware has added new functionality to detect GPIO change with no current consumption cost, it is
possible to close the UART and get to the 1.2uA current consumption regime and still be able to
detect for incoming data and be woken up so that the UART can be re-opened at expense of losing
that first character.
Note 3
In Deep Sleep, everything is disabled and the only wake-up sources (including NFC to wakeup) are
reset and changes on SIO or NFC pins on which sense is enabled. The current consumption seen is
~400 nA typical in BL652-Sx-xx.
 smartBASIC runtime engine firmware requires a hardware reset to come out of deep sleep.
 smartBASIC runtime engine firmware also allows coming out from Deep Sleep to Standby Doze
through GPIO signal through the reset vector. Deep Sleep mode is entered with a command in
smartBASIC application script.
Note 4
Data taken with a transmit power of 4 dBm and all peripherals off (UART OFF after radio event), slave
latency of 0 (in a connection). Average current consumption depends on a number of factors
(including Tx power, VCC, accuracy of 32MHz and 32.768 kHz). With these factors fixed, the largest
variable is the advertising or connection interval set.
Advertising Interval range:
 20 milliseconds to 10240 milliseconds in multiples of 0.625 milliseconds for the following Advert
type: ADV_IND and ADV_DIRECT_IND
 100 milliseconds to 10240 milliseconds in multiples of 0.625 milliseconds for the following
Advert types: ADV_SCAN_IND and ADV_NONCONN_IND
For advertising timeout, if the advert type is ADV_DIRECT_IND, then the timeout is limited to
1.28 seconds (1280 milliseconds).
For an advertising event:
 The minimum average current consumption is when the advertising interval is large 10240 mS
(although this may cause long discover times (for the advertising event) by scanners
 The maximum average current consumption is when the advertising interval is small 20 mS
Other factors that are also related to average current consumption include the advertising
payload bytes in each advertising packet and whether it’s continuously advertising or
periodically advertising.
Connection Interval range:
 7.5 milliseconds to 4000 milliseconds in multiples of 1.25 milliseconds.
For a connection event:
 The minimum average current consumption is when the connection interval is large 4000
milliseconds
 The maximum average current consumption is with the shortest connection interval of 7.5 ms;
no slave latency.