975 replies to this topic

[mjr]

you were right with the keyboard input .

I just all off.

PinballX starts now.

 

DirectOutput_R3Beta2_Build_5818.37242 was the latest version that I've found.

DirectOutput still does not work with me.

DirectOutput seems to start well , but I get no output from the Pinscape controller.

 

Okay, it sounds like my latest changes haven't made it into the DOF DLL yet.

 

 

Is there a tool where you can directly control the output to the test.

 

Not currently - I'm planning to add an output tester to the config tool, but that's not there yet.

[Santos76]

Hi Mjr ,
I can also connect ground of my 24V system on Pinscape .
My Contractors have 24V and I want to connect them to the Chieme Board.

Regards Sascha

[mjr]

I can also connect ground of my 24V system on Pinscape .
My Contractors have 24V and I want to connect them to the Chieme Board.

 

Yes, that'll work fine.  You can use multiple power supplies for the toys, with a mix of voltages.  Just connect all of the black/negative/ground/0V terminals from all of the power supplies together.  The recommended MOSFETs for the power board and chime board are rated for upwards of 50V, so just about anything you can put in a virtual pinball is within the limits.

[Santos76]

Cool, thank for you reply.

Regards Sascha

[roar]

I'm having trouble getting Windows to properly recognize my pinscape controller board... I swear I read a post on here on how to get the 'default' windows driver uninstalled so this would work, but the best I can seem to manage is to get it to show up under Other Devices with a question mark over Pinscape Controller. Can anyone point me to that reply?

 

Edit: Nevermind,I just reset my KLZ25 back to the original firmware and walked through all the steps again and everything is fine.

 

Edit number 2: Ugh!!! Back to the same problem. Once I come out of the initial install of the Pinscape Firmware the device manager detects the controller fine, but when I go to program my device with all my settings and it reboots that is when Windows stops recognizing it. So now I'm back to where I was before.

Edit number 3: And here we have found the information I was originally looking for... right on the Pinscape Setup tool Walked through it again and my device is now showing up again without error. What a morning.

Edited by roar, 28 May 2016 - 03:54 PM.

[Sam66]

This is probably not V2 software related but it may be - I'm running the latest firmware and used the new software for configuration.

 

In windows 7 if I use 'set up USB game controllers' I can see the state of all 32 inputs/buttons I have configured which is useful for testing.  The same board on a windows 10 machine shows only 7 buttons.  Both recognize it correctly as Pinscape controller when plugged in and the gyro appears to work ok on both.

 

mjr do you have any pointers what I should be looking at to resolve this?

Edited by Sam66, 03 June 2016 - 09:11 PM.

[mjr]

This is probably not V2 software related but it may be - I'm running the latest firmware and used the new software for configuration.

 

In windows 7 if I use 'set up USB game controllers' I can see the state of all 32 inputs/buttons I have configured which is useful for testing.  The same board on a windows 10 machine shows only 7 buttons.  Both recognize it correctly as Pinscape controller when plugged in and the gyro appears to work ok on both.

 

mjr do you have any pointers what I should be looking at to resolve this?

 

I've run into that on a few occasions during debugging - it seems that if there's a problem connecting, the Windows HID driver can put some incorrect information in the registry that sticks on future connections.

 

Two things to try.

 

1.  Go to Device Manager and open the Human Interface Devices section.  There should be either one or two entries titled "USB Input Device".  At least, there should be one or two entries for the Pinscape unit - you might have more than that from other devices as well.  If you have any keyboard keys (as opposed to joystick buttons) enabled in your Pinscape setup, there should be two entries for Pinscape, otherwise just one.  

 

To make certain which ones are the Pinscape units, double-click the device and select the Events tab.  If there's no Events tab, it's for some other device and you can ignore it and try the others.  If there's an Events tab, look at the cryptic top line in the Information box.  For a Pinscape unit, it should look like this:

 

   Device USB\VID_FAFA&PID_00Fx\...

 

The key identifying parts are the FAFA and 00Fx (x is a hex digit, 0-9 or A-F).  If those match, it's the device you're looking for.

 

After you identify the one or two Pinscape entries, right-click them in the list and click Uninstall.  Say yes if there's confirmation dialog.  After they're gone, reset the KL25Z with the button or by unplugging and re-plugging it.  After it connects again, try the game controller panel and see if the buttons came back.

 

2.  If that didn't help, there's one more place to try.  Run regedit and find this key:

 

HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_FAFA&PID_00Fx\Calibration

 

