# Function Command

#Command List

Num

Command

Function

1

AT+BLENAME (opens new window)

Query/Set Bluetooth LE device name.

2

AT+BLEADDR (opens new window)

Query the BLE public static address of the device, which is also the built-in MAC address of the device.

3

AT+BLESCANPARAM (opens new window)

Query/Set BLE scan parameter.

4

AT+BLESCAN (opens new window)

Enable/disable BLE scanning and provide advanced filtering parameters for scanning.

5

AT+BLEADVPARM (opens new window)

Query/Set Bluetooth LE Broadcast Parameters.

6

AT+BLEADVDATA (opens new window)

Query/Set Bluetooth LE Broadcast Data.

7

AT+BLEADVDATAEX (opens new window)

Automatically generate BLE broadcast packets based on configuration.

8

AT+BLEADVSTART (opens new window)

Start BLE Broadcast.

9

AT+BLEADVSTOP (opens new window)

Stop BE Broadcast.

10

AT+POWER (opens new window)

Query/Set Bluetooth Transmission Power.

11

AT+BLEDISCONN (opens new window)

Proactively disconnect from the current Central device.

12

AT+BLEGATTSNTFY (opens new window)

Send data to Central devices through the BLE Transparent service.

13

AT+BLEIOCAP (opens new window)

Set the IO interface capability of the BLE device.

14

AT+BLEPAIR (opens new window)

To enable the BLE binding pairing process.

15

AT+BLEPAIR_CANCEL (opens new window)

Cancel the currently in progress pairing process.

16

AT+BLEBONDS (opens new window)

Obtain the list of devices saved by the module that have completed pairing and binding.

17

AT+BLEFIXEDPASSKEY (opens new window)

Set/Query a fixed PASSKEY.

18

AT+BLEPASSKEY_CONFIRM (opens new window)

Confirm and reply to the received PASSKEY.

19

AT+BLEPASSKEY_INPUT (opens new window)

Enter PASSKEY during the authentication process.

#1. AT+BLENAME

Function：Query/Set Bluetooth LE device name.

Query Command：

AT+BLENAME?

Response：

+BLENAME:<"device_name">

OK

Parameter：

Please refer to set command parameter.

Set Command：

AT+BLENAME=<“device_name”>

Response：

OK

Parameter：

<device_ Name>: Bluetooth LE device name, maximum length: 32, default name is "XAT".

Description：

  • If AT+SYSSTORE=1, the configuration changes will be saved in the KV area.
  • The device name will be included in the GAP attribute.
  • The device name will also be included in the device's broadcast package, which defaults to scan response. And it can be set through the AT+BLEADVPARM command.
  • The device name format of the broadcast package is "device_name_XXXX", where XXXX is the lowest four bytes of the device MAC address.

Example:

AT+BLENAME="Hello"

OK

#2. AT+BLEADDR

Function：Query the BLE public static address of the device, which is also the built-in MAC address of the device.

Query Command：

AT+BLEADDR?

Response：

+BLEADDR:<"public_addr">

OK

Parameter

<public_addr>：BLE public static address is also the device's built-in MAC address. String format, separating each byte with:.

Demo:

AT+BLEADDR?
+BLEADDR:"D0:BA:E4:8F:07:E2"

OK

#3. AT+BLESCANPARAM

Function：Query/Set BLE scan parameter.

Query Command：

AT+BLESCANPARAM?

Response：

+BLESCANPARAM:<scan_type>, <filter>, <scan_interval>, <scan_window>,<timeout>

Parameter

Please refer to set command parameter.

Set Command：

AT+BLESCANPARAM=<scan_type>,[<filter>,<scan_interval>,<scan_window>,<timeout>]

Reponse：

OK

Parameter

  • <scan_ Type>: Scan type

    ○ 0: Passive scanning

    ○ 1: Active scanning will return scan response information

  • <filter>: Filter the scanning result information of the same address

    ○ 0: No filtering

    ○ 1: Enable filtering

  • <scan_ Interval>: Scan interval. This Parameter value should be greater than or equal to<scan_ Window>Parameter value. Parameter range: [0x0004,0x4000]. The scanning interval is the parameter multiplied by 0.625 milliseconds, so the actual scanning interval range is [2.510240] milliseconds.

  • <scan_ Window>: Scan the window. This Parameter value should be less than or equal to<scan_ Interval>Parameter value. Parameter range: [0x0004,0x4000]. The scanning window is multiplied by the parameter by 0.625 milliseconds, so the actual scanning window range is [2.510240] milliseconds.

  • <timeout>: Scan timeout time, in 10 milliseconds

    ○ 0: No timeout

    ○ Other: Automatically end scanning after timeout

