975 replies to this topic

[monza]

 

I'm using V2 software and the issue I'm having as that when I pull the plunger it starts off really slow (ie 10mm of real plunger pull moves the virtual plunger about 2mm) and then 'speeds up' to the point where after about 30mm then it gets closer to 10mm real to 10mm virtual. Is this just something to avoid a bit of jitter when the plunger is at rest? Or is this because VPX is setup for a key press plunger so it is hard coded to accelerate up to speed?

 

I can think of two possibilities:

 

1.  You're using an audio-taper potentiometer.  You didn't say what kind of sensor you're using, but if it's a pot, it needs to be a "linear taper" type.  The behavior you describe would occur if you use an "audio taper" type, which has a logarithmic resistance curve, which would produce the kind of response curve you're seeing with varying speed across the pull range.  If you're using an optical sensor, this obviously isn't the issue.

 

2.  You might have run the Windows joystick calibration.  The Windows calibration is bad for plungers; don't use it.  If you might have accidentally run it in the past, you can delete the calibration as follows:

 

Bring up the Start menu search box or Press Windows+S

Type "set up usb game controllers" into the box

Click on "Set up USB game controllers" in the result list

Double-click "Pinscape Controller" in the list

Click on the "Settings" tab

Click "Reset to default"

 

 

 

Thanks MJR, I'm not 100% sure what type of sensor I'm using as a bought a kit from OZstick website

http://www.ozstick.c...inball-encoder/

 

I think it is potentiometer one as it has a little slider attached to the plunger. 

 

In the calibrate screen it jitters between about 50 and 70, and when pull it fully back it goes to about 65000 position even though it says max of 4095. Even once I successfully calibrate it still goes up to 65k, I thought it would readjust so that a full pull would be 4095. Anyway if I go into Joystick viewer plunger it looks good in that I see the full range of the plunge back and forth. However in this screen I still have the issue where the first 10mm is real slow on screen, also now noticed it does the same at the other end too. Is there a way to see the sensor type I'm using in the config tool?

[mjr]

Thanks MJR, I'm not 100% sure what type of sensor I'm using as a bought a kit from OZstick website

http://www.ozstick.c...inball-encoder/

 

I think it is potentiometer one as it has a little slider attached to the plunger. 

 

Yep, I think you're right, judging by the picture.  They don't say exactly what type it is, but it looks like they designed it for the this software, so hopefully they picked out a pot with the right taper and tested it.

 

 

In the calibrate screen it jitters between about 50 and 70, and when pull it fully back it goes to about 65000 position even though it says max of 4095. Even once I successfully calibrate it still goes up to 65k, I thought it would readjust so that a full pull would be 4095. Anyway if I go into Joystick viewer plunger it looks good in that I see the full range of the plunge back and forth. However in this screen I still have the issue where the first 10mm is real slow on screen, also now noticed it does the same at the other end too. 

 

Strange.  The non-linear reponse really sounds like it's a non-linear potentiometer, since the way the software interprets the input is pretty literal.  It just reads the voltage level on the pot slider element and interprets it linearly.  

 

It's really hard to know what's going on in the software without knowing more about the input it's seeing, so...  Do you have a voltmeter?  You could try checking the voltage across the two ends of the potentiometer to make sure it's reading 3.3V, and then measure the voltage at various positions to see if it looks linear.  

 

 

Is there a way to see the sensor type I'm using in the config tool?

 

I'm afraid the software doesn't have any way of knowing what's attached other than what you tell it via the config tool.

Edited by mjr, 21 July 2017 - 05:57 PM.

[Onevox]

DOF not communicating with B2S: greyed out "plugins" button on B2S setting window. Buttons light up with pinscape and LED testers on ports 18-21 (moved the wires on the connector from 24-27 just in case the port number had something to do with this) 

 

I moved this issue to the software support thread, since it doesn't appear to be an expansion board related. 

 

I would like to confirm that the only thing I need in the DOF Configtool is "pinscape = 1"

 

1. One thing I find odd is that in examples and screenshots, I see a 'config' folder in 'direct output' folder. But no instructions to create one. Mine isn't being generated with any step. I made one and unpacked Configtool files into it ... and it didn't help.

 

I've gone through DOF instructions a half dozen times. I've done all the stuff on the "read this first" post by swisslizard:

 

'DirectOutput' folder in Visual Pinball Folder, unpacked Grand Unified into that folder. Created 'plugins' folder in tables folder, with a shortcut to the "DirectOutput' folder.

