Banggood HC-05 User Manual

Param1: Bluetooth address Param2: device class
Param3: RSSI signal strength

Example 1:
At+init\r\n – Initialize the SPP library (cannot be initialized repeatedly)
OK
At+iac=9e8b33\r\n – Query the Bluetooth device of any access code
OK
At+class=0\r\n – query various Bluetooth device classes
At+inqm=1,9,48\r\n ——Query mode: with RSSI signal strength indication, more than
9 Bluetooth devices Response will terminate the query, set the super
The time is 48×1.28=61.44 seconds. At+inq\r\n – Query peripheral Bluetooth devices
+INQ: 2:72:D2224,3E0104,FFBC
+INQ: 1234:56:0,1F1F,FFC1
+INQ:1234:56:0,1F1F,FFC0
+INQ: 1234:56:0,1F1F,FFC1
+INQ: 2:72:D2224,3F0104,FFAD
+INQ: 1234:56:0,1F1F, FFBE
+INQ: 1234:56:0,1F1F, FFC2
+INQ: 1234:56:0,1F1F, FFBE
+INQ: 2:72:D2224,3F0104,FFBC
OK
Example 2:
At+iac=9e8b33\r\n – Query the Bluetooth device of any access code
OK
At+class=1f1f\r\n – Query the Bluetooth device with device class 0x1f1f
OK
At+inqm=1,9,48\r\n ——Query mode: with RSSI signal strength indication, more than
9 Bluetooth devices Response will terminate the query, set the super
The time is 48×1.28=61.44 seconds. At+inq\r\n – Filter. Query peripheral Bluetooth devices
+INQ: 1234:56:0,1F1F, FFC2
+INQ: 1234:56:0,1F1F,FFC1
+INQ: 1234:56:0,1F1F,FFC1
+INQ: 1234:56:0,1F1F,FFC1
+INQ: 1234:56:0,1F1F, FFC2
+INQ: 1234:56:0,1F1F,FFC1
+INQ: 1234:56:0,1F1F,FFC1
+INQ:1234:56:0,1F1F,FFC0
+INQ: 1234:56:0,1F1F, FFC2
OK
Example 3:
At+iac=9e8b3f\r\n ——Query the Bluetooth device with access code 0x9e8b3f
OK
At+class=1f1f\r\n – Query the Bluetooth device with device class 0x1f1f
OK
At+inqm=1,1,20\r\n ——Query mode: with RSSI signal strength indication, more than
1 Bluetooth device Response will terminate the query, set the super
The time is 20×1.28=25.6 seconds. At+inq\r\n – Filter. Query peripheral Bluetooth devices
+INQ:1234:56:ABCDEF,1F1F,FFC2
OK

31. Cancel the inquiry of Bluetooth devices:

Command

| Response| Parameter
---|---|---
AT+INQC| OK|

/

32. Device pairing:

Command

| Response| Parameter
---|---|---
AT+PAIR=,| 1.  OK——Success
2.  FAIL——Failure|

Param1: Remote device Bluetooth address
Param2: Connection timeout (seconds)

for example:
Paired with a remote Bluetooth device: 12:34:56:ab:cd:ef, the maximum pairing
timeout is 20 seconds. At+pai=1234,56,abcdef,20\r\n
OK

33. Equipment connection:

Command

| Response| Parameter
---|---|---
AT+LINK=| 1.   OK——Success
2.  FAIL——Failure|

Param: Remote device Bluetooth address

for example:
Establish a connection with the remote Bluetooth device: 12:34:56:ab:cd:ef
At+fsad=1234,56,abcdef\r\n——Query whether the Bluetooth device
12:34:56:ab:cd:ef is in the pairing list
OK
At+link=1234,56,abcdef\r\n——Query the Bluetooth device 12:34:56:ab:cd:ef in the
pairing list, you can connect directly without query. OK

34. Disconnect:

Command

| Response| Parameter
---|---|---

AT+DISC

