Both sides previous revisionPrevious revisionNext revision | Previous revision |
en:iot-open:practical:hardware:sut:esp32 [2025/01/15 22:17] – [Network configuration and services] pczekalski | en:iot-open:practical:hardware:sut:esp32 [2025/04/28 19:55] (current) – [Hardware reference] pczekalski |
---|
</table> | </table> |
| |
The MCU standing behind the laboratory node is a genuine ESP32-S3-DevKitM-1-N8 from Espressif ((https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/hw-reference/esp32s3/user-guide-devkitm-1.html)), present in figure {{ref>esp32s3minidevkit}}: | The MCU working behind the laboratory node is ESP32-S3-DevKitM-1-N8 made by Espressif ((https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/hw-reference/esp32s3/user-guide-devkitm-1.html)), present in figure {{ref>esp32s3minidevkit}}: |
| |
<figure esp32s3minidevkit> | <figure esp32s3minidevkit> |
| |
<file ini platformio.ini> | <file ini platformio.ini> |
[env:esp32] | [env:vrelnextgen] |
platform = espressif32 | platform = espressif32 |
board = esp32-s3-devkitc-1 | board = esp32-s3-devkitc-1 |
Figure {{ref>sutvrelnextgeninfrastructure}} represents SUT's VREL Next Gen IoT remote lab networking infrastructure and services. Details are described below. | Figure {{ref>sutvrelnextgeninfrastructure}} represents SUT's VREL Next Gen IoT remote lab networking infrastructure and services. Details are described below. |
| |
<note important>If you're a fully remote student, you do not have access to the public part of the network (addresses 157.158.56.0/24); thus, you need to use only IoT devices and services available in the internal IoT WiFi network that IoT devices you're programming can access. Still you may access MQTT messaging via the 2nd MQTT Broker bridged, but it requires specific topics organisation as not all topics are forwarded. Refer to the documentation below.</note> | <note important>If you're a fully remote student, you do not have access to the public part of the network (addresses 157.158.56.0/24); thus, you need to use only IoT devices and services available in the internal IoT WiFi network that IoT devices you're programming can access. You may still access MQTT messaging via the 2nd MQTT Broker bridged, but it requires specific topic organisation as not all topics are forwarded. Refer to the documentation below.</note> |
If you're a SUT student or can access the campus network, you can also use 157.158.56.0/24 addresses. | If you're a SUT student or can access the campus network, you can also use 157.158.56.0/24 addresses. |
| |