Differences

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

--- en:edu:zmitac:s2:iotn:esp32ble2 [2024/03/31 17:16] – ktokarz
+++ en:edu:zmitac:s2:iotn:esp32ble2 [2024/04/09 08:58] (current) – [Prerequisites] ktokarz
@@ Line 3: / Line 3: @@
 ===== Prerequisites =====
-It is necessary to understand the principles of the Bluetooth Low Energy protocol with concepts of services, characteristics and descriptors. We will use in this scenario the knowledge of the advertising process so making the IoT_7 exercise is recommended.
+It is necessary to understand the principles of the Bluetooth Low Energy protocol with concepts of services, characteristics and descriptors. We will use in this scenario the knowledge of the advertising process so making the part 1 exercise is recommended.
 ===== Suggested Readings and Knowledge Resources =====
+None at the time.
 ===== Hands-on Lab Scenario =====
 This scenario is intended to be implemented using actual equipment on-site. Although it is possible to make it remotely, with the use of two BLE laboratory nodes, to observe all the details you need to have your mobile phone or similar device with an application which allows you to scan and explore your Bluetooth Low Energy devices and communicate with them. One of the best applications is nRF Connect created by Nordic Semiconductors.
@@ Line 12: / Line 12: @@
 ==== Start ====
-A similar program is available as the software example for the BLE server device in the ESP32 BLE Arduino package. You can use this example or the beacon program from IoT_7 as the starting point.
+A similar program is available as the software example for the BLE server device in the ESP32 BLE Arduino package. You can use this example or the beacon program from part 1 as the starting point.
 ==== Steps ====
@@ Line 32: / Line 32: @@
 BLECharacteristic  *pCharacteristic; //class for the characteristic
 </code>
-Any service or characteristic is identified with a unique UUID. If you use the standard service, like eg. Health Thermometer or Binary Sensor Service you can use a 16-bit UUID defined by Bluetooth SIG in the document (()). The same document defines the UUIDs for characteristics.
+Any service or characteristic is identified with a unique UUID. If you use the standard service, like eg. Health Thermometer or Binary Sensor Service you can use a 16-bit UUID defined by Bluetooth SIG in the document ((https://www.bluetooth.com/specifications/assigned-numbers/)). The same document defines the UUIDs for characteristics.
 <note>
 Example of the standard UUIDs for service and characteristic:
+\\
 Health Thermometer Service - 0x1809
+\\
 Temperature Measurement Characteristic - 0x2A1C
 </note>
@@ Line 129: / Line 131: @@
 <WRAP noprint>
 ===== Project information =====
-{{:en:iot-open:logo_iot_200_px.png?200|}}\\
+{{:en:edu:zmitac:s2:iotn:logo_iot_200_px.png?200|}}\\
 This Intellectual Output was implemented under the Erasmus+ KA2.\\
 Project IOT-OPEN.EU Reloaded – Education-based strengthening of the European universities, companies and labour force in the global IoT market.\\
@@ Line 142: / Line 144: @@
 The content is Copyrighted and distributed under CC BY-NC [[https://en.wikipedia.org/wiki/Creative_Commons_license|Creative Commons Licence]], free for Non-Commercial use.
 <figure label>
-{{:en:iot-open:ccbync.png?100|}}
+{{:en:edu:zmitac:s2:iotn:ccbync.png?100|}}
 </figure>
 </WRAP>