| 1. +DISC:SUCCESS – Disconnect Success
OK
2. +DISC: LINK_LOSS – connection lost
OK
3. +DISC: NO_SLC – no SLC connection
OK
4. +DISC: TIMEOUT – disconnect timeout
OK
5. +DISC:ERROR – disconnect error
OK|

/

35. Enter the energy saving mode:

Command

| Response| Parameter
---|---|---
AT+ENSNIFF=| OK|

Param: Device Bluetooth address

36. Exit the energy saving mode:

Command

| Response|

Parameter

---|---|---
AT+EXSNIFF=| OK|

Param: Device Bluetooth address

Appendix 1: ATCommand Error Code Description
Error code return form – ERROR: (error_code)

error_code (hexadecimal number)

| Comment
---|---

0

|

AT command error

1

|

Command result is the default value

2

|

PSKEY write error

3

|

Device name is too long (more than 32 bytes)

4

|

Device name length is zero

5

|

Bluetooth address: NAP is too long

6

|

Bluetooth address: UAP is too long

7|

Bluetooth address: LAP is too long

8

|

PIO sequence number mask length is zero

9

|

Countless PIO serial numbers

A|

Device class length is zero

B

|

Device class number is too long

C

|

Query access code length is zero

D

|

The query access code number is too long

E

|

Invalid query access code

F|

Pairing code length is zero

10

|

Pairing code is too long (more than 16 bytes)

11

| Module role is invalid

12

| Invalid baud rate

13

| Invalid stop bit
14|

Check digit is invalid

15|

No authentication device exists in the pairing list

16|

SPP library is not initialized

17

|

SPP library repeated initialization

18

|

Invalid query mode

19|

Query timeout too large

1A

|

Bluetooth address is zero

1B

|

Invalid security mode

1C|

Invalid encryption mode

Appendix 2: Device Class Description
The Class of Device/Service(COD)is a 32 bifs number that of 3 field specifies the service supported by the device. Another field specifies the minor device class, which describes the device type in more detail
The Class of Device /Service (CoD) field has a variable format. The format is
indicated using the ’within the CoD .The length of the Format Type field is variable and ends with two bits different from’11’.The version field starts at the least significant bit of the CoD and may extend upwards. In the ’format#1’ of the CoD (format Type field =00), 11 bits are assigned as a bit –mask(multiple bits can be set) each bit corresponding to a high level generic category of service class. Currently 7 categories are defined. These are primarily of a’ public service’ nature. The remaining 11 bits are used to indicate device type category and other device-specific characteristics. Any reserved but otherwise unassigned bits, such as in the Major Service Class field, should be to 0.
Figure 1.2: The Class of Device/Service field (format type). Please note the krder in which the octets are sent on the air and stored in memory. Bit number 0 is sent first on the air .

