32 replies to this topic

[tma73]

Running the Pinscape setup prog.

 

Under settings:

-ZB Launch Ball setup is enable.

-Output port # is 32

-Key button: Enter

-push distance: default (.063")

 

Not sure what to put in 'Button Inputs'  (trying to follow directions..)

 

-Under 'Feedback device outputs:

-Port #32 is Virtual, location is none and Port 'box' is empty.  At the end has the round red ZB ball logo.

 

 

-Ran the direct output prog. and gave me these 2 files:

-tablemappings (xml)

-directoutputconfig.ini

 

not sure or where to put these or what to do next :/

 

any help appreciated,

 

t

[mjr]

1.  Do you have Direct Output Framework installed?  Those DOF config files you mentioned go in the same directory where you've installed DOF.  If you haven't installed DOF, go through the setup procedure in the DOF documentation.  

 

1b.  You'll probably want to install my modified DOF DLLs instead of the original ones, since the original version has some compatibility problems when keyboard input is activated on the Pinscape device.  There's a link in the Pinscape config tool main page under the Miscellaneous section.

 

2. In the DOF config tool, make sure you have port 32 on your Pinscape device set to "ZB Launch Ball."  If you didn't do that already, set it, and be sure to re-generate the config files and download and install the new copies.

 

3. The ZB launch feature only works when you're running a table that has a pushbutton launcher, so make sure you're running a suitable table, such as Medieval Madness.

Edited by mjr, 11 October 2016 - 06:55 PM.

[tma73]

1.  Do you have Direct Output Framework installed?  Those DOF config files you mentioned go in the same directory where you've installed DOF.  If you haven't installed DOF, go through the setup procedure in the DOF documentation.  

 

1b.  You'll probably want to install my modified DOF DLLs instead of the original ones, since the original version has some compatibility problems when keyboard input is activated on the Pinscape device.  There's a link in the Pinscape config tool main page under the Miscellaneous section.

 

2. In the DOF config tool, make sure you have port 32 on your Pinscape device set to "ZB Launch Ball."  If you didn't do that already, set it, and be sure to re-generate the config files and download and install the new copies.

 

3. The ZB launch feature only works when you're running a table that has a pushbutton launcher, so make sure you're running a suitable table, such as Medieval Madness.

 

 

-1 yes, I have the latest DOF rev. and placed it:   C:\DOF

I believe I did try leaving the config files, but I'll recheck

 

-1b thank you

 

-2  k, I'll see if I can post back a few scrnshots of the Pinscape config tool and DOF...

 

-3 yup , hehe .  if I can ever get it to work

 

thanks for the info/reply

 

t

[FAB2TB]

Hi @tmr73 and @mjr, any update on this topic? because I did many many try to make the ZB button activated by the mecanical plunger following the installation procedure and pinscape configuration steps but can't make it work after so many hours.

Tried with Medieval Madness et Attack from Mars. I did everything as explain but my only doubt is about the DOF config .ini where into I can't manage to see what is written exactly once I have selected the PORT32 as ZB launch in the DOF tool and generate the file...

 

Here is my LOG file if you have an idea I would really appreciate:

 

This is the mjr modified DOF version R3+ 2016-10-19
2017.05.30 15:07:35.641    DirectOutput Logger initialized
2017.05.30 15:07:35.641    DirectOutput Version 0.9.6136.25325 as of 2016.10.19 14:04
2017.05.30 15:07:35.641    Global config loaded from: C:\Visual Pinball\Tables\GlobalConfig_B2SServer.xml
2017.05.30 15:07:35.641    Loading Pinball parts
2017.05.30 15:07:35.641    Loading cabinet
2017.05.30 15:07:35.642    No cabinet config file loaded. Will use AutoConfig.
2017.05.30 15:07:35.642    Cabinet auto configuration started
2017.05.30 15:07:35.698    Debug: Disposing LedWiz instance -01.
2017.05.30 15:07:35.700    Detected and added LedWiz Nr. 1 with name LedWiz 01
2017.05.30 15:07:35.701    Added LedwizEquivalent Nr. 1 with name LedWiz 01 Equivalent for Ledwiz Nr. 1
2017.05.30 15:07:35.795    Detected and added Pinscape Controller Nr. 1 with name Pinscape Controller 01
2017.05.30 15:07:35.796    Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 32
2017.05.30 15:07:35.796    Cabinet auto configuration finished
2017.05.30 15:07:35.796    Cabinet loaded
2017.05.30 15:07:35.796    Loading table config
2017.05.30 15:07:35.797    Warning: No table config file found. Will try to load config from LedControl file(s).
2017.05.30 15:07:35.797    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName afm_113b
2017.05.30 15:07:35.801    Loading LedControl file C:\Visual Pinball\Tables\directoutputconfig.ini
2017.05.30 15:07:35.806    Min DOF Version is 0.8 for file directoutputconfig.ini
2017.05.30 15:07:35.930    1 directoutputconfig.ini or ledcontrol.ini files loaded.
2017.05.30 15:07:35.932    Config for RomName afm_113b exists in LedControl data. Updating cabinet and config.
2017.05.30 15:07:35.966    Table config loading finished
2017.05.30 15:07:35.966    Pinball parts loaded
2017.05.30 15:07:35.967    Starting processes
2017.05.30 15:07:35.967    Initializing cabinet
2017.05.30 15:07:35.967    Debug: Initializing output controllers
2017.05.30 15:07:35.968    Debug: Initializing LedWiz Nr. 01
2017.05.30 15:07:35.969    LedWiz Nr. 01 initialized and updater thread initialized.
2017.05.30 15:07:35.970    Updater thread for LedWiz 01 started.
2017.05.30 15:07:35.971    Pinscape Pinscape Controller 01 intialized and updater thread started.
2017.05.30 15:07:35.971    Debug: Output controllers initialized
2017.05.30 15:07:35.972    Pinscape Pinscape Controller 01 updater thread  started.
2017.05.30 15:07:35.972    Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2017.05.30 15:07:35.975    Cabinet initialized
2017.05.30 15:07:35.979    Loading shape definition file: C:\Visual Pinball\Tables\DirectOutputShapes.xml
2017.05.30 15:07:36.039    Framework initialized.
2017.05.30 15:07:36.039    Have fun!
2017.05.30 15:45:51.380    Finishing framework
2017.05.30 15:45:51.383    Finishing cabinet
2017.05.30 15:45:51.384    Debug: Finishing output controllers
2017.05.30 15:45:51.384    Debug: Finishing LedWiz Nr. 01
2017.05.30 15:45:51.384    Updater thread for LedWiz 01 terminated.
2017.05.30 15:45:51.388    LedWiz Nr. 01 finished and updater thread stopped.
2017.05.30 15:45:51.390    Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2017.05.30 15:45:51.391    Pinscape Pinscape Controller 01 finished and updater thread stopped.
2017.05.30 15:45:51.391    Debug: Output controllers finished
2017.05.30 15:45:51.391    Cabinet finished
2017.05.30 15:45:51.391    DirectOutput framework finished.
2017.05.30 15:45:51.391    Bye and thanks for using!
2017.05.30 15:45:56.621    Debug: Disposing LedWiz instance 01.
 

[kiwiBri]

Hi, 

I just implemented the ZB launch on my pinscape a few days ago. I assigned mine to port 65 for testing in the Pinscape Config Utility then in DOF set it up there. When I tested in AFM and T2 it worked great. In Leathal Weapon, it didn't. (DOF possibly not configured for ZB Launch for that table) 

 

btw - Did you try different ports?

[FAB2TB]

Hi, thx for trying to help me, yes I ve tried on PORT 24 or something like that...it was the first virtual port of the pinscape but no results :/

If it not configured for that table do you know how to check if it is configured or not in the DOF .ini file?

[mjr]

Hi, thx for trying to help me, yes I ve tried on PORT 24 or something like that...it was the first virtual port of the pinscape but no results :/

If it not configured for that table do you know how to check if it is configured or not in the DOF .ini file?

 

First, open the Pinscape config tool in one window.  Go to the Settings page, scroll down to the Output Ports section.  Find the port with the ZB Launch Ball icon.

 

Open the DOF config tool in another window.  Find the ZB Launch Ball port.

 

** Make sure the port numbers are the same in both window. ** This is the critical step to making it work.  The port numbers have to match in the two tools.  If they don't, change the port assignment in the DOF window to match what's in the Pinscape window.  In the DOF window, click Save, then click Generate.  That will download a new ZIP file with new .ini files.  Unzip the .ini files into your DOF folder.

[FAB2TB]

Thx for your prompt reply mjr, I already did that and just repeated the operation and still dont work. Port is set to 32 on the pinscape tool (red ZB button logo) and I selected "ZB launch ball" in the port 32 menu of the DOF tool. then save, then unzip in my DOF file.

 

AFM table is launching, in the key menu of the VP I adjusted the Plunger to button N°5 which is the same in the pinscale tool. But nothing happen when I push or pull the plunger. Ball only launch when I push enter on the keyboard or my N°5 button.

 

Note that this pot plunger is working perfectly on the other tables which are not ZB type.

[mjr]

What do you have set for the button in the ZB Launch Ball section in the Pinscape config tool?  Maybe if you could post your full Settings page screen shot showing the keyboard, output port, and ZB Launch Ball sections, I might be able to spot the problem.

[FAB2TB]

thx mjr here it is:

 

https://ibb.co/kFiSca
https://ibb.co/cbCLxa
https://ibb.co/geLJiF
https://ibb.co/jPsW3F
https://ibb.co/jRBPOF
https://ibb.co/mj7Lxa

[mjr]

I think I see the problem.  In the ZB Launch Ball section, you have it set so that the plunger sends the "5" key.  I think you probably want to change it to send the Enter key instead, unless you have an unusual VP configuration where the plunger key is the "5" key in VP.  The "Key/Button" setting in the ZB Launch section isn't the "button number" from the list, it's the actual keyboard key that the plunger sends.  So by setting that to "5", you're telling Pinscape to press the "5" key on your keyboard.

 

So: go back to the Settings page.  Click in the Key/Button box.  Click the ENTER key on the keyboard map.  Program the KL25Z with the new settings.  Hopefully it'll work now!

[FAB2TB]

it should send the adress of the N°5 button of the joystick instead of 5 of the keyboard ! ...I already tried with the enter instead and just did it again...same sh#t

did you had a look at the DirectOutput LOG file in my first post? maybe you can find something wrong in it?

[mjr]

Oh, I see, that was meant to be the #5 joystick button?  The background doesn't show up in the printout so I thought it was the "5" key.  

 

Do you have any lighted buttons?  Like a lighted Start button?  If so, **as a test only**, try changing the DOF config so that the ZB Launch Ball output port is connected to one of those button lights.  The idea is to see if DOF is turning on your ZB port at the right times by observing the visible button state.  

 

For example, if your start button is on port 3, go to the DOF config tool and set port 3 to ZB Launch Ball, and change port 32 to nothing/empty.  Regenerate and reinstall the .ini files.  Run a NORMAL PLUNGER table to verify that the button light DOESN'T turn on.  Then run a BALL LAUNCHER table to verify that the button light DOES turn on.  

 

This should help determine whether or not the DOF signal is getting through correctly, by making the DOF signal directly visible via the light.  That should tell us whether we need to figure why the DOF signal isn't working, or why the button isn't working.

[FAB2TB]

unfortunatly I only plan to use the DOF for the launch ball function and all my buttons are not wired to any outputs

but when I push or pull my plunger nothing happen in the OUTPUTS diagnosis screen of the pinscape software while a table is running but don't know if this tool is a "live" diagnosis tool either...

[mjr]

Okay, there's still a way to test it, then.  You can assign the KL25Z's on-board LEDs as outputs.  That will give you the same type of visual feedback to test DOF as what I was proposing above, but without having to connect anything external.

 

Leave your DOF configuration as it is, with port 32 set to ZB Launch Ball.  

 

Go to the Pinscape config tool Settings page.  Go to the Outputs section.  Click in the output box for port 32.  Click GPIO Digital Out on the right side, then click PTB18 on the left side.  Accept the warning (click "Yes").

 

This will assign Port 32 to control the red on-board LED on the KL25Z.  

 

To make the test results easier to interpret, also do the following:

 

Click on the output box for port 31.  Click GPIO Digital Out on the right, then click PTB19 on the left.  Accept the warning.  Click on the port 30 output box.  Click GPIO Digital Out on the right, then click PTD1 on the left.  Accept the warning.

 

Program the KL25Z.

 

The normal diagnostic flashes on the KL25Z will no longer occur - the LED will be completely dark now.  This is nothing to worry about; it's normal given the new settings.  It's because you've taken over the LED for use as three output ports, red=port 32, green=port 31, blue=port 30.   We'll undo it later so that you get your normal diagnostic flashes back, after we're done with the test.

 

Now do that same VP test I described above.  Run a PLUNGER table.  The KL25Z LED should remain dark.  Run a LAUNCHER table.  The KL25Z red LED should turn on.

 

If that's not what happens, the problem is in the DOF setup.  Leave the KL25Z LED ports set like they are for now so that we can proceed to debug your DOF config.

 

If the LED display shows up as expected, your DOF setup is fine, so you can undo the test LED setup.

 

Once we get your DOF config debugged, you can undo the LED output ports by going back to the Setting page in the config tool.  For each of output ports 30, 31, and 32, click on the output port box, click the Virtual Out button on the right, and click the Virtual button in the middle.  That will disconnect the ports from the diagnostic LEDs, allowing the diagnostic flashes to return to normal.

[FAB2TB]

ok I did it:

 

blue led is always on (but PTB1 is written as J2-12 not Blue LED)

red led lights up when I push the start button of a ZB launch table after inserted the expected  nb of coins (tried 5 tables and it works)

green led never light but standard mechanical plunger still work correctly

[mjr]

ok I did it:

 

blue led is always on (but PTB1 is written as J2-12 not Blue LED)

red led lights up when I push the start button of a ZB launch table after inserted the expected  nb of coins (tried 5 tables and it works)

green led never light but standard mechanical plunger still work correctly

 

The blue led is PTD1 (not PTB1), but that's just a detail, as what we're really after is the red LED state here (I just wanted to turn the others off so you could see the red LED in isolation).  But it sounds like the red LED is turning on when it should.  Just to clarify, it comes on and stays on as long as a ball is ready to launch, right?

 

If the DOF signal is getting through, and manually pushing the same button (joystick button #5) correctly launches the ball in VP, and the ZB Launch Ball settings in the Pinscape config tool are all correct (they look like it from your screen shot), then it should be working.  I can't think of anything else that needs to be set up.  We've checked each piece in isolation now and they all seem to be working, so I think I'm just about out of ideas.

 

The only thing left that I can think of is plunger calibration.  Go to the main Pinscape config tool window.  Click the Plunger icon.  When you're not touching the plunger, is the green bar lined up with the purple triangles labeled "Park"?  And does the number by the green bar roughly match the number on the Park arrows?  If not, run the calibration procedure (click the Calibrate button).  Calibration is important for ZB Launch because the software detects the launch gestures by comparing the current reading to the calibrated resting position.

Edited by mjr, 30 May 2017 - 08:49 PM.

[FAB2TB]

Yes my mistake that's right, yes the  red LED goes off once the ball has been launched with button #5. Please check the calibration of the plunger here if you want:

 

https://ibb.co/d6hdHa

 

Do you mean if the red light diagnosis procedure passed it means the DOF .ini file generated is also correct? because I can't find the parameters of the port 32 & the ZB Launch ball into that DOF .ini file....do you kow how to verify if this file is correctly generated and the tables parameters in it also?

How is the DirectOutput Log I have posted according to you, is there any advice in that log which could help?

 

Thanks a lot for your time anyway

[mjr]

Yes my mistake that's right, yes the  red LED goes off once the ball has been launched with button #5. Please check the calibration of the plunger here if you want:

 

https://ibb.co/d6hdHa

 

Your physical placement of the potentiometer might be the problem.  Looking at your calibration, your park (resting) position is almost all the way forward.  The ZB Launch Ball "push" feature works by detecting when the plunger moves forward by about 1/6", which translates to roughly 25 units on your setup if I'm figuring it correctly.  It's impossible for it to do that because the furthest forward it can go is 14 units.

 

So you might try opening up the machine and moving the potentiometer slightly further forward.  You want to position the potentiometer so that the plunger NEVER hits EITHER END of the travel limits for the pot.  The pot should always be moving freely even when you push the plunger all the way forward (pressing against the barrel spring as hard as you can) or when you pull it all the way back.

 

 

Do you mean if the red light diagnosis procedure passed it means the DOF .ini file generated is also correct? because I can't find the parameters of the port 32 & the ZB Launch ball into that DOF .ini file....do you kow how to verify if this file is correctly generated and the tables parameters in it also?

How is the DirectOutput Log I have posted according to you, is there any advice in that log which could help?

 

The log file only tells us that DOF is loading, not what it's doing, and it's a huge pain to inspect the DOF .ini files.  Testing with an LED is a much more reliable way to tell.

[kiwiBri]

 

Yes my mistake that's right, yes the  red LED goes off once the ball has been launched with button #5. Please check the calibration of the plunger here if you want:

 

https://ibb.co/d6hdHa

 

Your physical placement of the potentiometer might be the problem.  Looking at your calibration, your park (resting) position is almost all the way forward.  The ZB Launch Ball "push" feature works by detecting when the plunger moves forward by about 1/6", which translates to roughly 25 units on your setup if I'm figuring it correctly.  It's impossible for it to do that because the furthest forward it can go is 14 units.

 

So you might try opening up the machine and moving the potentiometer slightly further forward.  You want to position the potentiometer so that the plunger NEVER hits EITHER END of the travel limits for the pot.  The pot should always be moving freely even when you push the plunger all the way forward (pressing against the barrel spring as hard as you can) or when you pull it all the way back.

 

 

 

 

I think this will be the cause of the issue.  Been following this discussion and with my recent testing of the plunger and setting up ZB launch, this seems the likely cause