975 replies to this topic

[Drybonz]

Well, it's a big arcade trackball (Centipede, Golden Tee, etc) instead of the mouse style trackballs.  There's no software for any of the X-Arcade components.  There aren't any mouse buttons.  It connects via USB, but has its own controller inside the casing... so I may have to open it up to check for loose wires.

 

As far as why it only happens when the KL25 is plugged in, I would guess because I never used to nudge the controller before that, and just never realized it, possibly.  I will have to open it up again and look around.

 

This is the controller... 2 Ultrastik joysticks, Turbo Twist spinner, original X-Arcade trackball, flipper buttons on the side and Pinscape inside... just so you can see what I am working with.

 

The nudging is working great, by the way, if I disable the Trackball in the Windows control panel.  I was practicing with it today and getting the hang of saving the ball, etc... the hardware and Pinscape software are great once I got everything set up.  I'm really having fun with it.

Edited by Drybonz, 12 June 2016 - 11:25 PM.

[sasa12345]

Unfortunately it does not work, future pinbal ok without ledWiz, VP or will not work, pinballx works without ledviz PLYGINS.

 

I made all of the items on the laptop and brought in pincab?

pin CAB does IE 11

Both flippers are doing better now when plays harder

Where a mistake?

greeting

[Santos76]

Hi mjr ,
there is already a version DofR3 the fail- works with the keyboard input.I use so your directoutput.dll but so unfortunately does not work the Teensy controller .

Regards Sascha

[sasa12345]

When you add a letter from the keyboard / error ..

in this letter do not have any function, but I need to FP TILT

[Avi]

Hi. There are some digram Transistors for lk25z . with all its components . to run with pinballX and pinball fx 2 .

[Santos76]

Hi. There are some digram Transistors for lk25z . with all its components . to run with pinballX and pinball fx 2 .

Yes, look here.
https://developer.mb...r/wiki/Homepage

[mjr]

there is already a version DofR3 the fail- works with the keyboard input.I use so your directoutput.dll but so unfortunately does not work the Teensy controller .

 

Could you be more specific?  

 

- What software are you running on the Teensy?

 

- What do you expect it should be doing?

 

- What exactly is going wrong?

Unfortunately it does not work, future pinbal ok without ledWiz, VP or will not work, pinballx works without ledviz PLYGINS.

 

I made all of the items on the laptop and brought in pincab?

pin CAB does IE 11

Both flippers are doing better now when plays harder

Where a mistake?

 

Sorry, I don't understand what you're trying to do or what's not working.  

When you add a letter from the keyboard / error ..

in this letter do not have any function, but I need to FP TILT

 

What's the error?  Details would help: exact error message, the program it's coming from, etc.

 

"FP TILT" means you're trying to assign a "tilt" key for Future Pinball - is that correct?

[Santos76]

[quote name="mjr" post="347313" timestamp="1465924943"][quote name="Santos76" post="347278" timestamp="1465901421"]
there is already a version DofR3 the fail- works with the keyboard input.I use so your directoutput.dll but so unfortunately does not work the Teensy controller .
[/quote]
 
Could you be more specific?  
 
- What software are you running on the Teensy?
 
- What do you expect it should be doing?
 


Hello mjr,
it run's the software from Swisslizard. https://github.com/D...roller/releases

