Swine Flew with panel at the conference.

For those of you who were never a Boy Scout, the Pinewood Derby is a competition in which contestants build a small wooden car to race on a 40 foot track against other cars of the same approximate size and weight. The goal is to work within the parameters of the rules to build the fastest car.

Several years ago, the IDSA (Industrial Designers Society of America) decided to sponsor a derby car race for designers at their annual IDSA National Conference in Pasadena. The response was overwhelming as designers and engineers entered dozens of impressive cars that would lie, cheat and creatively steal their way to the finish line.

Since that first race in 2004, the competition has raged on, with designers from all over the country fielding extraordinary cars. For this years IBM Unlimited Derby held at the IDSA conference in Miami, Continuum approached their participation in the race in a new way. Rather than trying to create the fastest car, the team decided to create the most memorable car. To accomplish this, we started by brainstorming themes that would be relevant to what’s going on in the world.

The planet is currently going through a financial crisis that hasn’t been experienced in eighty years. We’re all being forced to pinch pennies and find creative ways to save money. At the same time, worldwide concern is high around health threats like the swine flu. Continuum took these themes and turned them into a statement of hope, a piggy bank car called Swine Flew.

The generous contribution of the IDSA audience.

Throughout the four-day conference, the attendees were encouraged to add their spare change to the piggy bank. This served two purposes. First, each coin made the car slightly heavier, and consequently, faster. Second, Continuum offered to multiply every contribution by 10 and donate the final amount to design education.

The Swine Flew pit crew members, Jung Tak, Damien Vizcarra, and Kevin Young (many thanks to the non-traveling crew of Jake Childs, Rich Ciccarelli and Bruce MacRae) have returned from the IDSA National Conference and are proud to bring home the award for Fastest Car in the Gravity Weight Class as well as the award for Most Fun.

We’re also proud to say that the generous contributions of the IDSA audience helped Swine Flew raise a total of $1,274.40 for design education.

The crew members are proud to bring back two IBM Derby awards.

final blog in a series of 5

There is still quite a bit of detective work to be done. A cursory look at our graphs shows we are using on average 40kWatts (the equivalent of 400, 100 Watt, light bulbs) during nights/weekends and about 120kWatts peak during normal business hours.

From the below graph we can see that during business hours something is causing large spikes. Since this only happens during typical work hours we could probably attribute this behavior to the power hungry tools in our awesome Models Shop, or maybe the elevator. The spikes are probably due to the inductive load introduced when a motor such as a saw or compressor is turned on.

The chart below is a display of power use over a ten day period. You can see the reduced power consumption over the weekends and holidays. I would gather that since there is a small amount of power consumption on Monday May 25th (Memorial Day) some Continuumites are workaholics!

What’s Next

Possible improvements
Migrate data server applications to a proper web server
Add multi client capabilities so we can host data from other users.
Tie in real time power cost metrics
Carbon footprint tie in
Tie in weather parameters such as outside temperature and humidity.

Contribute
If you find this design intriguing and would like to contribute in some way, or if you have any questions feel free to email me at mcosta@dcontinuum.com

#4 of 5 part series

The client application runs on the iMx21 meter reader. It contains 2 endless threads SocketThread and LCD Thread.

LCDThread – each iteration of the loop it performs a frame grab using the EZFB API. It converts the image to grayscale then calculates the average pixel intensity for the square we care about. The pixel intensity is low when the box on the Elster LCD is “on” and goes up when the box is cleared. This thread also draws a square onto the LCD screen so the person installing the meter reader can easily align the video camera.

Images of the meter reader output LCD.
The Kh box is visible, note the O/F text output. 1 means the box has been detected.

The Hr box is not visible, note the O/F text output. 0 means the box has not been detected.

The second thread is the SocketThread. This thread waits for a new measurement from the LCDThread. When a new value is ready it just sends the power value over Socket to the web server.

Testing
I tested the accuracy of the box blink rate algorithm with a test LCD display. Using a Microchip Explorer16 Dev board and a PIC24H processor, I rigged up a simple blinking box on the explorer16 LCD. With this test setup I set the blink rate to .1Hz, 1Hz, and 10Hz to verify my Emeter application.

Calculations
This application converts Blink Time to power in kilo-watts. The formula for this calculation is:

Power (kW) = (.9kWh * 3600s * 200) / BlinkTime
The .9kW and 200 are values taken from the meter.

Data & Web Server
The web server is running Ubuntu Hardy Heron, ProFTPD and Apache 2.0

EMeterServer Application
The EMeterServer has only one simple socket thread. This thread just sits and waits for a new Power value from the client. If there is a new value, it writes it to a MySQL database table.

Web Server
The data server hosts the data via simple RSS feed, and Perl scripts. Any internet ready device or web page could access the scripts or RSS feeds to get real time power use.

PowerRss.php – Returns an XML RSS feed that contains the latest power use value.

graphUpdateLong.pl- Returns a link to an image of a graph of the power use over time.

meterUpdate.pl – Returns a link to an image indicating the power use as a simple needle meter.

GoogleJSON2.pl -Returns a JSON object table containing historical power use. (used for Google Visualizations API)

Insert a link to these files in your web browser and you will see the results

http://209.48.56.105/power/PowerRss.php

http://209.48.56.105/power/graphUpdateLong.pl

http://209.48.56.105/power/meterUpdate.pl

http://209.48.56.105/power/GoogleJSON2.pl

With the recent banning of Speedo’s LZR sharkskin-inspired speedsuits and the exposure of possible steroid use by Boston Red Sox baseball player David Ortiz, it raises an exciting question: What role does design play in the evolution of sport?

Michael Phelps’ eight Olympic gold medals is a record that may never be broken, all set while wearing Speedo’s suit. The suit is modeled after the drag-resistant texture of sharkskin and compresses the swimmer’s body in key areas. Though Olympic records are falling, most world-class swimmers have access to the suits — is this an unfair advantage or an enhanced design?

Andy Roddick hits tennis balls fast. 153 MPH fast. Speeds like these were unheard of in the days of Rod Laver and wooden tennis racquets. Nowadays it is commonplace for men and women on the professional tour to be serving well above 100 MPH. Now that graphite, titanium and ceramic composites are routinely used for weight reduction and enhanced rigidity, even beginners have the opportunity to use something much improved over the tennis racquets of yore. But are the racquets improved or is the game just different?

400-yard drives on the golf course? Not before monster-sized titanium club heads.
Track spikes that are lighter than a slice of 7-grain bread? Not just for Olympians anymore.

Why should full-body swimsuits be any different?

Can a shoe be too light? Can a ski have too much spring?

Should altering an athlete’s equipment be any different than altering an athlete’s body? What is “ethical” body-altering? How about Red Bull energy drink? Can an athlete with a super-reconstructed knee jump higher or cut quicker than one without? How “able” should an athlete be? How soon will it be before athletes intentionally integrate prostheses or have healthy joints and limbs replaced with titanium ones before the original is worn out?

What is “performance enhancing design”? Few groups are asking and acting upon such questions — certainly there are lots of terrific opportunities to evolve sport and enable our bodies to push the limits of sport, but within what ethical boundaries? And how can (or should) design enhance such experiences?