User's Manual
Class 1 Bluetooth v2.0 Module
User’s Guide
Americas: +1-800-492-2320 Option 2
Europe: +44-1628-858-940
Hong Kong: +852-2923-0610
www.lairdtech.com/bluetooth
41
CONN-GUIDE-BT730_v0.9
6.3.23 AT+BTC<devclass>{Set Device Class Code}
This command is used to set the device class code which is sent in subsequent inquiry responses. It can
be read back using the AT+BTC? command as described below.
<devclass> is a six digit hexadecimal number derived as per section “1.2 The Class of Device/Service
Field” of the Bluetooth specification “Bluetooth Assigned Numbers”.
The 24 bits are made of the following four fields (bit 0 corresponds to the least significant bit):
Bits 0-1:
Format Type. This field currently only has a value of 00 (i.e. format type
1).
Bits 2-7:
These 6 bits define the Minor Device Class and the value is interpreted
differently based on the Major Device class stored in the next 5 bits.
Bits 8-12:
These 5 bits define the Major Device Class as per Table 1.3 in “Bluetooth
Assigned Numbers”.
Bits 13-23:
This is an 11 bit field used as a mask to define the Major Service Class,
as per Table 1.2 in “Bluetooth Assigned Number”.
Laird devices do not map to any predefined Major Service Class or Major Device Class. The default
devclass as shipped is 001F00 which means no Major Service Class and “Unclassified” Major Device
class.
Table 6-4 shows examples of device class codes.
Table 6-4: Device class codes
Code (Hex)
Name
Major Service
Major Device
Minor Device
001F00
Unclassified
None
Unclassified
n/a
200404
Headset
Audio
Audio
Headset
Response: <cr,lf>OK<cr,lf>
Or for an invalid <devclass> value (usually a value which is not six hexadecimal characters long).
Response: <cr,lf>ERROR 08<cr,lf>
6.3.24 AT+BTC?{Read Device Class Code}
This command is used to read the current device class code.
Response: <cr,lf>123456<cr,lf>OK<cr,lf>
6.3.25 AT+BTD<bd_addr>{Remove Trusted Device}
This command is used to remove the specified device from the list of trusted devices in the non-volatile
database. If the device is not in the database, the response is still OK.
Response: <cr,lf>OK<cr,lf>