391 replies to this topic

[Cue777]

. Can someone post a screenshot of their pindmd + teensy hardware id and compatible id like I did in the post here in this link?

https://forum.pjrc.c...8761#post158761

 

 

Anyone?

[Westworld]

sorry, while I'm using Teensy, I do not own PinDMD3 but the older version (PinDMD2), which works fine together.

 

In the Teensy Forum they gave you the advise to use Windows 10, which I would also recommend. I use it with VP9 and VPX, PinballX, ledstrips, B2S.

But honestly, as I don't see the issue myself, I don't know for sure that this is the solution.

 

Did you tried to contacted the vendor of PinDMD3 to check if he really uses the same hardware/vendor ID's as a teensy, which looks very strange to me.

For PinDMD2 he uses standard drivers, no real ID's, not even a certified driver (which made using it under Windows 10 a little bit more difficult and he provided 0.000 support, saying the board is not supported anymore. There are here several suggestions how to use other drivers to use PinDMD2 with Windows 10).

But as PinDMD3 is still a supported and selling product, I would assume you get some help from him, did you try?

 

If he is really using internal a Teensy device, you might overwrite the vendor ID for your Teensy, that's not easy, I never tried myself, but seems to be possible, as described in this thread (#20): https://forum.pjrc.c...-0-PRODUCT_NAME

I don't know if DOF will still find the teensy (if it only uses the Com port or also check the ID, you might need to check that with the DOF sources as well)

 

Just in case: sometimes it all depends of the order devices are listed.

If he only looks for the vendor ID, maybe he takes just the first one he find.

So you could try to rearrange the order.

Try several USB ports in your computer. I cannot tell you which one, that depends on the board.

Try to have DMD connected to USB3 and Teensy to USB2 or vice versa.

Boot the computer with DMD, wait some seconds, then plugin Teensy (just for checking). Maybe that could help as well (even it is not a real solution)

Good luck

 

Very last idea if all that fail: before DOF supported the Teensy, I was using a Teensy via ARTNET protocol (which is supported by DOF as well) to drive my ledstrips.

I connected the Teensy to an Ethernet shield and that to the pinball computer. Creating the catalog.xml was challenging, as you need to define 3 entries for each LED, that was for me around 1500. start with 10, see if that works, then write a script to create the XML.

For the Teensy I needed my own firmware, which simply was based on an ARTNET example, assigning each entry to a LED, a kind of pass thru...

The Teensy does not need to be connected via USB to the computer, it could get his power from another source (=USB power supply)

[Cue777]

 

 

Did you tried to contacted the vendor of PinDMD3 to check if he really uses the same hardware/vendor ID's as a teensy, which looks very strange to me.

For PinDMD2 he uses standard drivers, no real ID's, not even a certified driver (which made using it under Windows 10 a little bit more difficult and he provided 0.000 support, saying the board is not supported anymore. There are here several suggestions how to use other drivers to use PinDMD2 with Windows 10).

But as PinDMD3 is still a supported and selling product, I would assume you get some help from him, did you try?

 

 

I dont know who the manufacturer actually is? I contacted Paul from this site who seems to be the only one that sells them but have not heard back.

 

 

I have tried every USB port, tried a USB hub, tried a USB PCI card and all with same results.

Good luck

 

Very last idea if all that fail: before DOF supported the Teensy, I was using a Teensy via ARTNET protocol (which is supported by DOF as well) to drive my ledstrips.

I connected the Teensy to an Ethernet shield and that to the pinball computer. Creating the catalog.xml was challenging, as you need to define 3 entries for each LED, that was for me around 1500. start with 10, see if that works, then write a script to create the XML.

For the Teensy I needed my own firmware, which simply was based on an ARTNET example, assigning each entry to a LED, a kind of pass thru...

The Teensy does not need to be connected via USB to the computer, it could get his power from another source (=USB power supply)

 

No idea how to do this,   so that option is out.

[gtxjoe]

Russdx for pindmd 1,2 and 3. He is not active here any more but he is on the pinside forums. You can try to PM him there

[supermario0523]

So after researching this for a bit,  I spent the entire day yesterday programming, troubleshooting to get these to work. I followed the guide exactly, didn't skip any step

Teensy is loaded with the correct firmware, teensy is soldered and connected to daughter board with RJ45 in the right (from bottom) jack, Orange cat5 going to data and striped orange going to ground. Cabinet file edited with correct comport and ledwizequivalent coding and strip definition (I will attach cabinet code below). Globalconfig is edited. DOF online cofiguration tool made with ports 1 and 4 being made combo toys (PF flasher and effects) for both left and right sides. Electrical wiring is powering LEDs properly.

