How to know which Pheripheral typev is connected in BLE_GAP_EVT_CONNECTED event Manage two different peripheral type on one central //

RE: How to know which Pheripheral typev is connected in BLE_GAP_EVT_CONNECTED event Manage two different peripheral type on one central //

run_ar — Wed, 21 Nov 2018 13:35:43 GMT

1. Have you done any pairing or similar? any chance you could have a whitelist?

2. I would recommend scanning first, then connect. Regardless you should check the information in the struct returned by the connected event. And the struct returned by the scan function ble_gap_evt_adv_t to see what options you have to identify the devices.

RE: How to know which Pheripheral typev is connected in BLE_GAP_EVT_CONNECTED event Manage two different peripheral type on one central //

Stephane — Thu, 15 Nov 2018 14:29:53 GMT

Hi,

Question 1. I use what is define by nordic :

For peripheral, in BLE_NUS.C (line 64) :

#define NUS_BASE_UUID {{0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x00, 0x00, 0x40, 0x6E}} /**< Used vendor specific UUID. */

For Central, in ble_nus_c.h (line 101)

#define NUS_BASE_UUID {{0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x00, 0x00, 0x40, 0x6E}} /**< Used vendor specific UUID. */

A other idea ?

Question 2 :

No I don't scan for a device first. One type of device or the other could be power supply first!!

if I use the sd_ble_gap_connect() fonction to scan :

- this fonction is not call today in the main

- I have to replace the scan_start() with this function ?

- you speak about the 'addresse of the device' : How can I know the address?

In the ble_evt_handler() called with the event BLE_GAP_EVT_CONNECTED, the only information to know the device is also the peer_addr.addr ?

Thanks in advance

Stephane

RE: How to know which Pheripheral typev is connected in BLE_GAP_EVT_CONNECTED event Manage two different peripheral type on one central //

run_ar — Thu, 15 Nov 2018 12:23:53 GMT

1. Are you sure the filter matches the UUID advertised by the peripheral?

2. I assume you scan for a device first. Then you call sd_ble_gap_connect and provide the address of the device you want to connect to. So at this stage you have already decided which device you should connect to. And you can check this address against the address returned in the BLE_GAP_EVT_CONNECTED event. You can also do a service discovery to see what services the device has. and also check the adv data returned in the connected event.