Removed all 'blocked messages' from and running all as admin: all DOF, Configtool, and B2S files.

Checked 'activate plugins' in backglass. 

 

I also updated VPX to 10.3 while I was at it. And reinstalled B2S, and then redid all the unblocking and admin steps.

 

Edit: I read a post about someone having a problem with the another interface board and the problem went away when they disconnected the USB from the computer, then reconnected it. I may try that, too.

 

Thanks for guidance or help.

 

Pete

Edited by Onevox, 21 August 2017 - 05:12 PM.

[mjr]

I moved this issue to the software support thread, since it doesn't appear to be an expansion board related. 

 

That's my take on it - the board is working if you can activate the lights from the Pinscape config tool.  The problem looks to be something wrong with the DOF installation.

 

 

I would like to confirm that the only thing I need in the DOF Configtool is "pinscape = 1"

 

Correct.

 

 

1. One thing I find odd is that in examples and screenshots, I see a 'config' folder in 'direct output' folder. But no instructions to create one. Mine isn't being generated with any step. I made one and unpacked Configtool files into it ... and it didn't help.

 

I don't think that's in any way related to the problem, so I wouldn't expect it to make any difference to create or move around or otherwise manipulate any such folders.

 

 

Edit: I read a post about someone having a problem with the another interface board and the problem went away when they disconnected the USB from the computer, then reconnected it. I may try that, too.

 

That won't help in your case, I'm afraid.  That would only conceivably help if the board weren't connecting to USB.  Since you've already confirmed it is (you can connect to it successfully via the Pinscape config tool), the problem has nothing to do with USB.

 

 

 

Are you absolutely certain that the VP table you're testing with is DOF-enabled?  Try this:

 

1.  Open the table in the VP editor

 

2.  Edit the script

 

3.  Search for the word "DOF"

 

4.  Does the search turn up anything?  

[Onevox]

I'll check. It was flupper's BK2K. I guess I assumed that would be a safe bet. I think I also tried an MB from March, not the new one. Well, the great news is that my pinscape build seems to have gone well, thanks to the design, instructions and support. So glad I went that route. I'll direct further questions to DOF forums, if needed. Thanks mike.


Sent from my iPhone using Tapatalk

[mjr]

I'll check. It was flupper's BK2K. I guess I assumed that would be a safe bet. I think I also tried an MB from March, not the new one. Well, the great news is that my pinscape build seems to have gone well, thanks to the design, instructions and support. So glad I went that route. I'll direct further questions to DOF forums, if needed. Thanks mike.

 

I'm sure you'll get it working at this point - just a matter of figuring out which DLL or config file or whatever is missing/in the wrong place/wrong version/whatever.  DOF is notoriously difficult to debug when it doesn't "just work", since there are so many pieces that all have to connect to each other (VP, table script, B2S, plugin, DOF DLL) and none of them are very good at reporting errors.  But once you get it working, you can usually forget about it and it'll just do its thing.

[Onevox]

Well, I got it working! I decided to set up my VP folder just like Bambi Plattfuss shows in his FAQ video on YT, and I had multiple problems with file locations. The DOF issue came from duplicate versions of B2S files (one in table folder, and one in VP folder), which seems so obvious in hindsight. Once I put things where they needed to be, the button lights started firing. Everything I wanted Pinscape to do, its doing. Button lights, CCD plunger, buttons, nudge. I can't believe I built the main board without component or solder issues. It was not possible without your attention to keeping the design and build manageable. And the patient answers, from you and others, on this forum. Thanks for this. 

 

Now I join everyone in the tweaking my cabinet phase. And I have a good list to work on. 

[mjr]

Well, I got it working! I decided to set up my VP folder just like Bambi Plattfuss shows in his FAQ video on YT, and I had multiple problems with file locations. The DOF issue came from duplicate versions of B2S files (one in table folder, and one in VP folder), which seems so obvious in hindsight. Once I put things where they needed to be, the button lights started firing. Everything I wanted Pinscape to do, its doing. Button lights, CCD plunger, buttons, nudge. I can't believe I built the main board without component or solder issues. It was not possible without your attention to keeping the design and build manageable. And the patient answers, from you and others, on this forum. Thanks for this. 

 

That's really great!

[kiwiBri]

