975 replies to this topic

[sliderpoint]

 

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?

 

 

Pictures = 1000 words

 

 

 

 

-Mike

For completeness:

 

 

[mjr]

It looks like everything should be set.  The one suspicious thing I see is that you have the key mapping set to "L" - when ZB Launch fires, it will press the "L" key on the keyboard.  Are you sure that's what you want?  Usually you'd want the Enter key there.

 

You also posted a snapshot of your list of button assignments, so let me point out in case it's not clear that the button assignments aren't used for the ZB feature.  The only thing that matters is the button in the ZB Launch section itself - in your case, the "L" key.  I think I've created some confusion with all of the different pointers in the ZB section - I was trying to reduce the potential for confusion by just putting the key assignment right there rather than going through the separate button list.  

 

So just to be clear, button #24 isn't involved in this in any way in your setup.  It's output 24, not button 24, that's important.

One other thing - does the red LED ever light up?  You won't be able to see red separately since the red light will combine with the green/blue flashing that's always happening, but it should change the green/blue to yellow/purple.

Edited by mjr, 17 June 2016 - 08:31 PM.

[sliderpoint]

Yes, "L" is what I want.  It works for PFX2 and I have setup preferences in FP and VP for L to be the launch key.  

 

There are zero light changes when I launch a table and start a game or push in the plunger a bit. Just default flash blue/green.

 

-Mike

[mjr]

Okay, I don't see any problems, then.  The red light (if it were working, which apparently it isn't) isn't affected by the plunger.  It's only affected by the DOF signal.  So it should turn on when you have MM loaded in VP and a ball is ready to launch at the plunger, because DOF should be turning port 24 on when all of those conditions are met.

 

The next troubleshooting step is to see if you can get any signal to the board.  Download my DOF tester program:

 

http://mjrnet.org/pi...e/doftest3.html

 

Install it and run it like this:

 

DirectOutputTest 8 

 

This will show a command line like this:

 

>

 

Type 24 255 <Enter>.  That should turn on port 24.  The red LED should light up.  If it does, the DOF signal is getting through.  If not, that's the problem.

 

If the red LED turns on, leave the DirectOutputTest program running, with the red LED still on, and open a Notepad window.  Press the plunger in.  This should press the "L" key, so you should see "L"'s repeating in the Notepad window as long as you hold the plunger in.

 

Give that a try and see what happens.  That will let us isolate this from VP to see if the problem is in the KL25Z or somewhere in the VP-B2S-DOF software setup.

 

**********************************

 

EDIT! Hang on - I see the problem!  I was looking in the wrong place.

 

Looks like you have your KL25Z set to impersonate LedWiz #1.  That's fine, but your DOF config is set for LedWiz #8.  You just need to change your DOF config to match. 

 

You can test this out without any DOF changes by renaming directoutputconfig8.ini to directoutputconfig1.ini.  Make sure you close all VP windows before testing again.

 

I assume you want to keep the LedWiz emulation on unit #1 for the sake of FP.  If so, you can fix this in your DOF config by going to the My Account page and changing the device assignments to:

 

Number of LedWiz units:  1

Number of KL25Z units:  0

 

You'll need to go to the Port Assignments page and re-do the port layout for LedWiz #1 after doing that, unfortunately - I don't think there's a way to carry the assignments over to a different unit.  Print out your DOF KL25Z port assignment page first so you can refer to it when setting up the LedWiz #1 page.

 

Alternative:  if you don't actually care which LedWiz unit # is used, you can just switch it back to LedWiz Unit #8 on the Pinscape Config Tool set up page, at the very top in the "USB ID" section.  That will let you keep all of the DOF config settings the way you currently have them.

Edited by mjr, 17 June 2016 - 10:13 PM.

[sliderpoint]

ding ding ding, we have a winner!  Changed settings to LedWiz#8 and it's working.   I don't really know where in the DOF config I would set that to 1.  But it works on 8 (which is where it was originally obviously).

 

Thanks

-Mike

[mjr]

ding ding ding, we have a winner!  Changed settings to LedWiz#8 and it's working. 

 

That's great news!

 

 

I don't really know where in the DOF config I would set that to 1.  But it works on 8 (which is where it was originally obviously).

 

Just for reference, in case you change your mind at some point, and for anyone else who might want to do that:  The trick  is to tell the DOF Config Tool that it's an LedWiz rather than a KL25Z.  On your "My Account" page, there's a list of all of the devices you have.

 

To tell DOF the unit number is 8:

Number of LedWiz units:  0

Number of KL25Z units: 1    <--- the config tool starts number KL25Z LedWiz emulators at #8

 

To tell DOF the unit number is 1:

Number of LedWiz units: 1   <--- DOF numbers real LedWiz'es starting at #1

Number of KL25Z units: 0

Edited by mjr, 17 June 2016 - 11:06 PM.

