490 replies to this topic

[wrd1972]

Thanks for the reply MJR.

 

Yeah I have tried the recent code you mentioned. I also performed the uninstall, then re-install hoping that would fix the issue. Still no improvement.

 

"what are you seeing in B2S when you look at the "plugins" status during the initial non-working run?"

I will look closer, but I think the plug-ins are active all of the time.\

 

Okay, understood on the now obsolete cabinet.xml

 

Can I get a bit more info on the following:

"So it's possible that your problems are due to leftover device listings in your config files from an earlier version."

To which config files are you referring? When I have performed a DOF uninstall, I even deleted the C:/Direct output directory...and installed from scratch. Are there config files in other places? Do I need to delete or address any files in the Tables directory?

[mjr]

Can I get a bit more info on the following:

"So it's possible that your problems are due to leftover device listings in your config files from an earlier version."

To which config files are you referring? When I have performed a DOF uninstall, I even deleted the C:/Direct output directory...and installed from scratch. Are there config files in other places? Do I need to delete or address any files in the Tables directory?

 

The config file with the old Sainsmart entries is Cabinet.xml.  If you deleted the whole folder, it should be gone, but you could always do a disk-wide search for Cabinet.xml to make sure DOF isn't sneakily finding one lurking in a dark corner somewhere.  

 

What you should probably really focus on is getting logging to work.  Without the log this is pure guesswork - the log might at least provide some clue about what's going wrong.

[Outhere]

Post your --- GlobalConfig_B2SServer.xml

[wrd1972]

Okay. Starting from scratch again.

 

Removed all DOF.

Reinstalled DOF from the link posted on the 9th of this month.

Nothing else run or configured.

Quick tested...DOF does work, but the original issue remains, not all of the three Sainsmart controllers work on first table start. But all work on 2nd table start.

 

Dont see GlobalConfig_B2SServer.xml

Where do I find the above file. Or should I run something first, to generate the file.

[Outhere]

Double click GlobalConfigEditor.exe it will open a new window and click on the ini files tab and down in the middle it'll say ini files path click on select Ini files path and then find your direct output folder and under that should be config highlight config then click okay... now close the global configuration editor and it may ask you about changing the configuration say yes and then a new window will open save the file in your config Folder and call it GlobalConfig_B2SServer.xml

----

 

In your directoutput folder make a text file and change it to  DirectOutput.log

 

Then see if the log will work if not then Post your --- GlobalConfig_B2SServer.xml

Edited by Outhere, 21 September 2018 - 10:59 PM.

[wrd1972]

Outhere,

A million thanks.

 

Okay, I followed the instructions to the letter. Still nothing getting into the log file.

 

Here is the .xml:

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 3.1.6816.20714: 2018-09-21 19-46-37-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>10</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <PacLedDefaultMinCommandIntervalMs>10</PacLedDefaultMinCommandIntervalMs>
  <IniFilesPath>C:\DirectOutput\Config</IniFilesPath>
  <CabinetConfigFilePattern></CabinetConfigFilePattern>
  <TableConfigFilePatterns />
  <EnableLogging>true</EnableLogging>
  <ClearLogOnSessionStart>true</ClearLogOnSessionStart>
  <LogFilePattern>.\DirectOutput.log</LogFilePattern>
</GlobalConfig>

[Outhere]

Change this line <LogFilePattern>.\DirectOutput.log</LogFilePattern>

to

<LogFilePattern>C:\DirectOutput\DirectOutput.log</LogFilePattern>

[wrd1972]

Now we have a log.

 

Okay, I started a table, and none of the three Sainsmarts were working:

---------------------------------------------------------------------------------
DirectOutput Version 3.1.6816.20714, built 2018.08.30 11:30
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2018.09.21 20:17:31.929    DirectOutput Logger initialized
2018.09.21 20:17:31.828    Pre-loading DLL Ciloci.Flee.dll from C:\DIRECTOUTPUT\Ciloci.Flee.dll : ok
2018.09.21 20:17:31.832    Pre-loading DLL Extensions.dll from C:\DIRECTOUTPUT\Extensions.dll : ok
2018.09.21 20:17:31.833    Pre-loading DLL FTD2XX32.dll from C:\DIRECTOUTPUT\FTD2XX32.dll : ok
2018.09.21 20:17:31.833    Pre-loading DLL Newtonsoft.Json.dll from C:\DIRECTOUTPUT\Newtonsoft.Json.dll : ok
2018.09.21 20:17:31.834    Pre-loading DLL PacDrive32.dll from C:\DIRECTOUTPUT\PacDrive32.dll : ok
2018.09.21 20:17:31.834    Pre-loading DLL Q42.HueApi.ColorConverters.dll from C:\DIRECTOUTPUT\Q42.HueApi.ColorConverters.dll : ok
2018.09.21 20:17:31.835    Pre-loading DLL Q42.HueApi.dll from C:\DIRECTOUTPUT\Q42.HueApi.dll : ok
2018.09.21 20:17:31.905    Global config filename is "C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml"
2018.09.21 20:17:31.929    Global config loaded from: C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml
2018.09.21 20:17:31.929    Loading Pinball parts
2018.09.21 20:17:31.929    Loading cabinet
2018.09.21 20:17:31.929    No cabinet config file loaded. Will use AutoConfig.
2018.09.21 20:17:31.930    Cabinet auto configuration started
2018.09.21 20:17:32.018    PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2018.09.21 20:17:32.539    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[0], name=FT245RBitbangController 0, description: ZB Plunger Output, serial #ZBPLUNGE01
2018.09.21 20:17:32.540    Detected and added FT245RBitbangController Id 0 with name FT245RBitbangController 0
2018.09.21 20:17:32.541    Added LedwizEquivalent Nr. 40 with name FT245RBitbangController 0 Equivalent 1 for PacUIO with Id 0
2018.09.21 20:17:32.541    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[1], name=FT245RBitbangController 1, description: FT245R USB FIFO, serial #AL00CV9I
2018.09.21 20:17:32.541    Detected and added FT245RBitbangController Id 1 with name FT245RBitbangController 1
2018.09.21 20:17:32.541    Added LedwizEquivalent Nr. 41 with name FT245RBitbangController 1 Equivalent 1 for PacUIO with Id 1
2018.09.21 20:17:32.541    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[2], name=FT245RBitbangController 2, description: FT245R USB FIFO, serial #AI05363W
2018.09.21 20:17:32.541    Detected and added FT245RBitbangController Id 2 with name FT245RBitbangController 2
2018.09.21 20:17:32.541    Added LedwizEquivalent Nr. 42 with name FT245RBitbangController 2 Equivalent 1 for PacUIO with Id 2
2018.09.21 20:17:32.541    Cabinet auto configuration finished
2018.09.21 20:17:32.541    Cabinet loaded
2018.09.21 20:17:32.541    Loading table config
2018.09.21 20:17:32.542    Warning: No table config file found. Will try to load config from LedControl file(s).
2018.09.21 20:17:32.542    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName grand_l4
2018.09.21 20:17:32.545    Loading LedControl file C:\DirectOutput\Config\directoutputconfig40.ini
2018.09.21 20:17:32.549    Min DOF Version is 0.8 for file directoutputconfig40.ini
2018.09.21 20:17:32.697    Loading LedControl file C:\DirectOutput\Config\directoutputconfig41.ini
2018.09.21 20:17:32.699    Min DOF Version is 0.8 for file directoutputconfig41.ini
2018.09.21 20:17:32.885    Loading LedControl file C:\DirectOutput\Config\directoutputconfig42.ini
2018.09.21 20:17:32.887    Min DOF Version is 0.8 for file directoutputconfig42.ini
2018.09.21 20:17:33.103    3 directoutputconfig.ini or ledcontrol.ini files loaded.
2018.09.21 20:17:33.107    Config for RomName grand_l4 exists in LedControl data. Updating cabinet and config.
2018.09.21 20:17:33.134    Table config loading finished: romname=grand_l4, tablename=Grand Lizard (Williams 1986)
2018.09.21 20:17:33.136    Pinball parts loaded
2018.09.21 20:17:33.136    Starting processes
2018.09.21 20:17:33.137    Initializing cabinet
2018.09.21 20:17:33.137    Debug: Initializing output controllers
2018.09.21 20:17:33.139    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been initialized and the updater thread has been started.
2018.09.21 20:17:33.139    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been initialized and the updater thread has been started.
2018.09.21 20:17:33.140    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been initialized and the updater thread has been started.
2018.09.21 20:17:33.140    Debug: Output controllers initialized
2018.09.21 20:17:33.144    Cabinet initialized
2018.09.21 20:17:33.149    Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2018.09.21 20:17:33.210    Framework initialized.
2018.09.21 20:17:33.210    Have fun!
2018.09.21 20:17:33.322    EXCEPTION: Could not open the connection to FTDI chip with serial number AL00CV9I.
2018.09.21 20:17:33.322    EXCEPTION: Thread: FT245RBitbangController AL00CV9I named FT245RBitbangController 1 updater thread
2018.09.21 20:17:33.322    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.09.21 20:17:33.323    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.21 20:17:33.323    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.21 20:17:33.323    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.21 20:17:33.324    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.21 20:17:33.324    Warning: No connection to FTDI chip AL00CV9I. Updater thread will terminate.
2018.09.21 20:17:33.324    EXCEPTION: Could not open the connection to FTDI chip with serial number AI05363W.
2018.09.21 20:17:33.324    EXCEPTION: Thread: FT245RBitbangController AI05363W named FT245RBitbangController 2 updater thread
2018.09.21 20:17:33.324    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.09.21 20:17:33.324    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.21 20:17:33.324    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.21 20:17:33.324    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.21 20:17:33.324    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.21 20:17:33.324    Warning: No connection to FTDI chip AI05363W. Updater thread will terminate.
2018.09.21 20:17:33.400    EXCEPTION: Could not open the connection to FTDI chip with serial number ZBPLUNGE01.
2018.09.21 20:17:33.400    EXCEPTION: Thread: FT245RBitbangController ZBPLUNGE01 named FT245RBitbangController 0 updater thread
2018.09.21 20:17:33.400    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not found.
2018.09.21 20:17:33.400    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.21 20:17:33.400    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.21 20:17:33.400    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.21 20:17:33.400    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.21 20:17:33.400    Warning: No connection to FTDI chip ZBPLUNGE01. Updater thread will terminate.
2018.09.21 20:17:42.966    Finishing framework
2018.09.21 20:17:42.968    Finishing cabinet
2018.09.21 20:17:42.969    Debug: Finishing output controllers
2018.09.21 20:17:42.970    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been finished and the updater thread has been terminated.
2018.09.21 20:17:42.970    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been finished and the updater thread has been terminated.
2018.09.21 20:17:42.970    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been finished and the updater thread has been terminated.
2018.09.21 20:17:42.970    Debug: Output controllers finished

 

