490 replies to this topic

[wrd1972]

Oh should have mentioned.  I have been testing with the expirimental  code from the 9th. Saw no improvement.

 

I will do some testing tomorrow, with maybe the Zebs plunger removed from the equation. And then 1 Sainsmart removed as well, and see what happens. I will also post some new logs tomorrow too.

Edited by wrd1972, 23 September 2018 - 02:25 AM.

[mjr]

Oh should have mentioned.  I have been testing with the expirimental  code from the 9th. Saw no improvement.

 

Okay, good to rule that out, at least.

 

 

I will do some testing tomorrow, with maybe the Zebs plunger removed from the equation. And then 1 Sainsmart removed as well, and see what happens. I will also post some new logs tomorrow too.

 

Great, let me know what happens.  If it starts working properly when you're down to a single Sainsmart device in the picture, I'm thinking that would point to some kind of timing problem in the device driver; maybe the multiple connections that DOF is trying to make all at once are getting in each other's way.  I could try adding some delays to see if it helps to make the connections go one at a time.

[wrd1972]

Well I just got fed-up and re-imaged the drive, and forgot to do the next troubleshooting steps that I had planned.  Hoping that a fresh OS will resolve these weird issues. I might know tonight.

I also have a cloned drive of the previous disk, so I can still perform the troubleshooting that we spoke to. I might have some news tomorrow.

 

"maybe the multiple connections that DOF is trying to make all at once are getting in each other's way."

I'm no genius on this stuff, but that's kind of what it feels like to me. Almost like three controllers are trying to initialize at the same time, but they are butting heads instead. Maybe if there were a slight delay, between initializations, that could help.

[mjr]

Hoping that a fresh OS will resolve these weird issues. 

 

I guess it's worth a shot now that you've started the process.   "Reinstall Windows" is never high on my troubleshooting checklist given what a pain it is, but in this case it might be justified given the evidence that the device driver might be at fault.

 

 

"maybe the multiple connections that DOF is trying to make all at once are getting in each other's way."

I'm no genius on this stuff, but that's kind of what it feels like to me. Almost like three controllers are trying to initialize at the same time, but they are butting heads instead. Maybe if there were a slight delay, between initializations, that could help.

 

Let's give that a try.  Here's a test version that will retry the initial device connection a few times after a random short pause if the first attempt fails.

 

http://mjrnet.org/pi...jr-20180925.msi

 

http://mjrnet.org/pi...jr-20180925.zip

[wrd1972]

MJR,

Many thanks for trying to help me out here MJR. 

 

Okay, I did a clean OS install to see if the issue remains. Yup...still doing it.    Saw no  difference at all.  Roll of the dice if the 3 worked on first start. Everything works on the second start. Tried the test version just now. Still no improvement.

 

 

So I tried pulling USB cables to see what happens. So here are the current assignments:

• SainSmart 1 (Zebs Plunger)
• SainSmart 8-relay board (left)
• SainSmart 8-relay board (right)

With the two 8-relay boards disconnected, and with the Zebs Sainsmart ONLY connected. The Zebs Sainsmart operates properly on first table start like it should.

With the Zebs Sainsmart  disconnected, and the two Sainsmart 8-relay CONNECTED. They seem to work on first table start. BUT also, the board assignments get jacked up (cause the plunger is disconnected).

 

 

Lets talk about this:

 

 It seems to me that the assignments can change, if some of the Sainsmarts are disconnected. Are these auto configged based on what controllers are hooked up. IIRC on DOF2, the assignments were "locked" in based on the cabinet.xml. Just throwing some things out to see if anything rings a bell. Maybe I can remove 3++ and try 2, but I may need help re-configuring it.

 

Totally willing to try all test versions thrown my way.

[mjr]

 Tried the test version just now. Still no improvement.

 

Could you check out the log on that and make sure it's reporting the timed retries?  We should make sure that's actually happening.

[wrd1972]

 

 Tried the test version just now. Still no improvement.

 

