Hello Nordic team,
I'm having some trouble with discovering the characteristics of a custom device.
The peripheral device has a private service with UUID 06000002-0000-0000-0000-0000004E4553 and two characteristics with write enabled : 06000003-0000-0000-0000-0000004E4553 & 06000004-0000-0000-0000-0000004E4553.
I'm using the SDK nRF5 v15.3.0 on an nrf52840 DK as central.
I'm using the ble_app_interactive example.
When I'm requesting the characteristics from the peripheral device private service, it only finds one characteristic (the first added so first in the memory list ?).
Here is the CLI call and responses:
uart_cli:~$ scan on
Scan started
<info> app: Scanning
uart_cli:~$ connect 00:1E:C0:43:15:8B
<info> app: CENTRAL: Connecting...
Connected to address: 00 1E C0 43 15 8B
<info> app: CENTRAL: Connected, handle: 0.
Current MTU: 23
MTU changed successfully
<info> app: Data length updated to 27 bytes.
uart_cli:~$ gatt services 00:1E:C0:43:15:8B -> Here is somthing strange: I have to repeat gatt services twice to see the correct UUID in the list
<info> app: Services count: 3
Found service UUIDs:
UUID: 1800 type: 0x1
UUID: 1801 type: 0x1
UUID: 0 type: 0x2
uart_cli:~$ gatt services 00:1E:C0:43:15:8B
<info> app: Services count: 3
Found service UUIDs:
UUID: 1800 type: 0x1
UUID: 1801 type: 0x1
UUID: 2 type: 0x2
uart_cli:~$ gatt characteristics 00:1E:C0:43:15:8B 2
on_characteristics_discovery_rsp
Characteristic UUID: 3
Parameters:
broadcast: 0 read: 0 write_wo_resp: 0 write: 1 notify: 0
indicate: 0 auth_signed_wr: 0
Number of characteristics: 1
uart_cli:~$
Here is a screeshot from nrf connect for the exact same device:
I've created a similar Gatt server advertiser with the same UUIDs on nrf connect and when I request the characteristics with the smartphone as peripheral device here the 2 characteristics are retrieved correctly:
uart_cli:~$ connect 60:66:4B:0A:51:EC
<info> app: CENTRAL: Connecting...
Connected to address: 60 66 4B 0A 51 EC
<info> app: CENTRAL: Connected, handle: 0.
<info> app: Data length updated to 251 bytes.
Current MTU: 247
MTU changed successfully
uart_cli:~$
Connection parameters update success
Connection parameters update success
uart_cli:~$ gatt services 60:66:4B:0A:51:EC
<info> app: Services count: 5
Found service UUIDs:
UUID: 1801 type: 0x1
UUID: 1800 type: 0x1
UUID: FE35 type: 0x1
UUID: 46A type: 0x1
UUID: 2 type: 0x2
uart_cli:~$
uart_cli:~$
uart_cli:~$ gatt characteristics 60:66:4B:0A:51:EC 2
on_characteristics_discovery_rsp
Characteristic UUID: 3
Parameters:
broadcast: 0 read: 0 write_wo_resp: 0 write: 1 notify: 0
indicate: 0 auth_signed_wr: 0
Characteristic UUID: 4
Parameters:
broadcast: 0 read: 0 write_wo_resp: 0 write: 1 notify: 0
indicate: 0 auth_signed_wr: 0
Number of characteristics: 2
Here is the Gatt server configuration on nrf connect :
I will try to get a sniffer capture tomorrow, any idea why this could happen ?
Thanks in advance,
Best regards,
Aloïs KYROU