home.social

#waveshare — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #waveshare, aggregated by home.social.

  1. Achei a ideia do #PocketTerm35 da #Waveshare interessante, apesar da ausência de um #trackball, mas a tela de 640x480, apesar de teoricamente adequada, reforça o retrocesso acumulado ao longo de décadas: apesar de todo o blá, blá, blá sobre convergência e dispositivos móveis, a realidade é outra, com desktop environments pesados demais para rodar em SBCs com 1 GB ou 2 GB de RAM (as poucas especificações minimamente acessíveis nos dias de hoje) e, em geral, pouca oferta de software convergente para algo além de relógios, cronômetros e calendários.

    O #GNOME, por exemplo, ainda tem problemas para exibir a grade de aplicativos a 720p, caso o scaling seja de 125% ou maior para tornar a leitura mais fácil em tela pequenas (o que, na prática, reduz a resolução) e, em linhas gerais, parece muito pouco testado para cenários do tipo. E, claro, o GNOME não é exatamente o tipo de ambiente gráfico que você vai rodar num dispositivo, seja ARM, seja x86, com 1 GB ou 2 GB de RAM.

    Mesmo aplicativos mais antigos e fora dos holofotes, como #Abiword e #Gnumeric realisticamente esperam 800x600 de resolução. É compreensível, mas problemático. Simplesmente não temos quase nada que rode em 640x480.

  2. I finally wrapped up my custom mini #cyberdeck build last night. Uses a #waveshare ESP32-S3 touchscreen and a mini "OS" built using #circuitpython I wrote a blog post about the build (including links to download the #3dprint models and code) andywarburton.co.uk/post/gr3ml

    #electronics #diy #maker #esp32 #3dprinting

  3. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  4. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  5. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  6. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  7. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  8. Which gen AI is best suited for Home Assistant and ESP32 wibe coding? I am getting frustrated with both M$ CoPilot and Claude Sonnet 4.6. I have two small projects. One for temp display and another for Nordpool electric prices now and two hours ahead. #haos #esp32 #waveshare #wibecoding #AI

  9. Lilbits: Android 17 Beta 1, Intel Arc B370 iGPU performance, and a $27 RLCD display with an ESP32-S3 chip

    Waveshare is now selling a cheap dev board that combines a 4.2 inch, 400 x 300 pixel RLCD sunlight-readable, black and white “E-paper-like” low-power display with an ESP32-S3 processor featuring support for WiFi and Bluetooth.

    Available with a battery for $27 or without one for $25, the kit could be an interesting alternative to E Ink for simple signage or other applications. There are also […]

    #android #android17 #google #lilbits #microsoft #pantherLake #rlcd #secureBoot #waveshare Read more: liliputing.com/lilbits-android
  10. This dev board features and ES32-S3 chip and a 4.2 inch, 400 x 300 pixel RLCD sunlight-readable "E-paper-like" black and white display. Available with or with an 18650 battery for $27 or without battery for $25. hackster.io/news/waveshare-s-n

  11. I adapted the #I2S Pinout for the #DECtalk Mini from the #MAX98357A Board to my NanoPi Nanohat #PCM5102A
    Sounds much louder as the PWM-Version :)
    The Board is a #Waveshare RP2040 Zero

  12. Wen es interessiert, hier die Anleitung, wie man 3,2 Inch GPIO #tft Displays von #Waveshare und Clone erfolgreich am #Raspberrypi 3 hinbekommt unter #Debian13 #Trixie. Eine Version für 3,5 Inch wird folgen. Erst danach werde ich mich um den PI4 und ggfls den PI5 kümmern. Allerdings finde ich den PI4 und PI5 für solche Displays eher ungeeignet, weil bei den Boliden sollte man schon HDMI oder besser noch DSI Displays verwenden. Pi1, Pi2 und Pi Zero kommt auch noch. Grund dass die Displays bisher nicht mehr funktionierten war, dass der fbcp obsolete Libs verwendet und es keinen Ersatz gibt. Also habe ich ihn rausgeworfen und manuell die Buffer gesetzt dank con2fbmap.
    github.com/katzenjens/lcd32

  13. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  14. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  15. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  16. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  17. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  18. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  19. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  20. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  21. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  22. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  23. Welcome to KAMPi! My Self-Built Digital Camera

    Hello everyone! I have always wanted to build my own digital camera. But not just any digital camera, one I would actually use like a regular point-and-shoot camera. I wanted something that would give me traditional feel, but still shoot in 4K. A tall order for sure, and to top it all off, I wanted to build everything myself. Well the time has come. . . Please join me in welcoming KAMPi! Check out my build below.

    Why KAMPi?

    KAMPi is short for “Kampay” which is Tagalog slang for “Kanpai” the Japanese word for cheers. It also sounds like CAMPi another way of saying Pi Cam, which is exactly what it is – a digital camera built using a Raspberry Pi mini computer.

    What’s Inside?

    I built KAMPi from the ground up: selected, wired, and soldered the hardware electronics, 3D printed the parts, and prepared the software.

    For the computer internals, I chose to use a Raspberry Pi Compute Module 5 which rides on a Waveshare Nano A. The camera imager and lens are from Raspberry Pi as well, the Raspberry Pi High Quality Camera with the 16mm Telephoto Lens. For the display I used a Pimoroni HyperPixel 4.0″ Hi-Res Display. The display is connected to the Waveshare Nano A via GPIO pins (the header of the Nano I soldered myself). Everything is packed together in a tight package shown above.

    For the power electronics I chose to use a Pimoroni LiPo SHIM I purchased from Adafruit. I wired it up with a on/off switch and connected it to a USB-C plug.

    For the trigger mechanism I chose to use Adafruit’s KB 2040 electronic board due to it’s small form factor, and also that it works over USB-C / USB serial. I also chose to use the KB 2040 because the HyperPixel 4.0 uses all the GPIO pins of the Waveshare Nano A and USB-C / USB serial seemed like a more straightforward alternative. Alternatively I could have used I2C, via the HyperPixel 4.0, but I didn’t have enough time to go that direction before the convention. The trigger itself is an illuminated pushbutton switch also from Adafruit.

    I’m no expert in 3D printing and I originally wanted the form factor to be smaller. But since the camera cable stuck out from the top, I needed to make extend the base.

    So I designed and 3D printed a cap portion to hold it all together.

    I even added a hinge and latch lock to for easy access.

    For the software, I wanted something simple. I’m running python script to take the photos. One thing to note is that the camera does not have any autofocus (which is exactly how I wanted it). That meant I needed to see what I’m shooting before taking the photo. I added a preview in the software, so I could focus the lens, and then take the shot.

    The desktop above shows the camera python script and the folder where the photos are saved. You can also see the Circuitpython mounted “disk” of the KB 2040 on the desktop. I’m also a space nerd so I chose a James Webb galaxy image as a backdrop to show off the beautiful Pimironi display. I included a fun logo and added a nice rectangle so I could easily see the program icons on the desktop too.

    KAMPi in Action

    KAMPi is so new, I haven’t been able to test it in the wild yet. But here are some raw unprocessed photos from my home test shots.

    https://www.instagram.com/reel/DMR6OegOWSn/?utm_source=ig_web_copy_link&igsh=MzRlODBiNWFlZA==

    More to come from Opensaucelive!*

    Tomorrow is Opensaucelive 2025 and I thought what better place to test and share my build there. Wow, I’m so excited to share KAMPi with everyone at Opensauce. If you see me, please do say hello. I’ll also upload some photos from KAMPi at Opensauce below:

    [*UPDATED July 20, 2025] See above sample photos I took at Opensaucelive 2025 using KAMPi. I chose the sharpest in focus images to share. Since it was my first time shooting with it, many of the photos came out blurry – which was exactly what I was expecting! I wanted KAMPi to emulate the feel of a film camera, capturing the moment. And KAMPi did just that. I’m also sure I’ll get better at taking photos with KAMPi with a litter more practice 🙂

    [*UPDATED Sept 20, 2025] Updated the description of the KB 2040 to provide additional info on why I decided to use it over I2C.

    Kampay (Cheers) for now!

    Did you like my build? Would you like to learn more about it? Let me know at the comments below!

    If you enjoyed reading this post please be sure to like, and follow us here at SKKAW.BLOG (IG: @skkaw) for more geek and pop-culture goodness.

    #Adafruit #camera #CamPi #ComputeModule5 #digitalCamera #DIY #DIYCamera #DIYDigitalCamera #KAMPi #Opensauce #OpenSauceLive #PiCam #RaspberryPi #RaspberryPiCamera #RaspberryPiComputeModule5 #RaspberryPiComputeModule5Camera #SelfMade #selfMadeDigitalCamera #selfBuilt #SelfMade #Waveshare

  24. Lilbits: Razer’s new Thunderbolt 5 docks, UGREEN’s new 25W Qi 2.2 wireless power bank

    Thunderbolt 5 supports bi-directional data transfer speeds up to 80 Gbps, or asymmetric speeds up to 120 Gbps for video output. And that makes it an even better fit for docking stations than Thunderbolt 4, which topped out at 40 Gbps. Now that PCs with Thunderbolt 5 are starting to gain traction, we’re starting to see more Thunderbolt 5 accessories. The latest are two new docking stations […]

    #arrowLake #gmkEvoT1 #lilbits #miniPc #qi #qi22 #raspberryPi #razer #razerCoreXV2 #razerThunderbolt5Dock #thunderbolt5 #ugreen #ugreenMagflow #waveshare #wirelessCharging

    Read more: liliputing.com/lilbits-razers-

  25. The original driver allocates a #framebuffer containing a single bit per pixel (that's why you can see some bitshifts in the code above). To support two colours, I need double the space. Fortunately there's already support for #BWR #eink displays in the #esphome #waveshare library, so I just need to extend WaveshareEPaperBWR instead of WaveshareEPaper and my framebuffer is magically double the size: the first half is for the black colour (as before), the second is for the red colour.
    [continues...]
  26. The original driver allocates a #framebuffer containing a single bit per pixel (that's why you can see some bitshifts in the code above). To support two colours, I need double the space. Fortunately there's already support for #BWR #eink displays in the #esphome #waveshare library, so I just need to extend WaveshareEPaperBWR instead of WaveshareEPaper and my framebuffer is magically double the size: the first half is for the black colour (as before), the second is for the red colour.
    [continues...]
  27. The original driver allocates a #framebuffer containing a single bit per pixel (that's why you can see some bitshifts in the code above). To support two colours, I need double the space. Fortunately there's already support for #BWR #eink displays in the #esphome #waveshare library, so I just need to extend WaveshareEPaperBWR instead of WaveshareEPaper and my framebuffer is magically double the size: the first half is for the black colour (as before), the second is for the red colour.
    [continues...]
  28. The original driver allocates a #framebuffer containing a single bit per pixel (that's why you can see some bitshifts in the code above). To support two colours, I need double the space. Fortunately there's already support for #BWR #eink displays in the #esphome #waveshare library, so I just need to extend WaveshareEPaperBWR instead of WaveshareEPaper and my framebuffer is magically double the size: the first half is for the black colour (as before), the second is for the red colour.
    [continues...]
  29. The original driver allocates a #framebuffer containing a single bit per pixel (that's why you can see some bitshifts in the code above). To support two colours, I need double the space. Fortunately there's already support for #BWR #eink displays in the #esphome #waveshare library, so I just need to extend WaveshareEPaperBWR instead of WaveshareEPaper and my framebuffer is magically double the size: the first half is for the black colour (as before), the second is for the red colour.
    [continues...]
  30. A few new #Microcontrollers - My wife always asks me why I need new microcontrollers, or how many microcontrollers do you need. But the answer is "because", or "why not", or "I thought we agreed it's not a good idea to ask me why"

    These all have a ST7789 LCD, but different microcontrollers, and different features.
    The #Waveshare is #ESP32C6,
    has a SD reader, #IdeaSpark is just a #ESP32 nothing extra, and the #Lilygo is a #ESP32S2 has a #OTG USB port, and SD reader, and Grove port,...

  31. Waveshare Pi5 module box turns a Raspberry Pi into a PC in a flash

    The Waveshare Pi5 Module Box is a compact aluminum enclosure that quickly turns a are Raspberry Pi 5 board into a slick-looking mini PC.
    It’s offered in three different configurations, each with a handful of extra ports that break out via a PCIe adapter board.
    The Pi5 Module Box A adds a second gigabit Ethernet port, perfect for builds like […]

    https://liliputing.com/?p=170670

    #cases #diy #enclosures #raspberryPi5 #waveshare