Could you check out the log on that and make sure it's reporting the timed retries?  We should make sure that's actually happening.

 

Should I just post that log here? Im not sure what to really look for.

[wrd1972]

Posted over on Randr's site:

I have the same issue.  I’m using Zebs ez install basic kit which is recognized as 2 sainsmart boards.  A lot of times I have to exit the table and when I restart the table DOF all works.  I did not have this problem in DOF R2 and only wanted to update to R3++ because of doflinx updates for fx3. I’ve tried the auto config and using my own cabinet.xml, still no luck with it working every time. When it fails, DOF can’t connect to the sainsmart boards but everything else looks good.

[mjr]

Should I just post that log here? Im not sure what to really look for.

 

Look for lines like this:

 

FTDI open for device at index 1 failed with status FT_DEVICE_NOT_OPENED; retrying in 123ms

 

You can pluck out the whole section around those and post it here if you want.  If you don't see any of those, either the retries aren't working or the update didn't take - you can check for that via the very top part to see if the build date is 9-25-2018.

[wrd1972]

So it appears that the new test version is loaded. But I dont see any reference to the "FTDI open for device at index 1 failed with status FT_DEVICE_NOT_OPENED; retrying in 123ms"

 

The following log is from a failed 1st start:

---------------------------------------------------------------------------------
DirectOutput Version 3.1.6842.20297, built 2018.09.25 11:16
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2018.09.26 02:43:21.915    DirectOutput Logger initialized
2018.09.26 02:43:21.859    Pre-loading DLL Ciloci.Flee.dll from C:\DIRECTOUTPUT\Ciloci.Flee.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Extensions.dll from C:\DIRECTOUTPUT\Extensions.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL FTD2XX32.dll from C:\DIRECTOUTPUT\FTD2XX32.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Newtonsoft.Json.dll from C:\DIRECTOUTPUT\Newtonsoft.Json.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL PacDrive32.dll from C:\DIRECTOUTPUT\PacDrive32.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Q42.HueApi.ColorConverters.dll from C:\DIRECTOUTPUT\Q42.HueApi.ColorConverters.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Q42.HueApi.dll from C:\DIRECTOUTPUT\Q42.HueApi.dll : FAILED
2018.09.26 02:43:21.883    Global config filename is "C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml"
2018.09.26 02:43:21.915    Global config loaded from: C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml
2018.09.26 02:43:21.915    Loading Pinball parts
2018.09.26 02:43:21.915    Loading cabinet
2018.09.26 02:43:21.915    No cabinet config file loaded. Will use AutoConfig.
2018.09.26 02:43:21.915    Cabinet auto configuration started
2018.09.26 02:43:22.008    PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2018.09.26 02:43:22.868    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[0], name=FT245RBitbangController 0, description: ZB Plunger Output, serial #ZBPLUNGE01
2018.09.26 02:43:22.868    Detected and added FT245RBitbangController Id 0 with name FT245RBitbangController 0
2018.09.26 02:43:22.868    Added LedwizEquivalent Nr. 40 with name FT245RBitbangController 0 Equivalent 1 for PacUIO with Id 0
2018.09.26 02:43:22.868    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[1], name=FT245RBitbangController 1, description: FT245R USB FIFO, serial #AL00CV9I
2018.09.26 02:43:22.868    Detected and added FT245RBitbangController Id 1 with name FT245RBitbangController 1
2018.09.26 02:43:22.868    Added LedwizEquivalent Nr. 41 with name FT245RBitbangController 1 Equivalent 1 for PacUIO with Id 1
2018.09.26 02:43:22.868    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[2], name=FT245RBitbangController 2, description: FT245R USB FIFO, serial #AI05363W
2018.09.26 02:43:22.868    Detected and added FT245RBitbangController Id 2 with name FT245RBitbangController 2
2018.09.26 02:43:22.868    Added LedwizEquivalent Nr. 42 with name FT245RBitbangController 2 Equivalent 1 for PacUIO with Id 2
2018.09.26 02:43:22.868    Cabinet auto configuration finished
2018.09.26 02:43:22.868    Cabinet loaded
2018.09.26 02:43:22.868    Loading table config
2018.09.26 02:43:22.868    Warning: No table config file found. Will try to load config from LedControl file(s).
2018.09.26 02:43:22.868    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName Abracadabra
2018.09.26 02:43:22.868    Loading LedControl file C:\DirectOutput\Config\directoutputconfig40.ini
2018.09.26 02:43:22.868    Min DOF Version is 0.8 for file directoutputconfig40.ini
2018.09.26 02:43:23.024    Loading LedControl file C:\DirectOutput\Config\directoutputconfig41.ini
2018.09.26 02:43:23.040    Min DOF Version is 0.8 for file directoutputconfig41.ini
2018.09.26 02:43:23.227    Loading LedControl file C:\DirectOutput\Config\directoutputconfig42.ini
2018.09.26 02:43:23.227    Min DOF Version is 0.8 for file directoutputconfig42.ini
2018.09.26 02:43:23.446    3 directoutputconfig.ini or ledcontrol.ini files loaded.
2018.09.26 02:43:23.446    Config for RomName Abracadabra exists in LedControl data. Updating cabinet and config.
2018.09.26 02:43:23.477    Table config loading finished: romname=Abracadabra, tablename=Abra Ca Dabra (Gottlieb 1975)
2018.09.26 02:43:23.477    Pinball parts loaded
2018.09.26 02:43:23.477    Starting processes
2018.09.26 02:43:23.477    Initializing cabinet
2018.09.26 02:43:23.477    Debug: Initializing output controllers
2018.09.26 02:43:23.477    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been initialized and the updater thread has been started.
2018.09.26 02:43:23.477    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been initialized and the updater thread has been started.
2018.09.26 02:43:23.477    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been initialized and the updater thread has been started.
2018.09.26 02:43:23.477    Debug: Output controllers initialized
2018.09.26 02:43:23.493    Cabinet initialized
2018.09.26 02:43:23.493    Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2018.09.26 02:43:23.508    Connection to FTDI chip ZBPLUNGE01 established.
2018.09.26 02:43:23.586    Framework initialized.
2018.09.26 02:43:23.586    Have fun!
2018.09.26 02:43:23.649    EXCEPTION: Could not open the connection to FTDI chip with serial number AI05363W.
2018.09.26 02:43:23.649    EXCEPTION: Thread: FT245RBitbangController AI05363W named FT245RBitbangController 2 updater thread
2018.09.26 02:43:23.649    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.09.26 02:43:23.649    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.26 02:43:23.649    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.26 02:43:23.649    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.26 02:43:23.649    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.26 02:43:23.649    Warning: No connection to FTDI chip AI05363W. Updater thread will terminate.
2018.09.26 02:43:23.789    EXCEPTION: Could not open the connection to FTDI chip with serial number AL00CV9I.
2018.09.26 02:43:23.789    EXCEPTION: Thread: FT245RBitbangController AL00CV9I named FT245RBitbangController 1 updater thread
2018.09.26 02:43:23.789    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not found.
2018.09.26 02:43:23.789    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.26 02:43:23.789    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.26 02:43:23.789    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.26 02:43:23.789    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.26 02:43:23.790    Warning: No connection to FTDI chip AL00CV9I. Updater thread will terminate.
2018.09.26 02:43:37.373    Finishing framework
2018.09.26 02:43:37.373    Finishing cabinet
2018.09.26 02:43:37.377    Debug: Finishing output controllers
2018.09.26 02:43:37.493    Connection to FTDI chip ZBPLUNGE01 closed.
2018.09.26 02:43:37.493    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been finished and the updater thread has been terminated.
2018.09.26 02:43:37.493    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been finished and the updater thread has been terminated.
2018.09.26 02:43:37.493    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been finished and the updater thread has been terminated.
2018.09.26 02:43:37.493    Debug: Output controllers finished
2018.09.26 02:43:37.493    Cabinet finished
2018.09.26 02:43:37.493    DirectOutput framework finished.
2018.09.26 02:43:37.493    Bye and thanks for using!
 

 

