Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

# Give Sign Assembly Instructions #

These instructions outline the steps for assembling the GIVE sign.

## Inventory ##



The give sign consists of

  1. Four base plates (one for each letter)
  2. Four Letters (G,I,V,E) with LEDs attached
  3. Spark Core and Circuit Board (should be attached to "G" base plate)
  4. 12V/5A DC Power Supply with 2.1mm male plug.
  5. Spare 4 x 1/2 panhead screws in case they are needed to secure LEDs (not pictured)

## Circuit Layout ##

The Spark Core is inserted in a socket on a circuit board that is inside the blue enclosure on the "G" base board. You can flip the clips out to remove the lid. YOU DO NOT NEED TO OPEN THE ENCLOSURE AS PART OF NORMAL OPERATION. You only need to open the enclosure to perform actions on the Spark Core.


  1. There is a schematic of the circuit at the end of this document: Circuit Schematic

## Tasks ##

The remainder of this document walks you through a number of tasks.

  1. Assembling the Sign
  2. Installing the Spark Core Windows USB Driver
  3. Installing the Spark-CLI
  4. Configuring WiFi for a Pre-Programmed Spark Core
  5. Flashing the LEDDOTS Sketch
  6. Identifying your Spark Core
  7. Testing the Spark Core

## Assembling the Sign ##

The sign assembly is pretty simple. Basically, just connect the base boards together, then connect the letters to the base boards, and finally connect the cables up. Easy!

FYI, a number of the pictures were taken under a shade tree. Apologies for the poor picture quality.

  1. Identify each base board by looking on the bottom:


  2. Connect the base boards in order (G,I,V,E) using the dowels and holes:


  3. Place each letter on it's corresponding base board, again using the dowels and holes:

    Note: the holes on the base board are off center and CLOSER to the FRONT. So make sure the front of the letter (with the LED bulbs showing) is closer to the front of the base board.



  4. When the bases and Letters are all attached it should look something like this (minus the lit LEDs):


  5. As you work with the connectors, make sure the handle them by the white plastic parts. DO NOT PULL THE WIRES GOING INTO THE CONNECTORS. They can be pulled out of the connector.


  6. Connect the NUMBERED connectors in the back. ("0","1","2","3")

    Note: The "letter" connectors ("A","B","C","D" and "E") are connectors within a letter and do not need to be messed with unless there is a problem. As mentioned though, if you do feel a need to disconnect and re-connect one, please take care to handle them only by the white plastic of the connector.


    • 0: Goes from the Spark Core enclosure to the corresponding "0" connector on the "tongue" of the letter "G". Route the wires from the Spark Core enclosure through the LED strip wires to help keep it in place.

    • 1: Goes from the cable leaving the "G" and to the corresponding connector at the bottom of the letter "I"

    • 2: Goes from the "I" to the corresponding connector at the bottom of the letter "V"

    • 3: Goes from the "V" to the bottom of the letter "E"

  7. When you are done connecting the wires, attempt to clean the wires up some by tucking them in where you can. Seeing the wires is part of the "character" of the sign though, so don't worry about trying to hide them altogether.

  8. The only step that remains is to connect the power supply to the Spark Core. You can wait to do this until you have configured the Spark Core as described in the following steps.

## Installing the Spark Core Windows USB Driver ##


