22 replies to this topic

[RyGuy82]

Really hopping someone can help me figure out what's wrong with my system. I'm running a virtuapin controller V3 to control my buttons, nudge and plunger and everything has been working perfectly. I just added a sainsmart relay to run a few small solenoids and on it's own that seems to work well too. The problem is when I run them at the same time. If I activate DOFlinx to run my relay, within less than a minute my controller will restart and the plunger will no longer work. The buttons still work, and so does the nudge but the plunger will be completely gone until I restart my machine or reboot the controller. I'm all so running the xbox360ce to map buttons for FX3 tables. Here is my DOFlinx.ini if this helps at all. I've tried just about everything I can think of. Please help!!
 

 

DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig.ini

 

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

 

PATH_B2S_SERVER=c:\vpinball\Visual Pinball\Tables\

 

# This is the path to where your B2SServer GlobalConfig is located. Needed for addressable led effects.

 

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\FX3\

 

PROCESSES=Pinball FX2,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

 

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

FP_ATTEMPT_LINK=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=102

R_FLIPPER_OUTPUT=104

LINK_LF=103,50,10000,255

LINK_RF=104,50,10000,255

 

# The other 8 solenoid of a 10 solenoid setup using ports 4 to 11 inclusive

LINK_LS=103,50,500,255

LINK_RS=104,50,500,255

LINK_ML=101,50,500,255

LINK_MC=102,50,500,255

LINK_MR=102,50,500,255

LINK_BL=101,50,500,255

LINK_BC=101,50,500,255

LINK_BR=102,50,500,255

 

####

# Pinscape analogue to key stroke plunger settings

####

#PLUNGER_AXIS=Z

#PLUNGER_JOYSTICK_NUMBER=1

#PLUNGER_KEY=0D

#PLUNGER_PULL_POINT=32767

#PLUNGER_RELEASE_POINT=45000

 

# Pinscape analogue nudge settings that get made into key strokes

####

#JOY_PORT=1

#JOY_X_OFFSET=32767

#JOY_Y_OFFSET=32767

#NUDGE_LEFT_POINT=-5500

#NUDGE_RIGHT_POINT=5500

#NUDGE_FORWARD_POINT=4000

#NUDGE_LEFT_KEY=4C

#NUDGE_RIGHT_KEY=52

#NUDGE_FORWARD_KEY=20

#NUDGE_LEFT_INPUT=A2

#NUDGE_RIGHT_INPUT=A3

#NUDGE_CHECK_BASIC_KEYBOARD=1

[DDH69]

Were you running DOFLinx before adding the Sainsmart, ie when all was well?

 

Have you eliminated USB hardware issues?  It could be that the KL25Z is getting disconnected.  Does the Virtuapin controller run Pinscape?  (sorry not overly familiar with this kit).  If so there is an option on the Pinscape setup regarding reconnecting.  Also, try other USB ports if you have them.  You can also try a powered hub if you have access to one.

[Juwellez]

I have the same issue but never added any toys.  Started about two years ago disconnecting the plunger.  Upgraded the entire pc (board chip mem vid card new usb cables) and still having the same issues of the board disconnecting while playing and then the plunger no longer works, till reboot of controller.

Edited by Juwellez, 10 December 2021 - 02:59 PM.

[tcadolphs]

Same exact problem!

[garnel]

Don't think DOFLinx is the source of your disconnects. I had similar issues until making sure everything was properly grounded. For example - mine would disconnect if I stepped away from the table, came back and touched the lockdown bar, as well as randomly during gameplay. When I connected the lockdown bar to ground most of the disconnects went away.   Also found that mine works better when connected directly to the computer usb port instead of using a hub.

 

2/17/22 update:

I was wrong.  Verified in my system that the disconnects only occur when DOFLinx is running. There are no disconnects if I close DOFLinx and play VPX tables. I even left it on overnight and the plunger was still working the next morning. If DOFLinx is running in the background when running VPX, disconnects happen.

Disconnects happen with FX3 as well.

 

So, when I play VPX tables, I close DOFLinx. Then the plunger works reliably.

Edited by garnel, 17 February 2022 - 07:14 PM.

[netsurfr]

I'm having this same problem with my Virtuapin KL25Z controller (running virtuapin's firmware) where it randomly disconnects for a short period of time and then reconnects. You hear the usb disconnect/reconnect Windows sound. It only happens when I have DOFLinx running. I recently installed DOFLinx to get SSF with FX3 tables as well as to get PinEvent tables working. When DOFLinx is not running in the background I don't get the disconnects. 

 

Any ideas?

[DDH69]

