391 replies to this topic

[vrumor]

I ran a wire between them, its still white. What firmware should I have on here? I have this TeensyStripController 1.02 1601021351.hex. I was using the fast one, but there is no difference between the 2. 

 

edit: Ok progress I think. I power cycled the teensy and the LEDs all turned off and I had a steady every 2 seconds blink. Then I started a table, I saw the indicator LED on the teensy flash really quickly like it was sending data, then it stopped and its blinking twice every 2 seconds now. 

 

And just like that, it all works. Awesome, thanks man.

Edited by vrumor, 29 August 2019 - 10:30 PM.

[Phazer51]

And just like that, it all works. Awesome, thanks man.

 

The addressable LED effects in some of these games are spectacular.  Good to see you've got things working.

 

Kudos to the guys who code this stuff and make it happen (DDH69, TerryRed, just to name a few).

[vrumor]

Are they specific? I seem to recall watching a vid a year or 2 ago about the LEDs following the ball when you launch it. 

[Phazer51]

Are they specific? I seem to recall watching a vid a year or 2 ago about the LEDs following the ball when you launch it.

Depends on the table.

Try Medeival Madness and Masters of the Universe (for an amazing light show).

[vrumor]

Played both, you are correct, pretty incredible light show. I do have a qucik question. What are the difference between the firmwares for the teensy? If I used the fast blink firmware, does it make a difference? does it even work? Dont wanna try it in case somehow I break something lol.

Edited by vrumor, 30 August 2019 - 12:53 PM.

[Phazer51]

Played both, you are correct, pretty incredible light show. I do have a qucik question. What are the difference between the firmwares for the teensy? If I used the fast blink firmware, does it make a difference? does it even work? Dont wanna try it in case somehow I break something lol.

That I don't know.  I only used the original (probably older) firmware when I set things up in 1/19.  It is now working for me, so I'm not messing with the Teensy module.

[MajorFrenchy]

Played both, you are correct, pretty incredible light show. I do have a qucik question. What are the difference between the firmwares for the teensy? If I used the fast blink firmware, does it make a difference? does it even work? Dont wanna try it in case somehow I break something lol.

For instance the beta firmware did not work on my cab. ( tested for a month ) and when I flashed firmware alpha it worked.

Sent from my SM-G965W using Tapatalk

[DaBanan1]

Hi,

I'm about to add some LED strips to left and right PF, eventually also a matrix to the back of the cabinet. Unfortenly I have run into a problem that I hope anyone has a quick answer to. Followed the FAQ and suggestions in this thread, but no luck.

Using a Teensy 3.2 and Octo2811 with a CAT6. Everything works fine with a 60 LED-strip but when connecting it to a 144 LED-stip it only fires up the first lights in the strip, to low power?

For now Im just testing this trough the basic test in the arduino software.

The LED-stirp with 60 only has 3 connection points, ground, power and signal. The 144 LED-strip has 6 connections (two I know is for extra power) but im not sure if the green or the yellow is signal or both? Pretty confused about this and appreciate a point in the right direction

Someone did sent me this picture, that shows the cable Im trying to use, but the instructions seams to be gone.

https://www.pjrc.com...to28_apa102.jpg


I'm trying to get these to work:
https://www.adafruit.com/product/2241

https://www.adafruit.com/product/2736




Thanks!

[MajorFrenchy]

I made a guide a while back. You should find all your Answers

https://www.mameinab...hardware/teensy

Sent from my SM-N960W using Tapatalk

Edited by MajorFrenchy, 03 October 2019 - 05:35 AM.

[DaBanan1]

I made a guide a while back. You should find all your Answers

https://www.mameinab...hardware/teensy

Sent from my SM-N960W using Tapatalk

 

Thanks, great guide! Unfortunately, the problem I'm having is that the LED strip has four connection points. GND, 5V, DATA and guessing the fourth (Ci) Clock input. So is there a solution where "Ci" should be connected, or can Teensy not handle this?

 

