User's Manual

Enhanced Class 1 Bluetooth v2.1 Module
User’s Guide
Americas: [phone] Option 2
Europe: [phone]
Hong Kong: [phone]
www.lairdtech.com/wireless
103
CONN-GUIDE-BT740_v0.2
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.
For example, to send the string “HelloWorld” and “LairdRules!” as the manufacturer specific data objects,
then the BLOB should load with the following data :
0B FF ‘H’ ‘e’ ‘l’ ‘l’ ‘o’ ‘W’ ‘o’ ‘r’ ‘l’ ‘d’ 0C FF ‘L’ ‘a’ ‘I’ ‘r’ ‘d’ ‘R’ ‘u’ ‘l’ ‘e’ ‘s’ ‘!’
Where 0B and 0C are length bytes and FF is the type value for ‘manufacturer specific data’.
Before submission, the data block is verified to see if the length bytes are consistent with total length of
the block.
Save Enhanced Inquired Response Data :: 8
Use this subcommand to save the BLOB data in non-volatile memory so that the data installs the custom
EIR data response on every power up. Before committing to memory, the data block is verified to see if
the length bytes are consistent with total length of the block.
Load Enhanced Inquired Response Data:: 9
Use this subcommand to load the BLOB specified with data from non-volatile memory associated with
Enhanced Inquiry responses; The data that was saved using subcommand 8 described.
8.17 HDP Profile Commands
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). The manager role is for testing the agent implementation
only and it is not expected or designed for eventual certification by the Continua Alliance.
It is assumed that the reader is familiar with all the HDP and IEEE documentation and relevant guidelines
published by the Continua Alliance. For further background information related to the HDP
implementation in this module please refer to AT Application Examples.
The HDP commands, responses and events described in the subsequent chapters are merely the MP
way of managing the functionality and do not add any new features other than those described in the AT
Applications Example section. Laird recommends the reader to refer to the AT Application Examples
section for further details.
To assist with this cross referencing of details, the table below shows the equivalent commands in AT and
MP mode respectively to achieve the same effect in the module.
AT Mode Commands
MP Mode Commands
Comments
AT+HAEiiii,”name”
AT+HMEiiii,”name”
CMD_HDP_ENDPOINT
Affects an entry in the SDP record
AT+HAL
AT+HML
CMD_HDP_SDPREGISTER
Register and activate HDP service
record
AT+HABeeeee,iiii
CMD_HDP_BIND
Create an agent data
specialization of type iiii which will
connect to a manager with
Bluetooth address ‘eeeeee’
AT+HAAhhhh
CMD_HDP_ASSOCIATE
AT+HARhhhh,pppp[…]
CMD_HDP_SCANREPORT_FI
XED
CMD_HDP_SCANREPORT_V
AR
In MP, the attribute list for var
report is supplied via a BLOB
channel.
AT+HAGhhhh,aaaa,ssss
CMD_HDP_ATTRIBUTE_REA
Read an attribute value. In MP