Started the table a second time, all three Sainsmarts were working:

---------------------------------------------------------------------------------
DirectOutput Version 3.1.6816.20714, built 2018.08.30 11:30
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2018.09.21 20:17:31.929    DirectOutput Logger initialized
2018.09.21 20:17:31.828    Pre-loading DLL Ciloci.Flee.dll from C:\DIRECTOUTPUT\Ciloci.Flee.dll : ok
2018.09.21 20:17:31.832    Pre-loading DLL Extensions.dll from C:\DIRECTOUTPUT\Extensions.dll : ok
2018.09.21 20:17:31.833    Pre-loading DLL FTD2XX32.dll from C:\DIRECTOUTPUT\FTD2XX32.dll : ok
2018.09.21 20:17:31.833    Pre-loading DLL Newtonsoft.Json.dll from C:\DIRECTOUTPUT\Newtonsoft.Json.dll : ok
2018.09.21 20:17:31.834    Pre-loading DLL PacDrive32.dll from C:\DIRECTOUTPUT\PacDrive32.dll : ok
2018.09.21 20:17:31.834    Pre-loading DLL Q42.HueApi.ColorConverters.dll from C:\DIRECTOUTPUT\Q42.HueApi.ColorConverters.dll : ok
2018.09.21 20:17:31.835    Pre-loading DLL Q42.HueApi.dll from C:\DIRECTOUTPUT\Q42.HueApi.dll : ok
2018.09.21 20:17:31.905    Global config filename is "C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml"
2018.09.21 20:17:31.929    Global config loaded from: C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml
2018.09.21 20:17:31.929    Loading Pinball parts
2018.09.21 20:17:31.929    Loading cabinet
2018.09.21 20:17:31.929    No cabinet config file loaded. Will use AutoConfig.
2018.09.21 20:17:31.930    Cabinet auto configuration started
2018.09.21 20:17:32.018    PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2018.09.21 20:17:32.539    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[0], name=FT245RBitbangController 0, description: ZB Plunger Output, serial #ZBPLUNGE01
2018.09.21 20:17:32.540    Detected and added FT245RBitbangController Id 0 with name FT245RBitbangController 0
2018.09.21 20:17:32.541    Added LedwizEquivalent Nr. 40 with name FT245RBitbangController 0 Equivalent 1 for PacUIO with Id 0
2018.09.21 20:17:32.541    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[1], name=FT245RBitbangController 1, description: FT245R USB FIFO, serial #AL00CV9I
2018.09.21 20:17:32.541    Detected and added FT245RBitbangController Id 1 with name FT245RBitbangController 1
2018.09.21 20:17:32.541    Added LedwizEquivalent Nr. 41 with name FT245RBitbangController 1 Equivalent 1 for PacUIO with Id 1
2018.09.21 20:17:32.541    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[2], name=FT245RBitbangController 2, description: FT245R USB FIFO, serial #AI05363W
2018.09.21 20:17:32.541    Detected and added FT245RBitbangController Id 2 with name FT245RBitbangController 2
2018.09.21 20:17:32.541    Added LedwizEquivalent Nr. 42 with name FT245RBitbangController 2 Equivalent 1 for PacUIO with Id 2
2018.09.21 20:17:32.541    Cabinet auto configuration finished
2018.09.21 20:17:32.541    Cabinet loaded
2018.09.21 20:17:32.541    Loading table config
2018.09.21 20:17:32.542    Warning: No table config file found. Will try to load config from LedControl file(s).
2018.09.21 20:17:32.542    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName grand_l4
2018.09.21 20:17:32.545    Loading LedControl file C:\DirectOutput\Config\directoutputconfig40.ini
2018.09.21 20:17:32.549    Min DOF Version is 0.8 for file directoutputconfig40.ini
2018.09.21 20:17:32.697    Loading LedControl file C:\DirectOutput\Config\directoutputconfig41.ini
2018.09.21 20:17:32.699    Min DOF Version is 0.8 for file directoutputconfig41.ini
2018.09.21 20:17:32.885    Loading LedControl file C:\DirectOutput\Config\directoutputconfig42.ini
2018.09.21 20:17:32.887    Min DOF Version is 0.8 for file directoutputconfig42.ini
2018.09.21 20:17:33.103    3 directoutputconfig.ini or ledcontrol.ini files loaded.
2018.09.21 20:17:33.107    Config for RomName grand_l4 exists in LedControl data. Updating cabinet and config.
2018.09.21 20:17:33.134    Table config loading finished: romname=grand_l4, tablename=Grand Lizard (Williams 1986)
2018.09.21 20:17:33.136    Pinball parts loaded
2018.09.21 20:17:33.136    Starting processes
2018.09.21 20:17:33.137    Initializing cabinet
2018.09.21 20:17:33.137    Debug: Initializing output controllers
2018.09.21 20:17:33.139    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been initialized and the updater thread has been started.
2018.09.21 20:17:33.139    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been initialized and the updater thread has been started.
2018.09.21 20:17:33.140    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been initialized and the updater thread has been started.
2018.09.21 20:17:33.140    Debug: Output controllers initialized
2018.09.21 20:17:33.144    Cabinet initialized
2018.09.21 20:17:33.149    Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2018.09.21 20:17:33.210    Framework initialized.
2018.09.21 20:17:33.210    Have fun!
2018.09.21 20:17:33.322    EXCEPTION: Could not open the connection to FTDI chip with serial number AL00CV9I.
2018.09.21 20:17:33.322    EXCEPTION: Thread: FT245RBitbangController AL00CV9I named FT245RBitbangController 1 updater thread
2018.09.21 20:17:33.322    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.09.21 20:17:33.323    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.21 20:17:33.323    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.21 20:17:33.323    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.21 20:17:33.324    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.21 20:17:33.324    Warning: No connection to FTDI chip AL00CV9I. Updater thread will terminate.
2018.09.21 20:17:33.324    EXCEPTION: Could not open the connection to FTDI chip with serial number AI05363W.
2018.09.21 20:17:33.324    EXCEPTION: Thread: FT245RBitbangController AI05363W named FT245RBitbangController 2 updater thread
2018.09.21 20:17:33.324    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.09.21 20:17:33.324    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.21 20:17:33.324    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.21 20:17:33.324    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.21 20:17:33.324    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.21 20:17:33.324    Warning: No connection to FTDI chip AI05363W. Updater thread will terminate.
2018.09.21 20:17:33.400    EXCEPTION: Could not open the connection to FTDI chip with serial number ZBPLUNGE01.
2018.09.21 20:17:33.400    EXCEPTION: Thread: FT245RBitbangController ZBPLUNGE01 named FT245RBitbangController 0 updater thread
2018.09.21 20:17:33.400    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not found.
2018.09.21 20:17:33.400    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.21 20:17:33.400    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.21 20:17:33.400    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.21 20:17:33.400    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.21 20:17:33.400    Warning: No connection to FTDI chip ZBPLUNGE01. Updater thread will terminate.
2018.09.21 20:17:42.966    Finishing framework
2018.09.21 20:17:42.968    Finishing cabinet
2018.09.21 20:17:42.969    Debug: Finishing output controllers
2018.09.21 20:17:42.970    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been finished and the updater thread has been terminated.
2018.09.21 20:17:42.970    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been finished and the updater thread has been terminated.
2018.09.21 20:17:42.970    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been finished and the updater thread has been terminated.
2018.09.21 20:17:42.970    Debug: Output controllers finished
2018.09.21 20:17:42.970    Cabinet finished
2018.09.21 20:17:42.970    DirectOutput framework finished.
2018.09.21 20:17:42.970    Bye and thanks for using!
2018.09.21 20:21:08.586    Pre-loading DLL Ciloci.Flee.dll from C:\DIRECTOUTPUT\Ciloci.Flee.dll : ok
2018.09.21 20:21:08.586    Pre-loading DLL Extensions.dll from C:\DIRECTOUTPUT\Extensions.dll : ok
2018.09.21 20:21:08.586    Pre-loading DLL FTD2XX32.dll from C:\DIRECTOUTPUT\FTD2XX32.dll : ok
2018.09.21 20:21:08.586    Pre-loading DLL Newtonsoft.Json.dll from C:\DIRECTOUTPUT\Newtonsoft.Json.dll : ok
2018.09.21 20:21:08.586    Pre-loading DLL PacDrive32.dll from C:\DIRECTOUTPUT\PacDrive32.dll : ok
2018.09.21 20:21:08.586    Pre-loading DLL Q42.HueApi.ColorConverters.dll from C:\DIRECTOUTPUT\Q42.HueApi.ColorConverters.dll : ok
2018.09.21 20:21:08.586    Pre-loading DLL Q42.HueApi.dll from C:\DIRECTOUTPUT\Q42.HueApi.dll : ok
2018.09.21 20:21:08.645    Global config filename is "C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml"
2018.09.21 20:21:08.649    Global config loaded from: C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml
2018.09.21 20:21:08.649    Loading Pinball parts
2018.09.21 20:21:08.649    Loading cabinet
2018.09.21 20:21:08.649    No cabinet config file loaded. Will use AutoConfig.
2018.09.21 20:21:08.649    Cabinet auto configuration started
2018.09.21 20:21:08.654    PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2018.09.21 20:21:09.169    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[0], name=FT245RBitbangController 0, description: ZB Plunger Output, serial #ZBPLUNGE01
2018.09.21 20:21:09.169    Detected and added FT245RBitbangController Id 0 with name FT245RBitbangController 0
2018.09.21 20:21:09.169    Added LedwizEquivalent Nr. 40 with name FT245RBitbangController 0 Equivalent 1 for PacUIO with Id 0
2018.09.21 20:21:09.170    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[1], name=FT245RBitbangController 1, description: FT245R USB FIFO, serial #AL00CV9I
2018.09.21 20:21:09.170    Detected and added FT245RBitbangController Id 1 with name FT245RBitbangController 1
2018.09.21 20:21:09.170    Added LedwizEquivalent Nr. 41 with name FT245RBitbangController 1 Equivalent 1 for PacUIO with Id 1
2018.09.21 20:21:09.170    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[2], name=FT245RBitbangController 2, description: FT245R USB FIFO, serial #AI05363W
2018.09.21 20:21:09.170    Detected and added FT245RBitbangController Id 2 with name FT245RBitbangController 2
2018.09.21 20:21:09.170    Added LedwizEquivalent Nr. 42 with name FT245RBitbangController 2 Equivalent 1 for PacUIO with Id 2
2018.09.21 20:21:09.170    Cabinet auto configuration finished
2018.09.21 20:21:09.170    Cabinet loaded
2018.09.21 20:21:09.170    Loading table config
2018.09.21 20:21:09.170    Warning: No table config file found. Will try to load config from LedControl file(s).
2018.09.21 20:21:09.170    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName grand_l4
2018.09.21 20:21:09.170    Loading LedControl file C:\DirectOutput\Config\directoutputconfig40.ini
2018.09.21 20:21:09.172    Min DOF Version is 0.8 for file directoutputconfig40.ini
2018.09.21 20:21:09.296    Loading LedControl file C:\DirectOutput\Config\directoutputconfig41.ini
2018.09.21 20:21:09.302    Min DOF Version is 0.8 for file directoutputconfig41.ini
2018.09.21 20:21:09.480    Loading LedControl file C:\DirectOutput\Config\directoutputconfig42.ini
2018.09.21 20:21:09.482    Min DOF Version is 0.8 for file directoutputconfig42.ini
2018.09.21 20:21:09.702    3 directoutputconfig.ini or ledcontrol.ini files loaded.
2018.09.21 20:21:09.705    Config for RomName grand_l4 exists in LedControl data. Updating cabinet and config.
2018.09.21 20:21:09.708    Table config loading finished: romname=grand_l4, tablename=Grand Lizard (Williams 1986)
2018.09.21 20:21:09.708    Pinball parts loaded
2018.09.21 20:21:09.708    Starting processes
2018.09.21 20:21:09.708    Initializing cabinet
2018.09.21 20:21:09.708    Debug: Initializing output controllers
2018.09.21 20:21:09.709    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been initialized and the updater thread has been started.
2018.09.21 20:21:09.709    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been initialized and the updater thread has been started.
2018.09.21 20:21:09.710    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been initialized and the updater thread has been started.
2018.09.21 20:21:09.710    Debug: Output controllers initialized
2018.09.21 20:21:09.710    Cabinet initialized
2018.09.21 20:21:09.710    Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2018.09.21 20:21:09.722    Framework initialized.
2018.09.21 20:21:09.722    Have fun!
2018.09.21 20:21:09.723    Connection to FTDI chip ZBPLUNGE01 established.
2018.09.21 20:21:09.726    Connection to FTDI chip AL00CV9I established.
2018.09.21 20:21:09.729    Connection to FTDI chip AI05363W established.
2018.09.21 20:21:23.634    Finishing framework
2018.09.21 20:21:23.635    Finishing cabinet
2018.09.21 20:21:23.635    Debug: Finishing output controllers
2018.09.21 20:21:23.709    Connection to FTDI chip ZBPLUNGE01 closed.
2018.09.21 20:21:23.709    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been finished and the updater thread has been terminated.
2018.09.21 20:21:23.785    Connection to FTDI chip AL00CV9I closed.
2018.09.21 20:21:23.786    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been finished and the updater thread has been terminated.
2018.09.21 20:21:23.866    Connection to FTDI chip AI05363W closed.