From a successful 2nd launch:

---------------------------------------------------------------------------------
DirectOutput Version 3.1.6842.20297, built 2018.09.25 11:16
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2018.09.26 02:43:21.915    DirectOutput Logger initialized
2018.09.26 02:43:21.859    Pre-loading DLL Ciloci.Flee.dll from C:\DIRECTOUTPUT\Ciloci.Flee.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Extensions.dll from C:\DIRECTOUTPUT\Extensions.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL FTD2XX32.dll from C:\DIRECTOUTPUT\FTD2XX32.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Newtonsoft.Json.dll from C:\DIRECTOUTPUT\Newtonsoft.Json.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL PacDrive32.dll from C:\DIRECTOUTPUT\PacDrive32.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Q42.HueApi.ColorConverters.dll from C:\DIRECTOUTPUT\Q42.HueApi.ColorConverters.dll : FAILED
2018.09.26 02:43:21.862    Pre-loading DLL Q42.HueApi.dll from C:\DIRECTOUTPUT\Q42.HueApi.dll : FAILED
2018.09.26 02:43:21.883    Global config filename is "C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml"
2018.09.26 02:43:21.915    Global config loaded from: C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml
2018.09.26 02:43:21.915    Loading Pinball parts
2018.09.26 02:43:21.915    Loading cabinet
2018.09.26 02:43:21.915    No cabinet config file loaded. Will use AutoConfig.
2018.09.26 02:43:21.915    Cabinet auto configuration started
2018.09.26 02:43:22.008    PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2018.09.26 02:43:22.868    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[0], name=FT245RBitbangController 0, description: ZB Plunger Output, serial #ZBPLUNGE01
2018.09.26 02:43:22.868    Detected and added FT245RBitbangController Id 0 with name FT245RBitbangController 0
2018.09.26 02:43:22.868    Added LedwizEquivalent Nr. 40 with name FT245RBitbangController 0 Equivalent 1 for PacUIO with Id 0
2018.09.26 02:43:22.868    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[1], name=FT245RBitbangController 1, description: FT245R USB FIFO, serial #AL00CV9I
2018.09.26 02:43:22.868    Detected and added FT245RBitbangController Id 1 with name FT245RBitbangController 1
2018.09.26 02:43:22.868    Added LedwizEquivalent Nr. 41 with name FT245RBitbangController 1 Equivalent 1 for PacUIO with Id 1
2018.09.26 02:43:22.868    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[2], name=FT245RBitbangController 2, description: FT245R USB FIFO, serial #AI05363W
2018.09.26 02:43:22.868    Detected and added FT245RBitbangController Id 2 with name FT245RBitbangController 2
2018.09.26 02:43:22.868    Added LedwizEquivalent Nr. 42 with name FT245RBitbangController 2 Equivalent 1 for PacUIO with Id 2
2018.09.26 02:43:22.868    Cabinet auto configuration finished
2018.09.26 02:43:22.868    Cabinet loaded
2018.09.26 02:43:22.868    Loading table config
2018.09.26 02:43:22.868    Warning: No table config file found. Will try to load config from LedControl file(s).
2018.09.26 02:43:22.868    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName Abracadabra
2018.09.26 02:43:22.868    Loading LedControl file C:\DirectOutput\Config\directoutputconfig40.ini
2018.09.26 02:43:22.868    Min DOF Version is 0.8 for file directoutputconfig40.ini
2018.09.26 02:43:23.024    Loading LedControl file C:\DirectOutput\Config\directoutputconfig41.ini
2018.09.26 02:43:23.040    Min DOF Version is 0.8 for file directoutputconfig41.ini
2018.09.26 02:43:23.227    Loading LedControl file C:\DirectOutput\Config\directoutputconfig42.ini
2018.09.26 02:43:23.227    Min DOF Version is 0.8 for file directoutputconfig42.ini
2018.09.26 02:43:23.446    3 directoutputconfig.ini or ledcontrol.ini files loaded.
2018.09.26 02:43:23.446    Config for RomName Abracadabra exists in LedControl data. Updating cabinet and config.
2018.09.26 02:43:23.477    Table config loading finished: romname=Abracadabra, tablename=Abra Ca Dabra (Gottlieb 1975)
2018.09.26 02:43:23.477    Pinball parts loaded
2018.09.26 02:43:23.477    Starting processes
2018.09.26 02:43:23.477    Initializing cabinet
2018.09.26 02:43:23.477    Debug: Initializing output controllers
2018.09.26 02:43:23.477    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been initialized and the updater thread has been started.
2018.09.26 02:43:23.477    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been initialized and the updater thread has been started.
2018.09.26 02:43:23.477    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been initialized and the updater thread has been started.
2018.09.26 02:43:23.477    Debug: Output controllers initialized
2018.09.26 02:43:23.493    Cabinet initialized
2018.09.26 02:43:23.493    Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2018.09.26 02:43:23.508    Connection to FTDI chip ZBPLUNGE01 established.
2018.09.26 02:43:23.586    Framework initialized.
2018.09.26 02:43:23.586    Have fun!
2018.09.26 02:43:23.649    EXCEPTION: Could not open the connection to FTDI chip with serial number AI05363W.
2018.09.26 02:43:23.649    EXCEPTION: Thread: FT245RBitbangController AI05363W named FT245RBitbangController 2 updater thread
2018.09.26 02:43:23.649    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.09.26 02:43:23.649    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.26 02:43:23.649    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.26 02:43:23.649    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.26 02:43:23.649    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.26 02:43:23.649    Warning: No connection to FTDI chip AI05363W. Updater thread will terminate.
2018.09.26 02:43:23.789    EXCEPTION: Could not open the connection to FTDI chip with serial number AL00CV9I.
2018.09.26 02:43:23.789    EXCEPTION: Thread: FT245RBitbangController AL00CV9I named FT245RBitbangController 1 updater thread
2018.09.26 02:43:23.789    EXCEPTION: Message: FT_EXCEPTION --> FTDI device not found.
2018.09.26 02:43:23.789    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.09.26 02:43:23.789    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.09.26 02:43:23.789    EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.09.26 02:43:23.789    EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.09.26 02:43:23.790    Warning: No connection to FTDI chip AL00CV9I. Updater thread will terminate.
2018.09.26 02:43:37.373    Finishing framework
2018.09.26 02:43:37.373    Finishing cabinet
2018.09.26 02:43:37.377    Debug: Finishing output controllers
2018.09.26 02:43:37.493    Connection to FTDI chip ZBPLUNGE01 closed.
2018.09.26 02:43:37.493    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been finished and the updater thread has been terminated.
2018.09.26 02:43:37.493    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been finished and the updater thread has been terminated.
2018.09.26 02:43:37.493    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been finished and the updater thread has been terminated.
2018.09.26 02:43:37.493    Debug: Output controllers finished
2018.09.26 02:43:37.493    Cabinet finished
2018.09.26 02:43:37.493    DirectOutput framework finished.
2018.09.26 02:43:37.493    Bye and thanks for using!
2018.09.26 02:51:31.218    Pre-loading DLL Ciloci.Flee.dll from C:\DIRECTOUTPUT\Ciloci.Flee.dll : FAILED
2018.09.26 02:51:31.218    Pre-loading DLL Extensions.dll from C:\DIRECTOUTPUT\Extensions.dll : FAILED
2018.09.26 02:51:31.218    Pre-loading DLL FTD2XX32.dll from C:\DIRECTOUTPUT\FTD2XX32.dll : FAILED
2018.09.26 02:51:31.218    Pre-loading DLL Newtonsoft.Json.dll from C:\DIRECTOUTPUT\Newtonsoft.Json.dll : FAILED
2018.09.26 02:51:31.218    Pre-loading DLL PacDrive32.dll from C:\DIRECTOUTPUT\PacDrive32.dll : FAILED
2018.09.26 02:51:31.218    Pre-loading DLL Q42.HueApi.ColorConverters.dll from C:\DIRECTOUTPUT\Q42.HueApi.ColorConverters.dll : FAILED
2018.09.26 02:51:31.218    Pre-loading DLL Q42.HueApi.dll from C:\DIRECTOUTPUT\Q42.HueApi.dll : FAILED
2018.09.26 02:51:31.220    Global config filename is "C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml"
2018.09.26 02:51:31.228    Global config loaded from: C:\DIRECTOUTPUT\GlobalConfig_B2SServer.xml
2018.09.26 02:51:31.228    Loading Pinball parts
2018.09.26 02:51:31.228    Loading cabinet
2018.09.26 02:51:31.229    No cabinet config file loaded. Will use AutoConfig.
2018.09.26 02:51:31.229    Cabinet auto configuration started
2018.09.26 02:51:31.234    PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2018.09.26 02:51:32.068    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[0], name=FT245RBitbangController 0, description: ZB Plunger Output, serial #ZBPLUNGE01
2018.09.26 02:51:32.068    Detected and added FT245RBitbangController Id 0 with name FT245RBitbangController 0
2018.09.26 02:51:32.068    Added LedwizEquivalent Nr. 40 with name FT245RBitbangController 0 Equivalent 1 for PacUIO with Id 0
2018.09.26 02:51:32.068    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[1], name=FT245RBitbangController 1, description: FT245R USB FIFO, serial #AL00CV9I
2018.09.26 02:51:32.068    Detected and added FT245RBitbangController Id 1 with name FT245RBitbangController 1
2018.09.26 02:51:32.068    Added LedwizEquivalent Nr. 41 with name FT245RBitbangController 1 Equivalent 1 for PacUIO with Id 1
2018.09.26 02:51:32.068    FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[2], name=FT245RBitbangController 2, description: FT245R USB FIFO, serial #AI05363W
2018.09.26 02:51:32.068    Detected and added FT245RBitbangController Id 2 with name FT245RBitbangController 2
2018.09.26 02:51:32.068    Added LedwizEquivalent Nr. 42 with name FT245RBitbangController 2 Equivalent 1 for PacUIO with Id 2
2018.09.26 02:51:32.068    Cabinet auto configuration finished
2018.09.26 02:51:32.068    Cabinet loaded
2018.09.26 02:51:32.068    Loading table config
2018.09.26 02:51:32.068    Warning: No table config file found. Will try to load config from LedControl file(s).
2018.09.26 02:51:32.068    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName Abracadabra
2018.09.26 02:51:32.068    Loading LedControl file C:\DirectOutput\Config\directoutputconfig40.ini
2018.09.26 02:51:32.068    Min DOF Version is 0.8 for file directoutputconfig40.ini
2018.09.26 02:51:32.200    Loading LedControl file C:\DirectOutput\Config\directoutputconfig41.ini
2018.09.26 02:51:32.200    Min DOF Version is 0.8 for file directoutputconfig41.ini
2018.09.26 02:51:32.385    Loading LedControl file C:\DirectOutput\Config\directoutputconfig42.ini
2018.09.26 02:51:32.400    Min DOF Version is 0.8 for file directoutputconfig42.ini
2018.09.26 02:51:32.617    3 directoutputconfig.ini or ledcontrol.ini files loaded.
2018.09.26 02:51:32.617    Config for RomName Abracadabra exists in LedControl data. Updating cabinet and config.
2018.09.26 02:51:32.617    Table config loading finished: romname=Abracadabra, tablename=Abra Ca Dabra (Gottlieb 1975)
2018.09.26 02:51:32.617    Pinball parts loaded
2018.09.26 02:51:32.617    Starting processes
2018.09.26 02:51:32.617    Initializing cabinet
2018.09.26 02:51:32.617    Debug: Initializing output controllers
2018.09.26 02:51:32.617    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been initialized and the updater thread has been started.
2018.09.26 02:51:32.617    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been initialized and the updater thread has been started.
2018.09.26 02:51:32.617    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been initialized and the updater thread has been started.
2018.09.26 02:51:32.617    Debug: Output controllers initialized
2018.09.26 02:51:32.617    Cabinet initialized
2018.09.26 02:51:32.617    Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2018.09.26 02:51:32.632    Connection to FTDI chip ZBPLUNGE01 established.
2018.09.26 02:51:32.632    Connection to FTDI chip AL00CV9I established.
2018.09.26 02:51:32.632    Framework initialized.
2018.09.26 02:51:32.632    Have fun!
2018.09.26 02:51:32.654    Connection to FTDI chip AI05363W established.
2018.09.26 02:51:39.512    Finishing framework
2018.09.26 02:51:39.512    Finishing cabinet
2018.09.26 02:51:39.512    Debug: Finishing output controllers
2018.09.26 02:51:39.638    Connection to FTDI chip ZBPLUNGE01 closed.
2018.09.26 02:51:39.638    FT245RBitbangController FT245RBitbangController 0 with serial number ZBPLUNGE01 has been finished and the updater thread has been terminated.
2018.09.26 02:51:39.778    Connection to FTDI chip AL00CV9I closed.
2018.09.26 02:51:39.778    FT245RBitbangController FT245RBitbangController 1 with serial number AL00CV9I has been finished and the updater thread has been terminated.
2018.09.26 02:51:39.898    Connection to FTDI chip AI05363W closed.
2018.09.26 02:51:39.898    FT245RBitbangController FT245RBitbangController 2 with serial number AI05363W has been finished and the updater thread has been terminated.
2018.09.26 02:51:39.898    Debug: Output controllers finished
2018.09.26 02:51:39.898    Cabinet finished
2018.09.26 02:51:39.898    DirectOutput framework finished.
2018.09.26 02:51:39.898    Bye and thanks for using!
 

