Show the "Received Bytes" on nrf52.

RE: Show the "Received Bytes" on nrf52.

Sigurd — Mon, 11 Sep 2017 07:36:48 GMT

The SoftDevice itself is the same, but the examples configures and uses the SoftDevice in different ways.

RE: Show the "Received Bytes" on nrf52.

MainOFF — Mon, 11 Sep 2017 04:15:22 GMT

Thanks for your information.I have a last question. Do have any differrent between SoftDevice of BLE_LED_Blinky example and SoftDevice of other example?

RE: Show the "Received Bytes" on nrf52.

Sigurd — Fri, 08 Sep 2017 08:48:00 GMT

For writable characteristics, the stack (SoftDevice) will automatically receive and store any writes to a database(inside the SoftDevice) for you. You will then receive an event that it happened, with a copy of the data. I.e. every time the state changes the led_write_handler() will be called, and you can read LED state from the led_state.

If you want to have a look at the value at a later point, you can use sd_ble_gatts_value_get() to fetch the current value.

RE: Show the "Received Bytes" on nrf52.

MainOFF — Thu, 07 Sep 2017 17:38:53 GMT

I was see that on terminal. But I want to know : which is the variable "hold" the value was recived.

RE: Show the "Received Bytes" on nrf52.

Sigurd — Thu, 07 Sep 2017 14:05:59 GMT

Hi,

Client board was send one ( or more) byte(s) to server board.

That is correct. The client(central) sets the LED characteristic on the serer(peripheral) to 1 to turn the LED on, and sets the value to 0 to turn the LED off. When this happens, the default-behaviour is that the UART prints the message "Received LED ON" and "Received LED OFF". So if you connect with e.g. termite terminal, you should see this printed on the terminal.