BNCOM BCM-SQ700-AS Bluetooth Module User Guide
- June 1, 2024
- BnCOM
Table of Contents
- BNCOM BCM-SQ700-AS Bluetooth Module
- Revision History
- Introduction
- References
- Definitions and abbreviations
- AT Command syntax and procedures
- General Commands
- HFP Commands
- Configuration Commands
- Information text and result codes
- APPENDICES
- FCC MODULAR APPROVAL INFORMATION EXAMPLES for Manual
- FCC Radiation Exposure Statement
- Read User Manual Online (PDF format)
- Download This Manual (PDF format)
BNCOM BCM-SQ700-AS Bluetooth Module
Revision History
Introduction
PURPOSE
This document presents the AT command set supported by the BnCOM Bluetooth
audio module and describes the protocol used to control and configure.
INTENDED AUDIENCE AND PERTINENT SECTIONS
This document is intended for BnCOM customers, especially system integrators,
about to implement Bluetooth modules in their applications. Readers of this
document should be familiar with BnCOM modules and their ease of controlling
using AT commands.
References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- ITU-T Recommendation V.250: “Serial asynchronous automatic dialing and control”.
- Bluetooth Core specification v5.2
- Supplement to the Bluetooth Code Specification
- Bluetooth Profile Specification: “Hands-Free Profile 1.8”.
- Bluetooth Profile Specification: “Advanced Audio Distribution v1.3.2”.
- Bluetooth Profile Specification: “Audio/Video Remote Control v1.6.2”.
Definitions and abbreviations
Definitions
For the present document, the following syntactical definitions apply:
-
Carriage return character is the command line and result code terminator character. -
Linefeed character. - <…> Name enclosed in angle brackets is a parameter. The angle brackets themselves do not appear in the command line.
- […] Square brackets are used to indicate that the enclosed items are optional. The square brackets themselves do not appear in the command line.
- Underline Underlined defined sub-parameter value is the recommended default setting of this sub-parameter.
Abbreviations
For the present document, the following abbreviation applies:
- DCE Data Communication Controller
- DTE Data Terminal Equipment
- SRC A device is the SRC when it acts as a source of a digital audio stream that is delivered to the SNK of the piconet
- SNK A device is the SNK when it acts as a sink of a digital audio stream delivered from the SRC on the same piconet
AT Command syntax and procedures
In this document, the following naming conventions are used:
- DCE (Data Communication Equipment): Bluetooth Audio module.
- DTE (Data Termination Equipment): The terminal that commands the module, e.g., PC or MCU.
Command Line
Command line general format
A command line is made up of three elements: the prefix, the body, and the
termination character.
- The command line prefix consists of the character “AT”.
- The body is made up of individual commands as specified later in this document.
- The termination character should be a carriage return character
and it may not appear in the body.
The command line buffer can accept a maximum of 80 characters. If the characters entered exceeded this number, then ERROR will be returned.
Case Sensitivity of Commands
In this document, all AT commands are in uppercase letters.
Basic Syntax commands
The format of basic syntax commands is as follows:
-
is either a single character or the “&” character followed by a single character. Characters used in shall be taken from the set of alphabetic characters. -
may be a string of one character from “0” through “9” representing a decimal integer value. - If a command expects
and it is missing, the default value is assumed. - If a command does not expect a
and a number is present, an ERROR is generated.
Extended Syntax commands
The name of extended syntax commands always begins with the character “+” and
the first character following the “+” shall be alphabetic in the range of “A”
through “Z”.
Type of extended syntax commands
There are four types of extended syntax command operations:
- Test command – Checks whether a certain AT command is supported. +
=? - Set command – Changes the settings. +
= + = - Read command – Retrieves the current settings. +
? - Execution command – Act or retrieve information/status. +
Information responses and result codes
Response format
Information responses and result codes always start and end with a carriage
return character
-
A final result codes indicate that the execution of currently running AT commands is finished. As an example, it can be any one of the following types: If the command is successful.
OK
If the command has the wrong format/the command is invalid/the command is not applicable, etc.
ERROR -
An intermediate result code (IRC) is a report of the progress of a DCE action.
- +
- +
: - +
: Note that a single space character separates the colon character from the .
- +
-
Unsolicited result codes (URC) indicate the occurrence of an event not directly associated with the issuance of a command from DTE.
Range of values
For example, the following are some examples of value range indications:
- (0) Only the value 0 is supported
- (1,2,3) The values 1, 2, and 3 are supported
- (1-3) The values 1 through 3 are supported
Informative examples
Extended syntax result codes
Command| Syntax| Example| Possible Response(s) *1
Test
| ****
+
| ****
AT+UART=? < CR>
| < CR>
+UART: (9600-1382400),(1,2),(N,O,E) < CR>
< CR>
Set| +
Read
| ****
+
| ****
AT+UART? < CR>
| < CR>
+UART: 115200,1,N < CR>
< CR>
Execution| +
General Commands
Attention
Description
Attention command determines the presence of a DCE, i.e., the Bluetooth audio
module.
Syntax
| Command | Possible Response(s) |
|---|---|
| AT | OK |
Defined values
None
Result codes
OK If the DTE and DCE are connected properly No response
Soft reset Z
Description
This command forces a reboot (warm reset) of the module
Syntax
| Command | Possible Response(s) |
|---|---|
| ATZ | OK |
Defined values
None
Result codes
OK If the DTE and DCE are connected properly No response
Examples
Set to factory-defined configuration &F
Description
This command resets all settings to their factory default values specified by
the manufacturer
Syntax
| Command | Possible Response(s) |
|---|---|
| AT&F[ |
OK |
*Defined values1**
- 0 Restore factory settings and reboot within a second*1
- 1 Remove all paired device lists
- (other) Reserved for manufacturer proprietary use
Examples
Version information +VERSION
Description
- Display firmware version
| Command | Possible Response(s) |
|---|---|
| AT+VERSION? | +VERSION: |
Defined values
None
Examples
Bluetooth local name +LOCALNAME
Description
Change Bluetooth local name
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+LOCALNAME= |
OK |
| AT+LOCALNAME? | +LOCALNAME: |
Defined values
Examples
Bluetooth local address +LOCALADDR
Description
This command can be used to read the local Bluetooth address.
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+LOCALADDR? | +LOCALADDR: OK |
Defined values
- None
Examples
Power On/Off +POWER
Description
This command is used to power on or off the module
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+POWER= |
OK |
| AT+POWER=? | +POWER: (list of supported |
Defined values
- 0 Power off
- 1 Power on
- (other) Reserved for manufacturer proprietary use.
Examples
Connection establishment +CONNECT
Description
This command attempts to establish a connection to the last connected device
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+CONNECT[= |
OK |
*Defined values1**
Notes
*1: If
Examples
Release connection +DISCONNECT
Description
This command used to disconnect the active connection
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+DISCONNECT | OK |
Defined values
None
Examples
HFP Commands
Answer an incoming call +ANSWER
Description
- Answer an incoming call
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+ANSWER | OK |
Defined values
- None
Examples
Reject/Terminate a call +CHUP
Description
- This command rejects an incoming call or terminates an ongoing call process
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+CHUP | OK |
Defined values
- None
Examples
Place a call with the phone number +DIAL
Description
- This command initiates outgoing voice calls by providing the destination phone number to the AG.
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+DIAL= |
OK |
Defined values
“0…9, *, #, +, -“ Dialing digits
Result codes
- OK If the value is valid
- ERROR If the value is not recognized or not supported
Examples
Last number re-dial +BLDN
Description
- This command initiates outgoing voice calls by recalling the last number dialed by the AG.
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+BLDN | OK |
Defined values
- None
Result codes
- OK If the value is valid
- ERROR If the value is not recognized or not supported
- NO CARRIER If network service is not available
Examples
Volume gain SCO +VGM
Description
Adjust the speaker volume level of the SNK device via SCO
Syntax
| Command *1 | Possible Response(s) |
|---|---|
| AT+VGM= |
OK |
| AT+VGM? | +VGM: |
| AT+VGM=? | +VGM: (range of supported |
Defined values
- 0 to 15 Decimal integers indicating the speaker gain
- + Volume up
- – Volume down
Notes
- 1: can only adjust the volume during a call.
Examples.
Configuration Commands
I2S internal settings +SETI2S
Description
- Change the settings of I2S used internally
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+SETI2S= |
OK |
Notes
- 1: Changes to this value should be rebooted to take effect.
Examples
UART configuration +UART
Description
Change baud rate, parity, and stop bits of UART in run-time
Syntax
| Command | Possible Response(s) |
|---|---|
| AT+UART= |
OK |
| AT+UART? | +UART: |
| AT+UART=? | +UART: (list of supported |
of supported
Examples
Information text and result codes
An information text is a string message provided by the DCE. It can be output at any time to inform the DTE of a specific event or status change.
| URC | Description |
|---|---|
| POWER OFF | The DCE is powered off |
| CONNECTABLE | The DCE is connectable |
| PAIRING | The DCE is discoverable |
| PAIR FAILED | Pairing is failed or timed-out |
| CONNECT FAIL | Connection failed |
+CONNECTED:
| Connected
n Parameters
n Example
CONNECTED: AABBCCDDEEFF
+DISCONNECTED:
| Disconnected
n Parameters
n Example
DISCONNECTED: AABBCCDDEEFF
APPENDICES
APPENDIX A: LED Pattern
| Status | LED Num | Working |
|---|---|---|
| Pairing | 0 | blink interval 0.2s |
n 0.1s ON, 0.1s OFF, ⋯ Repeated
Connected| 0| blink interval 1s
n 0.1s ON, 0.9s OFF, ⋯ Repeated
IDLE| 0| blink interval 2s
n 0.1s ON, 1.9s OFF, ⋯ Repeated
Streaming| 1| blink-blink interval 2s
n 0.05s ON, 0.05s OFF, 0.05s ON, 1.85s OFF, ⋯ Repeated
Call incoming| 0, 1| blink-blink interval 1s
n 0.05s ON, 0.05s OFF, 0.05s ON, 0.85s OFF, ⋯ Repeated
Calling| 1| blink-blink interval 2s
n 0.05s ON, 0.05s OFF, 0.05s ON, 1.85s OFF, ⋯ Repeated
APPENDIX B: ISSUES
List all unresolved issues, TBDs, pending decisions, findings required,
conflicts, etc.
ISSUES
ID| DESCRIPTION| PARTY RESPONSIBLE
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
FCC MODULAR APPROVAL INFORMATION EXAMPLES for Manual
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
- This device may not cause harmful interference.
- This device must accept any interference received, including interference that may cause undesired operation.
CAUTION: Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.
NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, under Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates uses and can radiate radio frequency energy and, if not installed and used by the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and the receiver.
- Connect the equipment to an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.
FCC Radiation Exposure Statement
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with a minimum distance of 20 cm between the radiator & your body.
OEM INTEGRATION INSTRUCTIONS:
This device is intended only for OEM integrators under the following
conditions: The module must be installed in the host equipment such that 20 cm
is maintained between the antenna and users, and the transmitter module may
not be co‐located with any other transmitter or antenna. The module shall be
only used with the internal on‐board antenna that has been originally tested
and certified with this module. External antennas are not supported. As long
as these 3 conditions above are met, further transmitter tests will not be
required. However, the OEM integrator is still responsible for testing their
end‐product for any additional compliance requirements required with this
module installed (for example, digital device emissions, PC peripheral
requirements, etc.). The end product may need Verification testing,
Declaration of Conformity testing, a Permissive Class II Change, or new
Certification. Please involve an FCC certification specialist to determine
what will be exactly applicable to the end product.
Validity of using the module certification:
If these conditions cannot be met (for example certain laptop configurations
or colocation with another transmitter), then the FCC authorization for this
module in combination with the host equipment is no longer considered valid
and the FCC ID of the module cannot be used on the final product. In these
circumstances, the OEM integrator will be responsible for re‐evaluating the
end product (including the transmitter) and obtaining a separate FCC
authorization. In such cases, please involve an FCC certification specialist
to determine if a Permissive Class II Change or new Certification is required.
Upgrade Firmware:
The software provided for firmware upgrade will not be capable of affecting
any RF parameters as certified for the FCC for this module, to prevent
compliance issues.
End product labeling:
This transmitter module is authorized only for use in devices where the
antenna may be installed such that 20 cm may be maintained between the antenna
and users. The end product must be labeled in avisiblea reaw withtheo
followinthe g: “C contains CCID: 2A PDI‐BCM‐LA100‐AS”.
Information that must be placed in the end user manual:
The OEM integrator has to be aware not to provide information to the end user
regarding how to install or remove this RF module in the user’s manual of the
end product that integrates this module. The end user manual shall include all
required regulatory information/warnings as shown in this manual.
RSS-GEN Section
This device complies with Industry Canada license-exempt RSS standard(s).
Operation is subject to the following two conditions: (1) this device may not
cause interference, and (2) this device must accept any interference,
including interference that may cause undesired operation of the device.
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>