Edited by wrd1972, 26 September 2018 - 09:52 AM.

[wrd1972]

Just wanted to restate one important detail.

 

Maybe 20% of the time, all three Sainsmarts will operate properly on the first table start, just like they should. This was also the case with the previous 3++ as well. But the other 80% of first starts, is a grab bag of none of them working...or maybe 1 or two. I keep thinking that the fix for this is close, since sometimes things work like they should.

[mjr]

So it appears that the new test version is loaded. But I dont see any reference to the "FTDI open for device at index 1 failed with status FT_DEVICE_NOT_OPENED; retrying in 123ms"

 

Yep, that's why we trust but verify; I usually get them wrong on the first try.  I see why... I only added the retries to the type of open that it's *not* doing in your situation.  Here's a revised version that should really do the retries:

 

http://mjrnet.org/pi...jr-20180926.msi

http://mjrnet.org/pi...jr-20180926.zip

 

If those work for you, please also give this additional update a try next.  This has some additional provisional cleanup that probably won't affect your underlying problem one way or the other, but there's an off chance that it might, and in any case some of the resource management is slightly improved.

 

http://mjrnet.org/pi...r-20180926a.msi

http://mjrnet.org/pi...r-20180926a.zip

[wrd1972]

Okay I am seeing some positive results.

 

