| Both sides previous revisionPrevious revision | |
| en:iot-open:practical:hardware:sut:esp32:scenarios [2025/10/03 14:28] – pczekalski | en:iot-open:practical:hardware:sut:esp32:scenarios [2026/05/01 22:56] (current) – pczekalski |
|---|
| <note>The remote access lab will not let you use the most common approach towards tracing, as you're physically away from the device and do not have access to, e.g. its serial port or debugger. For this reason, understanding actuators (mostly displays) is essential because the only way to monitor execution is to observe the results remotely via the video stream.</note> | <note>The remote access lab will not let you use the most common approach towards tracing, as you're physically away from the device and do not have access to, e.g. its serial port or debugger. For this reason, understanding actuators (mostly displays) is essential because the only way to monitor execution is to observe the results remotely via the video stream.</note> |
| |
| <note important>Note that video streaming has limitations, such as the number of frames per second, resolution, common use of many devices (dynamic video colours problem) and stream quality. That impacts how you write the software, e.g., using larger fonts and avoiding rapid changes to display contents, as you may be unable to observe those changes remotely.</note> | <note important>Note that video streaming has limitations, such as the number of frames per second, resolution, common use of many devices (dynamic video colours problem) and stream quality. That affects how you write the software, e.g., by using larger fonts and avoiding rapid changes to displayed content, as you may be unable to observe those changes remotely.</note> |
| |
| **Know the hardware**\\ | **Know the hardware**\\ |
| The following scenarios explain the use of hardware components and services that constitute the laboratory node. It is intended to seamlessly introduce users to IoT scenarios where using sensors and actuators is an intermediate step, and the main goal is to use networking and communication. Besides IoT, those scenarios can be utilised as part of the Embedded Systems Modules. | The following scenarios explain the use of hardware components and services that constitute the laboratory node. It is intended to seamlessly introduce users to IoT scenarios where using sensors and actuators is an intermediate step, and the main goal is to use networking and communication. Besides IoT, those scenarios can be utilised within the Embedded Systems Modules. |
| <WRAP excludefrompdf> | <WRAP excludefrompdf> |
| * [[en:iot-open:practical:hardware:sut:esp32:emb5_1]] How do you use LCD (component 5)? | * [[en:iot-open:practical:hardware:sut:esp32:emb5_1]] How do you use LCD (component 5)? |
| In the following scenarios, we will focus on advanced programming techniques, such as asynchronous programming and timers. | In the following scenarios, we will focus on advanced programming techniques, such as asynchronous programming and timers. |
| <WRAP excludefrompdf> | <WRAP excludefrompdf> |
| * [[en:iot-open:practical:hardware:sut:esp32:adv1_1]] Using timers to handle the asynchronously periodic data display. | * [[en:iot-open:practical:hardware:sut:esp32:adv1_1]] Using timers to handle the asynchronous periodic data display. |
| </WRAP> | </WRAP> |
| ** IoT programming **\\ | ** IoT programming **\\ |
