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:iot-open:practical:hardware:sut:esp32:iot_7 [2024/05/02 10:30] – [Task to be implemented] ktokarzen:iot-open:practical:hardware:sut:esp32:iot_7 [2024/05/02 11:11] (current) – [IOT7: BLE Beacon] ktokarz
Line 1: Line 1:
-====== IOT7: BLE Beacon =====+====== IoT7: BLE Beacon =====
 This scenario presents how to create the Bluetooth Low Energy beacon device which periodically broadcasts a small amount of information, and the client device which can receive packets sent by the beacon. Beacons are usually used for sending useful information (eg. the web address of the owner, a link to the page with tourist information). In some cases, they simply send the identification number recognised by a dedicated mobile application allowing the users to localise themselves. This scenario presents how to create the Bluetooth Low Energy beacon device which periodically broadcasts a small amount of information, and the client device which can receive packets sent by the beacon. Beacons are usually used for sending useful information (eg. the web address of the owner, a link to the page with tourist information). In some cases, they simply send the identification number recognised by a dedicated mobile application allowing the users to localise themselves.
  
Line 20: Line 20:
 This scenario is intended to be implemented using two laboratory nodes. One node will work as the beacon device, while the second will receive the beacon's packets and display information on the LCD. This scenario is intended to be implemented using two laboratory nodes. One node will work as the beacon device, while the second will receive the beacon's packets and display information on the LCD.
 ==== Task to be implemented ==== ==== Task to be implemented ====
-**Task 1** Implement a program that operates as the BLE beacon which advertises itself with the link to the simple website. This can be done with the Eddystone beacon format.+**Task 1** Implement a program that operates as the BLE beacon which advertises itself with the link to the website. This can be done with the Eddystone beacon format.
 **Task 2** Implement the receiver of advertising frames broadcasted by the beacon device capable of displaying information on the LCD screen. **Task 2** Implement the receiver of advertising frames broadcasted by the beacon device capable of displaying information on the LCD screen.
  
Line 263: Line 263:
 }; // MyAdvertisedDeviceCallbacks }; // MyAdvertisedDeviceCallbacks
 </code> </code>
 +Additional filtering of remote devices can be done with their names. We can add in the "MyAdvertisedDeviceCallbacks()" function the comparison of the remote device name with the constant string. It should be done if the Eddystone service was found. 
 +<code c> 
 +String name; 
 +name = advertisedDevice.getName().c_str(); 
 +if (name.equals("SUT BLE device")) 
 +  { 
 +    // here the internal code of the MyAdvertisedDeviceCallbacks() 
 +  } 
 +</code>
  
 === Step 5 === === Step 5 ===
en/iot-open/practical/hardware/sut/esp32/iot_7.1714645820.txt.gz · Last modified: 2024/05/02 10:30 by ktokarz
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0