Read BLE received data when being a peripheral ?

[Nour_l]

hello everyone ,

Well first I have to mention that I'm at a the very starting stages in using this great DK and I went throw some tutorials ... Well , I have some questions that might seem stupid so please forgive that fact , my question is how to read received data from when the nRF51 422 being a peripheral ? I actually also would like to know something else , I've spent quite time trying to follow the the heart rate example and at some point I guess that the data was encrypted before being sent so my second stupid question is how is the data supposed to be dealt with when received by an application ? thank you for your attention

[FormerMember]

First, it may be useful to take a look at the Heart Rate example documentation in the SDK.

What do you mean by "how is the data supposed to be dealt with when received by an application", if it is the central side you refer to, it depends on the application: a heart rate monitor would for example show the current heart rate on a screen.

The example ble_app_hrs_c shows how the central side for a heart rate link can be implemented. The documentation for that example can be found here.

[Pavan kumar]

"how to read received data from when the nRF51 422 being a peripheral" Generally the central will writes to peripheral through characteristics So the data is in characteristic what all you need to do is copy that data to your local buffers. I suggest you to check on_write() function in the standard ble_nus.c. It may give you better idea

[Nour_l]

Hi , well to be honest I actually run through the Heart Rate example and I found it a bit of a hard example to be start with but I'll keep on trying as you suggested , the thing is I'm a member of team developing a security system as a school project we are dealing with bluetooth communication using nRF51422 and I'm finding a hard time proceeding with that specialy with being kind of a beginner in this field

[Nour_l]

Hi , thanks for responding , well right now I'm having a look over the standard you suggested ... right now I'm wondering .. having more than one service provided by the DK how could the client recognize to which service the data belong and whether could a prephiral be a server and a client at the same time

[FormerMember]

Yes, the examples can seem fairly complex in the beginning.

It helps a lot to have some knowledge on how BLE works. To get an overview, you can take a look at this book.

Encrypted links are obtained with bonding or pairing. The peer manager module in the SDK handles the bonding/pairing process. The message sequence charts for bonding and pairing can be found here.