Jump to content



Photo
* * * * - 4 votes

How to Set Up Addressable LED Strips

Started By scottacus , Oct 18 2016 02:30 PM

  • Please log in to reply
391 replies to this topic

#281 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 01 March 2019 - 09:26 PM

Thx for the response. 

 

Here's the Issue, i spent literally 2 days trying to troubleshoot my Addressable LED not starting in the game. 

 

- I won't post my settings yet as someone might know what the issue is. I had it working 2 days ago , changed something and of course i can't get it to work again.

 

- I have all my DOF working in the table ( my ledwiz works )

- I connected all my addressable led strips and tested it with the simple test, all works. 

- I upload the teensy firmware on the Teensy and it uploads ok.

- I created my cabinet file with all my led strips defined

- i created a globalconfig.xml 

- i duplicated my GlobalConfig.xml and renamed it GlobalConfig_B2SServer.xml ( both files are in the c:/DirectOutput/Config folder

- I created my WS2811 config in DOF config tool . I used 3 combos ( Port 1 Backboard using Back flash MX, Back effect MX and back strobe MX assigned to it ) Port 4 in my right strip ( Combo2 right effect MX and right flasher MX ) Port 7 is my 3rd combo for the left strip )

- I extracted the config in the C:/DirectOutput/Config

- I Launch a VP9 Attack from Mars B2S table and i can see the light on the Teensy blinking rapidly. 

 

I get nothing........  but my led toys on the LED-WIZ work. 

 

I don't know if it's related but If i test my LEDWIZ outside VP using the New LED testing tool, i get an error, unable to initiate LEDwiz library. On the same token, If i try to configure The Addressable LED to work in PinballX, when i launch the plugin manager, i see the DirectOutput PinballX plugin but if i click on the setting or manage button, i get an Error. DirectOutput Framework not found. Make sure DOF com object is registered. 

 

---------- What was tried -----------

 

- of course, i click on the register objects in the direct output folder and it says it's ok.

- I ensured all dll were unblocked

- all exe run as admin

- i tried re installing DOF starting from dof 1-2 and 3

- tried just installing dof3 beta

- played around with different cabinets examples

- tried to assign just PF Back Effects MX instead of a combo in the DOF Configtool

- I re installed Windows 10 twice

- i disabled all firewalls, defender ANTI-VIRUS AND Disabled UAC

 

I am out of ideas and very tired..... 

 

Thanks for your suggestions folks you are the best


majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#282 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 01 March 2019 - 09:46 PM

Post your DirectOutput.log file


#283 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 02 March 2019 - 08:56 AM 

