ESP32-S3 Edge DTU Development | Obeita
Delivered project. The completed hardware and software met the customer’s agreed requirements in testing. Specifications for a new project must be agreed separately.
Obeita completed and delivered an ESP32-S3 edge DTU project that brought serial communication, discrete signals and network access into one hardware and software scope. Customer requirements and the contract defined the work, followed by design, physical testing and delivery. The case centres on coordinating field interfaces with a 24 V board architecture.
Defining the field-interface job
The project needed more than an undifferentiated serial-to-network connection. Its documented architecture combines RS485 and TTL communication with optocoupler inputs, relay outputs and a CAN transceiver path. Requirements definition separated the electrical interface from the application behaviour expected from it.
That distinction matters particularly for CAN and relay control. A transceiver establishes a physical bus connection; application identifiers and frame handling belong in firmware. Relay outputs also require a defined relationship between their drive circuitry, coil supply and intended load.
Coordinating board design and firmware
Obeita carried out the hardware and software design for the contracted edge DTU. The documented network architecture pairs ESP32-S3-WROOM-1U Wi-Fi with a CH390 SPI Ethernet controller. RS485/TTL-to-TCP forwarding is the base integration direction, while a USB command-line terminal is a local configuration option.
The board’s documented power and interface arrangement uses SGM6232 to convert the 24 V supply to 3.3 V, alongside PC817 input paths and ULN2003-driven HF46F-024-HS1 relays. The relay design uses a 24 V coil; substituting a 12 V relay requires hardware review of coil supply, drive current and the output circuit. Additional edge logic, cloud payloads and CAN application protocols remain features to specify individually for a new project.
Cabinet integration considerations
The architecture includes TVS components on RS485, CAN and power paths, with 3.81 mm data terminals and 5.08 mm power terminals. A printed enclosure with an added rail bracket is the documented cabinet-mounting direction; enclosure clearances and mounting arrangements must follow the selected assembly. Protective components alone do not establish an immunity rating.
Documented architecture and configuration
The table records the documented architecture, configuration directions and selection boundaries for this case. Optional items, firmware-dependent choices and expansion directions are not independent guarantees that every listed option was delivered. The agreed project hardware, software and functional scope define the actual delivery.
| Item | Configuration |
|---|---|
| Main module | ESP32-S3-WROOM-1U |
| Network controller | CH390, 10/100 Ethernet; Wi-Fi |
| Serial buses | 2 × RS485; 1 × TTL |
| CAN | 1 × SIT65HVD232DR transceiver path |
| Discrete I/O | 2 optocoupler inputs; 2 relay outputs |
| Supply design | 24 V DC; SGM6232 conversion |
Delivery outcome and test scope
The contracted edge DTU hardware and software were completed and delivered. Physical functional testing confirmed that the project met the customer’s requirements.
The result covers the agreed project functions. It does not imply support for every CAN protocol, unrestricted relay loads, a certified immunity level or implementation of all possible cloud and edge extensions.
Discuss a similar project
For a similar ESP32-S3 edge DTU, send Obeita the serial device protocols, required CAN messages, input signal types, relay loads and available cabinet supply. We can use these to define the interface and application scope together.