Hello !
Trace: • Admins's Guide • STM32 Wireless Series • Analog-to-digital Converter • Angle & Orientation Sensors • Raspberry Pi General Information • MQTTBox • SUT ESP32 Laboratory Node Hardware Reference • Debugging • Data Management Aspects in IoT • Arduino näited

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:iot-open:practical:hardware:sut:esp32 [2025/01/01 11:12] – [Application Layer Services] pczekalskien:iot-open:practical:hardware:sut:esp32 [2025/08/31 08:28] (current) – [Application Layer Services] pczekalski
Line 6: Line 6:
 ===== Hardware reference ===== ===== Hardware reference =====
 The table {{ref>esp32sutnodehardware}} lists all hardware components of the SUT's ESP32-S3 node and hardware details such as connectivity, protocols, GPIOs, etc. Please note that some pins overlap because buses such as SPI and I2C are shared among multiple components.\\  The table {{ref>esp32sutnodehardware}} lists all hardware components of the SUT's ESP32-S3 node and hardware details such as connectivity, protocols, GPIOs, etc. Please note that some pins overlap because buses such as SPI and I2C are shared among multiple components.\\ 
-The node is present in the figure {{ref>esp32sutnode1}} and reference numbers reflecting components in the table {{ref>esp32sutnodehardware}}.+The node is depicted in the figure {{ref>esp32sutnode1}} and referenced by component numbers in the table {{ref>esp32sutnodehardware}}.
  
 <figure esp32sutnode1> <figure esp32sutnode1>
Line 29: Line 29:
 </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/v5.2/esp32s3/hw-reference/esp32s3/user-guide-devkitm-1.html)), present in figure {{ref>esp32s3minidevkit}}:
  
 <figure esp32s3minidevkit> <figure esp32s3minidevkit>
Line 39: Line 39:
  
 <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
Line 54: Line 54:
 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.</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.
 +
 +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> <figure sutvrelnextgeninfrastructure>
Line 73: Line 75:
  
 ==== Application Layer Services ==== ==== Application Layer Services ====
-There are currently three application layer services available:+There are currently four application layer services available:
   * MQTT broker 1, available on private WiFi network and on the campus LAN network:   * 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);     * IP addresses: 192.168.91.5 (from internal IoT WiFi network), 157.158.56.57 (via the campus network);
Line 80: Line 82:
     * User: vrel     * User: vrel
     * Pass: vrel2018     * Pass: vrel2018
-    * Notice: all messages with a topic starting with <code>public/</code> will be routed to the public broker (MQTT broker 2, details on the broker below)+    * 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:   * 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;     * IP addresses: mqtt.iot-open.eu - do not use IP but rather DNS resolution as IP address may change without prior notice;
Line 87: Line 89:
     * User: vrel     * User: vrel
     * Pass: vrel2018     * 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 (MQTT broker 1, details on the broker above)+    * 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:   * CoAP server with two endpoints:
     * IP addresses: 192.168.91.5 (from internal IoT WiFi network), 157.158.56.57 (via the campus network);     * IP addresses: 192.168.91.5 (from internal IoT WiFi network), 157.158.56.57 (via the campus network);
Line 94: Line 96:
       * GET method for <code>coap://<ipaddress>/</code> that 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> that 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:8888/index.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.1735729967.txt.gz · Last modified: 2025/01/01 11:12 by pczekalski
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0