Mike R / Mbed 2 deprecated Pinscape_Controller

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

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.

--- a/main.cpp	Wed Aug 27 00:43:20 2014 +0000
+++ b/main.cpp	Sat Sep 13 23:47:32 2014 +0000
@@ -110,6 +110,20 @@
 //    the plunger are removed and reinstalled, since the relative alignment of the
 //    parts could cahnge slightly when reinstalling.
 //
+//  - Button input wiring.  24 of the KL25Z's GPIO ports are mapped as digital inputs
+//    for buttons and switches.  The software reports these as joystick buttons when
+//    it sends reports to the PC.  These can be used to wire physical pinball-style
+//    buttons in the cabinet (e.g., flipper buttons, the Start button) and miscellaneous 
+//    switches (such as a tilt bob) to the PC.  Visual Pinball can use joystick buttons
+//    for input - you just have to assign a VP function to each button using VP's
+//    keyboard options dialog.  To wire a button physically, connect one terminal of
+//    the button switch to the KL25Z ground, and connect the other terminal to the
+//    the GPIO port you wish to assign to the button.  See the buttonMap[] array
+//    below for the available GPIO ports and their assigned joystick button numbers.
+//    If you're not using a GPIO port, you can just leave it unconnected - the digital
+//    inputs have built-in pull-up resistors, so an unconnected port is the same as
+//    an open switch (an "off" state for the button).
+//
 //  - LedWiz emulation.  The KL25Z can appear to the PC as an LedWiz device, and will
 //    accept and process LedWiz commands from the host.  The software can turn digital
 //    output ports on and off, and can set varying PWM intensitiy levels on a subset
@@ -281,7 +295,7 @@
 // 32 GPIO ports to buttons (equipped with momentary switches).
 // Connect each switch between the desired GPIO port and ground
 // (J9 pin 12 or 14).  When the button is pressed, we'll tell the
-// host PC that the corresponding joystick button as pressed.  We
+// host PC that the corresponding joystick button is pressed.  We
 // debounce the keystrokes in software, so you can simply wire
 // directly to pushbuttons with no additional external hardware.
 //
@@ -503,16 +517,26 @@
 class LwPwmOut: public LwOut
 {
 public:
-    LwPwmOut(PinName pin) : p(pin) { }
-    virtual void set(float val) { p = val; }
+    LwPwmOut(PinName pin) : p(pin) { prv = -1; }
+    virtual void set(float val) 
+    { 
+        if (val != prv)
+            p.write(prv = val); 
+    }
     PwmOut p;
+    float prv;
 };
 class LwDigOut: public LwOut
 {
 public:
-    LwDigOut(PinName pin) : p(pin) { }
-    virtual void set(float val) { p = val; }
+    LwDigOut(PinName pin) : p(pin) { prv = -1; }
+    virtual void set(float val) 
+    {
+         if (val != prv)
+            p.write((prv = val) == 0.0 ? 0 : 1); 
+    }
     DigitalOut p;
+    float prv;
 };
 class LwUnusedOut: public LwOut
 {
@@ -544,27 +568,64 @@
 
 // profile (brightness/blink) state for each LedWiz output
 static uint8_t wizVal[32] = {
-    0, 0, 0, 0, 0, 0, 0, 0,
-    0, 0, 0, 0, 0, 0, 0, 0,
-    0, 0, 0, 0, 0, 0, 0, 0,
-    0, 0, 0, 0, 0, 0, 0, 0
+    48, 48, 48, 48, 48, 48, 48, 48,
+    48, 48, 48, 48, 48, 48, 48, 48,
+    48, 48, 48, 48, 48, 48, 48, 48,
+    48, 48, 48, 48, 48, 48, 48, 48
 };
 
 static float wizState(int idx)
 {
-    if (wizOn[idx]) {
+    if (wizOn[idx]) 
+    {
         // on - map profile brightness state to PWM level
         uint8_t val = wizVal[idx];
-        if (val >= 1 && val <= 48)
-            return 1.0 - val/48.0;
+        if (val <= 48)
+        {
+            // PWM brightness/intensity level - rescale from the LedWiz
+            // 0..48 integer range to our internal PwmOut 0..1 float range
+            return val/48.0;
+        }
+        else if (val == 49)
+        {
+            // 49 is undefined in the LedWiz documentation.  Even so, DOF2
+            // *does* set outputs to 49 in some cases where it intends for
+            // them to be fully on.  This is a DOF2 bug, but the real LedWiz 
+            // treats 49 as fully on, so it's a harmless bug when used with 
+            // real LedWiz units.  For the sake of bug-for-bug compatibility, 
+            // we must do the same thing.
+            return 1.0;
+        }
         else if (val >= 129 && val <= 132)
-            return 0.0;
+        {
+            // Values of 129-132 select different flashing modes.  We don't
+            // support any of these.  Instead, simply treat them as fully on.  
+            // Note that DOF doesn't ever use modes 129-132, as it implements 
+            // all flashing modes itself on the host side, so this limitation 
+            // won't have any effect on DOF users.  You can observe it using 
+            // LedBlinky, though.
+            return 1.0;
+        }
         else
+        {
+            // Other values are undefined in the LedWiz documentation.  Hosts
+            // *should* never send undefined values, since whatever behavior an
+            // LedWiz unit exhibits in response is accidental and could change
+            // in a future version.  We'll treat all undefined values as equivalent 
+            // to 48 (fully on).
+            // 
+            // NB: the 49 and 129-132 cases are broken out above for the sake
+            // of documentation.  We end up using 1.0 as the return value for
+            // everything outside of the defined 0-48 range, so we could collapse
+            // this whole thing to a single 'else' branch, but I wanted to call 
+            // out the specific reasons for handling the settings above as we do.
             return 1.0;
+        }
     }
-    else {
-        // off
-        return 1.0;
+    else 
+    {
+        // off - show at 0 intensity
+        return 0.0;
     }
 }
 
@@ -1311,10 +1372,12 @@
     
                     // update the physical LED state if this is the last bank                    
                     if (pbaIdx == 24)
+                    {
                         updateWizOuts();
-    
-                    // advance to the next bank
-                    pbaIdx = (pbaIdx + 8) & 31;
+                        pbaIdx = 0;
+                    }
+                    else
+                        pbaIdx += 8;
                 }
             }
         }