User guide

This command also has variants which allow authentication and encryption to be explicitly
specified. For example:-
AT+BTGU123456789012
AT+BTGY123456789012
AT+BTGUY123456789012
AT+BTGYU123456789012
Response: <cr,lf>OK<cr,lf>
2.2.30 AT+BTG {Enable Promiscuous Page Scanning ONLY}
Enable page scanning only and wait for a connection from any device. Inquiry scans are
disabled. Authentication and Encryption is as per S registers 502 and 503.
Response: <cr,lf>OK<cr,lf>
2.2.31 AT+BTGU {Enable Promiscuous Page Scanning ONLY}
Enable page scanning only and wait for a connection from any device. Inquiry scans are
disabled. Authentication is enabled and encryption is disabled.
Response: <cr,lf>OK<cr,lf>
2.2.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>
2.2.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>
2.2.34 AT+BTI<devclass> {Inquire}
This will make 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 6 digit device
class code or a 2 digit major device class. If it is not specified, then the value is taken from
S register 516.
When <devclass> is 6 hexadecimal characters long, it specifies an AND mask which is
used to filter inquiry responses. When <devclass> is 2 hexadecimal characters long, it
forces the inquiry to filter 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 filled as
responses come in. This array of addresses is stored in dynamic memory and as such if the
DSH_50003_v1v3 AT Command Reference 20 of 33