8 replies to this topic

[JPmini]

Been at this all afternoon and I can't figure out why my solenoids are not firing... really need some help.

 

- I have a SainSmart with 8 solenoids.

- DOF 3++ installed and working fine with correctly configured directoutputconfig.ini file.

- DOFLinx 6.20 installed and working fine.

- Visual Pinball and Future Pinball (with BAM) installed and working.

- DOFLinx.vbs is in the Scripts folder.

 

DOFLinx is working perfectly fine with every iteration of Visual Pinball and I am getting force feedback. It's just Future Pinball that doesn't seem to want to connect/link.

 

I have tried enabling the FP_LINK_WAIT_TIME=600000 but that did not do the trick.

 

Here is my INI:

 

####

# 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\directoutputconfig.ini

DIRECTOUTPUTGLOBAL=c:\DirectOutput\Config\GlobalConfig_b2sServer.xml

 

# 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\DOFLinx_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\DOFLinx_FX3_B2S\

 

# This is the folder where B2SServer.exe can be found on your system

 

PATH_B2S_SERVER=C:\pinball\Visual Pinball\Tables\

 

# 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=Future Pinball,VPinball908,VPinball920,VPinball992,VPinball994,VPinballX,VPinball99_PhysMod5

 

# 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

 

# Turn on the attempt to make a full connection to Future Pinball when it is detected as running

FP_ATTEMPT_LINK=1

# FP_LINK_WAIT_TIME=600000

 

# 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

 

# 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=101

R_FLIPPER_OUTPUT=102

LINK_LF=101,50,10000,255

LINK_RF=102,50,10000,255

 

# The other 6 solenoid

LINK_LS=103,50,500,255

LINK_RS=104,50,500,255

LINK_BL=105,50,500,255

LINK_BR=106,50,500,255

LINK_MR=107,50,500,255

LINK_BC=108,50,500,255

 

----------------

 

And LOG file:

 

12-feb-18 16:27:04.776 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

12-feb-18 16:27:04.901 - Starting up - version 6.20

12-feb-18 16:27:05.089 - 0 Pinscape device(s) found

12-feb-18 16:27:05.167 - 0 LEDWiz device(s) found

12-feb-18 16:27:05.339 - 1 FTDI (Sainsmart) device(s) found

12-feb-18 16:27:05.479 - DOFLinx Device: 1 Initializing as FTDI (Sainsmart) #1 serial # A907QJBP

12-feb-18 16:27:05.511 - DOFLinx device:1 FTDI (Sainsmart) setup with 8 outputs

12-feb-18 16:27:05.604 - 0 Ultimate IO device(s) found

12-feb-18 16:27:05.604 - Reading DOFLinx.INI startup config file details

12-feb-18 16:27:05.651 - Reading DirectOutputConfig file named c:\DirectOutput\Config\directoutputconfig.ini

12-feb-18 16:27:33.618 - Processing incoming message - GAME_FLAG_FILE=â€C:\pinball\Visual,Pinball\Tables\Super,Mario,Bros,VP9_1UP_UW_V1.2FS.vptâ€

12-feb-18 16:27:33.857 - Processing parameter 'GAME_FLAG_FILE' with data 'â€C:\pinball\Visual,Pinball\Tables\Super,Mario,Bros,VP9_1UP_UW_V1.2FS.vptâ€' in real-time

12-feb-18 16:27:34.897 - Found valid process name of 'VPinball994'

12-feb-18 16:27:36.005 - Found valid process name of 'VPinball994'

12-feb-18 16:27:37.019 - Found valid process name of 'VPinball994'

12-feb-18 16:27:38.035 - Found valid process name of 'VPinball994'

12-feb-18 16:27:39.049 - Found valid process name of 'VPinball994'

12-feb-18 16:27:40.065 - Found valid process name of 'VPinball994'

12-feb-18 16:27:41.081 - Found valid process name of 'VPinball994'

12-feb-18 16:27:42.110 - Found valid process name of 'VPinball994'

12-feb-18 16:27:43.130 - Found valid process name of 'VPinball994'

12-feb-18 16:27:44.143 - Found valid process name of 'VPinball994'

12-feb-18 16:27:45.160 - Found valid process name of 'VPinball994'

