Is it necessary to define a custom service application instead of relying on the softdevice?

[Luke.L]

Hi,

    I have successfully implement the code demonstrated in the two tutorials shown here:

https://devzone.nordicsemi.com/tutorials/b/bluetooth-low-energy/posts/ble-characteristics-a-beginners-tutorial

https://github.com/bjornspockeli/custom_ble_service_example

Now I am wondering, what are the differences or benefits to creating custom service handling at application level as shown in the bjorn's tutorial?

Thanks

[Bjørn Kvaale]

May I ask how else you would want to handle the custom service events otherwise? How do you plan on handling events from the softdevice otherwise? One of the benefits of using an event handler is that it is easy to see how events coming from the softdevice are handled by the event handler.

[Luke.L]

Thanks for replying, well those 2 examples are pretty basic, and they both appear to accomplish the same thing, capturing read/write values/setting notifications which serves my needs, is there something I am missing here?

[Bjørn Kvaale]

Nope, don't think you're missing anything. I agree with your conclusion.

[Luke.L]

Thanks for the reply once again! So beyond the point I mentioned, are there any real world use cases where I should build a custom events handler?

[Bjørn Kvaale]

If you write to a characteristic from a smartphone, you may want the generated event to be sent to a custom event handler, which will then respond to the event. For example, when writing to a characteristic on the smartphone side, you may want the DK to blink a LED.

[Luke.L]

Ah thank you so much. Now I understand.