15 replies to this topic

[bellatrixzen]

After a week of pulling hair out, I need to ask assistance. Been running my cab for months on way old DOF, and doflinx. Using with an LED-Wiz, and sainsmart 8ch controller.

Updated to DOF R3++ grander, and doflinx 6.5.

After update, the LED-Wiz is never recognized, with the sainsmart taking over as device 1. 

The LED-Wiz works great with LEDblinky simple test, and the PinballX plugin drives it just fine.

Doflinx just refuses to see it.

I have switched physical ports, cables, all returned same result. All dll's and other stuff are unblocked, etc etc.

 

Kind of at a loss. Any help is hugely appreciated.

Heres a snip of my log showing when I had LED-Wiz support, time elapsed during upgrades, and where I am at now.

 

Thanks, and sorry for long post!

 

04-Nov-18 13:52:58.623 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
04-Nov-18 13:52:58.717 - Starting up - version 6.11
04-Nov-18 13:52:58.779 - 1 LEDWiz device(s) found
04-Nov-18 13:52:58.810 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
04-Nov-18 13:52:58.842 - DOFLinx device:1 LEDWiz setup with 32 outputs
04-Nov-18 13:52:59.029 - 1 FTDI (Sainsmart) device(s) found
04-Nov-18 13:52:59.216 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # A506L0OC
04-Nov-18 13:52:59.248 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
04-Nov-18 13:52:59.279 - Reading DOFLinx.INI startup config file details
04-Nov-18 13:52:59.326 - Reading DirectOutputConfig file named C:\DirectOutput\config\directoutputconfig40.ini
04-Nov-18 13:52:59.388 - No DOF Global Config file supplied
04-Nov-18 13:53:41.685 - Found valid process name of 'Future Pinball'
04-Nov-18 13:53:41.732 - Setting Future Pinball process ID
04-Nov-18 13:53:41.783 - Activated by process name : 'Future Pinball'
04-Nov-18 13:53:41.821 - Named process detected and startup commenced
04-Nov-18 13:53:41.858 - 1 LEDWiz device(s) found
04-Nov-18 13:53:41.892 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
04-Nov-18 13:53:41.928 - DOFLinx device:1 LEDWiz setup with 32 outputs
04-Nov-18 13:53:41.963 - 1 FTDI (Sainsmart) device(s) found
04-Nov-18 13:53:42.000 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial #
04-Nov-18 13:53:42.036 - DOFLinx device:2 FTDI (Sainsmart) setup with 0 outputs
04-Nov-18 13:53:42.074 - Process has administration rights
04-Nov-18 13:53:42.109 - 64 bit OS detected
04-Nov-18 13:53:42.155 - FP full name=C:\pinball\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 12/31/2010 01:23:32 PM
04-Nov-18 13:53:42.194 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:44.002 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:45.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:46.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:48.002 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:50.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:52.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:54.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:56.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:53:58.002 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:54:00.002 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:54:03.000 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:54:06.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:54:09.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:54:12.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:54:15.001 - Starting scan of FP process for DOFLinx code
04-Nov-18 13:54:15.241 - FP table running DOFLinx code found and link established
04-Nov-18 13:54:15.282 - Using full colour palette
04-Nov-18 13:54:19.463 - Link is turning on device #21 for 1000 milliseconds
04-Nov-18 13:54:28.121 - Activating process disappeared so stopping things
04-Nov-18 13:54:28.212 - Stopping DOF controllers due to 'Start Each Time' flag
04-Nov-18 13:54:46.500 - Shutting down
04-Nov-18 13:54:46.531 - Program close
04-Nov-18 14:07:59.456 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
04-Nov-18 14:07:59.534 - Starting up - version 6.50
04-Nov-18 14:07:59.565 - For support come and visit the community here http://www.vpforums....p?showforum=104
04-Nov-18 14:07:59.612 - Pre-Reading DOFLinx.INI startup config file details
04-Nov-18 14:08:00.596 - 0 Pinscape device(s) found
04-Nov-18 14:08:00.643 - 0 LEDWiz device(s) found
04-Nov-18 14:08:00.674 - 1 FTDI (Sainsmart) device(s) found
04-Nov-18 14:08:00.706 - DOFLinx Device: 1 Initializing as FTDI (Sainsmart) #1 serial # A506L0OC
04-Nov-18 14:08:00.737 - DOFLinx device:1 FTDI (Sainsmart) setup with 8 outputs
04-Nov-18 14:08:00.768 - 0 Ultimate IO device(s) found
04-Nov-18 14:08:00.799 - Reading DOFLinx.INI startup config file details
04-Nov-18 14:08:00.846 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini
04-Nov-18 14:08:00.877 - Error in configuration for  left flipper trying to set device to 2 Needs to be in the range 1-1
04-Nov-18 14:08:13.226 - Shutting down
04-Nov-18 14:08:13.273 - Program close

 

 

 

 