Description:

  • The number of address filtering tables is 80. If more than 80 broadcast packets with different addresses have been found, more broadcast packets will not be filtered. Therefore, scanning should be stopped and restarted.

Demo:

//Passive scanning, same as MAC address filtering, 3 second timeout
AT+BLESCANPARAM=0,1,,,300

OK
AT+BLESCAN=1

OK
+BLESCAN:"E8:3F:EA:95:05:CC","random",-92,"ADV_NONCONN_IND","07FF4C0012020002"
+BLESCAN:"72:7B:61:DF:53:20","random",-92,"ADV_NONCONN_IND","1EFF060001092002E7187730AD7CA2896FF30E52B7FC2ED776902011EDEBC7"
+BLESCAN:"54:13:79:88:21:CA","public",-93,"ADV_SCAN_IND","1AFF4C00021550765CB7D9EA4E2199A4FA879613A492E35EE473CE"
+BLESCAN:"15:9E:E7:95:9F:3D","random",-56,"ADV_NONCONN_IND","02011A0BFF4C00090603DDC0A81FD9"
+BLESCAN:"1B:DC:54:87:E4:08","random",-91,"ADV_NONCONN_IND","02011A14FF4C0009060395C0A81FDF1307024A9A47CBDF98"
+BLESCAN:"17:CB:95:66:FF:E5","random",-63,"ADV_NONCONN_IND","02011A0BFF4C0009060318C0A81FC8"
+BLESCAN:"58:BA:28:C8:98:C8","random",-101,"ADV_IND","02011A020A0C0AFF4C001005101C3AE6B3"

#4. AT+BLESCAN

Enable/disable Bluetooth LE scanning and provide advanced filtering parameters for scanning.

Set Command：

AT+BLESCAN=<enable>[,<filter_type>,<"filter_param">]

Response：

OK

Parameter

  • <enable>: Turn on/off

    ○ 0: Stop scanning

    ○ 1: Start scanning

  • <filter_ Type>: Advanced filtering methods

    ○ 0: No filtering

    ○ 1: Enable address prefix based filtering

    ○ 2: Enable filtering based on device name prefix

  • <"filter_param">: used to filter strings

Event Response:

+BLESCAN:<"addr">,<"addr_type">,<rssi>,<"adv_type">,<"adv_data">

  • <"addr">: Device broadcast address, string, each byte separated by:

  • <"addr_type">: Device broadcast address type

    ○ "public": Public address

    ○ "random": random address

    ○ "public id": Resolveable public address

    ○ "random id": a parseable random address

  • <rssi>: Broadcast packet signal strength

  • <"adv_type">: Broadcast packet type

    ○ "ADV_IND": Ordinary broadcast package

    ○ "ADV_DIRECT_IND": Directional broadcast package

    ○ "ADV_SCAN_IND": Scannable broadcast package

    ○ "ADV-NONCONN_IND": Unconnectable broadcast

    ○ "SCAN_RSP": Scan response broadcast

    ○ "EXT_ADV": Extended Broadcast

  • <"adv_type">: Broadcast packet payload data, converting Hex into a string.

Description:

  • The number of advanced filtering tables is 20. If more than 20 matching broadcast packets have been found, more broadcast packets will not be filtered. Therefore, scanning should be stopped and restarted.

Demo:

// Start scanning and filter based on MAC address
AT+BLESCAN=1,1,"6C:4A:85"

OK
+BLESCAN:"6C:4A:85:0D:4C:BA","public",-65,"ADV_IND","02011A020A0C0AFF4C00100501146FB165"

// Set scanning parameters and use active scanning Because the device name is usually located in the Scan Response broadcast package
AT+BLESCANPARAM=1,1,,,300

OK
// Start scanning and filter based on device name
AT+BLESCAN=1,2,"SGUAI-S1X"

OK
+BLESCAN:"C3:0A:50:00:06:40","random",-106,"SCAN_RSP","0A0953475541492D533158"
+BLESCAN:"C3:0A:50:00:06:40","random",-106,"ADV_IND","02010609FFFFFF400600500AC31107B4A5C1D179EDC79CB17E5FF9D2830A50"

#5. AT+BLEADVPARM

Query/Set Bluetooth LE Broadcast Parameters.

