MultiLink communication through nus

RE: MultiLink communication through nus

Susheel Nuguru — Thu, 15 Nov 2018 11:07:49 GMT

in SDK15 in ble_db_discovery.c -> on_characteristic_discovery_rsp we see that when there are more chars than BLE_GATT_DB_MAX_CHARS discovered, then the rest are ignored but no error is being thrown. There is just a log warning in this case.

RE: MultiLink communication through nus

ReedLi — Thu, 15 Nov 2018 01:27:54 GMT

I read SDK V15 and find that in function ble_db_discovery_start()(SDK V12), it seems lack of this : memset(p_db_discovery, 0x00, sizeof(ble_db_discovery_t));

RE: MultiLink communication through nus

ReedLi — Wed, 14 Nov 2018 14:46:19 GMT

Hi, thanks for replying.

The peripherals advertise with special NAME, and central connects to the adv packets with the NAME. It's just a simple auto connection process.

I have some ideas about this problem, but i am not sure if it is right. I have read through the code of db_discovery and find ble_db_discovery_start() did't clear this member (ble_gatt_db_srv_t services[BLE_DB_DISCOVERY_MAX_SRV];) of the struct ble_db_discovery_t, so that the number of discovered services and characteristics increases with more connections.When maximum number of characteristic is greater than BLE_GATT_DB_MAX_CHARS, then something goes wrong.

RE: MultiLink communication through nus

Susheel Nuguru — Wed, 14 Nov 2018 13:26:33 GMT

[quote user=""]When peripheral receives message, it calls sd_ble_gap_disconnect(). [/quote]

Can you start your peripheral in debug mode and see why it is connecting?

With the information you gave here, it is pretty hard for any of us to decode the packets.