12-feb-18 16:27:46.174 - Found valid process name of 'VPinball994'

12-feb-18 16:27:47.198 - Found valid process name of 'VPinball994'

12-feb-18 16:27:48.208 - Found valid process name of 'VPinball994'

12-feb-18 16:27:49.223 - Found valid process name of 'VPinball994'

12-feb-18 16:27:50.239 - Found valid process name of 'VPinball994'

12-feb-18 16:27:51.258 - Found valid process name of 'VPinball994'

12-feb-18 16:27:52.268 - Found valid process name of 'VPinball994'

12-feb-18 16:27:53.287 - Found valid process name of 'VPinball994'

12-feb-18 16:27:54.304 - Found valid process name of 'VPinball994'

12-feb-18 16:27:55.316 - Found valid process name of 'VPinball994'

12-feb-18 16:27:56.332 - Found valid process name of 'VPinball994'

12-feb-18 16:27:57.349 - Found valid process name of 'VPinball994'

12-feb-18 16:27:58.365 - Found valid process name of 'VPinball994'

12-feb-18 16:27:59.382 - Found valid process name of 'VPinball994'

12-feb-18 16:28:00.394 - Found valid process name of 'VPinball994'

12-feb-18 16:28:01.409 - Found valid process name of 'VPinball994'

12-feb-18 16:28:02.425 - Found valid process name of 'VPinball994'

12-feb-18 16:28:03.441 - Found valid process name of 'VPinball994'

12-feb-18 16:28:04.459 - Found valid process name of 'VPinball994'

12-feb-18 16:28:05.478 - Found valid process name of 'VPinball994'

12-feb-18 16:28:06.495 - Found valid process name of 'VPinball994'

12-feb-18 16:28:07.505 - Found valid process name of 'VPinball994'

12-feb-18 16:28:08.524 - Found valid process name of 'VPinball994'

12-feb-18 16:28:09.540 - Found valid process name of 'VPinball994'

12-feb-18 16:28:10.552 - Found valid process name of 'VPinball994'

12-feb-18 16:28:11.565 - Found valid process name of 'VPinball994'

12-feb-18 16:28:12.583 - Found valid process name of 'VPinball994'

12-feb-18 16:28:13.599 - Found valid process name of 'VPinball994'

12-feb-18 16:28:14.611 - Found valid process name of 'VPinball994'

12-feb-18 16:28:15.633 - Found valid process name of 'VPinball994'

12-feb-18 16:28:16.644 - Found valid process name of 'VPinball994'

12-feb-18 16:28:17.660 - Found valid process name of 'VPinball994'

12-feb-18 16:28:18.676 - Found valid process name of 'VPinball994'

12-feb-18 16:28:19.693 - Found valid process name of 'VPinball994'

12-feb-18 16:28:20.708 - Found valid process name of 'VPinball994'

12-feb-18 16:28:21.721 - Found valid process name of 'VPinball994'

12-feb-18 16:28:22.739 - Found valid process name of 'VPinball994'

12-feb-18 16:28:23.760 - Found valid process name of 'VPinball994'

12-feb-18 16:28:24.775 - Found valid process name of 'VPinball994'

12-feb-18 16:28:25.788 - Found valid process name of 'VPinball994'

12-feb-18 16:28:26.800 - Found valid process name of 'VPinball994'

12-feb-18 16:28:27.818 - Found valid process name of 'VPinball994'

12-feb-18 16:28:28.833 - Found valid process name of 'VPinball994'

12-feb-18 16:28:32.021 - Processing incoming message - GAME_FLAG_FILE=

12-feb-18 16:28:32.035 - Processing parameter 'GAME_FLAG_FILE' with data '' in real-time

12-feb-18 16:29:32.083 - Found valid process name of 'Future Pinball'

12-feb-18 16:29:32.083 - Setting Future Pinball process ID

12-feb-18 16:29:32.129 - Activated by process name : 'Future Pinball'

12-feb-18 16:29:32.145 - Named process detected and startup commenced

12-feb-18 16:29:32.145 - 0 Pinscape device(s) found

12-feb-18 16:29:32.161 - 0 LEDWiz device(s) found

12-feb-18 16:29:32.333 - 1 FTDI (Sainsmart) device(s) found

