|
|
||
|---|---|---|
| .. | ||
| advertiser | ||
| blecent | ||
| blecsc | ||
| blehci | ||
| blehr | ||
| blemesh | ||
| blemesh_light | ||
| blemesh_models_example_1 | ||
| blemesh_models_example_2 | ||
| blemesh_shell | ||
| bleprph | ||
| blestress | ||
| btshell | ||
| bttester | ||
| central | ||
| ext_advertiser | ||
| mesh_badge | ||
| peripheral | ||
| scanner | ||
| README.md | ||
Sample applications
advertiser
This is the simplest example of advertising. Application sets NRPA, configures advertisement parameters: general discoverable and not connectable and fills advertisement fields. Transmited data contains only flags, tx power level and device name, which fits in 31B limit of single package. With this data set, device advertises for 10 seconds, terminates advertisement and repeats process again infinitely.
scanner
This application shows how to perform simple scan. Device performs discovery procedure, during which receives advertising reports (if any devices are advertising nearby). These reports are being parsed and results are printed to serial port. Applicaton starts new discovery every second.
peripheral
Peripheral application is based on advertiser, but has added capability of connecting with other devices. As peripheral, device doesn't initiate any connection by itself; instead, advertises infinitely and accepts any connection request it receives. Because we cannot use any 16 or 32 bit UUIDs, as these are reserved by Bluetooth SIG, we are forced to use 128-bit one. Including such long UUID in advertising data consumes large part of available payload, so this data is split in advertising data and response data.
central
This application works in pair with peripheral. It's based on scanner application - the difference is, that if there was detected device with UUID fitting to the one predefined in central application, connection is initiated.