Results for r....926 - Successful 1st start 9 out of ten times. All controller worked.

Results for r....926a - Successful 1st start 9 out of ten times. All controller worked.

 

Possible to tweak it a bit more to hopefully get a 100% success rate?

[mjr]

Okay I am seeing some positive results.

 

Results for r....926 - Successful 1st start 9 out of ten times. All controller worked.

Results for r....926a - Successful 1st start 9 out of ten times. All controller worked.

 

Possible to tweak it a bit more to hopefully get a 100% success rate?

 

All right, that's good progress.  I wish I knew what was causing the failures under the covers, but this does make it sound like we're onto something with the idea that the device driver can't handle too many accesses at the same time.

 

Here are three new versions for you to try:

 

 

"b" - this one backs out the retries and instead just makes sure that the "open" calls into the driver are one-at-a-time.  The whole problem might just be a simple threading issue in the FTDI driver.  If this one works, it would be a much better solution than the random retries because it should be 100% reliable.  The retry approach is always going to be probabilistic.  We can keep increasing the timeout, which should make the probability asymptotically closer to 100%, by it'll never actually get there with the retry approach.  On the other hand, if single-threading it works, this should be perfectly reliable, and as a side benefit won't require any artificial delays.

 

http://mjrnet.org/pi...r-20180926b.msi

