SUT ESP32 Laboratory Node Hardware Reference

Each laboratory node is equipped with an ESP32-S3 double-core chip. Several peripherals, networks and network services are available for the user. The UI is necessary to observe results in the camera when programming remotely. Thus, a proper understanding of UI programming is essential to successfully using the devices.

The table 1 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 1 and reference numbers reflecting components in the table 1.

The MCU standing behind the laboratory node is a genuine ESP32-S3-DevKitM-1-N8 from Espressif ^[1], present in figure 2:

A suitable platformio.ini file for the correct code compilation is presented below. It does not contain libraries that need to be added regarding specific tasks and hardware used in particular scenarios. The code below presents only the typical section. Refer to the scenario description for details regarding case-specific libraries needed for the implementation:

platformio.ini

[env:vrelnextgen]
platform = espressif32
board = esp32-s3-devkitc-1
board_build.mcu = esp32s3
board_build.f_cpu = 240000000L
framework = arduino
platform_packages =
    toolchain-riscv32-esp @ 8.4.0+2021r2-patch5
lib_ldf_mode = deep+

Figure 3 represents SUT's VREL Next Gen IoT remote lab networking infrastructure and services. Details are described below.

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.

The WiFi network, separated (no routing to and from the Internet) for IoT experimentation is available for all nodes:

• SSID: internal.IOT.NextGen
• PASS: IoTlab32768

A public, wired (157.158.56.0/24) network is available only for on-site students and from the SUT's campus network.

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.

There are currently four application layer services available:

• 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
  • Notice: all messages with a topic starting with

    public/

    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

    vrel/

    or

    sut/

    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

      coap://<ipaddress>/

      that brings you a secret code in the message's payload,

    • GET method for

      coap://<ipaddress>/hello

      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