About the characteristic "read" of BLE communication

RE: About the characteristic "read" of BLE communication

Andy — Tue, 14 May 2019 06:37:52 GMT

What problem?

RE: About the characteristic "read" of BLE communication

y001 — Tue, 14 May 2019 06:02:44 GMT

The problem was solved by calling the function in the main for loop.

RE: About the characteristic "read" of BLE communication

Andy — Wed, 08 May 2019 11:46:29 GMT

Well I'm not exactly sure which one is the "best" one, but you could start with the ble_peripheral/ble_app_hrs example.

RE: About the characteristic "read" of BLE communication

y001 — Wed, 08 May 2019 02:21:51 GMT

Thank you for the very easy-to-understand explanation.

I realized that I need to "subscribe" the value and receive notifications every second.

Which SDKsample would be the best reference for running this?

RE: About the characteristic "read" of BLE communication

Andy — Mon, 06 May 2019 08:56:10 GMT

There are two ways to send data from the peripheral to the central. Using notifications/indications or reads. If you want the phone to initiate the transfer, then you do a read. If you want the phone to always have the latest value, you "subscribe" to the characteristic and receive notifications every time the value changes.

It's totally up to you how you want to do this.

RE: About the characteristic "read" of BLE communication

y001 — Mon, 06 May 2019 08:25:16 GMT

Thank you for reply!

The relationship between central and peripheral seems to be understood.

This time, because you want to get the value from the peripheral, it is "read", right?

I want to send data from peripheral nRF52832 to Central Android.
This is the process of "read", right?

I want to know how to do this "read" process.
It will be helpful if there is an example that can be used as it is.

RE: About the characteristic "read" of BLE communication

Andy — Fri, 26 Apr 2019 08:35:35 GMT

There are two types of data transfers: transfers initiated by the central and transfers initiated by the peripheral.

Reads and writes are both central-initiated transfers. This means that the central either wants to update a value in the peripheral, or it wants to get a value from the peripheral.

There are two kinds of peripheral-initiated transfers: notifications and indications. These are used when the peripheral wants to let the central know that the value of a characteristic changed. At this point, just always use notifications. In my experience indications are quite useless (see this thread for more on this).