As I explained in the last post, everything works fine with the LED-strip that has three connection points, but it only has 60 LEDs. Sure...I could settle here and use that LED-strip, but what is the fun in that Was hoping to use the strip with fewer LEDs to under cab lighting. Also, the 144 LED-strip was not cheap so don't want to give it up yet

[DaBanan1]

Think I know now that this will not work with that type of LED strip. Got some info that the stirp doesn't use the same protocol as WS2812B,  and I need to get another LED stirp with just one Data. 

[dom69]

hi all, much more convenient for connection ...



https://techizy.fr/i...troller=product

[MikePinball]

hi all, much more convenient for connection ...

 

As we are now discussing hardware options, the Oak Micros Pinball Addressable LEDs (PAL) product is cheaper at $35. The detachable screw connectors together with the test button make this board very convenient.

 

[Bushav]

What effect are you guys assigning to your speaker RGB led’s?

I’m guessing PF back effects MX and/or PF back strobe MX? Maybe PF back flasher MX?

I am just attempting to add addressable LEDs this week. Another question. When I downloaded MRJ’s Teensy firmware file it had quite a few files to choose from. I chose the “BlinkFast32” file thinking it is the one since my teensy is a 3.2. Am I correct?

Thanks
Lane

[MikePinball]

I am just attempting to add addressable LEDs this week. Another question. When I downloaded MRJ’s Teensy firmware file it had quite a few files to choose from. I chose the “BlinkFast32” file thinking it is the one since my teensy is a 3.2. Am I correct?

 

The Blink* code just blinks the LED on the Teensy.

 

Assuming you have installed TeensyDuino from PJRC, then you need the following files from GitHub TeensyStripController repository:

• OctoWS8211ext.h
• OctoWS8211ext.c
• TeensyStripController.ino

There are several tutorials on this subject:

• Scottacus (this topic)
• MajorFrenchy

Edited by MikePinball, 13 February 2020 - 03:00 PM.

[MajorFrenchy]

I had no ideas that all pictures were removed from the guide as i switched website. ( i was linking the photos from my site ) 

i just re-uploaded the pictures to the guide. 

 

Addressable LED Guide

[Bushav]

Thanks for response guys.  I got it working yesterday after about 20 hours of trying!  It was a rewarding win.  I still want to know what lights you guys are assigning to your speaker grill lighting within the DOF Configuration Tool. I choose PF Back Flashers MX, PF Back Strobe MX and PF Back PBX MX.  I combined them and assigned combination to my right and left speaker grills.  It is working great but I am curious if others are doing something different.

 

Lane

[ViNsEDj]

Hi guys, need help. I´ve followed Frenchy tuto but with no luck (at all). My leds are working (just trying with the Matrix), with the TestLed program in arduino. But no luck in Pinball X neither VPX. I´ve notice that DirectOutput.log is not showing anything, no writting. Also, when executing a table, in Plugins, DOF appear, but when I double click and the configuration appears, all gaps say "no global configuration file found...etc" and the matrix do nothing.

 

I´ve tried everything and tons of times, dof tool etc etc, please, any clue on whats going on? Thanks a lot!!!

[DocDoom1979]

Have you followed those steps from Major Frenchys guide?;

 

 

Once your cabinet.xml is set, it will be placed in the C:/DirectOutput/Config

 

Run Global Config in the DirectOutput folder and point to your cabinet file. You will then save as GlobalConfig.xml in the C:/DirectOutput/Config.

 

 

You will need to save as again and name it GlobalConfig_B2S.Server and save it in the same location.

 

***** Extra ******

if you wish to have the dot matrix effects enabled you will have to Save as a 3rd time and call the file GlobalConfig_PinballX. 

 

Run RegisterDirectOutputcomobject as administrator and you should get a positive confirmation that DOF is running.

 

I actually only copied the GlobalConfig_B2S.Server from the examples folder into the config folder and overwrote it with the Global Cofiguration Editor to get it runnning.

[jlvandusen]

Hello

I too am embarking on the LED trek...  What is occuring is I got the left playfield and partial Matrix lit at pure white... I soldered pins 15 and 16 as requested... 

I have tried both Alpha and Beta HEX codes... when loading tables such as medieval madness etc... no lights.

i have a teensy with a WS2811 setup

