Welcome to Eclipse OS, a modern, modular, and scalable library for controlling Adressable LEDs in a performant yet convinent manner.
There are a lot of useful structures/classes, paradigms, and content all developed together. Hopefully you can extend to suit your needs.
Written in C++
The goal of the project comes from a need to generate unique patterns with controls similar to DMX (and hopefully compatible with DMX soon), but allowing us to create configurations at the lower level, create our knobs and controls accesible and custom per device setup, while letting maximum flexibility in sharing code among projects. This system promotes scalable development and lets me expand the featureset gradually.
This aint complex code, read it, learn about it. I write code like its made to not just work well, but be read and understood.
I see this as a generic abstract layer to handle modules for these microcontrollers without overhead. An all in one system for these microcontroller devices.
The library is broken down in a simple, modular setup to allow selective usage as best as possible. Most modules are dependent on ecore.
contains core system functionality and types. nothing in ecore has any dependencies.
- logging system
- coodinate system
- hsv color system
- floating point -> fixed point math conversion
- small math library
- range struct
- tickable interface
- timer
contains advanced generator system for creating led animations generically
- generators: generalized layer for coordinate -> output (float or color)
- noise generators (FastNoiseLite)
- processors: take in a target and perform some algorithm over time to get to it. (ex: spring, momentum, lerp)
contains io device wrappers. simple wrapper layers for:
- buttons
- gif drawing to screens
- hsv strip abstraction
a simple generic state machine. additional layer for hsv blending between states.
easy to understand wifi manager. easy way to hide secrets.
made for home assistant co
gathered from other projects, possible conversions. See credits on respective files.
These are more content specific and usually just a lot of cool presets. They are made as generically as possible to work on any project from a 1d strip on the ceiling to a 2d render dependeing on the underlying kit.
I take great pride in my work. With much of this work being the "game-systems" side of things, I found showing/reproing this full stack setup from the top down was vital for me to continue redoing/expanding these types of projects. I understand the importance of open source work and sharing knowledge, which is why this is provided.
My wish though is that you do not remake what I have made, but you make something new. I hope this is mearly a reference for the work and steps, but please, don't be a script kiddie, make something new from this, I made it so easy for ya.
I do not own any image binaries provided in this source code.
License Info is located in the license file. GNU GPLv3
A lot of work has gone to easy deployment and making this system less fragile. To reiterate, this is currently tested in the Arduino ecosystem, with goals to integrate more seamless at some point.
If terminals are scary, the ide instructions should work. i recommend the cli.
- compile.sh -> compile for raspberry pico w (use as reference, easy to change per chipset)
- upload.sh -> upload compiled project to first found device
- monitor.sh -> view serial out of first found device
I would recommend just running this in WSL for these tools.
- Install Arduino IDE
- Install RP2040 support for Arduino IDE
- Get Adafruit GC9A01 and AnimatedGif libraries in Arduino IDE
Can be downloaded + auto-setup in Arduino IDE Library Manager
- SPI Fixes (IMPORTANT)
- SPI had some bs fixes. I just modified these. Try and see if necessary as they maybe fix this soon.
- SPI.h: line 50 -> convert byte to uint_8
- SPIHelper.h: line 6 -> needed to add #pragma once
- SPI had some bs fixes. I just modified these. Try and see if necessary as they maybe fix this soon.
- A picoprobe might be preferred, although i got through all of development with only serial output (hence the nice logging library) as there is currently no way to serial output if a crash occurs. This makes a lot of sense as well an unhandled exception could occur. There is a plan to address in the todos readme.
Hopefully in future we can get these libraries linked with CMake to support this dev out of the box and improve VS support and parsing. CMake is started but untested and not working currently.
Related systems include jelly_main and afterglow
Making images to c code: https://javl.github.io/image2cpp/
Ok, so this sucks a bit, gonna be honest. This is the worst code of the project and im sorry, but it does the job.
I made images as small as possible, but then had major issues with using the transparency layers and optimized gifs.
Right now, the process I have is to go here. https://ezgif.com/repair/
Click Gifscicle unoptimize as well as ImageMagick coalesce. This can the size a lot. (+62.33%) Maybe you can just fix the code and do a PR if you want! I might at some point, but im also lazy.