The adresseable led's make this:
[url="http://vpuniverse.co...board-poll[/url]
See post 17.

If I use DirectOutput_R3Beta2_Build_5818.37242 and keystrokes turning down work the Teensy controller.
And if i use your directoutput.dll, the keystrokes are fine but the teensy controller does not work.

Sascha

Edited by Santos76, 14 June 2016 - 06:18 PM.

[mjr]

The adresseable led's make this:
http://vpuniverse.co...ller-board-poll
See post 17.

If I use DirectOutput_R3Beta2_Build_5818.37242 and keystrokes turning down work the Teensy controller.
And if i use your directoutput.dll, the keystrokes are fine but the teensy controller does not work.

 

Okay, I understand now.  

 

I'm not sure why that wouldn't work.  As far as I know I'm building my patched version from the same sources swisslizard uses for the official 5818 build, but if it's not working with the other device, there's probably something newer in his sources that I don't have in my copy.  I've been trying to get in touch with him about integrating my latest patches, but I haven't heard anything back yet, so I'm guessing he's on vacation or otherwise unable to tend to DOF matters at the moment.

 

I don't think there's anything I can do to help until I can coordinate this with swisslizard.  Hopefully he'll be back before too long and we can get everything synced.

[Santos76]

Ok, then we must wait.

Regards Sascha

[sasa12345]

"FP TILT" means you're trying to assign a "tilt" key for Future Pinball - is that correct?

yes Mike

 

All works ok, but as soon as I assign a key (letter) Visual Pinball will not work  ver.991, vpinballx?

it does not matter that the letter and sign..

 

future pinbal runs properly

Regards

[mjr]

"FP TILT" means you're trying to assign a "tilt" key for Future Pinball - is that correct?

yes Mike 

 

All works ok, but as soon as I assign a key (letter) Visual Pinball will not work  ver.991, vpinballx?

it does not matter that the letter and sign..

 

Okay, got it.  

 

When you assign any keyboard keys (rather than the original joystick button mappings), the KL25Z adds a USB keyboard interface.  This created a couple of compatibility problems with the early versions of DOF R3 and the standard ledwiz.dll.  One of the symptoms is that VP can get stuck trying to run a table.

 

The fix is to get my latest patched version of DOF.  I just added a link to it in the config tool because a number of people have run into this - here's the file:

 

http://www.mjrnet.or...ch_20160613.zip

 

The only snag is that this is based on the sources for build 5818, and there's a newer official build (5845) that I don't have the sources for.  Santos76 (see a couple posts back) says that my build doesn't work with the Teensy LED strip controller, so there must be some important updates I don't have.  I've been trying to reach swisslizard for a couple of weeks to get everything in sync so that the official build has the fixes, but he hasn't responded yet, so he's probably on vacation or away on business or something.  Hopefully he'll be back soon and we can get synced up; in the meantime, give the patch a try and see if it helps.

Edited by mjr, 14 June 2016 - 08:35 PM.

[sasa12345]

Ok thanks a lot, the results call tomorrow ..

greetings

[jukedock]

Hi - I have a problem that I can not find a way round with the V2 software.
Having programmed the board (very easily with your fantastic instructions) - I decided to go for the pot version rather than the CCD device as I have plenty of the pots - and  I also like the way it works (I prefer the PinAna system over the VP plunger that uses the same board).
The only thing I am having an issue with is using the LAUNCH button with the plunger - I just can not get it to work.  Should it just send the 'ENTER KEY' via a keyboard matrix to my VP software?  or does this feature not work when using a pot?
Phil

[mjr]

The only thing I am having an issue with is using the LAUNCH button with the plunger - I just can not get it to work.  Should it just send the 'ENTER KEY' via a keyboard matrix to my VP software?  or does this feature not work when using a pot?

 

It should work with the pot - it's based on the plunger position read from the sensor, so the sensor type shouldn't matter.

 

Some troubleshooting steps:

 

- Make sure you have a working DOF setup.  The ZB Launch feature is activated by a DOF output port, so DOF has to be working.

 

- Make sure you have my DOF patch installed (http://www.mjrnet.or...ch_20160613.zip).

 

- On the Pinscape config tool settings page, make sure ZB Launch is enabled, and that it's connected to a valid DOF port.  The DOF port has to be one that exists in the output list, even if it's a Virtual port.

 

- In your DOF Config Tool settings, check that the right port for your Pinscape unit is set to "ZB Launch".  This has to match the port number you set in the Pinscape settings page.

 

- Make sure you're testing with a table that has ZB Launch configured in the DOF database.  If you go to that table in the DOF config tool, you should see something other than a blank line for the "ZB Launch" item.

 

- Check that the plunger is calibrated.  You should have run through the calibration procedure in the Pinscape config tool at some point.  If it's calibrated properly, the physical rest position of the plunger should correspond to exactly the halfway point on the Z axis when you look at it in the Windows "Set up USB game controllers" control panel.

 

If you're not sure if your DOF setup is working, here's a test you can do.  Go to the Pinscape config tool setting page and scroll down to the bottom, to the Output Port section.  For the port that you're using as your ZB Launch port, click on the row to bring up the physical output selector.  Click on the "GPIO Digital Out" button on the right, and then click on "PTB18" in the port list at the left.  This will show a warning that you're reassigning the on-board LED - click Yes to proceed anyway.  What this does is route the DOF ZB Launch signal to the red on-board LED.  That will let you see if the signal from DOF is successfully reaching the unit - if it is, the red LED will light up whenever the signal is on.  Click the "Program KL25Z" to save the settings, then you can fire up VP and run a suitable table.  You should see the normal blue/green flash on the diagnostic LED turn into a yellow/purple flash when the ball is ready to launch, because DOF should be sending the ZB Launch signal, which should turn on the red LED.  The red will combine with the green/blue to make yellow/purple if this is working.

[r00n]

thanks again for taking time and being so specific. 

I have ordered all the parts I need and even a few tools like the soldering station.  Im looking forward to starting the project. 

 

I really hope my light sensor part isn't DOA.

 

Your efforts are admirable.  Thank again.

[jukedock]

Thanks for taking the time to help me out....

One more thing - the pulse to turn a TV on - do you need an add on board to do that?

[mjr]

Thanks for taking the time to help me out....
One more thing - the pulse to turn a TV on - do you need an add on board to do that?

 

That's built in to the expansion boards (it's part of the main interface board), so if you're planning on using those, you're set.  If you're using the stand-alone KL25Z without the expansion boards, you do need a little external circuitry.  The schematic for that will be in the build guide, but if you need it before I get that out, let me know and I'll draw it up.  (Or if you're good at reading schematics, you can find it in the expansion board schematic.  It's all on a separate page so it's pretty easy to identify the relevant parts.)  It's simple enough to build on one of those little prototyping perf boards without too much trouble, but if there's interest, I could put together a small PCB design for just that function.

[sliderpoint]

 

 

 

If you're not sure if your DOF setup is working, here's a test you can do.  Go to the Pinscape config tool setting page and scroll down to the bottom, to the Output Port section.  For the port that you're using as your ZB Launch port, click on the row to bring up the physical output selector.  Click on the "GPIO Digital Out" button on the right, and then click on "PTB18" in the port list at the left.  This will show a warning that you're reassigning the on-board LED - click Yes to proceed anyway.  What this does is route the DOF ZB Launch signal to the red on-board LED.  That will let you see if the signal from DOF is successfully reaching the unit - if it is, the red LED will light up whenever the signal is on.  Click the "Program KL25Z" to save the settings, then you can fire up VP and run a suitable table.  You should see the normal blue/green flash on the diagnostic LED turn into a yellow/purple flash when the ball is ready to launch, because DOF should be sending the ZB Launch signal, which should turn on the red LED.  The red will combine with the green/blue to make yellow/purple if this is working.

 

 

I've finally come back around to this.  I still can't get the ZB Launch function to work.  This section here does not work for me.  No change in lights at all.   I'm thinking this is some problem with my DOF config setup.  For this line "- Make sure you're testing with a table that has ZB Launch configured in the DOF database.  If you go to that table in the DOF config tool, you should see something other than a blank line for the "ZB Launch" item."  I don't see any lines, not even blank ones.

 

Here is my DOF test output log for MM.  Does it highlight any issues?

---------------------------------------------------------------------------------
Hello from the special LedWiz-sans-dll version of DirectOutput (test 4)!!!
2016.06.17 12:08:46.013	DirectOutput Logger initialized
2016.06.17 12:08:46.013	DirectOutput Version 0.8.6008.23387 as of 2016.06.13 12:59
2016.06.17 12:08:46.013	Global config loaded from: C:\Visual Pinball\Tables\Plugins\DirectOutput\GlobalConfig_.xml
2016.06.17 12:08:46.014	Loading Pinball parts
2016.06.17 12:08:46.014	Loading cabinet
2016.06.17 12:08:46.015	Will load cabinet config file: C:\Visual Pinball\Tables\Plugins\DirectOutput\config\Cabinet.xml
2016.06.17 12:08:46.094	1 output controller defnitions and 1 toy definitions loaded from cabinet config.
2016.06.17 12:08:46.094	Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2016.06.17 12:08:46.094	Cabinet auto configuration started
2016.06.17 12:08:46.102	Debug: Disposing LedWiz instance -01.
2016.06.17 12:08:46.141	Detected and added Pinscape Controller Nr. 1 with name Pinscape Controller 01
2016.06.17 12:08:46.142	Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 25
2016.06.17 12:08:46.142	Cabinet auto configuration finished
2016.06.17 12:08:46.142	Autoconfig complete.
2016.06.17 12:08:46.142	Cabinet config loaded successfully from C:\Visual Pinball\Tables\Plugins\DirectOutput\config\Cabinet.xml
2016.06.17 12:08:46.142	Cabinet loaded
2016.06.17 12:08:46.142	Loading table config
2016.06.17 12:08:46.143	Warning: No table config file found. Will try to load config from LedControl file(s).
2016.06.17 12:08:46.143	Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName mm
2016.06.17 12:08:46.146	Loading LedControl file C:\Visual Pinball\Tables\Plugins\DirectOutput\directoutputconfig8.ini
2016.06.17 12:08:46.230	1 directoutputconfig.ini or ledcontrol.ini files loaded.
2016.06.17 12:08:46.231	Config for RomName mm exists in LedControl data. Updating cabinet and config.
2016.06.17 12:08:46.248	Table config loading finished
2016.06.17 12:08:46.248	Pinball parts loaded
2016.06.17 12:08:46.248	Starting processes
2016.06.17 12:08:46.248	Initializing cabinet
2016.06.17 12:08:46.249	Debug: Initializing output controllers
2016.06.17 12:08:46.249	Debug: Initializing LedWiz Nr. 01
2016.06.17 12:08:46.251	LedWiz Nr. 01 initialized and updater thread initialized.
2016.06.17 12:08:46.252	Updater thread for LedWiz 01 started.
2016.06.17 12:08:46.253	Pinscape Pinscape Controller 01 intialized and updater thread started.
2016.06.17 12:08:46.253	Debug: Output controllers initialized
2016.06.17 12:08:46.255	Cabinet initialized
2016.06.17 12:08:46.255	Pinscape Pinscape Controller 01 updater thread  started.
2016.06.17 12:08:46.255	Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2016.06.17 12:08:46.295	Framework initialized.
2016.06.17 12:08:46.295	Have fun! :)
2016.06.17 12:08:54.500	Finishing framework
2016.06.17 12:08:54.501	Finishing cabinet
2016.06.17 12:08:54.501	Debug: Finishing output controllers
2016.06.17 12:08:54.502	Debug: Finishing LedWiz Nr. 01
2016.06.17 12:08:54.502	Updater thread for LedWiz 01 terminated.
2016.06.17 12:08:54.505	LedWiz Nr. 01 finished and updater thread stopped.
2016.06.17 12:08:54.508	Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2016.06.17 12:08:54.508	Pinscape Pinscape Controller 01 finished and updater thread stopped.
2016.06.17 12:08:54.508	Debug: Output controllers finished
2016.06.17 12:08:54.508	Cabinet finished
2016.06.17 12:08:54.508	DirectOutput framework finished.
2016.06.17 12:08:54.508	Bye and thanks for using!
2016.06.17 12:08:54.508	Global config loaded from: C:\Visual Pinball\Tables\Plugins\DirectOutput\GlobalConfig_.xml
2016.06.17 12:08:54.508	Loading Pinball parts
2016.06.17 12:08:54.508	Loading cabinet
2016.06.17 12:08:54.508	Will load cabinet config file: C:\Visual Pinball\Tables\Plugins\DirectOutput\config\Cabinet.xml
2016.06.17 12:08:54.514	1 output controller defnitions and 1 toy definitions loaded from cabinet config.
2016.06.17 12:08:54.514	Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2016.06.17 12:08:54.514	Cabinet auto configuration started
2016.06.17 12:08:54.516	Debug: Disposing LedWiz instance -01.
2016.06.17 12:08:54.516	Detected and added Pinscape Controller Nr. 1 with name Pinscape Controller 01
2016.06.17 12:08:54.516	Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 25
2016.06.17 12:08:54.516	Cabinet auto configuration finished
2016.06.17 12:08:54.516	Autoconfig complete.
2016.06.17 12:08:54.516	Cabinet config loaded successfully from C:\Visual Pinball\Tables\Plugins\DirectOutput\config\Cabinet.xml
2016.06.17 12:08:54.516	Cabinet loaded
2016.06.17 12:08:54.516	Loading table config
2016.06.17 12:08:54.517	Warning: No table config file found. Will try to load config from LedControl file(s).
2016.06.17 12:08:54.517	Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName mm
2016.06.17 12:08:54.517	Loading LedControl file C:\Visual Pinball\Tables\Plugins\DirectOutput\directoutputconfig8.ini
2016.06.17 12:08:54.522	Debug: Disposing LedWiz instance 01.
2016.06.17 12:08:54.570	1 directoutputconfig.ini or ledcontrol.ini files loaded.
2016.06.17 12:08:54.570	Config for RomName mm exists in LedControl data. Updating cabinet and config.
2016.06.17 12:08:54.570	Table config loading finished
2016.06.17 12:08:54.570	Pinball parts loaded
2016.06.17 12:08:54.570	Starting processes
2016.06.17 12:08:54.570	Initializing cabinet
2016.06.17 12:08:54.570	Debug: Initializing output controllers
2016.06.17 12:08:54.570	Debug: Initializing LedWiz Nr. 01
2016.06.17 12:08:54.570	LedWiz Nr. 01 initialized and updater thread initialized.
2016.06.17 12:08:54.570	Updater thread for LedWiz 01 started.
2016.06.17 12:08:54.571	Pinscape Pinscape Controller 01 intialized and updater thread started.
2016.06.17 12:08:54.571	Debug: Output controllers initialized
2016.06.17 12:08:54.571	Pinscape Pinscape Controller 01 updater thread  started.
2016.06.17 12:08:54.571	Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2016.06.17 12:08:54.571	Cabinet initialized
2016.06.17 12:08:54.576	Framework initialized.
2016.06.17 12:08:54.576	Have fun! :)
2016.06.17 12:08:55.969	Finishing framework
2016.06.17 12:08:55.970	Finishing cabinet
2016.06.17 12:08:55.970	Debug: Finishing output controllers
2016.06.17 12:08:55.970	Debug: Finishing LedWiz Nr. 01
2016.06.17 12:08:55.970	Updater thread for LedWiz 01 terminated.
2016.06.17 12:08:55.972	LedWiz Nr. 01 finished and updater thread stopped.
2016.06.17 12:08:55.973	Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2016.06.17 12:08:55.974	Pinscape Pinscape Controller 01 finished and updater thread stopped.
2016.06.17 12:08:55.974	Debug: Output controllers finished
2016.06.17 12:08:55.974	Cabinet finished
2016.06.17 12:08:55.974	DirectOutput framework finished.
2016.06.17 12:08:55.974	Bye and thanks for using!
2016.06.17 12:08:55.986	Debug: Disposing LedWiz instance 01.

Thanks

-Mike

[mjr]

I've finally come back around to this.  I still can't get the ZB Launch function to work.  This section here does not work for me.  No change in lights at all.   I'm thinking this is some problem with my DOF config setup.  For this line "- Make sure you're testing with a table that has ZB Launch configured in the DOF database.  If you go to that table in the DOF config tool, you should see something other than a blank line for the "ZB Launch" item."  I don't see any lines, not even blank ones.

 

Here is my DOF test output log for MM.  Does it highlight any issues?

 

It looks like you've got my latest DOF DLL successfuly installed.

 

Let's make sure we have the DOF ZB Launch port connected to the Pinscape ZB Launch port:

 

1.  In the Pinscape config tool setup page, what does your "ZB Launch Ball" section look like?  This should be marked as enabled and should have a port number listed.

 

2.  Still on the config tool setup page, does your output port list (near the bottom of the page) include that port number and show it with the little red ZB Launch icon?

 

3.  On the DOF Config Tool "Port Assignments" page for Device FRDM-KL25Z 1, is that same port number set as "ZB Launch Ball"?

 

4.  On the DOF Config Tool "Table Config" page for Medieval Madness, what does the "ZB Launch Ball" box contain?

Edited by mjr, 17 June 2016 - 07:36 PM.