51 replies to this topic

[DDH69]

Ok, I downloaded V4 and I still have no Sainsmart. Even when I did debug =2, I get an error from Microsoft.NET Framework with Unhandled exception and that it cant load the DirectOutput.dll.

 

Until I sort out the long term fix you will need a copy of DIrectOutput.dll in the same folder as DOFLinx.exe

[DDH69]

FYI, received my SainSmart board yesterday and have spent the last 24 hours playing around with it.  I will continue to look into making this better.

[DDH69]

Anyone running the new mjr x32 / x64 installation of DirectOutput was to do a little testing with me?

[digitalarts]

May I can help? Have all components up to date, including newest x64 dof. Doflinx 8.15 for FP, FX3, FX. pinscape and teensy, all kind of dof toys.

[DDH69]

May I can help? Have all components up to date, including newest x64 dof. Doflinx 8.15 for FP, FX3, FX. pinscape and teensy, all kind of dof toys.

 

Thanks, sounds promising.  Quick question, When you installed the new mjr DirectOutput did you separate DOFLinx to the suggested C:\DOFLinx , or did you simply add DOFLinx to C:\DIrectOutput\x64\ ?

[digitalarts]

Sorry for the delay... I created and used the separate doflinx folder after updating from 7.45 (yes really) to 8.14
Copied/compared/replaced files and configs If needed.

[DDH69]

Sorry for the delay... I created and used the separate doflinx folder after updating from 7.45 (yes really) to 8.14
Copied/compared/replaced files and configs If needed.

 

Cool.  Well then, the test is to find out if the newly released 8.15 will run without a DirectOutput.dll in the same folder as DOFLinx.exe with a SainSmart.  I think it does, but I've got ssooo many versions and setups that I'm keen for independent verification.

[queequeg]

Greetings!  Trying to get DOFLinx to work on a new build.  Have a SainSmart and a Pinscape Pico device.

DOF is working great in VPX and Future Pinball, but DOFLinx throws the error above related to SainSmart when using the latest DOFLinx (8.29)
On a whim I tried the 8.14 B4 file above, and got further (it let me run the config tool), but then throws an error if I try to assign any ports to the toys.

 

Has anybody gotten the 8.29 DOFlinx to work with a SainSmart?  If so, are there any tips you can give me to get it working correctly?

Thank you!

[DDH69]

Greetings!  Trying to get DOFLinx to work on a new build.  Have a SainSmart and a Pinscape Pico device.

DOF is working great in VPX and Future Pinball, but DOFLinx throws the error above related to SainSmart when using the latest DOFLinx (8.29)
On a whim I tried the 8.14 B4 file above, and got further (it let me run the config tool), but then throws an error if I try to assign any ports to the toys.

 

Has anybody gotten the 8.29 DOFlinx to work with a SainSmart?  If so, are there any tips you can give me to get it working correctly?

Thank you!

 

Can you please post your setup and a DOFlinx.LOG with DEBUG=2 (or 1) set.  Thanks

[queequeg]

Sure thing.  Did a fresh install of 8.29.  Ran the "DOFLinxConfig.exe", got the error, and here's the DOFLinx.log file with DEBUG=2 in the DOFLinx.ini:

21-Jul-25 21:27:16.376 - *********************************************************
21-Jul-25 21:27:16.379 - DOFLinx for Pinball and MAME Emulators - DOFLinx by DDH69
21-Jul-25 21:27:16.380 - Starting up - version 8.29
21-Jul-25 21:27:16.380 - *********************************************************
21-Jul-25 21:27:16.395 - DOF (DirectOutput.dll) path used = C:\DirectOutput\x64\
21-Jul-25 21:27:16.397 - DirectOutput.dll version = 3.2.9219.33016  dated 3/29/2025 6:20:34 PM
21-Jul-25 21:27:16.422 - Windows OS on X64 processor with 64 bit operating system and 64 bit application
21-Jul-25 21:27:16.423 - If you like it, please make a donation here https://www.paypal.com/donate?hosted_button_id=YEPCTUYFX5KDE
21-Jul-25 21:27:16.423 - The guide can be found here https://doflinx.github.io/docs/
21-Jul-25 21:27:16.423 - For support come and visit the community here https://www.vpforums.org/index.php?showforum=104
21-Jul-25 21:27:16.425 - Pre-Reading DOFLinx.ini startup config file details
21-Jul-25 21:27:16.467 - DEBUG enabled with showing of window False
21-Jul-25 21:27:18.109 - Joystick # 1 detected : 32 buttons   DPAD Z-Axis
21-Jul-25 21:27:18.118 - DOFLinx device: 1 Initializing as PSPico #1 with name=Main Pico
21-Jul-25 21:27:18.119 - DOFLinx device:1 PSPico setup with 2 outputs
21-Jul-25 21:27:18.512 - PinOne Port = 
21-Jul-25 21:27:18.520 - Starting FTDI (Sainsmart) controller failed with error - System.InvalidCastException: Method invocation failed because 'Public Function GetDeviceList(devicelist As DirectOutput.Cab.Out.FTDIChip.FTDI.FT_DEVICE_INFO_NODE()) As DirectOutput.Cab.Out.FTDIChip.FTDI.FT_STATUS' cannot be called with these arguments:
    Argument matching parameter 'devicelist' cannot convert from 'FT_DEVICE_INFO_NODE()' to 'FT_DEVICE_INFO_NODE()'.
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ResolveCall(Container BaseReference, String MethodName, MemberInfo[] Members, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, BindingFlags LookupFlags, Boolean ReportErrors, ResolutionFailure& Failure)
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
   at DOFLinx.MainForm.Start_DOF(Boolean TheDebug)

Not sure what you mean by my "setup", what info can I give you regarding that?

Thank you!

[DDH69]

Sure thing.  Did a fresh install of 8.29.  Ran the "DOFLinxConfig.exe", got the error, and here's the DOFLinx.log file with DEBUG=2 in the DOFLinx.ini:

21-Jul-25 21:27:16.376 - *********************************************************
21-Jul-25 21:27:16.379 - DOFLinx for Pinball and MAME Emulators - DOFLinx by DDH69
21-Jul-25 21:27:16.380 - Starting up - version 8.29
21-Jul-25 21:27:16.380 - *********************************************************
21-Jul-25 21:27:16.395 - DOF (DirectOutput.dll) path used = C:\DirectOutput\x64\
21-Jul-25 21:27:16.397 - DirectOutput.dll version = 3.2.9219.33016  dated 3/29/2025 6:20:34 PM
21-Jul-25 21:27:16.422 - Windows OS on X64 processor with 64 bit operating system and 64 bit application
21-Jul-25 21:27:16.423 - If you like it, please make a donation here https://www.paypal.com/donate?hosted_button_id=YEPCTUYFX5KDE
21-Jul-25 21:27:16.423 - The guide can be found here https://doflinx.github.io/docs/
21-Jul-25 21:27:16.423 - For support come and visit the community here https://www.vpforums.org/index.php?showforum=104
21-Jul-25 21:27:16.425 - Pre-Reading DOFLinx.ini startup config file details
21-Jul-25 21:27:16.467 - DEBUG enabled with showing of window False
21-Jul-25 21:27:18.109 - Joystick # 1 detected : 32 buttons   DPAD Z-Axis
21-Jul-25 21:27:18.118 - DOFLinx device: 1 Initializing as PSPico #1 with name=Main Pico
21-Jul-25 21:27:18.119 - DOFLinx device:1 PSPico setup with 2 outputs
21-Jul-25 21:27:18.512 - PinOne Port = 
21-Jul-25 21:27:18.520 - Starting FTDI (Sainsmart) controller failed with error - System.InvalidCastException: Method invocation failed because 'Public Function GetDeviceList(devicelist As DirectOutput.Cab.Out.FTDIChip.FTDI.FT_DEVICE_INFO_NODE()) As DirectOutput.Cab.Out.FTDIChip.FTDI.FT_STATUS' cannot be called with these arguments:
    Argument matching parameter 'devicelist' cannot convert from 'FT_DEVICE_INFO_NODE()' to 'FT_DEVICE_INFO_NODE()'.
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ResolveCall(Container BaseReference, String MethodName, MemberInfo[] Members, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, BindingFlags LookupFlags, Boolean ReportErrors, ResolutionFailure& Failure)
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
   at DOFLinx.MainForm.Start_DOF(Boolean TheDebug)

