User's Manual

11
www.lairdtech.com
Laird Technologies
BTM410/411
Bluetooth
®
AT Data Module
CONFIGURING
THE BTM410/411
3. AT
Used to check the module is available.
Response: <cr,lf>OK<cr,lf>
4. 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>
5. ATD<U><Y><bd_addr>,<uuid> {Make Outgoing Connection}
Make a connection to device with Bluetooth address <bd_addr> and SPP pro le <uuid>. The <uuid>
is an optional parameter which speci es the UUID of the pro le server to attach to, and if not supplied
then the default UUID from S Register 101 is used. As this is a device which utilises the RFCOMM
layer as described in the Bluetooth speci cation, it necessarily implies that only pro les based on
RFCOMM can be accessed.
If <U> is not speci ed, then authentication is as per register 500, otherwise the connection will
be authenticated.
If <Y> is not speci ed, then encryption is as per register 501, otherwise the connection will have
encryption enabled.
The timeout is speci ed by S register 505.
Response: <cr,lf>CONNECT 123456789012<cr,lf>
Or <cr,lf>NO CARRIER<cr,lf>
Due to a known issue in the Bluetooth RFCOMM stack, it is not possible to make more than 65525
outgoing connections in a single power up session. Therefore if that number is exceeded, then the
connection attempt will fail with the following response:-
Response: <cr,lf>CALL LIMIT
Or <cr,lf>NO CARRIER<cr,lf>
In that case, issuing an ATZ to reset the device will reset the count to 0 and more connections
are possible.
The following RFCOMM based UUIDs are de ned in the Bluetooth Speci cation:-
PROFILE NAME UUID
Serial Port 0x1101
LAN Access Using PPP 0x1102
Dialup Networking 0x1103
IrMC Sync 0x1104
OBEX Object Push 0x1105
OBEX File Transfer 0x1106
IrMC Sync Command 0x1107
Headset 0x1108
Cordless Telephony 0x1109
Intercom 0x1110
Fax 0x1111
Audio Gateway 0x1112
WAP 0x1113
WAP_CLIENT 0x1114