Bluemodsr
Bluemodsr
The software described in this document is the property of Telit and its licensors. It is
furnished by express license agreement only and may be used only in accordance with the
terms of such an agreement.
II. Copyrighted Materials
Components, units, or third-party products used in the product described herein are NOT
fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control
equipment in the following hazardous environments requiring fail-safe controls: the
operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air
Traffic Control, Life Support, or Weapons Systems (High Risk Activities"). Telit and its
supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High
Risk Activities.
IV. Trademarks
TELIT and the Stylized T Logo are registered in Trademark Office. All other product or
service names are the property of their respective owners.
V. Third Party Rights
The software may include Third Party Right software. In this case you agree to comply with
all terms and conditions imposed on you in respect of such separate software. In addition
to Third Party Terms, the disclaimer of warranty and limitation of liability provisions in this
License shall apply to the Third Party Right software.
TELIT HEREBY DISCLAIMS ANY AND ALL WARRANTIES EXPRESS OR IMPLIED
FROM ANY THIRD PARTIES REGARDING ANY SEPARATE FILES, ANY THIRD PARTY
MATERIALS INCLUDED IN THE SOFTWARE, ANY THIRD PARTY MATERIALS FROM
WHICH THE SOFTWARE IS DERIVED (COLLECTIVELY “OTHER CODE”), AND THE
USE OF ANY OR ALL THE OTHER CODE IN CONNECTION WITH THE SOFTWARE,
INCLUDING (WITHOUT LIMITATION) ANY WARRANTIES OF SATISFACTORY
QUALITY OR FITNESS FOR A PARTICULAR PURPOSE.
NO THIRD PARTY LICENSORS OF OTHER CODE SHALL HAVE ANY LIABILITY FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED
AND WHETHER MADE UNDER CONTRACT, TORT OR OTHER LEGAL THEORY,
ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE OTHER CODE
OR THE EXERCISE OF ANY RIGHTS GRANTED UNDER EITHER OR BOTH THIS
LICENSE AND THE LEGAL TERMS APPLICABLE TO ANY SEPARATE FILES, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
APPLICABILITY TABLE
PRODUCTS
BLUEMOD+SR/AI
BLUEMOD+SR/AP
Contents
NOTICE ..................................................................................................... 2
COPYRIGHTS ................................................................................................ 2
CONTENTS .................................................................................................... 5
1. INTRODUCTION .......................................................................... 9
Scope ........................................................................................... 9
Audience....................................................................................... 9
Contact Information, Support ........................................................ 9
Text Conventions ........................................................................ 10
Related Documents .................................................................... 11
2. OVERVIEW ................................................................................ 12
Feature Summary ....................................................................... 13
Applications ................................................................................ 13
2.2.1. General Cable Replacement ....................................................... 14
2.2.2. Industry ....................................................................................... 14
2.2.3. Automotive.................................................................................. 14
2.2.4. Healthcare and Medical .............................................................. 14
2.2.5. Sports and Fitness ...................................................................... 14
2.2.6. Entertainment ............................................................................. 14
8. APPLICATION DIAGRAM.......................................................... 60
9. APPROVALS/CERTIFICATIONS ............................................... 61
Declaration of Conformity CE...................................................... 61
FCC Compliance ........................................................................ 61
9.2.1. FCC Grant .................................................................................. 62
9.2.2. FCC Statement ........................................................................... 64
9.2.3. FCC Caution ............................................................................... 64
9.2.4. FCC Warning .............................................................................. 64
9.2.5. FCC RF-exposure Statement...................................................... 64
9.2.6. FCC Labeling Requirements for the End Product ....................... 65
IC Compliance ............................................................................ 65
9.3.1. IC Grant ...................................................................................... 66
9.3.2. IC Statement ............................................................................... 67
9.3.3. IC Caution................................................................................... 67
9.3.4. IC RF-exposure Statement ......................................................... 67
9.3.5. IC Labeling Requirements for the End Product ........................... 68
9.3.6. IC Label Information BlueMod+SR .............................................. 68
KC Certification ........................................................................... 69
9.4.1. KC Certificate ............................................................................. 69
MIC Certification ......................................................................... 70
9.5.1. MIC Certificates .......................................................................... 71
Anatel Certification...................................................................... 73
Bluetooth Qualification ................................................................ 74
RoHS Declaration ....................................................................... 75
1. INTRODUCTION
Scope
This document provides information how the BlueMod+SR can be integrated into customer
systems. It addresses hardware specifications of the BlueMod+SR and requirements of the
hardware environments for the BlueMod+SR.
Audience
This document is intended for Telit customers, especially system integrators, about to
implement Bluetooth modules in their application.
[email protected]
[email protected]
[email protected]
or
[email protected] for global Bluetooth support
Alternatively, use:
http://www.telit.com/support
For detailed information about where you can buy the Telit modules or for recommendations
on accessories and components visit:
http://www.telit.com
Our aim is to make this guide as helpful as possible. Keep us informed of your comments
and suggestions for improvements.
Telit appreciates feedback from the users of our information.
Text Conventions
Related Documents
[1] CD00171190.pdf Oct. 2011 Rev 14 (STM32_Reference)
[2] CD00191185.pdf April 2011 Rev 8 (STM32_datasheet)
[3] UICP+ UART Interface Control Protocol, 30507ST10756A
[4] BlueMod+SR AT Command Reference, 80507ST10752A
[5] BlueMod+SR Software User Guide, 1VV0301278
2. OVERVIEW
This document provides information how the BlueMod+SR/AI and BlueMod+SR/AP can be
integrated into customer systems. It addresses hardware specifications of the
BlueMod+SR/AI and /AP and requirements of the hardware environments for the
BlueMod+SR/AI and BlueMod+SR/AP.
For the latest version of this document please check the following URL:
http://www.telit.com/bluetooth/bluemod-sr/
Feature Summary
Bluetooth specification V4.0 compliant
Supports BR/EDR/LE
Supports Dual Mode
Fully qualified Bluetooth V4.0 Dual Mode BR/EDR/LE
CE certified
FCC, IC and KCC certified
CSR8811 BlueCore08 and Application Processor inside
Complete Co-location and Co-existence with 802.11 (AFH, Unity 3e+)
Fast Connection Setup
RF output power up to +7dBm with power control
Supply Voltage range 2,5V to 3,6V, typical 3.3V
Internal crystal oscillator (26 MHz and 14,7456 MHz)
LGA Surface mount type: BlueMod+SR: 17 x 10 x 2.6 mm3
Shielded to be compliant to FCC full modular approval
Bluetooth enhanced data rate up to 2178kbps asymmetric
Support for all Bluetooth power saving modes (Park, Sniff, Hold)
Optional support for ultra-low-power mode
Full 8- to 128-bit encryption
High sensitivity design
High-speed UART interface
I2C interface
SPI interface
Up to 11 digital IO’s for individual usage by embedded software
Cortex-M3 STM32F103 core for embedded profiles or application software
Manufactured in conformance with RoHS2
Operating temperature -30 ... +85 °C
Weight: 0,8 g
Applications
The BlueMod+SR can be used in different applications. Regardless if the application
requires high throughput or low energy consumption, BlueMod+SR offers the best of both
worlds. Some typical applications are described in this chapter.
BR/EDR:
SPP
LE:
Terminal I/O
GATT based LE profiles
2.2.2. Industry
Typical Bluetooth application include scanner, printer as well as automation controls. In the
automation application area Bluetooth is mainly used for transport of I/O signals. Bluetooth
low energy can be used to monitor and control motors, actuators, values and entire
processes.
2.2.3. Automotive
Modules are mainly used in aftermarket application like personal navigation devices, head
units or audio applications. These applications are typically Bluetooth BR/EDR only.
2.2.6. Entertainment
Bluetooth technology is already used in a wide variety of devices in the entertainment
sector, namely set-top boxes / gaming consoles. Bluetooth low energy is expected to further
increase the use of Bluetooth technology in devices like TV / DVD / STB / Media Player,
remote controls, gaming controller, wireless mouse/keyboard.
3. BLOCK DIAGRAM
BlueMod+SR
EEPROM
onboard 14,7456MHz
antenna 1)
26MHz TRACE
Serial Wire
(DEBUG)
CSR8811 STM32F103 3.0V
BP VSUP
Filter GND
1)BlueMod+SR/AI only
3
1
9
4
2)BlueMod+SR/AP only
2)
RESET
I2C
UART
GPIO
WLAN-COEX
opt. 32kHz
EXT-ANT
SPI
4. APPLICATION INTERFACE
Power Supply
BlueMod+SR require a power supply with the following characteristics:
BlueMod+SR
XC6204-3.3
C-1,E-6,F-6 5 VOUT VIN 1
VSUP +5VDC
CE 3
VSS
2
1µ
10µ + 100n + 1n
GND:
A-7,E-7,F-7,B-[5:8],
C-[5:8],D-8,E-8,F-8
The VSUP voltage has to rise continuously from 0V to the minimum VSUP operating voltage
defined in Table 8: DC operating conditions.
Reset
BlueMod+SR are equipped with circuitry for generating Power ON Reset from the internal
core voltage. A reset is generated when the core voltage falls below typically 1,88V and is
released when it rises above typically 1,92V.
By holding pin B-1 (EXT-RES#) at ≤ 0,5V for ≥ 5ms, an external reset is generated. This
pin has a fixed internal pull-up resistor (RPU = 30kΩ ... 50kΩ) and a capacitor to GND
(100n) which acts as debounce filter. If EXT-RES# is not used, it may be left open.
EXT-RES# pin can also be output. Use an open drain device or push
button to drive it low. EXT-RES# must not be connected to VSUP or
driven to logic high-level directly. Provide for a 1kΩ series resistor
when driving EXT-RES# from a CMOS output.
B-1
EXT-RES# 1k GPIO
Reset signal is optional
GND
Reset-Switch is optional
Please Note: BlueMod+SR has an open-drain output and approx. 40k internal pullup
The following table shows the pin states of BlueMod+SR during reset active.
The pin states as indicated in Table 2 are kept until hardware initialization has started.
Serial Interface
The serial interface of BlueMod+SR is a high-speed UART interface supporting RTS/CTS
flow control and interface-up/down mechanism according to the UICP+ protocol (refer to
[3]). Electrical interfacing is at CMOS levels (defined by VSUP).
UART-RXD
BlueMod+SR UART-TXD Host
UART-CTS#
UART-RTS#
IUR-IN#
IUR-OUT#
GND
The basic serial interface (with RTS/CTS flow control) uses only four signal lines (UART-
RXD, UART-TXD, UART-CTS#, UART-RTS#). IUR-IN#, IUR-OUT# and GPIO[4] (see
below) can be left unconnected.
A substantially saving of power during idle phases can be achieved (see 6.6.1) when the
UICP protocol is used (refer to [3] ). This protocol should be implemented on the host side
as well. Signals IUR-IN# and IUR-OUT# should be connected to the host and may be
mapped to DSR and DTR, if an RS232-style (DTE-type) interface is used (see Figure 5).
When using the SPP firmware and applications, call control can be supported by GPIO[4].
Driving GPIO[4] to logic High level during a data transfer phase will “hang up” the connection
and disconnect the Bluetooth link. This signal may be mapped to DSR, if an RS232-style
(DTE-type) interface is used. Please refer to [4] for a functional specification. GPIO[4] can
be left unconnected if this feature is not used.
MAX3241
22 SHDN#
+3V3
BlueMod+SR 23 EN#
VSUP +3V3 RS232
F-4 TXD 14 9 TXD 3
UART_TXD 220R
D-2 RXD 19 4 RXD
UART_RXD 220R 2
D-7 RTS# 13 10 RTS
UART_RTS# 220R 7
F-3 CTS# 18 5 CTS
UART_CTS# 220R 8
B-4 IUR-OUT# 12 11 DTR
IUR-OUT# 220R 4
D-5 IUR-IN# 17 6 DSR
IUR-IN# 220R 6
16 7
DCD 1
GND can be left open
15 8 RI 9
100n 28 26 SigGND
C1+ VCC +3V3 5
24 C1- 27
V+
100n 1 C2+ V-
3 DSUB9 (male)
2 C2- GND 25 DTE style connector
100n 100n 100n
XC6204-3.3
+3V3_switched
VOUT VIN +5VDC
1µ
VSS CE User Host System
100k
10µ+100n+1n
BT_ENABLE (GPIO, Out,
no pu/pd)
BlueMod+SR SN74AVC4T245
VDD_HOST (+1.2 .. +3.6V) VDDIO
VSUP VCCB VCCA (+1.2V .. +3.6V)
1DIR 100k
OE_DRV# (GPIO, Out,
1OE no pu/pd)
D-2 1B1 1A1 TXD
UART_RXD
F-4
UART_TXD
F-3 1B2 1A2 RTS#
UART_CTS#
D-7
UART_RTS#
2DIR
2OE
Assumed that on both sides the TX and RX baud rates are nominally equal, the total baud
rate deviation is the sum of the host baud rate deviation and the BlueMod+SR baud rate
deviation. The total baud rate deviation shall not exceed 2.5% to prevent loss of data. Some
margin should be considered to cover deviations through the transmission line, e.g. due to
asymmetry in low to high and high to low transitions.
The following table shows the BlueMod+SR baud rate deviation in percent of the standard
baud rates caused by the baud rate generator granularity. Add 50ppm for the tolerance of
the local oscillator over the full temperature range.
Custom baud rates (CBR) are generated by a fractional divider according to the formula
𝐵𝑅 14.745.600
=
𝐻𝑧 16 [𝑀𝐴𝑁𝑇𝐼𝑆𝑆𝐴 + 𝐹𝑅𝐴𝐶𝑇𝐼𝑂𝑁]
16
Where data types are for MANTISSA unsigned int12 and for FRACTION unsigned int4.
These values will be programmed to the fractional baud rate generator registers.
BR is the resulting baud rate which might not exactly be the targeted CBR due to the
granularity error of the fractional baud rate generator.
Therefore the baud rate deviation can be calculated by the following procedure:
14.745.600
𝐷𝐼𝑉 =
16 𝐶𝐵𝑅
If FRACTION > 15
MANTISSA := MANTISSA + 1
FRACTION := 0
𝐵𝑅 14.745.600
=
𝐻𝑧 16 [𝑀𝐴𝑁𝑇𝐼𝑆𝑆𝐴 + 𝐹𝑅𝐴𝐶𝑇𝐼𝑂𝑁]
16
𝐷𝑒𝑣𝑖𝑎𝑡𝑖𝑜𝑛 𝐶𝐵𝑅 − 𝐵𝑅
= 100 𝑚𝑎𝑡ℎ. 𝑎𝑏𝑠 [ ]
% 𝐶𝐵𝑅
GPIO Interface
It is possible to use the programmable digital I/Os GPIO[0:8] on the BlueMod+SR. Their
behavior has to be defined project specific in the firmware.
I2C Interface 1
The I2C bus interface serves as an interface between the internal microcontroller and the
serial I2C bus. It provides multimaster capability, and controls all I2C bus specific
sequencing, protocol, arbitration and timing. It supports standard (100kHz) and fast
(400kHz) speed modes.
Rpu Rpu
4k7 4k7
D-3
GPIO[0]/I2C-SCL I2C-SCL
B-2
GPIO[1]/I2C-SDA I2C-SDA
+3.3V
C-1,E-6,F-6
VSUP
NFC Support 2
From SPP firmware version V1.500 on and higher the NFC TAG NXP: NT3H1101 will be
supported by using the following signals:
GPIO[1]/NFC-SDA and GPIO[0]/NFC-SCL are used to form the I2C interface. It is required
to connect 4k7 pull-up resistors on NFC-SCL and NFC-SDA when this interface is used.
Rpu Rpu
4k7 4k7
D-3 3
GPIO[0]/I2C-SCL I2C-SCL
B-2 5
GPIO[1]/I2C-SDA I2C-SDA
GPIO[7]/FD C-3 4 FD (OD)
PU in CPU
+3.3V
C-1,E-6,F-6 6
VSUP VCC
The NFC TAG NXP: NT3H1101 works over the full voltage and temperature range of the
BlueMod+SR.
2 SPP FW version V1.500 and higher will use this interface to support NFC TAG NXP: NT3H1101
I2C interface
1VV0301276 Rev. 14 Page 25 of 84 2017-06-07
GPIO[2]: SPI-MOSI
GPIO[5]: SPI-MISO
GPIO[8]: SPI-SCK
BlueMod+SR Host
SPI-Master SPI-Slave
typical signals:
E-2
GPIO[8]/SPI-SCK SCK, SPI_CLK
D-1
GPIO[2]/SPI-MOSI SDI, MOSI
F-2
GPIO[5]/SPI-MISO SDO, MISO
It is highly recommended that you follow the design rule given in the Telit Application Note
on Antenna design [4].
BT-ACT
BlueMod+SR
BT-STAT WiFi Device
WLAN-DNY
BT-PER
If your application needs to use these signals, ask Telit for support.
SLCK specification:
32,768 kHz typ., 30 kHz min., 35 kHz max. Duty cycle 30...70%.
Signal must be square wave, at VSUP-level (see note below) and present as long
as VSUP is powered.
The module’s firmware will detect the presence of a slow clock during the boot process and
switch behavior appropriately. This check does only apply for presence of some clock; it is
not checked if the clock frequency is in the valid range required by CSR8811 (30kHz ...
35kHz).
If this signal is not used, to minimize risk of erroneous pulse detection in noisy environments,
Telit recommends the connection of A-6 to GND (direct connection or pull-down resistor).
Since SLCK is fed to both the STM32 and the CSR8811, the electrical
characteristics as described in Table 11 (VLSEH) and Table 12 (VIH)
apply both at the same time.
Test Mode
This functionality is reserved. Leave pin TESTMODE# open.
To connect to the module during system memory boot mode, an RS232 serial interface has
to be directly linked to the UART-TXD (F-4) and UART_RXD (D-2) pins.
The bootloader is stored in the internal boot ROM memory (system memory) of MCU. It is
programmed during production. Its main task is to upgrade the firmware to the internal Flash
memory. A communication protocol is defined with a specific command set and sequences.
a Telit provided firmware update tool. This is a Windows™ program that contains
the firmware and uses a PC with a serial port for the update
implementing the system memory boot mode protocol on the host system.
If firmware update shall be performed from a host MCU, signals BOOT0 and EXT-RES#
both must be controlled by that host MCU (GPIO ports). Please note that EXT-RES# must
not be driven directly from a push-pull signal (see chapter 4.3).
As stated in Table 6, the voltage on any I/O pin must not exceed VSUP by more than 0,4V
at any time. Otherwise some current IINJECT flows through the internal protection diodes. This
may damage the module.
There is no problem if the application circuit design and programming can assure that all
signals directed towards BlueMod+SR are set to low (U < 0,3V) before and while VSUP is
turned off. If this is not guaranteed, at least a series resistor (about 1k) must be inserted
into the signal path. This does protect the module but obviously cannot prevent from an
unwanted, additional current flow in case of such signal being at high-level. It may be
necessary to use driver chips in such applications, that gate off these signals while VSUP
is not present.
Leave SWDIO, SWCLK unconnected. Only if you intend to use it for debugging purposes,
make it available and connect SWDIO via a pullup resistor 100kΩ to VSUP (refer to [1]).
Trace Interface 5
The Trace UART TXD interface provides firmware internal trace information and is normally
not used in a customer’s product. In cases where customer support by Telit is requested it
may provide useful information about BlueMod+SR internal states and processes while in
operation. We recommend leaving GPIO[6] unconnected but allowing access to the signal
(e.g. by routing it to a via or a header).
5. MODULE PINS
Pin Numbering
A1 A2 A3 A4 A5 A6 A7 A8
B1 B2 B3 B4 B5 B6 B7 B8
C1 C2 C3 C4 C5 C6 C7 C8
D1 D2 D3 D4 D5 D6 D7 D8
E1 E2 E3 E4 E5 E6 E7 E8
F1 F2 F3 F4 F5 F6 F7 F8
Type: PU – pull-up; PD – pull-down; PWR – Power; I – Input; O – Output; I/O – bidir.; OD – open drain;
PP – push/pull; RF: RadioFreq
(1) a discrete pull up resistor is used
(3) function depends on firmware
(4) DNU: Do not use, do not connect
(5) GPIO pin. These pins may be programmed as analog-in, i-float, i-pu, i-pd, o-pp (output push/pull), o-od (output
A-7,E-7,F-7,
B-[5,6,7,8],
GND Power PWR Ground
C-[5,6,7,8],
D-8, E-8, F-8
A-8 ANT Antenna RF n.c. (/AI) or RF (/AP)
B-1 EXT-RES# Reset I/O-PU L User Reset
32,768kHz Slow Clock
A-6 SLCK SLCK I-PD
(optional)
F-4 UART-TXD TXD O-PP IUR Data OUT
D-2 UART-RXD RXD I-PD IUR Data IN
D-7 UART-RTS# /RTS O-PP (1) L Flow Control/IUC; refer to
F-3 UART-CTS# /CTS I-PD L Flow Control/IUC; refer to [3]
(1)
B-4 IUR-OUT# /IUR-OUT O-PP L UICP Control; refer to [3]
D-5 IUR-IN# /IUR-IN I-PD L UICP Control; refer to [3]
NFC TAG NXP: NT3H1101
I2C SCL (6)
D-3 GPIO[0] I2C_SCL O-OD
and RSSI output
and generic I2C function
NFC TAG NXP: NT3H1101
I2C SDA (6 )
B-2 GPIO[1] I2C_SDA I/O
and RSSI output
and generic I2C function
D-1 GPIO[2] IOC I/O User IO
E-4 GPIO[3] IOB I/O User IO
D-4 GPIO[4] HANGUP I-PD optional; refer to [4]
F-2 GPIO[5] IOD I/O User IO
C-4 GPIO[6] reserved O-PP TRACE UART TXD [4]
NFC TAG NXP: NT3H1101
C-3 GPIO[7] NFC_FD I-PU
Field Detect (3)
E-2 GPIO[8] IOA I/O User IO
A-3 BT-ACT WLAN coexistence O
A-1 BT-STAT WLAN coexistence O
A-4 WLAN-DNY WLAN coexistence I-PD
A-2 BT-PER WLAN coexistence O
F-1 TESTMODE# reserved I-PU L leave open
E-1 BOOT0 reserved I-PD (2) system memory bootloader
E-3 DNU (4) reserved leave open (serial wire)
(4)
D-6 DNU reserved leave open (serial wire)
Type: PU – pull-up; PD – pull-down; PWR – Power; I – Input; O – Output; I/O – bidir.; OD – open drain;
PP – push/pull; RF: RadioFreq
(1) a discrete pull up resistor is used
(2) a discrete pull down resistor is used
(3) function depends on firmware
(4) DNU: Do not use, do not connect
(5) If trace feature should be used, this signal has to be made accessible in customer hardware
(6) NFC support will be available with SPP FW version V1.500 and higher. Use 4k7 PU each on signals
(*) for being able to update the firmware, it is strongly recommended to provide for a means
to set BOOT0 temporarily to logic high level, and to reset the module; see chapter 4.14.
6. ELECTRICAL CHARACTERISTICS
Absolute Maximum Ratings
Stresses beyond those listed under “Absolute Maximum Ratings” may cause permanent
damage to the device. These are stress ratings only, and functional operation of the device
at these or any other conditions beyond those indicated under “Electrical Requirements” is
not implied. Exposure to absolute-maximum-rated conditions for extended periods may
affect device reliability.
Electrical Requirements
VSUP = 3,3V, Tamb = 25 °C if nothing else stated
Operating Conditions
Tamb = 25 °C
Environmental Requirements
Table 9: Environmental requirements
STM-Related Signals:
Tamb = 25 °C
Tamb = 25 °C
Signal at SLCK is also fed to CSR8811 and has to comply to Table 12,
too.
Tamb = 25 °C
internal 3,6
Sleep mode, no page scan, no inquiry scan mA
external 3,5
Deep sleep mode, no page scan, no inquiry scan, UICP (1) internal 0,29
mA
active Interface down external 0,15
(2) (3)
Device in reset 2,7 mA
VSUP = 3,3V, Tamb = 25°C, all GPIOs and UART lines open, SLCK: 32,768 kHz
(1) IUR-IN# and UART-CTS# signals connected to CMOS high level
(2) Valid for HW V3, higher in HW Version < 3
(3) Same current consumption w. internal or external slow clock
internal 4,2
Standby, page scan & inquiry scan interval 1,28s mA
external 4,0
Standby, page scan & inquiry scan interval 1,28s,UICP (1) internal 0,9
mA
active serial Interface down external 0,75
(2) (3)
Bluetooth connected, no data traffic (Slave) 14,4 mA
(2) (3)
Bluetooth connected, data traffic 115 kbit/s (Slave) 22 mA
(2) (3)
Bluetooth connected, no data traffic (Master) 9,3 mA
Bluetooth connected, no data traffic, active sniff using (2) (3) 5,0 mA
250 ms sniff interval (Master)
Bluetooth connected, no data traffic, active sniff using (2) (3) 1,9 mA
250 ms sniff interval, UICP active (Master)
Bluetooth connected, no data traffic, active sniff using (2) (3) 4,6 mA
500 ms sniff interval (Master)
Bluetooth connected, no data traffic, active sniff using (2) (3) 1,6 mA
500 ms sniff interval, UICP active (Master)
(2) (3)
Bluetooth connected, data traffic 115 kbit/s (Master) 20 mA
VSUP = 3,3V, Tamb = 25°C, Tx Power = 7 dBm, all GPIO lines left open, SLCK: 32,768 kHz
(1) IUR-IN# and UART-CTS# signals connected to CMOS high level
(2) about 2 meters through the air
(3) Same current consumption w. internal or external slow clock
6.6.2. LE Configurations
Table 16: Supply current BLE Terminal I/O Profile, peripheral device role, CI 7,5ms
Item Note Slow Current Unit
clock Consumption
SLCK
Tx power (dBm)
max (+7) min (-23)
IAvg IAvg
(2,3) (6)
Connected, connection interval: 7,5 ms, no data traffic 9,6 8,8 mA
Connected, connection interval: 7,5 ms, data traffic 115 (2) (6) 24 22 mA
kbit/s at the serial port, central to peripheral
Connected, connection interval: 7,5 ms, data traffic 115 (2) (6) 27 23 mA
kbit/s at the serial port, peripheral to central
Table 17: Supply current BLE Terminal I/O Profile, peripheral device role, CI 37,5ms
Item Note Slow Current Unit
clock Consumption
SLCK
Tx power (dBm)
max (+7) min (-23)
IAvg IAvg
VSUP = 3,3V, Tamb = 25°C, all GPIO lines left open, SLCK: 32,768 kHz
(1) UART-CTS#, IUR-IN# driven to CMOS high level, all other UART-lines left open
(2) Connection parameters are setup by the central device when connection is established
(3) No data to be transmitted, central device sends an empty packet (80 bit) then peripheral device answers
role
(5) All UART-lines left open
(6) Same current consumption w. internal or external slow clock
Table 19: Supply current BLE Terminal I/O Profile, central device role, CI 7,5ms
Item Note Slow Current Unit
clock Consumption
SLCK
Tx power (dBm)
max (+7) min (-23)
IAvg IAvg
(2,3) (6)
Connected, connection interval: 7,5 ms, no data traffic 10,8 10,1 mA
Connected, connection interval: 7,5 ms, data traffic,
(2) (6)
data traffic 115 kbit/s at the serial port, central to 28 25 mA
peripheral
Connected, connection interval: 7,5 ms, data traffic,
(2) (6)
data traffic 115 kbit/s at the serial port, peripheral to 25 23 mA
central
Table 20: Supply current BLE Terminal I/O Profile, central device role, CI 37,5ms
Item Note Slow Current Unit
clock Consumption
SLCK
Tx power (dBm)
max (+7) min (-23)
IAvg IAvg
(2,4) (6)
Connected, connection interval: 37,5ms, no data traffic 5,8 5,6 mA
Connected, connection interval: 37,5ms, data traffic 115 (2,4) (6) 16,5 15 mA
kbit/s at the serial port; central to peripheral
VSUP = 3,3V, Tamb = 25°C, all GPIO lines left open, SLCK: 32,768 kHz
(2)
Connection parameters are setup by the central device when connection is established
(3) No data to be transmitted, central device sends an empty packet (80 bit) then peripheral device answers
(empty packet: 80 bit)
(4) These are typical connection parameters used by an iPhone, iPad or iPad mini device in the central device
role
(6) Same current consumption w. internal or external slow clock
RF Performance
6.7.1. GFSK, PI/4 DQPSK, 8DPSK Receiver
VSUP = 2,5V to 3,6V, Tamb = +20°C
Measured conducted according to BT specification v1.2/2.0/2.0 + EDR/2.1/2.1 +
EDR/3.0/3.0 + HS/4.0
Receiver Frequency [GHz] Limit BT Spec Unit
Min Typ Max
2.402 -84 -80
Sensitivity at 0.1% BER DH1 2.441 -88 -84 -70 dBm
2.480 -88 -84
2.402 -84 -80
Sensitivity at 0.1% BER DH5 2.441 -88 -84 -70 dBm
2.480 -88 -84
2.402 -87 -70
Sensitivity at 0.1% BER
2.441 -91 -70 -70 dBm
EDR2, PI/4 DQPSK
2.480 -91 -70
2.402 -78 -70
Sensitivity at 0.1% BER
2.441 -82 -70 -70 dBm
EDR3, 8DPSK
2.480 -82 -70
Maximum received signal at 0.1% BER with DH1 -20 0 -20 dBm
Maximum received signal at 0.1% BER with DH5 -20 0 -20 dBm
Maximum received signal at 0.1% BER with EDR2,
-20 0 -20 dBm
PI/4 DQPSK
Maximum received signal at 0.1% BER with EDR3,
-20 0 -20 dBm
8DPSK
C/I co-channel GFSK 8 11 11 dB
Adjacent channel selectivity C/I f = f0 + 1MHz GFSK -2 0 0 dB
Adjacent channel selectivity C/I f = f0 - 1MHz GFSK -1 0 0 dB
Adjacent channel selectivity C/I f f0 + 2MHz GFSK -39 -30 -30 dB
Adjacent channel selectivity C/I f f0 - 2MHz GFSK -30 -30 -20 dB
Adjacent channel selectivity C/I f f0 + 3MHz GFSK -45 -40 -40 dB
Radiation Pattern will depend on the end products PCB size, masses in the antenna
environment, housing material and geometrics.
Z
X
Z
X
Z
X
Power-Up Time
The time until the BlueMod+SR is able to accept link requests or serial data depends on the
firmware version. In the SPP firmware the module is command ready and Bluetooth links
are accepted at least 1,1 s after signal EXT-RES# is de-asserted or VSUPx is in a valid
range.
7. MECHANICAL CHARACTERISTICS
Dimensions
2,6 +0,25
2,8+0,25
-0,25
-0,25
+0,1 +0,2 +0,1
0,1 -0,1
17,0 -0,0
0,1 -0,1
1,8
1,8
7x1,5=10,5
A1 A2 A3 A4 A5 A6 A7 A8
B1 B2 B3 B4 B5 B6 B7 B8
5x1,5=7,5
C1 C2 C3 C4 C5 C6 C7 C8
1,25
D1 D2 D3 D4 D5 D6 D7 D8
E1 E2 E3 E4 E5 E6 E7 E8
F1 F2 F3 F4 F5 F6 F7 F8
1,25 0,9
Figure 17: BlueMod+SR land pattern TOP VIEW
Devices will withstand the specified profile and will withstand up to 1 re-flows to a maximum
temperature of 260°C. The reflow soldering profile may only be applied if the BlueMod+SR
resides on the PCB side looking up. Heat above the solder eutectic point while the
BlueMod+SR is mounted facing down may damage the module permanently.
Placement Recommendation
To achieve best radio performance for BlueMod+SR/AI, it is recommended to use the
placement shown in Figure 19. This is a “corner placement” meaning the BlueMod+SR is
placed such that the antenna comes close to the corner of the application PCB (red area).
So, the yellow area is outside the PCB and regards to the housing, too (refer to 7.5).
Please note that for best possible performance the antenna should be directed away from
the application PCB as shown in Figure 19.
20
17
4,5
max.0,5
40
max.0,5
10
15
Housing Guidelines
The individual case must be checked to decide whether a specific housing is suitable for
the use of the internal antenna. A plastic housing must at least fulfill the following
requirements:
Antenna Issues
BlueMod+SR is shipped with 2 different antenna designs:
For an external antenna to be set in, e.g. because the BlueMod+SR is integrated into a
metal housing, the ceramic antenna is replaced.
When using an external Antenna the antenna must be fixed and shall not be removable or
replaceable by the end user. In any case, the performance of the antenna (whether it is
internal or external) has to be checked within the final integration environment. Adjacent
PCBs, components, cables, housings etc. could otherwise influence the radiation pattern or
be influenced by the radio wave energy.
It must be ensured that the antenna is not co-located or operating in conjunction with any
other antennas, transmitters, cables or connectors. When the internal ceramic antenna is
used, certain restrictions are to be considered.
Safety Guidelines
According to SAR regulation EN 62479:2010 the BlueMod+SR is not intended to be used
in close proximity to the human body. Please refer to above mentioned regulation for more
specific information.
In respect to the safety regulation EN60950-1: 2006 + A11: 2009 + A1: 2010 + AC:2011 all
conductive parts of the BlueMod+SR are to be classified as SELV circuitry. OEM’s
implementing the BlueMod+SR in their products should follow the isolation rules given in
regulation EN 60950-1: 2006.
Cleaning
In general, cleaning the modules mounted on the host board is strongly discouraged.
Residues between module and host board cannot be easily removed with any cleaning
method.
Cleaning with water or any organic solvent can lead to capillary effects where the
cleaning solvent is absorbed into the gap between the module and the host board.
The combination of soldering flux residues and encapsulated solvent could lead to
short circuits between conductive parts. The solvent could also damage any labels.
Ultrasonic cleaning could damage the module permanently. Especially for crystal
oscillators the risk of damaging is very high.
8. APPLICATION DIAGRAM
The following schematic shows a typical application of BlueMod+SR. The module is
connected to some MCU running the application layer. MCU and BlueMod+SR use the
same 3,3V power supply. Provisions are made for upgrading the firmware (BOOT0 and
EXT-RES# are managed by the MCU). The serial interface has RTS/CTS flow control but
no UICP support in this example. The Hangup feature to close down the link is provided.
As an option to save power, there is an external slow clock oscillator. All other module pins
may be left unconnected.
+3V3
all GND pads (14) must be connected.
Blocking capacitors not shown.
32,768kHz
square
In this example BlueMod+SR is connected to an MCU supporting RTS/CTS flow control and Hangup.
Firmware update is supported (BOOT0, EXT-RES# connected).
The slow clock oscillator (32,768kHz ) is optional; it helps to save power during power down states.
9. APPROVALS/CERTIFICATIONS
The BlueMod+SR/AI has been tested to comply to the appropriate EU, FCC and IC
directives.
CE testing is intended for end products only. Therefore CE testing is not mandatory for a
Bluetooth Module sold to OEM’s. However Telit provides CE tested modules for customers
in order to ease CE compliance assessment of end products and to minimize test effort.
Declaration of Conformity CE
The BlueMod+SR/AI or /AP fully complies with the essential requirements of the following
EU directives:
RED 2014/53/EU (Variant /AP for external antennas with less than +2dBi gain)
RoHS 2011/65/EC
The actual version of EU Declaration of Conformity (EU DoC) can be downloaded from
http://www.telit.com/RED
FCC Compliance
The BlueMod+SR/AI has been tested to fulfill the FCC requirements. Test reports are
available on request. Grants of the Full Modular Approval will be shown below.
BlueMod+SR/AP only:
For selling products implementing the BlueMod+SR/AP in the USA you’ll have to apply for
a Class II Permissive Change from the FCC authorities. Depending on antenna gain and
other factors the FCC TCB will issue a reduced test plan for re-testing. Telit can assist
customers with conducting this procedure on request. Especially the test plan reduction and
cost optimization may be items worth to look at.
Warning:
Changes or modifications made to this equipment not expressly
approved by Telit may void the FCC authorization to operate this
equipment.
The output power is < 10mW EIRP and therefore according to “FCC KDB 447498 D01
General RF Exposure Guidance v05” Appendix A, table “SAR Exclusion Threshold”,
excluded from SAR testing for test separation distances ≥5mm and if it is not used in co-
locations with other antennas. If the product implementing the BlueMod+SR/AI has other
antennas in co-location or separation distances < 5mm an FCC TCB should be asked for a
Class II Permissive Change.
IC Compliance
The BlueMod+SR/AI has been tested to fulfill the IC requirements. Test reports RSS-210 of
Industry Canada are available on request. Grants of the Full Modular Approval will be shown
below.
For selling products implementing the BlueMod+SR/AP in Canada you’ll have to apply for
a Class II Permissive Change from the IC authorities. Depending on antenna gain and other
factors the IC TCB will issue a reduced test plan for re-testing. Telit can assist customers
with conducting this procedure on request. Especially the test plan reduction and cost
optimization may be items worth to look at.
9.3.1. IC Grant
9.3.2. IC Statement
(i) Ce dispositif doit être installé et exploité dans une enceinte entièrement fermée afin de
prévenir les rayonnements RF qui pourraient autrement perturber la navigation
aéronautique. L’installation doit être effectuée par des installateurs qualifiés, en pleine
conformité avec les instructions du fabricant.
NOTICE:
9.3.3. IC Caution
Warning:
Changes or modifications made to this equipment not expressly
approved by Telit may void the IC authorization to operate this
equipment.
The BlueMod+SR shows no IC-ID on the product label, because there is no space available.
IC allows on request to state the IC-ID in the product manual. This product has been granted
to do so.
Model: BlueMod+SR
KC Certification
The BlueMod+SR/AI has been certified in Korea under the Clause 2, Article 58-2 of Radio
Waves Act. Certificate is shown below with MSIP-CRM-Rfr-BlueModSR.
9.4.1. KC Certificate
MIC Certification
The BlueMod+SR has been tested to fulfill the Japanese MIC requirements.
Please note that the Japanese Certificates are only valid for the
variants using the internal ceramic antenna, denoted by the string “AI”
in the product name.
BlueMod+SR modules designed for the use with an external antenna,
denoted by the string “AP” in the product name, do need extra
procedures if another antenna than in the following list of Approved
External Antennas is intended to be used.
日本の電気通信事業法と電気通信事業法の基準
本製品は、電波法と電気通信事業法に基づく適合証明を受けております。
This device should not be modified (otherwise the granted designation number will become
invalid)
本製品の改造は禁止されています。(適合証明番号などが無効となります。)
Anatel Certification
The BlueMod+SR/AI has been certified in Brazil by Anatel.
Bluetooth Qualification
The BlueMod+SR is a qualified design according to the Bluetooth Qualification Program
Reference Document (PRD) V2.3.
For further information about marking requirements of your product attention should be paid
the Bluetooth Brand Usage Guide at
https://www.bluetooth.org/en-us/bluetooth-brand/bluetooth-brand
According to the Bluetooth SIG rules (Bluetooth Declaration Process Document - DPD) you
must complete a Product Listing and Declaration of Compliance (DoC) referencing the
Qualified Design (QDID) for your product. For further information see www.bluetooth.org or
contact Telit.
RoHS Declaration
The BlueMod+SR/AI and BlueMod+SR/AP do fully comply with EU RoHS directive.
RoHS 2011/65/EC
The actual version of RoHS Declaration of Conformity (EU DoC) can be downloaded from
the Telit Download Zone:
http://www.telit.com/download-zone/
Take note that you have to register to get access to the Download Zone.
10. PACKING
The BlueMod+SR modules are packed either as Tape&Reel or as tray packing.
Tape&Reel Packing
The BlueMod+SR modules are packed using carrier tape in this orientation.
ABC
ABC
ABC
module type + label as example only
ABC
10.1.1. Tape
The dimensions of the tape are shown in the drawing below (values in mm):
+0,10
-0,10
+0,1
12,0 1,5 -0,0
1,75
+0,1 +0,2
0,3 2,0 -0,1
10x4,0=40,0 -0,2
+0,1
-0,1
11,5
+0,3
-0,3
+0,1
-0,1
24,0
18,3
R
+0,1
3,0 10,9
0,
-0,1
10.1.2. Reel 5
label content as example only
40
name XXXXXXXXXXXXXXXX
p/n aaaaa-aa
firmware b/c FCC ID: RFRMS
fw p/n ddddd-dd IC: 4957A-MS
trace mwwyy
quantity q
330
Tray Packing
10.2.1. Module Orientation
Do not disassemble the product; any mark of tampering will compromise the warranty
validity. We recommend following the instructions of the hardware user guides for correct
wiring of the product. The product has to be supplied with a stabilized voltage source and
the wiring has to be conformed to the security and fire prevention regulations. The product
has to be handled with care, avoiding any contact with the pins because electrostatic
discharges may damage the product itself. Same cautions have to be taken for the SIM,
checking carefully the instruction for its use. Do not insert or remove the SIM when the
product is in power saving mode.
The system integrator is responsible for the functioning of the final product; therefore, care
has to be taken to the external components of the module, as well as any project or
installation issue, because the risk of disturbing the GSM network or external devices or
having impact on the security. Should there be any doubt, please refer to the technical
documentation and the regulations in force. Every module has to be equipped with a proper
antenna with specific characteristics. The antenna has to be installed with care in order to
avoid any interference with other electronic devices and has to guarantee a minimum
distance from the body (20 cm). In case this requirement cannot be satisfied, the system
integrator has to assess the final product against the SAR regulation.
The European Community provides some Directives for the electronic equipment
introduced on the market. All of the relevant information is available on the European
Community website:
http://ec.europa.eu/enterprise/sectors/rtte/documents/
The text of the Directive 99/05 regarding telecommunication equipment is available, while
the applicable Directives (Low Voltage and EMC) are available at:
http://ec.europa.eu/enterprise/sectors/electrical/