Edited by wrd1972, 22 September 2018 - 12:22 AM.

[Outhere]

Now maybe mjr will have something to work with

[wrd1972]

Thanks again. This is a big step forward I hope.

 

I have been so damn bummed with this issue, I have not really felt like making tables recently. Seems all my spare time has been fixing the cab, so I can show it off. But hate showing it off with this problem. Its just maddening.

 

Really want this one put to bed, so I can go back to finishing tables again.

[Outhere]

Glad to see the log is working...
More tables - good
Cab not working - Bad

[mjr]

Now we have a log.

 

Very good!

 

 

DirectOutput Version 3.1.6816.20714, built 2018.08.30 11:30

 

One thing I'll point out first is that you're still on the last "stable" R3++ rather than the experimental 2018-09-04 version.  It might be worth trying that in case my original random guess about DLL loading issues is the problem.  You can find it on my R3++ page - look specifically for the new experimental version.  It's below the stable release on the page.

 

 

So anyway, on to what's in the log.  I notice that on the first run, you're getting a gob of these errors:

 

2018.09.21 20:17:33.322    EXCEPTION: Could not open the connection to FTDI chip with serial number AL00CV9I.

2018.09.21 20:17:33.322    EXCEPTION: Thread: FT245RBitbangController AL00CV9I named FT245RBitbangController 1 updater thread
2018.09.21 20:17:33.322    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.

 