Substitute the same 00Fx number as above.  If you find that key, unplug the KL2Z first, then delete the key.  Close regedit to make sure it writes the update.  Plug the KL25Z back in.

 

Hopefully one of those will clear it up.  There are probably other registry gremlins like this scattered around that I haven't found yet, but hopefully we won't have to hunt another one down today. 

Edited by mjr, 03 June 2016 - 09:43 PM.

[Mace]

Hey Mike,

 

A big thanks, just installed V2 and it's finally fixed the occassional USB not being recognised on boot which required the reset key to be pressed.

 

Other than the need to set up a virtual port for the Zeb plunger to function correctly (thanks to all in this thread for solving that one before I arrived) it's working like a charm.

[ronaldvg]

Hi all, I am trying out the Pinscape controller and I have one problem. Everything works great when I start VPX without the Pinscape controller connected. If I then connect it and Play the table, everything is ok. If I start VPX with the  controller attached, it runs the table until it says "Game Scripts" and then VPX crashes.

 

This only happens when I use B2S as the controller in the script, if I change that to the normal controller the table runs just fine, but then my Sainsmart Relay board is obviously not working.

 

In the Configtool all tests run fine, also the analog plunger is working very well. I guess it has something to do with the version of B2S or something. Maybe someone encountered this problem already ?

[mjr]

Hi all, I am trying out the Pinscape controller and I have one problem. Everything works great when I start VPX without the Pinscape controller connected. If I then connect it and Play the table, everything is ok. If I start VPX with the  controller attached, it runs the table until it says "Game Scripts" and then VPX crashes.

 

This only happens when I use B2S as the controller in the script, if I change that to the normal controller the table runs just fine, but then my Sainsmart Relay board is obviously not working.

 

In the Configtool all tests run fine, also the analog plunger is working very well. I guess it has something to do with the version of B2S or something. Maybe someone encountered this problem already ?

 

Do you have any keyboard keys set in the Pinscape configuration?  Either in the button mappings, or in the ZB Launch Ball feature?

 

 

 

If so, that might be the problem.  When the Pinscape unit has keyboard keys, it triggers a crash in the standard ledwiz.dll.  I'll PM you with a pointer to a fix.

[ronaldvg]

Yes, the ZB Launch was set to ENTER, as it is default I guess because I did not configure this yet. I read the post regarding PinballX and the keyboard commands earlier in this thread but did not connect the dots properly ;-)

 

Thanks for the very quick reply.

[sasa12345]

Congratulations for this soft 10+  ,

I had a script error or I installed the Explorer 11 and solved all!

Thank you very much

[Drybonz]

So, I have ordered and recieved my KL25Z, and installed it in my box, then fired up the Pinscape software and it is telling me I can't update the firmware without Windows 7 or earlier.  Are you guys all running old versions of Windows, or is there some way around this?  Any help is appreciated.

[mjr]

So, I have ordered and recieved my KL25Z, and installed it in my box, then fired up the Pinscape software and it is telling me I can't update the firmware without Windows 7 or earlier.  Are you guys all running old versions of Windows, or is there some way around this?  Any help is appreciated.

 

Unfortunately I don't know of a way around it.  The firmware they install at the factory is incompatible with Windows 8 and later, due to something about the way Windows tries to write some hidden desktop files to the virtual disk drive when you first connect it.  I've searched far and wide for a solution that doesn't involve an old version of Windows, but without any success - as far as I've seen there's simply no workaround.  

 

That said, you only need Win 7 or earlier *initially*, in order to replace the factory firmware with the newer version.  As soon as you do that, the device becomes happy on all Windows versions.  So you don't need to permanently switch to an old Windows, you just need to boot it up for long enough to do the update.

 

Hopefully you have an old machine or a friend with a Win 7 or XP machine where you can do the initial update.  If none of that is possible for you, it *might* work to use something like a VirtualBox VM to run an XP image in a VM on your current machine.  VirtualBox lets you hand full control of a USB device to the client OS, so you might be able to get that to work.  I've never tried that, though, so I don't know if the VM pass-through is perfect enough to get past the initial connection issue that creates the problem.

 

If you go the VM route and you have success with that, I'd really appreciate it if you could write down the steps you did to get it to work - I'd love to be able to add that to the documentation for anyone else in your situation!

[Drybonz]

Thanks for the quick reply... I appreciate it.  As it turns out, I'm actually stuck at the controller not being recognized stage.  I have been reading through this thread looking for a solution to that first.  I see that I do have the "FAFA" entry under HID devices in the device manager, but when I start up the Pinscape software it is always telling me that I do not have a controller connected.

 