[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?

 

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.

 

I just pretty well need to know what pin out from the main board triggers it.  I have found the diagram on the schematic but could really just do with a simple schematic just to trigger the relay (none of the IR sensor required). 
OR - can the main board be supplied in the UK?  I will just populate the area I need....

[mjr]

I just pretty well need to know what pin out from the main board triggers it.  I have found the diagram on the schematic but could really just do with a simple schematic just to trigger the relay (none of the IR sensor required). 

OR - can the main board be supplied in the UK?  I will just populate the area I need....

 

The pins can be set in the Config Tool settings page, in the TV ON section.  It actually needs three pins - two for the power monitor, one for the relay output.  Those are labeled on the schematic as PSU2_STATUS_SENSE, PSU2_STATUS_SET, and TV_SWITCH.  To build it separately, you just need to build the two blocks shown on the schematic on page 4 labeled TV-ON RELAY and PSU2 POWER SENSING.

 

I'm only shipping boards within the US myself, but roar (on here) mentioned that he was able to ship one to someone else in Europe at reasonable cost - you might try PMing him to see if it's cheaper than ordering locally.  There's a company in Germany selling them for about EU10 each as well (http://www.platinenc...Controller.html), which might be cheaper compared to shipping across the pond.

[Santos76]

@Jukedock
It gives EU and US version of the Boards.
The difference is only the transistors .
For EU version you need BC337 and BC327 transitors.
For US version you need 2N4401 and 2N4403 Transistor.

You can also on the US version using the BC transistors.
On the boards is an imprint, if you then in the US uses transistors BC , you must turn the transistors 180 degrees. The same is inversely.

I have the EU Boards transistors with 2N because I ordered the shopping list from Mouser that mjr has linked to its homepage .

The information is used only for info , in order to know what is the difference.

Regards Sascha

[dexter]

First of all, thank you so much for all the hard work you are putting into this project, much appreciated!

I am very happy with the new version but I have one small question. Is it possible that the accelerometer is less sensitive in this version than in the previous?

No matter how hard I push the cabinet I can't even get close to get it to output the highest value. I am using X360CE to remap some inputs to an emulated 360-controller and the nudging was working perfect before but now it's not just because the pinscape controller outputs much weaker values, thus weaker nudges in the game.

[mjr]

First of all, thank you so much for all the hard work you are putting into this project, much appreciated!

I am very happy with the new version but I have one small question. Is it possible that the accelerometer is less sensitive in this version than in the previous?

No matter how hard I push the cabinet I can't even get close to get it to output the highest value. I am using X360CE to remap some inputs to an emulated 360-controller and the nudging was working perfect before but now it's not just because the pinscape controller outputs much weaker values, thus weaker nudges in the game.

 

Nothing about the accelerometer code changed in the v2 firmware, and of course the hardware hasn't changed.

 

Is it possible something has changed on your PC setup?

 

You might just need to adjust the sensitivity in VP.  VP uses the X and Y axis "gain" settings in the keyboard setup options dialog to control this.  You can try increasing the X and Y gain numbers to see if that helps.  Which version of VP are you using, and what are your current settings?  Typical settings that work well are:

 

VP 9.x  -> X/Y gain about 1000

VP 10   -> X/Y gain about 10

[dexter]

Nothing about the accelerometer code changed in the v2 firmware, and of course the hardware hasn't changed.

 

Is it possible something has changed on your PC setup?

 

You might just need to adjust the sensitivity in VP.  VP uses the X and Y axis "gain" settings in the keyboard setup options dialog to control this.  You can try increasing the X and Y gain numbers to see if that helps.  Which version of VP are you using, and what are your current settings?  Typical settings that work well are:

 

VP 9.x  -> X/Y gain about 1000

VP 10   -> X/Y gain about 10

 

 

I haven't updated anything except Pinscape so that is strange.

 

I'm playing Pinball FX2 on my cabinet so I don't have VP installed at the moment. I am using X360CE to assign the accelerometer to the right analog stick of the xbox-controller (which controls nudging in FX2). Before the update I had to lower the sensitivity in X360CE, but now I can't get the analog stick to move more like maybe 30% even with the strongest nudges where I before quite easily could do 100%.

 

If nothing has changed with that code I guess it has nothing to do with Pinscape but since it happened just after the update and that was the only thing I updated in my cab I thought that it was the update that caused it.

[mjr]

If nothing has changed with that code I guess it has nothing to do with Pinscape but since it happened just after the update and that was the only thing I updated in my cab I thought that it was the update that caused it.

 

It's always possible there's some unexpected side effect of something else I changed.  You could try going back to the v1 software and see if it returns to the old behavior.

 

You could also try looking directly at the joystick output in the Windows "Set up USB game controllers" control panel.  (DON'T ever run that control panel's calibration, of course.)  The accelerometer is also a gravity detector, so if you tip the KL25Z the way sideways in any direction (so that the plane of the board is perpendicular with the floor) you should see 1g on one axis, which corresponds to full-scale deflection of the joystick.  If you see full deflection with that test, the raw accelerometer data is scaled as expected, at least.

Edited by mjr, 22 June 2016 - 10:35 PM.

[Santos76]

Hi mjr,
it is possible to added Force Feedback for Pinball FX2.
Here is a Arduino project.
http://www.gamoover....p?topic=30663.0

Perhaps it is possible to implant the code in your software ?
A joystick emulates the Pinscape yet.

Sascha

[mjr]

it is possible to added Force Feedback for Pinball FX2.
Here is a Arduino project.
http://www.gamoover....p?topic=30663.0

Perhaps it is possible to implant the code in your software ?
A joystick emulates the Pinscape yet.

 

Interesting idea!  It would probably be possible.  I don't have an x360ce device myself, so it's not something I'm going to be able to look into in the near term, but maybe I can look at it in the future.  If someone wants to take a crack at it in the meantime and manages to get it working, I'd be more than happy to integrate their code into the main repository.

Edited by mjr, 24 June 2016 - 06:10 PM.

[Drybonz]

Hi... you may remember me as the guy from earlier in the thread that had an X-Arcade controller and a bunch of problems... lol

 

Just reporting in to say I finally got around to troubleshooting and fixed the problem with the unwanted mouse clicks when nudging.

 

In the extremely unlikely situation that someone with a similar setup needs to fix this problem, here's what to do:  Open the X-Arcade, open the trackball casing (be careful that you are holding it right side up when you take the lid off), there are 2 small boards inside... on the board that has more stuff connected to it, remove the plug that has both an orange and brown wire on it.  Re-assemble.  Profit.

 

Just a heads up... this will disable the two "mouse" buttons on the side of the controller, so you have to decide what you want more.  I never used those buttons once.  I have removed them completely and put an arcade button cap in the hole.  You can get those from Groovy Game Gear or any other arcade parts place.

 

Thanks again for all the help earlier... everything is working great... pinscape and trackball living side-by-side in harmony.  The nudging is super fun.  Thanks.

[Drybonz]

My pinscape controller has started causing the pinball to move very slowly, like in slow motion... and even make the ball stop in the middle of the table.  If I unplug the controller everything is fine, but the same problems happen when I plug it back in.  How would I fix this problem?

 

Thanks for the help.

 

*edit*  Actually, just figured it out... had to raise the deadzone setting in VP.  Not sure why this started happening randomly, but this seems to have fixed it.

Edited by Drybonz, 22 July 2016 - 03:13 AM.

[sasa12345]

Here alone without tilt function, I accidentally pushed the cab but he did not register the tilt, the ball moves when you push all ok, but there is no tilt? 991.10 VER

Before everything was working perfectly ...

where did I go wrong?

thanks in advance MJR

[Mark70]

Thank you very much for this project!

I use it for plunger (with potentiometer) and for the nudge function.

[MatthGyver]

 

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.

 

 

Hi,

I've same problem that Santos76.

Teensy doesn't work with pinscape board and your patched DOF.

I get this error :

2016.08.02 21:16:37.754	EXCEPTION: TeensyStripController TeensyStripController updater thread  could not connect to the controller. Thread will quit.
2016.08.02 21:16:37.754	EXCEPTION: Thread: TeensyStripController TeensyStripController updater thread 
2016.08.02 21:16:37.754	EXCEPTION: Message: The TeensyStripController did not send the expected 3 bytes containing the data on the max number of leds per channel. Will not send data to the controller
2016.08.02 21:16:37.754	EXCEPTION: Stacktrace:    à DirectOutput.Cab.Out.AdressableLedStrip.TeensyStripController.ConnectToController()
2016.08.02 21:16:37.754	EXCEPTION: Stacktrace:    à DirectOutput.Cab.Out.OutputControllerCompleteBase.UpdaterThreadDoIt()
2016.08.02 21:16:37.754	EXCEPTION: Targetsite: Void ConnectToController()

Teensy work with classical DOF R3 but not your board :-/

If I plug Pinscape board, VP crash with this message :

Signature du problème :
  Nom d’événement de problème:	CLR20r3
  Signature du problème 01:	VPinball915.exe
  Signature du problème 02:	9.1.5.0
  Signature du problème 03:	51597acc
  Signature du problème 04:	DirectOutput
  Signature du problème 05:	0.9.5812.27024
  Signature du problème 06:	565c5690
  Signature du problème 07:	2a5
  Signature du problème 08:	15
  Signature du problème 09:	System.AccessViolationException
  Version du système:	6.3.9600.2.0.0.256.48
  Identificateur de paramètres régionaux:	1036
  Information supplémentaire n° 1:	5861
  Information supplémentaire n° 2:	5861822e1919d7c014bbb064c64908b2
  Information supplémentaire n° 3:	1318
  Information supplémentaire n° 4:	13181ae637ac2592fac0ca2dd662cdcc

If this errors messages could help ...

 

Thank you

 

EDIT :

 

I just try with original DOF R3  version that you have put in link into "PinscapeConfigTool" and all is done :-)

Edited by MatthGyver, 03 August 2016 - 05:09 PM.