Not sure what you mean by my "setup", what info can I give you regarding that?

Thank you!

 

Thanks.  Can you try copying c:\DirectOutput\X64\DirectOutput.dll to your DOFLinx folder and try again.  I think for FTDI boards it may still require both.  I am travelling at present and do not have my test board with me.

[queequeg]

Thank you! I copied the DirectOutput.dll as indicated (overwriting the one already in the folder).  The same error persists:

22-Jul-25 11:41:44.736 - *********************************************************
22-Jul-25 11:41:44.741 - DOFLinx for Pinball and MAME Emulators - DOFLinx by DDH69
22-Jul-25 11:41:44.743 - Starting up - version 8.29
22-Jul-25 11:41:44.743 - *********************************************************
22-Jul-25 11:41:44.842 - DOF (DirectOutput.dll) path used = C:\DirectOutput\x64\
22-Jul-25 11:41:44.844 - DirectOutput.dll version = 3.2.9219.33016  dated 3/29/2025 6:20:34 PM
22-Jul-25 11:41:44.902 - Windows OS on X64 processor with 64 bit operating system and 64 bit application
22-Jul-25 11:41:44.902 - If you like it, please make a donation here https://www.paypal.com/donate?hosted_button_id=YEPCTUYFX5KDE
22-Jul-25 11:41:44.904 - The guide can be found here https://doflinx.github.io/docs/
22-Jul-25 11:41:44.904 - For support come and visit the community here https://www.vpforums.org/index.php?showforum=104
22-Jul-25 11:41:44.905 - Pre-Reading DOFLinx.ini startup config file details
22-Jul-25 11:41:44.967 - DEBUG enabled with showing of window True
22-Jul-25 11:41:47.010 - Joystick # 1 detected : 32 buttons   DPAD Z-Axis
22-Jul-25 11:41:47.184 - DOFLinx device: 1 Initializing as PSPico #1 with name=Main Pico
22-Jul-25 11:41:47.187 - DOFLinx device:1 PSPico setup with 2 outputs
22-Jul-25 11:41:47.558 - PinOne Port = 
22-Jul-25 11:41:47.567 - Starting FTDI (Sainsmart) controller failed with error - System.InvalidCastException: Method invocation failed because 'Public Function GetDeviceList(devicelist As DirectOutput.Cab.Out.FTDIChip.FTDI.FT_DEVICE_INFO_NODE()) As DirectOutput.Cab.Out.FTDIChip.FTDI.FT_STATUS' cannot be called with these arguments:
    Argument matching parameter 'devicelist' cannot convert from 'FT_DEVICE_INFO_NODE()' to 'FT_DEVICE_INFO_NODE()'.
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ResolveCall(Container BaseReference, String MethodName, MemberInfo[] Members, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, BindingFlags LookupFlags, Boolean ReportErrors, ResolutionFailure& Failure)
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
   at DOFLinx.MainForm.Start_DOF(Boolean TheDebug)

 

[DDH69]

DOFLinx has two ways of initializing FTDI devices.

1. Queries DOF for the serial numbers (default), or

2. You provide the serial number and DOFLinx just tries to initialize it.

 

So at present your system will be using option #1 above, which is what I use.  Being away I cannot test this any further myself to try and sort out what might be happening.  So my suggestion to try and get you up and going is for you to try method #2.  This is enabled by adding a serial number line to your DOFLinx.INI file, ie "FTDI_SERIALS=xxxxxx" (no quotes)

 

I'll check in again in a couple of days to see if this has got you running.

[queequeg]

