RAU6 Dokuwiki

User Tools

Site Tools

Trace: • Programming in Assembler Laboratory • Programming in Assembler Laboratory • Laboratory on GPIO use in Zephyr OS • Fan and Servo controlling • STM32 Control of built-in LEDs with PWM • Zephyr BLE peripheral • IoT Networks: Laboratory 3 - CoAP • Laboratory on the Internet of Things - Advanced IoT Hardware - on-site edition • Bluetooth Low Energy for STM32 - peripheral write • ESP32 BLE in Arduino. Part2: Setting-up BLE Server
No ACL setup yet! Denying access to everyone.
en:edu:zmitac:s2:aih:lab:nrf52zephyrblecentral

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:edu:zmitac:s2:aih:lab:nrf52zephyrblecentral [2023/12/19 22:24] – [BLE central] ktokarzen:edu:zmitac:s2:aih:lab:nrf52zephyrblecentral [2023/12/19 23:19] (current) – [Tasks to do during the laboratory] ktokarz
Line 3: Line 3:
 BLE client must be configured to connect to the peripheral which exposes some specific service and characteristic. To do the lab exercise there is a need to create the peripheral device first. BLE client must be configured to connect to the peripheral which exposes some specific service and characteristic. To do the lab exercise there is a need to create the peripheral device first.
 ===== BLE Health Temperature peripheral ===== ===== BLE Health Temperature peripheral =====
-The default Health Temperature example is sufficient to make the laboratory. How to import the project, flash, and execute is shown in {{en:edu:zmitac:s2:aih:lab:nrf52zephyrbleperipheral}}.+The default Health Temperature example is sufficient to make the laboratory. How to import the project, flash, and execute is shown in {{https://dokuwiki.zmitac.aei.polsl.pl/en:edu:zmitac:s2:aih:lab:nrf52zephyrbleperipheral|peripheral example}}.
 ===== BLE central ==== ===== BLE central ====
 Among the examples provided with Zephyr OS, there is also one complementary to the Health Temperature peripheral. It is named central_ht ((..\.platformio\packages\framework-zephyr\samples\bluetooth\central_ht)). The program is quite complex, here we will explain the most important elements and the process of establishing the connection.\\ Among the examples provided with Zephyr OS, there is also one complementary to the Health Temperature peripheral. It is named central_ht ((..\.platformio\packages\framework-zephyr\samples\bluetooth\central_ht)). The program is quite complex, here we will explain the most important elements and the process of establishing the connection.\\
Line 22: Line 22:
 ... ...
 </code> </code>
-==== Scanning the neighbourhood ==== +The "scan_start()" function calls "bt_le_scan_start(&scan_param, device_found)" function. The second parameter is the callback function which processes scan results.  
-The "scan_start()" function calls "bt_le_scan_start(&scan_param, device_found)" function. The second parameter is the callback function which processes scan results. The "device_found()" function parses received advertising data with the "bt_data_parse()" function to the function "eir_found()". The latter function searches advertising data for the UUID of the Health Thermometer (0x1809) and after a successful search establishes a connection with the remote device by calling the function "bt_conn_le_create()".\\+==== Searching advertising data for info on service ==== 
 +The "device_found()" function parses received advertising data with the "bt_data_parse()" function to the function "eir_found()". The latter function searches advertising data for the UUID of the Health Thermometer (0x1809).  
 +==== Establishing the connection ==== 
 +After a successful search establishes a connection with the remote device by calling the function "bt_conn_le_create()".\\
 Further processing is done by callback functions registered by the macro: Further processing is done by callback functions registered by the macro:
 <code> <code>
Line 32: Line 35:
 </code> </code>
 Zephyr OS keeps the "bt_conn_cb" structure that allows the programmer to attach callback functions to chosen events. "BT_CONN_CB_DEFINE" macro attaches "connected" and "disconnected" functions to appropriate events. Zephyr OS keeps the "bt_conn_cb" structure that allows the programmer to attach callback functions to chosen events. "BT_CONN_CB_DEFINE" macro attaches "connected" and "disconnected" functions to appropriate events.
-The "connected()" function is executed after successfully establishing the connection to the peripheral device. This function registers the callback function "discover_func()", and starts the discovery process by searching for the Health Thermometer service (UUID = 0x1809).  +The "connected()" function is executed after successfully establishing the connection to the peripheral device.  
-After finding this service discovery_func() is executed which performs further searching. First, it looks for the Temperature Measurement characteristic (UUID = 0x2a1c). This characteristic should have the descriptor Client Characteristic Configuration (UUID = 0x1902) which makes it possible to enable notifications or indications. The indication enabling and registering the "notify_func()" as the callback for incoming indications finishes the establishing connection process.\\+==== Discovering the service ==== 
 +This function registers the callback function "discover_func()", and starts the discovery process by searching for the Health Thermometer service (UUID = 0x1809).  
 +==== Searching for the characteristic ==== 
 +After finding this service discovery_func() is executed which performs further searching. First, it looks for the Temperature Measurement characteristic (UUID = 0x2a1c).  
 +==== Subscribing to the data with indication ==== 
 +This characteristic should have the descriptor Client Characteristic Configuration (UUID = 0x1902) which makes it possible to enable notifications or indications. The indication enabling and registering the "notify_func()" as the callback for incoming indications finishes the establishing connection process.\\ 
 +==== Ready! ====
 Notice that after every successful discovery the function "discovery_func()" is called as the callback.\\ Notice that after every successful discovery the function "discovery_func()" is called as the callback.\\
 While the peripheral device updates the thermometer sensor reading, our central device receives this data and calls the "notify_func()" callback which prints the data using the UART port. While the peripheral device updates the thermometer sensor reading, our central device receives this data and calls the "notify_func()" callback which prints the data using the UART port.
 +===== Tasks to do during the laboratory =====
 +  - Create the Health Thermometer peripheral device and test if it operates properly
 +  - Import central device program "central_ht" (main.c and prj.conf files must be imported)
 +  - Compile and execute it observing its behaviour with and without peripheral running
 +  - Modify the peripheral code and central code to enable LED control on the central board with a button press on the peripheral board
  
 +<note>
 +If you find problems with undefined BT_ATT_FIRST_ATTRIBUTE_HANDLE and BT_ATT_LAST_ATTRIBUTE_HANDLE define them as in the following code.
 +</note>
 +<code>
 +#define BT_ATT_FIRST_ATTRIBUTE_HANDLE 0x0001
 +#define BT_ATT_LAST_ATTRIBUTE_HANDLE 0xFFFF
 +</code>
 +<note>
 +To send simple binary data you can use a binary sensor service (UUID = 0x183B) with a binary sensor response characteristic (UUID = 0x2B2C).
 +</note>
en/edu/zmitac/s2/aih/lab/nrf52zephyrblecentral.1703021053.txt.gz · Last modified: by ktokarz