No positive results.

The LEDs work just fine with the RGB tester loaded on it via the arduino loader... and when I load a VPX table the teensy flashes rapidly as if it's properly receiving data. But the LEDs don't change at all, in fact they don't even black out. They just kinda stay random or white... the same state they were in when the software started.

I'm really not sure what I'm missing. I've read, reread, and tried combinations of troubleshooting steps to try to isolate a problem. I tried different cabinet configurations, rewriting it....modifying others that have worked for other people. Different RJ45 jacks. different DOF settings... I'm not getting anywhere.

Any tips on what steps I can try to try and isolate a problem?

<?xml version="1.0"?>
<Cabinet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Name>VirtualPinball 2017</Name>
  <OutputControllers>
    <FT245RBitbangController>
      <Name>Sainsmart 1</Name>
      <SerialNumber>A600OJ7X</SerialNumber>
    </FT245RBitbangController>
    <FT245RBitbangController>
      <Name>Sainsmart 2</Name>
      <SerialNumber>AI053AHG</SerialNumber>
    </FT245RBitbangController>
    <TeensyStripController>
     <Name>TeensyStripController</Name>
      <NumberOfLedsStrip1>144</NumberOfLedsStrip1>
      <NumberOfLedsStrip2>144</NumberOfLedsStrip2>
      <NumberOfLedsStrip3>0</NumberOfLedsStrip3>
      <NumberOfLedsStrip4>0</NumberOfLedsStrip4>
      <NumberOfLedsStrip5>0</NumberOfLedsStrip5>
      <NumberOfLedsStrip6>0</NumberOfLedsStrip6>
      <NumberOfLedsStrip7>0</NumberOfLedsStrip7>
      <NumberOfLedsStrip8>0</NumberOfLedsStrip8>
      <ComPortName>COM8</ComPortName>
    </TeensyStripController>
  </OutputControllers>
  <Toys>
    <LedStrip>
      <Name>PF Left</Name>
      <Width>1</Width>
      <Height>144</Height>
      <LedStripArrangement>TopDownRightLeft</LedStripArrangement>
      <ColorOrder>GRB</ColorOrder>
      <FirstLedNumber>145</FirstLedNumber>
      <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
      <OutputControllerName>TeensyStripController</OutputControllerName>
    </LedStrip>
    <LedStrip>
      <Name>PF Right</Name>
      <Width>1</Width>
      <Height>144</Height>
      <LedStripArrangement>BottomUpLeftRight</LedStripArrangement>
      <ColorOrder>GRB</ColorOrder>
      <FirstLedNumber>1</FirstLedNumber>
      <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
      <OutputControllerName>TeensyStripController</OutputControllerName>
    </LedStrip>
    <LedWizEquivalent>
      <Name>SainsmartLWEQ 1</Name>
      <LedWizNumber>40</LedWizNumber>
      <Outputs>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.01</OutputName>
          <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
 	<LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.02</OutputName>
          <LedWizEquivalentOutputNumber>2</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
	<LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.03</OutputName>
          <LedWizEquivalentOutputNumber>3</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
	<LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.04</OutputName>
          <LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
 	<LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.05</OutputName>
          <LedWizEquivalentOutputNumber>5</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
 	<LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.06</OutputName>
          <LedWizEquivalentOutputNumber>6</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
	<LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.07</OutputName>
          <LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
	<LedWizEquivalentOutput>
          <OutputName>Sainsmart 1.08</OutputName>
          <LedWizEquivalentOutputNumber>8</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
      </Outputs>
</LedWizEquivalent>
    <LedWizEquivalent>
      <Name>SainsmartLWEQ 2</Name>
      <Outputs>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.01</OutputName>
          <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.02</OutputName>
          <LedWizEquivalentOutputNumber>2</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.03</OutputName>
          <LedWizEquivalentOutputNumber>3</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.04</OutputName>
          <LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.05</OutputName>
          <LedWizEquivalentOutputNumber>5</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.06</OutputName>
          <LedWizEquivalentOutputNumber>6</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.07</OutputName>
          <LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>Sainsmart 2.08</OutputName>
          <LedWizEquivalentOutputNumber>8</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
      </Outputs>
      <LedWizNumber>41</LedWizNumber>
    </LedWizEquivalent>