Query Command：

AT+BLEADVPARM?

Response：

+BLESCANPARAM:<options>,<adv_int_min>,<adv_int_max>,<"peer_addr">,<"peer_addr_type">

OK

Parameter：

Please refer to set command parameter.

Set Command：

AT+BLEADVPARM=<options>[,<adv_int_min>,<adv_int_max>,<"peer_addr">,<"peer_addr_type">]

Response：

OK

Parameter：

  • <options>: Broadcast Parameter, BITMAP type data

    ○ BIT [0]: BT_ LE_ ADV_ OPT_ CONNECTABLE

    Connected broadcast, if it is an unconnected broadcast, the network type is determined by the data in Scan Response

    ○ BIT [1]: BT_ LE_ ADV_ OPT_ ONE_ TIME

    Is it a one-time broadcast? Once connected/disconnected, one-time broadcasts cannot automatically resume broadcasting. Need to use AT+BLEADVSTART to turn on

    ○ BIT [2]: BT_ LE_ ADV_ OPT_ USE_ Identity

    Whether to use the device's Identity Address in the broadcast package, which includes public and random addresses, is determined by the device's privacy settings

    ○ BIT [3]: BT_ LE_ ADV_ OPT_ USE_ NAME

    Whether to include the BLE GAP device name of the device, which is set by AT+BLENAME. The BLE GAP device name is placed in the Scan Response packet by default, unless:

    a. BT_ LE_ ADV_ OPT_ FORCE_ NAME_ IN_ AD setting

    b. BT_ LE_ ADV_ OPT_ EXT_ ADV set, but BT_ LE_ ADV_ OPT_ SCANNABLE is not set

    If there is not enough space in the broadcast package to store the device name, the name will be truncated and Shortened Name will be used as the broadcast field type.

    If the device name field in the broadcast package is manually set, this option will not work.

    ○ BIT [4]: BT_ LE_ ADV_ OPT_ DIR_ MODE_ LOW_ DUTY

    Low frequency broadcasting mode for directional broadcasting

    ○ BIT [5-8]: Currently not supported in AT commands

    ○ BIT [9]: BT_ LE_ ADV_ OPT_ SCANNABLE

    Even if Scan Response data is not provided, it can still be scanned. When it comes to BT_ LE_ ADV_ OPT_ EXT_ When used together with ADV, BT_ LE_ ADV_ OPT_ CONNECTABLE cannot be set and Scan Response data must be provided.

    ○ BIT [10]: BT_ LE_ ADV_ OPT_ EXT_ ADV

    Use extended broadcasting. In the extended broadcast mode, broadcast header information on three main broadcast channels and broadcast data on seven secondary broadcast channels. The connection is established in 2M PHY mode.

    ○ BIT [11]: BT_ LE_ ADV_ OPT_ NO_ 2M

    Without using 2M PHY mode, the connection will be established in 1M mode. If using BT_ LE_ ADV_ OPT_ CODED, then this flag cannot be set.

    ○ BIT [12]: BT_ LE_ ADV_ OPT_ CODED

    Establishing a connection using Coded PHY while also using BT_ LE_ ADV_ OPT_ EXT_ ADV

    ○ BIT [13]: BT_ LE_ ADV_ OPT_ ANONYMOUS

    Anonymous broadcast without device address

    ○ BIT [14]: BT_ LE_ ADV_ OPT_ USE_ TX_ POWER

    The broadcast package contains device transmission power and requires the use of BT_ LE_ ADV_ OPT_ EXT_ ADV. If you need to add device transmission power to a regular broadcast, you need to use AT+BLEADVDATAEX to set it up

    ○ BIT [15]: BT_ LE_ ADV_ OPT_ DISABLE_ CHAN_ thirty-seven

    Close broadcast channel 37

    ○ BIT [16]: BT_ LE_ ADV_ OPT_ DISABLE_ CHAN_ thirty-eight

    Close broadcast channel 38

    ○ BIT [17]: BT_ LE_ ADV_ OPT_ DISABLE_ CHAN_ thirty-nine

    Close broadcast channel 39

    ○ BIT [18]: BT_ LE_ ADV_ OPT_ FORCE_ NAME_ IN_ AD

    Force the inclusion of device name fields in broadcast packets instead of scanning response packets

  • <ADV_ Int_ Min>: Minimum broadcast interval. Parameter range: [0x0020,0x4000]. The broadcast interval is equal to the parameter multiplied by 0.625 milliseconds, so the actual minimum broadcast interval range is [2020240] milliseconds. This Parameter value should be less than or equal to<adv_ Int_ Max>Parameter value.

  • <ADV_ Int_ Max>: Maximum broadcast interval. Parameter range: [0x0020,0x4000]. The broadcast interval is equal to the parameter multiplied by 0.625 milliseconds, so the actual maximum broadcast interval range is [2020240] milliseconds. This Parameter value should be greater than or equal to<adv_ Int_ Min>Parameter value.

  • <"peer_addr">: The target address and string in the directed broadcast packet. Each byte is separated by:.

  • <"peer_addr_type">: The target address type in the directed broadcast packet

    ○ "public": Public address

    ○ "random": random address

    ○ "public id": Resolveable public address

    ○ "random id": a parseable random address