http://mjrnet.org/pi...r-20180926b.zip

 

 

"c" - this one keeps the single-threading but adds back in the retries and extends the maximum delay time by about 3x.  If "b" doesn't work for you, this one should (as above) get you asymptotically closer to "reliable".  Hopefully this will get it up to 99/100 rather than just 9/10.

 

http://mjrnet.org/pi...r-20180926c.msi

http://mjrnet.org/pi...r-20180926c.zip

 

 

 

"d" - going back to the "b" approach but adding a little extra lock-out time between the single-threaded calls.  In case something has to "settle" in the driver internally between calls or something weird like that.  Seems like a long shot, but it *does* seem to be sensitive to timing, so who knows.

 

http://mjrnet.org/pi...r-20180926d.msi

http://mjrnet.org/pi...r-20180926d.zip

 

 

If "b" works, that will be the best option because it's clean and makes sense.  "d" is the next best option.  "c" is the last resort; it's ugly, it can never be perfect, and the underlying cause of the problem remains unclear.  If "c" gets the probability of success higher than "a" did, but not high enough to be satisfactory, what I can do is expose a new global setting for FTDI retries, so that you can increase the retry timing until it works on your machine.  This probably won't be a one-size-fits-all timing parameter; the "a" version was already pretty generous, so you might have to go to really huge delay times to get close to 100%.   There might be some hardware dependency involved, so some people might need higher delay times than others, in which case user-adjustable times would be best so that everyone doesn't have to be subjected to long delays that a few machines need.

