Jump to content



Photo
- - - - -

Addressable LED’s - Help Needed

Addressable LED

  • Please log in to reply
25 replies to this topic

#1 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 09 October 2019 - 09:31 PM

Hi all, I’m trying to setup two addressable LED strips (54 LED’s ea) using a teensy with octows2811. I’m fairly certain I have them wired correctly as running the basic test in the Arduino app works fine. I’ve set everything up in the DOF config tool per numerous tutorials. I’ve created my cabinet.xml, globalconfig.xml and globalconfig_b2sserver.xml per tutorials. When I launch a game, all the LED’s turn on in white and stay on. No effects and the LED’s remain on when exiting a table. Any guidance or insight is appreciated.

 

Thanks!



#2 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 09 October 2019 - 09:33 PM

https://www.vpforums...showtopic=41655



#3 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 09 October 2019 - 11:14 PM

Thanks, that worked! Now I have another issue... The last two LED's on each strip are lit dimly blue. Any idea what that could be? 



#4 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 10 October 2019 - 12:26 AM

I have not heard of somebody having that problem

Are you sure your Cabinet file matches your hardware as far as lights



#5 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 10 October 2019 - 11:02 PM

Got it squared away... I had the starting number of the second strip set the same as the end of the first strip.

 

Is there a tutorial for getting DOFLinx working with addressable LED's?



#6 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 10 October 2019 - 11:59 PM

I don't believe there is a tutorial for that but

Download DOFlinks 6.84

https://www.vpforums...&showfile=12318

And unzip - put the files in your directoutput folder

And take a look at this thread

https://www.vpforums...showtopic=42014

We just got this guy going so if you go through the whole thread you will more then likely figure out what you have to do

If not them post



#7 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 11 October 2019 - 12:15 AM

Thanks, I'm already running 6.84 and all functionality works except for addressable LED's. I read through that thread you pointed me to already. I'm not getting any errors, just the addressable strips do nothing in DOFLInx. Cabinet file belo:

 

<?xml version="1.0" encoding="utf-8"?>
<!-- This config file will set up two addressable LED strips orange on the right and blue on the left. Each is 53 long and have the distal LED as the first in the array -->
<Cabinet xmlns:xsi="http://www.w3.org/20...chema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> 
<Name>Virtual Pinball</Name> 
<OutputControllers>   
<TeensyStripController>
<Name>TeensyStripController</Name>     
<NumberOfLedsStrip1>55</NumberOfLedsStrip1>      
<NumberOfLedsStrip2>55</NumberOfLedsStrip2>
<NumberOfLedsStrip3>0</NumberOfLedsStrip3>     
<NumberOfLedsStrip4>0</NumberOfLedsStrip4>     
<NumberOfLedsStrip5>0</NumberOfLedsStrip5>     
<NumberOfLedsStrip6>0</NumberOfLedsStrip6>     
<NumberOfLedsStrip7>0</NumberOfLedsStrip7>     
<NumberOfLedsStrip8>0</NumberOfLedsStrip8>     
<ComPortName>COM4</ComPortName>   
</TeensyStripController> 
</OutputControllers> 
<Toys>   
<LedStrip>     
<Name>PF Right</Name>     
<Width>1</Width>
<Height>55</Height>     
<LedStripArrangement>BottomUpLeftRight</LedStripArrangement>   
<ColorOrder>GRB</ColorOrder>     
<FirstLedNumber>1</FirstLedNumber>     
<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
<OutputControllerName>TeensyStripController</OutputControllerName>   
</LedStrip>
<LedStrip>
<Name>PF Left</Name> Same a above
<Width>1</Width>
<Height>55</Height>     
<LedStripArrangement>BottomUpLeftRight</LedStripArrangement>     
<ColorOrder>GRB</ColorOrder>     
<FirstLedNumber>56</FirstLedNumber>      
<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>    
<OutputControllerName>TeensyStripController</OutputControllerName>   
</LedStrip>
<LedWizEquivalent>
<Name>LedWizEquivalent 30</Name>
<Outputs>
<LedWizEquivalentOutput><OutputName>PF Right</OutputName>         
<LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
</LedWizEquivalentOutput><LedWizEquivalentOutput>         
<OutputName>PF Left</OutputName>         
<LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber> 
</LedWizEquivalentOutput>     
</Outputs>
<LedWizNumber>30</LedWizNumber>
</LedWizEquivalent>
</Toys>
<AutoConfigEnabled>true</AutoConfigEnabled>
</Cabinet>



#8 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 11 October 2019 - 01:13 AM

Is it working in VP

 

This is the DOF for VP   ---- Grander Unified-er DOF R3++

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

 

This is the DOF for FX2,FX3 and FP  --- DOFlinks

https://www.vpforums...&showfile=12318



#9 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 11 October 2019 - 10:00 AM

Yes, the addressable LED’s are working in VP and PinballX. Just can’t seem to get them going in FX3... all other toys are working in FX3 as well... flashers, contractors, b2s. I’ve noticed in FX3 that the teensy is not receiving any commands. The light blinks slowly as it does when not in use.



