An input/output controller for virtual pinball machines, with plunger position tracking, accelerometer-based nudge sensing, button input encoding, and feedback device control.

Dependencies:   USBDevice mbed FastAnalogIn FastIO FastPWM SimpleDMA

/media/uploads/mjr/pinscape_no_background_small_L7Miwr6.jpg

The Pinscape Controller is a special-purpose software project that I wrote for my virtual pinball machine.

New version: V2 is now available! The information below is for version 1, which will continue to be available for people who prefer the original setup.

What exactly is a virtual pinball machine? It's basically a video-game pinball emulator built to look like a real pinball machine. (The picture at right is the one I built.) You start with a standard pinball cabinet, either built from scratch or salvaged from a real machine. Inside, you install a PC motherboard to run the software, and install TVs in place of the playfield and backglass. Several Windows pinball programs can take advantage of this setup, including the open-source project Visual Pinball, which has hundreds of tables available. Building one of these makes a great DIY project, and it's a good way to add to your skills at woodworking, computers, and electronics. Check out the Cabinet Builders' Forum on vpforums.org for lots of examples and advice.

This controller project is a key piece in my setup that helps integrate the video game into the pinball cabinet. It handles several input/output tasks that are unique to virtual pinball machines. First, it lets you connect a mechanical plunger to the software, so you can launch the ball like on a real machine. Second, it sends "nudge" data to the software, based on readings from an accelerometer. This lets you interact with the game physically, which makes the playing experience more realistic and immersive. Third, the software can handle button input (for wiring flipper buttons and other cabinet buttons), and fourth, it can control output devices (for tactile feedback, button lights, flashers, and other special effects).

Documentation

The Hardware Build Guide (PDF) has detailed instructions on how to set up a Pinscape Controller for your own virtual pinball cabinet.

Update notes

December 2015 version: This version fully supports the new Expansion Board project, but it'll also run without it. The default configuration settings haven't changed, so existing setups should continue to work as before.

August 2015 version: Be sure to get the latest version of the Config Tool for windows if you're upgrading from an older version of the firmware. This update adds support for TSL1412R sensors (a version of the 1410 sensor with a slightly larger pixel array), and a config option to set the mounting orientation of the board in the firmware rather than in VP (for better support for FP and other pinball programs that don't have VP's flexibility for setting the rotation).

Feb/March 2015 software versions: If you have a CCD plunger that you've been using with the older versions, and the plunger stops working (or doesn't work as well) after you update to the latest version, you might need to increase the brightness of your light source slightly. Check the CCD exposure with the Windows config tool to see if it looks too dark. The new software reads the CCD much more quickly than the old versions did. This makes the "shutter speed" faster, which might require a little more light to get the same readings. The CCD is actually really tolerant of varying light levels, so you probably won't have to change anything for the update - I didn't. But if you do have any trouble, have a look at the exposure meter and try a slightly brighter light source if the exposure looks too dark.

Downloads

  • Config tool for Windows (.exe and C# source): this is a Windows program that lets you view the raw pixel data from the CCD sensor, trigger plunger calibration mode, and configure some of the software options on the controller.
  • Custom VP builds: I created modified versions of Visual Pinball 9.9 and Physmod5 that you might want to use in combination with this controller. The modified versions have special handling for plunger calibration specific to the Pinscape Controller, as well as some enhancements to the nudge physics. If you're not using the plunger, you might still want it for the nudge improvements. The modified version also works with any other input controller, so you can get the enhanced nudging effects even if you're using a different plunger/nudge kit. The big change in the modified versions is a "filter" for accelerometer input that's designed to make the response to cabinet nudges more realistic. It also makes the response more subdued than in the standard VP, so it's not to everyone's taste. The downloads include both the updated executables and the source code changes, in case you want to merge the changes into your own custom version(s).

    Note! These features are now standard in the official VP 9.9.1 and VP 10 releases, so you don't need my custom builds if you're using 9.9.1 or 10 or later. I don't think there's any reason to use my 9.9 instead of the official 9.9.1, but I'm leaving it here just in case. In the official VP releases, look for the checkbox "Enable Nudge Filter" in the Keys preferences dialog. (There's no checkbox in my custom builds, though; the filter is simply always on in those.)
  • Output circuit shopping list: This is a saved shopping cart at mouser.com with the parts needed for each output driver, if you want to use the LedWiz emulator feature. Note that quantities in the cart are for one output channel, so multiply everything by the number of channels you plan to use, except that you only need one of the ULN2803 transistor array chips for each eight output circuits.
  • Lemming77's potentiometer mounting bracket and shooter rod connecter: Sketchup designs for 3D-printable parts for mounting a slide potentiometer as the plunger sensor. These were designed for a particular slide potentiometer that used to be available from an Aliexpress.com seller but is no longer listed. You can probably use this design as a starting point for other similar devices; just check the dimensions before committing the design to plastic.