---------------------------------------------------------------------------------
DirectOutput Version 3.1.6968.21374, built 2019.01.29 11:52
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2019.03.02 03:46:44.472	DirectOutput Logger initialized
2019.03.02 03:46:44.236	Global config filename is "C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml"
2019.03.02 03:46:44.472	Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml
2019.03.02 03:46:44.472	Loading Pinball parts
2019.03.02 03:46:44.472	Loading cabinet
2019.03.02 03:46:44.474	Will load cabinet config file: C:\DirectOutput\Config\Cabinet.xml
2019.03.02 03:46:45.115	1 output controller defnitions and 4 toy definitions loaded from cabinet config.
2019.03.02 03:46:45.115	Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2019.03.02 03:46:45.115	Cabinet auto configuration started
2019.03.02 03:46:45.138	PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2019.03.02 03:46:45.146	LedWiz-like device at VID=121, PID=6, product string=Generic   USB  Joystick  , manufacturer string=DragonRise Inc.  
2019.03.02 03:46:45.147	LedWiz-like device at VID=64250, PID=240, product string=LED-Wiz+GP 1, manufacturer string=GGG
2019.03.02 03:46:45.148	HID caps: usage page=1, usage=4, number of link collection nodes=2, output report byte length=9
2019.03.02 03:46:45.151	LedWiz-like device at VID=1133, PID=49948, product string=USB Keyboard, manufacturer string=Logitech
2019.03.02 03:46:45.154	LedWiz-like device at VID=1133, PID=49948, product string=USB Keyboard, manufacturer string=Logitech
2019.03.02 03:46:45.156	LedWiz-like device at VID=1133, PID=49948, product string=USB Keyboard, manufacturer string=Logitech
2019.03.02 03:46:45.159	Opening 32-bit LedWiz driver...
2019.03.02 03:46:45.160	Detected and added LedWiz Nr. 1 with name LedWiz 01
2019.03.02 03:46:45.160	Added LedwizEquivalent Nr. 1 with name LedWiz 01 Equivalent for Ledwiz Nr. 1
2019.03.02 03:46:45.163	Cabinet auto configuration finished
2019.03.02 03:46:45.163	Autoconfig complete.
2019.03.02 03:46:45.163	Cabinet config loaded successfully from C:\DirectOutput\Config\Cabinet.xml
2019.03.02 03:46:45.163	Cabinet loaded
2019.03.02 03:46:45.163	Loading table config
2019.03.02 03:46:45.164	Warning: No table config file found. Will try to load config from LedControl file(s).
2019.03.02 03:46:45.164	Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName afm_113b
2019.03.02 03:46:45.167	Loading LedControl file C:\DIRECTOUTPUT\config\directoutputconfig.ini
2019.03.02 03:46:45.172	Min DOF Version is 0.8 for file directoutputconfig.ini
2019.03.02 03:46:45.549	Loading LedControl file C:\DIRECTOUTPUT\config\directoutputconfig30.ini
2019.03.02 03:46:45.558	Min DOF Version is 0.8 for file directoutputconfig30.ini
2019.03.02 03:46:46.422	2 directoutputconfig.ini or ledcontrol.ini files loaded.
2019.03.02 03:46:46.425	Config for RomName afm_113b exists in LedControl data. Updating cabinet and config.
2019.03.02 03:46:46.450	Debug: Setting up shape effect for area. L: 0, T: 0, W: 9, H: 30
2019.03.02 03:46:46.450	Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 0, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 0, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 0, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 0, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 0, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30
2019.03.02 03:46:46.451	Debug: Setting up shape effect for area. L: 0, T: 0, W: 9, H: 30
2019.03.02 03:46:46.452	Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30
2019.03.02 03:46:46.453	Table config loading finished: romname=afm_113b, tablename=AttackFromMars_FS_B2S
2019.03.02 03:46:46.454	Pinball parts loaded
2019.03.02 03:46:46.454	Starting processes
2019.03.02 03:46:46.454	Initializing cabinet
2019.03.02 03:46:46.455	Debug: Initializing output controllers
2019.03.02 03:46:46.470	TeensyStripController LedStripController intialized and updater thread started.
2019.03.02 03:46:46.470	Debug: Initializing LedWiz Nr. 01
2019.03.02 03:46:46.471	TeensyStripController LedStripController updater thread  started.
2019.03.02 03:46:46.472	LedWiz Nr. 01 initialized and updater thread initialized.
2019.03.02 03:46:46.472	Debug: Output controllers initialized
2019.03.02 03:46:46.473	Updater thread for LedWiz 01 started.
2019.03.02 03:46:46.479	Cabinet initialized
2019.03.02 03:46:46.482	Loading shape definition file: C:\DIRECTOUTPUT\config\DirectOutputShapes.xml
2019.03.02 03:46:46.531	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:60, T:66, W:5, H:33), Matrix(W:256, H:1), ResultArea(Left: 0, Top:168, Right:0, Bottom:253, Width:1, Height:86)
2019.03.02 03:46:46.532	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:73, T:66, W:5, H:33), Matrix(W:256, H:1), ResultArea(Left: 0, Top:168, Right:0, Bottom:253, Width:1, Height:86)
2019.03.02 03:46:46.532	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:60, T:0, W:15, H:66), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:168, Width:1, Height:169)
2019.03.02 03:46:46.532	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:75, T:0, W:15, H:66), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:168, Width:1, Height:169)
2019.03.02 03:46:46.532	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:68, T:0, W:15, H:66), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:168, Width:1, Height:169)
2019.03.02 03:46:46.532	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:50, H:100), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:255, Width:1, Height:256)
2019.03.02 03:46:46.532	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:50, T:0, W:50, H:100), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:255, Width:1, Height:256)
2019.03.02 03:46:46.533	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:66, W:9, H:33), Matrix(W:256, H:1), ResultArea(Left: 0, Top:168, Right:0, Bottom:253, Width:1, Height:86)
2019.03.02 03:46:46.533	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:25, T:66, W:10, H:33), Matrix(W:256, H:1), ResultArea(Left: 0, Top:168, Right:0, Bottom:253, Width:1, Height:86)
2019.03.02 03:46:46.533	Debug: MatrixBase for RGBAMatrixFlickerEffect. Calculated area size: AreaDef(L:0, T:0, W:30, H:100), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:255, Width:1, Height:256)
2019.03.02 03:46:46.533	Debug: MatrixBase for RGBAMatrixFlickerEffect. Calculated area size: AreaDef(L:70, T:0, W:30, H:100), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:255, Width:1, Height:256)
2019.03.02 03:46:46.534	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.537	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.575	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.577	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.577	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.578	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.578	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.578	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.578	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.578	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.578	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.579	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.579	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.579	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.579	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.579	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.579	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.579	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.579	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.579	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.580	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.580	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.580	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.580	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.580	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.580	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.580	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.581	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.581	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.581	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.581	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.581	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.581	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.581	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.581	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.582	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.582	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.582	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:0, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.582	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.582	Debug: MatrixBase for RGBAMatrixColorScaleShapeEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.582	Debug: MatrixBase for RGBAMatrixColorScaleBitmapEffect. Calculated area size: AreaDef(L:91, T:0, W:9, H:30), Matrix(W:256, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:76, Width:1, Height:77)
2019.03.02 03:46:46.582	Debug: BitmapEffectBase. Grabbing image clip: W: 1, H:77, BML: 35, BMT: 18, BMW: 16, BMH: 16
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:80), Matrix(W:72, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:57, Width:1, Height:58)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:80), Matrix(W:72, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:57, Width:1, Height:58)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:35, W:100, H:8), Matrix(W:72, H:1), ResultArea(Left: 0, Top:25, Right:0, Bottom:30, Width:1, Height:6)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:7, W:100, H:6), Matrix(W:72, H:1), ResultArea(Left: 0, Top:5, Right:0, Bottom:9, Width:1, Height:5)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:15, W:100, H:6), Matrix(W:72, H:1), ResultArea(Left: 0, Top:10, Right:0, Bottom:15, Width:1, Height:6)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:65, W:100, H:15), Matrix(W:72, H:1), ResultArea(Left: 0, Top:46, Right:0, Bottom:57, Width:1, Height:12)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:70, W:100, H:20), Matrix(W:72, H:1), ResultArea(Left: 0, Top:50, Right:0, Bottom:64, Width:1, Height:15)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:10, W:100, H:90), Matrix(W:72, H:1), ResultArea(Left: 0, Top:7, Right:0, Bottom:71, Width:1, Height:65)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:80, W:100, H:10), Matrix(W:72, H:1), ResultArea(Left: 0, Top:57, Right:0, Bottom:64, Width:1, Height:8)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:80, W:100, H:10), Matrix(W:72, H:1), ResultArea(Left: 0, Top:57, Right:0, Bottom:64, Width:1, Height:8)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:15, W:100, H:8), Matrix(W:72, H:1), ResultArea(Left: 0, Top:10, Right:0, Bottom:16, Width:1, Height:7)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:6), Matrix(W:72, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:4, Width:1, Height:5)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:80), Matrix(W:72, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:57, Width:1, Height:58)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:65, W:100, H:15), Matrix(W:72, H:1), ResultArea(Left: 0, Top:46, Right:0, Bottom:57, Width:1, Height:12)
2019.03.02 03:46:46.583	Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:70, W:100, H:20), Matrix(W:72, H:1), ResultArea(Left: 0, Top:50, Right:0, Bottom:64, Width:1, Height:15)
2019.03.02 03:46:46.595	TeensyStripController LedStripController updater thread  has connected to TeensyStripController LedStripController.
2019.03.02 03:46:46.598	Framework initialized.
2019.03.02 03:46:46.598	Have fun! :)
2019.03.02 03:47:08.803	Finishing framework
2019.03.02 03:47:08.805	Finishing cabinet
2019.03.02 03:47:08.806	Debug: Finishing output controllers
2019.03.02 03:47:08.853	TeensyStripController LedStripController updater thread  has disconnected from TeensyStripController LedStripController and will terminate.
2019.03.02 03:47:08.853	TeensyStripController LedStripController finished and updater thread stopped.
2019.03.02 03:47:08.853	Debug: Finishing LedWiz Nr. 01
2019.03.02 03:47:08.853	Updater thread for LedWiz 01 terminated.
2019.03.02 03:47:08.865	LedWiz Nr. 01 finished and updater thread stopped.
2019.03.02 03:47:08.865	Debug: Output controllers finished
2019.03.02 03:47:08.865	Cabinet finished
2019.03.02 03:47:08.865	DirectOutput framework finished.
2019.03.02 03:47:08.865	Bye and thanks for using!
2019.03.02 03:47:36.677	Debug: Disposing LedWiz instance 01.

majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#284 arngrim

arngrim

    DJ Force Feedback

  • VIP
  • 2,188 posts
  • Location:Charleroi, Belgium

  • Flag: Belgium

  • Favorite Pinball: Monster bash



Posted 02 March 2019 - 10:19 PM

i would redirect you to mjr or terryred or randr, i don't have ledstrips, at least i don't see any error in the log file

 

so you didn't changed your globalconfig file since the last time it was working? can you show it?


a2k6.png
My youtube channel
How to use controller.vbs for SS tables in depth
How to use controller.vbs for EM and Original tables in depth

#285 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 02 March 2019 - 11:38 PM

Everything in a log file looks right...
Like arngrim said post your GlobalConfig_B2SServer.xml and your Cabinet file


#286 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 03 March 2019 - 07:34 AM

Everything in a log file looks right...
Like arngrim said post your GlobalConfig_B2SServer.xml and your Cabinet file

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


<TeensyStripController>
<Name>LedStripController</Name>
<NumberOfLedsStrip1>400</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>
</TeensyStripController>

</OutputControllers>

<Toys>
  
<LedStrip>
  <Name>BackBoard</Name>
  <Width>8</Width>
  <Height>32</Height>
  <LedStripArrangement>RightLeftAlternateBottomUp</LedStripArrangement>
  <ColorOrder>GRB</ColorOrder>
  <FirstLedNumber>1</FirstLedNumber>
  <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
  <OutputControllerName>LedStripController</OutputControllerName>
