I found that the feed into the matrix mentioned above is bottom to top and right to left...
I connected power to the unit half way through so it has power in the beginning and middle of the unit (127 each)
I did the same thing... I used the PF Right and connected it to the matrix... I loaded up Medieval and started with a ball... the red flasher was moving up and down on the far right...
So I know the unit is working...
When I connect it to wire pair 3 (green and green/white) it doesnt light at all with medieval madness or any other board with visual pinball x.
COVID has me playing a lot of pinball and cleaning up some items in my cab.
My addressable LED effects have been working for about a year but there is one random issue that occasionally occurs. While playing a table or browsing through front end my side addressable strips will occasionally go all white in the top third of the right and left strip. It is symmetrical. Once they go white the other addressable lights continue to function properly with the exception of the side strips. The only way to reset the side strips is to power down the Teensy.
This only happens on rare occasions but it is annoying. My 15 and 16 pins are soldered together.
Has anyone else seen this issue? I can find google references on the “all white” issues but I do have the 15 and 16 soldered solution and I’m not “all white”. Just partially white and only on the side strips.
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
I am super stumped right now. i have setup 2 or 3 matrix and addressable strip combos at this point, and i am struggling at the moment due to two different setups. the one i have been working on tonight is a 100 led strip connected to orange, 144 led strip connected to blue, and a 11x44 matrix confirmed to be RightLeftAlternateBottomUp. when i run either the direct output tester or fire up doflinx the matrix is scrambled but the strips are fine. i went through major frenchy's hour long video again so i could do the test part, but i skipped that the first time since i knew how the leds were working. the 8x32 matrix with same strips is acting weird also. i built the 8x32 setup first but then got the weird issues, which may be due to the matrix, not sure since its locked up over the weekend, but i am 97% sure i got all the setup right with the 11x44, but its acting way crazier. i have flashed the teensy with both versions of the software either using the exe loaded with a hex file and through arduino. this is my cab file, but im not sure i can upload any pics at the moment. when i run doflinx, the letters are not distinguishable and i used the table "24" direct output config tester line 24, which is supposed to be circles. its super weird. this is on 2 different setups also so it shouldnt be hardware related.
I am super stumped right now. i have setup 2 or 3 matrix and addressable strip combos at this point, and i am struggling at the moment due to two different setups. the one i have been working on tonight is a 100 led strip connected to orange, 144 led strip connected to blue, and a 11x44 matrix confirmed to be RightLeftAlternateBottomUp. when i run either the direct output tester or fire up doflinx the matrix is scrambled but the strips are fine. i went through major frenchy's hour long video again so i could do the test part, but i skipped that the first time since i knew how the leds were working. the 8x32 matrix with same strips is acting weird also. i built the 8x32 setup first but then got the weird issues, which may be due to the matrix, not sure since its locked up over the weekend, but i am 97% sure i got all the setup right with the 11x44, but its acting way crazier. i have flashed the teensy with both versions of the software either using the exe loaded with a hex file and through arduino. this is my cab file, but im not sure i can upload any pics at the moment. when i run doflinx, the letters are not distinguishable and i used the table "24" direct output config tester line 24, which is supposed to be circles. its super weird. this is on 2 different setups also so it shouldnt be hardware related.
Try Testing the matrix by itself
I believe there was somebody on Facebook 4 months ago Was trying out the 11 by 44 and I don't think it works like the regular 8 by 32
outhere, when i said confirmed in the post, i meant that i used arduino to run the basic test to verify the function of the matrix. my matrix is the same as in the setup video https://www.youtube....h?v=dWaGLqg5s50.
I'm setting up the addressable LEDs that were included in the EZKit I bought from Zebsboards. I have everything working so far....contacts, solenoids, beacon, shaker motor, etc., and I just have the addressable LED strips to go, and I'm done! But no, I don't yet have them working.
I just have two questions:
1. Is a global configuration for the DirectOutput framework needed, no exceptions? I'm asking because I have the EZKit.
2. I've read through the posts on this thread, and it seems that the standard .xml file to use is this:
<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 0.9.5764.18938: 2017-10-01 10-02-47-->
They sold you the EZKit with no Directions
That should work for the --- GlobalConfig_B2SServer.xml --- File
As far as I know you will also need a -- Cabinet -- File
Thanks Outthere, I knew you'd still be lurking around somewhere
Yes, i have the cabinet file all ready to go and Steve (Zebsboards) did provide me with that, but didn't say anything about the GlobalConfig_B2SServer.xml file. If this is all I need (software-wise) and it works, I'll be able to bug him about it until the end of days...haha.
I am loosing it i can't get the leds to work with the vpx tables ?
Followed tutorial from Major . Thx for this great tutorial .
My setup 720 leds in total .
-2 x 24 leds speaker rings
-2x 144 side led strips
-1x dot matrix 384 leds ( 1=8x32 and 2=8x8 )
My circuit ( 5v , ground and data ) starts on my right speaker ring ==> left speaker ring ==> left 144 led side strip (arrows going down) ==>
right 144 side strip ( arrows going up ) ==> last dot matrix on the right side .
In arduino software i select com3 teensy and teensy 3.2 .
Then i go to examples and choose octo out of the list and basic test . I change to 720 leds .
this is working perfectly . leds light up on my right speaker ring , goes to left speaker ring , then left side strip and right side strip to end up on the dot matrix .
Color changes everry 20 sec or so .
Now here comes my first question , how to turn this examples off ? Even when i restart my pc it lights up this example .
Now i am also following this tutorial
From min 12 you will see he start arduino software , he choose teensy 3.2 and com port . and on the teensystripcontroller tab he just do compile .
When i do this i have 1 led light up , first led from my left side strip . Why ??? grrrr
I don't know if its because of this leds are not working when starting vpx table .
second question when i login on dof linx website i do generate configfile . It will download the configfile , but its called "directoutputconfig30" .
Must this "30" at the end be removed ?
<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 3.1.7011.27968: 2020-12-19 22-03-14-->
<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>
my doflinx.ini
###### DOFLINX - MAIN CONFIG INI FILE ######
###### UPDATED BY TERRYRED ######
# IMPORTANT! Please go through and edit EVERY section for your particular setup! If you don't you may get errors!
# This is a config file for DOFLinx with most of the available settings as a sample.
# DOFLinx works with LEDWiz, PacLed64, Pinscape, Ultimate I/O Sainsmart (FTDI devices), PinControl, and Teensy (or similar).
# Lines that start with a hash (#) or are blank are not processed.
# Device outputs are entered in the format of device (D) and output number (#) in the format D##, so controller device 1 and output 3 is "103" without the quotes, controller board 2 output 23 is "223" without quotes.
# 0 = OFF (normal operation), 1 = ON. When ON a window will appear and a log file will be created in the EXE directory.
DEBUG=0
########## DIRECTORY PATHS ##########
# IMPORTANT!!! Keep this as the first pararameter (other than DEBUG if you need it) to process in your INI file. The order past ths point is not relevant!
# Point to your directoutputconfig.ini file. Your file may have a number, ie directoutputconfig20.ini
# You can point to any of your directoutputconfig.ini files, but only one.
# The location of the .FX3 game specific files included with the DOFLinx release package
# Ensure your path has a \ on the end of it
PATH_FX3=C:\DirectOutput\FX3_PUPlayer\
# The path to where you keep all of the .directb2s files that you've downloaded for use with FX3
# Ensure your path has a \ on the end of it
PATH_FX3_B2S=C:\DirectOutput\DOFLinx_FX3_B2S\
######### RGB UNDERCAB LIGHTING #########
# RGB Undercabinet Colour Change. RAINBOW = cycle through the colours. RANDOM = use random colour order
RGB_STYLE=RANDOM
# What changes the RGB undercabinet colour. TIME = set time period. FLIPPER = flipper press after the RGB_TRIGGER minimum time (to stop rapid colour changes)
RGB_TRIGGER=TIME
# The minimum time for change between flipper flips, 1000mS or 1 second
RGB_MIN_TIME=8000
# The Device and "RED" port for RGB undercabinet lighting
RGB_OUTPUT=120
######## FUTURE PINBALL LINK ########
# Turn on the attempt to make a full connection to Future Pinball when it is detected as running
FP_ATTEMPT_LINK=1
# When Future Pinball is detected and a Link is being established, this is the maximum amount of time the FP LINK will be attempted. After this time has passed, DOFLinx will activate it's Default mode.
FP_LINK_WAIT_TIME=95000
######## DEVICES and PORTS for FUTURE PINBALL and FX3 ########
######## DOFLINX DEFAULT and FALLBACK FUNCTIONS ########
# These are the default and "fallback" type of functions that are used when DOFLinx is made active, but no link to Future Pinball or FX3 is established.
# Turn on Button lights when DOFLinx is activated (such as EXIT button)
BUTTONS_ON=120
# Set the key code for the keys being used as Left and Right flippers
# Used for the default fall back if a full link cannot be established with FX3 or Future Pinball
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=A0
R_FLIPPER_KEY=A1
# The device and port for the left and right flippers.
L_FLIPPER_OUTPUT=101
R_FLIPPER_OUTPUT=102
# Just in case things go wrong (ie no keyup signal is detected, flipper held down for a long time), what is the maximum time a flipper solenoid / contactor can be in in milliseconds
MAX_FLIPPER_ON=5000
######## KEY TO OUTPUT / COLOUR, etc examples ########
# Make the "4" key (key code 34) to pulse controller/output 119
#KEY_TO_OUTPUT=34,119
# Set the left and right control keys to turn on a specific colour (red) for RGB.
# Example, when nudge keys are used it all goes red.
#KEY_TO_COLOUR=A2,109,Red,A3,109,Red
######## MISC SETTINGS ########
# The list of processes that can activate DOFLinx, such as Pinball FX3, Future Pinball, etc.
# An over-ride to the default setting if this is just being used with Pinball FX3, not FX2, FP or other systems that may require the default delay
#PROCESS_TO_ACTIVE_TIME=1
# AUTO_MX (enabled=1) Allows for FX3 and Future Pinball tables that have DOFLinx support (for 5 RGB Flashers, Beacon, and Strobe) to automatically create basic Addressable Led effects.
AUTO_MX=1
# Set to 1 to output the game name to the log regardless of the DEBUG flag setting. Set to 0 to simply follow the DEBUG flag.
# Quite useful when you trying to get the FX3 window game name for setting game specific colours, matching B2S names, etc
OUTPUT_GAME_NAME=0
######## DOFLINX SETTINGS SCREEN ########
# Configure the DOFLinx generated settings screen to activate when 4 keys are pressed, left shift, right shift, left ctl and right ctl (both flippers and magna saves)
# Set the Left flipper for UP, right flipper for DOWN, Start button for CHANGE and Extra Ball for EXIT
20-Dec-20 08:13:18.017 - Reading DOFLinx.INI startup config file details
20-Dec-20 08:13:18.017 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
20-Dec-20 08:13:18.027 - Error in configuration for RGB item #0 trying to set device # 1 port to 29 Needs to be in the range 1-20
20-Dec-20 08:15:51.827 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Dec-20 08:15:51.837 - Starting up - version 7.16
20-Dec-20 08:15:51.837 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Dec-20 08:15:51.837 - Pre-Reading DOFLinx.INI startup config file details
20-Dec-20 08:15:51.937 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Dec-20 08:15:51.947 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Dec-20 08:15:51.977 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
20-Dec-20 08:15:51.977 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Dec-20 08:15:51.977 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Dec-20 08:15:51.987 - Reading DOFLinx.INI startup config file details
20-Dec-20 08:15:51.987 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
20-Dec-20 08:15:51.997 - Error in configuration for RGB item #0 trying to set device # 1 port to 29 Needs to be in the range 1-20
20-Dec-20 08:16:35.197 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Dec-20 08:16:35.197 - Starting up - version 7.16
20-Dec-20 08:16:35.197 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Dec-20 08:16:35.207 - Pre-Reading DOFLinx.INI startup config file details
20-Dec-20 08:16:35.303 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Dec-20 08:16:35.312 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Dec-20 08:16:35.337 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
20-Dec-20 08:16:35.337 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Dec-20 08:16:35.347 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Dec-20 08:16:35.347 - Reading DOFLinx.INI startup config file details
20-Dec-20 08:16:35.347 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini
20-Dec-20 08:16:35.357 - Error in configuration for RGB item #0 trying to set device # 1 port to 29 Needs to be in the range 1-20
20-Dec-20 08:19:14.957 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Dec-20 08:19:14.967 - Starting up - version 7.16
20-Dec-20 08:19:14.977 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Dec-20 08:19:14.977 - Pre-Reading DOFLinx.INI startup config file details
20-Dec-20 08:19:15.077 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Dec-20 08:19:15.092 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Dec-20 08:19:15.117 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
20-Dec-20 08:19:15.117 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Dec-20 08:19:15.127 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Dec-20 08:19:15.129 - Reading DOFLinx.INI startup config file details
20-Dec-20 08:19:15.129 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
20-Dec-20 08:19:15.139 - Error in configuration for RGB item #0 trying to set device # 1 port to 29 Needs to be in the range 1-20
20-Dec-20 08:23:57.827 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Dec-20 08:23:57.827 - Starting up - version 7.16
20-Dec-20 08:23:57.827 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Dec-20 08:23:57.827 - Pre-Reading DOFLinx.INI startup config file details
20-Dec-20 08:23:57.935 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Dec-20 08:23:57.947 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Dec-20 08:23:57.967 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
20-Dec-20 08:23:57.977 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Dec-20 08:23:57.977 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Dec-20 08:23:57.977 - Reading DOFLinx.INI startup config file details
20-Dec-20 08:23:57.987 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
20-Dec-20 08:23:57.997 - Error in configuration for RGB item #0 trying to set device # 1 port to 29 Needs to be in the range 1-20
20-Dec-20 08:24:54.857 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Dec-20 08:24:54.857 - Starting up - version 7.16
20-Dec-20 08:24:54.857 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Dec-20 08:24:54.867 - Pre-Reading DOFLinx.INI startup config file details
20-Dec-20 08:24:54.967 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Dec-20 08:24:54.977 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Dec-20 08:24:54.997 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
20-Dec-20 08:24:55.007 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Dec-20 08:24:55.007 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Dec-20 08:24:55.007 - Reading DOFLinx.INI startup config file details
20-Dec-20 08:24:55.017 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
20-Dec-20 08:24:55.027 - Error in configuration for RGB item #0 trying to set device # 1 port to 29 Needs to be in the range 1-20
20-Dec-20 08:26:38.897 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Dec-20 08:26:38.907 - Starting up - version 7.16
20-Dec-20 08:26:38.907 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Dec-20 08:26:38.907 - Pre-Reading DOFLinx.INI startup config file details
20-Dec-20 08:26:39.017 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Dec-20 08:26:39.027 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Dec-20 08:26:39.047 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
20-Dec-20 08:26:39.057 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Dec-20 08:26:39.057 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Dec-20 08:26:39.057 - Reading DOFLinx.INI startup config file details
20-Dec-20 08:26:39.067 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
20-Dec-20 10:50:15.593 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Dec-20 10:50:15.625 - Starting up - version 7.16
20-Dec-20 10:50:15.625 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Dec-20 10:50:15.625 - Pre-Reading DOFLinx.INI startup config file details
20-Dec-20 10:50:15.875 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Dec-20 10:50:15.907 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Dec-20 10:50:15.943 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
20-Dec-20 10:50:15.943 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Dec-20 10:50:15.943 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Dec-20 10:50:15.959 - Reading DOFLinx.INI startup config file details
20-Dec-20 10:50:15.959 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
What i did now i solder pin 15 and 16 together . Now only last led in my circuit is lid blue ?
I tried upload firmware 1.01 .
But i don't know if its done correct . https://ibb.co/9pmNypb . I select the new firmware . Open it . Teensy is blinking . I push on the button on the teensy .
sorry again , when i start up teensystripcontroller .
I do upload the first time and the first 64 leds turn on . I was thinking why . Then when you scroll down in the script . You have a line where you put your max leds . by default i see 1100 .
When you scroll down further you will see a line leds 64 . Thats why 64 leds turns on . When i change this to 720 and do upload i have all my leds turning on white and stay like this .
Is it the meaning you change this in the script ?
And after you upload , what should normally happen with the leds . Do they need to stay off when upload teensystripcontroller ?