Ok, heading out of town but was able to test before I leave. It got further!  The config runs, but it looks like it's finding the device twice?  None of the "Tests" work under the "Toys" heading for the SainSmart device in the config tool.  Here's the output:

 

Update: I've tried everything I can to figure out why the device would be showing up twice.  I've tried deleting from Windows Device manager, deleting re-installing drivers, disabling devices, etc. and no matter what I do it still shows up twice (or doesn't show up at all).  I think I've hit a wall.  Any suggestions from anyone would be appreciated.
 

23-Jul-25 20:39:12.515 - *********************************************************
23-Jul-25 20:39:12.518 - DOFLinx for Pinball and MAME Emulators - DOFLinx by DDH69
23-Jul-25 20:39:12.519 - Starting up - version 8.29
23-Jul-25 20:39:12.519 - *********************************************************
23-Jul-25 20:39:12.533 - DOF (DirectOutput.dll) path used = C:\DirectOutput\x64\
23-Jul-25 20:39:12.536 - DirectOutput.dll version = 3.2.9219.33016  dated 3/29/2025 6:20:34 PM
23-Jul-25 20:39:12.560 - Windows OS on X64 processor with 64 bit operating system and 64 bit application
23-Jul-25 20:39:12.561 - If you like it, please make a donation here https://www.paypal.com/donate?hosted_button_id=YEPCTUYFX5KDE
23-Jul-25 20:39:12.561 - The guide can be found here https://doflinx.github.io/docs/
23-Jul-25 20:39:12.561 - For support come and visit the community here https://www.vpforums.org/index.php?showforum=104
23-Jul-25 20:39:12.563 - Pre-Reading DOFLinx.ini startup config file details
23-Jul-25 20:39:12.613 - DEBUG enabled with showing of window True
23-Jul-25 20:39:14.331 - Joystick # 1 detected : 32 buttons   DPAD Z-Axis
23-Jul-25 20:39:14.341 - DOFLinx device: 1 Initializing as PSPico #1 with name=Main Pico
23-Jul-25 20:39:14.343 - DOFLinx device:1 PSPico setup with 2 outputs
23-Jul-25 20:39:14.719 - PinOne Port = 
23-Jul-25 20:39:14.721 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH05153LA
23-Jul-25 20:39:14.725 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
23-Jul-25 20:39:14.738 - Reading DOFLinx.ini startup config file details
23-Jul-25 20:39:14.741 - DEBUG enabled with showing of window True
23-Jul-25 20:39:14.745 - Reading colour file named C:\DOFLinx\config\colours.ini
23-Jul-25 20:39:14.748 - The path 'C:\B2SServer\' does not exist
23-Jul-25 20:39:14.751 - The path 'C:\Pixelcade\' does not exist
23-Jul-25 20:39:14.754 - The path 'C:\HI2TXT\' does not exist
23-Jul-25 20:39:14.759 - The path 'C:\MAME\' does not exist
23-Jul-25 20:39:14.762 - The parameter 'PIXELCADE_MENU_HISCORE' with data '1' was not processed.  Realtime flag=False Process active flag=False
23-Jul-25 20:39:14.767 - Set Debug Privilege = Set OK
23-Jul-25 20:39:14.773 - No pixelcade.ini or settings.ini file could be found in the PATH_PIXELCADE= location
23-Jul-25 20:39:14.780 - Failed to start pixelweb.  Check your PATH_PIXELCADE= is correct
23-Jul-25 20:39:14.793 - C:\MAME\mame.exe for game names was not found
23-Jul-25 20:39:14.854 - Loading menu.ini
23-Jul-25 20:39:14.863 - Processing parameter 'LOAD_SOUND' with data 'LFlipper,100,LEFT_REAR,Flipper_L01,Flipper_L02,Flipper_L03,Flipper_L04,Flipper_L05,Flipper_L06,Flipper_L07,Flipper_L08,Flipper_L09,Flipper_L10,Flipper_L11' in real-time
23-Jul-25 20:39:14.875 - Processing parameter 'LOAD_SOUND' with data 'RFlipper,100,RIGHT_REAR,Flipper_R01,Flipper_R02,Flipper_R03,Flipper_R04,Flipper_R05,Flipper_R06,Flipper_R07,Flipper_R08,Flipper_R09,Flipper_R10,Flipper_R11' in real-time
23-Jul-25 20:39:14.883 - Processing parameter 'LOAD_SOUND' with data 'BallColl,100,REAR,Ball_Collide_1,Ball_Collide_2,Ball_Collide_3,Ball_Collide_4,Ball_Collide_5,Ball_Collide_6,Ball_Collide_7' in real-time
23-Jul-25 20:39:14.891 - Processing parameter 'LOAD_SOUND' with data 'DropTarget,100,SIDE,Drop_Target_Down_1,Drop_Target_Down_2,Drop_Target_Down_3,Drop_Target_Down_4,Drop_Target_Down_5,Drop_Target_Down_6' in real-time
23-Jul-25 20:39:14.914 - DOFLinx device: 1 Initializing as PSPico #1 with name=Main Pico
23-Jul-25 20:39:14.922 - DOFLinx device:1 PSPico setup with 2 outputs
23-Jul-25 20:39:15.308 - PinOne Port = 
23-Jul-25 20:39:15.315 - DOF reports 1 FTDI devices, your INI file FTDI_SERIALS= has 2 devices
23-Jul-25 20:39:15.322 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH05153LA
23-Jul-25 20:39:15.333 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
23-Jul-25 20:39:15.341 - DOFLinx Device: 3 Initializing as FTDI (Sainsmart) #2 serial # AH05153LA
23-Jul-25 20:39:15.347 - DOFLinx device:3 FTDI (Sainsmart) setup with 8 outputs
23-Jul-25 20:39:15.598 - Trigger thread starting
23-Jul-25 20:39:16.319 - Stopping ROM
23-Jul-25 20:39:21.101 - Shutting down
23-Jul-25 20:39:21.121 - Program close

Edited by queequeg, 30 July 2025 - 11:33 PM.

[queequeg]

Update: I gave up.  I believe Sainsmart is broken for the most recent DOFLinx versions.  I bought a Pico to replace the Sainsmart, and everything is working now.

[DDH69]

Update: I gave up.  I believe Sainsmart is broken for the most recent DOFLinx versions.  I bought a Pico to replace the Sainsmart, and everything is working now.

 

Glad to hear you have it sorted out via a Pico.
 

I am back with all my tools now and happy to look into it further if you still need.  From your previous post it looks like the serial is in your DOFLinx.INI twice.

[queequeg]

 

Update: I gave up.  I believe Sainsmart is broken for the most recent DOFLinx versions.  I bought a Pico to replace the Sainsmart, and everything is working now.

 

Glad to hear you have it sorted out via a Pico.
 

I am back with all my tools now and happy to look into it further if you still need.  From your previous post it looks like the serial is in your DOFLinx.INI twice.

 

Thank you. No need since I have a working system now, but I'm happy to provide info if you'd like to try some debugging.  

Correct, the latest was that if I specified the device serial in the INI file (per your suggestion), it would show up twice.  (Without doing that, it wouldn't find it at all).  

[DDH69]

Found and fixed in the next version.

[Aziels]

As always, thanks for the diligence in these issues!  
I've been reworking my table and updating DOFLinx and ran into this.  
Very much looking forward to the next release and getting everything back up and running!

[BornDead]

DOFLinx has two ways of initializing FTDI devices.

1. Queries DOF for the serial numbers (default), or

2. You provide the serial number and DOFLinx just tries to initialize it.

 

So at present your system will be using option #1 above, which is what I use.  Being away I cannot test this any further myself to try and sort out what might be happening.  So my suggestion to try and get you up and going is for you to try method #2.  This is enabled by adding a serial number line to your DOFLinx.INI file, ie "FTDI_SERIALS=xxxxxx" (no quotes)

 

I'll check in again in a couple of days to see if this has got you running.

Thank you so much! I have two SainSmart devices and just added FTDI_SERIALS= for them both and now it´s working again!