EC200U BLE not working as expected

Hi,
I have a EC200U which has a firmware version of EC200UCNAAR02A10M08.
I am trying to configure EC200UCNAA module as a BLE Server it worked as well for sometime but then suddenly. It started showing only Service UUID : 2774 and Characteristic UUID : 2A19 (Battery Level).

[2025-09-08 16:37:43:621_S:] AT+QBTPWR=0
[2025-09-08 16:37:43:674_R:] AT+QBTPWR=0
[2025-09-08 16:37:43:799_R:] OK
[2025-09-08 16:37:46:224_S:] AT+QBTPWR=1
[2025-09-08 16:37:46:277_R:] AT+QBTPWR=1
[2025-09-08 16:37:46:989_R:] OK
[2025-09-08 16:37:54:580_S:] AT+QBTGATADV=1,128,160,0,0,7,0
[2025-09-08 16:37:54:633_R:] AT+QBTGATADV=1,128,160,0,0,7,0
[2025-09-08 16:37:54:633_R:] OK
[2025-09-08 16:37:56:463_S:] AT+QBTADVSTR=63,1,“quec”,0,“06”,1,“quectel”,0,“0a”,0,“1803”,1,“bata”
[2025-09-08 16:37:56:518_R:] AT+QBTADVSTR=63,1,“quec”,0,“06”,1,“quectel”,0,“0a”,0,“1803”,1,“bata”
[2025-09-08 16:37:56:518_R:] OK
[2025-09-08 16:37:58:129_S:] AT+QBTGATSS=1,1,2759,1
[2025-09-08 16:37:58:183_R:] AT+QBTGATSS=1,1,2759,1
[2025-09-08 16:37:58:183_R:] OK
[2025-09-08 16:38:00:181_S:] AT+QBTGATSC=1,1,58,1,10766
[2025-09-08 16:38:00:234_R:] AT+QBTGATSC=1,1,58,1,10766
[2025-09-08 16:38:00:234_R:] OK
[2025-09-08 16:38:02:350_S:] AT+QBTGATSCV=1,1,3,1,10766,244,“1234”
[2025-09-08 16:38:02:405_R:] AT+QBTGATSCV=1,1,3,1,10766,244,“1234”
[2025-09-08 16:38:02:405_R:] OK
[2025-09-08 16:38:04:142_S:] AT+QBTGATSSC=1,1
[2025-09-08 16:38:04:194_R:] AT+QBTGATSSC=1,1
[2025-09-08 16:38:04:194_R:] OK
[2025-09-08 16:38:06:020_S:] AT+QBTADV=1
[2025-09-08 16:38:06:072_R:] AT+QBTADV=1
[2025-09-08 16:38:06:072_R:] OK

The data I received through this Battery Level UUID was the name set for using the command AT+QBTNAME = 0,“(name)”

I used nRF connect to check the BLE connection. Additionally I have used AT+QBTGATSSC=0 to clear all the services but still no use.

Do I have to do any reset for BLE? If yes, what is the appropriate command for that?

Hi,

You cleared the services with AT+QBTGATSSC=0, but this only resets the current configuration and leaves the module with the default Battery Level service. Therefore, you only see the Battery Level Service in nRF Connect.

You need to reset the BLE stack. To do this, use the following command:

AT+QBTRESET

(In some firmware, AT+CFUN=1,1, which is a complete reset of the module, has the same effect).

I can help you further when I’m available. :+1:

Hi @Navya_A ,

Have you tried resetting the BLE stack?

I examined your logs and I think there may be some mistakes. The log appears to use typographic quotes like “quectel”, “quec”, and “bata”. The AT parser expects ASCII double quotes (") on most hardware interfaces. Even if you see “OK” on the terminal screen, AD fields or GATT values ​​may be misspelled in the payload. Please use a plain ".

I think there’s an error with the UUID numbers (decimal/hex confusion).

Battery Service = 0x180F → decimal 6159
Battery Level = 0x2A19 → decimal 10777

AT+QBTGATSS=1,1,2759,1       // 2759 ≠ 0x180F (6159)
AT+QBTGATSC=1,1,58,1,10766   // 10766 ≠ 0x2A19 (10777)
AT+QBTGATSCV=1,1,3,1,10766,244,“1234”

Here, you wrote the service UUID as 2759 instead of 6159, and the characteristic as 10766 instead of 10777. That’s why, while you think you’re reading 0x2A19 in nRF Connect, you’re actually reading a different handle/UUID, and incorrect contents like “device name” are displayed (which also triggers the GATT cache/handle slip).

The AT+QBTGATSSC=1,1 command likely enables/starts service 1. Most FWs use AT+QBTGATSSC=0 (or equivalent) to “clear all services.” You didn’t clear this log; the previous faulty DB may have remained.


Hi @Emre_Karabek ,
AT+CFUN=1,1 is working but when I sent AT+QBTRESET it was invalid command line.
Regarding the characteristic UUIDs I just followed the manual example after which I changed to 128 bit UUID and it seems to be working fine. I have tried AT+QBTGATSSC=0 but that also did not work.

The 2A19 was advertising even after I use only 3 commands

AT+QBTPWR = 0
AT+QBTPWR = 1
AT+QBTADV = 1
Which was really confusing but it did reset when I sent AT+CFUN=1,1.

Thank you for the quick response