Edited by mjr, 27 September 2018 - 04:01 AM.

[wrd1972]

MJR,

More success!

 

Option B gave me 20 out of 20 successful first starts. All controllers worked as expected. Everything DOF related seems to be working fine. Clearly, this is an improvement and I cant thank you enough. I will continue to test and play and if the issue resurfaces, I will promptly let you know.

[mjr]

MJR,

More success!

 

Option B gave me 20 out of 20 successful first starts. All controllers worked as expected. Everything DOF related seems to be working fine. Clearly, this is an improvement and I cant thank you enough. I will continue to test and play and if the issue resurfaces, I will promptly let you know.

 

Hooray!  That's good news - "B" didn't even do the retries, so this must be a simple matter of the FTDI DLL/driver being un-thread-safe.

 

I just posted a final test version for you if you want to give that a try.  This is basically the "B" version with a bunch of code clean-up.  I should let you test it to make sure I didn't break anything cleaning it up - assuming it works for you as well as "B" does, I'll post that as the new general release.

Here's the new testing version:

 

http://mjrnet.org/pi...jr-20180927.msi

http://mjrnet.org/pi...jr-20180927.zip

[wrd1972]

Just loaded it. Many thanks again. I will continue to test it out.

[delt31]

just curious - what does this version of DOF do better than the DOF R2?  I have that one working well - is it worth upgrading?

[mjr]

just curious - what does this version of DOF do better than the DOF R2?  I have that one working well - is it worth upgrading?

 

You're on a really old version (probably, what, 5 years old?), so the changes are too numerous to list, but most of them are bug fixes and support for new devices.  If you don't have any devices that your version doesn't support, and you're not having any trouble with any bugs, you probably wouldn't notice any changes by updating.

[Cameron]

OK so in the DOF confit tool, There is a section for shaker and gear intensity. Is there a way to change the intensity for a gear motor?

My gear motor is too smooth at 100% lol but if I put it to 1/2 way full with PWM in the Pinscape output tool, it sounds more gear motor-ish.