Well, I got it working! I decided to set up my VP folder just like Bambi Plattfuss shows in his FAQ video on YT, and I had multiple problems with file locations. The DOF issue came from duplicate versions of B2S files (one in table folder, and one in VP folder), which seems so obvious in hindsight. Once I put things where they needed to be, the button lights started firing. Everything I wanted Pinscape to do, its doing. Button lights, CCD plunger, buttons, nudge. I can't believe I built the main board without component or solder issues. It was not possible without your attention to keeping the design and build manageable. And the patient answers, from you and others, on this forum. Thanks for this. 

 

Now I join everyone in the tweaking my cabinet phase. And I have a good list to work on. 

 

 

excellent. make a system backup now!!   No, seriously, do this!

[Onevox]

Ok ok! Running now. Thank you for the reminder. I had the external USB HD on my workbench one meter away from my cab. No, really big thanks for the push!


Sent from my iPhone using Tapatalk

Edited by Onevox, 22 August 2017 - 10:58 PM.

[Onevox]

Should/Can the Pinscape controller turn on the Start and Exit buttons in PinballX? 

 

Edit: Getting ready to do the IR sensors for two TVs (which share the same IR code). Does the IR emitter function have the ability to delay the signal or does it? It seems that the ON button on my PF TV isn't immediately responsive after I turn on my cabinet button (sending power to the TVs). Seems like I need to wait about 2-3 seconds before the ON button actually turns the screen on.

 

