When to use DK Buttons and LEDs versus CAF Led Module?

[nRF5xFanboy]

Hello Reader,

I noticed two almost similar modules "DK buttons and LEDs" library and the "CAF LED & Button" library (or module).

What is the difference between DK buttons and LEDs module and the CAF LED & Button modules

Is there conceptually or design wise any specific case to use either as preferred one?

Best regards,
     nRF5xFanBoy

[Øivind]

Hi,

DK buttons and LEDs is a much simpler module overall. Why you might want to use CAF instead is explained in the CAF overview: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/caf/caf_overview.html

If you have any questions regarding the CAF description, feel free to ask!

[nRF5xFanboy]

Hi Oivind,

The documentation lacks the answer on my question:
Is there conceptually or design wise any specific use-case (or situation) to use either as preferred solution?

Best regards,
     nRF5XFanBoy

[Øivind]

One of the biggest advantages of CAF is when your application is using multiple CAF modules, and modules need to react to events from other modules. CAF tries to simplify and provide a common architecture for this communication. CAF implements the Application Event Manager for this purpose, so it's documentation may also be insightful:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/others/app_event_manager.html

There is no "correct" answer, and you may prefer to use DK buttons and LEDs instead, or another solution entirely.

[nRF5xFanboy]

Thanks Øivind,

I agree "no correct answer."

It's about the intended design in mind when these modules where created.
Unfortunately the intended design of both modules is not written clearly nor completely in the module documentation.

I think this is something to improve when it come to wring documentation.
This would definitely help the reader in analyze & designing her/his application.
There is a always a brainstorming & choice picking moment selecting the candidate libraries in some overview and picking the best solution for the problem.

So yes the CAF is even-driven  
So the DK buttons and leds are more simple (read: not event-driven)
but what other differences are there .... 
- which library is faster (e.g. latency?)
- which library is drains the batter? 
- which uses interrupt?
- which is thread safe?
- which is lock free?

Just some design question the documentation does not answer ....

Yeah for now I stick with the CAF implementation in my aplication and build a few new CAF libraries myself.

best regards,
     nRF5xFanBoy

[nRF5xFanboy]

I feel OK if you close this ticket