<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://home.roboticlab.eu/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://home.roboticlab.eu/feed.php">
        <title>Robotic &amp; Microcontroller Educational Knowledgepage - Network of Excellence - en:iot-open:practical:hardware:sut:stm32</title>
        <description></description>
        <link>https://home.roboticlab.eu/</link>
        <image rdf:resource="https://home.roboticlab.eu/_media/wiki/logo.png" />
       <dc:date>2026-04-05T08:43:43+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb1a_1?rev=1711355014&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb1b_1?rev=1713692479&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb2_1?rev=1713698712&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb3_1?rev=1713806877&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb4_1?rev=1713808590&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb5_1?rev=1712780437&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb6_1?rev=1713620085&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb7_1?rev=1714072637&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb8_1?rev=1713606404&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb9a_1?rev=1711729557&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb9b_1?rev=1714651364&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb10_1?rev=1712776174&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_1?rev=1714205755&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_2?rev=1714205726&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_3?rev=1714210962&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_4?rev=1714210900&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_5?rev=1714812089&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_6?rev=1714810249&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_7?rev=1714820594&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_at?rev=1714205650&amp;do=diff"/>
                <rdf:li rdf:resource="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/scenarios?rev=1759490925&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://home.roboticlab.eu/_media/wiki/logo.png">
        <title>Robotic & Microcontroller Educational Knowledgepage - Network of Excellence</title>
        <link>https://home.roboticlab.eu/</link>
        <url>https://home.roboticlab.eu/_media/wiki/logo.png</url>
    </image>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb1a_1?rev=1711355014&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-03-25T08:23:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_1A: Use of fan</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb1a_1?rev=1711355014&amp;do=diff</link>
        <description>STM_1A: Use of fan

This scenario presents how to control the fan&#039;s rotation speed with a PWM signal. You can observe the rotation via the camera, but it would be rather hard to notice the change in the rotation speed. The fan is mounted on the top of the pressure tube and blows the air onto the pressure sensor. You can observe changes in sensor readings according to different fan speeds. How to use the sensor is shown in another scenario.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb1b_1?rev=1713692479&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-21T09:41:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_1B: Reading environmental data with a Bosch integrated sensor</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb1b_1?rev=1713692479&amp;do=diff</link>
        <description>STM_1B: Reading environmental data with a Bosch integrated sensor

We will read environmental data using a BME 280 sensor in this scenario. It is one of the most popular sensors in weather stations. It integrates a single chip&#039;s digital thermometer, hygrometer (air humidity), and air pressure meter. In our laboratory equipment, this sensor is located inside the yellow pressure chamber, under the fan which can blow the air onto it.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb2_1?rev=1713698712&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-21T11:25:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_2: Using a digital potentiometer</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb2_1?rev=1713698712&amp;do=diff</link>
        <description>STM_2: Using a digital potentiometer

Digital potentiometer DS1803 is an I2C-controlled device that digitally controls the resistance between the outputs as in a real turning potentiometer.
While in the turning potentiometers, there are wipers which are moving from minimal to a maximal value, in digital potentiometers there are no movable parts. Everything is implemented in a silicon.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb3_1?rev=1713806877&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-22T17:27:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_3: Use of integrated temperature and humidity sensor</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb3_1?rev=1713806877&amp;do=diff</link>
        <description>STM_3: Use of integrated temperature and humidity sensor

In this scenario, we will introduce a popular DHT11 sensor. The DHT series covers DHT11, DHT22, and AM2302. Those sensors differ in accuracy and physical dimensions but can all read environmental temperature and humidity. This scenario can be run stand-alone to read weather data in the laboratory nodes&#039; room. The DHT11 sensor is controlled with one GPIO (in all our laboratory nodes, it is GPIO D22 or PB_2 in Nucleo-style numbering) and us…</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb4_1?rev=1713808590&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-22T17:56:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_4: 1-Wire Temperature Sensor</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb4_1?rev=1713808590&amp;do=diff</link>
        <description>STM_4: 1-Wire Temperature Sensor