#10 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 11 October 2019 - 12:55 PM

Post your DOFLinx.ini and DOFLinx.log



#11 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 11 October 2019 - 01:02 PM

DOFLinx Startup Log - Not showing Teensy

 

11-Oct-19 09:01:16.231 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
11-Oct-19 09:01:16.245 - Starting up - version 6.84
11-Oct-19 09:01:16.254 - For support come and visit the community here http://www.vpforums....p?showforum=104
11-Oct-19 09:01:16.262 - Pre-Reading DOFLinx.INI startup config file details
11-Oct-19 09:01:16.348 - DEBUG enabled with showing of window True
11-Oct-19 09:01:16.367 - No DOF Global Config file supplied
11-Oct-19 09:01:16.555 - 0 Pinscape device(s) found
11-Oct-19 09:01:16.624 - 2 LEDWiz device(s) found
11-Oct-19 09:01:16.640 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=1
11-Oct-19 09:01:16.653 - DOFLinx device:1 LEDWiz setup with 32 outputs
11-Oct-19 09:01:16.662 - DOFLinx device: 2 Initializing as LEDWiz #2 with ID=0
11-Oct-19 09:01:16.672 - DOFLinx device:2 LEDWiz setup with 32 outputs
11-Oct-19 09:01:16.680 - 0 FTDI (Sainsmart) device(s) found
11-Oct-19 09:01:16.691 - 0 PacLED64 device(s) found
11-Oct-19 09:01:16.700 - 0 Ultimate IO device(s) found
11-Oct-19 09:01:16.709 - Reading DOFLinx.INI startup config file details
11-Oct-19 09:01:16.718 - Turning DEBUG off
11-Oct-19 09:01:16.749 - DEBUG enabled with showing of window True
11-Oct-19 09:01:16.768 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig30.ini
11-Oct-19 09:01:18.390 - 0 Pinscape device(s) found
11-Oct-19 09:01:18.399 - 2 LEDWiz device(s) found
11-Oct-19 09:01:18.407 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=1
11-Oct-19 09:01:18.416 - DOFLinx device:1 LEDWiz setup with 32 outputs
11-Oct-19 09:01:18.425 - DOFLinx device: 2 Initializing as LEDWiz #2 with ID=0
11-Oct-19 09:01:18.434 - DOFLinx device:2 LEDWiz setup with 32 outputs
11-Oct-19 09:01:18.442 - 0 FTDI (Sainsmart) device(s) found
11-Oct-19 09:01:18.451 - 0 PacLED64 device(s) found
11-Oct-19 09:01:18.458 - 0 Ultimate IO device(s) found
11-Oct-19 09:01:26.232 - Shutting down
11-Oct-19 09:01:26.283 - Program close


Edited by cherg, 11 October 2019 - 01:03 PM.


#12 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 11 October 2019 - 01:32 PM

Post your DOFLinx.ini file



#13 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 11 October 2019 - 02:14 PM

Don't know how to attach a file... Text below minus game specific data for brevity:

 

 