Description：

  • If AT+SYSSTORE=1, the configuration changes will be saved in the KV area.

#6. AT+BLEADVDATA

Function：Query/Set Bluetooth LE Broadcast Data.

Query Command：

AT+BLEADVDATA?

Response：

+BLEADVDATA:<"adv_data">,<"scan_rsp_data">

OK

Parameter：

Please refer to set command parameter.

Set Command：

AT+BLEADVDATA=<"adv_data">[,<"scan_rsp_data">]

Response：

OK

Parameter：
  • <ADV_ Data>: The data in the active broadcast packet should comply with the Bluetooth core specification, which is 1 byte Type+1 Byte Length+N bytes Data. Represents hexadecimal data as a string.
  • <scan_ RSP_ Data>: The data in the broadcast packet scanned and replied should also comply with the Bluetooth core specifications.

Description：

  • If AT+SYSSTORE=1, configuration changes will be saved in the KV area.
  • The response to the query command does not include broadcast data automatically added by the system, such as device name, transmission power, etc.

Demo：

AT+BLEADVDATA?
+BLEADVDATA:"020106030300FE06FF22090007E2"

#7. AT+BLEADVDATAEX

Function：Automatically generate BLE broadcast packets based on configuration.

Set Command：

AT+BLEADVDATAEX=[<"manufacture_data">,<include_power>,<"UUID16s/UUID128">,<"UUID16_DATA">]"

Response：

OK

Parameter：

  • <manufacturing_ Data>: The hexadecimal data stored in the 0xFF (BT-DATA-MANUFACTURER_DATA) field, represented as a string.

  • <include_ Power>: Read the current transmission power and save it in the 0x0A (BT-DATA_TX_POWER) field of the broadcast packet. Each time the broadcast is restarted, the current transmission power will be re read.

  • <UUID16s/UUID128>: Supports the following two types of UUID

    ○ One or more 16 bit UUIIDs, stored in the 0x03 (BT-DATA_UUID16_ALL) field, represented as a string of large hexadecimal UUIDs, for example: "FFF0" represents one 16 bit UUID or "FFF0FFF1" represents two 16 bit UUIDs

    ○ A 128 bit UUID, stored in the 0x07 (BT-DATA_UUID128_ALL) field, represented as a string for the large hexadecimal UUID. Example: "6E400001-B5A3-F393-E0A9-E50E24DCCA9E"

  • <UUID16_ DATA>: The data stored in the 0x16 (BT-DATA_SVC-DATA16) field is hexadecimal data represented as a string.

Description：

  • If AT+SYSSTORE=1, new broadcast data will be generated and changes will be saved in the KV area.
  • It will overwrite the custom broadcast data set using the AT+BLEADVDATA command.

Demo：

AT+BLEADVDATAEX="010203",0,"FFF0FFF1","1234"

OK
AT+BLEADVDATA?
+BLEADVDATA:"04FF0102030503F0FFF1FF03161234"

OK

#8. AT+BLEADVSTART

Funciton: Start BLE Broadcast.

Excecute Command：

AT+BLEADVSTART

Response：

OK

Description:

  • Broadcast based on saved broadcast data and broadcast parameter settings.
  • If the broadcast parameters or data have been modified, the broadcast should be restarted to take effect.
  • The default broadcast parameter, please refer to the work mode switching content on this page.

#9. AT+BLEADVSTOP

Function： Stop BE Broadcast.

Excecute Command：

AT+BLEADVSTART

Response：

OK

#10. AT+POWER

Function: Query/Set Bluetooth Transmission Power.

Query Command：

AT+POWER?

Response：

+POWER:<power>

OK

Parameter：

Please refer to set command parameter.

Set Command：