The temperature-only sensor DS18B20 uses a 1-wire protocol. “1-wire” applies only to the bidirectional bus; power and GND are on separate pins. The sensor is connected to the MCU using GPIO D0 only (PA_3 in Nucleo numbering). Many devices can be connected on a single 1-wire bus, each with a unique ID. Except plastic version, which we have in our laboratory (enclosure TO-92)</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb5_1?rev=1712780437&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-10T20:20:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_5: Using LCD Display</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb5_1?rev=1712780437&amp;do=diff</link>
        <description>STM_5: Using LCD Display

Alphanumerical LCD is one of the most popular output devices in the Embedded and IoT. Using LCD with predefined line organisation (here, 2 lines, 16 characters each) is as simple as sending a character&#039;s ASCII code to the device. This is so much simpler than in the case of the use of dot-matrix displays, where it is necessary to use fonts. The fixed organisation LCD has limits; here, only 32 characters can be presented to the user simultaneously.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb6_1?rev=1713620085&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-20T13:34:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_6: Using ePaper display</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb6_1?rev=1713620085&amp;do=diff</link>
        <description>STM_6: Using ePaper display

VREL NExtGen laboratory node is equipped with b/w, ePaper module. It is a dot matrix display with a native resolution of 250×122 pixels. It has 64kB display memory and is controlled via SPI. The ePaper display presents data even if powered off, so don&#039;t be surprised that finishing your application does not automatically clean up the display, even if you use some other code later. To clean up the display, one has to clear the screen explicitly.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb7_1?rev=1714072637&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-25T19:17:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_7: Using OLED display</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb7_1?rev=1714072637&amp;do=diff</link>
        <description>STM_7: Using OLED display

This scenario presents how to use the OLED display connected to the STM32WB55 SoC. Our OLED display is an RGB (16bit colour, 64k colours) 1.5in, 128×128 pixels. The OLED chip is SSD1351, and it is controlled over the SPI interface using the pin configuration as described in STM32 node Hardware Reference in Table 1 STM32WB55 Node Hardware Details.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb8_1?rev=1713606404&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-20T09:46:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_8: Controlling Smart LED stripe</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb8_1?rev=1713606404&amp;do=diff</link>
        <description>STM_8: Controlling Smart LED stripe

A Smart LED stripe is a chain of connected digital LEDs (also referenced as NEOPIXEL) which can be individually controlled. The stripe in our lab equipment consists of eight RGB LEDs. There exist also other colour configurations such as RGBWW (Red+Green+Blue+Warm White+Cold White) or WWA (Warm White+Cold White+Amber). They are controlled with just one pin/GPIO. GPIO sends the digital signal to the first LED in a chain and the LED passes data to the next one, …</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb9a_1?rev=1711729557&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-03-29T16:25:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_9A: Use of RGB LEDs</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb9a_1?rev=1711729557&amp;do=diff</link>
        <description>STM_9A: Use of RGB LEDs

This scenario presents how to handle the brightness control of the tri-coloured LEDs. One is observable via camera, as presented in the figure (component 9A), while another is hidden inside the black enclosure and lights a colour sensor (component 9B). Both LEDs are electrically bound and cannot be controlled independently. Those LEDs have 3 colour channels, controlled independently: R (Red), G (Green) and B (Blue). Mixing of those colours creates other ones, such as pin…</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb9b_1?rev=1714651364&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-02T12:02:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_9B: Reading colour sensor</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb9b_1?rev=1714651364&amp;do=diff</link>
        <description>STM_9B: Reading colour sensor

A colour sensor (TCS 34725) can detect the brightness and colour of the light emitted. It works with the I2C bus. In our laboratory, the sensor has a fixed 0x29 address. The sensor is in the black enclosure, ensuring no ambient light impacts readings. The only light source is an RGB LED, controlled as described in the scenario</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb10_1?rev=1712776174&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-10T19:09:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_10: Controlling standard servo</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/emb10_1?rev=1712776174&amp;do=diff</link>
        <description>STM_10: Controlling standard servo

You will learn how to control a standard miniature servo with the STM32 System on Chip. Standard miniature analogue servo is controlled with a PWM signal of frequency 50Hz with a duty cycle period between 1 ms (rotate to 0) and 2 ms (rotate to 180 degrees), where 1.5 ms corresponds to 90 degrees. Some servos have other duty cycle minimum and maximum values, always refer to the documentation.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_1?rev=1714205755&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-27T08:15:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_1: Reading MAC address of the WiFi</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_1?rev=1714205755&amp;do=diff</link>
        <description>STM_IoT_1: Reading MAC address of the WiFi

