2 replies to this topic

[jrussell26]

I am having an issue with DOFLinx where my second Sainsmart board does not load correctly and then crashes DOFLinx completely. Both devices and the PACLED are recognised in Windows Device Manager and I can see the serial numbers of both devices in Device Manager.

 

This is the error in DOFLinx.log:-

04-Jan-26 13:45:49.456 - *********************************************************

04-Jan-26 13:45:49.460 - DOFLinx for Pinball and MAME Emulators - DOFLinx by DDH69

04-Jan-26 13:45:49.461 - Starting up - version 9.08

04-Jan-26 13:45:49.461 - *********************************************************

04-Jan-26 13:45:49.473 - No valid DirectOutput.dll file found in registry derived path of C:\DirectOutput_new\x64\

04-Jan-26 13:45:49.475 - DOF path taken from old style fixed folder search = C:\DirectOutput\

04-Jan-26 13:45:49.475 - DOF (DirectOutput.dll) path used = C:\DirectOutput\

04-Jan-26 13:45:49.477 - DirectOutput.dll version = 3.2.9219.33016  dated 04/01/2026 11:27:42

04-Jan-26 13:45:49.505 - Windows OS on X64 processor with 64 bit operating system and 64 bit application

04-Jan-26 13:45:49.506 - If you like it, please make a donation here https://www.paypal.c...d=YEPCTUYFX5KDE

04-Jan-26 13:45:49.506 - The guide can be found here https://doflinx.github.io/docs/

04-Jan-26 13:45:49.506 - For support come and visit the community here https://www.vpforums...p?showforum=104

04-Jan-26 13:45:49.508 - Pre-Reading DOFLinx.ini startup config file details

04-Jan-26 13:45:51.979 - DOFLinx Device: 1 Initializing as FTDI (Sainsmart) #1 serial # A1012345

04-Jan-26 13:45:51.981 - DOFLinx device:1 FTDI (Sainsmart) setup with 8 outputs

04-Jan-26 13:45:51.981 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #2 serial # 

04-Jan-26 13:45:51.982 - DOFLinx device:2 FTDI (Sainsmart) setup with 0 outputs

04-Jan-26 13:45:51.983 - DOFLinx device: 3 Initializing as PacLED64 #1 with ID=4

04-Jan-26 13:45:51.984 - DOFLinx device:3 PacLED64 setup with 64 outputs

04-Jan-26 13:45:51.989 - Reading DOFLinx.ini startup config file details

04-Jan-26 13:45:51.990 - Reading colour file named c:\DirectOutput\config\directoutputconfig.ini

04-Jan-26 13:45:51.998 - Error in configuration for  LINK_ item #3  trying to set device # 2 port to 4 This device has 0 ports

 

 

[DDH69]

I'm here.  Rushing out at present, will look later and let you know.

[DDH69]

OK, I only have one SainSmart device myself so can not test this situation, I will need to rely on you, sorry.

 

To be 100% clear, you state "my second Sainsmart board ", so you have two physical SainSmart board and one PedLED64 connected.  Sorry for what seems like a dumb question, but I've chased issues before without checking the obvious.

 

DOFLinx can setup FTDI devices (SainSmart) in two way, either with defined serial numbers, or via discovery from DOF.  I suspect you are using the second (default) method by just letting DOFLinx / DOF `do its thing`.  On the surface it looks like DOF is not returning a correctly populated list for the second device.  This is just my initial theory.  Assuming you are using DOFLinx self discovery, the first thing to try is explicitly defining your boards in your DOFLinx.ini file.  To do this add the following line to your DOFLinx.INI

 

FTDI_SERIALS=A1012345,xxxxxx

 

where xxxxxx is the serial number of your other board.  You can find the serial a few ways:
1. Use the FTDI tools available on the web to read it

2. Turn logging on in DOF, start up and then look at the log

3. Disconnect the first board and start DOFLinx with logging on and get it from the log.  Simply ignore any other failures.  If you see the serial number you already have, swap the plugged in boards.

 

Please run with DEBUG=1 and post the log plus the results you get.  If this doesn't solve the issue are you prepared to try a beta version of DOFLinx with more logging?

 

The "crash" you are getting should be a critical shutdown as opposed to crash.  This will be because your device #2 is seen by DOFLinx as having 0 outputs so your setup of port 4 on device #2 is unreconcilable by DOFLinx.