SUT ESP32 Laboratory Scenarios

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 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 not changing display contents rapidly because you may be unable to observe those changes remotely.

* [Scenario Short Code]: [Scenario name] Laboratory scenario template. To be removed in the final version

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 a part of the Embedded Systems Modules.

Advanced techniques
In the following scenarios, we will focus on advanced programming techniques, such as asynchronous programming and timers.

IoT programming
In the following scenarios, you will write programs interacting with other devices, services, and networks, which are pure IoT applications.

en/iot-open/practical/hardware/sut/esp32/scenarios.txt · Last modified: 2024/03/25 20:54 by pczekalski
CC Attribution-Share Alike 4.0 International Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0