</LedStrip>
    
<LedStrip>
  <Name>Sideboard Right</Name>
  <Width>1</Width>
  <Height>72</Height>
  <LedStripArrangement>TopDownRightLeft</LedStripArrangement>
  <ColorOrder>GRB</ColorOrder>
  <FirstLedNumber>257</FirstLedNumber>
  <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
  <OutputControllerName>LedStripController</OutputControllerName>
</LedStrip>
      
<LedStrip>
  <Name>Sideboard Left</Name>
  <Width>1</Width>
  <Height>72</Height>
  <LedStripArrangement>BottomUpLeftRight</LedStripArrangement>
  <ColorOrder>GRB</ColorOrder>
  <FirstLedNumber>329</FirstLedNumber>
  <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
  <OutputControllerName>LedStripController</OutputControllerName>
</LedStrip>

  
<LedWizEquivalent>

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

    <LedWizEquivalentOutput>
    <OutputName>BackBoard</OutputName>
    <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>

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

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

    </Outputs>
    <LedWizNumber>30</LedWizNumber>
</LedWizEquivalent>
   
</Toys>

</Cabinet>

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 3.1.6968.21374: 2019-03-03 02-29-15-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>10</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <PacLedDefaultMinCommandIntervalMs>10</PacLedDefaultMinCommandIntervalMs>
  <IniFilesPath />
  <CabinetConfigFilePattern>C:\DirectOutput\Config\Cabinet.xml</CabinetConfigFilePattern>
  <TableConfigFilePatterns />
  <EnableLogging>true</EnableLogging>
  <ClearLogOnSessionStart>true</ClearLogOnSessionStart>
  <LogFilePattern>.\DirectOutput.log</LogFilePattern>
