User's Manual

24
www.lairdtech.com
Laird Technologies
BTM510/511
Bluetooth
®
Multimedia Module
CONFIGURING
THE BTM510/511
7.AT+BTF<bd_addr>{GetRemoteFriendlyName}
This command gets the remote friendly name of the peer specied.
Response: <cr,lf><bd_addr>,”Friendly Name”
<cr,lf>OK<cr,lf>
8.AT+BTG<bd_addr>{EnableCautiousPageScanningONLY}
Make device connectable and wait for a connection from device with Bluetooth address <bd_addr>.
If the specied address is 000000000000 then incoming connections are accepted from any device,
is as per AT+BTP without an address. Inquiry Scans are disabled.
Response: <cr,lf>OK<cr,lf>
 9.AT+BTG{EnablePromiscuousPageScanningONLY}
Enable page scanning only and wait for a connection from any device. Inquiry scans are disabled.
Response: <cr,lf>OK<cr,lf>
10.AT+BTI<devclass>{Inquire}
This will make the device perform an inquiry for device class code for delay seconds and max
number of unique responses, where delay is specied by S register 517 and max is specied by S
register 518.
The <devclass> is an optional parameter where the value species either a 6 digit device class code
or a 2 digit major device class. If it is not specied, then the value is taken from S register 516.
When <devclass> is 6 hexadecimal characters long, it species an AND mask which is used to lter
inquiry responses. When <devclass> is 2 hexadecimal characters long, it forces the inquiry to lter
responses to devices that match their major device class code to this value – which can only be in
the range 00 to 1F.
Response: <cr,lf>12346789012
<cr,lf>12345678914
<cr,lf>OK<cr,lf>
If the module is waiting for an incoming connection, (entered via AT+BTP, AT+BTG, AT+BTQ),
then it will respond with ERROR 14. To perform the inquiry, send AT+BTX to put the module
back into idle mode.
Response: <cr,lf>ERROR 14<cr,lf>
ERROR RESPONSE
A Bluetooth inquiry process is such that for a single inquiry request a device could respond
many times. To ensure that an address is sent to the host only once for a particular AT+BTI,
an array of addresses is created at the start of each AT+BTI and is lled as responses come in.
This array of addresses is stored in dynamic memory and as such if the memory allocation fails
then the inquiry procedure is aborted and in that case an error response is sent to the host.
To clarify, a single AT+BTI will never return the same Bluetooth address more than once, but as
long as the responding device is active, all AT+BTI commands will always return it.
Response: <cr,lf>ERROR 27<cr,lf>
11.AT+BTIV<devclass>{Inquire}
As per AT+BTI but the response includes the device class code for all inquiry responses. Please refer
to the ‘ERROR RESPONSE’ note in the description for AT+BTI<devclass>.
Response: <cr,lf>12346789012,123456
<cr,lf>12345678914,123456
<cr,lf>OK<cr,lf>