I'm having this same problem with my Virtuapin KL25Z controller (running virtuapin's firmware) where it randomly disconnects for a short period of time and then reconnects. You hear the usb disconnect/reconnect Windows sound. It only happens when I have DOFLinx running. I recently installed DOFLinx to get SSF with FX3 tables as well as to get PinEvent tables working. When DOFLinx is not running in the background I don't get the disconnects. 

 

Any ideas?

 

DOFLinx only talks to DOF, it does not do anything at the USB layer.  I believe connects / disconnects would be coincidental.  USB connects / disconnects are usually physical , driver or Windows related.

[netsurfr]

I'm having this same problem with my Virtuapin KL25Z controller (running virtuapin's firmware) where it randomly disconnects for a short period of time and then reconnects. You hear the usb disconnect/reconnect Windows sound. It only happens when I have DOFLinx running. I recently installed DOFLinx to get SSF with FX3 tables as well as to get PinEvent tables working. When DOFLinx is not running in the background I don't get the disconnects. 
 
Any ideas?

 
DOFLinx only talks to DOF, it does not do anything at the USB layer.  I believe connects / disconnects would be coincidental.  USB connects / disconnects are usually physical , driver or Windows related.

Thanks. Maybe coincidence but I disabled doflinx from loading at startup yesterday to test, and no disconnects at all in the last 24 hours. I’ll be testing with doflinx running again tomorrow and see if the disconnects return.


Sent from my iPhone using Tapatalk

[DDH69]

 

 

I'm having this same problem with my Virtuapin KL25Z controller (running virtuapin's firmware) where it randomly disconnects for a short period of time and then reconnects. You hear the usb disconnect/reconnect Windows sound. It only happens when I have DOFLinx running. I recently installed DOFLinx to get SSF with FX3 tables as well as to get PinEvent tables working. When DOFLinx is not running in the background I don't get the disconnects. 
 
Any ideas?

 
DOFLinx only talks to DOF, it does not do anything at the USB layer.  I believe connects / disconnects would be coincidental.  USB connects / disconnects are usually physical , driver or Windows related.

Thanks. Maybe coincidence but I disabled doflinx from loading at startup yesterday to test, and no disconnects at all in the last 24 hours. I’ll be testing with doflinx running again tomorrow and see if the disconnects return.


Sent from my iPhone using Tapatalk

 

 

You might want to try the reverse too.  Disable the custom driver for the Virtuapin and use a standard driver.  We know very well that DOFLinx and Pinscapes work very well together.

[netsurfr]

 

 

 

I'm having this same problem with my Virtuapin KL25Z controller (running virtuapin's firmware) where it randomly disconnects for a short period of time and then reconnects. You hear the usb disconnect/reconnect Windows sound. It only happens when I have DOFLinx running. I recently installed DOFLinx to get SSF with FX3 tables as well as to get PinEvent tables working. When DOFLinx is not running in the background I don't get the disconnects. 
 
Any ideas?

 
DOFLinx only talks to DOF, it does not do anything at the USB layer.  I believe connects / disconnects would be coincidental.  USB connects / disconnects are usually physical , driver or Windows related.

Thanks. Maybe coincidence but I disabled doflinx from loading at startup yesterday to test, and no disconnects at all in the last 24 hours. I’ll be testing with doflinx running again tomorrow and see if the disconnects return.


Sent from my iPhone using Tapatalk

 

 

You might want to try the reverse too.  Disable the custom driver for the Virtuapin and use a standard driver.  We know very well that DOFLinx and Pinscapes work very well together.

 

 

Will look into that too but not sure what custom driver to look for so have to figure that out first

 

Doesn't look like the virtuapin controller uses a custom driver. It's auto recognized by Windows as a controller when plugged in so must be using Windows drivers. 

[Noah Fentz]

This explains a lot. I have never been able to duplicate the disconnecting all this time, never had it show up in any machine I've built and run for hours at shows, and every kit that's been returned due to the issue has had zero issues whatsoever in all my tests. It's been absolutely baffling.

 

I've never used DOF/linx, as I don't play FX3 tables. It's certainly the common denominator, and it explains why I've never seen it in person in the years we've been offering our plunger kits.

 

DDH69, what could be the cause? Driver conflict? It runs as a default Windows game controller.

 

Thank you!

[netsurfr]

More testing today and I can confirm (& replicate) that as soon as I start DOFLinx I start hearing usb device disconnect/reconnect sounds so there's some sort of conflict going on between DOFLinx & the Virtuapin KL25Z controller.

 

DOFLinx and DOF are WIDELY used for not just FX3 tables but for force feedback, lighting, etc... 

 

