Differences

This shows you the differences between two versions of the page.

--- en:iot-open:practical:hardware:sut:esp32 [2024/05/07 12:21] – [Application Layer] pczekalski
+++ en:iot-open:practical:hardware:sut:esp32 [2025/04/28 19:55] (current) – [Hardware reference] pczekalski
@@ Line 29: / Line 29: @@
 </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>
@@ Line 39: / Line 39: @@
 <file ini platformio.ini>
-[env:esp32]
+[env:vrelnextgen]
 platform = espressif32
 board = esp32-s3-devkitc-1
@@ Line 54: / Line 54: @@
 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.</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.
+Openthread IP6 network with short addressing (up to 65k devices) is bound to the campus network (UDP forwarding, bidirectional) via Openthread BorderRouter. Refer to the diagram below (figure {ref>sutvrelnextgeninfrastructure}) for details.
 <figure sutvrelnextgeninfrastructure>
@@ Line 62: / Line 64: @@
 </figure>
-==== Networking layer ====
+==== Networking Layer ====
 The WiFi network, separated (no routing to and from the Internet) for IoT experimentation is available for all nodes:
@@ Line 72: / Line 74: @@
 It is important to distinguish the network context and use the correct address. Integration services usually have two interfaces: one is available from the IoT WiFi network so nodes can access it, and the other IP address (from the public campus network) is available only for students directly connected to it.
-==== Application Layer ====
+==== Application Layer Services ====
-There are currently two application layer services available:
+There are currently four application layer services available:
-  * MQTT broker available on both addresses:
+  * MQTT broker 1, available on private WiFi network and on the campus LAN network:
     * IP addresses: 192.168.91.5 (from internal IoT WiFi network), 157.158.56.57 (via the campus network);
     * Port: 1883 (TCP)
+    * Security: plain text authentication
     * User: vrel
     * Pass: vrel2018
-  * CoAP server with 2 endpoints:
+    * Notice: all messages with a topic starting with <code>public/</code> will be routed to the public broker via the MQTT bridge (MQTT broker 2, details on the broker below)
+  * MQTT broker 2, in the cloud segment, available virtually from everywhere:
+    * IP addresses: mqtt.iot-open.eu - do not use IP but rather DNS resolution as IP address may change without prior notice;
+    * Port: 8883 (TCP)
+    * Security: SSL/TLS
+    * User: vrel
+    * Pass: vrel2018
+    * Notice: all messages with topics starting with <code>vrel/</code> or <code>sut/</code> will be routed to the MQTT broker in the campus network via the MQTT bridge  (MQTT broker 1, details on the broker above)
+  * CoAP server with two endpoints:
     * IP addresses: 192.168.91.5 (from internal IoT WiFi network), 157.158.56.57 (via the campus network);
     * Port: 5683 (UDP)
     * Endpoints:
-      * GET method for <code>coap://<ipaddress>/</code> - brings you a secret code in the message's payload,
+      * GET method for <code>coap://<ipaddress>/</code> that brings you a secret code in the message's payload,
-      * GET method for <code>coap://<ipaddress>/hello</code> - brings you a hello world welcome message in the payload.
+      * GET method for <code>coap://<ipaddress>/hello</code> that brings you a hello world welcome message in the payload.
+  * OpenThread border router, capable of routing messages from the OpenThread network to the campus LAN:
+    * Management IP address: 192.168.88.53 (from internal wired network), 157.158.56.57 (via the campus network);
+    * Port for monitoring/management 8888 (WEB Gui interface / ESP32 Openthread Border Router API), URL is http://157.158.56.57/intex.html
+    * OpenThread network details:
+      * Channel: 15
+      * Wake-up Channel: 21
+      * Channel Mask: 0x07fff800
+      * Ext PAN ID: dead00beef00cafe
+      * Mesh Local Prefix: fc00:db8:a0:0::/64
+      * Network Key: 00112233445566778899aabbccddeeff
+      * Network Name: OpenThread-VREL
+      * PAN ID: 0x1234
+      * PSKc: 104810e2315100afd6bc9215a6bfac53

en/iot-open/practical/hardware/sut/esp32.1715084472.txt.gz · Last modified: 2024/05/07 12:21 by pczekalski