<LedWizEquivalent>
<Name>LedWizEquivalent 30</Name>
<LedWizNumber>30</LedWizNumber>
    <Outputs> 
    <LedWizEquivalentOutput>
     <OutputName>PF Left</OutputName>
     <LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>
    <LedWizEquivalentOutput>
     <OutputName>PF Right</OutputName>
     <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>
    </Outputs>
    </LedWizEquivalent>
  </Toys>
  <Colors/>
  <Curves/>
  <AutoConfigEnabled>true</AutoConfigEnabled>
</Cabinet>

[Outhere]

post your GlobalConfig_B2SServer file and DirectOutput.log

[Outhere]

Here's my setup....
If you use any of it you'll have to make sure that the drive path's are right and also change your sainsmart serial numbers, com port, the amount of Lights per strip and other things

 

http://www.vpforums....=36156&p=375849

[Cue777]

 

So after researching this for a bit,  I spent the entire day yesterday programming, troubleshooting to get these to work. I followed the guide exactly, didn't skip any step

Teensy is loaded with the correct firmware, teensy is soldered and connected to daughter board with RJ45 in the right (from bottom) jack, Orange cat5 going to data and striped orange going to ground. Cabinet file edited with correct comport and ledwizequivalent coding and strip definition (I will attach cabinet code below). Globalconfig is edited. DOF online cofiguration tool made with ports 1 and 4 being made combo toys (PF flasher and effects) for both left and right sides. Electrical wiring is powering LEDs properly.

No positive results.

The LEDs work just fine with the RGB tester loaded on it via the arduino loader... and when I load a VPX table the teensy flashes rapidly as if it's properly receiving data. But the LEDs don't change at all, in fact they don't even black out. They just kinda stay random or white... the same state they were in when the software started.

I'm really not sure what I'm missing. I've read, reread, and tried combinations of troubleshooting steps to try to isolate a problem. I tried different cabinet configurations, rewriting it....modifying others that have worked for other people. Different RJ45 jacks. different DOF settings... I'm not getting anywhere.

Any tips on what steps I can try to try and isolate a problem?

 

 

 

Thats pretty much the same problem I had, and my real DMD would also not work when loading a game. Do you have a real DMD? I gave up on mine completely, I was emailing back and forth with Russdx who makes the DMD and we still could not get it to work.

[supermario0523]

 
Thats pretty much the same problem I had, and my real DMD would also not work when loading a game. Do you have a real DMD? I gave up on mine completely, I was emailing back and forth with Russdx who makes the DMD and we still could not get it to work.

Nope no real DMD, but everything else I have as a DOF toy works great.

Outhere I will try your can XML in a bit but I think I tried it when I was troubleshooting... I'll try again and attach my Config and log when I get home in a few mins

[supermario0523]

 

post your GlobalConfig_B2SServer file and DirectOutput.log

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 0.9.5812.27024: 2017-11-30 20-43-41-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>1</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <IniFilesPath>D:\Virtual Pinball\DirectOutput\config</IniFilesPath>
  <ShapeDefintionFilePattern>{DllDir}\DirectOutputShapes.xml</ShapeDefintionFilePattern>
  <CabinetConfigFilePattern>D:\Virtual Pinball\DirectOutput\config\Cabinet.xml</CabinetConfigFilePattern>
  <TableConfigFilePatterns />
  <EnableLogging>true</EnableLogging>
  <ClearLogOnSessionStart>false</ClearLogOnSessionStart>
  <LogFilePattern>.\DirectOutput.log</LogFilePattern>
</GlobalConfig>

Global settings in post above, Log here:

---------------------------------------------------------------------------------
2017.12.01 11:44:31.520	DirectOutput Logger initialized
2017.12.01 11:44:31.520	DirectOutput Version 0.9.5812.27024 as of 2015.11.30 15:00
2017.12.01 11:44:31.520	Global config loaded from: D:\VIRTUAL PINBALL\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml
2017.12.01 11:44:31.520	Loading Pinball parts
2017.12.01 11:44:31.520	Loading cabinet
2017.12.01 11:44:31.521	Will load cabinet config file: D:\Virtual Pinball\DirectOutput\config\Cabinet.xml
2017.12.01 11:44:31.878	3 output controller defnitions and 5 toy definitions loaded from cabinet config.
2017.12.01 11:44:31.878	Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2017.12.01 11:44:31.879	Cabinet auto configuration started
2017.12.01 11:44:31.891	Debug: Ledwiz devicelist content. Handles: 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, Num devices: 1
2017.12.01 11:44:31.891	Debug: Disposing LedWiz instance -01.
2017.12.01 11:44:31.893	Debug: Ledwiz devicelist content. Handles: 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, Num devices: 1
2017.12.01 11:44:31.893	Detected and added LedWiz Nr. 1 with name LedWiz 01
2017.12.01 11:44:31.893	Added LedwizEquivalent Nr. 1 with name LedWiz 01 Equivalent for Ledwiz Nr. 1
2017.12.01 11:44:31.893	Cabinet auto configuration finished
2017.12.01 11:44:31.893	Autoconfig complete.
2017.12.01 11:44:31.893	Cabinet config loaded successfully from D:\Virtual Pinball\DirectOutput\config\Cabinet.xml
2017.12.01 11:44:31.893	Cabinet loaded
2017.12.01 11:44:31.893	Loading table config
2017.12.01 11:44:31.894	Warning: No table config file found. Will try to load config from LedControl file(s).
2017.12.01 11:44:31.894	Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName austin
2017.12.01 11:44:31.896	Loading LedControl file D:\Virtual Pinball\DirectOutput\config\directoutputconfig.ini
2017.12.01 11:44:32.214	Loading LedControl file D:\Virtual Pinball\DirectOutput\config\directoutputconfig30.ini
2017.12.01 11:44:32.460	Loading LedControl file D:\Virtual Pinball\DirectOutput\config\directoutputconfig40.ini
2017.12.01 11:44:32.532	Loading LedControl file D:\Virtual Pinball\DirectOutput\config\directoutputconfig41.ini
2017.12.01 11:44:32.686	4 directoutputconfig.ini or ledcontrol.ini files loaded.
2017.12.01 11:44:32.687	Config for RomName austin exists in LedControl data. Updating cabinet and config.
2017.12.01 11:44:32.711	Table config loading finished
2017.12.01 11:44:32.711	Pinball parts loaded
2017.12.01 11:44:32.711	Starting processes
2017.12.01 11:44:32.711	Initializing cabinet
2017.12.01 11:44:32.711	Debug: Initializing output controllers
2017.12.01 11:44:32.713	FT245RBitbangController Sainsmart 1 with serial number A600OJ7X has been initialized and the updater thread has been started.
2017.12.01 11:44:32.713	FT245RBitbangController Sainsmart 2 with serial number AI053AHG has been initialized and the updater thread has been started.
2017.12.01 11:44:32.720	TeensyStripController TeensyStripController intialized and updater thread started.
2017.12.01 11:44:32.721	Debug: Initializing LedWiz Nr. 01
2017.12.01 11:44:32.721	TeensyStripController TeensyStripController updater thread  started.
2017.12.01 11:44:32.722	LedWiz Nr. 01 initialized and updater thread initialized.
2017.12.01 11:44:32.722	Debug: Output controllers initialized
2017.12.01 11:44:32.722	Updater thread for LedWiz 01 started.
2017.12.01 11:44:32.727	Cabinet initialized
2017.12.01 11:44:32.728	Loading shape definition file: D:\VIRTUAL PINBALL\DIRECTOUTPUT\DirectOutputShapes.xml
2017.12.01 11:44:32.772	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixFlickerEffect. Calculated area size: AreaDef(L:0, T:85, W:100, H:15), Matrix(W:144, H:1), ResultArea(Left: 0, Top:122, Right:0, Bottom:143, Width:1, Height:22)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.773	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.774	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.774	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.774	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.774	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.774	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:144, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:17, Width:1, Height:18)
2017.12.01 11:44:32.780	Framework initialized.
2017.12.01 11:44:32.780	Have fun! :)
2017.12.01 11:44:32.822	TeensyStripController TeensyStripController updater thread  has connected to TeensyStripController TeensyStripController.
2017.12.01 11:44:32.856	Connection to FTDI chip A600OJ7X established.
2017.12.01 11:44:32.856	Connection to FTDI chip AI053AHG established.
2017.12.01 11:44:40.283	Finishing framework
2017.12.01 11:44:40.285	Finishing cabinet
2017.12.01 11:44:40.286	Debug: Finishing output controllers
2017.12.01 11:44:40.401	Connection to FTDI chip A600OJ7X closed.
2017.12.01 11:44:40.401	FT245RBitbangController Sainsmart 1 with serial number A600OJ7X has been finished and the updater thread has been terminated.
2017.12.01 11:44:40.516	Connection to FTDI chip AI053AHG closed.
2017.12.01 11:44:40.516	FT245RBitbangController Sainsmart 2 with serial number AI053AHG has been finished and the updater thread has been terminated.
2017.12.01 11:44:40.538	TeensyStripController TeensyStripController updater thread  has disconnected from TeensyStripController TeensyStripController and will terminate.
2017.12.01 11:44:40.538	TeensyStripController TeensyStripController finished and updater thread stopped.
2017.12.01 11:44:40.539	Debug: Finishing LedWiz Nr. 01
2017.12.01 11:44:40.539	Updater thread for LedWiz 01 terminated.
2017.12.01 11:44:40.540	LedWiz Nr. 01 finished and updater thread stopped.
2017.12.01 11:44:40.540	Debug: Output controllers finished
2017.12.01 11:44:40.540	Cabinet finished
2017.12.01 11:44:40.540	DirectOutput framework finished.
2017.12.01 11:44:40.540	Bye and thanks for using!

