====== SUT ESP32 Laboratory Node Hardware Reference ====== ===== Introduction ===== 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. Note that each node has a unique ID built into the chip, as well as unique MAC addresses for the WiFi and Bluetooth interfaces. ===== 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 node is present in the figure {{ref>esp32sutnode1}} and reference numbers reflecting components in the table {{ref>esp32sutnodehardware}}.
{{:en:iot-open:practical:hardware:sut:vrel_nextgen_sut_motherboard.png?560|}} ESP32-S3 SUT Node
^ 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. | | 1B | Pressure and environmental sensor | BME 280 | I2C, address 0x76 | SDA=5, SCL=4 | Spinning of the fan causes air to blow inside the yellow chamber and thus causes air pressure to change. | | 2 | Digital potentiometer | DS1803-100 | I2C, address 0x28 | SDA=5, SCL=4, analog input (A/D)=7 | Digital potententiometer's output is connected to the A/D input of the MCU. | | 3 | Temperature and humidity sensor 1 | DHT11 | proprietary protocol, one GPIO | control on GPIO 47 | | | 4 | Temperature sensor 2 | DS18B20 | 1-Wire | 1-Wire interface on GPIO 6 | | | 5 | 2x16 LCD | HD44780 | Proprietary 4 bit control interface | EN=1, RS=2, D4=39, D5=40, D6=41, D7=42 | 4-bit, simplified, one-directional (MCU->LCD) communication only | | 6 | ePaper, B&W 2.13in, 250x122 pixels | Pico-ePaper-2.13 | SPI | SPI_MOSI=15, SPI_CLK=18, SPI_DC=13, SPI_CS=10, SPI_RST=9, EPAPER_BUSY=8 | Memory size is 64kB (65536ul) | | 7 | OLED, RGB colourful 1.5in, 128x128 pixels | SSD1351 | SPI | SPI_MOSI=15, SPI_CLK=18, SPI_DC=13, SPI_CS=11, SPI_RST=12 | 64k colours RGB (16bit) | | 8 | RGB Smart LED stripe | 8*WS2812B | Proprietary protocol, one GPIO | NEOPIXEL=34 | | | 9A | Light intensity and colour sensor | TCS 34725 | I2C address 0x29 | SDA=5, SCL=4, Interrupt=16 | The sensor is illuminated by RGB LED (9A) | | 9B | RGB LED PWM controlled | | PWM | LED_R=33, LED_B=26, LED_G=21 | Each colour can be independently controlled with PWM. The LED is integrated with another, illuminating the colour sensor (9B) so that controlling this RGB LED also directly impacts the other. | | 10 | Standard miniature servo | SG90 or similar | PWM | SERVO_PWM=37 | Standard timings for micro servo: PWM 50Hz, duty cycle:\\ - 0 deg (right position): 1ms,\\ - 90 deg (up position): 1.5ms,\\ - 180 deg (left position): 2ms. |
ESP32-S3 SUT Node Hardware Details
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}}:
{{:en:iot-open:practical:hardware:sut:20231213_154426.jpg?200|ESP32-S3-DevKitM-1-N8 development kit}} ESP32-S3-DevKitM-1-N8 controlling the laboratory node
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: [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+ ===== Network configuration and services ===== Figure {{ref>sutvrelnextgeninfrastructure}} represents SUT's VREL Next Gen IoT remote lab networking infrastructure and services. Details are described below. 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. 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.
{{:en:iot-open:practical:hardware:sut:sut_network_infrastructure-new.drawio.png?600|}} VREL Next Gen IoT remote lab networking infrastructure and services
==== Networking Layer ==== 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. ==== Application Layer Services ==== 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:/// that brings you a secret code in the message's payload, * GET method for coap:///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