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
46
CONN-GUIDE-BT730_v0.9
6.3.47 AT+BTPU{Enable Promiscuous Page/Inquiry Scanning}
Enable page scanning and wait for a connection from any device. Inquiry scanning is also enabled.
Authentication is enabled and encryption is disabled.
Response: <cr,lf>OK<cr,lf>
6.3.48 AT+BTPY{Enable Promiscuous Page/Inquiry Scanning}
Enable page scanning and wait for a connection from any device. Inquiry scanning is also enabled.
Authentication is disabled and encryption is enabled.
Response: <cr,lf>OK<cr,lf>
6.3.49 AT+BTPUY{Enable Promiscuous Page/Inquiry Scanning}
Enable page scanning and wait for a connection from any device. Inquiry scanning is also enabled.
Authentication and encryption are both enabled. The order of U and Y is not significant.
Response: <cr,lf>OK<cr,lf>
6.3.50 AT+BTQ{Enable Inquiry Scans ONLY}
When inquiry scan is enabled, it implies that this device responds to inquiries from other devices. Use
AT+BTX to disable inquiries.
Response: <cr,lf>OK<cr,lf>
6.3.51 AT+BTR<bd_addr>{Set Outgoing Peer Address}
This command is used to store a peer address for outbound connections in non-volatile memory. A value
of 000000000000 has the special meaning of invalid peer address.
This command is used to set up a module in pure cable replacement mode.
If S register 512 = 1 and the peer address is not 000000000000, then it periodically (time specified via S
register 505) attempts to connect to the peer address specified. In this circumstance, all commands from
the host are buffered in the receive buffer until a Bluetooth connection is established with the peer device
and it then sends 0 the buffer across. This means that if the peer device is not in the vicinity and will
never be there, the device effectively becomes useless, as in this circumstance a host would want to get
attention of the AT parser to send it new commands – probably one to delete the peer device.
In this circumstance, a recovery is possible by one of two methods. The first method assumes that the
DTR from the host is connected to the DSR line of the module and the second method assumes that this
connection is absent. In the first method it is enough to deassert the DTR line from the host and that will
abort the autoconnect cycle. The second method is initiated by resetting the device and then ensuring
that the text string “AT+BT&BISM&<cr>” is sent (where <cr> is the carriage return character). There is
special code which looks out for this magic command and terminates the autoconnect cycle if it sees it
and confirms to the host of that fact by sending an “OK” response.
Response: <cr,lf>OK<cr,lf>