490 replies to this topic

[mjr]

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.

 

That doesn't seem to be an option currently, but I'd have to imagine it would be easy to add one analogous to the current global Shaker Motor and Fan intensity settings.  You should contact Arngrim about it, since he maintains that tool.  He usually hangs out on "the other site" - he usually responds quickly if you PM him there.

[arngrim]

I am there
Well, that part is not that easy, shaker intensity code i didn't change it from configtool 1.0, i used the same for the blower toy, it is not that dynamic, every table config needs to have an intensity for each gear assignment, and for each user, 2 new columns have to be added to the user table, with a default value min and max, changing the port assignment page, and controller logic, if we implement gear intensity.

If you can have a hardware intensity variator, like we have in our shakers, or take another gear motor, or putting your gear inside a box to make less noise?

Envoyé de mon SM-A320FL en utilisant Tapatalk

[mjr]

Well, that part is not that easy, shaker intensity code i didn't change it from configtool 1.0, ...

 

In that case... 

 

Cameron, you're using a Pinscape unit to control the gear motor, right?  In that case, you might be able to get the reduced power effect via the Pinscape config tool.  Try using the Flipper Logic settings for the port to set a lower hold power for the port - turn it down to about 50%, and set the initial time to the shortest setting.

 

Flipper Logic was really meant for coils, to save them from overheating, but it's just a generic PWM control so it'll work for anything.

[hawkeyez88]

Disregard - Got this worked out.

 

Is it okay to post for support on this thread? I have the V2_2 of zebs kit - followed the guide can get everything looking good - go to run a table in vpx and don't get any feedback. Here's the log.

 

---------------------------------------------------------------------------------

DirectOutput Version 3.1.6863.36690, built 2018.10.16 20:23

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

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

2018.10.31 21:25:29.636 DirectOutput Logger initialized

2018.10.31 21:25:29.602 Global config filename is "C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml"

2018.10.31 21:25:29.636 Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml

2018.10.31 21:25:29.636 Loading Pinball parts

2018.10.31 21:25:29.636 Loading cabinet

2018.10.31 21:25:29.637 No cabinet config file loaded. Will use AutoConfig.

2018.10.31 21:25:29.637 Cabinet auto configuration started

2018.10.31 21:25:29.681 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)

2018.10.31 21:25:29.731 Opening 32-bit LedWiz driver...

2018.10.31 21:25:29.733 Detected and added LedWiz Nr. 2 with name LedWiz 02

2018.10.31 21:25:29.733 Added LedwizEquivalent Nr. 2 with name LedWiz 02 Equivalent for Ledwiz Nr. 2

2018.10.31 21:25:29.733 Opening 32-bit LedWiz driver...

2018.10.31 21:25:29.733 Detected and added LedWiz Nr. 1 with name LedWiz 01

2018.10.31 21:25:29.733 Added LedwizEquivalent Nr. 1 with name LedWiz 01 Equivalent for Ledwiz Nr. 1

2018.10.31 21:25:29.736 Cabinet auto configuration finished

2018.10.31 21:25:29.736 Cabinet loaded

2018.10.31 21:25:29.736 Loading table config

2018.10.31 21:25:29.736 Warning: No table config file found. Will try to load config from LedControl file(s).

2018.10.31 21:25:29.736 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName dof_test

2018.10.31 21:25:29.739 Loading LedControl file C:\DIRECTOUTPUT\directoutputconfig40.ini

2018.10.31 21:25:29.741 Min DOF Version is 0.8 for file directoutputconfig40.ini

2018.10.31 21:25:29.847 Loading LedControl file C:\DIRECTOUTPUT\directoutputconfig41.ini

2018.10.31 21:25:29.847 Min DOF Version is 0.8 for file directoutputconfig41.ini

2018.10.31 21:25:29.926 2 directoutputconfig.ini or ledcontrol.ini files loaded.

2018.10.31 21:25:29.926 Config for RomName dof_test exists in LedControl data. Updating cabinet and config.

2018.10.31 21:25:29.926 Table config loading finished: romname=dof_test, tablename=dof_test_table_VPX

2018.10.31 21:25:29.926 Pinball parts loaded

2018.10.31 21:25:29.926 Starting processes

2018.10.31 21:25:29.926 Initializing cabinet

2018.10.31 21:25:29.926 Debug: Initializing output controllers

2018.10.31 21:25:29.926 Debug: Initializing LedWiz Nr. 02

2018.10.31 21:25:29.941 LedWiz Nr. 02 initialized and updater thread initialized.

2018.10.31 21:25:29.941 Debug: Initializing LedWiz Nr. 01