####
# The config file for DOFLinx with most of the available settings as a sample
#
# Note - this works with LEDWiz, PacLed64, Pinscape, Ultimate I/O and Sainsmart (FTDI devices)
# Edit this file as you see fit, lines that start with a hash (#) or are blank are not processed.  This blurb and comments can be cut out if you want.
#
# Output devices 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
#
# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx
#
####
# 0 = OFF (normal operation), 1 = ON - When ON a window will appear and a log file will be created in the EXE directory.
DEBUG=1
# 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
# 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
DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig30.ini
# 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\
# 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\FX3_B2S\
# This is the folder where B2SServer.exe can be found on your system
PATH_B2S_SERVER=C:\Visual Pinball\Tables\
# If you have a PinControl2 device then uncomment the lines below.  The values provided will work unless you've got something unique
#PINCONTROL2_UNIVERSE=0
#PINCONTROL2_BROADCAST=192.168.178.50
# The list of processes that can activate DOFLinx, in this case, Pinball FX3, Future Pinball VP 9.91 and VP Physics Mod
# Activating for VP assumes the use of Flag Files to control which VP games have added "fake" force feedback
PROCESSES=Pinball FX3,Future Pinball
# An over-ride to the default setting given 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
# Set the key code for the keys being used as Left and Right flippers
# Used for the default fll back if a full link cannot be established
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=A0
R_FLIPPER_KEY=A1
# 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
# Use random colour order for the RGB undercabinet lighting
RGB_STYLE=RANDOM
# Use the flipper key press to to cause undercabinet lighting to change
RGB_TRIGGER=FLIPPER
# The minimum time for change between flipper flips, 1000mS or 1 second
RGB_MIN_TIME=1000
# The red device / port for undercabinet lighting, device #1, port 29
RGB_OUTPUT=118,215
# Turn on the attempt to make a full connection to Future Pinball when it is detected as running
FP_ATTEMPT_LINK=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=1
# The device / port for the left and right flippers, set to output device 1, left flipper solenoid on port 1 and right flipper solenoid on port 2
L_FLIPPER_OUTPUT=207
R_FLIPPER_OUTPUT=201
LINK_LF=207,50,10000,255
LINK_RF=201,50,10000,255
# The other 8 solenoid of a 10 solenoid setup using ports 4 to 11 inclusive
LINK_LS=208,50,500,255
LINK_RS=202,50,500,255
LINK_ML=209,50,500,255
LINK_MC=204,50,500,255
LINK_MR=203,50,500,255
LINK_BL=210,50,500,255
LINK_BC=206,50,500,255
LINK_BR=205,50,500,255
# Ports for the shaker, gear motor, knocker, beacon and strobe using ports 12 - 16 inclusive
#LINK_SH=112,1000,5000,255
#LINK_GR=113,750,10000,255
LINK_KN=212,120,500,255
LINK_BK=211,ON,200,255
LINK_SR=116,ON,0,255
# Ports for the lights inside the various buttons being Start, Extra Ball, Coin, Exit, Launch Ball and Fire for ports 17 to 22 inclusive
LINK_ST=120
#LINK_EB=118
LINK_CN=121
#LINK_EX=120
LINK_LB=122
#LINK_FR=122
# The device and red ports for five flashers, these have been set in the example below as on the second output device, ie LEDWiz #2
LINK_FLOL=113
LINK_FLIL=110
LINK_FLCN=107
LINK_FLIR=104
LINK_FLOR=101
# Turn on the Exit Button when DOFLinx is activated
#BUTTONS_ON=120
# 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.
# In Pinball FX3 this means when nudge keys are used it all goes red.
KEY_TO_COLOUR=A2 109 Red A3 109 Red
# Set the joystick settings for nudge with Pinscape and FX3
JOY_PORT=1
JOY_X_OFFSET=32767
JOY_Y_OFFSET=32767
FX_LEFT_NUDGE_POINT=-2500
FX_RIGHT_NUDGE_POINT=2500
FX_FORWARD_NUDGE_POINT=2500
FX_LEFT_NUDGE_KEY=4C
FX_RIGHT_NUDGE_KEY=52
FX_FORWARD_NUDGE_KEY=20
FX_LEFT_NUDGE_INPUT=A2
FX_RIGHT_NUDGE_INPUT=A3
# Configure the analogue plunger, such a Pinscape Z axis, to work with FX3
PLUNGER_AXIS=Z
PLUNGER_JOYSTICK_NUMBER=1
PLUNGER_KEY=0D
PLUNGER_PULL_POINT=40000
PLUNGER_RELEASE_POINT=20000
######## MISC SETTINGS ########
# 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

# 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
SETTING_ACTIVATE=A0,A1,A2,A3
SETTING_UP=A0
SETTING_DOWN=A1
SETTING_CHANGE=31
SETTING_EXIT=32
SETTING_MESSAGE=L Flipper = Up, R Flipper = Down, Start = Change, EB = Exit
SETTING=UnderCab,115,Under cabinet lighting disabled,Off,Y,114,150
SETTING=Addressable,119,Addressable LEDs Enabled,On,Y,118,50
SETTING=NIGHT,,Night Mode,Off,Y
#####
# Game specific colours in the formnat of a CSV of Game Name,Colour#1,Colour#2 - colours as they appear in your directoutputconfig
# Thanks to Vizzini here is a great starting list for Pinball FX2
# Extended for FX3 games by DDH69
#####


#14 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 11 October 2019 - 02:24 PM

Add this line

DIRECTOUTPUTGLOBAL=C:\DirectOutput\Config\GlobalConfig_B2SServer.xml



#15 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 11 October 2019 - 02:36 PM

That did the trick! Thank you so much for the assistance!



#16 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 14 October 2019 - 01:02 PM

Ran into another small issue while using PinballX... When I turn on my cabinet I have DOFLinx load at startup along with PinballX. It takes about 15 seconds for PinballX to start using DOFLinx however the addressable LED's don't work. When I exit from PinballX and go back in, the addressable LED's are working. All DOFLinx effects work fine when starting a VP table from PinballX. I'm guessing this has to do with startup timing. Any thoughts/ideas are appreciated,



#17 Phazer51

Phazer51

    Enthusiast

  • Platinum Supporter
  • 155 posts

  • Flag: United States of America

  • Favorite Pinball: Medieval Madness

Posted 15 October 2019 - 02:16 AM

Ran into another small issue while using PinballX... When I turn on my cabinet I have DOFLinx load at startup along with PinballX. It takes about 15 seconds for PinballX to start using DOFLinx however the addressable LED's don't work. When I exit from PinballX and go back in, the addressable LED's are working. All DOFLinx effects work fine when starting a VP table from PinballX. I'm guessing this has to do with startup timing. Any thoughts/ideas are appreciated,

I've had the same problem.

The first table I start with VPX, whether through PinballY or directly from VPX, my addressable LEDs do not work (though, other DOF features triggered through the LEDWiz do - 5 LED flasher bar and 10 solenoids). If I quit the table and restart it, even without exiting VPX, the addressable LEDs work until the system's power next gets cycled.