</GlobalConfig>

majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#287 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 03 March 2019 - 08:13 AM

I don't see anything wrong, Maybe post something in here and I don't have any Problem with either one of these things

https://www.vpforums...c=39557&page=18

 

I don't know if it's related but If i test my LEDWIZ outside VP using the New LED testing tool, i get an error, unable to initiate LEDwiz library. On the same token, If i try to configure The Addressable LED to work in PinballX, when i launch the plugin manager, i see the DirectOutput PinballX plugin but if i click on the setting or manage button, i get an Error. DirectOutput Framework not found. Make sure DOF com object is registered. 


#288 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 03 March 2019 - 04:03 PM

I don't see anything wrong, Maybe post something in here and I don't have any Problem with either one of these things
https://www.vpforums...c=39557&page=18
 

I don't know if it's related but If i test my LEDWIZ outside VP using the New LED testing tool, i get an error, unable to initiate LEDwiz library. On the same token, If i try to configure The Addressable LED to work in PinballX, when i launch the plugin manager, i see the DirectOutput PinballX plugin but if i click on the setting or manage button, i get an Error. DirectOutput Framework not found. Make sure DOF com object is registered. 

Thank you for taking the time to look at the log Outhere. If anyone else has an idea I posted a private video on YouTube with the setup and issue. The video is crappy and non edited it's just to show my issue. https://youtu.be/QRfB3faq_4E

Sent from my SM-G965W using Tapatalk

majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#289 mon72

mon72

    Enthusiast

  • Members
  • PipPipPip
  • 66 posts
  • Location:Gothenburg

  • Flag: Sweden

  • Favorite Pinball: Indiana Jones

Posted 04 March 2019 - 05:28 AM

I have a similar problem and have read in some places that you should connect pin 15 and pin 16 on the Teensy 3.2 board...

 

I looked at a link for this at the https://www.pjrc.com...OctoWS2811.html site...

This is what they write about this... hope it helps!

will try this myself after work :-)

teensy_3.2.png

"OctoWS2811 uses internally uses a timer, and a PWM waveform at a pin on some boards. This PWM pin and the timer must not be used. See the table above for details.

Early versions of OctoWS2811 required pins 15 & 16 to be connected together. Modern versions do not use pin 15 or 16. "

 

BR

Mon72


Edited by mon72, 04 March 2019 - 05:31 AM.

#290 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 04 March 2019 - 06:01 AM

I built mine 2 years ago and bought the parts from the links in the 1st post of this topic...

I never had to solder 15 and 16 together ... So the boards They're talking about are at least 2 years ago or older...

 

When I bought my stuff I put the 2 boards together .... Program the board and hooked everything up ran a game and everything worked...

 

Over the last 2 years I have seen at least a 1/2 dozen people having to Solder those 2 pins together otherwise their lights are all white...