Etc.  That's consistent with the Sainsmarts not working, although it's not giving us much information beyond "no can do".  Unfortunately I think it's the nature of the Sainsmarts that there isn't much more information than that to be had, so it's not really DOF's fault for being so vague here.

 

But it does suggest a new hypothesis, which I really should have thought of earlier given your description of the problem, but I guess I missed the obvious thinking about all of the other more esoteric things that can go wrong with DOF.  So, new hypothesis:  it's a simple matter of contention for device access with something else in your system.  Are you running a front end that's also accessing the Sainsmarts, like PinballX or PuP?  If so, my money is now on a conflict there.  The Sainsmarts use that FTDI driver, which only allows one-process-at-a-time access, so if your front end isn't closing out its connection fast enough, it'll still have a lock on the device when the VP instance of DOF tries to connect.

 

You should be able to test this hypothesis by launching VP directly from Windows.  Make sure you quit out of your front end and don't leave any remnant of it running.  Also make sure that any other programs that might access DOF are shut down.

[wrd1972]

Regarding launching VP. I have been doing all testing directly from Windows (not through PinballX - PBX). Is this what you mean?

 

Now I also use PinballX too, but thats certainly not the norm.  And I do know that PBX is accessing DOF, when browsing through the tables. But again, for all of this testing, I am not going through PBX. That said, is there a way I can disconnect PBX from DOF just to see, if there is some kind of elusive conflict there?

 