2018.10.31 21:25:29.941 LedWiz Nr. 01 initialized and updater thread initialized.

2018.10.31 21:25:29.941 Debug: Output controllers initialized

2018.10.31 21:25:29.941 Updater thread for LedWiz 02 started.

2018.10.31 21:25:29.941 Updater thread for LedWiz 01 started.

2018.10.31 21:25:29.941 Cabinet initialized

2018.10.31 21:25:29.941 Loading shape definition file: C:\DIRECTOUTPUT\DirectOutputShapes.xml

2018.10.31 21:25:29.972 Framework initialized.

2018.10.31 21:25:29.972 Have fun!

2018.10.31 21:25:41.372 Finishing framework

2018.10.31 21:25:41.372 Finishing cabinet

2018.10.31 21:25:41.372 Debug: Finishing output controllers

2018.10.31 21:25:41.372 Debug: Finishing LedWiz Nr. 02

2018.10.31 21:25:41.372 Updater thread for LedWiz 02 terminated.

2018.10.31 21:25:41.393 LedWiz Nr. 02 finished and updater thread stopped.

2018.10.31 21:25:41.393 Debug: Finishing LedWiz Nr. 01

2018.10.31 21:25:41.393 Updater thread for LedWiz 01 terminated.

2018.10.31 21:25:41.412 LedWiz Nr. 01 finished and updater thread stopped.

2018.10.31 21:25:41.412 Debug: Output controllers finished

2018.10.31 21:25:41.412 Cabinet finished

2018.10.31 21:25:41.412 DirectOutput framework finished.

2018.10.31 21:25:41.412 Bye and thanks for using!

2018.10.31 21:25:42.563 Debug: Disposing LedWiz instance 01.

2018.10.31 21:25:42.563 Debug: Disposing LedWiz instance 02.

Edited by hawkeyez88, 02 November 2018 - 12:22 AM.

[Cameron]

Flipper logic! OK that should work fine. I really need to find a more noisy, grindy gear motor. This one is too quiet hahaha

[bellatrixzen]

Hello folks, DDH suggested I post over here with an issue I'm having with DOF Grander Unified and an LED-Wiz.

I recently upgraded from older DOF and DofLinx to R3++ and DofLinx 6.5.

 

Before upgrade, I had one LED-Wiz controlling strips undercab & beacon, and a sainsmart board controlling contactors etc..

Everything worked great.

After update, Sainsmart is seen and runs as device 1 (instead of 2), but the LED-Wiz has vanished.

I can run the LED-Wiz no problem with LEDBlinky, and the pinball X plug-in also has no problems.

Only DOF (and DOFLinx) will not see it. I have went thru all the usual unblocking, etc to no success.

 

Original post is here: https://www.vpforums...showtopic=41233

 

Here is a copy of the DOF log, I'm at a loss, having tried everything I and DDH can think of.

Any help is appreciated!!!!

 

EDIT: I used the msi to install, and in case a look at my DOF directory would be helpful, here it is : https://drive.google...eUQt1OFoCRe-eL6

Also, While LEDBlinky works, the new LEDtester that comes with R3++ does not....

 

