Differences

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

Link to this comparison view

Next revision
Previous revision
en:iot-open:practical:hardware:itsilesia:esp32 [2025/08/31 09:05] – created pczekalskien:iot-open:practical:hardware:itsilesia:esp32 [2025/08/31 12:53] (current) – [Networking Layer] pczekalski
Line 1: Line 1:
 ====== ItSilesia ESP32 Mobile Laboratory Node Hardware Reference ====== ====== ItSilesia ESP32 Mobile Laboratory Node Hardware Reference ======
-In general, these laboratory nodes share the same physical configuration as the [[en:iot-open:practical:hardware:sut:esp32|ESP32 laboratory of the SUT]] but differ in IP addressing.+In general, these laboratory nodes share the same physical configuration as the [[en:iot-open:practical:hardware:sut:esp32|ESP32 laboratory of the SUT]] but differ in IP addressing. For this reason, all laboratory hands-on-lab scenarios for SUT are valid for ItSilesia's mobile lab, still keep in mind different services and addressing.
  
 ===== Introduction ===== ===== Introduction =====
Line 6: Line 6:
 <note tip>Note that each node has a unique ID built into the chip, as well as unique MAC addresses for the WiFi and Bluetooth interfaces.</note> <note tip>Note that each node has a unique ID built into the chip, as well as unique MAC addresses for the WiFi and Bluetooth interfaces.</note>
 ===== 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>esp32itsilesianodehardware}} lists all hardware components of ItSilesia'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 depicted in the figure {{ref>esp32sutnode1}} and referenced by component numbers in the table {{ref>esp32sutnodehardware}}.+The node is depicted in the figure {{ref>esp32itsilesianode1}} and referenced by component numbers in the table {{ref>esp32itsilesianodehardware}}.
  
-<figure esp32sutnode1>+<figure esp32itsilesianode1>
 {{:en:iot-open:practical:hardware:sut:vrel_nextgen_sut_motherboard.png?560|}} {{:en:iot-open:practical:hardware:sut:vrel_nextgen_sut_motherboard.png?560|}}
-<caption>ESP32-S3 SUT Node</caption>+<caption>ESP32-S3 ItSilesia Node</caption>
 </figure> </figure>
-<table esp32sutnodehardware+<table esp32itsilesianodehardware
-<caption>ESP32-S3 SUT Node Hardware Details</caption>+<caption>ESP32-S3 ItSilesia Node Hardware Details</caption>
 ^ Component ID  ^ Description                                ^ Hardware model (controller)  ^ Control method                       ^ GPIOs (as connected to the ESP32-S3)                                     ^ Remarks                                                                                                                                                                                          ^ ^ Component ID  ^ Description                                ^ Hardware model (controller)  ^ Control method                       ^ GPIOs (as connected to the ESP32-S3)                                     ^ Remarks                                                                                                                                                                                          ^
 | 1A            | 12V PWM controlled fan                     | Pe60251b1-000u-g99           | PWM                                  | FAN_PWM = 35                                                             | Fan blows air into the pressure chamber (yellow container) to stimulate air pressure changes.                                                                                                    | | 1A            | 12V PWM controlled fan                     | Pe60251b1-000u-g99           | PWM                                  | FAN_PWM = 35                                                             | Fan blows air into the pressure chamber (yellow container) to stimulate air pressure changes.                                                                                                    |
Line 55: Line 55:
 Users connect to the WiFi Access Point provided by the laboratory module. This WiFi is shared for both users (NATed to the Internet) as well as for IoT devices and services. Users connect to the WiFi Access Point provided by the laboratory module. This WiFi is shared for both users (NATed to the Internet) as well as for IoT devices and services.
  
-Figure {{ref>itsilesiavrelnextgeninfrastructure}} represents SUT's VREL Next Gen IoT remote lab networking infrastructure and services. Details are described below.+Figure {{ref>itsilesiavrelnextgeninfrastructure}} represents ItSilesia's VREL Next Gen IoT remote lab networking infrastructure and services. Details are described below.
  
 <figure itsilesiavrelnextgeninfrastructure> <figure itsilesiavrelnextgeninfrastructure>
 +{{ :en:iot-open:practical:hardware:itsilesia:vrel_mobile-networking.drawio.png?600 |VREL Mobile Lab network configuration}}
 <caption>VREL Next Gen IoT remote lab networking infrastructure and services</caption> <caption>VREL Next Gen IoT remote lab networking infrastructure and services</caption>
 </figure> </figure>
Line 69: Line 69:
  
 All clients get an IP address from the range of 192.168.0.100 to 192.168.0.200 All clients get an IP address from the range of 192.168.0.100 to 192.168.0.200
-Gateway is 192.168.0.1, and it is also the address of the IoT VREL management service for accessing devices: [[http://192.168.0.1|IoT Mobile VREL labs instance]].+Gateway is 192.168.0.1, and it is also the address of the IoT VREL management service for accessing devices: [[http://192.168.0.1]]
 +<note warning>Note, even if available, the system WILL NOT work using the public IP address.</note> 
 + 
 +In this laboratory module, for simplicity and portability of the solution, all clients connect to a single, private, NATed network, including IoT devices and clients (developers/students). 
 +All IoT integration services are also available via this network.
  
 ==== Application Layer Services ==== ==== Application Layer Services ====
-There are currently 2 application-layer services available: +There are currently 2 application-layer services available, accessible for IoT nodes when connected to the VRELlab network
-  * MQTT broker 1+  * MQTT broker: 
-    * IP addresses: 192.168.0.5;+    * IP addresses: 192.168.0.1;
     * Port: 1883 (TCP)     * Port: 1883 (TCP)
     * Security: plain text authentication     * Security: plain text authentication
Line 80: Line 84:
     * Pass: vrel1234     * Pass: vrel1234
   * CoAP server with two endpoints:   * CoAP server with two endpoints:
-    * IP addresses: 192.168.0.10;+    * IP addresses: 192.168.0.1;
     * Port: 5683 (UDP)     * Port: 5683 (UDP)
     * Endpoints:     * Endpoints:
-      * GET method for <code>coap://192.168.0.10/</code> that brings you a secret code in the message's payload, +      * GET method for <code>coap://192.168.0.1/</code> that brings you a secret code in the message's payload, 
-      * GET method for <code>coap://192.168.0.10/hello</code> that brings you a hello world welcome message in the payload.+      * GET method for <code>coap://192.168.0.1/hello</code> that brings you a hello world welcome message in the payload.
  
en/iot-open/practical/hardware/itsilesia/esp32.1756631117.txt.gz · Last modified: 2025/08/31 09:05 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