[Outhere]

Post your DOFLinx.ini file

[bellatrixzen]

Thanks for the response, I appreciate it. Here it is. I changed the output numbers just so I could at least play with contactors and stuff while the LED-Wiz problem was being researched......

 

Thanks again

 

 

 

####
# The config file for DOFLinx
# A mad idea by DDH69 to have some flipper sounds, RGB display and turn buttons on when playing Pinball FX2 via Steam
# Its grown a lot since that silly start!
# 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
####

# location of your standard DOF outut configuration file.  Keep this as the first item in the file
DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig.ini
#DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig40.ini
DIRECTOUTPUTGLOBAL=c:\DirectOutput\config\GlobalConfig_b2sServer.xml
#PATH_FX2=C:\DirectOutput\DOFLinx_FX2\
PATH_FX3=C:\DirectOutput\DOFLinx_FX3\
#PATH_FX2_B2S=C:\DirectOutput\DOFLinx_FX2_B2S\
PATH_FX3_B2S=C:\DirectOutput\DOFLinx_FX3\
PATH_B2S_SERVER=C:\pinball\B2S\
AUTO_MX=0

# If you want to list the processes that will wake up DOFLinx, comment it out if you just want Pinball FX2
PROCESSES= Pinball FX3,Future Pinball,PinballArcadeCabinet

# If you are using flag files, comment the line below out or set to 2000 as the default.
# If you need to use the Pinball FX2 grid to select games you will want this at around 30000 - I recommend not using the FX2 grid
PROCESS_TO_ACTIVE_TIME=1

# Which DOF Controller output for the flipper solenoids / contactors
L_FLIPPER_OUTPUT=101
R_FLIPPER_OUTPUT=102
# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=25
R_FLIPPER_KEY=27
# 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
# What LEDWiz output(s) are used for RGB devices.  Just enter the Red output number.  Multiples can be entered seperated by a comma
#RGB_OUTPUT=201,204
# Rainbow - cycle through the colours, Random - pick a random next colour, A colour name as it appears in the DirectOutputConfig.ini file
RGB_STYLE=RANDOM
# What changes the colour?  Time - set time period, Flipper = flipper press after the RGB_TRIGGER minimum time (to stop rapid colour changes)
RGB_TRIGGER=FLIPPER
# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips
RGB_MIN_TIME=1000
# The button(s) to turn on when DOFLinx starts, ie the exit button LED
#BUTTONS_ON=102 104
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
#KEY_TO_OUTPUT=32 101 35 106 36 105
# Set a key to turn on a specific colour for your RGB.  The line below makes the Left Control (A2) and the Right Control (A3) turn my undercab RGB strip red.
# In Pinball FX2 this means when I nudge it all goes red.
#KEY_TO_COLOUR=A2 109 Red A3 109 Red
# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.  Handy for using it for things other than PinBall FX2
FORCE_ACTIVE=0
# If you want the program to stop when your named process stops then set this to 1.  If you want it to run in the background all the time leave it as 0
QUIT_AFTER_PROCESS=0
# 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 FX2 window game name for setting game specific colours
OUTPUT_GAME_NAME=1

####
# Sample setup to enable the Future Pinball Link.  Edit the LINK_ items to be your ports and settings.
####
FP_ATTEMPT_LINK=1
# Use the line below if you need to extend the wait time for a FP table to load
FP_LINK_WAIT_TIME=200000
LINK_LF=101,50,10000,255
LINK_RF=102,50,10000,255
LINK_LS=105,50,500,255
LINK_RS=106,50,500,255
LINK_ML=103,50,500,255
LINK_MC=107,50,500,255
LINK_MR=108,50,500,255
LINK_BL=103,50,500,255
LINK_BC=107,50,500,255
LINK_BR=108,50,500,255
#LINK_SH=115,1000,5000,255
#LINK_GR=116,750,10000,255
#LINK_KN=124,120,500,255
#LINK_ST=104,50,10000,255
#LINK_EB=104
#LINK_CN=106
#LINK_EX=105
#LINK_LB=102,50,10000,255
LINK_SR=104,ON,4000,255
#LINK_BK=207,ON,1,255
####
# 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