---------------------------------------------------------------------------------
DirectOutput Version 3.1.6843.36499, built 2018.09.26 20:16
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2018.11.13 19:28:28.566 DirectOutput Logger initialized
2018.11.13 19:28:28.535 Finishing framework
2018.11.13 19:28:28.535 Finishing cabinet
2018.11.13 19:28:28.535 Debug: Finishing output controllers
2018.11.13 19:28:28.535 Debug: Output controllers finished
2018.11.13 19:28:28.535 Cabinet finished
2018.11.13 19:28:28.535 DirectOutput framework finished.
2018.11.13 19:28:28.535 Bye and thanks for using!
2018.11.13 19:28:28.535 Global config filename is "c:\DirectOutput\config\GlobalConfig_b2sServer.xml"
2018.11.13 19:28:28.566 Global config loaded from: c:\DirectOutput\config\GlobalConfig_b2sServer.xml
2018.11.13 19:28:28.566 Loading Pinball parts
2018.11.13 19:28:28.566 Loading cabinet
2018.11.13 19:28:28.566 Will load cabinet config file: C:\DirectOutput\config\Cabinet.xml
2018.11.13 19:28:28.644 1 output controller defnitions and 1 toy definitions loaded from cabinet config.
2018.11.13 19:28:28.644 Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2018.11.13 19:28:28.644 Cabinet auto configuration started
2018.11.13 19:28:28.660 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2018.11.13 19:28:28.957 FT245RBitbangControllerAutoConfigurator.AutoConfig.. Detected FT245RBitbangController[0], name=FT245RBitbangController 0, description: FT245R USB FIFO, serial #A506L0OC
2018.11.13 19:28:28.957 Detected and added FT245RBitbangController Id 0 with name FT245RBitbangController 0
2018.11.13 19:28:28.957 Cabinet auto configuration finished
2018.11.13 19:28:28.957 Autoconfig complete.
2018.11.13 19:28:28.957 Cabinet config loaded successfully from C:\DirectOutput\config\Cabinet.xml
2018.11.13 19:28:28.957 Cabinet loaded
2018.11.13 19:28:28.957 Loading table config
2018.11.13 19:28:28.957 No TableFilename specified, will use empty tableconfig
2018.11.13 19:28:28.957 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName doflinx
2018.11.13 19:28:28.957 Loading LedControl file c:\DirectOutput\config\directoutputconfig.ini
2018.11.13 19:28:28.957 Min DOF Version is 0.8 for file directoutputconfig.ini
2018.11.13 19:28:29.066 Loading LedControl file c:\DirectOutput\config\directoutputconfig40.ini
2018.11.13 19:28:29.082 Min DOF Version is 0.8 for file directoutputconfig40.ini
2018.11.13 19:28:29.207 2 directoutputconfig.ini or ledcontrol.ini files loaded.
2018.11.13 19:28:29.207 Config for RomName doflinx exists in LedControl data. Updating cabinet and config.
2018.11.13 19:28:29.207 Table config loading finished: romname=doflinx, tablename=doflinx
2018.11.13 19:28:29.207 Pinball parts loaded
2018.11.13 19:28:29.207 Starting processes
2018.11.13 19:28:29.207 Initializing cabinet
2018.11.13 19:28:29.207 Debug: Initializing output controllers
2018.11.13 19:28:29.222 FT245RBitbangController Sainsmart 1 with serial number A506L0OC has been initialized and the updater thread has been started.
2018.11.13 19:28:29.222 FT245RBitbangController FT245RBitbangController 0 with serial number A506L0OC has been initialized and the updater thread has been started.
2018.11.13 19:28:29.222 Debug: Output controllers initialized
2018.11.13 19:28:29.222 Cabinet initialized
2018.11.13 19:28:29.222 Connection to FTDI chip A506L0OC established.
2018.11.13 19:28:29.222 FTDI open serial #A506L0OC attempt #1 failed with status FT_DEVICE_NOT_OPENED; retrying in 300ms
2018.11.13 19:28:29.222 Loading shape definition file: c:\DirectOutput\config\DirectOutputShapes.xml
2018.11.13 19:28:29.266 Framework initialized.
2018.11.13 19:28:29.266 Have fun!
2018.11.13 19:28:29.271 Initializing cabinet
2018.11.13 19:28:29.271 Debug: Initializing output controllers
2018.11.13 19:28:29.271 Debug: Output controllers initialized
2018.11.13 19:28:29.271 Cabinet initialized
2018.11.13 19:28:29.417 FT245RBitbangController  with serial number A506L0OC has been initialized and the updater thread has been started.
2018.11.13 19:28:29.417 FTDI open serial #A506L0OC attempt #1 failed with status FT_DEVICE_NOT_OPENED; retrying in 326ms
2018.11.13 19:28:29.531 EXCEPTION: Could not open the connection to FTDI chip with serial number A506L0OC.
2018.11.13 19:28:29.531 EXCEPTION: Thread: FT245RBitbangController A506L0OC named FT245RBitbangController 0 updater thread
2018.11.13 19:28:29.531 EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.11.13 19:28:29.541 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.11.13 19:28:29.541 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.11.13 19:28:29.541 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.11.13 19:28:29.542 EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.11.13 19:28:29.544 Warning: No connection to FTDI chip A506L0OC. Updater thread will terminate.
2018.11.13 19:28:29.568 ArtNet  finished and updater thread stopped.
2018.11.13 19:28:29.568 PinControl  finished and updater thread stopped.
2018.11.13 19:28:29.744 EXCEPTION: Could not open the connection to FTDI chip with serial number A506L0OC.
2018.11.13 19:28:29.744 EXCEPTION: Thread: FT245RBitbangController A506L0OC named  updater thread
2018.11.13 19:28:29.744 EXCEPTION: Message: FT_EXCEPTION --> FTDI device not opened.
2018.11.13 19:28:29.744 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
2018.11.13 19:28:29.744 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FTDI.ErrorHandler(FT_STATUS ftStatus)
2018.11.13 19:28:29.744 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Out.FTDIChip.FT245RBitbangController.Connect()
2018.11.13 19:28:29.744 EXCEPTION: Targetsite: Void ErrorHandler(FT_STATUS, FT_ERROR)
2018.11.13 19:28:29.744 Warning: No connection to FTDI chip A506L0OC. Updater thread will terminate.
2018.11.13 19:28:29.744 FT245RBitbangController  with serial number A506L0OC has been finished and the updater thread has been terminated.
2018.11.13 19:28:29.744 ArtNet  finished and updater thread stopped.
2018.11.13 19:28:29.744 PinControl  finished and updater thread stopped.
2018.11.13 19:28:29.744 Finishing cabinet
2018.11.13 19:28:29.744 Debug: Finishing output controllers
2018.11.13 19:28:29.744 Debug: Output controllers finished
2018.11.13 19:28:29.744 Cabinet finished
2018.11.13 19:28:31.260 Finishing framework
2018.11.13 19:28:31.260 Finishing cabinet
2018.11.13 19:28:31.260 Debug: Finishing output controllers
2018.11.13 19:28:31.385 Connection to FTDI chip A506L0OC closed.
2018.11.13 19:28:31.385 FT245RBitbangController Sainsmart 1 with serial number A506L0OC has been finished and the updater thread has been terminated.
2018.11.13 19:28:31.385 FT245RBitbangController FT245RBitbangController 0 with serial number A506L0OC has been finished and the updater thread has been terminated.
2018.11.13 19:28:31.385 Debug: Output controllers finished
2018.11.13 19:28:31.385 Cabinet finished
2018.11.13 19:28:31.385 DirectOutput framework finished.
2018.11.13 19:28:31.385 Bye and thanks for using!
 