(It dawned on me that the emitter is a great idea because I can position it near the coin door and just position the TV's sensor to the front of the cab, so no wire to disconnect when I lift or pull the PF TV. Sounds so obvious now.)

Edited by Onevox, 14 September 2017 - 01:53 PM.

[mjr]

Should/Can the Pinscape controller turn on the Start and Exit buttons in PinballX? 

 

Yes, at least I think so.  I actually haven't set that up on my own machine yet, but PBX is supposed to work with DOF, so it should just be a matter of activating the DOF support in PBX.  Sorry I don't have the how-to details for you - I really have to look into it and set it up myself.  I'm still using an old ad hoc scheme from the days before PBX DOF support where I fire up a batch script when DOF enters and exits to control the button lights.

[Onevox]

Thanks. I'll look for that in PBX.

Does IR emitter have option to set a delay? I have a tv that needs like 3-4 seconds of standby electricity before ON button works. Hit cabinet button then immediately hit tv power and it doesn't come on. Have to wait for a couple of seconds for the tv button to work. Thinking if the board sends a signal too quickly and the tv won't be ready to accept.


Sent from my iPhone using Tapatalk

[mjr]

Thanks. I'll look for that in PBX.

Does IR emitter have option to set a delay? I have a tv that needs like 3-4 seconds of standby electricity before ON button works. Hit cabinet button then immediately hit tv power and it doesn't come on. Have to wait for a couple of seconds for the tv button to work. Thinking if the board sends a signal too quickly and the tv won't be ready to accept.

 

Yep - you can set whatever delay you need in the "TV ON" section in the config tool.  Most TVs need the same thing.  I think the default is set to 7 seconds, which is pretty generous, but you can set it longer or shorter as needed.

 

And if the standard startup timing isn't enough, you can send IR commands from .CMD scripts via the PinscapeCmd.exe tool (included in the config tool folder):

 

  > PinscapeCmd SendIR=1 SendIR=2

 

sends the stored command in slot #1, followed by the command in slot #2.

[dgamboa1988]

im having trouble with the ir sensor. im trying to program to 1 tv but the board isnt learning any codes. tried just about everything to my knowledge but the information ive found on this is still pretty vague. 

[mjr]

im having trouble with the ir sensor. im trying to program to 1 tv but the board isnt learning any codes. tried just about everything to my knowledge but the information ive found on this is still pretty vague. 

 

You're using the IR learning mode in the Config Tool, I assume.  When you try to program a command, do you see any pulses appear in the raw sensor view area?  There should be a little graph showing the timing of the light pulses the sensor is receiving.  If that's not happening, the problem is at the hardware level - the sensor isn't getting any data.  That could be either because there's something wrong with the sensor or the wiring, or because the remote uses an IR light frequency that the sensor can't detect.  If you're seeing a pattern of pulses in the raw view, but the software won't learn a code, it means that your remote uses physically compatible IR signals that the sensor can receive, but that the Pinscape software doesn't recognize the protocol that your remote uses (the protocol is the method of encoding information in the light pulses).  If that's the case, use the raw data viewer to pull up the list of numbers giving the pulse timing data, copy that to an email, and send it to me, along with as much detail as possible on the brand and model number of the TV the remote came from.  I can try to find information on the protocol it uses and hopefully add it to the suite of supported protocols.

[Gribnif]

Hi mjr,

 

I built my Pinscape some time ago, and just recently started to have a major problem with my KLZ25 board. Last week, I went to the config tool and it told me there was a firmware update, so I told it to install it. At this point, the tool gave me some sort of error message (I think it was something like "failed to copy file", but to be honest I could be wrong.)

 

Now if I try to re-copy the Pinscape firmware the LED just flashes 7 times in a row and Pinscape never starts up: its LED never lights up and there is no HID device. The laststat.txt contains Error: 12291. The config tool doesn't recognize that the device is present, presumably because the firmware doesn't start.

 

I tried re-copying the bootloader and openSDA, and that seemed to work. When I look at the SDA_INFO.HTM it has the versions I copied: 

 

microboot kernel 1.05;

boot loader ver 1.11;

installed app: pemicro frdm-kl25z mass storage/debug app;

app version: 1.18

 

but I still can't reinstall pinscape. Do I have a brick on my hands?

[mjr]

Hi mjr,

 

I built my Pinscape some time ago, and just recently started to have a major problem with my KLZ25 board. Last week, I went to the config tool and it told me there was a firmware update, so I told it to install it. At this point, the tool gave me some sort of error message (I think it was something like "failed to copy file", but to be honest I could be wrong.)

 

Now if I try to re-copy the Pinscape firmware the LED just flashes 7 times in a row and Pinscape never starts up: its LED never lights up and there is no HID device. The laststat.txt contains Error: 12291. The config tool doesn't recognize that the device is present, presumably because the firmware doesn't start.

 

I tried re-copying the bootloader and openSDA, and that seemed to work. When I look at the SDA_INFO.HTM it has the versions I copied: 

 

microboot kernel 1.05;

boot loader ver 1.11;

installed app: pemicro frdm-kl25z mass storage/debug app;

app version: 1.18

 

but I still can't reinstall pinscape. Do I have a brick on my hands?

 

Hopefully you can revive it.  The KL25Z is pretty robust against bricking because there's a whole separate CPU just for boot loader.  That makes it almost impossible to brick it with software, because the boot loader CPU is physically isolated from the KL25Z side in such a way that the KL25Z software can't affect the boot loader side, no matter how badly it screws up.  And the boot loader completely wipes the KL25Z side's memory each time you download new firmware, which makes it almost impossible to brick the KL25Z side - each firmware update completely wipes out whatever damage the last firmware might have done.

 

It looks like your boot loader side is doing fine given that you can get to the SDA_INFO file.  I expect that the KL25Z memory side got wiped when you reinstalled the boot loader, but that should be okay - you just need to do a fresh install of the Pinscape software like you have a brand new board.  Try running the Pinscape tool and clicking on "Set up a new KL25Z" on the front page.  Skip the first step where it prompts you to update the firmware, since it looks like you're already good there.  

 

If it still can't load the Pinscape software, try going back to the "Set up a new KL25Z", and this time repeat the boot loader update process.  It might be that something got corrupted on that side, and hopefully doing another update will fix that.

 

Another thing to try if it keeps failing at those steps is to just unplug the KL25Z entirely for a few minutes (unplug both USB cables, so that it's completely un-powered).   The "7 flashes" you saw sometimes happens if you activate the boot loader too many times in a row without unplugging the board.  The boot loader has a bug in its firmware that makes it eventually crap out and need a reboot after multiple file transfers (the boot loader is unfortunately proprietary software, so it's not possible to look at it and track down that bug).  If you've been leaving it plugged into your system continuously, you might have just reached the point where it needed to be rebooted.  In my experience, all it takes to get it out of that mode is to reboot it completely by unplugging both of its USB cables so the whole thing power cycles.

Edited by mjr, 28 October 2017 - 08:44 PM.

[Gribnif]

Thanks for the help, mjr. I did get it working. It turns out that in addition to unplugging both USB ports, I also had to unplug the Pinscape main board from the PC PSU. Apparently, it was somehow powering the KLZ25Z.

[mjr]

Thanks for the help, mjr. I did get it working. It turns out that in addition to unplugging both USB ports, I also had to unplug the Pinscape main board from the PC PSU. Apparently, it was somehow powering the KLZ25Z.

 

Glad you were able to revive it!  Good to know about the PSU power aspect - something to try if anyone else runs into a similar problem.