I will do some more poking around. But I dont think I have anything else leveraging DOF.

[mjr]

Regarding launching VP. I have been doing all testing directly from Windows (not through PinballX - PBX). Is this what you mean?

 

Right.

 

 

Now I also use PinballX too, but thats certainly not the norm.  And I do know that PBX is accessing DOF, when browsing through the tables. But again, for all of this testing, I am not going through PBX. That said, is there a way I can disconnect PBX from DOF just to see, if there is some kind of elusive conflict there?

 

If PBX isn't running then it can't possibly be accessing DOF.  There's nothing to disconnect.  Unless you mean that you're leaving it running the background while you test, in which case you can disconnect it by quitting out of it.

 

But assuming that no other programs are running, and you're running VP directly from Windows Explorer, I don't know what else could be conflicting, so we're back to no good theory.  You're sure there's not something that you're automatically starting that could be interfering?  It doesn't have to be anything DOF-related, by the way - anything that tries to connect to the FTDI driver at any level will cause this conflict.  The one-process-at-a-time rule isn't a DOF limitation , it's the FTDI device driver's limitation.

 

I wonder if there's some self-conflict problem with the FTDI driver given that you have multiple devices.  Do you think you could try unplugging two of the three devices (your choice which two) and see if that makes any difference? 

[wrd1972]