AT+POWER=<power>

Response：

OK

Parameter：

<power>: Emission power, signed integer, in dBm. Value range: -127~127. The specific settable power varies depending on different hardware platforms.

#11. AT+BLEDISCONN

Proactively disconnect from the current Central device.

Execute Command：

AT+BLEDISCONN

Response：

OK

Demo:

+BLECONN//Connection success message
AT+BLEDISCONN//Device actively disconnects

OK
+BLEDISCONN//Connection disconnect message

#12. AT+BLEGATTSNTFY

Send data to Central devices through the BLE Transparent service.

Execute Command：

AT+BLEGATTSNTFY

Response：

OK

>

Description:

Receive data from the serial interface, and send the received data to the Central device through the Data Out feature of the Transparent service. The method of receiving data adopts the packaging method in the transparent transmission working mode, which includes two methods: "maximum data length packaging" and "no data received within a certain period of time packaging". This working mode will continue until:

  • Normal exit: When the serial port receives three consecutive+characters, it exits the reception of serial port data and returns to the AT command mode.
  • Passive exit due to error: when sending data fails
  • Active exit due to errors: When it is detected that it cannot be sent, such as a connection disconnection event, CCCD's Notification flag being closed, etc

A series of event messages will be generated, which can be closed or opened using AT+SYSMSG:

When exiting the current mode, a+QUITT message will be sent.

Normal exit: will send+SEND_ OK message

  • Passive exit due to error: send+SEND_ ERROR message
  • Active exit due to error: send+SEND_ CANCELED message

Set Command：

AT+BLEGATTSNTFY=<length>

Response：

OK

>

Parameter：

<length>: Receives data of a specified length from the serial port and sends the data to the Bluetooth protocol stack, which is then sent to the Central device through the Data Out feature of the Transparent service.

Description:

Start receiving data of specified length from the serial port. And the received data will be sent to the Central device through the Data Out feature of the Transparent service, where only the "maximum data length packaging" in the transparent working mode is used, and the "no data received within a certain period of time packaging" is not used. This working mode will continue until:

  • Normal exit: The received data length reaches the data length specified by the AT+BLEGATSNTFY command
  • Passive exit due to error: when sending data fails
  • Active exit due to error: When it is detected that it cannot be sent to the protocol stack, such as a connection disconnection event, CCCD's Notification flag being closed, etc

A series of event messages will be generated, which can be closed or opened using AT+SYSMSG:

  • When exiting the current mode, a+QUITT message will be sent.
  • Normal exit: will send+SEND_ OK message
  • Passive exit due to error: send+SEND_ ERROR message
  • Active exit due to error: send+SEND_ CANCELED message

Tips:

When sending, it is necessary to ensure that the connection has been established and that the main device has opened the Notification flag of the device Data Out feature through CCCD. Otherwise, it will directly return ERROR

Demo:

Receive data of variable length from the serial port and send it to the Central device. Exit when receiving+++.

+BLECONN           //BLE Connection success message
+NOTIFY_ ENABLED   //Notification flag on message
AT+BLEGATTSNTFY

OK
>                  //Waiting for data to be received from the serial port

+QUITT             //Received+++, exit current mode
+SEND_ OK          //Sending successful message

Receive data of variable length from the serial port and send it to the Central device. But there was a disconnection event.

+BLECONN        	//BLE Connection success message
+NOTIFY_ENABLED		//Notification flag on message
AT+BLEGATTSNTFY

OK
>									//Waiting for data to be received from the serial port
+NOTIFY_DISABLED  //Notification flag clear event (triggered before the disconnection event occurs)
+SEND_CANCELED		//Cancle sending event
+BLEDISCONN				//Disconnection event

Receive 4 bytes of data from the serial port and send it to the Central device.

+BLECONN
+NOTIFY_ENABLED
AT+BLEGATTSNTFY=4

OK

+QUITT
+SEND_OK

#13. AT+BLEIOCAP

Function： Set the IO interface capability of the BLE device, and the protocol stack determines which authentication method to use during the pairing and binding process based on this capability.

Set Command：

AT+BLEIOCAP=<io>

Response：

OK

Parameter：

IO: The IO interface capability of BLE devices, supporting the following parameters:

<span class="ne-text">○ 0: ALL. Supports all capabilities.</span>

<span class="ne-text">○ 1: Input. Support the ability to input numbers through the keyboard to input PassKey.</span>

<span class="ne-text">○ 2: DISPLAY. Ability to display PassKey through display devices.</span>