The steps covered here are specific to configuring a Spark Core using the Command Line Interface on a Windows machine. If you will be working with the spark core from a Mac or Linux box, you can can refer to the online documentation for configuring a Spark Core.

  1. Before you work with the Spark Core on a Windows Machine, you will need to install the Windows USB Driver. First, you'll need to download the driver from . Download the .zip file and extract it to a folder on your computer.

    Note: You can also refer to the documentation for Connecting to the Spark Core via USB

  2. Connect the Spark Core to your computer via the USB. ***Note that due to some poor planning during the circuit board layout, the capacitors will likely prevent you from connecting the cable. You can tilt the Spark Core up slightly in it's socket (or remove it all together) to make the USB connection.***:


  3. Ensure that the Spark Core is in "Listening Mode" by confirming that the RGB LED on the board is flashing blue. If it isn't, hold the "MODE" button on the Spark Core for about three seconds until it begins flashing blue:


  4. Open your computer's "Device Manager". Under "Other Devices" you should see the "Spark Core with WiFi". Right click on the "Spark Core with WiFi" and select "Update Driver Software..." from the pop-up menu:

    Note: If you are doing this from a Windows 10 preview machine, the device may not show up under "Other Devices" but rather under "Ports" with a unique name like "USB Port on COM4" (your name may vary). If you see that, update the driver on that device as described below.


  5. Select the "Browse my computer for driver software" option:


  6. Then browse to the folder where you extracted the file you downloaded previously with the Windows USB driver. (There should be a spark_core.inf and file in the folder), then click "Next":


  7. In the "Windows Security" window, click "Install" to install the driver:


  8. You should see a confirmation that the "Spark Core with Wifi and Arduino Compatability" driver was installed. Click "Close" to close the window.


  9. Finally, back in the "Device Manager" you should see the Spark Core listed under "Ports":


  10. At this point, if you were to use a terminal program (Like PuTTY) you could connect serially to the Spark Core via the COM port listed (COM4 in this case) and issue some commands. However, the Spark Command Line Interface (Spark-CLI) offers significantly more functionality, so we'll use that.

## Installing the Spark-CLI ##


The Spark Command Line Interface (Spark-CLI) is a Node.js application that allows you to manage your spark cores, and the code that runs on them. The Spark-CLI source is available from GitHub at and you can read the docs here:

  1. First, ensure that you have Node.js installed. You can install it from here:

    Note: It helps if you let the installer install the Node Package Manager (npm) as well as to add Node to the system path. If you add node the path, you can use node from any Windows Command Prompt.

  2. To install the Spark-CLI using node, you can open a Node.js Command Prompt (or any command administrator prompt if you allowed the Node.js installer to add Node to the path) and issue the following command:

    npm install -g spark-cli


  3. This documentation was written with the Spark-CLI version 0.4.1. If you already have the Spark-CLI installed, you can determine its version using the following command:

    npm list -g spark-cli


  4. In addition, you can always upgrade to the latest version of the Spark-CLI using the command:

    npm update -g spark-cli

## Configuring WiFi for a Pre-Programmed Spark Core ##


If you received the GIVE sign with a Spark Core that has been pre-programmed, you only need to configure the Spark Core to connect to your local WiFi.

  1. Connect the Spark Core to your PC via USB, and place the Spark Core into "Listening Mode" by holding down the "Mode" button on the spark core until the RGB LED flashes blue repeatedly.

  2. Open a Node Command Prompt, and issue the following command

    spark setup wifi

  3. Follow the prompts to configure the Spark Core for your WiFi network.

    Note: Some MiFi wifi hot spots (like my Verizon MiFi), and other networks take the user to a start screen on the first load. If connecting to your mifi, the Spark might fail to connect the first time. Try cycling the power on your Spark Core to get it to restart and connect. If the WiFi network you are connecting to requires a browser based authentication process, you won't be able to connect your Spark Core to it. You must know the WiFi SSID, Security Mode, and Password.


  4. When the WiFi setup is complete, you should see the RGB LED on the Spark Core "Breathing Cyan". This means that it should have a cyan color (light blue) and should repeatedly fade in and out.

## Flashing the LEDDOTS Sketch ##

If your Spark Core has not been claimed, you need to do that first.

If the Spark Core you want to claim has already been claimed by another account, you will have to have that account owner remove the core before you can claim it:

spark core remove <core name / core id>

If your Spark Core is new, or is available to be claimed you can use the Spark-CLI commands:

spark cloud login
spark setup

You can find instructions for connecting and claiming a core here:

The "LEDDOTS" sketch (app) we use below is used to drive a spark core that is connected to a string of 30mm LED Dots from Adafruit ( These LED strips provide are a powerful way to create extremely active and colorful visualizations. The LEDs are controlled using a WS2801 chip. It allows a string of LEDs (54 in the case of the GIVE Sign) to be strung together and controlled with only two pins on a Microcontroller. Super cool!

The sketch uses a modified version of the Adafruit_WS2801 library. The code has been modified to work with the Spark Core: . The modified version of the code was provided via GitHub by Technobly

The LEDDOTS sketch has two methods, showPercent(string) and setDelay(string). The setDelay(string) method is used really more for debugging purposes. It sets the delay (ms) used by the various animations. Setting the delay lower speeds up the animations. However, the default delay is only 5ms so you can't make them much faster.

The showPercent(string) function is the main purpose of the sketch. It takes in a string command that has a single integer in it representing a percentange between 0 and 100.

It then uses that displays that percentage as a number of dots in the LED dot stream. 0% = 0 dots, 50% = 27 dots, 100% = 54 dots. The dots fill with the following pattern:

Note: the following picture was taken when the percentage was 48% or 26 dots (rounded up).


The color of the "filled" dots will be based on the percentage (note, this may change in the future):

  • 00 - 92% = Red

  • 93 - 97% = Yellow

  • 98 - 100% = Green

The Spark Core that is shipped with the GIVE sign should already have the LEDDOTS sketch flashed on it, however if you need to program another Spark Core, you can follow these steps:

  1. Login to the Spark Build web development environment with your Spark.IO credentials (the same credentials you used to claim your Spark Core):

  2. If this isn't your first sketch, clik the "CREATE NEW APP" button:


  3. When prompted, enter "LEDDOTS" as the name for your new app:


  4. Paste the following code into the code window:

    Note: This is a big code piece. You can also just open the source file at LEDDOTS.ino. Also, while the code file has the arduino ∗.ino extension, you CAN NOT open and compile this in the Arduino IDE.

    // SPARK CORE Adafruit_WS2801 LIBRARY & EXAMPLE  //
    // Copy this into a new application at:          //
    // and go nuts!       //
    // Read comments in APPLICATION.CPP section for  //
    // Hookup details!                               //
    // Technobly / BDub - Jan 9th, 2014              //
    // NOTE: Library is kind of hacked up at the moment
    // Look for 4 '////' for all areas commented out
    // Will clean up after verified working!
    // YES, I'M SHOUTING! xD
    // Code From:
    /* ========================== Adafruit_WS2801.h =========================== */
    ///#if (ARDUINO >= 100)
    //// #include <Arduino.h>
    /// #include <WProgram.h>
    /// #include <pins_arduino.h>
    // Not all LED pixels are RGB order; 36mm type expects GRB data.
    // Optional flag to constructors indicates data order (default if
    // unspecified is RGB).  As long as setPixelColor/getPixelColor are
    // used, other code can always treat 'packed' colors as RGB; the
    // library will handle any required translation internally.
    #define WS2801_RGB 0
    #define WS2801_GRB 1
    #define boolean bool
    class Adafruit_WS2801 {
      // Configurable pins:
      Adafruit_WS2801(uint16_t n, uint8_t dpin, uint8_t cpin, uint8_t order=WS2801_RGB);
      Adafruit_WS2801(uint16_t x, uint16_t y, uint8_t dpin, uint8_t cpin, uint8_t order=WS2801_RGB);
      // Use SPI hardware; specific pins only:
      Adafruit_WS2801(uint16_t n, uint8_t order=WS2801_RGB);
      // Empty constructor; init pins/strand length/data order later:
      // Release memory (as needed):
    	 setPixelColor(uint16_t n, uint8_t r, uint8_t g, uint8_t b),
    	 setPixelColor(uint16_t n, uint32_t c),
    	 setPixelColor(uint16_t x, uint16_t y, uint8_t r, uint8_t g, uint8_t b),
    	 setPixelColor(uint16_t x, uint16_t y, uint32_t c),
    	 updatePins(uint8_t dpin, uint8_t cpin), // Change pins, configurable
    	 updatePins(void), // Change pins, hardware SPI
    	 updateLength(uint16_t n), // Change strand length
    	 updateOrder(uint8_t order); // Change data order
    	 getPixelColor(uint16_t n);
    	 width,     // used with matrix mode
    	 height;    // used with matrix mode
    	 *pixels,   // Holds color values for each LED (3 bytes each)
    	 rgb_order, // Color order; RGB vs GRB (or others, if needed in future)
    	 clkpin    , datapin,     // Clock & data pin numbers
    	 clkpinmask, datapinmask; // Clock & data PORT bitmasks
      volatile uint8_t
    	 *clkport  , *dataport;   // Clock & data PORT registers
    	 alloc(uint16_t n),
    	 hardwareSPI, // If 'true', using hardware SPI
    	 begun;       // If 'true', begin() method was previously invoked
    /* ========================== Adafruit_WS2801.cpp =========================== */
    ////#include "SPI.h"
    ////#include "Adafruit_WS2801.h"
    // Example to control WS2801-based RGB LED Modules in a strand or strip
    // Written by Adafruit - MIT license
    // Constructor for use with hardware SPI (specific clock/data pins):
    Adafruit_WS2801::Adafruit_WS2801(uint16_t n, uint8_t order) {
      rgb_order = order;
    // Constructor for use with arbitrary clock/data pins:
    Adafruit_WS2801::Adafruit_WS2801(uint16_t n, uint8_t dpin, uint8_t cpin, uint8_t order) {
      rgb_order = order;
      updatePins(dpin, cpin);
    // Constructor for use with a matrix configuration, specify w, h for size of matrix
    // assumes configuration where string starts at coordinate 0,0 and continues to w-1,0, w-1,1
    // and on to 0,1, 0,2 and on to w-1,2 and so on. Snaking back and forth till the end.
    // other function calls with provide access to pixels via an x,y coordinate system
    Adafruit_WS2801::Adafruit_WS2801(uint16_t w, uint16_t h, uint8_t dpin, uint8_t cpin, uint8_t order) {
      rgb_order = order;
      alloc(w * h);
      width = w;
      height = h;
      updatePins(dpin, cpin);
    // Allocate 3 bytes per pixel, init to RGB 'off' state:
    void Adafruit_WS2801::alloc(uint16_t n) {
      begun   = false;
      numLEDs = ((pixels = (uint8_t *)calloc(n, 3)) != NULL) ? n : 0;
    // via Michael Vogt/neophob: empty constructor is used when strand length
    // isn't known at compile-time; situations where program config might be
    // read from internal flash memory or an SD card, or arrive via serial
    // command.  If using this constructor, MUST follow up with updateLength()
    // and updatePins() to establish the strand length and output pins!
    // Also, updateOrder() to change RGB vs GRB order (RGB is default).
    Adafruit_WS2801::Adafruit_WS2801(void) {
      begun     = false;
      numLEDs   = 0;
      pixels    = NULL;
      rgb_order = WS2801_RGB;
      updatePins(); // Must assume hardware SPI until pins are set
    // Release memory (as needed):
    Adafruit_WS2801::~Adafruit_WS2801(void) {
      if (pixels != NULL) {
    // Activate hard/soft SPI as appropriate:
    void Adafruit_WS2801::begin(void) {
      if(hardwareSPI == true) {
      } else {
    	 pinMode(datapin, OUTPUT);
    	 pinMode(clkpin , OUTPUT);
      begun = true;
    // Change pin assignments post-constructor, switching to hardware SPI:
    void Adafruit_WS2801::updatePins(void) {
      hardwareSPI = true;
      datapin     = clkpin = 0;
      // If begin() was previously invoked, init the SPI hardware now:
      if(begun == true) startSPI();
      // Otherwise, SPI is NOT initted until begin() is explicitly called.
      // Note: any prior clock/data pin directions are left as-is and are
      // NOT restored as inputs!
    // Change pin assignments post-constructor, using arbitrary pins:
    void Adafruit_WS2801::updatePins(uint8_t dpin, uint8_t cpin) {
      if(begun == true) { // If begin() was previously invoked...
    	 // If previously using hardware SPI, turn that off:
    	 if(hardwareSPI == true) SPI.end();
    	 // Regardless, now enable output on 'soft' SPI pins:
    	 pinMode(dpin, OUTPUT);
    	 pinMode(cpin, OUTPUT);
      } // Otherwise, pins are not set to outputs until begin() is called.
      // Note: any prior clock/data pin directions are left as-is and are
      // NOT restored as inputs!
      hardwareSPI = false;
      datapin     = dpin;
      clkpin      = cpin;
      ////clkport     = portOutputRegister(digitalPinToPort(cpin));
      ////clkpinmask  = digitalPinToBitMask(cpin);
      ////dataport    = portOutputRegister(digitalPinToPort(dpin));
      ////datapinmask = digitalPinToBitMask(dpin);
    // Enable SPI hardware and set up protocol details:
    void Adafruit_WS2801::startSPI(void) {
    	 SPI.setClockDivider(SPI_CLOCK_DIV128); // 1 MHz max, else flicker (set to 72MHz/128 = 562.5kHz)
    uint16_t Adafruit_WS2801::numPixels(void) {
      return numLEDs;
    // Change strand length (see notes with empty constructor, above):
    void Adafruit_WS2801::updateLength(uint16_t n) {
      if(pixels != NULL) free(pixels); // Free existing data (if any)
      // Allocate new data -- note: ALL PIXELS ARE CLEARED
      numLEDs = ((pixels = (uint8_t *)calloc(n, 3)) != NULL) ? n : 0;
      // 'begun' state does not change -- pins retain prior modes
    // Change RGB data order (see notes with empty constructor, above):
    void Adafruit_WS2801::updateOrder(uint8_t order) {
      rgb_order = order;
      // Existing LED data, if any, is NOT reformatted to new data order.
      // Calling function should clear or fill pixel data anew.
    void Adafruit_WS2801::show(void) {
      uint16_t i, nl3 = numLEDs * 3; // 3 bytes per LED
      ////uint8_t  bit;
      // Write 24 bits per pixel:
      ////if(hardwareSPI) {
    	 for(i=0; i<nl3; i++) {
    		////while(!(SPSR & (1<<SPIF)));
    	 /*} else {
    	 for(i=0; i<nl3; i++ ) {
    		for(bit=0x80; bit; bit >>= 1) {
    		  if(pixels[i] & bit) *dataport |=  datapinmask;
    		  else                *dataport &= ~datapinmask;
    		  *clkport |=  clkpinmask;
    		  *clkport &= ~clkpinmask;
      delay(1); // Data is latched by holding clock pin low for 1 millisecond
    // Set pixel color from separate 8-bit R, G, B components:
    void Adafruit_WS2801::setPixelColor(uint16_t n, uint8_t r, uint8_t g, uint8_t b) {
      if(n < numLEDs) { // Arrays are 0-indexed, thus NOT '<='
    	 uint8_t *p = &pixels[n * 3];
    	 // See notes later regarding color order
    	 if(rgb_order == WS2801_RGB) {
    		*p++ = r;
    		*p++ = g;
    	 } else {
    		*p++ = g;
    		*p++ = r;
    	 *p++ = b;
    // Set pixel color from separate 8-bit R, G, B components using x,y coordinate system:
    void Adafruit_WS2801::setPixelColor(uint16_t x, uint16_t y, uint8_t r, uint8_t g, uint8_t b) {
      boolean evenRow = ((y % 2) == 0);
      // calculate x offset first
      uint16_t offset = x % width;
      if (!evenRow) {
    	 offset = (width-1) - offset;
      // add y offset
      offset += y * width;
      setPixelColor(offset, r, g, b);
    // Set pixel color from 'packed' 32-bit RGB value:
    void Adafruit_WS2801::setPixelColor(uint16_t n, uint32_t c) {
      if(n < numLEDs) { // Arrays are 0-indexed, thus NOT '<='
    	 uint8_t *p = &pixels[n * 3];
    	 // To keep the show() loop as simple & fast as possible, the
    	 // internal color representation is native to different pixel
    	 // types.  For compatibility with existing code, 'packed' RGB
    	 // values passed in or out are always 0xRRGGBB order.
    	 if(rgb_order == WS2801_RGB) {
    		*p++ = c >> 16; // Red
    		*p++ = c >>  8; // Green
    	 } else {
    		*p++ = c >>  8; // Green
    		*p++ = c >> 16; // Red
    	 *p++ = c;         // Blue
    // Set pixel color from 'packed' 32-bit RGB value using x,y coordinate system:
    void Adafruit_WS2801::setPixelColor(uint16_t x, uint16_t y, uint32_t c) {
      boolean evenRow = ((y % 2) == 0);
      // calculate x offset first
      uint16_t offset = x % width;
      if (!evenRow) {
    	 offset = (width-1) - offset;
      // add y offset
      offset += y * width;
      setPixelColor(offset, c);
    // Query color from previously-set pixel (returns packed 32-bit RGB value)
    uint32_t Adafruit_WS2801::getPixelColor(uint16_t n) {
      if(n < numLEDs) {
    	 uint16_t ofs = n * 3;
    	 // To keep the show() loop as simple & fast as possible, the
    	 // internal color representation is native to different pixel
    	 // types.  For compatibility with existing code, 'packed' RGB
    	 // values passed in or out are always 0xRRGGBB order.
    	 return (rgb_order == WS2801_RGB) ?
    		((uint32_t)pixels[ofs] << 16) | ((uint16_t) pixels[ofs + 1] <<  8) | pixels[ofs + 2] :
    		(pixels[ofs] <<  8) | ((uint32_t)pixels[ofs + 1] << 16) | pixels[ofs + 2];
      return 0; // Pixel # is out of bounds
    /* ========================== Application.cpp =========================== */
    ////#include "SPI.h"
    ////#include "Adafruit_WS2801.h"
    Example sketch for driving Adafruit WS2801 pixels on the Spark Core!
      Designed specifically to work with the Adafruit RGB Pixels!
      12mm Bullet shape ---->
      12mm Flat shape   ---->
      36mm Square shape ---->
      These pixels use SPI to transmit the color data, and have built in
      high speed PWM drivers for 24 bit color per pixel
      2 pins are required to interface
      Adafruit invests time and resources providing this open source code, 
      please support Adafruit and open-source hardware by purchasing 
      products from Adafruit!
      Written by Limor Fried/Ladyada for Adafruit Industries.  
      BSD license, all text above must be included in any redistribution
    // The colors of the wires may be totally different so
    // Spark Core   WS2801
    // VIN       -- +5V
    // A3 (SCK)  -- Green wire on Adafruit Pixels, CI (Clock Input) on strips
    // A5 (MOSI) -- Yellow wire on Adafruit Pixels, DI (Data Input) on strips
    // GND       -- GND
    // Don't forget to connect the ground wire to Arduino ground,
    // and the +5V wire to a +5V supply
    // Set the argument to the NUMBER of pixels. 25 = 25 pixels in a row
    Adafruit_WS2801 strip = Adafruit_WS2801(54,WS2801_RGB);
    // For 36mm LED pixels: these pixels internally represent color in a
    // different format.  Either of the above constructors can accept an
    // optional extra parameter: WS2801_RGB is conventional RGB order
    // WS2801_GRB is the GRB order required by the 36mm pixels.  Other
    // than this parameter, your code does not need to do anything different;
    // the library will handle the format change.  Example:
    //Adafruit_WS2801 strip = Adafruit_WS2801(25, WS2801_GRB);
    // Initialze the pct value for the showPercent() function to 0
    int pct = 0;
    // Initialize the delay that will be used when setting pixel colors.
    int dly=5;  //Leave at least some delay in.  It doesn't appear to work without a delay. 
    //Flag to indicate if a showPercentage update is already in progress
    bool updating = false;
    void setup() {
      // Update LED contents, to start they are all 'off';
    void loop() {
      // Some example procedures showing how to display to the pixels
      //colorWipe(Color(255, 0, 0), 50);
      //colorWipe(Color(0, 255, 0), 50);
      //colorWipe(Color(0, 0, 255), 50);
    int setDelay(String delayString) {
      //get the new delay value from the string
      int newDly = delayString.toInt();
      //make sure that the delay is at least 1
      dly = max(1,newDly);
      //make sure the delay is no more than 50
      dly = min(50,dly);
      return dly;
    int showPercent(String percent)
    	 Serial.print("percent: ");
    	 int newPct = percent.toInt();
    	 Serial.print("newPct: ");
    	 if(newPct == pct) {
    		  return 0;
    	 if(updating) {
    		return 0;
    	 updating = true;
    	 pct = newPct;
    	 int pixels = (int)(strip.numPixels() * (pct / 100.0));
    	 int pixel;
    	 Serial.print("Num pixels: ");
    	 //Determine the color based on the percentage
    	 //If the pct is less than 98, full red component, otherwise no red component
    	 int r = (pct < 98) ? 255 : 0;
    	 //If the pct <= 92, no green cpt, if it is <= 98, half green component if it is > 98, full green component
    	 int g = (pct > 92) ? ((pct > 98) ? 255 : 128) : 0;
    	 uint32_t c = Color(r, g, 0);
    	 for (pixel=0; pixel < pixels; pixel++) {
    		  strip.setPixelColor(pixel, c);;
    	 if(pixels < strip.numPixels()) {
    		  c = Color(128,128,128);
    		  for(pixel = pixels; pixel < strip.numPixels(); pixel++) {
    	 updating = false;
    	 return pct;
    void rainbow(uint8_t wait) {
      int i, j;
      for (j=0; j < 256; j++) {     // 3 cycles of all 256 colors in the wheel
    	 for (i=0; i < strip.numPixels(); i++) {
    		strip.setPixelColor(i, Wheel( (i + j) % 255));
    	 };   // write all the pixels out
    // Slightly different, this one makes the rainbow wheel equally distributed 
    // along the chain
    void rainbowCycle(uint8_t wait) {
      int i, j;
      for (j=0; j < 256 * 5; j++) {     // 5 cycles of all 25 colors in the wheel
    	 for (i=0; i < strip.numPixels(); i++) {
    		// tricky math! we use each pixel as a fraction of the full 96-color wheel
    		// (thats the i / strip.numPixels() part)
    		// Then add in j which makes the colors go around per pixel
    		// the % 96 is to make the wheel cycle around
    		strip.setPixelColor(i, Wheel( ((i * 256 / strip.numPixels()) + j) % 256) );
    	 };   // write all the pixels out
    // fill the dots one after the other with said color
    // good for testing purposes
    void colorWipe(uint32_t c, uint8_t wait) {
      int i;
      for (i=0; i < strip.numPixels(); i++) {
    		strip.setPixelColor(i, c);;
    /* Helper functions */
    // Create a 24 bit color value from R,G,B
    uint32_t Color(byte r, byte g, byte b)
      uint32_t c;
      c = r;
      c <<= 8;
      c |= g;
      c <<= 8;
      c |= b;
      return c;
    //Input a value 0 to 255 to get a color value.
    //The colours are a transition r - g -b - back to r
    uint32_t Wheel(byte WheelPos)
      if (WheelPos < 85) {
    	return Color(WheelPos * 3, 255 - WheelPos * 3, 0);
      } else if (WheelPos < 170) {
    	WheelPos -= 85;
    	return Color(255 - WheelPos * 3, 0, WheelPos * 3);
      } else {
    	WheelPos -= 170; 
    	return Color(0, WheelPos * 3, 255 - WheelPos * 3);
  5. Click the "Save" button (looks like a folder, don't ask me why) to save the sketch:


  6. You can the "Verify" your sketch:


  7. If you have claimed multiple cores with your account, make sure that the correct Spark Core is set as the target by choosing the "Cores" option along the left, then clicking on the "Star" icon next to the core you want to flash:


  8. Finally, you can flash the code to your Spark Core:

    Note: The Spark Core's LED should blink purple while it is being flashed


  9. You know your core is ready when it is once again "breathing cyan"

## Identifying your Spark Core ##
  1. Before you can call the "showPercent" function on your Spark Core, you need to know

    • The Spark Cores Core ID
    • The Access Token for your account

We'll walk through finding both of these here:

  1. You can determine your Spark Core's Core ID using the Spark-CLI if it is connected to your PC and "breathing cyan" by issuing the following commands:

    spark cloud login
    spark cloud list


  2. You can also determine your Spark Core's ID from the "Spark Build" web interface. Login to "Spark Build", and from the "Cores" page, click on the arrow next to your core to see it's Core ID:


  3. Your access token can also be retrieved from the Spark Build web interface. Click on the "Settings" link, and copy your Access Token from there:


## Testing the Spark Core ##

Ok, if you got this far it is assumed that you have a Spark Core connected to a GIVE sign. You can now disconnect the Spark Core from your computer (disconnect the USB cable), and power it from the 12V/5A DC Power Supply instead.

We will be using the Spark REST API to call the "showPercent" function published by the "LEDDOTS" app we flashed onto the Spark Core.

The REST Api requires that all requests include the "access_token" for the account that the Spark Core belongs to, as well as the Spark core's devic ID (Core ID). Use the instructions in the "Identifying your Spark Core" section to retrieve those values if needed.

The showPercent(string) method takes a single string "command" that represents an integer. The integer is a percent between 0 and 100.

The showPercent function only applies the new value if it is different from the current value. When a new value is receive it plays an animation (cycles the rainbow colors, then does a chase of white dots) before showing the new value.

The server sends updates to the Spark Core about once every 10 seconds. Be aware of that when you are testing. If you set a value using the REST api, it may be subsequently wiped out a an update from the server. In fact, this is pretty much guaranteed to happen if things are working right.

You can call the "showPercent" function on the spark a number of ways:

  • Spark-CLI
  • Curl
  • A REST Client Tool
  • A custom App

We will cover the first three here and leave the custom app implementation to you:

  1. Connect the 12VDC Power Supply to the Spark Core circuit in the enclosure, and wait until it is "breathing cyan":


  2. To use the Spark-CLI to call the showPercent function on your Spark Core, first make sure you are logged in via the Spark CLI:

    spark cloud login

    Then run either:

    spark call <core id> showPercent 50


    spark call <core name> showPercent 50

    for example:


    Note: showPercent returns the percent that was set. It returns 0 if the new percent is the same as the old percent. Feel free to change the percentage to try different values.

  3. You can also use curl to test your spark using the following format:

    curl<core id>/showPercent -k -d access_token=<access token> -d params=<pct>

    For example:


  4. Finally, you can also use a REST client like the "Advanced Rest Client" app for Chrome.


  5. To create a custom app (A Windows or Windows Phone App, Web App, iOS, Android, etc) you can read up on the "Spark REST Api" and implement your client code accordingly.

## Circuit Schematic ##