R1 code for micro:bit based train controller code, requires second micro:bit running rx code to operate - see https://meanderingpi.wordpress.com/ for more information

Fork of nrf51-sdk by Lancaster University

Embed: (wiki syntax)

« Back to documentation index

Service/Protocol Types

Service/Protocol Types
[Device Manager]

Describes the possible types of Service/Protocol Contexts for a bonded/peer device. More...

Describes the possible types of Service/Protocol Contexts for a bonded/peer device.

Possible Service/Protocol context per peer device. The Device Manager provides the functionality of persistently storing the Service/Protocol context and can automatically load them when needed. For example system attributes for a GATT Server. Based on the nature of the application, not all service types may be needed. The application can specify only the service/protocol context it wants to use at the time of registration.