#####
# 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
#####
<snip>

[Outhere]

Everything works OK in VP?

I really don't see anything wrong, you may have to wait for the expert to answer

With this version -- R3++    http://mjrnet.org/pi...ll-updates.html

you do not need a cabinet file for a sainsmart 8ch controller board so

If you are still using a cabinet file for the sainsmart board that may be screwing something up

The is the latest DOFLinx  6.51

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

[bellatrixzen]

While I have VP installed, I don't use it or have any tables setup really. So, I cant really answer that.

I just run, FP, TPA Arcooda, and FX3.

 

Thanks again, much appreciated!

[DDH69]

Hmmm, looking at your log in the first post I can see two "runs" of DOFLinx.  in the first run all appears well, you get the LEDWiz initialise as device #1, FP is detected and a link established.  In the second run the LEDWiz is not detected.

 

Between those runs what happened?  Did you close DOFLinx for a reason, or do you have it set to start and stop each time you run something from your front end menu?  Is DOFLinx set to run at startup and keep running?

 

DOFLinx queries DOF for the number of LEDWiz devices and tries to initialise the number returned.  So if DOF returns 0 devices that is what DOFLinx processes.

 

Question #1 - Is DOFLinx being setup to run at startup and left running?

Question #2 - If yes to #1, then why is DOF returning 0 LEDWiz devices?

[bellatrixzen]

What you see in the log is me running DOFLinx, shutting it down, timelapse while I install Grander DOF and DOFLinx 6.50, then bootup and start DOFLinx again to test.

 

I just installed the new DOF LEDtester and it fails, while LEDblinky tester works great.

I am thinking this is more of a DOF problem?

 

Edit:

 

I start DOFLinx from shortcut on desktop, then typically load pinball X after. Nothing starts automatically...

And thanks for the help DDH

Edited by bellatrixzen, 11 November 2018 - 10:09 PM.

[DDH69]

Understood.

 

Yes probably DOF, but none-the-less needs fixing !

 

Did you replace the LEDWIz.dll along with DOF R3++ ?  You might want to check that you don't have any old LEDWiz.dll's hanging around the place too.  From memory the new DLL is about 7Kb  (sorry at work and can't check)

 

If we can't sort it out here, then get onto the DOF R3++ thread on this site as well.

[bellatrixzen]

I did replace the LEDwiz.dll in the DirectOutput directory with the new one from the link provided by Outhere earlier. I will check to make sure others aren't hiding somewhere.

Thanks very much!

[DDH69]

Is DOFLinx in the same folder as the new LEDWIz.dll ?

[bellatrixzen]

It is..

 

And close, 17kb

 

Whole thing is very strange

Edited by bellatrixzen, 11 November 2018 - 10:37 PM.

[DDH69]

If you post the contents of your DirectOutput (and if different folder with DOFLinx.exe) I can check against mine later on.

[bellatrixzen]

Ok, I will figure out where to upload it and post back once I get home from work today.

Thanks

 

[bellatrixzen]

Ok, hope this link works......

 

Thanks again!

 

https://drive.google...eUQt1OFoCRe-eL6

[DDH69]

OK, so its been a while since I looked at this.  I forgot, you don't even need LEDWiz.dll anymore !  To test with R3++ you should rename this file out and see if that makes any difference.

 

I have a slightly older release of R3++ so my files are not directly comparable.  Having said that, nothing stands out to me.

 

As a second thing to do, it would be worth setting up the logging for the Direct Output Framework and see if your LEDWiz is recognised at that point or if there are any guiding messages.

[bellatrixzen]

Renamed file and no change. It has to be a DOF thing. Checked my dof log and it never reports a LEDwiz controller.

I really appreciate the attention and support DDH! This is just a weird deal.....

 

Gonna go give the DOF thread a shot. 

Thanks again!