When I connect to a PB-02 via UART(8data bits, no parity, 1 stop bit) it does not execute all AT commands. These work fine:

  1. AT\r\n results in AT\r\n\nOK\r\n
  2. AT+RST\r\n results in :
    all driver init\n
    MAC:94 C9 60 88 DC DB\n
    firmware_version:release/V1008 \r\n
    compile_time:Sep  3 2021 15:41:57\n\r\n
  3. ATE0 and ATE1 work as expected...
  4. It also dumps messages like CON OK\r\n and DISCONNECT OK\r\n, when I connect with a Test App...


  1. AT+NAME?\r\n and AT+NAME=WhiteTulip\r\n do not work. There is just the echo. But no OK and no name change.

Why is that?

How can I change its name and add parity bits, without flashing new firmware?

  • \$\begingroup\$ To help get an answer, can you edit the question and include a link to the documentation for the PB-02. I'm guessing it is some sort of modem. \$\endgroup\$ Feb 11 at 14:16
  • \$\begingroup\$ They call it "bluetooth module". On the UART side it speaks "AT". And on the airside it speaks Bluetooth BLE 5.0. But: The PDF "PB-01/02 Tmall Genie docking at instruction set" and the PDF "PB-01/02 Bluetooth passthrough (non mesh) at instruction set" describes AT commands, that the PB-02 does not understand. \$\endgroup\$
    Feb 11 at 14:35
  • \$\begingroup\$ Using google translate to convert the documentation from Chinese (Simplified) to English, I can't see any error in the AT commands you are using for AT+NAME? and AT+NAME=WhiteTulip. The translated document does say Changing the Bluetooth device name requires restarting to take effect. The maximum length is 20 bytes.. Have you tried restarting the PB-02 after attempting to change the name? \$\endgroup\$ Feb 11 at 14:44
  • \$\begingroup\$ @ChesterGillon it does not even reply "OK", although that PDF says, it should do. I just did that AT+NAME=WhiteTulip and then a power cycle, but it still says its name is "ai-Thinker"... \$\endgroup\$
    Feb 11 at 15:03
  • \$\begingroup\$ Given the firmware doesn't reply to the AT+NAME, you might have to contact Ai-Thinker Technology support to ask why the firmware doesn't even reply "OK". \$\endgroup\$ Feb 11 at 15:14

1 Answer 1


I found this PDF via Google. It says that it is "BLENAME" in v1.1.3.


AT+BLENAME=White Tulip<0D>


But: AT+UARTCFG? says just +UARTCFG:115200 (no parity configurable). So I seem to have a special version v1.1.3. So I will use 32bit CRC every few bytes. That should be even better than parity (which is 1bit CRC, IIRC).


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.