Features

  • Plunger position sensing, using a TAOS TSL 1410R CCD linear array sensor. This sensor is a 1280 x 1 pixel array at 400 dpi, which makes it about 3" long - almost exactly the travel distance of a standard pinball plunger. The idea is that you install the sensor just above (within a few mm of) the shooter rod on the inside of the cabinet, with the CCD window facing down, aligned with and centered on the long axis of the shooter rod, and positioned so that the rest position of the tip is about 1/2" from one end of the window. As you pull back the plunger, the tip will travel down the length of the window, and the maximum retraction point will put the tip just about at the far end of the window. Put a light source below, facing the sensor - I'm using two typical 20 mA blue LEDs about 8" away (near the floor of the cabinet) with good results. The principle of operation is that the shooter rod casts a shadow on the CCD, so pixels behind the rod will register lower brightness than pixels that aren't in the shadow. We scan down the length of the sensor for the edge between darker and brighter, and this tells us how far back the rod has been pulled. We can read the CCD at about 25-30 ms intervals, so we can get rapid updates. We pass the readings reports to VP via our USB joystick reports.

    The hardware build guide includes schematics showing how to wire the CCD to the KL25Z. It's pretty straightforward - five wires between the two devices, no external components needed. Two GPIO ports are used as outputs to send signals to the device and one is used as an ADC in to read the pixel brightness inputs. The config tool has a feature that lets you display the raw pixel readings across the array, so you can test that the CCD is working and adjust the light source to get the right exposure level.

    Alternatively, you can use a slide potentiometer as the plunger sensor. This is a cheaper and somewhat simpler option that seems to work quite nicely, as you can see in Lemming77's video of this setup in action. This option is also explained more fully in the build guide.
  • Nudge sensing via the KL25Z's on-board accelerometer. Mounting the board in your cabinet makes it feel the same accelerations the cabinet experiences when you nudge it. Visual Pinball already knows how to interpret accelerometer input as nudging, so we simply feed the acceleration readings to VP via the joystick interface.
  • Cabinet button wiring. Up to 24 pushbuttons and switches can be wired to the controller for input controls (for example, flipper buttons, the Start button, the tilt bob, coin slot switches, and service door buttons). These appear to Windows as joystick buttons. VP can map joystick buttons to pinball inputs via its keyboard preferences dialog. (You can raise the 24-button limit by editing the source code, but since all of the GPIO pins are allocated, you'll have to reassign pins currently used for other functions.)
  • LedWiz emulation (limited). In addition to emulating a joystick, the device emulates the LedWiz USB interface, so controllers on the PC side such as DirectOutput Framework can recognize it and send it commands to control lights, solenoids, and other feedback devices. 22 GPIO ports are assigned by default as feedback device outputs. This feature has some limitations. The big one is that the KL25Z hardware only has 10 PWM channels, which isn't enough for a fully decked-out cabinet. You also need to build some external power driver circuitry to use this feature, because of the paltry 4mA output capacity of the KL25Z GPIO ports. The build guide includes instructions for a simple and robust output circuit, including part numbers for the exact components you need. It's not hard if you know your way around a soldering iron, but just be aware that it'll take a little work.

Warning: This is not replacement software for the VirtuaPin plunger kit. If you bought the VirtuaPin kit, please don't try to install this software. The VP kit happens to use the same microcontroller board, but the rest of its hardware is incompatible. The VP kit uses a different type of sensor for its plunger and has completely different button wiring, so the Pinscape software won't work properly with it.

Committer:
mjr
Date:
Mon Aug 18 21:46:10 2014 +0000
Revision:
9:fd65b0a94720
Parent:
6:cc35eb643e8f
Child:
10:976666ffa4ef
Tweaks to plunger firing detection

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mjr 3:3514575d4f86 1 /* Copyright (c) 2010-2011 mbed.org, MIT License
mjr 3:3514575d4f86 2 * Modified Mouse code for Joystick - WH 2012
mjr 3:3514575d4f86 3 *
mjr 3:3514575d4f86 4 * Permission is hereby granted, free of charge, to any person obtaining a copy of this software
mjr 3:3514575d4f86 5 * and associated documentation files (the "Software"), to deal in the Software without
mjr 3:3514575d4f86 6 * restriction, including without limitation the rights to use, copy, modify, merge, publish,
mjr 3:3514575d4f86 7 * distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the
mjr 3:3514575d4f86 8 * Software is furnished to do so, subject to the following conditions:
mjr 3:3514575d4f86 9 *
mjr 3:3514575d4f86 10 * The above copyright notice and this permission notice shall be included in all copies or
mjr 3:3514575d4f86 11 * substantial portions of the Software.
mjr 3:3514575d4f86 12 *
mjr 3:3514575d4f86 13 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
mjr 3:3514575d4f86 14 * BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
mjr 3:3514575d4f86 15 * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
mjr 3:3514575d4f86 16 * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
mjr 3:3514575d4f86 17 * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
mjr 3:3514575d4f86 18 */
mjr 3:3514575d4f86 19
mjr 3:3514575d4f86 20 #include "stdint.h"
mjr 3:3514575d4f86 21 #include "USBJoystick.h"
mjr 3:3514575d4f86 22
mjr 9:fd65b0a94720 23 bool USBJoystick::update(int16_t x, int16_t y, int16_t z, uint16_t buttons, uint16_t status)
mjr 3:3514575d4f86 24 {
mjr 3:3514575d4f86 25 _x = x;
mjr 3:3514575d4f86 26 _y = y;
mjr 3:3514575d4f86 27 _z = z;
mjr 3:3514575d4f86 28 _buttons = buttons;
mjr 9:fd65b0a94720 29 _status = (uint8_t)status;
mjr 3:3514575d4f86 30
mjr 3:3514575d4f86 31 // send the report
mjr 3:3514575d4f86 32 return update();
mjr 3:3514575d4f86 33 }
mjr 3:3514575d4f86 34
mjr 3:3514575d4f86 35 bool USBJoystick::update() {
mjr 3:3514575d4f86 36 HID_REPORT report;
mjr 3:3514575d4f86 37
mjr 3:3514575d4f86 38 // Fill the report according to the Joystick Descriptor
mjr 6:cc35eb643e8f 39 #define put(idx, val) (report.data[idx] = (val) & 0xff, report.data[(idx)+1] = ((val) >> 8) & 0xff)
mjr 9:fd65b0a94720 40 put(0, _buttons);
mjr 6:cc35eb643e8f 41 put(2, _x);
mjr 6:cc35eb643e8f 42 put(4, _y);
mjr 6:cc35eb643e8f 43 put(6, _z);
mjr 9:fd65b0a94720 44 report.data[8] = _status;
mjr 9:fd65b0a94720 45 report.length = 9;
mjr 3:3514575d4f86 46
mjr 5:a70c0bce770d 47 // send the report
mjr 3:3514575d4f86 48 return sendNB(&report);
mjr 3:3514575d4f86 49 }
mjr 9:fd65b0a94720 50
mjr 3:3514575d4f86 51 bool USBJoystick::move(int16_t x, int16_t y) {
mjr 3:3514575d4f86 52 _x = x;
mjr 3:3514575d4f86 53 _y = y;
mjr 3:3514575d4f86 54 return update();
mjr 3:3514575d4f86 55 }
mjr 3:3514575d4f86 56
mjr 3:3514575d4f86 57 bool USBJoystick::setZ(int16_t z) {
mjr 3:3514575d4f86 58 _z = z;
mjr 3:3514575d4f86 59 return update();
mjr 3:3514575d4f86 60 }
mjr 3:3514575d4f86 61
mjr 3:3514575d4f86 62 bool USBJoystick::buttons(uint16_t buttons) {
mjr 3:3514575d4f86 63 _buttons = buttons;
mjr 3:3514575d4f86 64 return update();
mjr 3:3514575d4f86 65 }
mjr 3:3514575d4f86 66
mjr 3:3514575d4f86 67
mjr 3:3514575d4f86 68 void USBJoystick::_init() {
mjr 3:3514575d4f86 69
mjr 3:3514575d4f86 70 _x = 0;
mjr 3:3514575d4f86 71 _y = 0;
mjr 3:3514575d4f86 72 _z = 0;
mjr 3:3514575d4f86 73 _buttons = 0x0000;
mjr 9:fd65b0a94720 74 _status = 0;
mjr 3:3514575d4f86 75 }
mjr 3:3514575d4f86 76
mjr 3:3514575d4f86 77
mjr 3:3514575d4f86 78 uint8_t * USBJoystick::reportDesc()
mjr 3:3514575d4f86 79 {
mjr 3:3514575d4f86 80 static uint8_t reportDescriptor[] =
mjr 3:3514575d4f86 81 {
mjr 3:3514575d4f86 82 USAGE_PAGE(1), 0x01, // Generic desktop
mjr 3:3514575d4f86 83 USAGE(1), 0x04, // Joystick
mjr 3:3514575d4f86 84
mjr 3:3514575d4f86 85 COLLECTION(1), 0x01, // Application
mjr 9:fd65b0a94720 86
mjr 9:fd65b0a94720 87 // NB - the canonical joystick has a nested collection at this
mjr 9:fd65b0a94720 88 // point. We remove the inner collection to enable the LedWiz
mjr 9:fd65b0a94720 89 // emulation. The LedWiz API implementation on the PC side
mjr 9:fd65b0a94720 90 // appears to use the collection structure as part of the
mjr 9:fd65b0a94720 91 // device signature, and the real LedWiz descriptor has just
mjr 9:fd65b0a94720 92 // one top-level collection. The built-in Windows HID drivers
mjr 9:fd65b0a94720 93 // don't appear to care whether this collection is present or
mjr 9:fd65b0a94720 94 // not for the purposes of recognizing a joystick, so it seems
mjr 9:fd65b0a94720 95 // to make everyone happy to leave it out.
mjr 9:fd65b0a94720 96 //
mjr 9:fd65b0a94720 97 // All of the reference material for USB joystick device builders
mjr 9:fd65b0a94720 98 // does use the inner collection, so it's possible that omitting
mjr 9:fd65b0a94720 99 // it will create an incompatibility with some non-Windows hosts.
mjr 9:fd65b0a94720 100 // But that seems largely moot in that VP only runs on Windows.
mjr 9:fd65b0a94720 101 // If you're you're trying to adapt this code for a different
mjr 9:fd65b0a94720 102 // device and run into problems connecting to a non-Windows host,
mjr 9:fd65b0a94720 103 // try restoring the inner collection. You probably won't
mjr 9:fd65b0a94720 104 // care about LedWiz compatibility in such a situation so there
mjr 9:fd65b0a94720 105 // should be no reason not to return to the standard structure.
mjr 6:cc35eb643e8f 106 // COLLECTION(1), 0x00, // Physical
mjr 3:3514575d4f86 107
mjr 9:fd65b0a94720 108 // input report (device to host)
mjr 3:3514575d4f86 109 USAGE_PAGE(1), 0x09, // Buttons
mjr 3:3514575d4f86 110 USAGE_MINIMUM(1), 0x01, // { buttons }
mjr 3:3514575d4f86 111 USAGE_MAXIMUM(1), 0x10, // { 1-16 }
mjr 3:3514575d4f86 112 LOGICAL_MINIMUM(1), 0x00, // 1-bit buttons - 0...
mjr 3:3514575d4f86 113 LOGICAL_MAXIMUM(1), 0x01, // ...to 1
mjr 3:3514575d4f86 114 REPORT_SIZE(1), 0x01, // 1 bit per report
mjr 3:3514575d4f86 115 REPORT_COUNT(1), 0x10, // 16 reports
mjr 3:3514575d4f86 116 UNIT_EXPONENT(1), 0x00, // Unit_Exponent (0)
mjr 3:3514575d4f86 117 UNIT(1), 0x00, // Unit (None)
mjr 3:3514575d4f86 118 INPUT(1), 0x02, // Data, Variable, Absolute
mjr 3:3514575d4f86 119
mjr 3:3514575d4f86 120 USAGE_PAGE(1), 0x01, // Generic desktop
mjr 9:fd65b0a94720 121 USAGE(1), 0x30, // X axis
mjr 9:fd65b0a94720 122 USAGE(1), 0x31, // Y axis
mjr 9:fd65b0a94720 123 USAGE(1), 0x32, // Z axis
mjr 6:cc35eb643e8f 124 LOGICAL_MINIMUM(2), 0x00,0xF0, // each value ranges -4096
mjr 6:cc35eb643e8f 125 LOGICAL_MAXIMUM(2), 0x00,0x10, // ...to +4096
mjr 6:cc35eb643e8f 126 REPORT_SIZE(1), 0x10, // 16 bits per report
mjr 9:fd65b0a94720 127 REPORT_COUNT(1), 0x03, // 3 reports (X, Y, Z)
mjr 9:fd65b0a94720 128 INPUT(1), 0x02, // Data, Variable, Absolute
mjr 9:fd65b0a94720 129
mjr 9:fd65b0a94720 130 USAGE_PAGE(1), 0x06, // generic device controls - for config status
mjr 9:fd65b0a94720 131 USAGE(1), 0x00, // undefined device control
mjr 9:fd65b0a94720 132 LOGICAL_MINIMUM(1), 0x00, // 1-bit flags
mjr 9:fd65b0a94720 133 LOGICAL_MAXIMUM(1), 0x01,
mjr 9:fd65b0a94720 134 REPORT_SIZE(1), 0x01, // 1 bit per report
mjr 9:fd65b0a94720 135 REPORT_COUNT(1), 0x08, // 8 reports (8 bits)
mjr 3:3514575d4f86 136 INPUT(1), 0x02, // Data, Variable, Absolute
mjr 3:3514575d4f86 137
mjr 9:fd65b0a94720 138 // output report (host to device)
mjr 9:fd65b0a94720 139 REPORT_SIZE(1), 0x08, // 8 bits per report
mjr 9:fd65b0a94720 140 REPORT_COUNT(1), 0x08, // output report count (LEDWiz messages)
mjr 3:3514575d4f86 141 0x09, 0x01, // usage
mjr 3:3514575d4f86 142 0x91, 0x01, // Output (array)
mjr 3:3514575d4f86 143
mjr 6:cc35eb643e8f 144 // END_COLLECTION(0),
mjr 3:3514575d4f86 145 END_COLLECTION(0)
mjr 3:3514575d4f86 146 };
mjr 3:3514575d4f86 147
mjr 3:3514575d4f86 148 reportLength = sizeof(reportDescriptor);
mjr 3:3514575d4f86 149 return reportDescriptor;
mjr 3:3514575d4f86 150 }
mjr 3:3514575d4f86 151
mjr 3:3514575d4f86 152 uint8_t * USBJoystick::stringImanufacturerDesc() {
mjr 3:3514575d4f86 153 static uint8_t stringImanufacturerDescriptor[] = {
mjr 3:3514575d4f86 154 0x10, /*bLength*/
mjr 3:3514575d4f86 155 STRING_DESCRIPTOR, /*bDescriptorType 0x03*/
mjr 3:3514575d4f86 156 'm',0,'j',0,'r',0,'c',0,'o',0,'r',0,'p',0 /*bString iManufacturer - mjrcorp*/
mjr 3:3514575d4f86 157 };
mjr 3:3514575d4f86 158 return stringImanufacturerDescriptor;
mjr 3:3514575d4f86 159 }
mjr 3:3514575d4f86 160
mjr 3:3514575d4f86 161 uint8_t * USBJoystick::stringIserialDesc() {
mjr 3:3514575d4f86 162 static uint8_t stringIserialDescriptor[] = {
mjr 3:3514575d4f86 163 0x16, /*bLength*/
mjr 3:3514575d4f86 164 STRING_DESCRIPTOR, /*bDescriptorType 0x03*/
mjr 3:3514575d4f86 165 '0',0,'1',0,'2',0,'3',0,'4',0,'5',0,'6',0,'7',0,'8',0,'9',0, /*bString iSerial - 0123456789*/
mjr 3:3514575d4f86 166 };
mjr 3:3514575d4f86 167 return stringIserialDescriptor;
mjr 3:3514575d4f86 168 }
mjr 3:3514575d4f86 169
mjr 3:3514575d4f86 170 uint8_t * USBJoystick::stringIproductDesc() {
mjr 3:3514575d4f86 171 static uint8_t stringIproductDescriptor[] = {
mjr 9:fd65b0a94720 172 0x28, /*bLength*/
mjr 3:3514575d4f86 173 STRING_DESCRIPTOR, /*bDescriptorType 0x03*/
mjr 3:3514575d4f86 174 'P',0,'i',0,'n',0,'s',0,'c',0,'a',0,'p',0,'e',0,
mjr 3:3514575d4f86 175 ' ',0,'C',0,'o',0,'n',0,'t',0,'r',0,'o',0,'l',0,
mjr 3:3514575d4f86 176 'l',0,'e',0,'r',0 /*String iProduct */
mjr 3:3514575d4f86 177 };
mjr 3:3514575d4f86 178 return stringIproductDescriptor;
mjr 3:3514575d4f86 179 }