Each network card is supposed to have a unique physical address called a MAC address. MAC abbreviation stands for Medium Access Control protocol, which provides access to the physical link in the network layer. The STM32WB55 SoC doesn&#039;t have a WiFi network controller so our STM laboratory stands have the WiFi module based on ESP32-C3 SoC connected by serial port additional ESP32-C3 module and controlled with AT commands. To learn how to use these comma…</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_2?rev=1714205726&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-27T08:15:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_2: Connecting to the WiFi Access Point and presenting IP</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_2?rev=1714205726&amp;do=diff</link>
        <description>STM_IoT_2: Connecting to the WiFi Access Point and presenting IP

Each computer connected to the Internet is identified with the IP address. IP abbreviation stands for Internet Protocol, which is responsible for transmitting data packets between computers in the whole global web - the Internet. The same mechanism is used for addressing and transmitting packets among IP-capable IoT devices. The most popular local networks which support IP addressing are Ethernet and WiFi. Currently, the transitio…</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_3?rev=1714210962&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-27T09:42:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_3: Connecting to the MQTT broker and publishing data</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_3?rev=1714210962&amp;do=diff</link>
        <description>STM_IoT_3: Connecting to the MQTT broker and publishing data

In the following scenario, you will learn how to connect to the MQTT broker and publish a message.

Prerequisites

To implement this scenario, it is necessary to get familiar with at least one of the following scenarios first:</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_4?rev=1714210900&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-27T09:41:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_4: Connecting to the MQTT broker and subscribing to the topic</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_4?rev=1714210900&amp;do=diff</link>
        <description>STM_IoT_4: Connecting to the MQTT broker and subscribing to the topic

In the following scenario, you will learn how to connect to the MQTT broker and subscribe to the chosen topic to receive messages.

Prerequisites

To implement this scenario, it is necessary to get familiar with the LED controlling scenario:</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_5?rev=1714812089&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-04T08:41:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_5: BLE Beacon</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_5?rev=1714812089&amp;do=diff</link>
        <description>STM_IoT_5: 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 t…</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_6?rev=1714810249&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-04T08:10:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_6: BLE Communication with characteristics</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_6?rev=1714810249&amp;do=diff</link>
        <description>STM_IoT_6: BLE Communication with characteristics

This scenario presents how to create the Bluetooth Low Energy server device and corresponding client device. The server can be the sensor device which responds to the client with the results of the measurements. This can also be the output device, which we can control writing the data to. The client connects to a server and reads the data. This scenario presents the use of the concept of services and characteristics.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_7?rev=1714820594&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-04T11:03:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_7: BLE Communication with indications</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_7?rev=1714820594&amp;do=diff</link>
        <description>STM_IoT_7: BLE Communication with indications

This scenario presents how to extend the Bluetooth Low Energy server and client devices with a notification or indication mechanism for sending data automatically. If enabled, notifications or indications are sent at any time while the data in the server is updated. A difference between them is that a notification is an unacknowledged message while an indication is an acknowledged message. While one of them is enabled by the client, the server decid…</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_at?rev=1714205650&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-27T08:14:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM_IoT_AT: Programming of the WiFi interface with AT commands</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/iot_at?rev=1714205650&amp;do=diff</link>
        <description>STM_IoT_AT: Programming of the WiFi interface with AT commands

The STM32WB55 SoC doesn&#039;t have a WiFi network controller so our STM laboratory stands have the WiFi module based on ESP32-C3 SoC connected by serial port and controlled with AT commands. In this scenario, you will learn how to use these commands.</description>
    </item>
    <item rdf:about="https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/scenarios?rev=1759490925&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-03T11:28:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>STM32 Laboratory Scenarios</title>
        <link>https://home.roboticlab.eu/en/iot-open/practical/hardware/sut/stm32/scenarios?rev=1759490925&amp;do=diff</link>
        <description>STM32 Laboratory Scenarios

 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.</description>
    </item>
</rdf:RDF>
