Is possible to put S110 in observer role (as peripheral) , waiting for a specific advertising (or waiting for an active scanning) and then switch to advertiser role (always as peripheral) ?
Thank all.
Update : Nordic has released S130 softdevice.
Is possible to put S110 in observer role (as peripheral) , waiting for a specific advertising (or waiting for an active scanning) and then switch to advertiser role (always as peripheral) ?
Thank all.
Update : Nordic has released S130 softdevice.
If the aim is to connect to a specific Central device, with which you have already bonded, you should look into whitelisting. This is the exact functionality this offers. For an example of how this can be implemented, I'd recommend you to take a look on the ble_app_proximity. It uses a bond manager API function to get a whitelist, which it then uses when advertising.
The S110 can do the Peripheral and Broadcaster roles only, and can not behave as an Observer. Also, an Observer would not normally be able to see other Central devices, so I'm not sure how useful that would have been.
If you have two devices, both capable of switching roles, you might be able to get this working, but then again, I'm having trouble understanding what you achieve by all this trouble, as it seems pretty excessive to me.
I'd absolutely looking into whitelisting and the addition of manufacturer specific data to solve this in some other way. Whitelisting will require that you either have been bonded with the other device, or that you know its Bluetooth address. Manufacturer specific data is data that you can add to your advertisement package, which the Central then can read for specific information about your peripheral. If you need further information on either of these, it might make most sense to post it as a separate question.
If you have two devices, both capable of switching roles, you might be able to get this working, but then again, I'm having trouble understanding what you achieve by all this trouble, as it seems pretty excessive to me.
I'd absolutely looking into whitelisting and the addition of manufacturer specific data to solve this in some other way. Whitelisting will require that you either have been bonded with the other device, or that you know its Bluetooth address. Manufacturer specific data is data that you can add to your advertisement package, which the Central then can read for specific information about your peripheral. If you need further information on either of these, it might make most sense to post it as a separate question.