Smart Technology. Delivered. Enhanced Class 1 Bluetooth v2.1 Module USER’S GUIDE VERSION 0.2 Part # BT740-SA, BT740-SC Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide REVISION HISTORY Revision Revision Date Description Version 0.1 12/0413 Initial release to CA Version -.2 01/05/13 JK updates and DW regulatory Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 2 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Table of Contents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Overview and Key Features .................................................................................................. 4 Specifications ....................................................................................................................... 5 I/O Characteristics ......................................................................................................
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 1 OVERVIEW AND KEY FEATURES ® Every BT740 series Bluetooth module from Laird is designed to add robust, long-range Bluetooth data connectivity to any device. Based on the market-leading Cambridge Silicon Radio (CSR) BC04 chipset, BT740 modules provide exceptionally low power consumption with outstanding Class 1 range via 18 dBm of transmit power. The modules support the latest Bluetooth Version 2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 2 SPECIFICATIONS 2.1 Detailed Specifications Table 2-1: Detailed specifications Categories Wireless Specification Host Interface Profiles Command Interfaces Audio Feature Bluetooth® Frequency Max Transmit Power Implementation V2.1 + EDR 2.402 - 2.480 GHz Class 1 18 dBm from integrated antenna 18 dBm at UFL antenna connector Better than -87 dBm (at 25° C) >1000m Up to 2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Categories Antenna Options Physical Environmental Miscellaneous Development Tools Approvals Feature Internal Implementation Multilayer ceramic - BT740-SA-xx External Connection via u.FL - BT740-SC-xx Dimensions Weight Operating Storage Lead Free Warranty Development Kit Bluetooth® FCC / IC / CE 15.29 mm x 28.71 mm x 2.5 mm 1.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 2.3 Pin Definitions Table 2-2: Pin definitions Pin Signal Description Comment 1 GND 2 SPI_MOSI SPI bus serial I/P See Note 0 3 GPIO6 I/O for host 4 GPIO7 I/O for host 5 RESET Module reset I/P See Note 0 6 SPI_CLK SPI bus clock I/P See Note 0 7 PCM_CLK PCM clock I/P 8 PCM_SYNC PCM sync I/P 9 PCM_IN PCM data I/P 10 PCM_OUT PCM Data O/P 11 VCC_5VIN 3.0 V < VIN < 5.0 V 12 GND 13 VCC_3V3 3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Notes: Unused pins may have internal connections and must not be connected. Note 1: Pins 2, 6, 32, and 33 (SPI related) are only for Laird internal production purposes. Note 2: Pins 34 - 36 are only for uFL connector version of module – BT740-SC Note 3: Power-on-reset (power cycling and brown out consideration) – The reset circuitry within the BT740 module incorporates a brown-out detector; this may simplify power supply design.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide GPIO3 is also used for DTR output (active low). See S Registers 552 and 553. Analogue 0 and 1 should not exceed 1.8 V and are accessible through S Registers 701 and 702. 2.4 Electrical Specifications 2.4.1 Absolute Maximum ratings Absolute maximum ratings for supply voltage and voltages on digital and analogue pins of the module are listed below. WARNING: Exceeding the following values causes permanent damage to the device.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Signal Name UART_RX UART_CTS UART_RTS UART_DSR UART_DTR UART_RI UART_DCD Pin No 22 25 24 16 29 28 17 I/O I I O I O I or O I or O Comments Pin No 2 33 32 6 I/O I O I I Comments I/O I or O I I or O O Comments Shared with GPIO3 Direction may be programmed. Direction may be programmed. 2.4.2.4 SPI Bus Signal Name SPI_MOSI SPI_MISO SPI_CSB SPI_CLK INTERNAL USE ONLY - Used to reprogram Flash in Laird production. 2.4.2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 3 I/O Characteristics 3.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 baud rate, and the operating mode. The hardware specification for the module allows for a voltage range of 3.0 to 5.0 at VCC.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 4 FUNCTIONAL DESCRIPTION The BT740 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 baseband circuitry provides the Bluetooth wireless link and the UART interface provides a connection to the host system.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide BT740 Application - UART_TX /RXD Host UART_RX /TXD UART_CTS /RTS UART_RTS /CTS UART_DSR /DTR UART_DTR /DSR UART_RI UART_DCD Note: /RING /DCD The serial module output is at 3.3 V CMOS logic levels. Level conversion must be added to interface with an RS232 level compliant interface. Some serial implementations link CTS and RTS to remove the need for handshaking.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 4.4 General Purpose I/O and ADC 4.4.1 GPIO Laird provides seven lines of programmable bi-directional input/outputs (I/O) 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 BT730 module can be used for control and data acquisition without the need for any additional host processor.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5 AT COMMAND SET 5.1 Introduction to AT Commands This chapter describes the ‘AT’ protocol used to control and configure the BT740-Sx Bluetooth modules after it is configured to present an ‘AT’ protocol instead of the alternate multipoint packet-based interface. The Multipoint Protocol is also described in this document.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide The claim made for this device is that it has a protocol similar to an AT modem. In fact, the protocol is similar enough so that existing source code written for modems can be used with very little modification with a Laird device. Therefore the following assumptions are made: All commands terminate by the carriage return character 0x0D, represented by the string in subsequent sections. It cannot be changed at runtime.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide A 4 character UUID number consisting of ASCII characters ‘0’ to ‘9’, ‘A’ to ‘F’ and ‘a’ to ‘f’. 5.3.1 Enter Local Command Mode Command: ^^^ Response: OK Description: When in data + connected mode, the host can force the device into a command + connected mode so that AT Commands can issue to the device while a connection establishes. The S2 register specifies the character in this escape sequence, so it can change.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.5 Enable/Disable Echo Command: ATEn Response: OK Or ERROR nn Description: This command enables or disables the echo of characters to the host. The default echo condition sets via S Register 506. This command does not affect the S Register 506. 0 Disable echo. 1 Enable echo. All other values of n generate an error. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Index Description D = Developer ID E = Branch ID F = Build Number (divisible by 10 for production releases and Odd for Engineering) G = Twig Number (will normally be 0, but minor releases on subbranches is non-zero) 4 A 12 digit hexadecimal number corresponding to the Bluetooth address of the Laird device. 6 The maximum size of trusted device database. 9 0 if not in a connect state and 1 if in a connect state.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Index Description A,B,C Where A = UART receive buffer size B = Threshold at which the RTS output line deasserts C = Threhsold at which the RTS output line re-asserts again. 202 The number of times the UART_DSR input line has been detected to toggle since the module was powered or reset via appropriate commands in AT and MP mode.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide as $3E8 5.3.11 Read S Register’s Valid Range Command: ATSn=? Response: For recognised values of n: nnnn..mmmmOK For unrecognised values of n: ERROR nn Description: This returns the valid range of values for register n. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.15 Factory Default (Preserve Protocol Setting) Command: AT&F*AT* Response: OK Or ERROR nn Description: This command erases all user parameters in non-volatile memory except S Register 9255. This means that the trusted device database clears, but ‘AT’ protocol mode retains and UART parameters reset to factory default settings. The new protocol and settings become active after a reset. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.19 Append To Blob(0) Command: AT+BTB+ Response: OK Or ERROR nn Description: This command appends BLOB(0) after the string de-escapes. This allows binary data to load into the BLOB buffer for subsequent processing using the AT+BTBnnnn command syntax. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.21 Remove Trusted Device Command: AT+BTD Response: OK Or ERROR nn Description: This command removes the specified device from the list of trusted devices in the nonvolatile database. If the device is not in the database then the response is still an OK. Error response is for when the address is not a 12 character hex string. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.25 Inquire Command: AT+BTI Response: 12346789012 12345678914 OK Description: This makes the device perform an inquiry for ‘duration’ milliseconds and ‘max’ number of unique responses, where S register 517 specifies ‘duration’ and S register 518 specifies ‘max’. Only the Bluetooth address of responding devices is listed. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide The string length must be in the range 1 to 16, for PIN? otherwise an error returns. The string length must be exactly 6 characters, for PASSKEY? otherwise an error returns and each character MUST be a decimal digit in the range 0 to 9. If there is no ongoing pairing in progress, then the stores in non-volatile memory and may be used in subsequent legacy pairing attempts.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.34 Enable Connectable+Discoverable Mode Command: AT+BTP Response: OK Or ERROR nn Description: Enable page and inquiry scanning and wait for a connection from any device. The page scan window and interval timing derives from S Reg 9009 and 9010. The inquiry scan window and interval timing derives from S Reg 9007 and 9008. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.37 List Trusted Device Command: AT+BTTn? Response: 12346789012 12345678913 12345678914 OK Or ERROR nn Description: This command lists the contents of either the ‘rolling’ or the ‘persist’ trusted device database, where n=0 for the rolling database and 1 for the persist database. The link key does NOT display so the response is as shown below.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.40 Disable Connectable And Discoverable Mode Command: AT+BTX Response: OK Or ERROR nn Description: Disable page/inquiry scanning. This means it does not accept incoming connections or inquiry requests. More specifically it negates the effect of AT+BTQ, AT+BTG and AT+BTP commands. Use ATi21 and ATi22 to determine the discoverable and connectable modes at any time. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.44 HDP: Endpoint Definition In SDP Record Command: AT+HAE,iiii,”endpointname” Response: OK Or ERROR nn Description: This is a Health Device Profile (HDP Agent related command. Refer to Application Examples for details). Please note ERROR 59 implies that the profile has not been activated which means bit 2 in S Reg 9003 is not set AND S Reg 9070 is not 0. It inserts details in the SDP record. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.48 HDP: Write Attribute Value To Agent Command: AT+HAShhhh,aaaa,ssss,ddddd Response: OK Or ERROR nn Description: This is a Health Device Profile (HDP Agent related command. Refer to Application Examples for details). Please note ERROR 59 implies that the profile has not been activated which means bit 2 in S Reg 9003 is not set AND S Reg 9070 is not 0. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.52 HDP: Read Attribute Value (Manager) Command: AT+HMGhhhh,oooo,aaaa Response: OK Or ERROR nn Description: This is a Health Device Profile (HDP Manager related command. Refer to Application Examples for details). Please note ERROR 59 implies that the profile has not been activated which means bit 2 in S Reg 9003 is not set AND S Reg 9070 is not 1. 5.3.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5.3.56 Unsolicited/Async Responses The ‘AT’ Protocol is a command/response type of protocol. This means that the Laird device normally only responds to AT commands and in addition only responds to one AT command at a time. Under special circumstances, unsolicited responses send to the host. They are described in the following subsections. Each unsolicited response is prefixed and postfixed by a cr,lf two character sequence. Command: No Command.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide The parameter is the address of the peer device if available. Command: No Command. This is a status message. Response: RX Description: This response sends to the host when the unit is in online-command mode, S Register 531 is set to 3, and data arrives from a peer. For profiles other than SPP (1101), use S Register 531 as a flag.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 6 S REGISTERS All S registers are accessible when operating in AT protocol mode, but in MP protocol mode the only visible S Registers are listed as ‘Standard’ and ‘Special’. ‘Standard’ and ‘AT’ S Registers share the same numbers in some cases. For this reason, the Standard and Special registers access from AT mode by offsetting 9000. For example, the standard S register 3 for profiles is read by using the command ATS9003? and set using ATS9003=n. 6.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Description 8 (08) 12 2560 GAP Inquiry Scan Window in units of msec 9 (09) 12 2560 GAP Page Scan Interval in units of msec 10 (0A) 12 2560 GAP Page Scan Window in units of msec 11 (0B) 23 4096 SPP RFCOMM frame size for all RFCOMM based profiles. 23-512 range has a granularity of 1; 512 to 4096 range has a granularity of 4. For example: Setting 4095 sets a value of 4092 (round down new values).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Description SPP connections are allowed up to the number specified in this register 36 (24) 0 1 Profiles 37 (25) 0 0xFFF F Profiles USB Vendor ID to use in the DeviceID record 38 (26) 0 0xFFF F Profiles USB Product ID to use in the DeviceID record 39 (27) -2 2 HID Significant if the HID profile enables via Register 3. Negative values imply that HID HOST Profile is registered.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Description HID_SIF_BOOTDEVICE 0x02 HID_SIF_NORMALLYCONNECTABLE 0x04 HID_SIF_RECONNECTINITIATE 0x08 HID_SIF_REMOTEWAKE 0x10 HID_SIF_SDPDISABLE 0x20 HID_SIF_VIRTUALCABLE 0x40 HID_SIF_SUPERVISIONTIMEOUT 0x80 For more details about what these flags do and mean, see the HID profile specification available on the BT SIG website.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Note: If HID functionality is not included in the firmware build, then this register is not available. Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.
Enhanced Class 1 Bluetooth v2.
Enhanced Class 1 Bluetooth v2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Description 7 : UART RI Input (DTE) (Ring Indicate) 8 : UART DCD Input (DTE) 9 : UART DSR Input 10 : UART RI Output (DCE) 11 : UART DCD Output (DCE) 12 : UART DTR Output 13 : UART TX Buffer NOT Empty Output 14 : Input pin – Select Protocol 0=AT,1=MP 15 : Output pin – 0 for AT, 1 for MP For all UART input/outputs (except 13, 14, & 15) there is an implied inversion.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Description 72 (48) 48 1024 HDP HDP Profile related. This is the max TX pdu size and computes to the nearest multiple of 16. Note: If HDP functionality is not included in the firmware build, then this register is not available. 73 (49) 0 2000 0 Sniff Mode / Power Saving Sniff Attempt Time in units of milliseconds. 0 means disable. This value must be less than half the Sniff Minimum Interval (SReg 75).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Description 81 10 80 UART Comms Memory usage in percent for MP mode UART RX processing. Leave to default value. Only change on advice from manufacturer. New values round up to the nearest 10. This register controls how many memory blocks are reserved when the module receives a flood of UART data packets with small payloads.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Dec (Hex) Min Max Category Description class of device is overridden with a value which specifies a HID keyboard device. Note: Most registers read by the firmware at reset. Hence the radio requires a reset after setting a register for it to be effective. This means the relevant S Register set MUST commit to nonvolatile memory before initiating a reset. The S Registers store to non-volatile memory using the command [CMD_STORE_SREG].
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 6.2 Special S Registers (240 to 255) Registers 240 to 255 inclusive are special in the sense that when written, the value automatically commits to non-volatile memory.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 6.3 ‘AT’ S Registers These registers are specific to AT protocol operation only and are not accessible from MP protocol mode. Any S Register marked ‘remapped’ is detailed with the descriptions of the mapped-to S Registers. Table 6-3: 'AT' S registers RegNo Min Max Category Description 0 0 15 SPP Rings before auto answering an incoming SPP connection. Setting 0 means a connection is not auto answered.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Min Max Category Description 520 Remapped UART Comms To S Reg 9240 (240 in MP Mode. See section Standard S Registers). 521 Remapped UART Comms To S Reg 9240 (240 in MP Mode. See section Standard S Registers). 522 Remapped UART Comms To S Reg 9241 (241 in MP Mode. See section Standard S Registers). 523 Remapped UART Comms To S Reg 9242 (242 in MP Mode. See section Standard S Registers).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RegNo Min Max Category Description an 8 bit number on the terminal program. 651 -1 8 GPIO -1 means no GPIO pin allocation. See Note 1 and 3 below. Requires firmware build 185 or newer. 652 -1 8 GPIO -1 means no GPIO pin allocation. See Note 1 and 3 below. Requires firmware build 185 or newer. 653 -1 8 GPIO -1 means no GPIO pin allocation. See Note 1 and 3 below. Requires firmware build 185 or newer.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Note 3: This capability enables the state of between 2 and 4 (depends on the direction of the connection) digital pins to exchange between peers without any host intervention. 7 ERROR CODES 7.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Error 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 Description Both L and R modifier cannot be specified in ATD command Invalid Major Device Class – valid value in range 0x00 to 0x1F inclusive Pairing in progress – Command cannot be actioned – try again later Invalid Sniff parameter specified. E.g. Remote new Attempt value greater than MinInterval.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Error 99 Description Functionality yet to be coded (please report to manufacturer) Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 52 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8 MULTIPOINT PROTOCOL 8.1 Introduction to Multipoint Protocol This chapter describes a packet based messaging interface which a host uses to send commands, receive responses, receive asynchronous events and exchange multiplexed data with the Bluetooth serial module, henceforth described as the module.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.3 Packet Format This section describes the general format of incoming and outgoing packets. The term ‘incoming’ henceforth implies packets sent by the host to the module and ‘outgoing’ in the reverse direction. That is, the direction terminology is module (server) centric. All packets have octet granularity.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide The value of CNF_ID is in the range of 64 to 127 inclusive. Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 55 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Unknown command values result in an EVT_UNKNOWN_COMMAND event, with the command value reflected in the data field. If the octet value is specified in the range 128 to 255 (0x80 to 0xFF), then reflecting that value in the data field of an EVT_UNKNOWN_COMMAND instead of the COMMAND field of a response packet guarantees that the packet is NOT mistakenly processed as an event.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.7.2 Response Packets The format for response packets is displayed in Table 8-3. Table 8-3: Response packet format Octet 0 1 2 3 Field LENGTH CHANNEL CMD_ID FLOW_OUT 4 N..M STATUS DATA[] Description Total length of this packet, including this octet Always zero Echoed from the command packet (Shall be > 0 and < 128) Bit 0 to 6 specify a mask. A clear bit means the host should NOT send any more packets to that corresponding data channel.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.7.4 Data Packets The format for data packets is displayed in Table 8-5. The only method by which the host can stop the module from sending this message is by sending a zero value in the FLOW_IN field of command message, and even that is only for channels 1 to 7 inclusive. Table 8-5: Data packet format Octet 0 1 2..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Channel Number 0xB0 .. 0xB1 0xF0 Profile Comments HDP DATA HDP Data Channels See HDP Data Channels for further details of the logical channel conveyed in these data channel Enhance Inq Response Enhanced Inquiry Response Data Note 1: In MP mode this module can support connections to up to seven other modules. This channel differentiates between the various connections. Note 2: This channel is used for ‘canned’ HID Keyboard Device reports.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.7.6 Host Packet Receive Flowchart As optimal data throughput is the design goal, the format and detail of packets have been constructed appropriately. It is recommended that the host implement the following flowchart, for rapid servicing and flow control of packets.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.8 Host Command/Responses This section describes all host commands and confirms in detail what is specified via the CMD_ID/CNF_ID field of all command and confirm packets. The description for each command/confirm below is in the form of a command or confirm packet table and a corresponding response packet table when appropriate. Each command has a unique CMD_ID value in the range 1 to 63 (0x01 to 0x3F).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Response Packet Offset Field Value Comments 1 CHANNEL 0 2 COMMAND [CMD_NO_OPERATION] 3 FLOW_OUT ?? Runtime value 4 STATUS [OK] Or [INVALID_LICENSE] 8.9.2 Get Connectable, Discoverable, Security Modes This command gets the current connectable, discoverable, and security modes.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Response Packet Offset 7 Note 1: Field Value SECMODE 12..15 Comments 12 = SSP + IO_CAP_NO_INPUT_NO_OUTPUT 13 = SSP + IO_CAP_DISPLAY_YES_NO 14 = SSP + IO_CAP_KEYBOARD_ONLY 15 = SSP + IO_CAP_DISPLAY_ONLY SECMODE is now driven by the Simple Secure Pairing procedure included in and after v.2.1 of the BT specification. Note 2: For SECMODE, the No I/O Capability option is equivalent to the ‘Just Works’ scenario in SSP.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 5..10 BDADDR[] Nap[0,1]:Uap[2]:Lap[3,4,5] Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless Bluetooth address 64 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.9.4 Information This command extracts information from the module, for example version number. Command Packet Offset Field Value Comments 0 LENGTH 5 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_INFORMATION] 3 FLOW_IN ?? 4 INFOTYPE 0..255 Runtime value Response Packet Offset Field Value Comments 0 LENGTH 14 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_INFORMATION] 3 FLOW_OUT ?? 4 STATUS [OK] 5 INFOTYPE 0..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide INFOTYPE = GET_VERSION (0) Offset 7 Field Name Range Comments TWIG number/SDK ID 0..255 B7654321 : Twig number B1 : Laird private use INFOTYPE = GET_MANUFACTURER (1) Offset 0..7 Field Name Range Comments Manufacturer/Stack information E.g. “CSR/CCL” Chip manufacturer, null terminated string INFOTYPE = GET_CHIP_INFO (2) Offset Field Name Range Comments 0..7 Chip Designation E.g.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide INFOTYPE = CCL STACK BRANCH VERSION (241 0xF1) Offset 6..7 Field Name Range Comments Stack Branch Version E.g. 1234 Branch Version of CCL stack INFOTYPE = CCL STACK VENA VERSION (248 0xF8) Offset 6..7 Field Name Range Comments Stack VENA Version E.g. 1234 VENA Version of CCL stack 8.10 Configuration Commands This group of commands configures the module. 8.10.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Response Packet Offset 6..9 Field Value Comments REGVAL[] Register Value REGVAL[0] is the most significant octet. 8.10.2 Write ‘S’ Register This command writes a new value to the S register REGNO. See the S Registers section for a full list of all registers.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Response Packet Offset Field Value Comments 0 LENGTH 5 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_STORE_SREG_] 3 FLOW_OUT ?? 4 STATUS As appropriate Runtime value 8.10.4 Default ‘S’ Registers This command forces all S register values in cache to factory defaults.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Command Packet Offset Field Value Comments 3 FLOW_IN ?? Runtime value 4 ENABLE 0..1, 0xFF 5 ACCEPT Bit mask 0 = Disable, 1=Enable 0xFF Read current mode Bit 0: = Set to auto accept channel setup Bit 1..7: Reserved for future use If bit 0 is set then it overrides SReg Comments 14 otherwise that S Register is Fixed consulted Fixed or incoming connections.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Receipt of the response is not an indication that the connection has established. If the connection is to be accepted, the module sends EVT_INCOMING_CONNECTION when the connection is fully established, as shown in the message sequence chart below.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Response Packet Offset Field Value Comments 0 LENGTH 7 Fixed 1 CHANNEL 0 Fixed 2 COMMAND 3 FLOW_OUT [CMD_ MAKE_CONNECTION] ?? Runtime value 4 STATUS As appropriate 5 HANDLE 0..255 Echoed from the command 6 CHANNEL 1..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Command Packet Offset Field Value Comments EVT_INCOMMING_CONNECTION Response Packet Offset Field Value 0 LENGTH 1 CHANNEL 0 2 COMMAND [CMD_ DROP_CONNECTION] 3 FLOW_OUT ?? 4 STATUS As appropriate 5 HANDLE 0..255 Comments Fixed Fixed Runtime value Echoed from the command If the STATUS field in the response is MPSTATUS_OK, then the request to drop the channel successfully submitted to the lower layers of the stack.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide This command sends DTR, RTS, DCD, and RI states to the peer device and also to specify a BREAK – Future Feature. Command Packet Offset Field Value Comments 0 LENGTH 7 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_ CONTROLMODEMLINES] 3 FLOW_IN ?? Runtime value 4 CHANNEL 1..7 Channel ID of an open channel 5 MODEM Bit Mask Bit 0: DTR state Bit 1: RTS state Bit 2: DCD state Bit 3: RI state Bits 4 ..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Command Packet Offset Field Value Comments 2 COMMAND [CMD_RSSI_LINKQUAL] 3 FLOW_IN ?? Runtime value 4..9 BDADDR[] Nap[0,1]:Uap[2]:Lap[3,4,5] Bluetooth addr Response Packet Offset Field Value Comments 0 LENGTH 1 CHANNEL 0 2 COMMAND [CMD_RSSI_LINKQUAL] 3 FLOW_OUT ?? 4 STATUS As appropriate BDADDR[] Nap[0,1]:Uap[2]:Lap[3,4,5] Bluetooth addr 11 RSSI -128 to 127 RSSI value.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.13 Get Open Channel List This command obtains a list of channel IDs corresponding to connections which are open. It is a good method of querying the module to see how many Bluetooth connections are established and their corresponding channel ID numbers. A host should not need to use this command as it should be keeping track of the following two events and responses: EVT_DISCONNECT, EVT_CONNECTION_SETUP, RSP_MAKE_CONNECTION.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Command Packet Offset Field Value Comments 3 FLOW_IN ?? Runtime value 4 MAXRESP 1..255 Maximum number of responses before aborting the inquiry procedure 5 TIMEOUT 1..120 Time in seconds, before aborting the inquiry procedure. 6 FLAGS 0..1 Bit 0 : 1 Bits 1..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Where:: LL is the total length of the packet, and given only the EE..EE field is of variable length, the length of the EE..EE field is calculated by subtracting 12 (decimal) from LL. F0 is the channel number and is fixed AAAAAAAAAAAA is a 6 byte field containing the Bluetooth address of the responding device. CCCCCC is the device class code of the responding device RR is the measured RSSI value for that response (8 bit signed integer) EE..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 3 FLOW_IN ?? Runtime value 4 MODE 0..1, 0xFF 0 = Disable, 1 = Generic Access Code 0xFF = Read current mode Response Packet Offset Field Value Comments 0 LENGTH 6 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_ DISCOVERABLE_MODE] 3 FLOW_OUT ?? 4 STATUS As appropriate 5 CURMODE 0..1 Runtime value 1 = Generic Access Code The module uses the parameters stored in ‘S’ Registers 7 and 8 to set the inquiry scan interval and window.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide For example: If one end has Display only, but the other end has keyboard only, then the negotiation results in one end displaying a six digit passcode on the Display Only side, which is then required to be entered at the keyboard only end. If both ends have Display with Yes/No, then during the procedure both ends display a six digit passcode which needs to be visually compared and then the Yes/No buttons are used to confirm that they match.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Figure 8-7: Just Works sequence diagram The EVT_SIMPLE_PAIRING displays a success/fail indication. If it fails, then the EVT_LINK_KEY event does not send to the host. 8.15.1.2 Simple Secure Pairing ‘Display Yes/No’ The message sequence diagram for when the device has display and yes/no capability is as follows: Figure 8-8: Display Yes/No capability sequence diagram The first EVT_SIMPLE_PAIRING contains a passcode that needs to be confirmed by the host.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Figure 8-9: Display Only sequence diagram The first EVT_SIMPLE_PAIRING contains the passcode which must be displayed. When the peer confirms the passcode or otherwise, a second EVT_SIMPLE_PAIRING is sent to the host with an appropriate success/fail code. If pairing is successful, EVT_LINK_KEY is sent to the host; if not RSP_PAIR_INITIATE indicates a non-ok status code. 8.15.1.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide In that situation, when a pairing procedure is detected, a pincode request event packet is sent to the host and the host responds with a CMD_PINCODE or CNF_PINCODE command as shown in the message sequence diagram below (Figure 8-11). It responds with CNF_PINCODE if it is in the middle of making a connection and a response for ‘make connection’ is still pending.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Figure 8-13: SSP, Display Yes/No sequence diagram The first EVT_SIMPLE_PAIRING contains a passcode that must be confirmed by the host. To confirm the passcode, the host sends a CNF_SIMPLE_PAIRING packet which echoes the passcode. To reject it, the host uses any non-matching value.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Figure 8-15: SSP, Keyboard Only sequence diagram The first EVT_SIMPLE_PAIRING indicates that a simple pairing procedure started and at that point the host responds with a confirm packet which contains the passcode that was visually obtained from the peer device (or both peers decided to use the same code). When the peer confirms the pairing, a second EVT_SIMPLE_PAIRING is sent to the host with an appropriate success/fail code.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide This informs the module the response to a passcode query. In this case the ‘actionval’ conveys the passcode value. Note: A successful connection to an unpaired 2.1 and newer device requires this confirmation packet because the MP protocol does not process new commands unless the previous command was completed by sending an appropriate response packet.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.15.5 PinCode (Confirmation) This is a confirmation packet which sends a pincode in response to an EVT_PINCODE_REQUEST message while making an outgoing connection to a legacy pairing device and there was a pairing challenge by the peer prior to connection acceptance. This packet, just like the command version of this packet, can also register a pincode for all subsequent incoming legacy pairings from BT2.0 and older devices.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Response Packet Offset Field Value Comments 0 LENGTH 8 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_ TRUSTED_DB_COUNT] 3 FLOW_OUT ?? 4 STATUS As appropriate 5 DBTYPE 0..1 Echoed from command 6 COUNT 0..N Number of trusted devices in this database 7 MAXCOUNT 0..N Maximum number of devices that can be stored in this database Note: Runtime value ROLLING database stores all new pairings automatically.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.15.7 Trusted Database Read Record This command reads the Bluetooth address of the ITEMNO pairing in the database specified, counted from the top. ITEMNO is indexed from one. Command Packet Offset Field Value Comments 0 LENGTH 6 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_TRUSTED_DB_READ] 3 FLOW_IN ?? Runtime value 4 DBTYPE 0..1 0 = ROLLING DATABASE 1 = PERSISTANT DATABASE 5 ITEMNO 1..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Command Packet Offset Field Value Comments 3 FLOW_IN ?? Runtime value 4..9 BDADDR[] Nap[0,1]:Uap[2]:Lap[3,4,5] Bluetooth addr of device to be unpaired Field Value Comments 0 LENGTH 11 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_ TRUSTED_DB_DELETE] 3 FLOW_OUT ?? 4 STATUS As appropriate BDADDR[] Nap[0,1]:Uap[2]:Lap[3,4,5] Response Packet Offset 5..10 Runtime value Bluetooth addr, echoed from the command 8.15.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.15.10 Trusted Database Is Peer Trusted This command checks if a device is trusted. Command Packet Offset Field Value Comments 0 LENGTH 10 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_ TRUSTED_DB_ISTRUSTED] 3 FLOW_IN ?? Runtime value 4..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Command Packet Offset Field Value Comments 10..25 KEY[16] 16 byte Link Key Any random value 26..29 FLAGS[4] 00 00 00 00 For future use and MUST be set to 00000000 Field Value Comments 0 LENGTH 11 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_ TRUSTED_DB_ADD] 3 FLOW_OUT ?? 4 STATUS As appropriate Response Packet Offset Runtime value The STATUS value is MPSTATUS_OK if the device was successfully added to the database.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Response Packet Offset 1. Field Value 2 COMMAND [CMD_SECURITY_MODE] 3 FLOW_OUT ?? 4 STATUS As appropriate 5 SECMODE 12..15 Comments Runtime value Current mode 12 = SSP with no input no output 13 = SSP with yes/no display 14 = SSP with keyboard only 15 = SSP with Display only SECMODE is now driven by the ‘Simple Secure Pairing’ procedure which got included in and after v2.1 of the Bluetooth specification 2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide characters to read Response Packet Offset Field Value Comments 0 LENGTH 8 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_GET_REM_FNAME] 3 FLOW_OUT ?? 4 STATUS As appropriate 5 NAMELEN 0..248 Actual size of the friendly name 6 START N Echoed from the command 7 SENTLEN S Total number of bytes sent Note: Runtime value SENTLEN could be less than MAXBYTES. It can happen if there is no space in the module’s TX buffer to send events.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide This length may still be too big to send to the host in one packet. Therefore the name sends in a similar fashion to ‘get friendly name’ described above. However, in this case, the event EVT_LCL_FNAME gets the name to the host.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Command Packet Offset Field Value Comments 0 LENGTH 37 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_SET_LCL_FNAME] 3 FLOW_IN ?? Runtime value 4 FLAGS 1..2 1 = Write to non-vol store for use on next power up 2 = Make the name visible now 5 NAMELEN 1..30 6..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 4 STATUS As appropriate Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 97 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.16.6 Factory Default This command clears non-volatile memory in the module so that it reverts to factory default state. The FLAGS field is a bit mask which selectively clears various types of non-volatile memory and should be set to FF.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.16.7 Get Digital/Analog I/O This command reads the states of up to 16 digital input lines and optionally requests an analogue input reading. This response packet contains two octets containing the digital input states. If an analogue input reading is requested then the ADC reading is supplied in an EVENT_ADC event.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.16.8 Set Digital I/O This command controls the states of up to 16 digital output lines. Command Packet Offset Field Value Comments 0 LENGTH 6 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_SET_IO_EX] 3 FLOW_IN ?? Runtime value 4 ioId 0 0 = Digital I/o in Module 5..6 mask[2] 0000..FFFF Only set bits are specify which bits in ioVal submit to the digital I/O See Note 1 7..8 ioVal[2] 0000..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide There is no response to this command packet. However, on reset there is at least one EVT_STATUS event so that can be used to detect that the device has rebooted. 8.16.10 BLOB Manage This command manages binary data uploaded from the host through data channels 0x98 to 0x9F (the number of BLOB data channels is compile time dependent). The binary data is referred to as a ‘BLOB’ (binary long object).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide SubCmdId field specifies the actions that the BLOB manager should take on the BLOB specified in field blobID and are described in the following sub sections. Clear :: 0 Use this subcommand to clear the BLOB specified by ‘blobID’, On return ParmA and ParmB are set to zero. Get Size :: 1 Use this subcommand to get the number of bytes in the BLOB specified by ‘blobID’, On return ParmA contains the number and ParmB is set to zero.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide The data block consists of one or more objects, where the first byte of each object specifies the length and the second byte specifies the type of data and the rest of the bytes for that object are the associated data.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide AT Mode Commands AT+HMGhhhh,oooo,aaaa MP Mode Commands D AT+HAShhhh,aaaa,ssss,dddd dd CMD_HDP_ATTRIBUTE_WRIT E AT+HMThhhh,ttttt CMD_HDP_SETTIME AT+HADhhhh CMD_HDP_DISASSOCIATE Comments mode the data value sends in data channel B0 Write an attribute value. In MP mode the data value is taken from data channel B0 Used at manager end to send new date/time to the agent The following table shows the equivalent AT asynchronous responses and MP events.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 0 LENGTH 22 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_HDP_ENDPOINT] 3 FLOW_IN ?? Runtime value 4..5 SpecType[2] As per IEEE spec [4]=msb,[5]=lsb Data Specialization code. For example: 100F (4111 dec) for Weigh Scale 6..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 0 LENGTH 5 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_HDP_SDPPREGISTER] 3 FLOW_OUT ?? 4 STATUS As appropriate Runtime value Internally in the module, the SpecType[2] and Name[15+1] information previously cached in heap memory from CMD_HDPENDPOINT commands transfers into an SDP record and submits to the underlying stack. After this a peer is able to see this device offering HDP services. 8.17.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.17.5 Associate with Manager This command associates an agent with a manager, using the pre-defined object created using the CMD_HDP_BIND command which returns a handle to represent that object. This command is relevant for Agent role only.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Host Agent CMD_HDP_ASSOCIATE(handle) EVT_ASSOCIATED(handle,spec,cfgid,sysid) Successful Association RSP_HDP_ASSOCIATE(OK) Host Agent CMD_HDP_ASSOCIATE(handle) EVT_DISASSOCIATED(handle) Unsuccessful Association RSP_HDP_ASSOCIATE(not OK) Figure 8-17: Associate sequence diagram 8.17.6 Send Fixed Scan Report to Manager This command associates (if not already associated) and sends a fixed scan report from an agent to the bound manager.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Offset Field Value Comments 0 LENGTH 8 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_HDP_SCANREPORT_FIXED] 3 FLOW_OUT ?? 4 STATUS As appropriate HANDLE[2] [4]=msb,[5]=lsb Echoed back from the command HOSTCONTEXT XX This is echoed back from the command 5..6 7 Runtime value The host waits until the response receives before submitting further commands.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.17.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.17.8 Send VAR Scan Report to Manager This command associates (if not already associated) and then sends a VAR scan report from an agent to the bound manager; the binding is specified via the CMD_HDP_BIND command which returns a handle to represent that combination. This command is relevant for Agent role only, and results in an EVT_HDP_SCANREPORT event at the manager end.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide If the agent is already associated, then there is a response as soon as the manager acknowledges that the scan report was received. If association was not successful, because for example the manager is not in range or the Bluetooth device specified in CMD_HDP_BIND does not offer HDP services, then the EVT_DISASSOCIATED sends to the host prior to the response message. This is shown in the message sequence diagram below (Figure 8-19).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.17.9 Message Sequence chart for VAR Scan Report Host Agent DATA CHANNEL[0x98+blobid] {aaaa,bbbb,cccc ....} CMD_HDP_SCANREPORT_VAR(handle,personid,ctx,blobId) data removed from blob data channel EVT_ASSOCIATED(handle,spec,cfgid,sysid) No prior Association and Successful Scan Report RSP_HDP_SCANREPORT_VAR(OK) Host Agent DATA CHANNEL[0x98+blobid] {aaaa,bbbb,cccc ....
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.17.10 Read Attribute Value This command is valid for both agent and manager role and reads the value of the attribute specified via the attribute ID and the qualifier ID. The value returns in HDP data channel 0xB0 formatted as described below. Command Packet Offset Field Value Comments 0 LENGTH 10 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_HDP_ATTRIBUTE_READ] 3 FLOW_IN ?? Runtime value 4..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Since all data is transparently treated in the module, the endienness of DATA[N] should be determined by trial and error with the aid of an HDP manager and finalized to be correct by the time the implementation submits for certification by the Continua Alliance. However, if the attribute data type is a 16 or 32 bit integer/float, then it is little endian. 8.17.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.17.12 Set Date and Time This command is valid for manager role only and updates the date and time in the associated agent identified by the handle. When any HDP manager sends a time update to an agent, it results in an EVT_HDP_UPDATE event to the host of that agent. Command Packet Offset Field Value Comments 0 LENGTH 14 Fixed 1 CHANNEL 0 Fixed 2 COMMAND [CMD_HDP_SET_TIME] 3 FLOW_IN ?? Runtime value 4..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 8.17.13 Disassociate From Manager This command disassociates an agent identified by the handle specified in the command from a manager. This command is relevant for Agent role only.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 9 MODULE EVENTS This section describes all module originated asynchronous events in detail and is specified via the EVT_ID field of all event packets. The description for each event below is in the form of an event packet tables. Each event has a unique EVT_ID value in the range 129 to 255 (0x81 to 0xFF), 0x80 is reserved.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 9.2.2 Status This event asynchronously sends current status to the host. This event is sent to the host after power up to inform the host that the module is ready and operational. You can also obtain the information contained in this message by sending the CMD_GET_MODES command. Event Packet Offset Field Value Comments 0 LENGTH 8 1 CHANNEL 0 2 EVENT [EVT_ STATUS] 3 FLOW_OUT ?? 4 STATUS OK or INVALID_LICENSE 5 DISCMODE 0..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 9.3 Connection Events This group of events are connection related. 9.3.1 Connection Setup This event informs the host that a remote device is requesting a connection. The host responds with a CMD_CONNECTION_SETUP with an accept or reject flag. Event Packet Offset Field Value Comments 0 LENGTH 12 1 CHANNEL 0 2 EVENT [EVT_ CONNECTION_SETUP] 3 FLOW_OUT ?? Runtime value 4..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 1. Channel number allocation is as follows: Profile Channel ID Range Command Parser 0x00 SPP 0x1 .. 0x7 HID DEVICE(Canned) 0x20 HID HOST(Raw) 0x90 .. 0x97 HID DEVICE(Raw) 0xA0 BLOB 0x98 .. 0x9F HDP 0xB0..0xB1 (B1 is continuation channel) Enhanced Inquiry Response 0xF0 9.3.3 Disconnect This event informs the host that a connection was dropped by the remote device.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 9.3.4 Modem Status This event conveys modem status signals originating from the peer device for an SPP connection. Event Packet Offset Field Value Comments 0 LENGTH 6 1 CHANNEL 0 2 EVENT [EVT_ MODEM_STATUS] 3 FLOW_OUT ?? Runtime value 4 CHANNEL 1..7 Channel ID of an open SPP channel 5 MODEMSIG Bit Mask Bit 0: DSR state Bit 1: CTS state Bit 2: DCD state Bit 3: RI state 6 BREAKSIG 0 For future implementation 9.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 9.4.2 Link Key Ex This event sends to the host when CMD_TRUSTED_DB_ISTRUSTED processes, a link key for that peer device exists, and S Register 47 is set to 1. It conveys the link key along with the Bluetooth address to the host. Event Packet Offset Field Value Comments 0 LENGTH 30 1 CHANNEL 0 2 EVENT [EVT_ LINK_KEY_EX] 3 FLOW_OUT ?? Runtime value 4..9 BDADDR[6] Nap[0,1]:Uap[2]:Lap[3,4,5] Bluetooth address of paired device 10..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Event Packet Offset Field Value Comments 3 FLOW_OUT ?? Runtime value 4..9 BDADDR[6] Nap[0,1]:Uap[2]:Lap[3,4,5] Bluetooth address of pairing device 10 action 0..3 See description below actionval 4 bytes See description below 11..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 6..15 NAME[10] Xx xx xx xx Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless The name fragment 125 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 9.4.6 Remote Friendly Name This event sends a fragment of the remote friendly name to the host. The maximum length of the fragment is 10, so at least 25 of these events are required to convey a remote friendly name, if it has the maximum length of 248. Event Packet Offset Field Value 0 LENGTH 16 1 CHANNEL 0 2 EVENT [EVT_REM_FNAME] 3 FLOW_OUT ?? Runtime value 4 INDEX 0..247 Start index into the string 5 LEN 1..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 10 HDP PROFILE RELATED EVENTS 10.1 Associated This event informs the host that an agent associated with the manager and contained the handle, data specialization nominal code, device config ID (as per the IEEE standard) and a unique 8 byte identification number for the agent (or manager). It is relevant for both agent and manager roles.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 10.3 Time Update This event generates for an agent role only and informs the host that the agent received an updated date and time from the manager. Event Packet Offset Field Value 0 LENGTH 11 1 CHANNEL 0 2 EVENT [EVT_HDP_TIMEUPDATE] 3 FLOW_OUT ?? 4 ROLE 00=Agent, 01==Manager HANDLE[2] [5]=msb, [6]=lsb Handle of the agent DATETIME[8] ccyymmddhhssnnxx See Note 1 5..6 11..14 Comments Runtime value 1.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 11.2 Malloc Statistics This event conveys pool malloc statistics to the host and is available in engineering/beta builds only. Event Packet Offset Field Value Comments 0 LENGTH 16 1 CHANNEL 0 2 EVENT [EVT_DEBUG_PACKET] 3 FLOW_OUT ?? Runtime value 4..5 ELSIZE[2] 0..N Pool Element Size 6..7 NUMELS[2] 0..N Number of elements 8..9 TAKEN[2] 0..N Number of elements taken 10..11 MAXTKN[2] 0..N Tide mark for taken 12..
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 12.2 Logical Packet Format The format of the HDP logical packet is as follows: LEN PACKET_TYPE DATA 2 bytes 1 byte N bytes LEN is set to N+3 and big endian, so that the first byte of LEN sent on the wire is the MSB. The DATA field structure depends on the logical packet type specified by PACKET_TYPE and the following subsections describe the types of packets available at the time of writing. 12.2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 12.2.3 Field Type: Object Handle This is the format of the ‘Object Handle’ field type and is always 3 bytes long: 00 Object Handle Always 0x00 2 bytes 12.2.4 Field Type: Attribute Tag/Value This is the format of the ‘Attribute Tag/Value’ field type which is of variable size: 01 ATTR CODE ATTR VALUE LEN ATTR VALUE Always 0x01 2 bytes 2 bytes N bytes The size of this field is ‘ATTR VALUE LEN’ + 5 12.2.4.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 12.2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide { printf("INSUFFICIENT LENGTH -- ABORT display of msg"); break; } pMsg += sprintf(pMsg," A:%d (%04X), ", nAttrId, nAttrId, nAttrLen); { uint16 nBlockLen = (nAttrLen>24) ? 24 : nAttrLen; uint8 *pData = pSrc; while(nBlockLen--) { pMsg += sprintf(pMsg,"%02X",*pData++); } if( nAttrLen > 24 ) { pMsg += sprintf(pMsg,"...
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 13 MULTIPOINT APPLICATION EXAMPLES 13.1 BLOB Manager BLOB stands for ‘Binary Long OBject’. There are many Bluetooth related operations which require large strings to submit to the underlying Bluetooth stack. For example, friendly names and extended inquiry responses fall into this category. These strings can be larger than the data packets allowed by the multipoint protocol defined in this specification.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide See description of the command CMD_BLOB_MANAGE for all the actions possible. 13.2 HID Connections HID (Human Interface Device) was originally described in detail in a specification published by the USB organization. The Bluetooth SIG has built on that idea but uses wireless instead of USB as the transport mechanism.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 13.3 Sending INPUT Reports Once a connection establishes, a report sends by a device end by sending an entire INPUT report in a single data packet with channel ID 0xA0. For example, if the descriptor specifies a standard keyboard and if the ‘a’ key pressed, then the following data sends over the UART to the module: 0A A0 00 00 04 00 00 00 00 00 And to convey that the left shift was pressed, the data is: 0A A0 02 00 04 00 00 00 00 00 13.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide service name from non-volatile memory. This can be done by writing an empty name via the BLOB manager. 13.6.2 HDP Usage Message The module offers both HDP Agent and HDP Manager roles with IEEE Data Specialization functionality. HDP Manager functionality is provided mainly for prototyping and testing an Agent implementation and is not intended for eventual Continua Alliance certification.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 13.6.
Enhanced Class 1 Bluetooth v2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 13.7 Agent UART Traffic for Chart This section shows the UART traffic for a module operating as a HDP Weigh Scale agent communicating with a manager. It is NOT a log of the UART traffic for the message sequence chart illustrated in the previous section. ********************************************** ********************************************** <70 006.896 08 00 81 7F 00 00 00 0C EVT_STATUS //State: RESET_GETADDR >70 000.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide RSP_HDP_BIND (MPSTATUS_OK) >70 026.037 04 00 2F 7F CMD_HDP_SDPREGISTER <70 000.125 05 00 2F 7F 00 RSP_HDP_SDPREGISTER (MPSTATUS_OK) >70 011.918 06 00 31 7F B538 CMD_HDP_ASSOCIATE <70 000.109 05 00 31 7F 00 RSP_HDP_ASSOCIATE (MPSTATUS_OK) <70 002.013 08 00 81 7F 00 00 01 0C EVT_STATUS <70 003.775 13 00 97 7F 00 B538 100F 05DC 4C414952444D4752 EVT_HDP_ASSOCIATED >70 029.235 06 B0 12345678 >70 018.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 13.8 Manager UART Traffic for Chart This section shows the UART traffic for a module operating as a HDP manager communicating with a Weigh Scale agent. ********************************************** ********************************************** ********************************************** <71 003.900 08 00 81 7F 00 00 00 0C EVT_STATUS //State: RESET_GETADDR >71 000.000 04 00 02 7F CMD_READ_BDADDR <71 000.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide // A:2448 (0990), 0000000000000000 // A:2454 (0996), 06C3 >71 043.056 0E 00 37 7F 72B4 140B020C102D214E CMD_HDP_SET_TIME <71 000.109 05 00 37 7F 00 RSP_HDP_SET_TIME (MPSTATUS_OK) <71 008.721 07 00 96 7F 01 72B4 EVT_HDP_DISASSOCIATED <71 002.059 08 00 81 7F 00 01 01 0C EVT_STATUS 13.8.1 Sniff Mode Explained Bluetooth connections are master/slave in nature. A master sends packets and a slave has to acknowledge that packet in the next timeslot.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Figure 13-1: Sniff Mode 13.8.2 UART Host Power Saving Facility There are circumstances where a CPU driving the module consumes a lot of power and some means are necessary to reduce that power consumption while the module is in a Bluetooth connection. To facilitate that, the module has many GPIO pins, and using S Registers 50 to 65, one (and only one) GPIO pin can configure with the value 13 so that it is an output configuration.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Is PIN High? Wait for data to arrive from Module Assert RTS Deassert RTS Configure to wake up when PIN goes high Go to Sleep PIN goes high Wake up and Assert RTS Figure 13-2: CPU power saving strategy 13.8.3 Out of Band (OOB) Pairing When two devices pair using the legacy procedure or the simple secure pairing method, the end result is that they both end up with the same 16 byte random key.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Whatever OOB means are chosen, it implies that some externally generated key has to be added to the trusted device database in the device. The module caters for this link key addition using the CMD_TRUSTED_DB_ADD command when in the multipoint protocol mode and the AT+KY command when in the AT protocol mode. 13.8.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Basically, users must fine tune S Registers 7,8,9,10,11,81 and MP packet sizes to ensure desired throughput operation. Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 147 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 148 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 13.8.5 UART Protocol Selection & Indication Via GPIO S register 255 selects either MP(1) or AT(2) protocol mode for communications over the UART. If S Register 255 is set to zero, then it implies that a GPIO selects the protocol such that zero sets AT mode and one for MP mode. To configure a particular GPIO pin for this functionality, set the appropriate S Reg (in range 50 to 65) to a value of 14.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 13.8.7 The HCOMMAND & EVENT Values The following is a listing of a snapshot of the file BMHOSTPROTOCOL.H at the time of this document’s release. Laird does NOT guarantee that this listing is kept up to date. For development purposes, please request the latest version of the appropriate ‘C’ header file.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide .... //+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ //The following are EVENT (octet 2) values in event packets //+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ #define EVT_STATUS 0x81 #define EVT_INVALID_PKTSIZE 0x82 #define EVT_UNKNOWN_COMMAND 0x83 #define EVT_INQUIRY_RESULT 0x84 #define EVT_MODEM_STATUS 0x85 .... .... .... 13.8.1.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14 AT APPLICATION EXAMPLES 14.1 Connection Management Commands ATD, ATA, ATH, AT+BTP, and AT+BTG are all connection related and are discussed generically in this section. On connection, depending on the value of S Register 531, the module enters data pass through mode (S Reg 531 = 0) or remains in command mode (S Reg 531 > 0).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Where is 100 milliseconds. The four guard time means that even when a file transfer is occurring and it happens to be full of characters, it is not going to drop into command mode. This is because when transferring a file, it happens as fast as possible and so the inter character gap will be significantly shorter than the .
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide In non-canned mode (S Reg 531 > 0) the host has to send the raw 8 byte INPUT reports in the ATX command and conversely any OUTPUT reports from the host send to the host in RX asynchronous responses. Disconnections from the module initiate via DSR deassertion. However, if the module is in non-canned mode (S Register 531 > 0) then it is also possible to initiate a disconnection using the ATH command.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.5 HDP Profile (Health Device Profile) UUID : 1400,1401,1402 14.5.1 Background Health Device Profile (HDP) is available on the module in both Agent and Manager roles as defined by the Continua Alliance (see www.continua.org).
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide data specializations as needed. Once ratified, the end result is always an abstract data model which defines what data is pertinent for that instrument and how it shall be presented to the real world. Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 156 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.5.3 Abstract Data Model From a software engineer’s perspective, an abstract data model for an IEEE data specialization can best be described as a collection of arrays of different types of data (which the specifications refer to as attributes). Each attribute is unambiguously defined to consist of a tag, a type, and the actual value. There is no reliance on any programming language in the definition; it is purely a data model.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.5.4 HDP Agent Model From a software perspective the HDP Agent implementation is as shown in the diagram below.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide The diagram shows that the agent model is the Bluetooth communications stack. The stack consists of an SDP record that exposes to the outside world the data specializations it is capable of, a ‘Laird IEEE/HDP Service Encapsulation’ layer which relays commands and responses to the host, and 0 or more instances of Data Specializations. At the time of the first release of the firmware, only a Weigh Scale specialization is offered.
Enhanced Class 1 Bluetooth v2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide System ID 2436 0 8 System Model – product name 2344 0 12 System Model – model name 2344 1 16 Serial Number 2349 0 8 14.5.6 Thermometer Data Specialization The Thermometer Specialization (nominal code 4104) is embedded in the firmware is shown as below and it contains a MDS and an NU object.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Attribute Tag Data Type Comments MDC_ATTR_UNIT_CODE 2454 OID_TYPE Var:Weight Units MDC_ATTR_TIME_PD_MSMT_ACT IVE 2649 RELATIVE_TIME Var:Time (int32) MDC_ATTR_ATTRIBUTE_VAL_MA P 2645 ATTR_VAL_MAP 2646,2448 MDC_ATTR_TIME_STAMP_ABS 2448 ABSOLUTE_TIME Var:Time MDC_ATTR_NU_VAL_OBS_BASIC 2636 BASIC_NU_OBS_VAL Var:temperature MDC_ATTR_NU_ACCUR_MSMT 2378 FLOAT_TYPE Always: 1 MDC_ATTR_MSMT_STAT 2375 MEASUREMENT_STAT US Var:Meas. Stat.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Serial Number 2349 0 8 Measurement Active Period 2649 0 4 Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 163 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.5.7 Glucometer Data Specialization The Glucometer Specialization (nominal code 4113) embedded in the firmware is shown as below and it contains a MDS and an NU object.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Attribute Tag Data Type Comments MDC_ATTR_TIME_STAMP_ABS 2448 ABSOLUTE_TIME Var:Time MDC_ATTR_NU_VAL_OBS_BASIC 2636 BASIC_NU_OBS_VAL Var:temperature MDC_ATTR_NU_ACCUR_MSMT 2378 FLOAT_TYPE Always: 1 MDC_ATTR_MSMT_STAT 2375 MEASUREMENT_STAT US Var:Meas. Stat.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.6 Agent Related AT Commands This section describes all the commands used to manage the Agent role for HDP. 14.6.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.6.2 Bind a Data Specialization Command: AT+HAB,iiii Response: hhhhOK Or ERROR nn Description: This command binds a data specialization identified by the nominal code ‘iiii’ (for example 4111 = Weigh Scale) with an HDP manager identified by the Bluetooth address ‘’. For this command to be successful, the data specialization identified by ‘iiii’ has to be pre-embedded in the firmware.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Or ERROR nn Description: This command reads (gets) the value of one of the variable attributes identified by ‘aaaa’ and sub ID ‘ssss’ in the attribute collections for that agent identified by the handle ‘hhhh’. For the embedded weigh scale data specialization this command reads the value of an attribute listed in Table 14-1.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide collections for the agent identified by the handle ‘hhhh’. For the embedded weigh scale data specialization, this command writes to an attribute listed in Table 14-1. The value ‘hhhhhhhhh’ is in hexadecimal and is NOT validated in any way apart from the requirement that it shall be twice the size in bytes as specified for that attribute. SReg Required Settings: Bit 2 set in S9003 and S9070=0 14.6.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide SS Seconds (e.g. 2F==47) AA Hundreths of seconds (e.g 63==99) For example, the data and time 12 Feb 2011, 16:45:33.78 sends as 140B020C102D214E 14.6.5 HDP Manager Model From a software perspective the HDP Manager implementation is as shown in the diagram below and the functionality is provided mainly to enable prototyping and regression testing of agent specializations. There are many far more capable HDP Managers available which are hosted on a PC.
Enhanced Class 1 Bluetooth v2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 0 or more instances of Specialization Associations. These ‘Associated Agent Objects’ are transient and come into existence only when an agent successfully associates. The associated process results in the top few attributes in the MDS and NU collections caching in the Manager which the host reads using the AT+HMG command after an association.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide SReg Required Settings: Bit 2 set in S9003 and S9070=1 Command: AT+HMThhhh, ccyymmddhhmmssaa Response: OK Or ERROR nn Description: This command sends the current data and time to the associated agent identified by handle ‘hhhh’. The time ccyymmddhhmmssaa is a 16 character hexadecimal value which is encoded as follows: CC Century (e.g. 14==20) YY Year (e.g. 0B==11) MM Month (e.g. 0C==12) DD Day (e.g 1F==31) HH Hour (e.g.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Description: This response sends to the host when a successful association happens for the agent identified by ‘hhhh’ (16 bit decimal number). For completeness, the data specialization nominal code ‘iiii’ (16 bit decimal) and the device configuration ID ‘cccc’ (16 bit decimal) that got negotiated with the manager, is also provided. The 16 character parameter ‘ssssssss’ specifies the system ID of the agent.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.7.1.
Enhanced Class 1 Bluetooth v2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.7.2 Authentication and Encryption The module and firmware is BT v2.1 compliant so it uses Simple Secure Pairing (SSP) to authenticate devices to trust, and only invokes a legacy pairing procedure when a peer device is v2.0 or older. It is not possible to configure the unit to be only capable of legacy pairing and still have v2.1 approvals. The purpose of pairing, whether legacy or SSP, is to generate the same random 16 byte key at both ends.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide None Display Only Display with a Yes/No button Keyboard only This I/O capability exchanges by the two peers going through a pairing procedure so that the optimal user interaction selects at both ends. For example, if one end admits to keyboard only and the other to Display only, then the two negotiate that the display end shows the passcode with an appropriate prompt to get the user at the other end to type in the passcode.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide As you can see, the host is able to determine if SSP or legacy pairing is in progress because in the former the challenge message is “PASSKEY?” whereas in the latter it is “PIN ?”. In the ‘just works’ scenario the PAIR 0 message informs the host that a pairing is complete. 14.7.4.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide As a result, it is possible to convey the state of a digital pin to the peer with some inherent latency. The latency depends on the quality of the RF connection, and even with the best of connection the user must test actual timings to check that the latency is acceptable for the use case. Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 180 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 14.7.6 Enhanced Inquiry Responses Bluetooth 2.1 specification allows up to 240 bytes of extended inquiry data. On BT740-Sx modules, this data is limited to a maximum length based on firmware builds due to internal memory restrictions. Extended inquiry data transmits e.g. the friendly name, UUIDs of supported profiles, or user defined data within the inquiry process and without a Bluetooth connection.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 15 SURFACE MOUNT MODULES 15.1 Introduction Laird surface mount modules are designed to conform to all major manufacturing guidelines. This section provides additional guidance for mounting the module. This section is considered a living document and is updated as new information is presented. The modules are designed to meet the needs of a number of commercial and industrial applications.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 15.3 Reflow Parameters Laird surface mount modules are designed to be easily manufactured, including reflow soldering to a PCB. Ultimately it is the responsibility of the customer to choose the appropriate solder paste and to ensure oven temperatures during reflow meet the requirements of the solder paste. Laird’s surface mount modules conform to J-STD-020D1 standards for reflow temperatures.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 16 FCC REGULATORY STATEMENTS Family US/FCC CANADA/IC BT7x0 SQGBT700 3147A-BT700 Part # BT740-SA-XX BT740-SC-XX Form Factor Surface Mount Surface Mount Tx Output 18dBm 18dBm Antenna Chip U.FL *Last two slots "XX" in Part # are for production firmware release changes. Can be values 01-99, aa-zz The BT740 family is designed to operate with the antennas listed below, with a maximum gain of 2dBi. The required antenna impedance is 50 ohms.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide applications require further RF evaluation. Contact a qualified test house or a Laird representative for further information on this topic (reference FCC Part 2.1093 for further details on portable devices). Maximum Permissible Exposure report was created and shows the minimum distances for Public and Occupational use of the BT740. Note: Occupational Limit Minimum Distance = 1.5 cm. Public Limit Minimum Distance = 3 cm.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 16.2 OEM Responsibilities This device is intended only for OEM integrators under the following conditions: 1) The antenna must be installed such that 20 cm is maintained between the antenna and users, and 2) The transmitter module may not be co-located with any other transmitter or antenna. As long as 2 conditions above are met, further transmitter test will not be required.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Industry Canada (IC) Warning: This device complies with RSS-210 of the Industry Canada 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. Ce dispositif est conforme à la norme CNR-210 d'Industrie Canada applicable aux appareils radio exempts de licence.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide NOTE IMPORTANTE: Dans le cas où ces conditions ne peuvent être satisfaites (par exemple pour certaines configurations d'ordinateur portable ou de certaines co-localisation avec un autre émetteur), l'autorisation du Canada n'est plus considéré comme valide et l'ID IC ne peut pas être utilisé sur le produit final.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 1. CE Regulatory The BT740 has been tested for compliance with relevant standards for the EU market. The OEM should consult with a qualified test house before entering their device into an EU member country to make sure all regulatory requirements have been met for their complete device. The BT740 was tested with a 2dBi dipole antenna.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 17 EU DECLARATIONS OF CONFORMITY 17.1 BT740-SA Manufacturer: Laird Product: BT740-SA EU Directive: RTTE 1995/5/EC Conformity Assessment: Annex IV Reference standards used for presumption of conformity: Article Number Requirement Reference standard(s) 3.1a Health and Safety EN 60950-1:2006 3.1b Protection requirements with respect to electromagnetic compatibility EN 301 489-1 V1.8.1 EN 301 489-17 V2.1.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 17.2 BT740-SC Manufacturer: Laird Product: BT740-SC EU Directive: RTTE 1995/5/EC Conformity Assessment: Annex IV Reference standards used for presumption of conformity: Article Number Requirement Reference standard(s) 3.1a Health and Safety EN 60950-1:2006 3.1b Protection requirements with respect to electromagnetic compatibility EN 301 489-1 V1.8.1 EN 301 489-17 V2.1.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 18 MECHANICAL DETAILS 18.1 BT740-SC Mechanical Details Figure 18-1: BT740-SC mechanical details Module Keep-Out Area: An area of 1.5 mm around the module should be reserved as a keep-out area .No other components should be placed in this area. 18.2 BT740-SA Mechanical Details Figure 18-2: BT740-SA mechanical details Module Keep-Out Area: An area of 1.5 mm around the module should be reserved as a keep-out area.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 18.3 BT740 Pad Definitions – Mechanical Drawing Figure 18-3: Pad definitions mechanical drawing Americas: +1-800-492-2320 Option 2 Europe: +44-1628-858-940 Hong Kong: +852-2923-0610 www.lairdtech.com/wireless 193 CONN-GUIDE-BT740_v0.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 19 ORDERING INFORMATION Part Number Description BT740-SA Enhanced Class 1 Bluetooth V2.1 Module (internal antenna) BT740-SC Enhanced Class 1 Bluetooth v2.1 Module (uFL for external antenna) DVK – BT740-SA Development board with BT740-SA module soldered in place DVK – BT740-SC Development board with BT740-SC module soldered in place 19.1 General Comments This is a preliminary datasheet.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide 20 BLUETOOTH SIG APPROVALS 20.1 Subsystem Combinations This section covers the procedure for generating a new EPL (End Product Listing) on the Bluetooth SIG website. In the instance of subsystems, a member can combine two or more subsystems to create a complete Bluetooth end product. Subsystem listings referenced as an example: Design Name Owner QDID number Link to listing on the SIG website BT740-Sx Laird B0xxxx https://www.bluetooth.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Note: Alternatively, the member can choose to have a new QDID for the subsystem combination. However, note that this incurs a listing fee and requires the subsystem combination to be assessed against the latest qualification requirements. 20.1.2 Useful FAQ links https://www.bluetooth.org/ticketing/view_article.cfm?action=article_comment&aid=284 https://www.bluetooth.org/ticketing/view_article.cfm?action=article_comment&aid=300 https://www.bluetooth.
Enhanced Class 1 Bluetooth v2.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Term Description PWM : Pulse Width Modulation SBC : Sub Band Codec SCO : Synchronous Connection Oriented Link (used for Audio) SLC : Service Level Connection SPP : Serial Port Profile SSO : Serial Stream Oriented SSP : Secure Simple Pairing SUI : SUBUNIT INFO Command Sxxx : S-Register No.
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Index ^^^ ........................................................................ 17 AT+BTKY ............................................................. 26 ‘AT’ S Registers................................................. 46 AT+BTN? ............................................................. 26 Abstract Data Model........................................... 146 AT+BTN= ................................................
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide AT+KY? .................................................... 32 Debug Packet..................................................... 119 ATA ...................................................................... 17 Default ‘S’ Registers............................................. 65 ATD,......................................... 17 Disassociate From Manager .............................. 109 ATEn .....................................
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide HDP Usage Message......................................... 128 Malloc Statistics ................................................. 120 HDP: Endpoint Definitionin SDP Record .............. 31 Manager Related AT Asynchronous Responses 161 HID Connections ................................................ 126 Manager Related AT Commands ....................... 160 HID Descriptors ..................................................
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Read The Link Key For Address Specified .......... 32 Sniff Mode Explained ......................................... 134 Register SDP record ............................................ 99 Special S Registers (240 to 255).......................... 45 Remote Friendly Name ...................................... 117 Specifying a Custom Hid Descriptor for Use ...... 127 Reset....................................................................
Enhanced Class 1 Bluetooth v2.1 Module User’s Guide Smart Technology. Delivered. Laird Ltd. is the world leader in the design and manufacture of customized, performance-critical products for wireless and other advanced electronics applications.
