zimmer62 Posted June 6, 2019 Share Posted June 6, 2019 So I have boatloads of Addressable RGB leds, and the wiring in my opinion is easier than having a bunch of home runs to my PACLED64... So solving two problems I'd like to run the addressable LED's that I have already. The question I have is: Can I single out just one or two LED's in a "strip" to have them act as a non RGB led? Example: Start Button, Launch Button, Fire Button, Coin LED's etc... I've tried setting them up as a 1Wx1H LED strip, but it occurred to me there would be no where to set the color... I guess I was hoping to find a spot to set the color of a single addressable RGB led to emulate a single color LED. The way I'd picture it looking is something like the attached image, then in the Cabinet.xml file there would be a way to assign a color to the 1x1 toy. I couldn't find anything while searching so forgive me if this has been asked and answered. Link to comment Share on other sites More sharing options...
Rappelbox Posted June 7, 2019 Share Posted June 7, 2019 For addressable LEDs you can only use MX ending options in the dof config tool. Others won’t work. Link to comment Share on other sites More sharing options...
zimmer62 Posted June 7, 2019 Author Share Posted June 7, 2019 It seems like this could be a feature request at some point. As cheap and as easy to come by the Addressable LED's are, I'm imaging a table where all LED's are controlled by a teensy and daisychained LED's Link to comment Share on other sites More sharing options...
dondi Posted December 8, 2019 Share Posted December 8, 2019 I have been thinking about something like this as well, calling it, a "Universal Button Indicator". I envision something like a strip (or a mirrored set of two) of WS2812Bs (daisy-chained off the usual addressables and segmented in the Cabinet.xml file), maybe installed somewhere in line-of-sight in the backglass/speakerpanel, or maybe a single WS2812B LED installed in the apron giving the player a visual cue of button status; i.e.: Attract Mode MX = ON White AT0 AL0 AW100 AH100 Coin MX = ON Yellow Blink AT0 AL0 AW100 AH100 Start Button MX = ON White Blink AT0 AL0 AW100 AH100 Extra Ball MX = ON Green Blink AT0 AL0 AW100 AH100 Fire MX = ON Red Blink AT0 AL0 AW100 AH100 Launch Button MX = (some cool MX effect like the PF Right MX) Authentic Launch Button MX = ON Lime Blink AT0 AL0 AW100 AH100 Well, there are several obstacles to the above as with the current status of DOF, as I see it (I'm still new to this, but currently going-through the docs). There are no addressable MX types for these buttons I think the above status "modes" would need to stacked into a Custom Combo and Assigned to a currently-non-existent toy (i.e., Button Status Toy MX) I think also the challenge would be to have these global without modifying individual tables (I have no experience in table creation, so I have no idea, I am ignorantly assuming that the event calls to the above are already present) I think this would be a cool little thing for our tables if it is possible. Link to comment Share on other sites More sharing options...
christian0007 Posted January 22, 2020 Share Posted January 22, 2020 First post here! You got me out of lurking with your question and I might have something for you in a short time (or even shorter time if you can compile code). I'm currently in the planning phase of my pincab build and I bougth these individual WS2812 https://fr.aliexpress.com/item/32805045364.html?spm=a2g0s.9042311.0.0.4f146c37TrJzBd thinking that I could do something like this Neopixel tutorial (https://learn.adafruit.com/neopixel-arcade-button/assembly) to light all of my buttons. I didn't want to buy a LedWiz (shipping is so expensive to Québec), so I figured I'd use the Teensy I needed for the led strip for all the button lights in my cab. I ran into the same issue as you, single RGB led and lamp could not be assigned to a ledstrip as it was expecting an area effect. So I had no way of having my clear buttons light up green for the Start button, red for exit.... So I coded new toys! This is my fork of DirectOutput: https://github.com/donchristian0007/DirectOutput I added 2 toys: LedStripLamp and LedStripRGBLed. They basically are 1 led long ledstrip that accept the original toy (non ledstrip) commands. In the LedStripLamp you can specify the color you want. This is my cabinet.xml file (for testing). Keep in mind at this moment I only conducted small scale tests, but it seems to work fine. I wanted to test more before doing a pull request to the original DirectOutput github. <?xml version="1.0"?> <Cabinet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <Name>Christian0007</Name> <OutputControllers> <TeensyStripController> <Name>LEDStripController</Name> <NumberOfLedsStrip1>130</NumberOfLedsStrip1> <NumberOfLedsStrip2>0</NumberOfLedsStrip2> <NumberOfLedsStrip3>0</NumberOfLedsStrip3> <NumberOfLedsStrip4>0</NumberOfLedsStrip4> <NumberOfLedsStrip5>0</NumberOfLedsStrip5> <NumberOfLedsStrip6>0</NumberOfLedsStrip6> <NumberOfLedsStrip7>0</NumberOfLedsStrip7> <NumberOfLedsStrip8>0</NumberOfLedsStrip8> <ComPortName>COM3</ComPortName> <ComPortTimeOutMs>5000</ComPortTimeOutMs> </TeensyStripController> </OutputControllers> <Toys> <LedStripLamp> <Name>Start Button</Name> <ColorOrder>RGB</ColorOrder> <Color>#00FF00</Color> <LedNumber>129</LedNumber> <FadingCurveName>Linear</FadingCurveName> <OutputControllerName>LEDStripController</OutputControllerName> </LedStripLamp> <LedStripLamp> <Name>Coin Button</Name> <ColorOrder>RGB</ColorOrder> <Color>#FF0000</Color> <LedNumber>130</LedNumber> <FadingCurveName>Linear</FadingCurveName> <OutputControllerName>LEDStripController</OutputControllerName> </LedStripLamp> <LedStrip> <Name>PF Back</Name> <Width>8</Width> <Height>16</Height> <LedStripArrangement>TopDownAlternateRightLeft</LedStripArrangement> <ColorOrder>RGB</ColorOrder> <FirstLedNumber>1</FirstLedNumber> <FadingCurveName>Linear0To224</FadingCurveName> <OutputControllerName>LEDStripController</OutputControllerName> </LedStrip> <LedWizEquivalent> <Name>LEDStripControllerEQ 1</Name> <LedWizNumber>80</LedWizNumber> <Outputs> <LedWizEquivalentOutput> <OutputName>Start Button</OutputName> <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber> </LedWizEquivalentOutput> <LedWizEquivalentOutput> <OutputName>Coin Button</OutputName> <LedWizEquivalentOutputNumber>2</LedWizEquivalentOutputNumber> </LedWizEquivalentOutput> <LedWizEquivalentOutput> <OutputName>PF Back</OutputName> <LedWizEquivalentOutputNumber>3</LedWizEquivalentOutputNumber> </LedWizEquivalentOutput> </Outputs> </LedWizEquivalent> </Toys> <Colors/> <Curves/> <AutoConfigEnabled>true</AutoConfigEnabled> </Cabinet> Let me know what you think! I'll take any suggestion, but not sure I'll have time to implement them quickly! Link to comment Share on other sites More sharing options...
AussieM8 Posted September 24, 2021 Share Posted September 24, 2021 I came across this while searching for a solution to using a single addressable LED in DOF and wondering whether there was any further progress in the last year? Link to comment Share on other sites More sharing options...
jarr3 Posted September 29, 2021 Share Posted September 29, 2021 Yes! This sounds really interesting. How was your experience with it? Did it work out well? /Richard Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now