Communication between master and slave

RE: Communication between master and slave

Petter Myhre — Tue, 21 Nov 2017 19:09:36 GMT

Then the master will look at the device name in the advertisement from the slave, recognize it, and send a connection request to it. Yes, you need to make changes, as I said currently it looks for the NUS UUID, not a device name. See how BLE_GAP_EVT_ADV_REPORT is handled inside on_ble_evt().

RE: Communication between master and slave

pavan — Tue, 21 Nov 2017 15:03:28 GMT

Hi thanks for the information. well lets say if change the Device name of the slave then how will Master detects the particular slave and connect it. do i need to make any changes in the master program?

How and where to change in master program? . like if master detects particular name the only pair otherwise dont connect how to configure that?

RE: Communication between master and slave

Petter Myhre — Tue, 21 Nov 2017 11:25:57 GMT

The unmodified central example will not connect to the nearest peripheral, it will try to connect to the device that sent out the first advertisement it received.

If you want M1 to only connect to S1 you need to configure M1 (and S1) so that it can recognize S1 advertisement. Unmodified the example only looks for the NUS UUID in the advertisement. See how BLE_GAP_EVT_ADV_REPORT is handled inside on_ble_evt(). The Bluetooth address of the slave is one way of doing it. Or use different UUIDs. Or add a device name, or some manufacturer specific data.