User Tools

Site Tools


No ACL setup yet! Denying access to everyone.
en:edu:zmitac:s2:iotn:esp32ble1

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:iotn:esp32ble1 [2024/03/31 17:36] – ktokarzen:edu:zmitac:s2:iotn:esp32ble1 [2024/04/03 12:51] (current) – ktokarz
Line 11: Line 11:
 ===== Hands-on Lab Scenario ===== ===== 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. 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.
 +
 ==== Task to be implemented ==== ==== Task to be implemented ====
 Implement a program that operates as the BLE beacon which advertises itself with the link to the SUT website. This can be done with the Eddystone beacon format. Implement a program that operates as the BLE beacon which advertises itself with the link to the SUT website. This can be done with the Eddystone beacon format.
  
 ==== Start ==== ==== Start ====
-The example software for the beacon device available in the software package differs between versions of the environment, that's why we will write the program from scratch. +The example software for the beacon device available in the software package differs between versions of the environment, that's why we will write the program from scratch. But even in such a situation, it is much easier to start by using some simple example. We can use the "arduino-blink" example to have the project structure ready with basic source and configuration files. 
 +\\ 
 +The platformio.ini file can look like in the following example. 
 +<file ini platformio.ini> 
 +[env:esp32] 
 +platform = espressif32 
 +board = esp32-s3-devkitc-1 
 +board_build.mcu = esp32s3 
 +board_build.f_cpu = 240000000L 
 +framework = arduino 
 +platform_packages = 
 +    toolchain-riscv32-esp @ 8.4.0+2021r2-patch5 
 +lib_ldf_mode = deep+ 
 +</file>
 ==== Steps ==== ==== Steps ====
 We can go through the lab in a few steps. In the beginning, we will write a simple program which advertises the device with the default parameters set in the software package. After a successful first attempt, we will add our information to the advertising frame, and lastly, we will use the Eddystone format to send the chosen URL address. We can go through the lab in a few steps. In the beginning, we will write a simple program which advertises the device with the default parameters set in the software package. After a successful first attempt, we will add our information to the advertising frame, and lastly, we will use the Eddystone format to send the chosen URL address.
en/edu/zmitac/s2/iotn/esp32ble1.1711899371.txt.gz · Last modified: by ktokarz