*edit*  or the firmware problem is causing it to be not recognized at all, I guess?

Edited by Drybonz, 12 June 2016 - 12:08 AM.

[mjr]

Thanks for the quick reply... I appreciate it.  As it turns out, I'm actually stuck at the controller not being recognized stage.  I have been reading through this thread looking for a solution to that first.  I see that I do have the "FAFA" entry under HID devices in the device manager, but when I start up the Pinscape software it is always telling me that I do not have a controller connected.

 

*edit*  or the firmware problem is causing it to be not recognized at all, I guess?

 

It could be the firmware issue, but it's hard to be sure.  The symptoms are really weird, because the basic problem is that the software download process (from Windows to the KL25Z) gets corrupted, but the device doesn't have any way to report the failure to Windows, so everything *looks* like it worked on the Windows side.  Windows happily reports success, but things just mysteriously don't work.  I'm actually surprised things got as far as making the FAFA entry, because that means that you probably managed to download *something* to the device.  Do you by chance have an LedWiz in your system, now or in the past?  That's the same ID that the LedWiz uses (that's how the LedWiz compatibility mode works, by mimicking the ID).  The FAFA entry you see might be coming from that if so.  If not then you've managed to get the Pinscape install partway there, although I'm not sure how!

[Drybonz]

I don't have LedWiz.  My setup is kind of weird.  I'm on my desktop system with dual monitors and an arcade controller which also doubles as my pinball controls.  I'm installing the Pinscape controller (for the nudging) in the arcade controller box.

Edited by Drybonz, 12 June 2016 - 01:05 AM.

[mjr]

I don't have LedWiz.  My setup is kind of weird.  I'm on my desktop system with dual monitors and an arcade controller which also doubles as my pinball controls.  I'm installing the Pinscape controller (for the nudging) in the arcade controller box.

 

Well, unless the arcade controller also uses the FAFA ID, you must have gotten at least a partial download to work.  If you go to regedit, and navigate to 

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA...

 

...what do you see there, for the full key name and the subkeys?

Also, just to make sure, you've got the joystick port on the KL25Z plugged in at this point, right?  Do you still have the programming port plugged in as well, or just the joystick port?  You might try unplugging the programming port if it's still connected.

[Drybonz]

The reg key is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060

 

subkeys:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060\7&1262d56e&0&2

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060\8&3541e348&0&2

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060\8&c60c9e6&0&2

 

I have the KL25Z out of the box now (for ease of troubleshooting).  The port listed as "KL25Z USB" is plugged in, and not the one listed as "Open SDA" in the diagram.

 

*edit*  I have also now set up Windows XP in VirtualBox and downloaded the Pinscape software there.  It is telling me that Pinscape Config Tool is not a valid application.  Is this because of the Internet Explorer issue?  I'm not sure that I can get a new version of IE in there.

Edited by Drybonz, 12 June 2016 - 01:46 AM.

[mjr]

The reg key is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060

 

subkeys:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060\7&1262d56e&0&2

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060\8&3541e348&0&2

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_FAFA&PID_0060\8&c60c9e6&0&2

 

Okay, I think that actually is your other arcade controller!  Is it by chance a Groovy Game Gear product?  FAFA is their "vendor ID", which means everything from that company will have that ID.  The PID_0060 part is definitely not something the Pinscape software would use.

 

 

I have the KL25Z out of the box now (for ease of troubleshooting).  The port listed as "KL25Z USB" is plugged in, and not the one listed as "Open SDA" in the diagram.

 

*edit*  I have also now set up Windows XP in VirtualBox and downloaded the Pinscape software there.  It is telling me that Pinscape Config Tool is not a valid application.  Is this because of the Internet Explorer issue?  I'm not sure that I can get a new version of IE in there.

 

Okay - here's what you should try.

 

You can do the firmware update without the Pinscape software involved.  The only thing it does is show you a list of steps, since the firmware update is all third-party software from the manufacturer that you have to install.

 

You said you have two monitors, so what I'm going to suggest is that you make sure you have your REAL Windows running on one monitor, and the XP VM running on the other monitor.  On your REAL Windows monitor, bring up the Pinscape tool.  Go to the "Set up a new KL25Z" page, click Start, click past the warning about Windows versions, and then click SHOW ALL to list all of the steps.

 

Now you can just leave that window up on your real Windows monitor and switch over to the other monitor where you have XP running.  Just go through the steps listed in the Pinscape window, carrying them out through the XP VM.  

 

Does that make sense?