Ezurio 01B The Intelligent Bluetooth Serial Module Version II User Manual Hardware Interface Description

Download:
Mirror Download [FCC.gov]
Document ID	579850
Application ID	tR/PTuDxm39zftpu8kTmnA==
Document Description	Users Manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	35.71kB (446358 bits)
Date Submitted	2005-09-09 00:00:00
Date Available	2005-09-09 00:00:00
Creation Date	2005-07-13 03:14:43
Producing Software	Acrobat Distiller 7.0 (Windows)
Document Lastmod	2005-07-13 03:18:10
Document Title	Hardware Interface Description
Document Creator	Acrobat PDFMaker 7.0 for Word
Document Author:	Nick Letheren

BISM2 Bluetooth™ Version 2.0 Serial Module
1. General Description
Ezurio’s BISM2 Bluetooth Serial Module is a fully integrated and qualified Class 1 Bluetooth solution
designed for lowest cost of integration and ownership for designers wishing to incorporate Bluetooth
functionality into their products. The module is qualified to Bluetooth Version 2.0.
The BISM2 Bluetooth Serial Module is one of the most compact complete Bluetooth solutions, making
it ideal to integrate into handheld devices. However a version of the BISM2 module is available that
retains the same board size, mounting holes and connector as the previous Bluetooth Module from
Ezurio, allowing users to access the improved radio performance and functionality without the need
for any pcb modifications.
The BISM2 Module is based on Cambridge Silicon Radio’s BlueCore 04 chipset. The module contain
all of the hardware and firmware for a complete Bluetooth solution, requiring no further components.
The Module has an integrated, high performance antenna which is matched with the Bluetooth RF and
baseband circuitry. The firmware integrated into the BC04 chipset implement the higher layer
Bluetooth protocol stack, up to and including the Generic Access Profile (GAP), Service Discovery
Profile (SDAP), Serial Port Profile (SPP), Dial Up Networking Profile (DUN), Headset Profile (HSP),
Hands Free Profile (HFP), File Transfer Profile (FTP) and Audio Gateway. A virtual processor is used
within the BC04 to implement an AT command processor. This interfaces to the host system over a
straight forward serial port using an extensive range of AT commands. The AT command set abstracts
the Bluetooth protocol from the host application, saving many months of programming and
integration time. It provides extremely short integration times for data oriented cable replacement
and voice applications. A low cost development system is available for fast product evaluation and
development.
An alternative version of firmware is available that provides programming support for multi-point
applications.
The Module can be configured so that it can be attached to a ‘dumb’ terminal or attached to a PC or
PDA for cable replacement applications.
In addition to the Bluetooth functionality, The BISM2 Module provides access to 9 General I/O lines
and 2 analogue input lines. These can be configured to provide connection to simple devices such as
switches or LEDs without requiring any external processing. Both the GPIO and ADC lines can be
accessed either via the wired host UART connection, or remotely over the Bluetooth link.
The BISM2 module is supplied in a small form factor pcb (22.0mm x 34.0mm x 7.6mm), that
connects to a main pcb using a 40 way Hirose connector. The interface is compatible with the BISM1
module. The module includes a high sensitivity, high gain antenna which provides excellent range.
Typical open field performance provides ranges of over 250 metres at transmit powers of 4mW.
Support is provided for low power modes that make the BISM2 particularly applicable to battery
powered installations.
The BISM2 module is Lead-free and is RoHS compliant and supports an industrial temperature range
of -40°C to +85°C.
1.1 Applications
•
POS Equipment
•
Voice Applications
•
Medical Equipment
•
Industrial Automation
•
Telematics
•
Automotive Applications
Bluetooth is a trademark owned by Bluetooth SIG, Inc., USA, and is licensed to Ezurio Ltd
Module shown without RF shield
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
2. Features
Feature
Implementation
Bluetooth Transmission
Class 1
Fully Bluetooth pre-qualified
Bluetooth 2.0
Range
250 metres typical (free space)
Frequency
2.400 – 2.485 GHz
Max Transmit Power
+6dBm
Min Transmit Power
+0dBm
Receive Sensitivity
Better than -90dB
Antenna Gain
+2dBi
Data Transfer rate
Up to 300Kbps
Serial Interface
RS-232 bi-directional for commands and data using AT commands
Serial parameters
Default 9600,n,8,1 - Configurable from 1,200bps to 961,200 bps.
Support for DTR, DSR, DCD, RI, RTS, CTS
Physical size
22.8 x 33.8 x 7.6 mm, 8g
24.0 x 69.0 x 7.6mm, 9g (BISM1 Form Factor)
Current consumption
Less than 36mA during data transfer in standard power mode. Lower
powers are attainable with a configurable low power mode.
Low power sniff mode
2.5mA typ
Temperature Range
Normal operation: -40°C to +85°C
Supply Voltage
3.6V – 7.0V
Brown-out
Integrated brown out detection
Interface Levels
3.3V Logic
Audio
Audio can be transferred over SCO channels through the PCM interface
at 64kbps. PCM can be configured as master or slave.
Profiles
Server - SPP (Full), DUN, Audio Gateway, Headset, Handsfree
Client - All RFCOMM based profiles
Multipoint
Max 7 slaves
Field upgradeable
Over UART
Protocols
Single point firmware is controlled and configured using AT
Commands. Standard multipoint firmware uses a simple packet based
protocol and requires a host to enable the module to function
effectively.
Single point only allows a point to point connection whereas multipoint
allows more than one simultaneous connection.
GPIO
9 x digital
2 x analogue (8 bit resolution)
Indicators
1 x programmable LED (small form factor board only)
Lead free
Lead-free and RoHS compliant
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
3. Functional Block Diagram
3.1 Connection Diagram
The Module is equipped with a 40-pin 0.5mm pitch board-to-board connector that connects to the
application platform.
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
3.2 Pin Descriptions
The Hirose DF12C board-to-board connector on the module is a 40-pin double-row receptacle.
The table below defines the pin functions. Note that this pin-out is as viewed from the underside of
the Module.
Pin
No.
Signal
Description
Pin
No.
Signal
Description
Analogue 0
1.8v Max
GPIO1
I/O for Host.
Analogue 1
1.8v Max
GPIO2
I/O for Host
SPI_MISO
SPI bus serial O/P
UART_RI
‘Ring’ Input or Output
SPI_CSB
SPI bus chip select I/P
UART_DCD
Input or Output
SPI_CLK
SPI bus clock I/P
10
UART_DSR
Input
11
GND
12
GPIO3/UART_DTR
I/O for Host
13
RESET
14
GPIO4
I/O for Host & LED
15
GND
16
GPIO5
I/O for Host
17
SPI_MOSI
SPI bus serial I/P
18
GND
19
UART_CTS
Clear to Send I/P
20
PCM_CLK
PCM Clock I/P
21
UART_TX
Transmit Data O/P
22
PCM_IN
PCM Data I/P
23
UART_RTS
Request to Send O/P
24
PCM_SYNC
PCM Sync I/P
25
UART_RX
Receive Data I/P
26
PCM_OUT
PCM Data O/P
27
VCC_3V3
3.3V Monitor
28
N/C
29
VCC_5V
3.6V < VIN < 7.0V
30
GND
31
N/C
32
USB / RESERVED
Do not connect
33
GPIO6 **
I/O for Host
34
USB / RESERVED
Do not connect
35
GPIO7 **
I/O for Host
36
GND
37
GPIO8 **
I/O for Host
38
GND
39
GPIO9
I/O for Host
40
N/C
Reset I/P *
Notes:
* The reset circuitry within the BISM Serial Modules now incorporates a brown-out detector within
the module. Customers migrating from previous modules should check their implementation, as they
may be able to simplify their external power supply design. The reset line has a fixed 10kOhm pull
down resistor to ground.
** Pins 33, 35 and 37 were N/C on BISM1. Pin 39 was a 1V8 monitor. Designers migrating between
designs should be aware that these are now available as I/O. Default configuration is as an input
PIO lines can be configured through software to be either inputs or outputs with weak or strong pullups or pull-downs. At reset, all PIO lines are configured as inputs with weak pull-downs.
UART_RX, UART_TX, UART_CTS, UART_RTS, UART_RI, UART_DCD and UART_DSR are all 3.3v level
logic. For example, when RX and TX are idle they will be sitting at 3.3V. Conversely for handshaking
pins CTS, RTS, RI, DCD, DSR a 0v is treated as an assertion.
Pin 6 (UART_RI) is active low. It is normally 3.3v. When a remote device initiates a connection, this
pin goes low. This means that when this pin is converted to RS232 voltage levels it will have the
correct voltage level for assertion.
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
Pin 8 (UART_DCD) is active low. It is normally 3.3v. When a connection is live this pin is low. This
means that when this pin is converted to RS232 voltage levels it will have the correct voltage level for
assertion.
Pin 10 (UART_DSR) is an input, with active low logic. It should be connected to the DTR output of the
host. When the BISM2 Module is in high speed mode (See definition for S Register 507), this pin
should be asserted by the host to ensure that the connection is maintained. A deassertion is taken to
mean that the connection should be dropped, or an online command mode is being requested.
Pin 27 (VCC_3V3 monitor) may only be used for monitoring purposes. It must not be used as a
current source.
The GPIO pins can be accessed using S Registers 621 to 628. GPIO4 is connected to an LED on the
module. If these I/O pins are set for input, then the LED will be driven by the host and appropriate
drive current requirements must be satisfied. A Logic 1 switches on the LED.
GPIO3 is also used for DTR output (active low). See S Register 552 & 553.
Analogue 0 and 1 should not exceed 1.8v and S Registers 7xx are used to access them.
3.3 Electrical Specifications
3.3.1
Absolute Maximum ratings
Absolute maximum ratings for supply voltage and voltages on digital and analogue pins of the Module
are listed below; exceeding these values will cause permanent damage.
Parameter
Min
Max
Unit
Peak current of power supply
100
mA
Voltage at digital pins
-0.3
3.7
Voltage at POWER pin
3.6
3.3.2
Recommended Operating Parameters
3.3.2.1
Power Supply
Signal Name
Pin No
I/O
Voltage level
Comments
Vcc
29
3.6V to 7.0V
Ityp = 30mA
GND
11, 15, 18,
30, 36, 38
VCC_3V3
27
3.3.2.2
6 Ground terminals to be attached
in parallel
3.3V typical
For monitoring only. No current
source
RS-232 Interface
Signal Name
Pin No
I/O
Signal level
UART_TX
21
VOLmax=0.2V
Comments
VOHmin=2.8V
UART_RX
25
VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
UART_CTS
www.ezurio.com
19
VILmax=0.8V
Version 1.03 © Ezurio Ltd 2005
VIHmin=2.1V
VIHmax=3.7V
UART_RTS
23
VOLmax=0.2V
VOHmin=2.8V
UART_DSR
10
VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
UART_DTR
12
VOLmax=0.2V
Shared with GPIO3
VOHmin=2.8V
UART_RI
I or O
O/P : VOLmax=0.2V
Direction may be programmed.
VOHmin=2.8V
I/P
: VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
UART_DCD
I or O
O/P : VOLmax=0.2V
Direction may be programmed.
VOHmin=2.8V
I/P
: VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
3.3.2.3
SPI Bus
Signal Name
Pin No
I/O
Signal level
Comments
SPI_MOSI
17
VILmax=0.8V
Used to reprogram Flash
VIHmin=2.1V
VIHmax=3.7V
SPI_MISO
VOLmax=0.2V
VOHmin=2.8V
SPI_CSB
VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
SPI_CLK
VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
3.3.2.4
PCM Interface
Signal Name
Pin No
I/O
Signal level
Comments
PCM_CLK
20
I or O
O/P : VOLmax=0.2V
If unused keep pins open
VOHmin=2.8V
I/P
: VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
PCM_IN
22
VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
PCM_SYNC
24
I or O
O/P : VOLmax=0.2V
VOHmin=2.8V
I/P
: VILmax=0.8V
VIHmin=2.1V
VIHmax=3.7V
PCM_OUT
26
VOLmax=0.2V
VOHmin=2.8V
3.3.2.5
General Purpose I/O and ADC
Signal Name
Pin No
I/O
Signal level
GPIO 1 - 9
2,4,12,
I or O
O/P : VOLmax=0.2V
14,16,
Comments
VOHmin=2.8V
33, 35,
I/P
: VILmax=0.8V
37, 39
VIHmin=2.1V
VIHmax=3.7V
AIO_0, AIO_1
3.3.2.6
1, 3
I/O
Range 0 – 1.8V
Miscellaneous
Function
Signal Name
Pin No
I/O
Signal level
Comments
Reserved
USB D-
32
VILmax =0.3vdd_usb
Normally inactive.
Pull to GND
through 10K
VIHmin =0.7vdd_usb
Reserved
Reset
USB D+
RESET
34
13
VILmax =0.3vdd_usb
VIHmin =0.7vdd_usb
Normally inactive.
Pull to GND
through 10K
Threshold 2.6V
Active HIGH
Terminology:
USB Signal Levels. vdd_usb refers to the internal voltage generated by the LDO regulator on the
module, which is typically 3.3V. Hence 0.3vdd_usb and 0.7vdd_usb correspond to 1.0V to 2.3V. If
Vcc falls below the recommended minimum of 3.6V, these values will be reduced.
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
4. I/O Characteristics
4.1 Power Consumption
The current drain from the Vcc power input line is dependent on various factors. The three most
significant factors are the voltage level at Vcc, UART Baudrate and the operating mode.
The hardware specification for the Module allows for a voltage range of 3.6 to 7.0 at Vcc. Tests have
shown that there is no significant difference in current draw when Vcc is 5 or 6V. Therefore the data
presented below, pertains to Vcc levels of 3.6 and 5v only. Tests have shown that where power drain
is an issue, it is best to keep Vcc at the lower end of the range.
The UART baudrate has a bearing on power drain because as is normal for digital electronics, the
power requirements increase linearly with increasing clocking frequencies. Hence higher baudrates
result in a higher current drain.
Finally with regards to operating mode the significant modes are; idle, waiting for a connection,
inquiring, initiating a connection, sniff and connected. With connected mode, it is also relevant to
differentiate between no data being transferred and when data is being transferred at the maximum
rate possible. The AT command Set document describes how to configure the Module for optimal
power performance.
4.1.1
Typical Current Consumption in mA
Baudrate
Idle Mode, S512=1
Wait for Connection Or Discoverable Mode,
AT+BTP
S508=S510=640, S509=S511=320
Wait for Connection Or Discoverable Mode,
AT+BTP
S508=S510=1000, S509=S511=11*
Inquiring Mode, AT+BTI
Connecting Mode (ATDxxx)
Connected Mode (No Data Transfer)
Connected Mode (Max Data Transfer)
9,600
38,400
115,200
460,800
3.6v
1.60
1.80
1.96
3.00
5.0v
2.00
2.10
2.30
3.40
3.6v
59.00
59.00
59.00
59.00
5.0v
65.00
65.00
65.00
65.00
3.6v
2.75
2.94
3.10
4.12
5.0v
3.26
3.36
3.55
4.63
3.6v
50.00
50.00
50.00
50.00
5.0v
54.00
54.00
54.00
54.00
3.6v
50.00
50.00
50.00
50.00
5.0v
54.00
54.00
54.00
54.00
3.6v
6.00
6.10
6.40
7.20
5.0v
7.20
7.20
7.40
8.20
3.6v
21.50
22.50
24.50
32.50
5.0v
24.50
26.00
28.00
36.00
Notes: These figures were obtained with pre-production firmware. Production values will typically be
20% lower.
* Calculated figures
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
5. DC Characteristics
5.1 RF Performance
5.1.1
Transmit Power
Conducted Transmit Power
min: 1.0mW (0dBm)
Antenna Gain
+2dBi typ.
Effective Transmit Power
min:0dBm
max: 4mW (6dBm)
Max: +6dBm
Output power can be reduced by program control
5.1.2
Receive Sensitivity
Receive Sensitivity
-86dBm (at 25°C)
Antenna Gain
+2dBi typ
Effective Receive Sensitivity
-88dBm (at 25°C)
5.1.3
RF Performance Data
Receive Sensitivity
-40 deg
-20 deg
0 deg
20 deg
40 deg
60 deg
80 deg
100 deg
-10
-20
Attenuation Setting dBm
-30
-40
-50
-60
-70
-80
-90
NOTE: Measured as attenuation required
to achieve better than 0.1% BER
-100
Temperature Deg. C.
5.2 Range
See the Data Transfer Rate vs. distance graph below. The data throughput of the Module is limited to
280Kbps by the parsing of the data being transferred through the RFCOMM stack. The graph below
shows the typical data throughput. Distances are measured in free space between 2 Modules.
www.ezurio.com
Version 1.03 © Ezurio Ltd 2005
Data Transfer Rate / Distance
800
700
Data Transfer Rate (kbps)
600
500
RF data rate
Serial port data rate
400
300
200
100
10m
50m
100m
150m
200m
250m
300m
Distance (meters)
5.3 Temperature Performance
Data Transmit Rate with Temperature and Attenuation
800
700
600
Data Transmission Rate kbs
-40 deg
-20 deg
500
0 deg
20 deg
400
40 deg
60 deg
300
80 deg
200
100 deg
100
-60dBm
-65dBm
-70dBm
-75dBm
-80dBm
-85dBm
-90dBm
dBm attenuation
www.ezurio.com
10
Version 1.03 © Ezurio Ltd 2005
6. Functional Description
The BISM2 Bluetooth module is a self-contained Bluetooth product and requires only power to
implement full Bluetooth communication. The integrated, high performance antenna together with the
RF and Base-band circuitry provides the Bluetooth wireless link and the UART interface provides a
connection to the host system.
The variety of interfaces and the AT command set allow the BISM2 module to be used for a wide
number of short range wireless applications, from simple cable replacement to complex multipoint
applications, where multiple radio links are active at the same time.
The complexity and flexibility of configuration are made simple for the design engineer by the
integration of a extremely comprehensive set of AT commands, supplemented with a range of “S”
registers which are used for non-volatile storage of system parameters. These are fully documented
in the “Blu2i AT Command Reference Manual”.
To provide the widest scope for integration a range of different physical host interfaces are provided:
6.1 Interfaces
6.1.1
UART interface
UART_TX, UART_RX, UART_RTS and UART_CTS form a conventional asynchronous serial data port
with handshaking. The interface is designed to operate correctly when connected to other UART
devices such as the 16550A. The signalling levels are nominal 0V and 3.3V and are inverted with
respect to the signalling on an RS232 cable. The interface is programmable over a variety of bit
rates; no, even or odd parity; stop bit and hardware flow control. The default condition on power-up
is pre-assigned in the external Flash. Two-way hardware flow control is implemented by UART_RTS
and UART_CTS. UART_RTS is an output and is active low. UART_CTS is an input and is active low.
These signals operate according to normal industry convention.
By writing different values to the relevant S register the UART_RI can be continuously polled to detect
incoming communication. The UART_RI signal serves to indicate incoming calls.
UART_DSR is an active low input. It should be connected to DTR output of the host. When the module
is running in high speed mode (See definition for S Reg 507), this pin should be asserted by the host
to ensure connection is maintained. A de-assertion is taken to mean that the connection should be
dropped, or an online command mode is being requested.
The module communicates with the customer application using the following signals:
RS-232
Port /TXD @ application sends data to the module’s UART_RX signal line
Port /RXD @ application receives data from the module’s UART_TX signal line
Serial Module
Application
/RXD
UART_RX
/TXD
UART_CTS
/RTS
UART_RTS
/CTS
UART_DSR
/DTR
UART_DTR
/DSR
UART_RI
/RING
RS232 Interface
UART Interface
UART_TX
Figure 6.1 : UART interfaces
Note that the serial module output is at 3.3V CMOS logic levels. Level conversion must be added to
interface with an RS-232 level compliant interface.
www.ezurio.com
11
Version 1.03 © Ezurio Ltd 2005
6.1.2
SPI bus
The Module is a slave device that uses terminals SPI_MOSI, SPI_MISO, SPI_CLK and SPI_CSB. This
interface is used for program firmware updates at the factory.
Ezurio supply a PC based utility to allow firmware upgrade over the UART port. It is highly
recommended that customers should use this method for updating firmware.
Note: The designer should be aware that no security protection is built into the hardware or firmware
associated with this port, so the terminals should not be permanently connected in a PC application.
6.1.3
GPIO Port
Eight lines of programmable bi-directional input/outputs (I/O) are provided that can be accessed
either via the UART port, or Over The Air (OTA) from a second Bluetooth unit. These can be used as
data inputs or to control external equipment. By using these in OTA mode, a BISM module can be
used for control and data acquisition without the need for any additional host processor.
Each of the GPIO[1:8] ports can be independently configured to be either an Input or Output. A
selection of ports can be accessed synchronously.
GPIO 1 and 2 can be configured as event counters.
The ports are powered from VCC. The mode of these lines can be configured and the lines are
accessed via S Registers 621 to 628.
Low latency I/O can be accessed by using Ezurio’s I/O via an enhanced inquiry process.
6.1.4
PCM CODEC Interface
PCM_OUT, PCM_IN, PCM_CLK and PCM_SYNC carry up to three bi-directional channels of voice data,
each at 8ksamples/s. The format of the PCM samples can be 8-bit A-law, 8-bit μ-law, 13-bit linear or
16-bit linear. The PCM_CLK and PCM_SYNC terminals can be configured as inputs or outputs,
depending on whether the module is the Master or Slave of the PCM interface. Please contact an
Ezurio FAE for further details.
The Module is compatible with the Motorola SSI TM interface and interfaces directly to PCM audio
devices including the following:
6.1.4.1
Compatible Codec Chips
•
Qualcomm MSM 3000 series and MSM 5000 series CDMA baseband devices
•
OKI MSM7705 four channel A-law and μ-law CODEC
•
Motorola MC145481 8-bit A-law and μ-law CODEC
•
Motorola MC145483 13-bit linear CODEC
6.1.5
ADC
The BISM2 provides access to two 8-bit ADCs. These provide an input range of 0mV to 1,800mV,
which can be read using the S registers 701 and 702.
Suitable external scaling and over-voltage protection should be incorporated in your design. The
module provides 5 samples per second at the UART with a baud rate of 115200 or above.
Low latency access of the upper 6 bits of the ADCs can be obtained by using Ezurio’s I/O via an
enhanced inquiry process.
www.ezurio.com
12
Version 1.03 © Ezurio Ltd 2005
6.1.6
LED
A single LED provides information on the status of the module. It is controlled by a S register to
display the status of various parameters and is useful for debug and test.
7. Integrated Firmware
7.1 General
The BISM2 has been designed to provide the fastest route to market for designers who wish to use
Bluetooth to wirelessly enable their products. To achieve this Ezurio has implemented a wide ranging
set of AT commands that control all of the standard Bluetooth tasks. These remove the complexity of
Bluetooth from the design engineer and allow the wireless link to be controlled by means of a simple
set of commands.
For applications where multiple concurrent live connections need to be maintained a variant of
firmware is available which is specifically targeted at multipoint operation.
For both applications a comprehensive range of windows based software and is available to speed up
the design process. A low cost development kit is also available that can be used for prototyping both
cable replacement and multipoint applications.
7.2 Profiles
Bluetooth has been designed to accommodate a very wide range of wireless applications. To enable
these different applications the Bluetooth SIG (Special Interest Group) has defined a series of
different profiles that define the way in which Bluetooth devices communicate with each other and
perform basic functions. These provide a base line of interoperability for specific application
scenarios, upon which more complex user applications can be developed.
There are over 30 different profiles, many of which have been developed for specific applications.
The BISM2 firmware is provided with support for the profiles that are most commonly required for
cable replacement applications.
The current profiles support includes:
•
GAP
Generic Access Profile. The base connection profile upon which others are based.
•
SDP
Service Discovery Profile. The profile to find other Bluetooth devices and the services
they support.
•
SPP
•
DUN
Dial Up Networking.
or VPN connection.
•
Audio Gateway. The base element for Headset and Handsfree profile. A portion of these
profiles must be implemented within the host system.
•
HSP
Headset Profile. Supports early implementations of headsets. Now largely replaced
by the:
•
HFP
Hands-free profile, which provide more control over the headset operation.
•
FTP
File Transfer Profile (full client support).
Serial Port Profile. Emulation of a serial cable for cable replacement applications.
Profile support for connection to an external PSTN, GSM, GPRS
For other profile support, please contact Ezurio Ltd at blu2i@ezurio.com
7.3 AT Overview
The AT command set is well known by engineers and was developed to aid the integration of PSTN
modems. It provides simple high level commands for complex functions that can easily be
incorporated into programs or used within programming scripts.
www.ezurio.com
13
Version 1.03 © Ezurio Ltd 2005
Ezurio has used this familiar concept and extended it to Bluetooth to simplify the integration of
Bluetooth for product designers. Rather than having to understand the many stages of setting up a
Bluetooth connection or function, a single AT command is all that is required.
For example to connect to a Bluetooth device with an address 00809844EA13, all that is needed is to
send the string
ATD00809844EA13
to the UART of the BISM2 module. The module will attempt to make a connection and return connect
00809844ea13,1101) or (NO CARRIER), depending on whether the connection was successful.
The scope of the AT command set developed by Ezurio is such that most Bluetooth functionality can
be covered, greatly reducing development time.
To provide additional functionality a range of “S” registers has been implemented. These allow
program settings to be stored to control the BISM2 function and also give access to configuring and
reading ports and status registers within the BISM2.
Full details of the AT command set are provided in the Blu2i AT Command Reference Manual.
7.3.1
AT features at a glance
7.3.1.1
General
•
Configure two modules to automatically connect and transfer data, audio or a combination of
data and audio when both devices are powered. The peer device does not have to be another
Intelligent Serial Module. It is possible to implement auto connect with a Bluetooth enabled
mobile phone.
•
Automatically re-connect devices when a connection is dropped.
•
Remotely access the AT parser of the remote unit from a master device to perform Over The
Air (OTA) configuration.
•
Configure the module to enter a state on power up and after a period of time change to
another state automatically. This allows units to be placed in the discoverable state for a
limited time period.
•
Read and write to GPIO lines
•
Read the ADC channels
•
Get fast GPIO and ADC status through an inquiry response (patent pending)
7.3.1.2
Audio
•
Set up audio connections
•
Enable / disable Auto Answer for incoming connections
7.3.1.3
UART
•
Change the baud rate from 1200 to 921,600 baud.
•
Use the DSR line to drop connections
•
Flexible configuration as either DTE or DCE
•
Change escape sequence character
•
Change the number of Stop bits and Parity
•
Enable or disable echoes
7.3.1.4
Security
•
Enable Authentication by requiring a PIN code for incoming AND / OR outgoing connections
•
Enable data to be encrypted over the air for incoming AND / OR outgoing connections. The
module can be configured to be:
www.ezurio.com
14
Version 1.03 © Ezurio Ltd 2005
non-connectable and non-discoverable,
non-connectable but discoverable,
connectable but non-discoverable,
connectable and discoverable.
•
Automatically store Paired devices in a trusted device database in the flash memory
7.3.1.5
Bluetooth
•
Set the module to be a master or slave
•
Make a Bluetooth connection to a specified device
•
Perform a full inquiry for other Bluetooth devices
•
Query a remote device to check if a service is offered
•
Fetch the friendly name of a remote device
•
Increase or decrease the delay before the master abandons a connection attempt
•
Change the device class code
•
Set the device’s friendly name
•
Change the Inquiry scan time
•
Change number of returned devices from an inquiry scan
•
Obtain the RSSI value for a connection
7.3.1.6
Power Management
•
Decrease or increase the output power to suit your connection range
•
Configure the modules to work in Sniff and other low power modes.
7.4 Multipoint Firmware
For multipoint operation, the same hardware can be loaded with multipoint software. Whereas the
firmware for single point ‘AT’ communication only allows one connection to be active at any one time,
using multipoint firmware allows a number of simultaneous connections to be made and maintained.
It also allows connections to multiple profiles to one or more devices. Multipoint firmware should be
seen as a concept of channels instead of slave connections.
When operating in Bluetooth multipoint mode, the resources and bandwidth of a Bluetooth master
device are shared amongst the different connected devices. This has an impact on the maximum
throughput to any one device. If multiple device connections are maintained it also impacts on the
memory resources and device database within the Bluetooth stack. Designers should be aware of
these restrictions when using multipoint configurations. In most cases better latency and power
consumption can be achieved by polling or fast data transfer rather than by maintaining concurrent
connections.
In general, multipoint connections are viable for up to three connections, but other connection
schemes become appropriate if a greater number of devices are being deployed.
7.5 OTA (Over the Air) Configuration
When the BISM2 has its remote AT parser enabled, its settings can be remotely controlled by a
master unit (see register S536). This places the slave unit’s AT parser in remote mode providing
over the air configuration. This mode is of use for remote sensor applications, where no host
processor is required to control the slave Bluetooth unit.
www.ezurio.com
15
Version 1.03 © Ezurio Ltd 2005
7.6 Boot modes
The module has the capability of booting into 1 of 7 modes.
Boot Mode 1 is default and gives functionality equivalent to the BISM1 module.
These modes will specify different PSKEY settings to allow for different basic operation. Please
contact Ezurio for further information.
8. Low Power Modes
The current drain from the Vcc power input line is dependent on various factors. The three most
significant factors are the voltage level at Vcc, UART baud rate and the operating mode.
The hardware specification for the blu2i module allows for a voltage range of 3.6 to 7.0v at Vcc. Tests
have shown that there is no significant difference in current draw when Vcc is 5 or 6V. Therefore the
data presented below, pertains to Vcc levels of 3.6 and 5v only. Tests have shown that where power
drain is an issue, it is best to keep Vcc at the lower end of the range.
The UART baud rate has a bearing on power drain because as is normal for digital electronics, the
power requirements increase linearly with increasing clocking frequencies. Hence higher baud rates
result in a higher current drain.
Finally with regards to operating mode the significant modes are; idle, waiting for a connection,
inquiring, initiating a connection and connected. With connected mode, it is also relevant to
differentiate between no data being transferred and when data is being transferred at the maximum
rate possible.
The operating mode can best be described by stating the AT commands required to enter that mode.
In addition, there are certain S Registers which have a direct impact on power consumption, which
are described next.
The blu2i Module has a single LED which can be configured to display connection status. Tests have
shown that this LED can consume up to 5.3mA which is more than double the current draw when in
Idle mode. S Register 534 can be used to completely disable this indicator.
S Registers 508 to 511, which specify the page and inquiry scan intervals and windows, can be used
to adjust the average current drain when in discoverable and or connectable modes. Registers 508
and 509 specify the interval and window for page scans and registers 510 and 511 specify the
interval and window for inquiry scans. Register pairs 508/509 and 510/511 describe duty cycles when
the blu2i module goes into scan modes. It is while scanning that the highest current draw occurs. The
average current draw is determined by simple arithmetic using the values stored in the 508/509 and
510/511 register pairs.
Typical current consumption is given in Section 4.1.
The current drain while waiting for a connection or discoverable mode is about 30 times higher than
in idle mode. This is when the page/inquiry scan duty cycle is 100%. These modes give the quickest
response to a page or inquiry request from a remote peer.
It is possible to reduce the duty cycle down to as low as 0.5% at the expense of response time. The
response time can be specified via S Registers 508 and 510 for page and inquiry respectively, where
the worst case response time can be as high as 2.5 seconds. Then the duty cycle can be varied by
changing the value of S Registers 509 and 511 appropriately.
For example, if S Register 508 and 510 are both set to 1000ms and S Register 509 and 511 are both
set to 11ms then the duty cycle is reduced to 1%, this means that average current drain at 5.0v will
be 2% of 65mA plus the normal idle mode current, that is, it is as low as 2.75mA. However, in this
case, it can take up to 1 second to establish a connection.
The connected state current consumption while a master or slave can be considerably reduced by
enabling Sniff mode, described in detail in the next section.
www.ezurio.com
16
Version 1.03 © Ezurio Ltd 2005
mA
Current per LED (when fitted)
3.6V
3.20
5.0V
5.30
8.1 Low Power Modes using Sniff
Bluetooth connections are master/slave in nature. A master sends packets and a slave has to
acknowledge that packet in the next timeslot. Timeslots in Bluetooth are 625 microseconds wide. This
implies that a master will always know when packets will be sent and received, which further means
it is able to optimise power usage by switching on power hungry circuitry only when needed.
A slave on the other hand does NOT have prior knowledge of when a packet will be received and has
to assume that a packet will be received from a master on every receive slot. This means that it has
to leave its receiving circuitry on for most of the receive slot duration. The result of this is high power
consumption as illustrated in the power table in Section 4.1, where a slave with no data transmission
still consumes around 31mA whereas a master consumes only 6mA.
This problem was identified very early in the evolution of Bluetooth (especially since headsets spend
all their time as a slave in a Bluetooth connection) and it was solved by having a mode called Sniff,
with appropriate lower layer negotiating protocol.
Sniff mode during connection is basically an agreement between the slave and its master that data
packets will only be exchanged for N timeslots every M slots. The slave can then assume that it will
never be contacted during N-M slots, and so can switch its power hungry circuitry off. The
specification goes further by also specifying a third parameter called ‘timeout’ (T) which specifies
‘extra’ timeslots that the slave will agree to listen for after receiving a valid data packet. Put another
way, if a data packet is received by the slave, then it knows that it MUST carry on listening for at
least T more slots. If within that T slot time period another data packet is received, then the timer is
restarted. This mechanism ensures low power consumption when there is no data transfer – at the
expense of latency. When there is a lot of data to be transferred, it acts as if sniff mode were not
enabled.
It is stated above that during sniff mode, a slave listens for N slots every M slots. The Bluetooth
specification states that a master can have up to 7 slaves attached to it with all slaves having
requested varying sniff parameters. It may therefore be impossible to guarantee that each slave gets
the M parameter it requested. In light of this, the protocol for enabling sniff mode specifies that a
requesting peer specify the M parameter as a minimum and maximum value. This will allow the
master to interleave the sniff modes for all slaves attached.
For this reason, the sniff parameters are specified in the BISM2 module via four S registers. S
Register 561 is used to specify ‘N’, S Register 562 is used to specify ‘T’ and S Registers 563/564 are
used to specify minimum ‘M’ and maximum ‘M’ respectively. Although the specification defines these
parameters in terms of timeslots, the S register values have to be specified in units of milliseconds
and the firmware does the necessary translation to timeslots.
Low Power Consumption
T Slots
T Slots
Data Exchange
Data Exchange
Data
Data Exchange
Exhange
Data Exchange
Data Exchange
High Power Consumption
T Slots
T Slots
N Slots
T Slots
N Slots
M Slots (Negotiated)
www.ezurio.com
N Slots
M Slots (Negotiated)
17
Version 1.03 © Ezurio Ltd 2005
9. Application Examples
9.1 RS232 Modem Signals
Just as a telephony modem has control and status lines, the blu2i Module also provides for 6 control
and status lines as per the table below. The direction column is as seen from the module’s viewpoint.
Direction
Function
IN or OUT *
CI also known as RI (Ring Indicate)
IN or OUT *
DCD (Data Carrier Detect)
IN
DSR (Data Set ready)
OUT
DTR (Data Terminal Ready)
IN
CTS (Clear to Send)
OUT
RTS (Request to Send)
* configurable with S register 552
The first four lines are under program control. These use four of the GPIO pins and are mapped to
I/O as per the table below. The last two are under control of the UART driver and their functionality is
always enabled.
Direction
Connector Pin Label
Function
IN/OUT
GPIO1
General Purpose I/O
IN/OUT
GPIO2
General Purpose I/O
IN/OUT
UART_RI
Input/Output from module
IN/OUT
UART_DCD
Input/Output from module
IN
UART_DSR
Input to Module
IN/OUT
GPIO3/UART_DTR
General Purpose I/O (or DTR functionality)
IN/OUT
GPIO4/LED
General Purpose I/O (LED)
IN/OUT
GPIO5
General Purpose I/O
IN/OUT
GPIO6
General Purpose I/O
IN/OUT
GPIO7
General Purpose I/O
IN/OUT
GPIO8
General Purpose I/O
Notes:
1.
PIO4 (DSR) is used by the blu2i module to sense that the host is connected, and is intricately
linked with connections. For outgoing calls, if this line is not asserted then an error is indicated.
Similarly for AT+BTP and AT+BTG.
While in a call, for appropriate modes, a de-assertion means fall into command state. If the deassertion exists for longer than the period specified in S Register 519 then the connection is dropped
as if an ATH command was received.
2.
PIO2 (RI), is normally de-asserted. When an incoming connection is detected it will be
asserted, until the connection is either answered or rejected using ATA and ATH respectively. See S
Registers 552 & 553 for more details
www.ezurio.com
18
Version 1.03 © Ezurio Ltd 2005
3.
PIO3 (DCD) will be de-asserted when the device is in the unconnected state. Asserted when a
connection is active. See S Registers 552 and 553 for more details.
4.
PIO5 is either used as GPIO or driven as UART_DTR. When the unit is configured in pure host
mode, this pin is forced into UART_DTR and is asserted when there is a Bluetooth connection.
GPIO Pins 1 to 8 are available for general purpose use.
9.2 Modem signalling over Bluetooth
The RFCOMM protocol used in Bluetooth for implementing the serial port profile allows for the
exchange of four modem signals. This information is contained in a special transparent message
which contains bits identified as RTR, RTC, DV and IC which depending on the type of serial device
being emulated maps to DTR or DSR, RTS, DCD and RI respectively. In addition, this message also
includes the ability to convey a BREAK input from one end to the other.
To allow for the greatest flexibility and variability in how the modem control signals are used out in
the real world, S Registers 551, 552 and 553 have been provided which allow for any of RTR,RTC,DV
and IC to be mapped to any modem control/status line.
BREAK signal on RX line
If the host sends a break signal of duration greater than 100ms, then the blu2i module is
configured to treat that as a signal to perform a hardware reset.
This being the case it is not possible to convey a BREAK over Bluetooth to the peer device.
Reset
The module can be reset by the host without the need of any I/O using a BREAK signal. The
module has been configured to reset when the RX line detects a break condition for durations
greater than 100 milliseconds.
The Reset line has a fixed pull down resistor of 10kOhm
9.3 Pure Cable Replacement Mode
The module has the capability of being preset into a pure 5-wire data cable replacement mode. The 5
wires being RX, TX, CTS, RTS and GND. This mode requires no changes to a host application since
the Bluetooth connection is automatically set up on power up. If the connection is lost the BISM2
module will constantly retry until the connection is reinstated.
By implication, two devices are needed to replace a cable. One device is pre-configured to always be
a master and the other, a slave.
Assuming the Bluetooth address of the master to be  and that of the slave to be
, the master module is configured by sending it the following AT commands:
AT&F*
ATS512=1
ATS504=1
ATS507=2
ATS530=2000
AT&W
AT+BTR
The ATS507=2 setting puts the device in DSR drop mode only. This means that when the device
needs to be reconfigured, deasserting the DSR line will ensure that the module responds quickly to AT
commands. This further means that in stand alone mode, the DSR input line MUST be asserted e.g.
0V in TTL signal mode.
www.ezurio.com
19
Version 1.03 © Ezurio Ltd 2005
The slave is configured by:
AT&F*
ATS512=4
ATS0=-1
AT&W
AT+BTR
Where  is optional. If it is not specified, then the slave unit will accept connections from
any device. If specified then only connections from the device specified will be accepted.
If it is desired that the slave unit should not be discoverable (the master is by default not
discoverable), then the configuration commands are:
AT&F*
ATS512=3
ATS0=-1
AT&W
AT+BTR
Where  is optional. If it is not specified, then the slave unit will accept connections from
any device. If specified then only connections from the device specified will be accepted.
When the units are next power cycled, the slave unit will wait for the master to connect to it and the
master will continually look for the slave. If a connection attempt fails, the master will wait for 2
seconds before reattempting a connection. This 2 second delay can be varied by issuing it an ATS530
command with an appropriate value in the range 100ms to 15000ms.
IMPORTANT NOTE: The DSR input to the module MUST be asserted for the auto connection to
succeed. When operating at TTL levels a 0V is seen as an assert state. When operating at RS232
levels and voltage greater than 3V is seen as assert. It is usual to connect the DTR line of the host to
the DSR line of this device.
9.4 Audio Cable (voice)
With a pair of these modules it is possible to replace a mono audio cable with two way traffic. That is,
a setup where a microphone is connected to a speaker at the remote end and vice versa. So this
mode effectively replaces two audio cables.
Assuming the Bluetooth address of the master to be  and that of the slave to be
, the master module is configured by sending it the following AT commands:
AT&F*
ATS512=1
ATS504=1
ATS530=2000
ATS532=7
AT&W
AT+BTR
And the slave is configured by:
AT&F*
ATS512=4
ATS0=-1
AT&W
AT+BTR
www.ezurio.com
20
Version 1.03 © Ezurio Ltd 2005
9.5 Modem Control and Status Signals
A serial port has DTR, DSR, RTS, CTS, DCD and RI control lines. RTS and CTS are locally controlled to
prevent local buffer overflow.
The status of DTR, DRS, DCD and RI can be exchanged with the remote peer device. If for example,
the DTR/DSR lines are to be exchanged between the two peers to simulate the performance of a
physical cable, then it is possible to do so. Refer to the description for S Registers 551, 552 and 553
for more details.
Some serial implementations link CTS and RTS to remove the need for handshaking. Ezurio do not
recommend linking CTS and RTS other than for testing and prototyping. If these pins are linked and
the host sends data at the point that the Bluetooth Serial Module deasserts its RTS signal, then there
is a significant risk that internal receive buffers will overflow which could lead to an internal processor
crash. This will lead to a drop in connection and may require a power cycle to reset the module.
Ezurio recommend that the correct CTS/RTS handshaking protocol be adhered to for proper
operation.
9.6 Oscillator Output
The output from the high performance crystal oscillator (+ 10ppm) can be divided and output on one
of the selected PIO lines, removing the need for a crystal on the customer’s main pcb. The
frequencies available are:
•
8 MHz
•
16 MHz
•
24 MHz
•
48 MHz
For more implementation details, please contact Ezurio’s FAE team.
www.ezurio.com
21
Version 1.03 © Ezurio Ltd 2005
10. Application Information
10.1
Antenna Position
The antenna used on the BISM2 Bluetooth module is designed to be largely immune from the effects
of proximity detuning. Normally, antennas operating at 2.4GHz are affected by their surroundings, so
that great care is needed in their placement and orientation.
The BISM2 can be used in most locations and orientations and is only marginally affected by the
presence of a significant ground plane in close proximity.
The antenna distribution is close to isotropic, which means that the orientation of mounting has only
a limited effect on the overall range. However the optimum range is achieved when the two
antennae are directly facing each other
The module should not be located in a sealed metal enclosure, as this will act as a Faraday cage and
prevent the radio signal from penetrating.
10.2
Power Supply Considerations
The power supply for the Module has to be a single voltage source of Vcc within the range of 3.6 V to
7.0 V. It must be able to provide sufficient current in a transmit burst. This can rise to 65mA.
The Module includes regulators to provide local 3.3V. This rail is accessible on connector J2 for
monitoring purposes only. Under no circumstances should this pin be used to source current.
Power (Vcc) can be provided via the board-to-board connector Pin 29 on J2.
10.3
Power-On-Reset (Power Cycling and Brown Out
considerations).
The Module is provided with an active high reset pin (Hirose 40way DF12C connector pin 13). Upon
the application of power, the Power On Reset circuit built into the Module will ensure that the unit
starts correctly. There is no need for an external power reset monitor.
Note: The previous version of the Bluetooth Serial Module required an external Brown Out circuit to
ensure correct operation. This circuitry has now been incorporated into the module. The power
supply has been designed to work with previous versions of customer circuitry that may or may not
have external brown-out implementations. Customers migrating from a BISM1 to BISM2 module may
be able to simplify their power supply circuitry as a result..
10.4
RF Shield
To meet FCC requirements, all modules are supplied with a soldered RF shield. This meets the
requirement that users may not be able to access RF circuitry without special tools. Removal of the
shield may negate RF approvals.
10.5
Mounting the Module onto the application platform
There are many ways to properly install the Module in the host device. An efficient approach is to
mount the PCB to a frame, plate, rack or chassis. Fasteners can be M1.8 or M2 screws plus suitable
washers, circuit board spacers, or customized screws, clamps, or brackets in 2.2mm diameter holes.
Note that care should be taken to ensure the head of the fixing does not interfere with the circuit.
Nylon fixings are recommended. In addition, the board-to-board connection can also be utilized to
achieve better support.
The antenna (Brown square component on top side of PCB) must not be influenced by any other
PCBs, components or by the housing of the host device. The proximity of the antenna to large
metallic objects can affect the range and performance of the system. Designers should carefully
consider the location of the Module and the type of enclosure material that is used.
www.ezurio.com
22
Version 1.03 © Ezurio Ltd 2005
To prevent mechanical damage, be careful not to force, bend or twist the Module. Be sure it is
positioned flat against the host device.
10.5.1
Fixing Pillars
Ezurio in conjunction with Richco has designed a mounting pillar for use with the Bluetooth Serial
Module. This allows the module to be securely held to a primary pcb using snap fit details. A variety
of different heights are available to accommodate different variants of Hirose stacked connectors.
Pillars supporting a 3.5mm stacked board height can be supplied by Ezurio. These and alternative
spacings can also be ordered directly from Richco.
Customer designs using these pillars should use 2.5mm diameter holes on a 1.6mm thick PCB. in
conjunction with the 3.6 mm stacked height Hirose if they are to take advantage of this.
Board Spacing
Part number
3.6 mm
NPR2005-153-3.6
Ezurio / Richco
CL537-0032-4-**
4.1 mm
NPR2005-153-4.1
Richco
CL537-0057-5-**
5.1 mm
NPR2005-153-5.1
Richco
CL537-0157-0-**
www.ezurio.com
Source
23
Matching HRS PCB
Socket
Version 1.03 © Ezurio Ltd 2005
11. Board to Board Connector
This chapter provides specifications for the 40-pin board-to-board connector which serves as physical
interface to the host application. The receptacle assembled on the Module is Hirose type DF12C.
Details are available at: http://www.hirose.co.jp/cat2002e/500/e53700036.pdf
11.1
Stacking Height
Mating headers from Hirose are available in different stacking heights, allowing the spacing between
the BISM2 and carrier pcb to be changed from 3.5mm to 5.0mm.
Item
Part number
Stacking height
HRS number
Receptacle on
Module
DF12C-40DS-0.5V(81)
3.5 mm – 5 mm
CL537-0007-7-
Headers DF12 series
DF12(3.5)-40DP-0.5V(81)
3.5 mm
CL537-0032-4-**
DF12(4.0)-40DP-0.5V(81)
4.0 mm
CL537-0057-5-**
DF12(5.0)-40DP-0.5V(81)
5.0 mm
CL537-0157-0-**
Notes: The headers listed above are without boss and metal fitting.
11.2
Hirose Connector general specification
Parameter
Specification (40 pin Board to Board connector)
Number of Contacts
40
Quantity delivered
2000 Connectors per Tape & Reel
Voltage
50V
Current Rating
0.5A max per contact
Resistance
0.05 Ohm per contact
Dielectric Withstanding Voltage
500V RMS min
Operating Temperature
www.ezurio.com
-45°C...+125°C
24
Version 1.03 © Ezurio Ltd 2005
Contact Material
phosphor bronze (surface: gold plated)
Insulator
Material PA , beige natural
Stacking height
3.0 mm ; 3.5 mm ; 4.0 mm ; 5.0 mm
Insertion force
21.8N
Withdrawal force 1st
10N
Withdrawal force 50th
10N
Maximum connection cycles
50
12. Qualification
12.1
Bluetooth Qualification Process
The following safety precautions must be observed during all phases of the operation, usage, service
or repair of any application incorporating this Module. Manufacturers of the RF equipment are advised
to convey the following safety information to users and operating personnel and to incorporate these
guidelines into all manuals supplied with the product. Failure to comply with these precautions
violates safety standards of design, manufacture and intended use of the product. Ezurio assumes no
liability for customer failure to comply with these precautions.
12.2
Safety Information:
Switch off the Bluetooth device before boarding an aircraft. Make sure it cannot be switched on
inadvertently. The operation of wireless appliances in an aircraft is forbidden by many airlines to
prevent interference with communications systems. Applications that could result in use on aircraft
should carry appropriate warnings.
12.3
12.3.1
Qualifications
RF approvals
The Module is listed as a Bluetooth Product in terms of the Bluetooth SIG Program Reference
Document (PRD). This means that it can be integrated into end products without further testing or
approval listing. The manufacturer must state the Ezurio part number and product reference in his
literature in order to meet the requirements of the Bluetooth and regulatory approvals.
A list of the countries where the Module is approved will be provided by Ezurio as required. As a
minimum the product is listed in Europe, Scandinavia and USA. Ezurio assumes no liability for
customer failure to comply with national RF approvals.
12.3.1.1
Radio.
R&TTE EN 300 328-2 V1.1.1 (2000-07)
EN 301 489-1 V1.3.1 (2001-09)
12.3.1.2
EMC Emissions.
FCC15B Class B
EN55022 Class B
12.3.1.3
EMC Immunity.
EN55024 Class
www.ezurio.com
25
Version 1.03 © Ezurio Ltd 2005
12.3.1.4
Environmental.
EN301 489-1 V1.3.1 (2001-09)
12.3.1.5
Medical
EN60601-1-2
12.3.1.6
Automotive
Emission test to 95/54/EC
www.ezurio.com
26
Version 1.03 © Ezurio Ltd 2005
12.4
12.4.1
Safety and Regulatory Statements
Europe – EU Declaration of Conformity
DECLARATION OF CONFORMITY
In accordance with Annex IV of the EU directive 1999/5/EC
Notified Body consulted:
Phoenix Test-Lab
ID-Number of Notified Body:
0700
declare under our responsibility that the blu2i Module
complies with the appropriate essential requirements of the Article 3 of
the R&TTE and the other relevant provisions, when used for its intended
purpose.
Health and Safety requirements contained in Article 3 (1) a)
EN 60 950: 1992 Safety of information technology equipment +
Amendment A1:1993, Amendment A2:1993, Amendment A3:1995,
Amendment A4:1997, Amendment A11:1997
EN 50371: Generic standard to demonstrate the compliance of lowpower electronic and electrical apparatus with the basic restrictions
related to human exposure to electromagnetic fields (10 MHz - 300 GHz)
– General public
Protection requirements with respect to electromagnetic compatibility
Art.3 (1) b)
EN 301489-17 V1.1.1 (09-2000), Electromagnetic Compatibility and
radio spectrum Matters (ERM); Electro Magnetic Compatibility (EMC)
standard for radio equipment and services; Part 17: Specific conditions
for wideband data HiperLAN equipment
Means of the efficient use of the radio frequency spectrum
EN 300328-2 V1.2.1 (11-2001), Radio Equipment and Systems (RES);
Wideband transmission systems; Technical characteristics and test
conditions for data transmission equipment operating in the 2,4 GHz ISM
band and using spread spectrum modulation techniques. Part 2:
Harmonized EN covering essential requirements under article 3(2) of the
R&TTE directive.
Ezurio Ltd
tel: +44 (0)20 8938 1000
Unit 2, 126 Colindale Avenue, Colindale
fax: +44 (0)20 8905 8608
Registered in England
London NW9 5HD, United Kingdom
www.ezurio.com
No. 5178293
www.ezurio.com
27
Version 1.03 © Ezurio Ltd 2005
12.4.2
FCC and Industry Canada Statements
This device complies with part 15 of the FCC Rules. Operation is subject to the following two
conditions: (1) This device may not cause harmful interference, and (2) this device must accept any
interference received, including interference that may cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance could void
the user's authority to operate the equipment.
12.4.2.1
FCC Labelling requirement
If the FCC ID is not visible when the module is installed inside another device, then the outside of the
device into which the module is installed must also display a label referring to the enclosed module.
This exterior label can use wording such as the following: “Contains Transmitter Module FCC ID:
PI401B” or “Contains FCC ID: PI401B.” Any similar wording that expresses the same meaning may be
used.
13. Environmental
13.1
Operating temperatures
Parameter
Min
Typ
Max
Unit
Operating temp (standard product)
-40
25
+85
°C
13.2
Storage temperature
Parameter
Min
Max
Unit
Storage temp
-40
+125
°C
13.3
Reliability
Parameter
Test
Comment
Thermal Shock
200 cycles -40ºC /+85ºC 30 min
1 cycle/hour
Vibration
Continuous operation at 60 Hz,
2mm stroke
15g max sine wave, 12 hours
Shock
50G 11ms Half Sine Wave
6 axis x 3 cycles each axis
Moisture Resistance
High Temp Storage
85ºC, 360 hours
Low Temp Storage
-40ºC, 240 hours
High Temp/Humidity
Operation
60ºC, 90%RH, 360 hours
Thermal shock
-40 to 60ºC in 30min
Electro Static Discharge
EN55024:1998 & IEC61000-4-3
Drop Test
75cm to concrete, 3 axis x 2
cycles per corner
www.ezurio.com
200 cycles with continuous
operation
28
Version 1.03 © Ezurio Ltd 2005
14. Physical Dimensions
14.1
14.1.1
Mechanical Dimensions
Standard Module
Location of Connector
(Top View)
All dimensions in mm
www.ezurio.com
29
Version 1.03 © Ezurio Ltd 2005
14.2
BISM1 Compatible Module (special order)
The BISM1 Compatible format version of the BISM2 Bluetooth Serial Module, preserves all of
the mechanical mounting detail and dimensions of the earlier module design.
This is a special order module for customers who are currently in production with the BISM1,
but want to migrate to the additional features of the BISM2. It is not recommended for new
designs.
TOP VIEW
SIDE VIEW
All dimensions in mm.
14.3
Labelling
The label contains the Part number and the unique Bluetooth address of the module.
www.ezurio.com
30
Version 1.03 © Ezurio Ltd 2005
14.4
Ordering Information
The BISM2 is available with different variants of production firmware. Ordering information is
provided below:
Part Number
Description
Firmware Version
TRBLU23-00200
BISM2 with integrated ceramic antenna and
standard AT firmware
Version 4.9.0
TRBLU23-002MP
BISM2 with integrated ceramic antenna and
standard Multipoint firmware
Version 1.4.5.0
TRBLU23-002HC
BISM2 with integrated ceramic antenna and
standard HCI firmware
Version 4.9.0
TRBLU23-00300
BISM2 with SMA jack and standard AT
firmware
Version 4.9.0
TRBLU23-003MP
BISM2 with SMA jack and standard Multipoint
firmware
Version 1.4.5.0
TRBLU23-003HC
BISM2 with SMA jack and standard HCI
firmware
Version 4.9.0
The following parts are available to special order:
Part Number
Description
Firmware Version
TRBLU23-001DN
Elongated format BISM2 with integrated
ceramic antenna and original AT firmware
Version 1.5.0
TRBLU23-00100
Elongated format BISM2 with integrated
ceramic antenna and standard AT firmware
Version 4.9.0
15. Related Documents
•
blu2i AT Command Set Version 2.7.0 Reference Manual
•
blu2i Firmware Release Notes Version 2.7.0
•
blu2i Multipoint Firmware Reference Manual
•
BISM Bluetooth Serial Module - Quick Start Guide
•
BISM Bluetooth Serial Module - FAQ
•
Blu2i Application Scenarios
•
BISM Developer’s Kit User Guide
•
Bluetooth Core 2.0 Specification – www.bluetooth.org
16. Datasheet Revision History
Version
Date
Changes
0.91
10th March 2005
Initial Draft for customer release.
1.0
16th March 2005
First customer release
LED information added
www.ezurio.com
31
Version 1.03 © Ezurio Ltd 2005
Reset Pin note indicating change from BISM1 added.
1.01
4th April 2005
Elongated board options merged into this document.
Pin 27 and 39 defined with new note to clarify that they may only be used for
monitoring voltage.
GPIO Pins 6-8 added in 3.3.2.5
AIO levels defined in 3.3.2.5
Reset threshold defined in 3.3.2.6
USB levels clarified and vdd_usb explained in 3.3.2.6
Ityp corrected for Vcc in 3.3.2.1
Baud rate corrected to 921,600 in 7.3.1.3
Various textual corrections to improve readability.
1.02
19th June 2005
Added Scandinavia listing, which was omitted.
LED information added.
Reset information updated to reflect redesign, giving backwards compatibility to
BISM1. (3.2, 3.3.2.6, 10.4)
CTS/RTS linking risks added in sect 9.5
RF shield notes added (section 1.1 and 10.4)
Richco spacer details added
PIO configuration and default status added in 3.2 notes
Oscillator output feature added in 9.6
Mechanical Drawing updated. 14.1.1
Supply voltage limits corrected to 3.6V – 7.0V
Recommendation to use DFU instead of SPI (sect 6.1)
S register reference extended to 628 (sect 6.1.3)
10kOhm reset pull down resistor defined.
AT&F corrected to AT&F*
N/C pins in BISM1 identified
Multipoint wording updated
Reg 553 added for GPIO3 (sect 3.2)
Caveat on current figures (sect 4.1.1)
Level conversion not added to Fig 6.1
Fast ADC access identified in 6.1.5
FTP defines as full client support (sect 7.2)
Additional features added in 7.3.1.1
Reg 536 references in OTA configuration (sect 7.5)
Boot mode corrected to 7 options instead of 8 (sect 7.6)
LED setup register changed from S533 to S534 (sect 8)
Configuration register added in sect 9.1
GPIO 6-8 added in sect 9.1
ATS532=7 correction from ATS532=1 in sect 9.4
Various textual corrections to improve readability.
1.03
12th July 2005
FCC labelling requirement added.
Pin 39 changed to GPIO
17. Differences from previous modules
The BISM2 has been designed to be a drop in replacement for previous BISM modules from TDK
Systems and Ezurio. However, some additional features have been made. This section lists all of
these changes. More details can be found in the relevant section of the data sheet.
Significant additions have been made to the AT command set.
Pin 27 is now marked as RESERVED instead of VCC_3V3. It can no longer be relied to provide a 3.3v
regulated output.
Pins 33, 35 & 37 are now GPIO instead of N/C. The default state is configured as an inputs.
Pin 39 is now allocated as GPIO9 which defaults as an input line instead of a “VCC_1V8” monitor.
This change has been made to increase the I/O capability and to prevent noise being injected onto
the 1V8 rail.
The module is physically smaller so the fixing holes no longer align with those of the previous
module.
A brown-out circuit is now incorporated on the module. Reset functionality remains the same.
The Oscillator output is now available.
www.ezurio.com
32
Version 1.03 © Ezurio Ltd 2005
18. Disclaimers
EZURIO’S BLUETOOTH PRODUCTS ARE NOT AUTHORISED FOR USE AS CRITICAL COMPONENTS IN
LIFE SUPPORT DEVICES OR SYSTEMS WITHOUT THE EXPRESS WRITTEN APPROVAL OF THE
MANAGING DIRECTOR OF EZURIO LTD.
The definitions used herein are:
a) Life support devices or systems are devices which (1) are intended for surgical implant into the
body, or (2) support or sustain life and whose failure to perform when properly used in accordance
with the instructions for use provided in the labelling can reasonably be expected to result in a
significant injury to the user.
b) A critical component is any component of a life support device or system whose failure to perform
can be reasonably expected to cause the failure of the life support device or system, or to affect its
safety or effectiveness.
Ezurio does not assume responsibility for use of any of the circuitry described, no circuit patent
licenses are implied and Ezurio reserves the right at any time to change without notice said circuitry
and specifications.
18.1
Data Sheet Status
This data sheet contains data from the Preliminary specification. Supplementary data will be
published at a later date. Ezurio Ltd reserve the right to change the specification without notice in
order to improve the design and supply the best possible product.
Please check with Ezurio Ltd for the most recent data before initiating or completing a design.
18.2
Warranty
Ezurio warrants that its products shall conform to Ezurio’s published specifications and remain free
from defects in materials and workmanship under normal, proper and intended use for a period of
two (2) years from date of purchase, provided that proof of purchase be furnished with any returned
equipment.
If during the warranty period any component part of the equipment becomes defective by reason of
material or workmanship, and Ezurio is immediately notified of such defect, Ezurio shall at its option
supply a replacement part or request return of equipment, freight prepaid, to its designated facility
for repair. In the event no trouble is found on products returned for repair, Ezurio reserves the right
to charge the customer its standard published repair charge.
This warranty shall not apply to any products that have been subject to misuse, bending, twisting,
neglect, alteration, improper installation, testing or unauthorized repair performed by anyone other
than a Ezurio designated repair facility. Any non-warranty repairs or maintenance shall be at Ezurio’s
standard rates in effect at the time.
This warranty is in lieu of all other warranties, whether expressed, implied, or statutory, including but
not limited to, implied warranties or merchantability and fitness for a particular purpose. In no event
shall Ezurio be liable, whether in contract, in part, or on any other basis, for any damage sustained
by its customers or any other person arising from or related to loss of use, failure or interruption in
the operation of any products, or delay in maintenance, or for incidental, consequential, in direct, or
special damages or liabilities, or for loss of revenue, loss of business, or other financial loss arising
out of or in connection with the sale, lease, maintenance, use, performance, failure, or interruption of
these products.
www.ezurio.com
33
Version 1.03 © Ezurio Ltd 2005

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Tagged PDF                      : Yes
XMP Toolkit                     : 3.1-701
Producer                        : Acrobat Distiller 7.0 (Windows)
Company                         : TDK Systems Europe
Source Modified                 : D:20050713080601
Creator Tool                    : Acrobat PDFMaker 7.0 for Word
Modify Date                     : 2005:07:13 03:18:10-07:00
Create Date                     : 2005:07:13 03:14:43-07:00
Metadata Date                   : 2005:07:13 03:18:10-07:00
Document ID                     : uuid:5c79f801-530a-4f8d-846b-e0ab927f0365
Instance ID                     : uuid:ef9bfce3-2cdf-42e1-840e-f730bd57b431
Version ID                      : 11
Format                          : application/pdf
Title                           : Hardware Interface Description
Creator                         : Nick Letheren
Description                     : Bluetooth Serial Module
Subject                         : 
Headline                        : Bluetooth Serial Module
Page Count                      : 33
Page Layout                     : OneColumn
Author                          : Nick Letheren

EXIF Metadata provided by EXIF.tools