If you figure this out, let me know what you come up with.

Edited by Phazer51, 15 October 2019 - 02:17 AM.


#18 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 15 October 2019 - 02:33 AM

Ran into another small issue while using PinballX... When I turn on my cabinet I have DOFLinx load at startup along with PinballX. It takes about 15 seconds for PinballX to start using DOFLinx however the addressable LED's don't work. When I exit from PinballX and go back in, the addressable LED's are working. All DOFLinx effects work fine when starting a VP table from PinballX. I'm guessing this has to do with startup timing. Any thoughts/ideas are appreciated,

Turn off PinballX from starting at boot up then do everything as normal and see if that is the problem..

Grander Unified-er DOF R3++  is for VP And Pnballx

DOFLinx is for  FX2/FX3 and future pinball


If you're running programs as administrator try turning it off on all program and see how things run



#19 cherg

cherg

    Enthusiast

  • Members
  • PipPipPip
  • 54 posts

  • Flag: United States of America

  • Favorite Pinball: Whirlwind

Posted 15 October 2019 - 11:00 PM

I don't have anything running as Administrator. I removed the PinballX shortcut from startup and let the machine boot with DOFLinx only at startup. When I start PinballX manually it freezes for about 20 seconds and then starts working normally... Below is the DOF log from the PinballX folder. Definately seeing some erros just not sure why... Thoughts?

 