So I can only assume those people are picking up old board somewhere...


Edited by Outhere, 04 March 2019 - 06:13 AM.

#291 Phazer51

Phazer51

    Enthusiast

  • Platinum Supporter
  • 155 posts

  • Flag: United States of America

  • Favorite Pinball: Medieval Madness

Posted 04 March 2019 - 08:00 PM

I purchased my Teensy 3.2 and Octo board at the end of 2018. All of my sample tests through the Arduino uploader worked.  But, I couldn't get anything to work with DOF.  I had to bridge pins 15 and 16.

 

I was so happy to accidentally run across someone who had posted the solution in some forum that I started a thread so that others could find it by title:

 

DOF addressable LEDs "all white" problem [SOLVED]

https://www.vpforums...topic=41655&hl=


Edited by Phazer51, 04 March 2019 - 08:04 PM.

#292 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 04 March 2019 - 08:35 PM

I purchased my Teensy 3.2 and Octo board at the end of 2018. All of my sample tests through the Arduino uploader worked.  But, I couldn't get anything to work with DOF.  I had to bridge pins 15 and 16.

 

I was so happy to accidentally run across someone who had posted the solution in some forum that I started a thread so that others could find it by title:

 

DOF addressable LEDs "all white" problem [SOLVED]

https://www.vpforums...topic=41655&hl=

 

 

Phazer51, and Mon72 if you trick works i am going to kiss you both..... sort of. almost a week i;m on this issue, will test it tonight and will report back. 

 

Thanks again, 


majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#293 mon72

mon72

    Enthusiast

  • Members
  • PipPipPip
  • 66 posts
  • Location:Gothenburg

  • Flag: Sweden

  • Favorite Pinball: Indiana Jones

Posted 12 March 2019 - 02:24 PM

Hi MajorFrenchy
 

How did it go with the LEDstrips??

 

A wish from me and I think I speak for a lot of people in this issue...

In your next "Tutorial / How to Video" please go through the setting/assigning of buttons...

If one uses Pinscape it differs from if you use the other variants for inputs and outputs.

For example in VPinballX emulator I should have "none" on the inputs with Pinscape but not if I use one of the other variants.

And the Settings for PinballX there are two pages for Keyboard and Joystick... When should I fill in what and what is not in conflict...?

And when it comes to making it work with Pinscape and FX3 we need to use XBOX360CE for example... and here we can also configure nudge and plunger...

I think this would be a godsend of a tutorial :-)

I know I have wrestled with this...

Big thanks for the ones that you have done up til now... a grate source of inspiration.  Thanks.

BR

Mon72


#294 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 12 March 2019 - 03:08 PM

Hi MajorFrenchy
 
How did it go with the LEDstrips??
 
A wish from me and I think I speak for a lot of people in this issue...
In your next "Tutorial / How to Video" please go through the setting/assigning of buttons...
If one uses Pinscape it differs from if you use the other variants for inputs and outputs.
For example in VPinballX emulator I should have "none" on the inputs with Pinscape but not if I use one of the other variants.
And the Settings for PinballX there are two pages for Keyboard and Joystick... When should I fill in what and what is not in conflict...?
And when it comes to making it work with Pinscape and FX3 we need to use XBOX360CE for example... and here we can also configure nudge and plunger...
I think this would be a godsend of a tutorial :-)
I know I have wrestled with this...
Big thanks for the ones that you have done up til now... a grate source of inspiration.  Thanks.
BR
Mon72

We got it working, after spending almost an entire week troubleshooting that pre made 8x32 matrix I threw it in the garbage. We used 3 strips of 144L/ meter that I cut in half , 2 full size 144 strips for the left and right and 2x 24 led rings behind our speaker grill. In our future guide we will cover as many settings as possible. Unfortunately we never tried a pinscape. Our next tutorial will not be a guide but a full website with sections , that way when we update a section or set up and test a new device we will be able to update it. This was not possible with our previous guide. For this future build we used a ledwiz and a usb zero delay controller board for the buttons. There are many ways to achieve your build. We are making good progress with the guide and YouTube series. Hope you enjoy it soon