1. MAJOR SERVICE CLASSES
   Bit no Major Service Class
   13 Limited Discoverable Mode [Ref #1] 14 (reserved)
   15 (reserved)
   16 Positioning(Location identification)
   17 Networking (LAN,Ad hoc, ⋯ )
   18 Rendering (Printing ,Speaker,⋯ 19 Capturing (Scanner,Misrophone,⋯ 20 0bject Transfer (v-Inbox, v-Folder,⋯ 21 Audio (Speaker,Microphone,Headset service,⋯ 22 Telephony (Cordless telephony, Modem, Headset service,⋯ 23 Imformation (WEB-server, WAP- server,⋯
   TABLE 1.2:MAJOR SERVICE CLASSES
   [Ref #1 As defined in See Generic Access Profile,Bluetooth SIG]

2. MAJOR DEVICE CLASSES
   The Major Class segment is the highest level of granularity for defining a Bluetooth Device. The main function of a device is used to determine the major Class grouping. There are 32 different possible major classes. The assignment of this Major Class field is defined in Table1.3.
   1 2 1 1 1 0 9 8 Major Device Class
   0 0 0 0 0 Miscel laneous [Ref #2] 0 0 0 0 1 Computer (desktop, notebook,PDA, organizers,⋯ 0 0 0 1 0 Phone (cellular ,cordless ,payphone,modem,⋯ 0 0 0 1 1 LAN/Network Access point
   0 0 1 0 0 Audio/Video (headset,speaker,stereo, video display, vcr ⋯ 0 0 1 0 1 Periphereal (mouse, joystick, keyboards.⋯ 0 0 1 1 0 Imaging (printing, scanner, camera, display,⋯ 1 1 1 1 1 Uncategorized, specific device code not specified
   X X X X All other values reserved
   TABLE 1.3: MAJOE DEVICE CLASSES
   [Ref #2:Used where a more specific Major Device Class is not suited (but only as specified as in this document) .Devices that do not have a major class assigned can use the all-1 code until’ classified’]

3. THE MINOR DEVICE CLASS FIELD
   The’ Minor Device Class field’ (bits 7 to 2 in the CoD ), are to be interpreted only in the context of the Major Device Class (but interpreted of the Service Class field). Thus the meaning of the bits may change, depending on the value of the ’ Major Device Class field’. When the Minor Device Class field indicates a device class ,then the primary device class should be reported, e. g . a cellular phone that can work as a cordless handset should

4. MINOR DEVICE CLASS FIELD–COMPUTER MAJOR CLASS
   Minor Device Class
   7 6 5 4 3 2 bit no of CoD
   0 0 0 0 0 0 Uncategorized,code for device nof assigned
   0 0 0 0 0 1 Desktop workstation
   0 0 0 0 1 0 Server-class computer
   0 0 0 0 1 1 Laptop
   0 0 0 1 0 0 Handheld PC/PDA(clam shell)
   0 0 0 1 0 1 Palm sized PC/PDA
   0 0 0 1 1 0 Wearable computer (Watch sized)
   X X X X X X All other values reserved
   TABLE 1.4: SUB DEVICE CLASS FIELD FOR THE’ COMPUTER ’MAJOR CLASS

5. MINOR DEVICE CLASS FIELD – PHONE MAJOR CLASS
   Minor Device Class
   7 6 5 4 3 2 bit no of CoD
   0 0 0 0 0 0 Uncategorized, code for device not assigned
   000001 Cellular
   0 0 0 0 1 0 Cordless
   0 0 0 0 1 1 Smart phone
   0 0 0 1 0 0 Wired modem or voice gateway
   0 0 0 1 0 1 Common ISDN Access
   0 0 0 1 1 0 Sim Card Reader
   X X X X X X All other values reserved
   TABLE1.5: SUB DEVICE CLASSES FOR THE’PHONE’ MAJOR CLASS

6. MINOR DEVICE CLASS FIELD –LAN/NETWORK ACCESS POINE MAJOR CLASS
   Minor Device Class
   7 6 5 bit no of CoD
   0 0 0 Fully available
   0 0 1 1 – 17% utilized
   0 1 0 1 7 – 33% utilized
   0 1 1 3 3 – 50% utilized
   1 0 0 5 0 – 67% utilized
   1 0 1 6 7 – 83% utilized
   1 1 0 8 3 – 99% utilized
   1 1 1 No service available [REF #3] XXX All other values reserved
   TABLE1.6: THE LAN/NETWORK ACCESS POINE LOAD FACTOR FIELD
   [Ref #3:”Device is fully utilized and cannot accept additional connections at this time, please retry later”] The exact loading formula is not standardized. It is up to each LAN/Network Access
   Point implementation to determine what internal conditions to report as a
   utilization of communication requirement is that the box .As a recommendation, a client that locates multiple LAN/Network Access Points should attempt to connect to the one reporting the lowest load. Minor Device Class
   4 3 2 bit no of CoD
   0 0 0 Uncategorized (use this value if no other apply )
   XXX All other values reserved
   TABLE1.7:RESERVED SUB-FIELD FOR THE LAN/NETWORK ACCESS POINE

7. MINOR DEVICE CLASS FIELD – AUDIO/VIDEO MAJOR CLASS
   Minor Device Class
   7 6 5 4 3 2 bit no of CoD
   0 0 0 0 0 0 Uncategorized, code not assigned
   0 0 0 0 0 1 Device conforms to the Headset profile
   000010 Hands-free
   0 0 0 0 1 1 (Reserved )
   0 0 0 1 0 0 Microphone
   0 0 0 1 0 1 Loudspeaker
   0 0 0 1 1 0 Headphones
   0 0 0 1 1 1 Portable Audio
   0 0 1 0 0 0 Car audio
   0 0 1 0 0 1 Set-top box
   0 0 1 0 1 0 HiFi Audio Device
   001011 VCR
   0 0 1 1 0 1 Camcorder
   0 0 1 1 1 0 Video Monitor
   0 0 1 1 1 1 Video Display and Loudspeaker
   0 1 0 0 0 0 Video Conferencing
   0 1 0 0 0 1 (Reserved)
   0 1 0 0 1 0 Gaming/Toy [Ref #4] X X X X X X All other values reserved
   [Ret #4: Only to be used with a Gaming/Toy device that makes audio/video
   capabilities
   available via Bluetooth] TABLE 1.8: SUB DEVICES FOR THE ’AUDIO/VIOEO’MAJOR CLASS

8. MINOR DEVICE CLASS FIELD – PERIPHERAL MAJOR CLASS
   Minor Device Class
   7 6 bit no of CoD
   0 1 Keyboard
   1 0 Pointing device
   1 1 Combo keyboard /pointing device
   X X X All other values reserved
   TABLE1.9 : THE PERIPHERAL MAJOR CLASS KEYBOARD/POINTING DEVICE FIELD
   Bits 6 and 7 independently specify mouse, keyboard or combo mouse/keyboard devices.
   These may be combined with the lower bits in a multifunctional device. Minor Device Class
   5 4 3 2 bit no of CoD
   0 0 0 0 Uncategorized device
   0 0 0 1 Gamepad
   0 0 1 1 Remote control
   0 1 0 0 Sensing device
   0 1 0 1 Digitizer tablet
   X X X X All other values reserved
   TABLE1.10: RESERVED SUB-FIELD FOR THE DEVICE TYPE

9. MINOR DEVICE CLASS FIELD – IMAGING MAJOR CLASS
   Minor Device Class
   7 6 5 4 bit no of CoD
   X X X 1 Display
   X X 1 X Camera
   X 1 X X Scanner
   1 X X X Printer
   X X X X All other values reserved
   TABLE 1.11: THE TMAGING MAJOR CLASS BITS 7 TO 7
   Bits 4 to 7 independent ly specify bi splay, camera, scanner or printer. These may be combined in a multifunctional device.
   Minor Device Class
   3 2 bit no of CoD
   0 0 Uncategorized, default
   X X All other values reserved
   TABLE 1. 12: THE IMAGING MAJOR CLASS BITS 2 AND 3
   Bits 2 and 3 are reserved

Appendix 3: The Inquiry Access Codes

The General-and Device-Specific Inquiry Access Codes (DIACs)
The Inquiry Access Code is the first level of filtering when finding Bluetooth
The main purpose of defining multiple IACs is to limit the number of
Reply that are received when scanning devices within range. 0. 0x9E8B33 — General/Unlimited Inquiry Access Code (GIAC)

1. 0x9E8B00 – Limited Dedicated Inquiry Access Code (LIAC)
2. 0x9E8B01 ~ 0x9E8B32 RESERVED FOR FUTURE USE
3. 0x9E8B34 ~ 0x9E8B3F RESERVED FOR FUTURE USE

The Limited Inquiry Access Code(LIAC)is only intended to be used for limited time Periods in scenarios where both are have been explicitly caused to enter this state, Usually by user action. For further explanation of the use of the LIAC, please refer To the Generic Access Profile.
In contrast it is allowed to be continuously scanning for the General Inquiry Access Code (GIAC) and respond whenever inquired

Banggood HC-05 User Manual – Download [optimized]
Banggood HC-05 User Manual – Download

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>