So I had a Sainsmart folder with various items (possibly drivers) used for the Sainsmart board. I have removed it from the system. But the issue remains.

 

In device manager, under com ports. I see 4 items listed. But for giggles, I went to where you can re-assign an items comm port, and that window said there are 10 com ports in use, but they dont show up in the DM. Could there be some issue where com ports could be jacked up, and how might I fix that if so?

[mjr]

In device manager, under com ports. I see 4 items listed. But for giggles, I went to where you can re-assign an items comm port, and that window said there are 10 com ports in use, but they dont show up in the DM. Could there be some issue where com ports could be jacked up, and how might I fix that if so?

 

Seems unlikely; I think if it were some basic system setup issue, it would flat out never work, not come and go like this.

 

I think I'm still not clear on exactly what "start a table a second time" means.  Do you mean...

 

1.  The very first time you run VP after rebooting Windows, it doesn't work.  Every subsequent VP session works until you reboot Windows.

 

2.  Every single time you run VP, it fails.  But if you hit F3 to restart the ROM, without exiting VP, it works.  But if you exit VP, and run VP again, it'll fail again.

 

3.  Something else?

I took a look at the FTDI code, and as I kind of expected, there's no more detailed diagnostic information available from the FTDI hardware driver.  DOF's vague "can't connect" is really all the information that's available.