Major Frenchy!


Sent from my SM-G965W using Tapatalk
cc4816efb24c10b48559e0431e4cbc91.jpg

Edited by MajorFrenchy, 12 March 2019 - 04:14 PM.

majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#295 mon72

mon72

    Enthusiast

  • Members
  • PipPipPip
  • 66 posts
  • Location:Gothenburg

  • Flag: Sweden

  • Favorite Pinball: Indiana Jones

Posted 12 March 2019 - 09:17 PM

Im all ready interested in how you connected your leds
My setup is similar with 144 per side and 40 per speaker...
My plan was to use one Channel for each on the Teensy first 4 of 8 channels.
How did you assign the direct output to your speakers?
Br
Mon72

Edited by mon72, 12 March 2019 - 09:18 PM.

#296 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 12 March 2019 - 09:25 PM

Im all ready interested in how you connected your leds
My setup is similar with 144 per side and 40 per speaker...
My plan was to use one Channel for each on the Teensy first 4 of 8 channels.
How did you assign the direct output to your speakers?
Br
Mon72

I will describe it in the guide. It would be too long to describe.
For the speaker , there are no specific effects for the speaker light, I will assign it a back flasher effect or something like that. I have all my strips on one channel I personally find it less confusing.

Sent from my SM-G965W using Tapatalk

majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#297 MikePinball

MikePinball

    Oak Micros Pinball Products

  • Platinum Supporter
  • 416 posts

  • Flag: United States of America

  • Favorite Pinball: Space Invaders

Posted 17 March 2019 - 03:38 AM

This append is about LED density and which ones I should buy.

 

In order to create a matrix that has square pixels, it would seem that the only option is to use 10 mm spaced LEDs (i.e. 100 per meter). Looking at the picture below LEDs that are 144 per meter can only be spaced 12 mm apart vertically (and the horizontal spacing is 1000/144 = ~7 mm. Similarly LEDs at 60 per meter can be spaced 10 mm apart vertically but the horizontal spacing is 1000/60 = ~17 mm.

 

addressableleddensity.jpg

 

In fact when you look at the 8x32 (e.g. Amazon) and 8x8 (e.g. eBay) LED matrices, the LED spacing is also 10 mm.

 

Hence it would seem that the best option is to either combine the 8x32 and 8x8 matrices or create your own custom width matrix using 100 per meter LEDs (which are available but with less sources). Anything wrong with my reasoning?


MikePinball (dba Oak Micros).

 

#298 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 17 March 2019 - 04:35 AM

This is my set up and I used the pre made Matrix for a matter of convenience but I can see what you're saying And I think it looks fabulous

https://www.vpforums...093#entry393762


#299 MajorFrenchy

MajorFrenchy

    Enthusiast

  • Members
  • PipPipPip
  • 256 posts
  • Location:Canada

  • Flag: Canada

  • Favorite Pinball: The Flintstones

Contributor

Posted 21 March 2019 - 11:41 PM

Anyone have seen this before. I tried a new Matrix pre made 8x32 addressable.

I got it to work in the game and in the PinballX menu but the shapes are all wonky and there are some white led artifacts.

I filmed it.

https://s.amsu.ng/xsYHu3teVYMN

It did the same on a home made strip and another one like this I had laying around.

Sent from my SM-G965W using Tapatalk

majorfrenchylogosmall.png

https://www.majorfrenchy.com/

#300 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 22 March 2019 - 01:16 AM

Post cabinet file


Back to Virtual Pinball Cabinets


  1. VPForums.org
  2. → Emulation Station
  3. → Virtual Pinball Cabinets
  4. Privacy Policy
  5. Board Rules ·