Edited by bellatrixzen, 17 November 2018 - 08:44 PM.

[Outhere]

Rename your DirectOutput folder to something like - DirectOutputold

download the new DOF and install it -- The one from - (16 Oct 2018) Thanks mjr

https://www.vpforums...topic=39557&hl=

Inside the new DirectOutput folder you will find a config folder in there is in examples folder put that GlobalConfig_B2SServer.xml in your config folder...

No Cabinet.xml needed for sainsmart board with new DOF

I just did this on a cab last night and it worked perfectly running 1 ledwiz and 1 sainsmart board...

Best thing to do is get this running in visual pinball 1st then get it running in the other DOF

Edited by Outhere, 18 November 2018 - 02:18 AM.

[mjr]

bellatrixzen - it looks like you're not on the latest, so you might try that.  One of the most recent changes was to fix a problem with multiple Sainsmarts.  See the posts about one page back on this thread about that if you're curious, but it looks like that's what you're running into, and that should be fixed in the latest.

 

http://mjrnet.org/pi...ll-updates.html

[bellatrixzen]

Thanks to you both, I will give that a shot in the morning and see how it goes.

I appreciate it, and will report back.

[bellatrixzen]

OK, tried both suggestions. Neither worked. And now LEDWiz no longer functions in PinballX. Only way to even test it is with LEDBlinky.

 

Something in the new DOF just hates this LEDWiz it seems. Windows sees it, LEDBlinky sees it, just not DOF. And now PinballX.

Ugh.

 

I think at this moment I need to walk away from this for now. I'm going to have a house full of people later this week, and I'm afraid if I do anymore "updating" I am bound to lose all of my contactor/solenoid feedback as well.

 

Thanks for the help guys. I think I should have left well enough alone when everything was working so well.

I will revisit this issue here after the holiday when I don't have a bunch of people wanting to play with this cab, and just do a wipe and start all over.

 

Thanks again, damn is this a frustrating hobby at times.... 

[mjr]

And now LEDWiz no longer functions in PinballX.

 

Strange as it may seem, that might actually be a good sign.  Reason: PBX uses DOF.  If PBX was working with the LedWiz and DOF doesn't see it, that would be weird. It would suggest to me that you have some old cruft that's getting loaded by PBX, which would suggest that you have configuration problems.  But I guess you already knew that because nothing is working anyway.

 

Did you install the DOF update with the MSI, or manually with the ZIP?  If you used the ZIP, you might try starting over with the MSI.  Installing manually with the ZIP has ALWAYS been trouble-prone.  There are so many manual steps that some little detail inevitably gets missed.  The MSI has been more reliable.

[bellatrixzen]

So since I can't leave things alone, I found a backup of my PBX directory with my original ledwiz.dll in it. I started PBX in that directory and the LED-Wiz worked.
I then copied it to the normal PBX directory, and it continued to work.
I also copied it to the new DOF directory, and the NewLEDTester.exe started to magically work. It hasn't worked before now.

 

