User's Manual

Class 1 Bluetooth v2.0 Module
User’s Guide
Americas: [phone] Option 2
Europe: [phone]
Hong Kong: [phone]
www.lairdtech.com/bluetooth
43
CONN-GUIDE-BT730_v0.9
6.3.32 AT+BTGY{Enable Promiscuous Page Scanning ONLY}
Enable page scanning only and wait for a connection from any device. Inquiry scans disabled.
Authentication is disabled and encryption is enabled.
Response: <cr,lf>OK<cr,lf>
6.3.33 AT+BTGUY{Enable Promiscuous Page Scanning ONLY}
Enable page scanning only and wait for a connection from any device. Inquiry scans are disabled.
Authentication and encryption are both enabled. The order of U and Y is not significant.
Response: <cr,lf>OK<cr,lf>
6.3.34 AT+BTI<devclass>{Inquire}
This makes the device perform an inquiry for device class code for delay milliseconds and max number
of unique responses, where delay is specified by S register 517 and max is specified by S register 518.
The <devclass> is an optional parameter where the value specifies either a six digit device class code or
a two digit major device class. If it is not specified, the value is taken from S register 516.
When <devclass> is six hexadecimal characters long, it specifies an AND mask which is used to filter
inquiry responses. When <devclass> is two hexadecimal characters long, it forces the inquiry to filter
responses to devices that match their major device class code to this value (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
responds 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>
6.3.35 ERROR RESPONSE
For a single inquiry request with the Bluetooth inquiry process, 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 filled as responses come in. This array of addresses is stored
in dynamic memory and, if the memory allocation fails, the inquiry procedure is aborted. If that occurs, an
error response is sent to the host.
To clarify, a single AT+BTI never returns the same Bluetooth address more than once, but as long as the
responding device is active, all AT+BTI commands always return it.
Response: <cr,lf>ERROR 27<cr,lf>
6.3.36 AT+BTIV<devclass>{Inquire}
As per AT+BTI but the response includes the device class code for all inquiry responses. Refer to the
‘ERROR RESPONSE’ note in the description for AT+BTI<devclass>.
Response: <cr,lf>12346789012,123456
<cr,lf>12345678914,123456