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
19
CONN-GUIDE-BT730_v0.9
6.3.1 ^^^{Enter Local Command Mode}
When in data and connected mode, the host can force the device into a command and connected mode
so that AT commands can be issued to the device. The character in this escape sequence is specified in
the S2 register, therefore it can be changed. In addition, the escape sequence guard time is specified by
S Register 12. By default the guard time is set to 100 milliseconds. Refer to Section 6.6: Dropping
Connections for more information.
In modems this escape sequence is usually “+++”. “^^^” is specified to avoid confusion when the module
is providing access to a modem.
Response:<cr,lf>OK<cr,lf>
6.3.1 !!!{Enter Remote Command Mode}
When in data and connected mode, the host can force the remote device into a command and connected
mode so that AT commands can be issued to the device remotely. The escape sequence guard time is
specified by S Register 12 and is the same as per the ^^^ escape sequence. By default the guard time is
set to 100 milliseconds. The remote device issues ATO as normal to return to data mode. (Refer to 2.2.12)
For this command to be effective, S Register 536 must be set to 1.
Response:<cr,lf>OK<cr,lf>
6.3.2 AT
Used to check the module is available.
Response:<cr,lf>OK<cr,lf>
6.3.3 ATA{Answer Call}
Accept an incoming connection, which is indicated by the unsolicited string
<cr,lf>RING 123456789012<cr,lf> every second. 123456789012 is the Bluetooth address of the
connecting device.
Response: <cr,lf>CONNECT 123456789012<cr,lf>
6.3.4 ATD<U><Y><bd_addr>,<uuid> {Make Outgoing Connection}
Make a connection to a device with Bluetooth address <bd_addr> and profile <uuid>. The <uuid> is an
optional parameter which specifies the UUID of the profile server to attach to; if not supplied, then the
default UUID from S Register 101 is used. Because this is a Laird device which utilises the RFCOMM
layer as described in the Bluetooth specification, it implies that only profiles based on RFCOMM can be
accessed.
If <U> is not specified, then authentication is as per register 500, otherwise the connection will be
authenticated.
If <Y> is not specified, then encryption is as per register 501, otherwise the connection will have
encryption enabled.
The timeout is specified by S register 505.
Response: <cr,lf>CONNECT 123456789012<cr,lf>
Or <cr,lf>NO CARRIER<cr,lf>