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:
Fri Jul 11 03:26:11 2014 +0000
Revision:
0:5acbbe3f4cf4
Child:
1:d913e0afb2ac
Initial testing setup, before starting on real configuration

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mjr 0:5acbbe3f4cf4 1 /* Copyright (c) 2010-2011 mbed.org, MIT License
mjr 0:5acbbe3f4cf4 2 * Modified Mouse code for Joystick - WH 2012
mjr 0:5acbbe3f4cf4 3 *
mjr 0:5acbbe3f4cf4 4 * Permission is hereby granted, free of charge, to any person obtaining a copy of this software
mjr 0:5acbbe3f4cf4 5 * and associated documentation files (the "Software"), to deal in the Software without
mjr 0:5acbbe3f4cf4 6 * restriction, including without limitation the rights to use, copy, modify, merge, publish,
mjr 0:5acbbe3f4cf4 7 * distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the
mjr 0:5acbbe3f4cf4 8 * Software is furnished to do so, subject to the following conditions:
mjr 0:5acbbe3f4cf4 9 *
mjr 0:5acbbe3f4cf4 10 * The above copyright notice and this permission notice shall be included in all copies or
mjr 0:5acbbe3f4cf4 11 * substantial portions of the Software.
mjr 0:5acbbe3f4cf4 12 *
mjr 0:5acbbe3f4cf4 13 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
mjr 0:5acbbe3f4cf4 14 * BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
mjr 0:5acbbe3f4cf4 15 * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
mjr 0:5acbbe3f4cf4 16 * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
mjr 0:5acbbe3f4cf4 17 * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
mjr 0:5acbbe3f4cf4 18 */
mjr 0:5acbbe3f4cf4 19
mjr 0:5acbbe3f4cf4 20 #include "stdint.h"
mjr 0:5acbbe3f4cf4 21 #include "USBJoystick.h"
mjr 0:5acbbe3f4cf4 22
mjr 0:5acbbe3f4cf4 23 bool USBJoystick::update(int16_t x, int16_t y, int16_t z, uint16_t buttons)
mjr 0:5acbbe3f4cf4 24 {
mjr 0:5acbbe3f4cf4 25 _x = x;
mjr 0:5acbbe3f4cf4 26 _y = y;
mjr 0:5acbbe3f4cf4 27 _z = z;
mjr 0:5acbbe3f4cf4 28 _buttons = buttons;
mjr 0:5acbbe3f4cf4 29
mjr 0:5acbbe3f4cf4 30 // send the report
mjr 0:5acbbe3f4cf4 31 return update();
mjr 0:5acbbe3f4cf4 32 }
mjr 0:5acbbe3f4cf4 33
mjr 0:5acbbe3f4cf4 34 bool USBJoystick::update() {
mjr 0:5acbbe3f4cf4 35 HID_REPORT report;
mjr 0:5acbbe3f4cf4 36
mjr 0:5acbbe3f4cf4 37 // Fill the report according to the Joystick Descriptor
mjr 0:5acbbe3f4cf4 38 report.data[0] = _buttons & 0xff;
mjr 0:5acbbe3f4cf4 39 report.data[1] = (_buttons >> 8) & 0xff;
mjr 0:5acbbe3f4cf4 40 report.data[2] = _x & 0xff;
mjr 0:5acbbe3f4cf4 41 report.data[3] = _y & 0xff;
mjr 0:5acbbe3f4cf4 42 report.data[4] = _z & 0xff;
mjr 0:5acbbe3f4cf4 43 report.length = 5;
mjr 0:5acbbe3f4cf4 44
mjr 0:5acbbe3f4cf4 45 return send(&report);
mjr 0:5acbbe3f4cf4 46 }
mjr 0:5acbbe3f4cf4 47
mjr 0:5acbbe3f4cf4 48 bool USBJoystick::move(int16_t x, int16_t y) {
mjr 0:5acbbe3f4cf4 49 _x = x;
mjr 0:5acbbe3f4cf4 50 _y = y;
mjr 0:5acbbe3f4cf4 51 return update();
mjr 0:5acbbe3f4cf4 52 }
mjr 0:5acbbe3f4cf4 53
mjr 0:5acbbe3f4cf4 54 bool USBJoystick::setZ(int16_t z) {
mjr 0:5acbbe3f4cf4 55 _z = z;
mjr 0:5acbbe3f4cf4 56 return update();
mjr 0:5acbbe3f4cf4 57 }
mjr 0:5acbbe3f4cf4 58
mjr 0:5acbbe3f4cf4 59 bool USBJoystick::buttons(uint16_t buttons) {
mjr 0:5acbbe3f4cf4 60 _buttons = buttons;
mjr 0:5acbbe3f4cf4 61 return update();
mjr 0:5acbbe3f4cf4 62 }
mjr 0:5acbbe3f4cf4 63
mjr 0:5acbbe3f4cf4 64
mjr 0:5acbbe3f4cf4 65 void USBJoystick::_init() {
mjr 0:5acbbe3f4cf4 66
mjr 0:5acbbe3f4cf4 67 _x = 0;
mjr 0:5acbbe3f4cf4 68 _y = 0;
mjr 0:5acbbe3f4cf4 69 _z = 0;
mjr 0:5acbbe3f4cf4 70 _buttons = 0x0000;
mjr 0:5acbbe3f4cf4 71 }
mjr 0:5acbbe3f4cf4 72
mjr 0:5acbbe3f4cf4 73
mjr 0:5acbbe3f4cf4 74 uint8_t * USBJoystick::reportDesc()
mjr 0:5acbbe3f4cf4 75 {
mjr 0:5acbbe3f4cf4 76 static uint8_t reportDescriptor[] =
mjr 0:5acbbe3f4cf4 77 {
mjr 0:5acbbe3f4cf4 78 USAGE_PAGE(1), 0x01, // Generic desktop
mjr 0:5acbbe3f4cf4 79 USAGE(1), 0x04, // Joystick
mjr 0:5acbbe3f4cf4 80
mjr 0:5acbbe3f4cf4 81 COLLECTION(1), 0x01, // Application
mjr 0:5acbbe3f4cf4 82 // COLLECTION(1), 0x00, // Physical
mjr 0:5acbbe3f4cf4 83
mjr 0:5acbbe3f4cf4 84 USAGE_PAGE(1), 0x09, // Buttons
mjr 0:5acbbe3f4cf4 85 USAGE_MINIMUM(1), 0x01, // { buttons }
mjr 0:5acbbe3f4cf4 86 USAGE_MAXIMUM(1), 0x10, // { 1-16 }
mjr 0:5acbbe3f4cf4 87 LOGICAL_MINIMUM(1), 0x00, // 1-bit buttons - 0...
mjr 0:5acbbe3f4cf4 88 LOGICAL_MAXIMUM(1), 0x01, // ...to 1
mjr 0:5acbbe3f4cf4 89 REPORT_SIZE(1), 0x01, // 1 bit per report
mjr 0:5acbbe3f4cf4 90 REPORT_COUNT(1), 0x10, // 16 reports
mjr 0:5acbbe3f4cf4 91 UNIT_EXPONENT(1), 0x00, // Unit_Exponent (0)
mjr 0:5acbbe3f4cf4 92 UNIT(1), 0x00, // Unit (None)
mjr 0:5acbbe3f4cf4 93 INPUT(1), 0x02, // Data, Variable, Absolute
mjr 0:5acbbe3f4cf4 94
mjr 0:5acbbe3f4cf4 95 USAGE_PAGE(1), 0x01, // Generic desktop
mjr 0:5acbbe3f4cf4 96 USAGE(1), 0x30, // X
mjr 0:5acbbe3f4cf4 97 USAGE(1), 0x31, // Y
mjr 0:5acbbe3f4cf4 98 USAGE(1), 0x32, // Z
mjr 0:5acbbe3f4cf4 99 LOGICAL_MINIMUM(1), 0x81, // each value ranges -127...
mjr 0:5acbbe3f4cf4 100 LOGICAL_MAXIMUM(1), 0x7f, // ...to 127
mjr 0:5acbbe3f4cf4 101 REPORT_SIZE(1), 0x08, // 8 bits per report
mjr 0:5acbbe3f4cf4 102 REPORT_COUNT(1), 0x03, // 3 reports
mjr 0:5acbbe3f4cf4 103 INPUT(1), 0x02, // Data, Variable, Absolute
mjr 0:5acbbe3f4cf4 104
mjr 0:5acbbe3f4cf4 105 REPORT_COUNT(1), 0x08, // input report count (LEDWiz messages)
mjr 0:5acbbe3f4cf4 106 0x09, 0x01, // usage
mjr 0:5acbbe3f4cf4 107 0x91, 0x01, // Output (array)
mjr 0:5acbbe3f4cf4 108
mjr 0:5acbbe3f4cf4 109 // END_COLLECTION(0),
mjr 0:5acbbe3f4cf4 110 END_COLLECTION(0)
mjr 0:5acbbe3f4cf4 111 };
mjr 0:5acbbe3f4cf4 112
mjr 0:5acbbe3f4cf4 113 reportLength = sizeof(reportDescriptor);
mjr 0:5acbbe3f4cf4 114 return reportDescriptor;
mjr 0:5acbbe3f4cf4 115 }
mjr 0:5acbbe3f4cf4 116
mjr 0:5acbbe3f4cf4 117 uint8_t * USBJoystick::stringImanufacturerDesc() {
mjr 0:5acbbe3f4cf4 118 static uint8_t stringImanufacturerDescriptor[] = {
mjr 0:5acbbe3f4cf4 119 0x10, /*bLength*/
mjr 0:5acbbe3f4cf4 120 STRING_DESCRIPTOR, /*bDescriptorType 0x03*/
mjr 0:5acbbe3f4cf4 121 'm',0,'j',0,'r',0,'c',0,'o',0,'r',0,'p',0 /*bString iManufacturer - mjrcorp*/
mjr 0:5acbbe3f4cf4 122 };
mjr 0:5acbbe3f4cf4 123 return stringImanufacturerDescriptor;
mjr 0:5acbbe3f4cf4 124 }
mjr 0:5acbbe3f4cf4 125
mjr 0:5acbbe3f4cf4 126 uint8_t * USBJoystick::stringIserialDesc() {
mjr 0:5acbbe3f4cf4 127 static uint8_t stringIserialDescriptor[] = {
mjr 0:5acbbe3f4cf4 128 0x16, /*bLength*/
mjr 0:5acbbe3f4cf4 129 STRING_DESCRIPTOR, /*bDescriptorType 0x03*/
mjr 0:5acbbe3f4cf4 130 '0',0,'1',0,'2',0,'3',0,'4',0,'5',0,'6',0,'7',0,'8',0,'9',0, /*bString iSerial - 0123456789*/
mjr 0:5acbbe3f4cf4 131 };
mjr 0:5acbbe3f4cf4 132 return stringIserialDescriptor;
mjr 0:5acbbe3f4cf4 133 }
mjr 0:5acbbe3f4cf4 134
mjr 0:5acbbe3f4cf4 135 uint8_t * USBJoystick::stringIproductDesc() {
mjr 0:5acbbe3f4cf4 136 static uint8_t stringIproductDescriptor[] = {
mjr 0:5acbbe3f4cf4 137 0x1E, /*bLength*/
mjr 0:5acbbe3f4cf4 138 STRING_DESCRIPTOR, /*bDescriptorType 0x03*/
mjr 0:5acbbe3f4cf4 139 'P',0,'i',0,'n',0,'M',0,'a',0,'s',0,'t',0,'e',0,'r',0,
mjr 0:5acbbe3f4cf4 140 ' ',0,'2',0,'0',0,'0',0,'0',0 /*String iProduct - PinMaster 2000*/
mjr 0:5acbbe3f4cf4 141 };
mjr 0:5acbbe3f4cf4 142 return stringIproductDescriptor;
mjr 0:5acbbe3f4cf4 143 }