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:
Tue Jul 22 04:33:47 2014 +0000
Revision:
2:c174f9ee414a
Before change to ISR for accelerometer

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mjr 2:c174f9ee414a 1 #include "FreescaleIAP.h"
mjr 2:c174f9ee414a 2
mjr 2:c174f9ee414a 3 //#define IAPDEBUG
mjr 2:c174f9ee414a 4
mjr 2:c174f9ee414a 5 enum FCMD {
mjr 2:c174f9ee414a 6 Read1s = 0x01,
mjr 2:c174f9ee414a 7 ProgramCheck = 0x02,
mjr 2:c174f9ee414a 8 ReadResource = 0x03,
mjr 2:c174f9ee414a 9 ProgramLongword = 0x06,
mjr 2:c174f9ee414a 10 EraseSector = 0x09,
mjr 2:c174f9ee414a 11 Read1sBlock = 0x40,
mjr 2:c174f9ee414a 12 ReadOnce = 0x41,
mjr 2:c174f9ee414a 13 ProgramOnce = 0x43,
mjr 2:c174f9ee414a 14 EraseAll = 0x44,
mjr 2:c174f9ee414a 15 VerifyBackdoor = 0x45
mjr 2:c174f9ee414a 16 };
mjr 2:c174f9ee414a 17
mjr 2:c174f9ee414a 18 static inline void run_command(FTFA_Type *);
mjr 2:c174f9ee414a 19 bool check_boundary(int address, unsigned int length);
mjr 2:c174f9ee414a 20 bool check_align(int address);
mjr 2:c174f9ee414a 21 IAPCode check_error(void);
mjr 2:c174f9ee414a 22
mjr 2:c174f9ee414a 23 FreescaleIAP::FreescaleIAP()
mjr 2:c174f9ee414a 24 {
mjr 2:c174f9ee414a 25 }
mjr 2:c174f9ee414a 26
mjr 2:c174f9ee414a 27 FreescaleIAP::~FreescaleIAP()
mjr 2:c174f9ee414a 28 {
mjr 2:c174f9ee414a 29 }
mjr 2:c174f9ee414a 30
mjr 2:c174f9ee414a 31 // execute an FTFA command
mjr 2:c174f9ee414a 32 static inline void run_command(FTFA_Type *ftfa)
mjr 2:c174f9ee414a 33 {
mjr 2:c174f9ee414a 34 // disable interupts
mjr 2:c174f9ee414a 35 __disable_irq();
mjr 2:c174f9ee414a 36
mjr 2:c174f9ee414a 37 // Clear possible old errors, start command, wait until done
mjr 2:c174f9ee414a 38 ftfa->FSTAT = FTFA_FSTAT_FPVIOL_MASK | FTFA_FSTAT_ACCERR_MASK | FTFA_FSTAT_RDCOLERR_MASK;
mjr 2:c174f9ee414a 39 ftfa->FSTAT = FTFA_FSTAT_CCIF_MASK;
mjr 2:c174f9ee414a 40 while (!(ftfa->FSTAT & FTFA_FSTAT_CCIF_MASK));
mjr 2:c174f9ee414a 41
mjr 2:c174f9ee414a 42 // re-enable interrupts
mjr 2:c174f9ee414a 43 __enable_irq();
mjr 2:c174f9ee414a 44 }
mjr 2:c174f9ee414a 45
mjr 2:c174f9ee414a 46
mjr 2:c174f9ee414a 47 IAPCode FreescaleIAP::erase_sector(int address) {
mjr 2:c174f9ee414a 48 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 49 printf("IAP: Erasing at %x\r\n", address);
mjr 2:c174f9ee414a 50 #endif
mjr 2:c174f9ee414a 51 if (check_align(address))
mjr 2:c174f9ee414a 52 return AlignError;
mjr 2:c174f9ee414a 53
mjr 2:c174f9ee414a 54 //Setup command
mjr 2:c174f9ee414a 55 FTFA->FCCOB0 = EraseSector;
mjr 2:c174f9ee414a 56 FTFA->FCCOB1 = (address >> 16) & 0xFF;
mjr 2:c174f9ee414a 57 FTFA->FCCOB2 = (address >> 8) & 0xFF;
mjr 2:c174f9ee414a 58 FTFA->FCCOB3 = address & 0xFF;
mjr 2:c174f9ee414a 59
mjr 2:c174f9ee414a 60 run_command(FTFA);
mjr 2:c174f9ee414a 61
mjr 2:c174f9ee414a 62 return check_error();
mjr 2:c174f9ee414a 63 }
mjr 2:c174f9ee414a 64
mjr 2:c174f9ee414a 65 IAPCode FreescaleIAP::program_flash(int address, const void *vp, unsigned int length) {
mjr 2:c174f9ee414a 66
mjr 2:c174f9ee414a 67 const char *data = (const char *)vp;
mjr 2:c174f9ee414a 68
mjr 2:c174f9ee414a 69 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 70 printf("IAP: Programming flash at %x with length %d\r\n", address, length);
mjr 2:c174f9ee414a 71 #endif
mjr 2:c174f9ee414a 72 if (check_align(address))
mjr 2:c174f9ee414a 73 return AlignError;
mjr 2:c174f9ee414a 74
mjr 2:c174f9ee414a 75 IAPCode eraseCheck = verify_erased(address, length);
mjr 2:c174f9ee414a 76 if (eraseCheck != Success)
mjr 2:c174f9ee414a 77 return eraseCheck;
mjr 2:c174f9ee414a 78
mjr 2:c174f9ee414a 79 IAPCode progResult;
mjr 2:c174f9ee414a 80 for (int i = 0; i < length; i+=4) {
mjr 2:c174f9ee414a 81 progResult = program_word(address + i, data + i);
mjr 2:c174f9ee414a 82 if (progResult != Success)
mjr 2:c174f9ee414a 83 return progResult;
mjr 2:c174f9ee414a 84 }
mjr 2:c174f9ee414a 85
mjr 2:c174f9ee414a 86 return Success;
mjr 2:c174f9ee414a 87 }
mjr 2:c174f9ee414a 88
mjr 2:c174f9ee414a 89 uint32_t FreescaleIAP::flash_size(void) {
mjr 2:c174f9ee414a 90 uint32_t retval = (SIM->FCFG2 & 0x7F000000u) >> (24-13);
mjr 2:c174f9ee414a 91 if (SIM->FCFG2 & (1<<23)) //Possible second flash bank
mjr 2:c174f9ee414a 92 retval += (SIM->FCFG2 & 0x007F0000u) >> (16-13);
mjr 2:c174f9ee414a 93 return retval;
mjr 2:c174f9ee414a 94 }
mjr 2:c174f9ee414a 95
mjr 2:c174f9ee414a 96 IAPCode FreescaleIAP::program_word(int address, const char *data) {
mjr 2:c174f9ee414a 97 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 98 printf("IAP: Programming word at %x, %d - %d - %d - %d\r\n", address, data[0], data[1], data[2], data[3]);
mjr 2:c174f9ee414a 99 #endif
mjr 2:c174f9ee414a 100 if (check_align(address))
mjr 2:c174f9ee414a 101 return AlignError;
mjr 2:c174f9ee414a 102
mjr 2:c174f9ee414a 103 //Setup command
mjr 2:c174f9ee414a 104 FTFA->FCCOB0 = ProgramLongword;
mjr 2:c174f9ee414a 105 FTFA->FCCOB1 = (address >> 16) & 0xFF;
mjr 2:c174f9ee414a 106 FTFA->FCCOB2 = (address >> 8) & 0xFF;
mjr 2:c174f9ee414a 107 FTFA->FCCOB3 = address & 0xFF;
mjr 2:c174f9ee414a 108 FTFA->FCCOB4 = data[3];
mjr 2:c174f9ee414a 109 FTFA->FCCOB5 = data[2];
mjr 2:c174f9ee414a 110 FTFA->FCCOB6 = data[1];
mjr 2:c174f9ee414a 111 FTFA->FCCOB7 = data[0];
mjr 2:c174f9ee414a 112
mjr 2:c174f9ee414a 113 run_command(FTFA);
mjr 2:c174f9ee414a 114
mjr 2:c174f9ee414a 115 return check_error();
mjr 2:c174f9ee414a 116 }
mjr 2:c174f9ee414a 117
mjr 2:c174f9ee414a 118 /* Check if no flash boundary is violated
mjr 2:c174f9ee414a 119 Returns true on violation */
mjr 2:c174f9ee414a 120 bool check_boundary(int address, unsigned int length) {
mjr 2:c174f9ee414a 121 int temp = (address+length - 1) / SECTOR_SIZE;
mjr 2:c174f9ee414a 122 address /= SECTOR_SIZE;
mjr 2:c174f9ee414a 123 bool retval = (address != temp);
mjr 2:c174f9ee414a 124 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 125 if (retval)
mjr 2:c174f9ee414a 126 printf("IAP: Boundary violation\r\n");
mjr 2:c174f9ee414a 127 #endif
mjr 2:c174f9ee414a 128 return retval;
mjr 2:c174f9ee414a 129 }
mjr 2:c174f9ee414a 130
mjr 2:c174f9ee414a 131 /* Check if address is correctly aligned
mjr 2:c174f9ee414a 132 Returns true on violation */
mjr 2:c174f9ee414a 133 bool check_align(int address) {
mjr 2:c174f9ee414a 134 bool retval = address & 0x03;
mjr 2:c174f9ee414a 135 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 136 if (retval)
mjr 2:c174f9ee414a 137 printf("IAP: Alignment violation\r\n");
mjr 2:c174f9ee414a 138 #endif
mjr 2:c174f9ee414a 139 return retval;
mjr 2:c174f9ee414a 140 }
mjr 2:c174f9ee414a 141
mjr 2:c174f9ee414a 142 /* Check if an area of flash memory is erased
mjr 2:c174f9ee414a 143 Returns error code or Success (in case of fully erased) */
mjr 2:c174f9ee414a 144 IAPCode FreescaleIAP::verify_erased(int address, unsigned int length) {
mjr 2:c174f9ee414a 145 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 146 printf("IAP: Verify erased at %x with length %d\r\n", address, length);
mjr 2:c174f9ee414a 147 #endif
mjr 2:c174f9ee414a 148
mjr 2:c174f9ee414a 149 if (check_align(address))
mjr 2:c174f9ee414a 150 return AlignError;
mjr 2:c174f9ee414a 151
mjr 2:c174f9ee414a 152 //Setup command
mjr 2:c174f9ee414a 153 FTFA->FCCOB0 = Read1s;
mjr 2:c174f9ee414a 154 FTFA->FCCOB1 = (address >> 16) & 0xFF;
mjr 2:c174f9ee414a 155 FTFA->FCCOB2 = (address >> 8) & 0xFF;
mjr 2:c174f9ee414a 156 FTFA->FCCOB3 = address & 0xFF;
mjr 2:c174f9ee414a 157 FTFA->FCCOB4 = (length >> 10) & 0xFF;
mjr 2:c174f9ee414a 158 FTFA->FCCOB5 = (length >> 2) & 0xFF;
mjr 2:c174f9ee414a 159 FTFA->FCCOB6 = 0;
mjr 2:c174f9ee414a 160
mjr 2:c174f9ee414a 161 run_command(FTFA);
mjr 2:c174f9ee414a 162
mjr 2:c174f9ee414a 163 IAPCode retval = check_error();
mjr 2:c174f9ee414a 164 if (retval == RuntimeError) {
mjr 2:c174f9ee414a 165 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 166 printf("IAP: Flash was not erased\r\n");
mjr 2:c174f9ee414a 167 #endif
mjr 2:c174f9ee414a 168 return EraseError;
mjr 2:c174f9ee414a 169 }
mjr 2:c174f9ee414a 170 return retval;
mjr 2:c174f9ee414a 171
mjr 2:c174f9ee414a 172 }
mjr 2:c174f9ee414a 173
mjr 2:c174f9ee414a 174 /* Check if an error occured
mjr 2:c174f9ee414a 175 Returns error code or Success*/
mjr 2:c174f9ee414a 176 IAPCode check_error(void) {
mjr 2:c174f9ee414a 177 if (FTFA->FSTAT & FTFA_FSTAT_FPVIOL_MASK) {
mjr 2:c174f9ee414a 178 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 179 printf("IAP: Protection violation\r\n");
mjr 2:c174f9ee414a 180 #endif
mjr 2:c174f9ee414a 181 return ProtectionError;
mjr 2:c174f9ee414a 182 }
mjr 2:c174f9ee414a 183 if (FTFA->FSTAT & FTFA_FSTAT_ACCERR_MASK) {
mjr 2:c174f9ee414a 184 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 185 printf("IAP: Flash access error\r\n");
mjr 2:c174f9ee414a 186 #endif
mjr 2:c174f9ee414a 187 return AccessError;
mjr 2:c174f9ee414a 188 }
mjr 2:c174f9ee414a 189 if (FTFA->FSTAT & FTFA_FSTAT_RDCOLERR_MASK) {
mjr 2:c174f9ee414a 190 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 191 printf("IAP: Collision error\r\n");
mjr 2:c174f9ee414a 192 #endif
mjr 2:c174f9ee414a 193 return CollisionError;
mjr 2:c174f9ee414a 194 }
mjr 2:c174f9ee414a 195 if (FTFA->FSTAT & FTFA_FSTAT_MGSTAT0_MASK) {
mjr 2:c174f9ee414a 196 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 197 printf("IAP: Runtime error\r\n");
mjr 2:c174f9ee414a 198 #endif
mjr 2:c174f9ee414a 199 return RuntimeError;
mjr 2:c174f9ee414a 200 }
mjr 2:c174f9ee414a 201 #ifdef IAPDEBUG
mjr 2:c174f9ee414a 202 printf("IAP: No error reported\r\n");
mjr 2:c174f9ee414a 203 #endif
mjr 2:c174f9ee414a 204 return Success;
mjr 2:c174f9ee414a 205 }