12-feb-18 16:29:32.489 - DOFLinx Device: 1 Initializing as FTDI (Sainsmart) #1 serial # A907QJBP

12-feb-18 16:29:32.489 - DOFLinx device:1 FTDI (Sainsmart) setup with 8 outputs

12-feb-18 16:29:32.504 - 0 Ultimate IO device(s) found

12-feb-18 16:29:32.520 - Process has administration rights

12-feb-18 16:29:32.536 - 64 bit OS detected

12-feb-18 16:29:32.567 - FP full name=C:\pinball\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 31-12-2010 12:23:32

12-feb-18 16:29:32.583 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:34.020 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:35.019 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:36.004 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:37.001 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:38.001 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:39.021 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:40.017 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:41.012 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:43.004 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:45.005 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:47.000 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:49.000 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:51.000 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:54.013 - Starting scan of FP process for DOFLinx code

12-feb-18 16:29:57.003 - Starting scan of FP process for DOFLinx code

12-feb-18 16:30:00.030 - Starting scan of FP process for DOFLinx code

12-feb-18 16:30:03.001 - Starting scan of FP process for DOFLinx code

12-feb-18 16:30:06.014 - Starting scan of FP process for DOFLinx code

12-feb-18 16:30:08.015 - Starting scan of FP process for DOFLinx code

12-feb-18 16:30:10.017 - Starting scan of FP process for DOFLinx code

12-feb-18 16:30:12.023 - Starting scan of FP process for DOFLinx code

12-feb-18 16:30:13.023 - Failed to find a FP table running DOFLinx code and establish a link, checking other methods

12-feb-18 16:30:13.039 - Using full colour palette

12-feb-18 16:30:13.304 - Activating process disappeared so stopping things

12-feb-18 16:30:13.320 - Stopping DOF controllers due to 'Start Each Time' flag

 

--------

 

Been reading through tons of forum posts but to no avail. Also tried a DOF'ed table from terryred but nothing.

 

Appreciate any input or thoughts.

 

 

 

[Pitbull100]

For me looks like a timing problem .....FP needs some time to load the table....from time stamp 16:29:32 to 16:30:13 DOFlinx scans about 41 seconds......may you try to check  how long it takes your table loads...within 41 seconds ?   Try to load a table which loads quickly.....

Edited by Pitbull100, 12 February 2018 - 05:24 PM.

[DDH69]

While you say you have FP_LINK_WAIT_TIME=60000 its actually commented out in the INI you posted.  Try removing the # at the beginning of the line.  @Pitbul100 is corrent, DOFLinx is using the default FP_LINK_WAIT_TIME and not finding a loaded FP table with DOFLInx in it after 40 seconds.

[JPmini]

Thank you both for the replies. I have already tried a few tables which load fast, like Aliens legacy, Space cadet, Super mario world. All load within 40 seconds and launching them from PinballX frontend by the way. Nothing... I enabled FP_LINK_WAIT_TIME once again (I tried this method prior to your reply DDH69) but as expected nothing happened, even with several reboots of the system.

Also I tried all of this with both the 2.5 and 2.7 physics versions of FP, I don't know if it makes any difference.

Edit: I also have the .NET 4.6.2 framework installed.

Edited by JPmini, 13 February 2018 - 03:31 PM.

[Pitbull100]

Does it work now ?  If not, pls check all the DLL files are flaged as "unblocked"....

[JPmini]

Not yet. I'll recheck if all dll's are unblocked. Pretty sure they are but I might have overlooked.

[JPmini]

They are all unblocked. I am at a total loss why it doesn't work.

[DDH69]

Sorry I missed your update on this thread and just caught up due to @PitBull100's post.

 

Do you have a log that you can post with the 600000 parameter?  For testing sake try 120000 as well and post.

 

Once you get the "Failed to find a FP table running DOFLinx code and establish a link, checking other methods" line in your log file it means that DOFLinx has failed to see a DOFLinx enabled table start in FP.  How long from selecting FP with your table from your front end menu is it taking to load the table to a running state?  (I am gathering you are loading via a front end and not manually starting FP then selecting a table - please confirm)

[rasmuzzen]

Did You ever solve this problem ?