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 Sep 25 21:28:31 2015 +0000
Revision:
30:6e9902f06f48
Parent:
29:582472d0bc57
Child:
33:d832bcab089e
Use DMA for TLC5940 SPI transfer to reduce time interrupt handler (fixes problem with MMA8415Q freezing up).  All LedWiz flashing modes now fully supported.

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mjr 26:cb71c4af2912 1 // Pinscape Controller TLC5940 interface
mjr 26:cb71c4af2912 2 //
mjr 26:cb71c4af2912 3 // Based on Spencer Davis's mbed TLC5940 library. Adapted for the
mjr 26:cb71c4af2912 4 // KL25Z, and simplified to just the functions needed for this
mjr 26:cb71c4af2912 5 // application. In particular, this version doesn't include support
mjr 26:cb71c4af2912 6 // for dot correction programming or status input. This version also
mjr 26:cb71c4af2912 7 // uses a different approach for sending the grayscale data updates,
mjr 26:cb71c4af2912 8 // sending updates during the blanking interval rather than overlapping
mjr 26:cb71c4af2912 9 // them with the PWM cycle. This results in very slightly longer
mjr 26:cb71c4af2912 10 // blanking intervals when updates are pending, effectively reducing
mjr 26:cb71c4af2912 11 // the PWM "on" duty cycle (and thus the output brightness) by about
mjr 26:cb71c4af2912 12 // 0.3%. This shouldn't be perceptible to users, so it's a small
mjr 26:cb71c4af2912 13 // trade-off for the advantage gained, which is much better signal
mjr 26:cb71c4af2912 14 // stability when using multiple TLC5940s daisy-chained together.
mjr 26:cb71c4af2912 15 // I saw a lot of instability when using the overlapped approach,
mjr 26:cb71c4af2912 16 // which seems to be eliminated entirely when sending updates during
mjr 26:cb71c4af2912 17 // the blanking interval.
mjr 26:cb71c4af2912 18
mjr 26:cb71c4af2912 19
mjr 26:cb71c4af2912 20 #ifndef TLC5940_H
mjr 26:cb71c4af2912 21 #define TLC5940_H
mjr 26:cb71c4af2912 22
mjr 26:cb71c4af2912 23 #include "mbed.h"
mjr 26:cb71c4af2912 24 #include "FastPWM.h"
mjr 30:6e9902f06f48 25 #include "SimpleDMA.h"
mjr 26:cb71c4af2912 26
mjr 26:cb71c4af2912 27 /**
mjr 26:cb71c4af2912 28 * SPI speed used by the mbed to communicate with the TLC5940
mjr 26:cb71c4af2912 29 * The TLC5940 supports up to 30Mhz. It's best to keep this as
mjr 26:cb71c4af2912 30 * high as the microcontroller will allow, since a higher SPI
mjr 26:cb71c4af2912 31 * speed yields a faster grayscale data update. However, if
mjr 26:cb71c4af2912 32 * you have problems with unreliable signal transmission to the
mjr 26:cb71c4af2912 33 * TLC5940s, reducing this speed might help.
mjr 26:cb71c4af2912 34 *
mjr 26:cb71c4af2912 35 * The SPI clock must be fast enough that the data transmission
mjr 26:cb71c4af2912 36 * time for a full update is comfortably less than the blanking
mjr 26:cb71c4af2912 37 * cycle time. The grayscale refresh requires 192 bits per TLC5940
mjr 26:cb71c4af2912 38 * in the daisy chain, and each bit takes one SPI clock to send.
mjr 26:cb71c4af2912 39 * Our reference setup in the Pinscape controller allows for up to
mjr 26:cb71c4af2912 40 * 4 TLC5940s, so a full refresh cycle on a fully populated system
mjr 26:cb71c4af2912 41 * would be 768 SPI clocks. The blanking cycle is 4096 GSCLK cycles.
mjr 26:cb71c4af2912 42 *
mjr 26:cb71c4af2912 43 * t(blank) = 4096 * 1/GSCLK_SPEED
mjr 26:cb71c4af2912 44 * t(refresh) = 768 * 1/SPI_SPEED
mjr 26:cb71c4af2912 45 * Therefore: SPI_SPEED must be > 768/4096 * GSCLK_SPEED
mjr 26:cb71c4af2912 46 *
mjr 26:cb71c4af2912 47 * Since the SPI speed can be so high, and since we want to keep
mjr 26:cb71c4af2912 48 * the GSCLK speed relatively low, the constraint above simply
mjr 26:cb71c4af2912 49 * isn't a factor. E.g., at SPI=30MHz and GSCLK=500kHz,
mjr 26:cb71c4af2912 50 * t(blank) is 8192us and t(refresh) is 25us.
mjr 26:cb71c4af2912 51 */
mjr 26:cb71c4af2912 52 #define SPI_SPEED 3000000
mjr 26:cb71c4af2912 53
mjr 26:cb71c4af2912 54 /**
mjr 26:cb71c4af2912 55 * The rate at which the GSCLK pin is pulsed. This also controls
mjr 26:cb71c4af2912 56 * how often the reset function is called. The reset function call
mjr 26:cb71c4af2912 57 * rate is (1/GSCLK_SPEED) * 4096. The maximum reliable rate is
mjr 26:cb71c4af2912 58 * around 32Mhz. It's best to keep this rate as low as possible:
mjr 26:cb71c4af2912 59 * the higher the rate, the higher the refresh() call frequency,
mjr 26:cb71c4af2912 60 * so the higher the CPU load.
mjr 26:cb71c4af2912 61 *
mjr 26:cb71c4af2912 62 * The lower bound is probably dependent on the application. For
mjr 26:cb71c4af2912 63 * driving LEDs, the limiting factor is that lower rates will increase
mjr 26:cb71c4af2912 64 * visible flicker. 200 kHz seems to be a good lower bound for LEDs.
mjr 26:cb71c4af2912 65 * That provides about 48 cycles per second - that's about the same as
mjr 26:cb71c4af2912 66 * the 50 Hz A/C cycle rate in many countries, which was itself chosen
mjr 26:cb71c4af2912 67 * so that incandescent lights don't flicker. (This rate is a function
mjr 26:cb71c4af2912 68 * of human eye physiology, which has its own refresh cycle of sorts
mjr 26:cb71c4af2912 69 * that runs at about 50 Hz. If you're designing an LED system for
mjr 26:cb71c4af2912 70 * viewing by cats or drosophila, you might want to look into your
mjr 26:cb71c4af2912 71 * target species' eye physiology, since the persistence of vision
mjr 26:cb71c4af2912 72 * rate varies quite a bit from species to species.) Flicker tends to
mjr 26:cb71c4af2912 73 * be more noticeable in LEDs than in incandescents, since LEDs don't
mjr 26:cb71c4af2912 74 * have the thermal inertia of incandescents, so we use a slightly
mjr 26:cb71c4af2912 75 * higher default here. 500 kHz = 122 full grayscale cycles per
mjr 26:cb71c4af2912 76 * second = 122 reset calls per second (call every 8ms).
mjr 26:cb71c4af2912 77 */
mjr 26:cb71c4af2912 78 #define GSCLK_SPEED 500000
mjr 26:cb71c4af2912 79
mjr 26:cb71c4af2912 80 /**
mjr 26:cb71c4af2912 81 * This class controls a TLC5940 PWM driver IC.
mjr 26:cb71c4af2912 82 *
mjr 26:cb71c4af2912 83 * Using the TLC5940 class to control an LED:
mjr 26:cb71c4af2912 84 * @code
mjr 26:cb71c4af2912 85 * #include "mbed.h"
mjr 26:cb71c4af2912 86 * #include "TLC5940.h"
mjr 26:cb71c4af2912 87 *
mjr 26:cb71c4af2912 88 * // Create the TLC5940 instance
mjr 26:cb71c4af2912 89 * TLC5940 tlc(p7, p5, p21, p9, p10, p11, p12, 1);
mjr 26:cb71c4af2912 90 *
mjr 26:cb71c4af2912 91 * int main()
mjr 26:cb71c4af2912 92 * {
mjr 26:cb71c4af2912 93 * // Enable the first LED
mjr 26:cb71c4af2912 94 * tlc.set(0, 0xfff);
mjr 26:cb71c4af2912 95 *
mjr 26:cb71c4af2912 96 * while(1)
mjr 26:cb71c4af2912 97 * {
mjr 26:cb71c4af2912 98 * }
mjr 26:cb71c4af2912 99 * }
mjr 26:cb71c4af2912 100 * @endcode
mjr 26:cb71c4af2912 101 */
mjr 26:cb71c4af2912 102 class TLC5940
mjr 26:cb71c4af2912 103 {
mjr 26:cb71c4af2912 104 public:
mjr 26:cb71c4af2912 105 /**
mjr 26:cb71c4af2912 106 * Set up the TLC5940
mjr 26:cb71c4af2912 107 * @param SCLK - The SCK pin of the SPI bus
mjr 26:cb71c4af2912 108 * @param MOSI - The MOSI pin of the SPI bus
mjr 26:cb71c4af2912 109 * @param GSCLK - The GSCLK pin of the TLC5940(s)
mjr 26:cb71c4af2912 110 * @param BLANK - The BLANK pin of the TLC5940(s)
mjr 26:cb71c4af2912 111 * @param XLAT - The XLAT pin of the TLC5940(s)
mjr 26:cb71c4af2912 112 * @param nchips - The number of TLC5940s (if you are daisy chaining)
mjr 26:cb71c4af2912 113 */
mjr 26:cb71c4af2912 114 TLC5940(PinName SCLK, PinName MOSI, PinName GSCLK, PinName BLANK, PinName XLAT, int nchips)
mjr 26:cb71c4af2912 115 : spi(MOSI, NC, SCLK),
mjr 26:cb71c4af2912 116 gsclk(GSCLK),
mjr 26:cb71c4af2912 117 blank(BLANK),
mjr 26:cb71c4af2912 118 xlat(XLAT),
mjr 26:cb71c4af2912 119 nchips(nchips),
mjr 28:2097c6f8f2db 120 newGSData(true)
mjr 26:cb71c4af2912 121 {
mjr 30:6e9902f06f48 122 // Set initial output pin states - XLAT off, BLANK on (BLANK turns off
mjr 30:6e9902f06f48 123 // all of the outputs while we're setting up)
mjr 30:6e9902f06f48 124 xlat = 0;
mjr 30:6e9902f06f48 125 blank = 1;
mjr 30:6e9902f06f48 126
mjr 26:cb71c4af2912 127 // allocate the grayscale buffer
mjr 26:cb71c4af2912 128 gs = new unsigned short[nchips*16];
mjr 28:2097c6f8f2db 129 memset(gs, 0, nchips*16*sizeof(gs[0]));
mjr 26:cb71c4af2912 130
mjr 26:cb71c4af2912 131 // Configure SPI format and speed. Note that KL25Z ONLY supports 8-bit
mjr 26:cb71c4af2912 132 // mode. The TLC5940 nominally requires 12-bit data blocks for the
mjr 26:cb71c4af2912 133 // grayscale levels, but SPI is ultimately just a bit-level serial format,
mjr 26:cb71c4af2912 134 // so we can reformat the 12-bit blocks into 8-bit bytes to fit the
mjr 26:cb71c4af2912 135 // KL25Z's limits. This should work equally well on other microcontrollers
mjr 26:cb71c4af2912 136 // that are more flexible. The TLC5940 appears to require polarity/phase
mjr 26:cb71c4af2912 137 // format 0.
mjr 26:cb71c4af2912 138 spi.format(8, 0);
mjr 26:cb71c4af2912 139 spi.frequency(SPI_SPEED);
mjr 29:582472d0bc57 140
mjr 30:6e9902f06f48 141 // Allocate a DMA buffer. The transfer on each cycle is 192 bits per
mjr 30:6e9902f06f48 142 // chip = 24 bytes per chip.
mjr 30:6e9902f06f48 143 dmabuf = new char[nchips*24];
mjr 26:cb71c4af2912 144
mjr 30:6e9902f06f48 145 // Set up the Simple DMA interface object. We use the DMA controller to
mjr 30:6e9902f06f48 146 // send grayscale data updates to the TLC5940 chips. This lets the CPU
mjr 30:6e9902f06f48 147 // keep running other tasks while we send gs updates, and importantly
mjr 30:6e9902f06f48 148 // allows our blanking interrupt handler return almost immediately.
mjr 30:6e9902f06f48 149 // The DMA transfer is from our internal DMA buffer to SPI0, which is
mjr 30:6e9902f06f48 150 // the SPI controller physically connected to the TLC5940s.
mjr 30:6e9902f06f48 151 sdma.source(dmabuf, 1);
mjr 30:6e9902f06f48 152 sdma.destination(&(SPI0->D), 0, 8);
mjr 30:6e9902f06f48 153 sdma.trigger(Trigger_SPI0_TX);
mjr 30:6e9902f06f48 154 sdma.attach(this, &TLC5940::dmaDone);
mjr 30:6e9902f06f48 155
mjr 30:6e9902f06f48 156 // Enable DMA on SPI0. SimpleDMA doesn't do this for us; we have to
mjr 30:6e9902f06f48 157 // do it explicitly. This is just a matter of setting bit 5 (TXDMAE)
mjr 30:6e9902f06f48 158 // in the SPI controllers Control Register 2 (C2).
mjr 30:6e9902f06f48 159 SPI0->C2 |= 0x20; // set bit 5 = 0x20 = TXDMAE in SPI0 control register 2
mjr 30:6e9902f06f48 160
mjr 30:6e9902f06f48 161 // Configure the GSCLK output's frequency
mjr 26:cb71c4af2912 162 gsclk.period(1.0/GSCLK_SPEED);
mjr 30:6e9902f06f48 163 }
mjr 29:582472d0bc57 164
mjr 30:6e9902f06f48 165 // Start the clock running
mjr 29:582472d0bc57 166 void start()
mjr 29:582472d0bc57 167 {
mjr 26:cb71c4af2912 168 // Set up the first call to the reset function, which asserts BLANK to
mjr 26:cb71c4af2912 169 // end the PWM cycle and handles new grayscale data output and latching.
mjr 26:cb71c4af2912 170 // The original version of this library uses a timer to call reset
mjr 26:cb71c4af2912 171 // periodically, but that approach is somewhat problematic because the
mjr 26:cb71c4af2912 172 // reset function itself takes a small amount of time to run, so the
mjr 26:cb71c4af2912 173 // *actual* cycle is slightly longer than what we get from counting
mjr 26:cb71c4af2912 174 // GS clocks. Running reset on a timer therefore causes the calls to
mjr 26:cb71c4af2912 175 // slip out of phase with the actual full cycles, which causes
mjr 26:cb71c4af2912 176 // premature blanking that shows up as visible flicker. To get the
mjr 26:cb71c4af2912 177 // reset cycle to line up exactly with a full PWM cycle, it works
mjr 26:cb71c4af2912 178 // better to set up a new timer on each cycle, *after* we've finished
mjr 26:cb71c4af2912 179 // with the somewhat unpredictable overhead of the interrupt handler.
mjr 26:cb71c4af2912 180 // This ensures that we'll get much closer to exact alignment of the
mjr 26:cb71c4af2912 181 // cycle phase, and in any case the worst that happens is that some
mjr 26:cb71c4af2912 182 // cycles are very slightly too long or short (due to imperfections
mjr 26:cb71c4af2912 183 // in the timer clock vs the PWM clock that determines the GSCLCK
mjr 26:cb71c4af2912 184 // output to the TLC5940), which is far less noticeable than a
mjr 26:cb71c4af2912 185 // constantly rotating phase misalignment.
mjr 26:cb71c4af2912 186 reset_timer.attach(this, &TLC5940::reset, (1.0/GSCLK_SPEED)*4096.0);
mjr 26:cb71c4af2912 187 }
mjr 26:cb71c4af2912 188
mjr 26:cb71c4af2912 189 ~TLC5940()
mjr 26:cb71c4af2912 190 {
mjr 26:cb71c4af2912 191 delete [] gs;
mjr 30:6e9902f06f48 192 delete [] dmabuf;
mjr 26:cb71c4af2912 193 }
mjr 26:cb71c4af2912 194
mjr 26:cb71c4af2912 195 /**
mjr 26:cb71c4af2912 196 * Set the next chunk of grayscale data to be sent
mjr 26:cb71c4af2912 197 * @param data - Array of 16 bit shorts containing 16 12 bit grayscale data chunks per TLC5940
mjr 26:cb71c4af2912 198 * @note These must be in intervals of at least (1/GSCLK_SPEED) * 4096 to be sent
mjr 26:cb71c4af2912 199 */
mjr 26:cb71c4af2912 200 void set(int idx, unsigned short data)
mjr 26:cb71c4af2912 201 {
mjr 26:cb71c4af2912 202 // store the data, and flag the pending update for the interrupt handler to carry out
mjr 26:cb71c4af2912 203 gs[idx] = data;
mjr 30:6e9902f06f48 204 newGSData = true;
mjr 26:cb71c4af2912 205 }
mjr 26:cb71c4af2912 206
mjr 26:cb71c4af2912 207 private:
mjr 26:cb71c4af2912 208 // current level for each output
mjr 26:cb71c4af2912 209 unsigned short *gs;
mjr 26:cb71c4af2912 210
mjr 30:6e9902f06f48 211 // Simple DMA interface object
mjr 30:6e9902f06f48 212 SimpleDMA sdma;
mjr 30:6e9902f06f48 213
mjr 30:6e9902f06f48 214 // DMA transfer buffer. Each time we have data to transmit to the TLC5940 chips,
mjr 30:6e9902f06f48 215 // we format the data into this buffer exactly as it will go across the wire, then
mjr 30:6e9902f06f48 216 // hand the buffer to the DMA controller to move through the SPI port.
mjr 30:6e9902f06f48 217 char *dmabuf;
mjr 30:6e9902f06f48 218
mjr 26:cb71c4af2912 219 // SPI port - only MOSI and SCK are used
mjr 26:cb71c4af2912 220 SPI spi;
mjr 26:cb71c4af2912 221
mjr 26:cb71c4af2912 222 // use a PWM out for the grayscale clock - this provides a stable
mjr 26:cb71c4af2912 223 // square wave signal without consuming CPU
mjr 26:cb71c4af2912 224 FastPWM gsclk;
mjr 26:cb71c4af2912 225
mjr 26:cb71c4af2912 226 // Digital out pins used for the TLC5940
mjr 26:cb71c4af2912 227 DigitalOut blank;
mjr 26:cb71c4af2912 228 DigitalOut xlat;
mjr 26:cb71c4af2912 229
mjr 26:cb71c4af2912 230 // number of daisy-chained TLC5940s we're controlling
mjr 26:cb71c4af2912 231 int nchips;
mjr 26:cb71c4af2912 232
mjr 26:cb71c4af2912 233 // Timeout to end each PWM cycle. This is a one-shot timer that we reset
mjr 26:cb71c4af2912 234 // on each cycle.
mjr 26:cb71c4af2912 235 Timeout reset_timer;
mjr 26:cb71c4af2912 236
mjr 26:cb71c4af2912 237 // Has new GS/DC data been loaded?
mjr 26:cb71c4af2912 238 volatile bool newGSData;
mjr 26:cb71c4af2912 239
mjr 26:cb71c4af2912 240 // Function to reset the display and send the next chunks of data
mjr 26:cb71c4af2912 241 void reset()
mjr 26:cb71c4af2912 242 {
mjr 30:6e9902f06f48 243 // start the blanking cycle
mjr 30:6e9902f06f48 244 startBlank();
mjr 26:cb71c4af2912 245
mjr 26:cb71c4af2912 246 // If we have new GS data, send it now
mjr 30:6e9902f06f48 247 if (true)
mjr 26:cb71c4af2912 248 {
mjr 26:cb71c4af2912 249 // Send the new grayscale data.
mjr 26:cb71c4af2912 250 //
mjr 26:cb71c4af2912 251 // Note that ideally, we'd do this during the new PWM cycle
mjr 26:cb71c4af2912 252 // rather than during the blanking interval. The TLC5940 is
mjr 26:cb71c4af2912 253 // specifically designed to allow this. However, in my testing,
mjr 26:cb71c4af2912 254 // I found that sending new data during the PWM cycle was
mjr 26:cb71c4af2912 255 // unreliable - it seemed to cause a fair amount of glitching,
mjr 26:cb71c4af2912 256 // which as far as I can tell is signal noise coming from
mjr 26:cb71c4af2912 257 // crosstalk between the grayscale clock signal and the
mjr 26:cb71c4af2912 258 // SPI signal. This seems to be a common problem with
mjr 26:cb71c4af2912 259 // daisy-chained TLC5940s. It can in principle be solved with
mjr 26:cb71c4af2912 260 // careful high-speed circuit design (good ground planes,
mjr 26:cb71c4af2912 261 // short leads, decoupling capacitors), and indeed I was able
mjr 26:cb71c4af2912 262 // to improve stability to some extent with circuit tweaks,
mjr 26:cb71c4af2912 263 // but I wasn't able to eliminate it entirely. Moving the
mjr 26:cb71c4af2912 264 // data refresh into the blanking interval, on the other
mjr 26:cb71c4af2912 265 // hand, seems to entirely eliminate any instability.
mjr 26:cb71c4af2912 266 //
mjr 30:6e9902f06f48 267 // update() will format the current grayscale data into our
mjr 30:6e9902f06f48 268 // DMA transfer buffer and kick off the DMA transfer, then
mjr 30:6e9902f06f48 269 // return. At that point we can return from the interrupt,
mjr 30:6e9902f06f48 270 // but WITHOUT ending the blanking cycle - we want to keep
mjr 30:6e9902f06f48 271 // blanking the outputs until the DMA transfer finishes. When
mjr 30:6e9902f06f48 272 // the transfer is complete, the DMA controller will fire an
mjr 30:6e9902f06f48 273 // interrupt that will trigger our dmaDone() callback, at
mjr 30:6e9902f06f48 274 // which point we'll finally complete the blanking cycle and
mjr 30:6e9902f06f48 275 // start a new grayscale cycle.
mjr 26:cb71c4af2912 276 update();
mjr 26:cb71c4af2912 277
mjr 26:cb71c4af2912 278 // the chips are now in sync with our data, so we have no more
mjr 26:cb71c4af2912 279 // pending update
mjr 26:cb71c4af2912 280 newGSData = false;
mjr 30:6e9902f06f48 281 }
mjr 30:6e9902f06f48 282 else
mjr 30:6e9902f06f48 283 {
mjr 30:6e9902f06f48 284 // no new grayscale data - just end the blanking cycle without
mjr 30:6e9902f06f48 285 // a new XLAT
mjr 30:6e9902f06f48 286 endBlank(false);
mjr 30:6e9902f06f48 287 }
mjr 30:6e9902f06f48 288 }
mjr 30:6e9902f06f48 289
mjr 30:6e9902f06f48 290 void startBlank()
mjr 30:6e9902f06f48 291 {
mjr 30:6e9902f06f48 292 // turn off the grayscale clock, and assert BLANK to end the grayscale cycle
mjr 30:6e9902f06f48 293 gsclk.write(0);
mjr 30:6e9902f06f48 294 blank = 1;
mjr 30:6e9902f06f48 295 }
mjr 26:cb71c4af2912 296
mjr 30:6e9902f06f48 297 void endBlank(bool needxlat)
mjr 30:6e9902f06f48 298 {
mjr 30:6e9902f06f48 299 if (needxlat)
mjr 30:6e9902f06f48 300 {
mjr 26:cb71c4af2912 301 // latch the new data while we're still blanked
mjr 26:cb71c4af2912 302 xlat = 1;
mjr 26:cb71c4af2912 303 xlat = 0;
mjr 26:cb71c4af2912 304 }
mjr 26:cb71c4af2912 305
mjr 26:cb71c4af2912 306 // end the blanking interval and restart the grayscale clock
mjr 26:cb71c4af2912 307 blank = 0;
mjr 26:cb71c4af2912 308 gsclk.write(.5);
mjr 26:cb71c4af2912 309
mjr 26:cb71c4af2912 310 // set up the next blanking interrupt
mjr 26:cb71c4af2912 311 reset_timer.attach(this, &TLC5940::reset, (1.0/GSCLK_SPEED)*4096.0);
mjr 26:cb71c4af2912 312 }
mjr 26:cb71c4af2912 313
mjr 26:cb71c4af2912 314 void update()
mjr 26:cb71c4af2912 315 {
mjr 30:6e9902f06f48 316 // Send new grayscale data to the TLC5940 chips.
mjr 30:6e9902f06f48 317 //
mjr 30:6e9902f06f48 318 // To do this, we set up our DMA buffer with the bytes formatted exactly
mjr 30:6e9902f06f48 319 // as they will go across the wire, then kick off the transfer request with
mjr 30:6e9902f06f48 320 // the DMA controller. We can then return from the interrupt and continue
mjr 30:6e9902f06f48 321 // with other tasks while the DMA hardware handles the transfer for us.
mjr 30:6e9902f06f48 322 // When the transfer is completed, the DMA controller will fire an
mjr 30:6e9902f06f48 323 // interrupt, which will call our interrupt handler, which will finish
mjr 30:6e9902f06f48 324 // the blanking cycle.
mjr 30:6e9902f06f48 325 //
mjr 30:6e9902f06f48 326 // The serial format orders the outputs from last to first (output #15 on
mjr 30:6e9902f06f48 327 // the last chip in the daisy-chain to output #0 on the first chip). For
mjr 30:6e9902f06f48 328 // each output, we send 12 bits containing the grayscale level (0 = fully
mjr 30:6e9902f06f48 329 // off, 0xFFF = fully on). Bit order is most significant bit first.
mjr 26:cb71c4af2912 330 //
mjr 26:cb71c4af2912 331 // The KL25Z SPI can only send in 8-bit increments, so we need to divvy up
mjr 26:cb71c4af2912 332 // the 12-bit outputs into 8-bit bytes. Each pair of 12-bit outputs adds up
mjr 26:cb71c4af2912 333 // to 24 bits, which divides evenly into 3 bytes, so send each pairs of
mjr 26:cb71c4af2912 334 // outputs as three bytes:
mjr 26:cb71c4af2912 335 //
mjr 26:cb71c4af2912 336 // [ element i+1 bits ] [ element i bits ]
mjr 26:cb71c4af2912 337 // 11 10 9 8 7 6 5 4 3 2 1 0 11 10 9 8 7 6 5 4 3 2 1 0
mjr 26:cb71c4af2912 338 // [ first byte ] [ second byte ] [ third byte ]
mjr 30:6e9902f06f48 339 for (int i = (16 * nchips) - 2, dst = 0 ; i >= 0 ; i -= 2)
mjr 26:cb71c4af2912 340 {
mjr 26:cb71c4af2912 341 // first byte - element i+1 bits 4-11
mjr 30:6e9902f06f48 342 dmabuf[dst++] = (((gs[i+1] & 0xFF0) >> 4) & 0xff);
mjr 26:cb71c4af2912 343
mjr 26:cb71c4af2912 344 // second byte - element i+1 bits 0-3, then element i bits 8-11
mjr 30:6e9902f06f48 345 dmabuf[dst++] = ((((gs[i+1] & 0x00F) << 4) | ((gs[i] & 0xF00) >> 8)) & 0xFF);
mjr 26:cb71c4af2912 346
mjr 26:cb71c4af2912 347 // third byte - element i bits 0-7
mjr 30:6e9902f06f48 348 dmabuf[dst++] = (gs[i] & 0x0FF);
mjr 26:cb71c4af2912 349 }
mjr 30:6e9902f06f48 350
mjr 30:6e9902f06f48 351 // Start the DMA transfer
mjr 30:6e9902f06f48 352 sdma.start(nchips*24);
mjr 26:cb71c4af2912 353 }
mjr 30:6e9902f06f48 354
mjr 30:6e9902f06f48 355 // Interrupt handler for DMA completion. The DMA controller calls this
mjr 30:6e9902f06f48 356 // when it finishes with the transfer request we set up above. When the
mjr 30:6e9902f06f48 357 // transfer is done, we simply end the blanking cycle and start a new
mjr 30:6e9902f06f48 358 // grayscale cycle.
mjr 30:6e9902f06f48 359 void dmaDone()
mjr 30:6e9902f06f48 360 {
mjr 30:6e9902f06f48 361 // when the DMA transfer is finished, start the next grayscale cycle
mjr 30:6e9902f06f48 362 endBlank(true);
mjr 30:6e9902f06f48 363 }
mjr 30:6e9902f06f48 364
mjr 26:cb71c4af2912 365 };
mjr 26:cb71c4af2912 366
mjr 26:cb71c4af2912 367 #endif