I visited the DOF Config online tool and set it up as suggested.

Downloaded the directoutputconfig40 = my Sainsmart 8 port relay which works.

Downloaded the directoutputconfig30 = the teensy WS2811 unit configured with the combined toys.

 

My Hardware assignments:

I have a PF_right (60leds)

PF_left (60leds)

PF_Matrix (back) (256leds or 8x32)

 

I assigned Orange (pin1/2) = PF_RIght

I assigned Blue (pin3/4) = PF_left

I assigned Green (pin5/6) = PF_Matrix

 

my cabinet.xml is

<?xml version="1.0"?>
<Cabinet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>XtensionCabinet</Name>
<OutputControllers>

<TeensyStripController>
<Name>LedStripController</Name>
<NumberOfLedsStrip1>60</NumberOfLedsStrip1>
<NumberOfLedsStrip2>60</NumberOfLedsStrip2>
<NumberOfLedsStrip3>256</NumberOfLedsStrip3>
<NumberOfLedsStrip4>0</NumberOfLedsStrip4>
<NumberOfLedsStrip5>0</NumberOfLedsStrip5>
<NumberOfLedsStrip6>0</NumberOfLedsStrip6>
<NumberOfLedsStrip7>0</NumberOfLedsStrip7>
<NumberOfLedsStrip8>0</NumberOfLedsStrip8>
<ComPortName>COM4</ComPortName>
</TeensyStripController>


  
</OutputControllers>

<Toys>
   
<LedStrip>
  <Name>Sideboard Right</Name>
  <Width>1</Width>
  <Height>60</Height>
  <LedStripArrangement>TopDownRightLeft</LedStripArrangement>
  <ColorOrder>GRB</ColorOrder>
  <FirstLedNumber>60</FirstLedNumber>
  <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
  <OutputControllerName>LedStripController</OutputControllerName>
</LedStrip>
      
<LedStrip>
  <Name>Sideboard Left</Name>
  <Width>1</Width>
  <Height>60</Height>
  <LedStripArrangement>BottomUpLeftRight</LedStripArrangement>
  <ColorOrder>GRB</ColorOrder>
  <FirstLedNumber>120</FirstLedNumber>
    <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
  <OutputControllerName>LedStripController</OutputControllerName>
</LedStrip>

<LedStrip>
  <Name>BackBoard</Name>
  <Width>32</Width>
  <Height>8</Height>
  <LedStripArrangement>TopDownAlternateLeftRight</LedStripArrangement>
  <ColorOrder>GRB</ColorOrder>
  <FirstLedNumber>256</FirstLedNumber>
  <FadingCurveName>Linear0To16</FadingCurveName>
  <OutputControllerName>LedStripController</OutputControllerName>
</LedStrip>

<LedWizEquivalent>

   <Name>LedWizEquivalent 30</Name>
    <Outputs>

    <LedWizEquivalentOutput>
    <OutputName>Sideboard Right</OutputName>
    <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>

    <LedWizEquivalentOutput>
    <OutputName>Sideboard Left</OutputName>
    <LedWizEquivalentOutputNumber>4/LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>

    <LedWizEquivalentOutput>
    <OutputName>BackBoard</OutputName>
    <LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>
	
    </Outputs>
    <LedWizNumber>30</LedWizNumber>
</LedWizEquivalent>
  
</Toys>

</Cabinet>

My Globalconfig_B2SServer.xml  is

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 3.1.7011.27968: 2020-05-17 18-00-12-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>10</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <PacLedDefaultMinCommandIntervalMs>10</PacLedDefaultMinCommandIntervalMs>
  <IniFilesPath>D:\Emulators\DirectOutput\Config</IniFilesPath>
  <CabinetConfigFilePattern>D:\Emulators\DirectOutput\Config\Cabinet.xml</CabinetConfigFilePattern>
  <TableConfigFilePatterns />
  <EnableLogging>true</EnableLogging>
  <ClearLogOnSessionStart>true</ClearLogOnSessionStart>
  <LogFilePattern>.\DirectOutput.log</LogFilePattern>
</GlobalConfig>