It will come with a cable that does that. You can get a micro HDMI to HDMI cable and either splice that yourself or get an HDMI breakout board and wire it up that way if you want to change the length, though.
-
Save 20% on ALL SFF Network merch, until Dec 31st! Use code SFF2024 at checkout. Click here!
USB2. There's no benefit to USB3 and most people have lots of free USB2 headers on their boards. At the very least you'll be able to program it with MPLAB X using the C language, but I would like to make it Arduino-compatible if I can manage to do so.
Then you get a few presets that you can set with a small command line tool or a GUI tool. C is very easy when it's just about controlling LEDs, though 
K, I am probably just going to change the shade of green everyday...Then you get a few presets that you can set with a small command line tool or a GUI tool. C is very easy when it's just about controlling LEDs, though
Yah, you have any estimate on price and production and production quantity?Yeah that will absolutely be possible without re-programming it
No, I don't even know where I'll get the casing machined, still have to search for possible manufacturers.
Have you thought about having your unique (and very cool) looking iF logo etched on the button face?
I did indeed, but there are two issues with it. First, if you have a case that supports multiple orientations like the S4 Mini, the logo will be on its side some of the time. And second, I don't think many people want branding on the front of the button. It's supposed to be a minimal piece that fits into every case and hopefully enhances either look, functionality or both.
What I'd rather do is put it on the back of the button, but that space might have to be used for compliance logos.
It would also require me to design the slider of the button as to not rotate. That can be done, but it makes the two pieces its made from more complex than they need to be. I might still do that anyway to make them more stiff, but the main two problems remain.
Maybe we should go into some detail about how those RGB LED Strips work in the first place, and how LED control works in my button.
FIrst off, this is a schematic of a bog-standard RGB LED Strip with 5050 RGB LEDs (resistor values might vary):
Image courtesy of Adafruit
The four contacts you get on each strip are +12V, RED, GREEN and BLUE, as you might imagine. Now, to drive these, you would power the +12V and then pull the contacts for the colours to ground. To change the brightness, you can either use analog voltage control or PWM. Analog voltage control means that you set the colour pin to a voltage lower than 12V. For example, you could set it 9V, then the voltage across the LEDs would be 3V, and they would be less bright. This requires relatively complex circuitry to do and the results can vary depending on the parameters of the LEDs, so generally PWM is more often used. This means that you quickly turn the strips on and off, and the ratio between on- and off-time determines the brightness.
So, you might conclude that you could just use three GPIO pins from my button to control the three colour pins and power the +12V from your PSU. However, this is not necessarily correct. The current flowing through the +12V pin is equal to the combined current of the three colour pins, according to Kirchhoff's Current Law. The spec sheet of my microcontroler mentions an absolute maximum drive and sink current of 50mA for each pin. So, if the total current draw of the strip goes over 150mA, the micro could blow up, and that is not an exaggeration. In general, I would want to keep the current flow much lower than that, the maximum I'd go for is half of the absolute maximum, so about 75mA. So, how much current does flow through such a strip?
Again, Adafruit has great resources on this, and according to them, a single segment (that's three RGB LEDs or about 10-5cm of strip) pulls approximately 60mA total. That would be fine, no problem. Even if the actual draw is a little higher, we're on the safe side. Theoretically, even two segments would work at 120mA, but that'd already be too close to the upper limit in my eyes, and remember that other manufacturers stips could draw more than the ones from Adafruit. The LEDs inside my Button will never draw more than 30mA total, even when the ring is set to white at 100% brightness (the real number is a little lower but I can't look it up right now, I think it's 23mA).
To get away with a higher current that allows long strips to be powered (for example the 2m that Asus AURA boards can handle), driving transistors would be required, which are way too large to fit inside the button. You could easily rig that up yourself or annoy me enough to make an external solution, but at that point I feel it would be more sensible to make a small LED strip controller a separate product.
Thanks for the extensive reply. I'm lacking in electronic engineering knowledge that I don't know much about this stuff. Though it does seem like an interesting feature to be able to combine case RGB LED lighting with the RGB LED lighting in your button or just as well be completely seperated. With an additional controller ofcourse !
Do you have any plans for this, maybe in the future after the RGB button is finished ?
Do you have any plans for this, maybe in the future after the RGB button is finished ?
Yes, certainly! Well not plans strictly, but ideas on how to implement it. Ideally, I'd want to do something simple like ASUS AURA, just not as tacky.
I mean, look at this:
It's super simple. On the left you have all the devices, on the right you have the functionality for this device. Choose colour and effects, and whether to sync the effect between all the devices, done. I'm already thinking about ways to implement this in a way that makes it flexible enough to support any kind of RGB-lit hardware, but a simple USB-to-LED-strip controller is certainly one of the first possible candidates.
Maybe the blinkstick software would work for this as well? Haven't looked into it that much, but it seems like a good baseline.
I mean, look at this:
It's super simple. On the left you have all the devices, on the right you have the functionality for this device. Choose colour and effects, and whether to sync the effect between all the devices, done. I'm already thinking about ways to implement this in a way that makes it flexible enough to support any kind of RGB-lit hardware, but a simple USB-to-LED-strip controller is certainly one of the first possible candidates.
Maybe the blinkstick software would work for this as well? Haven't looked into it that much, but it seems like a good baseline.
Small addendum: You could control an addressable LED strip with my button, though. Power and data are sent separately and the button would only supply the control data. That would work.
I just noticed, did you ever think to do RGBW instead of RGB? What would have been the problems?
Similar threads
