This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot-open:practical:hardware:sut:esp32:iot_10 [2024/04/01 18:14] – [Suggested Readings and Knowledge Resources] ktokarz | en:iot-open:practical:hardware:sut:esp32:iot_10 [2024/05/02 11:05] (current) – [IoT10: BLE Client] ktokarz | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | This scenario presents the Bluetooth Low Energy client device with a notification/ | + | This scenario presents the Bluetooth Low Energy client device with a notification/ |
| ===== Prerequisites ===== | ===== Prerequisites ===== | ||
| - | It is necessary to understand the principles of the Bluetooth Low Energy protocol with concepts of services, characteristics and descriptors. Notification and indication methods of data transmission should be known. We will use in this scenario the knowledge and the server device created in part 3. | + | It is necessary to understand the principles of the Bluetooth Low Energy protocol with concepts of services, characteristics and descriptors. Notification and indication methods of data transmission should be known. We will use in this scenario the knowledge and the server device created in IoT_9. |
| ===== Suggested Readings and Knowledge Resources ===== | ===== Suggested Readings and Knowledge Resources ===== | ||
| * [[en: | * [[en: | ||
| Line 22: | Line 22: | ||
| === Step 1 === | === Step 1 === | ||
| In this step, we will analyse the behaviour of the client. The client software is much more complex than the server. It is because the central device in many circumstances is a more powerful device than the peripheral. Some parts of the software are implemented as callback functions because they handle reactions on the data coming asynchronously from the server. The diagram presents the algorithm of the client and data coming from the server. | In this step, we will analyse the behaviour of the client. The client software is much more complex than the server. It is because the central device in many circumstances is a more powerful device than the peripheral. Some parts of the software are implemented as callback functions because they handle reactions on the data coming asynchronously from the server. The diagram presents the algorithm of the client and data coming from the server. | ||
| - | {{ en: | + | {{ en: |
| === Step 2 === | === Step 2 === | ||