<span class="ne-text">○ 3: DISPLAY_ YESNO. Not only can PassKey be displayed through the display screen, but it can also support the user's ability to input "confirm" or "reject" through the UI.</span>

<span class="ne-text">○ 4: CONFIRM. Support the ability for users to input "confirm" current binding requests through the UI.</span>

<span class="ne-text">○ 5: OOB. Support for out of band transmission of authentication information, i.e. through communication methods other than BLE.</span>

<span class="ne-text">○ 6: Status. No user interaction interface is supported, only the current pairing status can be displayed, such as pairing success or pairing failure. For example, using LED lights.</span>

<span class="ne-text">○ 7: NONE. Without any IO interface capability.</span>

Demo:

Set the device's ability to display the current paired password through the display device.

AT+BLEIOCAP=2  //Set IO capability

OK

+BLECONN       //Waiting BLE connection
AT+BLEPAIR=4   //Starting pairing according to security level 4

OK
+PASSKEY_DISPLAY:"F4:D4:88:7C:AC:7D (public)","575000" //The password generated by the module needs to be entered or confirmed by the user on another device (based on the capabilities of the other device)
+PAIR_COMPLETE:"F4:D4:88:7C:AC:7D (public)",1 //Pairing success event

#14. AT+BLEPAIR

To enable the BLE binding pairing process, it is necessary to ensure that the BLE connection has been established before calling, i.e. a +BLECONN event is generated.

Set Command：

AT+BLEPAIR=<sec_level: (1 - 4)>[,<force: (0: no, 1: force)>]

Response：

OK

Parameter：

  • sec_level：Encryption level

    ○ 0: Level 0, Only for BR/EDR special cases, like SDP。Note：BLE

    Module doesn't support.

    ○ 1: Level 1, No encryption and no authentication

    ○ 2: Level 2, Encryption and no authentication (no MITM).

    ○ 3: Level 3, Encryption and authentication (MITM)

    ○ 4: Level 4, Authenticated Secure Connections and 128-bit key.

  • force: Whether to force a re pairing.

    ○ 0: If it has already been paired before, do not force a new pairing

    ○ 1: Re pair and regenerate the relevant key, overwriting the previous pairing information

#15. AT+BLEPAIR_CANCEL

Cancel the currently in progress pairing process.

Execute Command：

AT+BLEPAIR_CANCEL

Response：

OK

#16. AT+BLEBONDS

Obtain the list of devices saved by the module that have completed pairing and binding.

Query Command：

AT+BLEBONDS？

Response：

+BLEBONDS:<"address">

OK

Parameter：
  • address：address of BLE device.

Clear the device information saved in the flash of the module that has completed pairing and binding.

Execute Command：

AT+BLEBONDS_CLEAR

Response：

OK

Parameter：

Demo:

AT+BLEBONDS？
+BLEBONDS:"F4:D4:88:7C:AC:7D (public)"

OK

#17. AT+BLEFIXEDPASSKEY

Set/Query a fixed PASSKEY for the following situations:

  • When generating a PASSKEY, the module no longer generates it randomly, but instead uses the fixed PASSKEY.
  • When a PASSKEY needs to be input, the module automatically enters the set fixed PASSKEY.

Set Command：

AT+BLEFIXEDPASSKEY=[<passkey: (0 - 999999)>]

Response：

OK

Parameter：

Passkey: Fixed PASSKEY, ranging from 0 to 999999. If an empty parameter is provided, the saved fixed PASSKEY in Flash is clear.

Query Command：

AT+BLEFIXEDPASSKEY？

Response：

+BLEFIXEDPASSKEY:<"NONE"|passkey>

Parameter：

Passkey: Fixed PASSKEY, ranging from 0 to 999999. If an empty parameter is provided, the saved fixed PASSKEY in Flash is clear.

#18. AT+BLEPASSKEY_CONFIRM

Confirm and reply to the received PASSKEY.

Execute Command：

AT+BLEPASSKEY_CONFIRM

Response：

OK

#19. AT+BLEPASSKEY_INPUT

Enter PASSKEY during the authentication process, and the protocol stack will verify whether the entered PASSKEY is correct to determine whether the authentication is successful.

Set Command：

AT+BLEPASSKEY_INPUT=<passkey: (0 - 999999)>

Response：

OK

_____________________________________________________________________________________________________________

End.

Last Updated: 11/29/2023, 1:52:34 PM

← EMB1082 AT Command →