---------------------------------------------------------------------------------
DirectOutput Version 3.1.7011.27968, built 2019.03.13 15:32
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2019.10.15 18:55:15.815 DirectOutput Logger initialized
2019.10.15 18:55:15.798 Global config filename is "C:\DirectOutput\config\GlobalConfig_PinballX.xml"
2019.10.15 18:55:15.815 Global config loaded from: C:\DirectOutput\config\GlobalConfig_PinballX.xml
2019.10.15 18:55:15.815 Loading Pinball parts
2019.10.15 18:55:15.815 Loading cabinet
2019.10.15 18:55:15.816 Will load cabinet config file: C:\DirectOutput\Config\Cabinet.xml
2019.10.15 18:55:15.895 1 output controller defnitions and 3 toy definitions loaded from cabinet config.
2019.10.15 18:55:15.895 Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2019.10.15 18:55:15.896 Cabinet auto configuration started
2019.10.15 18:55:15.931 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2019.10.15 18:55:15.938 LedWiz-like device at VID=16700, PID=8467, product string=Dell KB216 Wired Keyboard, manufacturer string=<not available>
2019.10.15 18:55:15.940 LedWiz-like device at VID=16700, PID=8467, product string=Dell KB216 Wired Keyboard, manufacturer string=<not available>
2019.10.15 18:55:15.949 LedWiz-like device at VID=53769, PID=1056, product string=I-PAC 2, manufacturer string=Ultimarc
2019.10.15 18:55:15.959 LedWiz-like device at VID=53769, PID=1056, product string=I-PAC 2, manufacturer string=Ultimarc
2019.10.15 18:55:15.961 LedWiz-like device at VID=16700, PID=8467, product string=Dell KB216 Wired Keyboard, manufacturer string=<not available>
2019.10.15 18:55:15.962 LedWiz-like device at VID=8352, PID=241, product string=ZB 24Port DEV2, manufacturer string=Zebsboards.com
2019.10.15 18:55:15.962 HID caps: usage page=65280, usage=1, number of link collection nodes=1, output report byte length=9
2019.10.15 18:55:15.972 LedWiz-like device at VID=53769, PID=1056, product string=I-PAC 2, manufacturer string=Ultimarc
2019.10.15 18:55:15.982 LedWiz-like device at VID=53769, PID=1056, product string=I-PAC 2, manufacturer string=Ultimarc
2019.10.15 18:55:15.983 LedWiz-like device at VID=8352, PID=240, product string=ZB Lighting Board DEV1, manufacturer string=Zebsboards.com
2019.10.15 18:55:15.983 HID caps: usage page=65280, usage=1, number of link collection nodes=1, output report byte length=9
2019.10.15 18:55:15.985 Opening 32-bit LedWiz driver...
2019.10.15 18:55:15.986 Detected and added LedWiz Nr. 2 with name LedWiz 02
2019.10.15 18:55:15.986 Added LedwizEquivalent Nr. 2 with name LedWiz 02 Equivalent for Ledwiz Nr. 2
2019.10.15 18:55:15.986 Opening 32-bit LedWiz driver...
2019.10.15 18:55:15.986 Detected and added LedWiz Nr. 1 with name LedWiz 01
2019.10.15 18:55:15.986 Added LedwizEquivalent Nr. 1 with name LedWiz 01 Equivalent for Ledwiz Nr. 1
2019.10.15 18:55:15.989 Cabinet auto configuration finished
2019.10.15 18:55:15.989 Autoconfig complete.
2019.10.15 18:55:15.989 Cabinet config loaded successfully from C:\DirectOutput\Config\Cabinet.xml
2019.10.15 18:55:15.989 Cabinet loaded
2019.10.15 18:55:15.989 Loading table config
2019.10.15 18:55:15.989 No TableFilename specified, will use empty tableconfig
2019.10.15 18:55:15.989 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName PinballX
2019.10.15 18:55:15.991 Loading LedControl file C:\DirectOutput\Config\directoutputconfig.ini
2019.10.15 18:55:15.995 Min DOF Version is 0.8 for file directoutputconfig.ini
2019.10.15 18:55:16.192 Failed: @ALLRGB@
2019.10.15 18:55:16.193 Warning: Cant parse the trigger part @ALLRGB@ of the ledcontrol table config setting @allrgb@.
2019.10.15 18:55:16.193 EXCEPTION: Could not parse setting @allrgb@ in column data @allrgb@.
2019.10.15 18:55:16.193 EXCEPTION: Thread:
2019.10.15 18:55:16.193 EXCEPTION: Message: Exception --> Cant parse the part @ALLRGB@ of the ledcontrol table config setting @allrgb@.
2019.10.15 18:55:16.195 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2019.10.15 18:55:16.195 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2019.10.15 18:55:16.195 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2019.10.15 18:55:16.195 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2019.10.15 18:55:16.195 Warning: Previous exceptions occured in the line PinballY,$PBYAttractA5 Red 100 W0/$PBYAttractA4 Blue 100 W800/$PBYAttractA1 Green 100 W500/$PBYAttractA1 Orange 100 W700/$PBYWheelNext White 80 W320 L2/$PBYWheelPrev White 80 W0 L3/$PBYWheelPrevPage|$PBYWheelNextPage White 400 5 L4,$PBYAttractA5 Purple 100 W200/$PBYAttractA4 Green 100 W600/$PBYAttractA2 Yellow 100 W500/$PBYAttractA2 Cyan 100 W700/$PBYWheelNext White 80 W240 L2/$PBYWheelPrev White 80 W80 L3/$PBYWheelPrevPage|$PBYWheelNextPage White 400 5 L4,$PBYAttractA5 Blue 100 W400/$PBYAttractA4 Yellow 100 W400/$PBYAttractA3 White 100 4 W0/$PBYWheelNext White 80 W160 L2/$PBYWheelPrev White 80 W160 L3/$PBYWheelPrevPage|$PBYWheelNextPage White 400 5 L4,$PBYAttractA5 Green 100 W600/$PBYAttractA4 Orange 100 W200/$PBYAttractA2 Orange 100 W0/$PBYAttractA2 Blue 100 W300/$PBYWheelNext White 80 W80 L2/$PBYWheelPrev White 80 W240 L3/$PBYWheelPrevPage|$PBYWheelNextPage White 400 5 L4,$PBYAttractA5 Yellow 100 W800/$PBYAttractA4 Red 100 W0/$PBYAttractA1 Red 100 W0/$PBYAttractA1 Purple 100 W300/$PBYWheelNext White 80 W0 L2/$PBYWheelPrev White 80 W320 L3/$PBYWheelPrevPage|$PBYWheelNextPage White 400 5 L4,$PBYAttractR1 80/$PBYAttractR2 Blink 50 5,@allrgb@,ON Blink fu500 fd600,ON,0,0 of the ledcontrol file
2019.10.15 18:55:16.333 Loading LedControl file C:\DirectOutput\Config\directoutputconfig2.ini
2019.10.15 18:55:16.335 Min DOF Version is 0.8 for file directoutputconfig2.ini
2019.10.15 18:55:16.420 Failed: @ALLRGB@
2019.10.15 18:55:16.420 Warning: Cant parse the trigger part @ALLRGB@ of the ledcontrol table config setting @allrgb@.
2019.10.15 18:55:16.420 EXCEPTION: Could not parse setting @allrgb@ in column data @allrgb@.
2019.10.15 18:55:16.420 EXCEPTION: Thread:
2019.10.15 18:55:16.420 EXCEPTION: Message: Exception --> Cant parse the part @ALLRGB@ of the ledcontrol table config setting @allrgb@.
2019.10.15 18:55:16.420 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2019.10.15 18:55:16.420 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2019.10.15 18:55:16.420 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2019.10.15 18:55:16.420 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2019.10.15 18:55:16.420 Warning: Previous exceptions occured in the line PinballY,$PBYFlipperRIght/$PBYMagnaRight,0,0,0,0,0,$PBYFlipperLeft/$PBYMagnaLeft,0,0,0,$PBYAttractR3 2500,0,0,@allrgb@ of the ledcontrol file
2019.10.15 18:55:16.500 Loading LedControl file C:\DirectOutput\Config\directoutputconfig30.ini
2019.10.15 18:55:16.512 Min DOF Version is 0.8 for file directoutputconfig30.ini
2019.10.15 18:55:16.584 Failed: YELLOW
2019.10.15 18:55:16.584 Warning: Cant parse the trigger part YELLOW of the ledcontrol table config setting Yellow AL0 AT10 AW100 AH8 L3.
2019.10.15 18:55:16.584 EXCEPTION: Could not parse setting Yellow AL0 AT10 AW100 AH8 L3 in column data Yellow AL0 AT10 AW100 AH8 L3/W38 Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W42 Aqua 50 AH100 ADU AS300/W18 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W17 Blue 100 AT80 AH20 ADD AS300/W27 Navy AT72 AH15 F200 ADU AS200 BLINK 1000 BPW20/W27 Navy AT72 AH15 F200 ADD AS200 BLINK 1000 BPW20 W500/W27 Aqua L0 APCRed AL0 AW100 AT85 AH15/W48 Aqua 50 AH100 ADU AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W57|W58|W38 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W57|W58|W38 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W47 Blue 100 W300 AH80 ADD AS300 L25.
2019.10.15 18:55:16.584 EXCEPTION: Thread:
2019.10.15 18:55:16.584 EXCEPTION: Message: Exception --> Cant parse the part YELLOW of the ledcontrol table config setting Yellow AL0 AT10 AW100 AH8 L3.
2019.10.15 18:55:16.584 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2019.10.15 18:55:16.584 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2019.10.15 18:55:16.584 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2019.10.15 18:55:16.584 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2019.10.15 18:55:16.584 Failed: YELLOW
2019.10.15 18:55:16.584 Warning: Cant parse the trigger part YELLOW of the ledcontrol table config setting  Yellow AL0 AT80 AW100 AH8 L3.
2019.10.15 18:55:16.584 EXCEPTION: Could not parse setting  Yellow AL0 AT80 AW100 AH8 L3 in column data Yellow AL0 AT10 AW100 AH8 L3/W38 Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W42 Aqua 50 AH100 ADU AS300/W18 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W17 Blue 100 AT80 AH20 ADD AS300/W27 Navy AT72 AH15 F200 ADU AS200 BLINK 1000 BPW20/W27 Navy AT72 AH15 F200 ADD AS200 BLINK 1000 BPW20 W500/W27 Aqua L0 APCRed AL0 AW100 AT85 AH15/W48 Aqua 50 AH100 ADU AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W57|W58|W38 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W57|W58|W38 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W47 Blue 100 W300 AH80 ADD AS300 L25.
2019.10.15 18:55:16.584 EXCEPTION: Thread:
2019.10.15 18:55:16.584 EXCEPTION: Message: Exception --> Cant parse the part YELLOW of the ledcontrol table config setting  Yellow AL0 AT80 AW100 AH8 L3.
2019.10.15 18:55:16.584 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2019.10.15 18:55:16.584 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2019.10.15 18:55:16.584 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2019.10.15 18:55:16.584 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2019.10.15 18:55:16.585 Warning: Previous exceptions occured in the line dm,Yellow AL0 AT10 AW100 AH8 L3/W38 Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W42 Aqua 50 AH100 ADU AS300/W18 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W17 Blue 100 AT80 AH20 ADD AS300/W27 Navy AT72 AH15 F200 ADU AS200 BLINK 1000 BPW20/W27 Navy AT72 AH15 F200 ADD AS200 BLINK 1000 BPW20 W500/W27 Aqua L0 APCRed AL0 AW100 AT85 AH15/W48 Aqua 50 AH100 ADU AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W57|W58|W38 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W57|W58|W38 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W47 Blue 100 W300 AH80 ADD AS300 L25,Yellow AL0 AT10 AW100 AH8 L3/ Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W41 Aqua 50 AH100 ADU AS300/W15 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W16 Blue 100 AT80 AH20 ADD AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W66 Dark_violet 80 AT40 AL0 AH10 AW100 AS400 ADU L25/W66 Dark_violet 80 AT50 AL0 AH10 AW100 AS400 ADD L25/W78 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W78 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W52|W62 Blue 100 W300 AH80 ADD AS300 L25 of the ledcontrol file
2019.10.15 18:55:16.585 Failed: YELLOW
2019.10.15 18:55:16.585 Warning: Cant parse the trigger part YELLOW of the ledcontrol table config setting Yellow AL0 AT10 AW100 AH8 L3.
2019.10.15 18:55:16.585 EXCEPTION: Could not parse setting Yellow AL0 AT10 AW100 AH8 L3 in column data Yellow AL0 AT10 AW100 AH8 L3/ Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W41 Aqua 50 AH100 ADU AS300/W15 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W16 Blue 100 AT80 AH20 ADD AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W66 Dark_violet 80 AT40 AL0 AH10 AW100 AS400 ADU L25/W66 Dark_violet 80 AT50 AL0 AH10 AW100 AS400 ADD L25/W78 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W78 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W52|W62 Blue 100 W300 AH80 ADD AS300 L25.
2019.10.15 18:55:16.585 EXCEPTION: Thread:
2019.10.15 18:55:16.585 EXCEPTION: Message: Exception --> Cant parse the part YELLOW of the ledcontrol table config setting Yellow AL0 AT10 AW100 AH8 L3.
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2019.10.15 18:55:16.585 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2019.10.15 18:55:16.585 Failed: YELLOW
2019.10.15 18:55:16.585 Warning: Cant parse the trigger part YELLOW of the ledcontrol table config setting  Yellow AL0 AT40 AW100 AH8 L3.
2019.10.15 18:55:16.585 EXCEPTION: Could not parse setting  Yellow AL0 AT40 AW100 AH8 L3 in column data Yellow AL0 AT10 AW100 AH8 L3/ Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W41 Aqua 50 AH100 ADU AS300/W15 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W16 Blue 100 AT80 AH20 ADD AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W66 Dark_violet 80 AT40 AL0 AH10 AW100 AS400 ADU L25/W66 Dark_violet 80 AT50 AL0 AH10 AW100 AS400 ADD L25/W78 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W78 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W52|W62 Blue 100 W300 AH80 ADD AS300 L25.
2019.10.15 18:55:16.585 EXCEPTION: Thread:
2019.10.15 18:55:16.585 EXCEPTION: Message: Exception --> Cant parse the part YELLOW of the ledcontrol table config setting  Yellow AL0 AT40 AW100 AH8 L3.
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2019.10.15 18:55:16.585 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2019.10.15 18:55:16.585 Failed: YELLOW
2019.10.15 18:55:16.585 Warning: Cant parse the trigger part YELLOW of the ledcontrol table config setting  Yellow AL0 AT80 AW100 AH8 L3.
2019.10.15 18:55:16.585 EXCEPTION: Could not parse setting  Yellow AL0 AT80 AW100 AH8 L3 in column data Yellow AL0 AT10 AW100 AH8 L3/ Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W41 Aqua 50 AH100 ADU AS300/W15 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W16 Blue 100 AT80 AH20 ADD AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W66 Dark_violet 80 AT40 AL0 AH10 AW100 AS400 ADU L25/W66 Dark_violet 80 AT50 AL0 AH10 AW100 AS400 ADD L25/W78 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W78 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W52|W62 Blue 100 W300 AH80 ADD AS300 L25.
2019.10.15 18:55:16.585 EXCEPTION: Thread:
2019.10.15 18:55:16.585 EXCEPTION: Message: Exception --> Cant parse the part YELLOW of the ledcontrol table config setting  Yellow AL0 AT80 AW100 AH8 L3.
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigSetting..ctor(String SettingData)
2019.10.15 18:55:16.585 EXCEPTION: Stacktrace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2019.10.15 18:55:16.585 EXCEPTION: Targetsite: Void ParseSettingData(System.String)
2019.10.15 18:55:16.585 Warning: Previous exceptions occured in the line dm,Yellow AL0 AT10 AW100 AH8 L3/W38 Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W42 Aqua 50 AH100 ADU AS300/W18 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W17 Blue 100 AT80 AH20 ADD AS300/W27 Navy AT72 AH15 F200 ADU AS200 BLINK 1000 BPW20/W27 Navy AT72 AH15 F200 ADD AS200 BLINK 1000 BPW20 W500/W27 Aqua L0 APCRed AL0 AW100 AT85 AH15/W48 Aqua 50 AH100 ADU AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W57|W58|W38 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W57|W58|W38 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W47 Blue 100 W300 AH80 ADD AS300 L25,Yellow AL0 AT10 AW100 AH8 L3/ Yellow AL0 AT40 AW100 AH8 L3/ Yellow AL0 AT80 AW100 AH8 L3/W41 Aqua 50 AH100 ADU AS300/W15 Red 700 AT85 AH15 AFDEN40 AFMIN100 AFMAX160/W16 Blue 100 AT80 AH20 ADD AS300/S19|S20 White L13 AT0 AFDEN15 AFMIN10 AFMAX20/W73|W72 Dark_violet L13 AT0 AFDEN8 AFMIN150 AFMAX250 AFFADE150/W71 Red 60 AW100 AH100 ADD AS300/W81|W82|W83|W84|W85 Red M50 MAX50 AH100 ADU AS300/W66 Dark_violet 80 AT40 AL0 AH10 AW100 AS400 ADU L25/W66 Dark_violet 80 AT50 AL0 AH10 AW100 AS400 ADD L25/W78 Yellow 40 AT40 AL0 AH10 AW100 AS400 ADU L25/W78 Yellow 40 AT50 AL0 AH10 AW100 AS400 ADD L25/W52|W62 Blue 100 W300 AH80 ADD AS300 L25 of the ledcontrol file
2019.10.15 18:55:16.799 3 directoutputconfig.ini or ledcontrol.ini files loaded.
2019.10.15 18:55:16.800 Config for RomName PinballX exists in LedControl data. Updating cabinet and config.
2019.10.15 18:55:16.816 Warning: Skipped setting 3 in column 7 for LedWizEqivalent number 1 since #4500 is not a valid color specification.
2019.10.15 18:55:16.816 Warning: Skipped setting 4 in column 7 for LedWizEqivalent number 1 since = is not a valid color specification.
2019.10.15 18:55:16.817 Warning: Skipped setting 24 in column 7 for LedWizEqivalent number 1 since L109|L114|L149 is not a valid color specification.
2019.10.15 18:55:16.817 Warning: Skipped setting 25 in column 7 for LedWizEqivalent number 1 since L130|L136|L132 is not a valid color specification.
2019.10.15 18:55:16.817 Warning: Skipped setting 26 in column 7 for LedWizEqivalent number 1 since L303|L305|L304 is not a valid color specification.
2019.10.15 18:55:16.822 Warning: Skipped setting 4 in column 14 for LedWizEqivalent number 2 since #4500 is not a valid color specification.
2019.10.15 18:55:16.822 Warning: Skipped setting 5 in column 14 for LedWizEqivalent number 2 since it does not contain a color specification.
2019.10.15 18:55:16.822 Warning: Skipped setting 6 in column 14 for LedWizEqivalent number 2 since = is not a valid color specification.
2019.10.15 18:55:16.822 Warning: Skipped setting 26 in column 14 for LedWizEqivalent number 2 since L106|L105|L104 is not a valid color specification.
2019.10.15 18:55:16.822 Warning: Skipped setting 27 in column 14 for LedWizEqivalent number 2 since L109|L114|L149 is not a valid color specification.
2019.10.15 18:55:16.822 Warning: Skipped setting 28 in column 14 for LedWizEqivalent number 2 since L130|L136|L132 is not a valid color specification.
2019.10.15 18:55:16.822 Warning: Skipped setting 29 in column 14 for LedWizEqivalent number 2 since L303|L305|L304 is not a valid color specification.
2019.10.15 18:55:16.826 Table config loading finished: romname=PinballX, tablename=PinballX
2019.10.15 18:55:16.827 Pinball parts loaded
2019.10.15 18:55:16.827 Starting processes
2019.10.15 18:55:16.827 Initializing cabinet
2019.10.15 18:55:16.827 Debug: Initializing output controllers
2019.10.15 18:55:16.829 TeensyStripController TeensyStripController intialized and updater thread started.
2019.10.15 18:55:16.830 Debug: Initializing LedWiz Nr. 02
2019.10.15 18:55:16.830 TeensyStripController TeensyStripController updater thread  started.
2019.10.15 18:55:16.831 LedWiz Nr. 02 initialized and updater thread initialized.
2019.10.15 18:55:16.831 Debug: Initializing LedWiz Nr. 01
2019.10.15 18:55:16.831 LedWiz Nr. 01 initialized and updater thread initialized.
2019.10.15 18:55:16.831 Debug: Output controllers initialized
2019.10.15 18:55:16.831 Updater thread for LedWiz 02 started.
2019.10.15 18:55:16.831 Updater thread for LedWiz 01 started.
2019.10.15 18:55:16.836 Cabinet initialized
2019.10.15 18:55:16.838 Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2019.10.15 18:55:16.882 Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:70), Matrix(W:55, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:38, Width:1, Height:39)
2019.10.15 18:55:16.882 Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:70), Matrix(W:55, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:38, Width:1, Height:39)
2019.10.15 18:55:16.882 Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:70), Matrix(W:56, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:39, Width:1, Height:40)
2019.10.15 18:55:16.882 Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:70), Matrix(W:56, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:39, Width:1, Height:40)
2019.10.15 18:55:16.893 Framework initialized.
2019.10.15 18:55:16.893 Have fun! :)
2019.10.15 18:55:16.928 TeensyStripController TeensyStripController updater thread  has connected to TeensyStripController TeensyStripController.
2019.10.15 18:55:59.314 Finishing framework
2019.10.15 18:55:59.315 Finishing cabinet
2019.10.15 18:55:59.316 Debug: Finishing output controllers
2019.10.15 18:55:59.344 TeensyStripController TeensyStripController updater thread  has disconnected from TeensyStripController TeensyStripController and will terminate.
2019.10.15 18:55:59.344 TeensyStripController TeensyStripController finished and updater thread stopped.
2019.10.15 18:55:59.344 Debug: Finishing LedWiz Nr. 02
2019.10.15 18:55:59.368 Updater thread for LedWiz 02 terminated.
2019.10.15 18:55:59.390 LedWiz Nr. 02 finished and updater thread stopped.
2019.10.15 18:55:59.390 Debug: Finishing LedWiz Nr. 01
2019.10.15 18:55:59.390 Updater thread for LedWiz 01 terminated.
2019.10.15 18:55:59.401 LedWiz Nr. 01 finished and updater thread stopped.
2019.10.15 18:55:59.401 Debug: Output controllers finished
2019.10.15 18:55:59.401 Cabinet finished
2019.10.15 18:55:59.401 DirectOutput framework finished.
2019.10.15 18:55:59.401 Bye and thanks for using!


Edited by cherg, 15 October 2019 - 11:04 PM.


#20 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,806 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 15 October 2019 - 11:05 PM

What freezes

PinballX just sits there and does nothing







Also tagged with one or more of these keywords: Addressable LED