Any thoughts/ideas as to what could be going or better yet how to fix it or work around it?

[DDH69]

I wonder what DOF is returning as connected devices?  Can you clear DOFLinx.LOG (delete it), add DEBUG=2 to your DOFLinx.INI file, start everything up and see if you get the connect / disconnect, note the PC time down to the second.  Share the results and the LOG file and see what we see.

 

My only thought is that DOF is reporting the device back to DOFLinx as something its not and hence DOFLinx is trying to talk inappropriately to it (not the first time I've been accused of that  ).  First working theory,, reserving the right to change with more facts.

[netsurfr]

Ok will try this out but I'm heading out of town for a week today so won't have a ton of time to test it. I was thinking along the same line as you and did look at the log files (both doflinx & dof) and "think" it dof/doflinx may think the virtuapin controller is a ledwiz device based on some log entries I saw. One thing I did last night was increase 2 scan/timing variables in global config file from 10ms to 1000ms and the disconnects seemed to have dropped a lot. I also installed a usb logging app that will log any usb connect/disconnect activity so will be looking at all this and trying your tips later this morning before heading out of town. Thanks for the help!

 

 

 

I wonder what DOF is returning as connected devices?  Can you clear DOFLinx.LOG (delete it), add DEBUG=2 to your DOFLinx.INI file, start everything up and see if you get the connect / disconnect, note the PC time down to the second.  Share the results and the LOG file and see what we see.

 

My only thought is that DOF is reporting the device back to DOFLinx as something its not and hence DOFLinx is trying to talk inappropriately to it (not the first time I've been accused of that  ).  First working theory,, reserving the right to change with more facts.

[netsurfr]

Got a disconnect during play this AM so including log info below. One thing I noticed is that when I increased the LedWiz and PacLED Default Min Command Interval in DOF Global Config Editor from 10ms to 100ms (max) then the disconnects seemed to improve meaning... in the past I would hear the disconnects even if I wasn't actually playing a table and the vpin was in "attract mode". After increasing that interval the controller didn't disconnect and I left the vpin running in attract mode overnight and found no entries in the usb data logging app I installed. Not sure if it could be related but mentioning just in case. BTW - I don't have any toys at all installed so using DOF/DOFLinx just for SSF in FX3 and PinEvent tables.

 

DOFLinx log (machine powered up at 8:06 AM & disconnect/reconnect happens at 8:24 AM. Played FP & VPX tables during that time and event happened while playing a vpx table. 

 

03-Feb-22 08:06:13.903 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

03-Feb-22 08:06:13.919 - Starting up - version 7.33

03-Feb-22 08:06:13.919 - For support come and visit the community here http://www.vpforums....p?showforum=104

03-Feb-22 08:06:13.919 - Pre-Reading DOFLinx.INI startup config file details

03-Feb-22 08:06:13.950 - DEBUG enabled with showing of window False

03-Feb-22 08:06:14.122 - Joystick # 1 detected : 16 buttons   Z-Axis

03-Feb-22 08:06:14.200 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

03-Feb-22 08:06:14.200 - Reading DOFLinx.INI startup config file details

03-Feb-22 08:06:14.200 - Turning DEBUG off

03-Feb-22 08:06:14.200 - DEBUG enabled with showing of window False

03-Feb-22 08:06:14.215 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini

03-Feb-22 08:06:14.215 - Set Debug Privilege = Set OK

03-Feb-22 08:06:16.124 - Stopping ROM

03-Feb-22 08:06:16.125 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

03-Feb-22 08:12:13.381 - Found valid process name of 'Future Pinball'

03-Feb-22 08:12:13.385 - Setting Future Pinball process ID to :9864

03-Feb-22 08:12:15.396 - Activated by process name : 'Future Pinball'

03-Feb-22 08:12:15.407 - Named process detected and startup commenced

03-Feb-22 08:12:15.410 - 64 bit OS detected

03-Feb-22 08:12:15.462 - FP full name=C:\Pinball Emporium\emulators\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 12/31/2010 2:23:32 PM

03-Feb-22 08:12:15.464 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:18.013 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:20.008 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:22.015 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:24.011 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:26.008 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:28.013 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:30.002 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:32.015 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:34.002 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:36.007 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:38.011 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:40.015 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:42.007 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:44.008 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:46.010 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:48.006 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:50.006 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:52.004 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:54.002 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:56.001 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:12:58.013 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:00.016 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:02.010 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:04.011 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:06.012 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:08.015 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:10.012 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:12.010 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:14.003 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:16.008 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:18.008 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:20.005 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:22.009 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:24.010 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:26.013 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:28.009 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:30.012 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:32.012 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:34.015 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:36.013 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:38.015 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:40.001 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:42.002 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:44.005 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:46.005 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:48.005 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:50.014 - Starting scan of FP process for DOFLinx code

03-Feb-22 08:13:51.802 - Failed to find a FP table running DOFLinx code and establish a link, checking other methods

03-Feb-22 08:13:51.806 - Using full colour palette

03-Feb-22 08:13:51.807 - 122 colours added to the palette

03-Feb-22 08:14:15.291 - Activating process disappeared so stopping things

03-Feb-22 08:14:15.294 - Stopping ROM

03-Feb-22 08:14:15.295 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

03-Feb-22 08:24:54.483 - Shutting down

03-Feb-22 08:24:54.486 - Program close

 

 

DirectOutput.log

 

irectOutput Version 3.1.7776.42172, built 2021.04.16 23:25

MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy

DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput

2022.02.03 08:06:13.981 DirectOutput Logger initialized

2022.02.03 08:06:13.966 Finishing framework

2022.02.03 08:06:13.966 Finishing cabinet

2022.02.03 08:06:13.966 Debug: Finishing output controllers

2022.02.03 08:06:13.966 Debug: Output controllers finished

2022.02.03 08:06:13.966 Cabinet finished

2022.02.03 08:06:13.966 DirectOutput framework finished.

2022.02.03 08:06:13.966 Bye and thanks for using!

2022.02.03 08:06:13.966 Global config filename is "C:\DirectOutput\config\GlobalConfig_b2SServer.xml"

2022.02.03 08:06:13.981 Global config loaded from: C:\DirectOutput\config\GlobalConfig_b2SServer.xml

2022.02.03 08:06:13.981 Loading Pinball parts

2022.02.03 08:06:13.981 Loading cabinet

2022.02.03 08:06:13.981 No cabinet config file loaded. Will use AutoConfig.

2022.02.03 08:06:13.981 Cabinet auto configuration started

2022.02.03 08:06:14.028 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)

2022.02.03 08:06:14.028 LedWiz-like device at VID=4660, PID=273, product string=VirtuaPin Controller, manufacturer string=

2022.02.03 08:06:14.044 LedWiz-like device at VID=3468, PID=258, product string=USB Sound Device        , manufacturer string=<not available>

2022.02.03 08:06:14.044 LedWiz-like device at VID=49153, PID=7658, product string=<not available>, manufacturer string=<not available>

2022.02.03 08:06:14.044 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2022.02.03 08:06:14.044 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2022.02.03 08:06:14.044 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2022.02.03 08:06:14.044 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2022.02.03 08:06:14.044 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2022.02.03 08:06:14.044 LedWiz-like device at VID=1133, PID=50475, product string=USB Receiver, manufacturer string=Logitech

2022.02.03 08:06:14.044 Cabinet auto configuration finished

2022.02.03 08:06:14.044 Cabinet loaded

2022.02.03 08:06:14.044 Loading table config

2022.02.03 08:06:14.044 No TableFilename specified, will use empty tableconfig

2022.02.03 08:06:14.044 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName doflinx

2022.02.03 08:06:14.044 Loading LedControl file C:\DirectOutput\config\directoutputconfig.ini

2022.02.03 08:06:14.059 Min DOF Version is 0.8 for file directoutputconfig.ini

2022.02.03 08:06:14.059 Warning: Could not find table config section in file C:\DirectOutput\config\directoutputconfig.ini.

2022.02.03 08:06:14.059 1 directoutputconfig.ini or ledcontrol.ini files loaded.

2022.02.03 08:06:14.059 No config for table found in LedControl data for RomName doflinx.

2022.02.03 08:06:14.059 Table config loading finished: romname=doflinx, tablename=doflinx

2022.02.03 08:06:14.059 Pinball parts loaded

2022.02.03 08:06:14.059 Starting processes

2022.02.03 08:06:14.059 Initializing cabinet

2022.02.03 08:06:14.059 Debug: Initializing output controllers

2022.02.03 08:06:14.059 Debug: Output controllers initialized

2022.02.03 08:06:14.059 Cabinet initialized

2022.02.03 08:06:14.059 Loading shape definition file: C:\DirectOutput\DirectOutputShapes.xml

2022.02.03 08:06:14.106 Framework initialized.

2022.02.03 08:06:14.106 Have fun!

2022.02.03 08:06:14.200 Initializing cabinet

2022.02.03 08:06:14.200 Debug: Initializing output controllers

2022.02.03 08:06:14.200 Debug: Output controllers initialized

2022.02.03 08:06:14.200 Cabinet initialized

2022.02.03 08:06:16.125 Finishing framework

2022.02.03 08:06:16.125 Finishing cabinet

2022.02.03 08:06:16.125 Debug: Finishing output controllers

2022.02.03 08:06:16.125 Debug: Output controllers finished

2022.02.03 08:06:16.125 Cabinet finished

2022.02.03 08:06:16.125 DirectOutput framework finished.

2022.02.03 08:06:16.125 Bye and thanks for using!

2022.02.03 08:06:16.125 Initializing cabinet

2022.02.03 08:06:16.125 Debug: Initializing output controllers

2022.02.03 08:06:16.125 Debug: Output controllers initialized

2022.02.03 08:06:16.125 Cabinet initialized

2022.02.03 08:14:15.295 Finishing framework

2022.02.03 08:14:15.295 Finishing cabinet

2022.02.03 08:14:15.295 Debug: Finishing output controllers

2022.02.03 08:14:15.295 Debug: Output controllers finished

2022.02.03 08:14:15.295 Cabinet finished

2022.02.03 08:14:15.295 DirectOutput framework finished.

2022.02.03 08:14:15.295 Bye and thanks for using!

2022.02.03 08:14:15.295 Initializing cabinet

2022.02.03 08:14:15.295 Debug: Initializing output controllers

2022.02.03 08:14:15.295 Debug: Output controllers initialized

2022.02.03 08:14:15.295 Cabinet initialized

 

USB data log:

 

==================================================

Event Type        : Unplug

Event Time        : 2/3/2022 8:24:19 AM

Device Name       : Port_#0008.Hub_#0001

Description       : USB Input Device

Device Type       : HID (Human Interface Device)

Drive Letter      : 

Serial Number     : 0123456789

Vendor ID         : 1234

Product ID        : 0111

Vendor Name       : Unknown

Product Name      : 

Firmware Revision : 1.30

USB Class         : 03

USB SubClass      : 00

USB Protocol      : 00

==================================================

 

==================================================

Event Type        : Plug

Event Time        : 2/3/2022 8:24:21 AM

Device Name       : Port_#0008.Hub_#0001

Description       : USB Input Device

Device Type       : HID (Human Interface Device)

Drive Letter      : 

Serial Number     : 0123456789

Vendor ID         : 1234

Product ID        : 0111

Vendor Name       : Unknown

Product Name      : 

Firmware Revision : 1.30

USB Class         : 03

USB SubClass      : 00

USB Protocol      : 00

==================================================

 

[DDH69]

From the LOG you can see that DOFLinx is not having any output devices reported back to it, so its definitely not trying to do anything with them.  With no output devices the best idea is to place DISABLEDOF=YES on the command line (in your shortcut) for starting up DOFLinx.  The added benefit here is that it will certainly stop DOFLinx having any active interaction with DOF for output devices.

 

Interesting that DOF changes are impacting your disconnects.  Not sure how DOFLinx could have anything to do with that?  I don't have any new ideas at present, sorry.

[netsurfr]

Couple questions I just have a shortcut in my startup folder ponying to doflinx so how can I add that argument/command you suggested? Also, could a conflict between the virtuapin controller and the doflinx DLL be an issue that wouldnt create an entry in the debug log?

From the LOG you can see that DOFLinx is not having any output devices reported back to it, so its definitely not trying to do anything with them.  With no output devices the best idea is to place DISABLEDOF=YES on the command line (in your shortcut) for starting up DOFLinx.  The added benefit here is that it will certainly stop DOFLinx having any active interaction with DOF for output devices.
 
Interesting that DOF changes are impacting your disconnects.  Not sure how DOFLinx could have anything to do with that?  I don't have any new ideas at present, sorry.

Edited by netsurfr, 04 February 2022 - 09:54 PM.

[DDH69]

So somewhere you are likely calling the DOFLinx.exe file with a pointer to the DOFLinx.INI file, this is where you add it. If not create a shortcut.  Page #3 of the guide has details of the command line options.  You probably want something like this ...

 

"DOFLinx.EXE DISBALEDOF=YES PATHINI=C;\DirectOutput\Whereever you put your INI.INI"  .  This goes in the "Target" box.  Page #33 of the guide has some screen shots of shortcuts.

[netsurfr]

Will add those arguments but dont think that will fix it so not sure where to go with this. Could there be a conflict between your DLL and the Virtuapin controller firmware that is causing this?

[DDH69]

The DLL only sets the debug permissions to be able to attach to a process.  It does no communication work at all.