[gtxjoe]

How do you open and start the table the first time? And the second time?

[wrd1972]

Ok I will spell it out in detail.

As a reminder, I have the following 3 Sainsmart controllers in my cab:

• 2x Sainsmart 8- channel relays USB controllers
• Zebs Deluxe plunger controller . Has a Sainsmart controller built in for the lighted buttons features.

 

Execute VP10.

Load any given table through the editor.

Play the table.

• Typically, the 3 controllers will not ALL work during play. Might be 1, might be 2.  On occasion, all 3 will work. But usually, 1 or 2 will not work. Sometimes, none of the 3 will work. Its very random.

Exit the table.

Restart the table (same VP10 session).

• Every time...all three controllers work as they should. No issues at all. Things work great.
• Same sucessful results for all tables, within the current VP10 session.

Now if you close out the VP10 session, and start a new one. Im back to the events described above.

[gtxjoe]

Is it reliable if you just have one of the sainsmart controllers connected?

[mjr]

Is it reliable if you just have one of the sainsmart controllers connected?

 

I'll second that - try running with just one of the three devices plugged in.

 

Is anyone else seeing this run once = fail, run twice = good behavior?  Regardless of device configuration.

 

And separately, does anyone else have multiple Sainsmart units that you're running with DOF R3++?

Ok I will spell it out in detail.

 

Thanks - that's exactly the kind of detail I was after.

 

One thing about that particular order of events is that the DOF DLL is going to get loaded once each time you load VP.  So maybe there's something about the order or timing of the DLL loading such that DOF isn't ready on the initial load, but it works on the second attempt because everything has had time to stabilize

 

I'd suggest a third time that you try the experimental 2018-09-04 version, because it's (supposed to be) more reliable about the DLL loading.