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

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


    Port OTPClient to GTK >= 4.18 by pstivanin

    Project Description

    OTPClient is currently using GTK3 and cannot easily be ported to GTK4. Since GTK4 came out, there have been quite some big changes. Also, there are now some new deprecation that will take effect with GTK5 (and are active starting from 4.10 as warnings), so I need to think ahead and port OTPClient without using any of those deprecated features.

    Goal for this Hackweek

    • fix the last 3 opened issues (https://github.com/paolostivanin/OTPClient/issues/402, https://github.com/paolostivanin/OTPClient/issues/404, https://github.com/paolostivanin/OTPClient/issues/406) and release a new version
    • continue the rewrite from where we left last year
    • if possible, finally close this 6 years old issue: https://github.com/paolostivanin/OTPClient/issues/123