So if PBX uses DOF (PBX LED plugin is enabled), Can I assume DOF is seeing the LEDWiz even though it isn't mentioned in the DOF log?? I ask because Doflinx still does not see it. Maybe a reinstall of Doflinx at this point.

 

In any case, it seems as though the new DLL may be the cause...

 

I used the MSI installer today after renaming the DirectOutput folder. I did not delete DOF before running the MSI, just renamed old folder. All found instances of the new LEDWiz.dll have been replaced with the old version.

 

I am running the LED-Wiz+GP version of the hardware btw....

 

Again, sincere thanks for your time!!!!

Edited by bellatrixzen, 18 November 2018 - 10:08 PM.

[mjr]

So if PBX uses DOF (PBX LED plugin is enabled), Can I assume DOF is seeing the LEDWiz even though it isn't mentioned in the DOF log??

 

Nope, sorry.  That plugin is a different matter.  It goes directly to the LedWiz interface, so that's unrelated to DOF.  Trust the log.

 

In any case, it seems as though the new DLL may be the cause...

 

Sorry, which DLL is "the new DLL"? The new DOF DLLs, you mean?

Edited by mjr, 19 November 2018 - 07:16 PM.

[bellatrixzen]

ledwiz.dll

 

Or is that the original version I would have had forever that shows up in DirectOutput folder after install.

 

In any case, if the PinballX plugin does things on its own, then I guess I'm back to start.

Not a problem. It's working fine now, just no cool undercab lighting during play. I can deal with that for a lil bit.

 

This hobby cracks me up man. So much stuff running to run so much stuff... Kinect, lights, contactors, solenoids.....

 

Then I walk over and start a game of ST:Next Generation on a real machine.

 

 

And hope the machine doesnt break. Again.  

[mjr]

ledwiz.dll

 

Or is that the original version I would have had forever that shows up in DirectOutput folder after install.

 

Okay.

 

To help you avoid red herrings, here's what uses what:

 

VP:  DOF: yes, LedWiz.dll: no

PBX (the main part): DOF: yes, LedWiz.dll: no

PBX LED plugin: DOF: no, LedWiz.dll: yes

 

So if you want to get your LedWiz working with VP again, you just need to focus on DOF.  ledwiz.dll is not involved in any way with that.

[zebulon]

It's the integration of the dll into the build not seeing the LEDWiz+GP that's at issue. 

 

Something I noticed and forgot to mention when we were tinkering Mike was that LED Blinky with the original dll recognizes the LEDWiz portion of the GP but the build itself prior to the ZB updates that we were testing with wouldn't (i remember using the GP as it was the only authentic LEDWiz product that I had available in the office prior to contacting you).

 

The dll that you built does recognize the GP so it's likely something in the integration of the dll in the build.  I'm leaning toward the vid and pid being read not being the ones for the ledwiz portion (it uses the standard LEDWiz ones), but being the ones for the gamepad side of things.

 

I should've mentioned that at the time, apologies for the oversight.

[mjr]

It's the integration of the dll into the build not seeing the LEDWiz+GP that's at issue. 

 

Do you mean the integration of ledwiz.dll into the DOF build?  There actually is no integration of ledwiz.dll into DOF any more - DOF doesn't use the DLL at all.

 

Does the LedWiz+GP use a different VID/PID from a regular LedWiz?  That would explain why it's not being detected if so, as the scan is based on the VID/PID.  If someone knows the new VID/PID it's using I can add it to the DOF scan.

[bellatrixzen]

Thanks for the input Zeb!

 

If there is something I can look up on my end with the GP, by all means, tell me how.

 

I feel a bit better now, I thought I was going nuts...

 

Does this help? VID fafa PID 00f0

 

Screenie of VID/PID report:

 

https://drive.google...PgKR68vZUcCSavd

 

Edited by bellatrixzen, 20 November 2018 - 09:45 PM.

[mjr]

Thanks for the input Zeb!

 

If there is something I can look up on my end with the GP, by all means, tell me how.

 

I feel a bit better now, I thought I was going nuts...

 

Does this help? VID fafa PID 00f0

 

That's the normal ledwiz VID/PID.  Maybe they changed something in the USB HID descriptors - the scan also does some sanity checking to avoid false positives to unrelated devices.  Given that the +GP model must expose some kind of keyboard or joystick HID reports, the interface checks might be discarding it despite the matching VID/PID.

 

I'll put some instrumentation in for you to log the relevant data and see if we can figure out what needs to be added.

[mjr]

Okay, here's a new test build for you:

 

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

 

You should get some new info in the DOF log after running VP, with data on the FAFA/00F* device USB HID characteristics.  Hopefully your device will show up there and the extra logging will explain why it's being rejected.