No luck with editing your cabinet xml to get addressables to work either :/
 

[Outhere]

Do you have the data wire hooked up to the right end of the LED strip?...

. sorry I missed this earlier when I read your first post..stay random or white...Before I start a game or when I go into a game my addressable lights aren't doing anything

until the game calls out something for them to do

Edited by Outhere, 01 December 2017 - 08:09 PM.

[supermario0523]

Do you have the data wire hooked up to the right end of the LED strip?...
. sorry I missed this earlier when I read your first post..stay random or white...Before I start a game or when I go into a game my addressable lights aren't doing anything
until the game calls out something for them to do

My data strand is going to where the arrows come from, not where they are pointing to. If that makes sense

There is a green, white, and red wire. I have ground from power supply and the orange/white strad going to white, red gets hot from 5v power, green gets orange data line

Edited by supermario0523, 01 December 2017 - 08:15 PM.

[Outhere]

It sounds like you have it hooked up right to me ....your data is going in the direction of the arrows.....
Did you try a different USB port, did you try other games are you sure it's com port 8... just throwing out some ideas

[supermario0523]

Didn't try different USB port but I'm positive on the comport

The led on the teensy flashes whenever a table loads which baffles me further. Yep tried other tables too


I reloaded the teensy strip controller a half a dozen times too

[JasonLyvers]

You are using com port 8 in dof config, and you are connected to orange? That surprises me - and its exactly the mistake I made when I couldnt get my lights on. Might be worth triple checking.

[supermario0523]

You are using com port 8 in dof config, and you are connected to orange? That surprises me - and its exactly the mistake I made when I couldnt get my lights on. Might be worth triple checking.

Yes I can confirm I'm using comport 8 and connected to orange

No luck

[supermario0523]

I tried bypassing the octoboard today, and when I change the strip length in the GlobalConfig file, it reflects the changes I input, but the strips stay solid white, even upon exiting the table. I can't figure out what else I can troubleshoot....

Edited by supermario0523, 08 December 2017 - 03:19 AM.

[MajorFrenchy]

Thanks for that explanation Scottacus,

 

I finished my 1st cab a while back and just finishing my 2nd cab and want to set it up with addressable LED.  

2 questions.

 

1- your Light bar, is it 5 separate addressable  LED daisy chained and connected to one the the RJ45 connected to the Teensy?

 

2- the question might be for someone who has done the DOT matrix display, can the whole array ( Let say 8 rows of LED ) be connected one of the Teensy channel? 

 

Thanks! 

[Outhere]

This is what I did, I used three channels total ....one for each side of the pinball and one in the back

http://www.vpforums....=38892&p=391732

http://vpuniverse.co.../#comment-30746

[nickbuol]

Can someone validate my setup please?

 

6 total 144/m strips.  

 

1 down the right side

4 cut in half and zig-zagging to make an 8 x 72 matrix

1 down the left side

 

I am injecting power at the beginning of each strip, including the first one where it also connects to the Teensy/Octo board combo

 

I've got all of that done, but with the Cat6 cable, the orange/white goes to the data wire for the strip, but do I need to plug anything else in from the Teensy/Octo board?  I was worried about connecting the white/orange wire from the CAT6 to the LED strip since it will also be, basically, directly connected to the - (negative) that goes to the power supply.

 

Can someone just let me know if I am OK with just the Orange/white being connected for data or do I need to do something different?

 

Thanks a ton. I am so close to finally powering up the computer yet tonight, and I am hoping to connect everything but the power (wired, but won't turn on yet) and the CAT6 until I know for sure.