Use ESP-01S as WiFi to UART bridge
a project by iivanov
Updated over 2 years ago. 4 hacker ♥️. 1 follower.

Project Description

Currently with just with 8 RPi devices cables occupy most of the space in the 'rack. Reduce the clutter with replacing USB to UART converter with WiFi to UART ones.

Goal for this Hackweek

  • Devices are ordered
  • Prepare device programmer
  • Study platform
  • Create clean WiFi to UART bridge implementation

Resources

Result

UART WiFI

Join this project

Looking for hackers with the skills:

embedded esp espressif wifi uart electronics c

This project is part of:

Hack Week 21

Activity

  • over 2 years ago: mbrugger liked this project.
  • over 3 years ago: radolin liked this project.
  • over 3 years ago: clin liked this project.
  • over 3 years ago: bschmidt liked this project.
  • over 3 years ago: iivanov started this project.
  • over 3 years ago: iivanov added keyword "c" to this project.
  • over 3 years ago: iivanov added keyword "electronics" to this project.
  • over 3 years ago: iivanov added keyword "uart" to this project.
  • over 3 years ago: iivanov added keyword "wifi" to this project.
  • over 3 years ago: iivanov added keyword "espressif" to this project.
  • over 3 years ago: iivanov added keyword "embedded" to this project.
  • over 3 years ago: iivanov added keyword "esp" to this project.
  • over 3 years ago: iivanov originated this project.


    • Comments

    • radolin
      over 3 years ago by radolin | Reply

      I have also thought about this problem, but think WiFi and the ESPs may not be very reliable. I have my eye on a new cheap USB to 8 UART chip: http://www.wch-ic.com/products/CH348.html

      • iivanov
        over 3 years ago by iivanov | Reply

        Sounds Okayish, but it will still require lot of wiring and soldering.

    Similar Projects

    pudc - A PID 1 process that barks to the internet by mssola

    Description

    As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:

    • The backend is written in a mixture of C and RISC-V assembly.
    • The backend is actually PID1 (for real, not within a container).
    • We poll and parse incoming HTTP requests ourselves.
    • The frontend is a mere HTML page with htmx.

    The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.

    I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.

    Goals

    • Have a better understanding of different Linux features from user space down to the kernel internals.
    • Most importantly: have fun.

    Resources