Hugh, Pedro, Ethan, Miranda

Flask is an intelligent beverage container that interacts with the International Space Station. It allows the user to experience the excitement of space exploration through their bottle. Using the cloud network, Flask is constantly aware of the ISS’s location and relays that information to the user through the use of an LED ring.We decided we wanted to make something fun, that had a less serious tone than other projects we’ve undertaken in previous years. Thus, Flask was born. The idea was made to connect to completely unrelated areas: beverage consumption and the International Space Station. The idea formed into an intelligent bottle that displays the ISS’s location on a compass-like ring of lights. Anyone could use Flask, but it’s geared towards the “ThinkGeek” type of consumer.


User Testing Materials

NASA Parts List Part ID Count Cost Cost + Tax Cost (group)

3x Particle Photon Wifi Dev Module $64.41

4x ‘4X6cm Prototyping Board’  $6.67

4x neopixel ring $42.94

4x Plastic Flask $40.00






Part 1

16523230_10155034877154596_1301031756_o 16523756_10155034877314596_745456409_o 16651149_10155034877264596_1782412401_o

We began with the simple mathematics behind tracking the actual space station. During this time, from prior projects, we knew of tools that previously existed in terms of technology that could help this project come together. We moved from this to a quick decision about the form factor. We settled on it being a flask.

It was at this stage that we decided on using the Photon, using a Bottle, and having the tracking of the ISS in place as a core element to the tool.

part 2

16593600_10155034874849596_1975783129_o 16523208_10155034874949596_931137436_o 16523676_10155034875909596_399266324_o

Using the photon proved frustrating to use as we attempted further with the code, but luckily the early-made decisions about the form factors allowed other members of the team to get working on the different aspects of this project.

Depicted above are the elementary stages someone goes through to initialize the particle photon; the first step in relation to preparing for Internet of Things.

part 3

nasa_p-2_3x5 nasa_p-5_5x3 nasa_p-6_5x3

The development of the tool went quickly after the photon micro controllers arrived

we got right to prototyping the bottle. These pictures are part of the instructable on Nasaflask.

nasaflask-p-1 nasa_b-1_7x3 16593741_10155034871684596_300066054_o


  • Fill canteens with water. Make sure the prototypes are in their casings.
  • Do you need extra batteries?
  • No, just bring the lithium ion battery.


In-Class User Testing – Testing By Classmates

  • Set up canteens, allow users to form their own first impressions on what the device appears to be/do.

Field Testing – You testing your own device.




 User testing our object was unique in the fact that there is little input from the user. It is more of a static object that changes over time. I found that people were intrigued by the form as I used it, and wanted to know what it was. This curiosity is good and bad. While people wanted to know what it did, they couldn’t tell what it did until I explained it to them. I think the learnability and accessibility of an object is important and I think it was lacking in our product when we tested it. Stickers, instructions or even logo imagery could have helped the accessibility. Users enjoyed watching the lights change but after the first couple times, they lost interest. Adding an interactive feature I think could greatly reduce boredom in the user and extend the lifespan of the product. Users suggested that the product be sold on Thinkgeek or similar sites. Our product concept was validated by the users. Most of the critiques came about from our execution.



Testing periods: Saturday and Sunday, 1-9pm

Notes about Canteen user testing:

  • Seems much too large, not comfortable to carry around for long periods of time. Could be a household item, but still would be much better to make it a lot smaller.
  • Common consensus is that the idea is “neat”, “fun” and “entertaining”.
  • People liked the lights, wanted a more sleek design
  • It felt too fragile over long periods of time; I was always conscious of the fact that I had it with me and if a certain way I moved my bag would screw with the electronics.
  • Most younger people liked the idea, as well as the older, “parent” aged group I asked. A lot of people said that it was the type of thing they’d see on ThinkGeek.
  • Most people said that the actual bottle wasn’t good quality enough to warrant the price that would cover our costs. Plastic just doesn’t seem to translate into an idea of “high quality”, even though the plastic is thick.
  • The bottom compartment seems too squishy; it doesn’t stand up well on its own at all which means you constantly have to lie it on its side, making it very difficult to see the light.
  • Most people had no idea what it did based on first appearances, and they all said that having more space-centered design on the bottle would help add to the “fun” factor as well as making the bottle more easily understood.


  • “As long as it happens semi-often it’s a cool idea”
  • “I like it as a reminder to drink water, when I’m so busy I forget.”
  • “It would definitely sell, people love that kind of shit now.”
  • “Super unique.”
  • “It’s fun! Wish it was a bit smaller.”
  • “It would need to come with instructions to explain how it works, because I have no clue what this thing does.”

General Consensus/Things Learned

  • The bottle is far too large, and the design of the device is too bulky.
  • Most people don’t want a plastic-based water bottle.
  • The idea intrigues many and most people that tested it out thought it was fun and interesting.
  • Best marketed towards the “ThinkGeek” consumer crowd.
  • Battery is seemingly sufficient


  • After the in-class user testing, our team looked at the google form findings and discussed possible changes we could make to the flask within our time limit.
  • After the field testing, our team came together to talk about our findings and again discuss what issues were possible to act upon within the time limit we had before final iterations.
  • We decided to take some of our google form data and add it to our presentation, so as to allow the class to better understand why some changes were made between the user testing form they experienced and the final form we had.


Questions for testers:

  • When first presented, is it obvious what the object does?
  • Once in your hand is it intuitive to use?
  • Do you feel like you want to interact with the object? If not, why?
  • What context would you use this device in?
  • Is this device aesthetically pleasing?
  • How does the object make you feel when you use it?
  • What would you change about the device?
  • What appeals to you most about the device?
  • Would you purchase this product? What price point do you think is reasonable for this product?
  • The data collected from the survey should be available using the Google Form survey, if there’s an issue accessing it, let me know and I can try to fix it. I’ve never had to share a result before, but I did click the box that said anyone answering the survey can see the result? So you may have to add answers into the fields and then it displays the results.


  • references & related works
  • any references / support materials used for the project
  • references to related articles, papers, projects, or other work that provide context for your project. Write about the relationship between your project and these references



 2 hours – Decided to write an update on the second hour then every four hours after this update. Well the flask has been on for a bit now and the lights come on for a few minutes then turn off for a longer time, this has sort of a meditational effect on me right now but I’m not sure how it will change.

4 hours – Four hours have passed and the blinking lights of the bottle don’t seem to bother me, but I do wish there was some sort of communication every time the lights turned on to tell me. I feel like that would make this product more interactive in many ways if that is a part of it. But all things considered, the battery still doing fine and LED ring still not burned out.

8 hours – After 8 hours the bottle became background notifications I could see that the lights showing and when they were showing and they did not seem to bother me nearly as much as earlier on when I was not used to the blinking lights. Battery still holding fine and I think I’m going to start taking a drink of water from the bottle when it blinks. Battery still holding and LED still not burned out, as well as structurally the bottle is still holding.

12 hours – At the end of the 12 hours of user testing there are some observations I do have to make, one of them is that user experience changed drastically for the better if I did take a drying every time it blinked and that it was not only more interactive but I cared much more for it and wished the lights changed every time I did take a drink.

Battery and hardware wise it held perfectly and being one of the programmers I would change a lot of things after this user testing on the code. It was fairly accurate only losing the ISS during the end of the testing did it desynchronize with the orbit. Summary of User Testing This user testing was about answering questions of accuracy and strength of the machine but it wielded much more to look over and consider.

The fact of the flask losing accuracy over time and the user needing extra incentive to start using the machine as a bottle were the main ones I found. Though it did do very well for 12 hours straight it was a very bright cold light blinking and I do wish now that we had changed it to something that either change light color or are a warmer color as it reaches your location. It still functions very well as a driving game and has great potential for kids and schools to learn and teach younger kids more about space and stellar bodies.

The battery lasted for the whole testing and looks like it is still for 24 hours after so recharging might be necessary every 3-4 days of usage, the actual components of the Flask are still intact and compact enough so that everything is not a burden to carry around. All in all, it is a very good design, however, there are minor changes in the algorithm that I do have to make so that accuracy does not slowly desynchronize over time, and that is something with my math more than anything.

It was a fun product to have around the house and I would totally buy it if I I saw it online but not in the form it is now it would have to be more compact and better looking with the entire system built into the bottle.


In conclusion, the premise behind the device was interesting to users, but the execution could be improved upon. Many people wanted the Flask to have more visual cues, as it was hard to know the connection between the Flask and its technology upon first look. In addition to that, because most issues were with design, the actual build of the Flask would have to be drastically improved in further iterations. Most people felt that the plastic bottle composition did not translate into a “quality” feel. The bottle itself was also much too large for day-to-day use, and would have to be made more compact. The electronics themselves need to be secured more permanently, and downsized as well. Overall, the major problems were size and design factors. There would also have to be a change in materials in terms of the microcontroller, as we found that the Photon could not handle the code for what was necessary to make the device successful.

What we would do in our next steps is move towards a metal material and to solidify the software so that the device remains accurate. We want to integrate some design factors that can inform the user what they are using and how it works. Ideally we would want to produce a product that feels worth fifty dollars, as opposed to the overall 20 dollar price point that people expected to pay.

The best parts that worked for us was the sleekness and overall design, but the overall design got in the way of the clear use that should be depicted on the object.

Hugh, Pedro, Ethan, Miranda

Remindlet – Final Report

Project Overview

Members: Jade Wu, Clay Burton, Do Park, John Cho

Remindlet is a wristband type wearable which tracks any bluetooth device to see if it has left its wearer’s vicinity. It alerts the user with vibration and light when tracked devices are out of range. 

Click here to see product video.

Final Design

16466822_10154062133987186_404734406_o 16466211_10154062135207186_2121618709_o 16492535_10154062134752186_2036688774_o

This is our final design, we tried to make the whole circuit as small as possible. It turned out that the final prototype is nearly half size of the first prototype. For the future iteration, we will look for different type of material. e.g. plastic, rubber.

Production Material


1. 2 female to male jumper cables

2. 1 RGB led (any size)

3. 1 Sparkfun FTDI Basic Breakout

4. 1-2k resistors 1-1k resistors

5. Lithium battery (3.7v)

6. Vibration motor

7. Small (or cut) proto-board

8. Arduino Pro Mini 5V

9. HC-04 Bluetooth Module

10. Jst 2 pin connector

11. 4 pin female to male connector


Final Bill of Materialsbill

Final Circuit Diagram


Final Code: Click Here

User Testing: Field test – During our field test a few problems we had was that since the electronic parts are attached to the fabric, the fabric wasn’t washable. Although it didn’t really matter for our field test, it was pretty apparent that it would be a problem long term with how dirty they got in 2 days. The code and bluetooth chip was also not perfect and that caused the bracelet to malfunction from time to time (turning red and alerting the user that bluetooth has disconnected even though it hasn’t). That was slightly annoying during the testing since it would buzz randomly, that could be fixed by using a higher grade of bluetooth module and optimizing the code. One last problem we had was the battery wouldn’t run for a long time because of how much energy the bluetooth module needed. Some of the positives results we had was that the Remindlet was very comfortable to wear because of the fabric we choose (it was thick and almost cushiony). Also, the battery was removable and could be recharged easily and that was by design. User test: Most people thought although the Remindlet worked well they would find it more useful in other situations or in a different format-such as a keychain.


How bluetooth works: Link

AT Commands Sheet: Link

Projects done with HC-05 bluetooth module: Link 1 Link 2 Link 3



Overall it was quite fun project to do. We had a tough time to figure out how to make it work in the beginning, but it turned out great at the end. The most challenging part was understanding how the bluetooth module works, and how to command it to find the other devices around it. We invested significant amount of time to research on this and fortunately we were able to find a useful resources to make it work. For the casing, we didn’t have enough time to look for silicon printing/molding. However, we are currently looking for other students from industrial design program to take this project further Working with them would make the future prototypes more marketable and practical.



Tech-Charades (Final Report)

Project Overview
Alessia, David, Janelle and Thomas Present: Tech-Charades!

Tech-Charades is a wearable party game for 2 or more players which uses a microcontroller and TFT screen to display different images to act out.






Production Materials

Bill of Materials:

Circuit & Code:

Design Process
1) Initial Concept

The original pitch for Tech-Charades was a headband in conjunction with a touch screen, which we ended up not using due to cost. Instead we opted for a TFT display with a built-in SD card reader. Hypothetically an end user could add their own photos to the game, however as we later learned the screen was very particular in terms of the image formatting.

Alessia produced a prototype headband as pictured above, but we decided to change the form of the wearable to a baseball cap to improve comfort and stability.

Our original concept also included the use of two tilt ball sensors. These would be used for player feedback: Tilt your head one way to confirm a correct answer and another to skip. After some tests this idea was abandoned due to the uncomfortable 90 degree angle needed to activate the tilt ball reliably. Using a PIR motion sensor was also looked into, however it would be nearly impossible to get two different outputs, and was more costly and complicated than a simple button. So we made the design decision to not differentiate between a “skip” and a “correct answer” and instead have the player track their own score. This made the circuit and code much simpler.

2) Prototype

Getting our prototype ready for user testing was quite difficult due to the finnicky nature of the TFT screen. All connections to the screen must be secure upon initialization of the Arduino sketch, otherwise the screen may power on but will not display anything. This meant there was no room for error when it came to soldering. Ultimately we were only able to have the screen with the game running separately on a breadboard and the cap with the enclosure full of parts prepared for user testing, though these still produced valuable feedback.

The biggest change made to the design at this point was the development of the head mount for the enclosure. Due to the cap being round and the enclosure being rectangular it did not snap on properly at the time of user testing. To solve this Thomas modeled out the head mount in Rhino, and had planned to 3D print it, but was unable due to a miscommunication. This setback turned out alright though, as we moved on to a papercraft version of the mount which was lighter and cheaper than the 3D printed version would have been.

3) Final Design(s)

Due to the technical challenges with the screen and with fitting all the electronics inside the enclosure, we each ended up with similar but slightly varied designs.

David’s Version:


Initially it seemed as though the Feather 32u4 would not be a viable microcontroller due to the documentation for the TFT screen provided by Adafruit. However after some trial and error it was found that the Feather simply has different SPI pinouts than the Arduino Uno. These are as follows:

Uno     Feather
TCS 10 10
D/C 8 9
RST* 9 0
CCS* 4 6
Interrupt 0 (skip button)    2 3

*customizable pins

In this version of the design the Feather (rather than the screen) is mounted to the protoboard using female header, which connects to the screen via hookup wire. Female header was also soldered to the TFT instead of male header for a simple socket-to-socket connection; the tension from the wires holds the screen in place. A hole was drilled in the back of the enclosure, and the wires for the skip button were threaded through to the side of the head mount.

Alessia’s Version:


For the Uno design, the screen is soldered to male header which plugs into a set of female headers on the protoboard. Wires connected to the protoboard go from there to the Uno which is placed underneath the protoboard. Additionally, a longer set of screws is needed to keep everything in place.

Besides the soldering and wiring, the main challenge of this configuration was fitting the power supply, as the 9-volt input jack for the Uno was inaccessible. Alessia’s solution was to drill a hole in side of the enclosure, both for the skip button and a USB cable which lead to a rechargeable unit fastened to the back of the cap.

Thomas’s Version:

This version was mostly the same as Alessia’s, however for the battery Thomas cut the jack off the 9-volt adapter and wired it directly to the gutters of protoboard. This worked initially, however for the sake of consistency he changed the power connection on the TFT from the Vin pin to the 3v3 pin. Because there was no voltage regulator on the latter, this sadly blew out the screen. Thomas also drilled a hole in the top of the enclosure to mount the skip button.

Janelle’s Version:


Janelle’s used the same external battery configuration as Alessia’s (with the regular 9-volt), and the front-facing button configuration used by Thomas. Unfortunately during testing the 9-volt adapter came undone and the enclosure had a tendency to fall out of the mount.

Version Differences Overview:

David Alessia Thomas Janelle
Microcontroller Feather Uno Uno Uno
Battery Rechargeable? Yes (LiPo) Yes No No
Battery Placement Inside enclosure Outside enclosure Inside enclosure Outside enclosure
Button Placement Side Side Front Front

4) Instructable

User Testing




Essentially we were testing 2 distinct aspects of our project; the wearable and the game itself. Overall the response to the wearable aspect was good, although there were some concerns about the weight and secureness of the enclosure. In response to this Thomas designed a head mount for the device as previously mentioned.

As for the game, users found that it was intuitive once explained, but nearly unanimously agreed that 30 seconds was a better image refresh rate than 10 (though for demonstration purposes 10 was appropriate). Users also desired the added functionality of a button, which was planned but not ready at the time of testing.

Field Testing


Results: tech-charades-final-usertesting-survey-google-forms-2


During field testing found some things came to our attention which did not come up in our initial in-class test. One prominent issue which affected the readability of the images was the difference in height between players. A simple solution was to have the wearer of the hat sit down during gameplay. A more involved solution for a future iteration would be to design an adjustable hinge for the screen to sit on top of.

Another takeaway from participating in the playtesting was our inherent bias/advantage as the designers. Because we had become familiarized with the set of images used we were much better at the game than newcomers were. Though players understood the rules just fine they did not always feel they were intuitive to act upon. For example, the ambiguity in what constituted a correct answer, which was partially left to the player to determine. Players also seemed to prefer to use either words (as in Hedbanz) or actions (as in Charades) solely, instead of a combination of both as permitted by the rules.


Pocket Breathalyzer: Final Report

Project Overview


Members: Mackenzie, Quinn, Enoch, Caroline

The Pocket Breathalyzer is a tool created for management of the recreational use of alcohol, as a portable safety unit capable of identifying the levels at which a user is legally allowed to drive. The small and portable device is intuitive, and easy for anyone to use as a quick and reliable way to check their own BAC. The device can be used by anyone from teenagers to adults, and targets users ages 19-25 as the intended consumer. This device was created as a rough guideline for people new to alcohol who may not have a full grasp over the legal limits set in place by the government. This device proves as an easy way to take precautions, and ensure that nobody steps into the driver’s seat while intoxicated.

Pocket Breathalyzer Promo Video



Production Materials

Final 3D Model Design File

Bill of Materials


Code used for Pocket Breathalyzer

User Testing Materials

Our plan for user testing was to create a Google Forms survey for every user to complete after listening to us discuss the concept and ideas behind the pocket breathalyzer and interacting with our prototype. With the data we collect from the surveys, we hoped to receive suggestions on how to improve the devices for the final iteration and gain a better understanding of what people wanted from a product like this.

End-of-session Report Forms

Data Collected

Photos & Videos

During our user testing session, the general reactions to the pocket breathalyzer were positive, and this was reflected in the answers to the Google Forms survey they filled out. Everyone found the 3D printed models of the breathalyzer easy to use. Most liked its simple but functional design, as well as the compact size that allowed it to fit inside most pockets. Regarding the design, several people noticed the grey colour of all the prototypes and suggested making the breathalyzers more colourful. Some other advice we received was to add an LED colour gauge that corresponds with the alcohol readings, replace the screw sockets, make an port to easily recharge the breathalyzer, and add a logo that immediately identifies it as a pocket breathalyzer.

The breathalyzer’s coding and function was also commented on, with most people agreeing that our initial plan of the user blowing into the product and having an LED indicate their alcohol levels by the appropriate colour was a solid idea. A few people offered suggestions such as sending a notification to the user’s phone or adding a vibration function, but those were ideas to be added as extra features rather than ways to improve the product.

The concept of the pocket breathalyzer was unanimously well received, as everyone agreed that it was a useful device whether for social events, preventing drunk driving, personal safety, restaurants, or merely as a fun party toy. Many also thought it would be personally useful; those who drink regularly are interested in knowing how much alcohol they consume, especially if they plan on driving afterwards.


Gas Sensors With Arduino – This page provides an example code and wiring diagram for the MQ-3 Alcohol Gas Sensor, the same sensor we used in the pocket breathalyzer.





Nathaniel Leslie   |   Luke Garwood   |   Jacob Cram   |   Colin Borins


Below is a link to the pdf containing the the blog post.


A Gentle Reminder (final report)

Project Overview

  • project title
    • A Gentle Reminder
  • names of group of members
    • Carolina Gonzalez-Brossard, Sunny Ho, Arsalan Rashdi, Bernice Wong
  • project description, including overview of object and intended context and users
    • It is a device that is to be worn on the arm or wrist that vibrates after a preset amount of time to remind the user of something they need to do. With only three buttons, it makes it very user friendly: each press of the ↑ button increases the timer by 30s, and when ready, pressing the Start/Off will enable the timer, and simultaneously turns on the LED. The LED will turn off when the device starts vibrating after the timer ends.
  • 2-minute video presenting the portable & summarizing the field testing plan & results
  • Instructable link:
  • clean portrait images with device being worn / used by each group member


  • img_20170201_123503   16466616_1193226900733166_344824614_o

Production Materials

  • final design files
  • final Bill of Materials (spreadsheet including costs & suppliers)
    Part Number Part Name Supplier Name Link Cost Per Unit Quantity Needed Total
    SPEDE-001201 MINI VIBRATION MOTOR – 10MM creatron $3.59 1 $3.69
    LEDGE-005500 5MM LED – GREEN (20 PACK) creatron $0.10 1 $0.10
    SWTAC-000022 Button creatron $0.30 3 $0.90
    PCBDA-090571 PROTOYPING BOARD – BREADBOARD creatron $7.35 1 $7.35
    FEATH-002829 feather bluefruit adafruit/creatron $39.50 1 $39.50
    UBATT-008481UBATT-007120 LITHIUM ION BATTERY – 1200MAH creatron $17.85 1 $17.85
    FEATH-002829 velcro dollarama $1.25 0.25 $0.31
    FEATH-002829 lycra fabric king textiles $12.50 0.25 $3.13
    TGT12CL4 R12 4 Ft. Tube Guard T12 home depot $6.98 1 $6.98
    WIRES-822254 22 AWG HOOKUP WIRE – YELLOW creatron $4.75 1 $4.75
    H0305 canvas board 3″x 5″ curry’s art store $0.49 1 0.49
  • final circuit diagram
  • final code (link to GitHub)

User Testing Materials

  • user testing plan
    • User test
      • We first gave an introduction to our device, stating what it is and what it does. Then we demonstrated how to use the device by showing them the buttons and first setting the timer to 30s. After that short test, we had them set the device themselves to 5 minutes, and told them to perform a task after the timer rings. During that time, we had them play a few games on our laptops as a form of distraction. When the timer rang, they were expected to perform the task stated to them before the 5 minute testing period began. Afterwards, we had them fill out the user testing forms to collect feedback.
    • Field test
      • Each of us wore the device for 8 hours in our own time. We didn’t set any other guidelines for ourselves other than that we had to take note of anything that didn’t function as it should. Afterwards, we had us fill out the field testing forms to collect observations.

      img_20170130_120647 img_20170128_185316

  • link to end-of-session report forms
    • User test
    • Field test
  • link to data collected
  • summary of the testing process
    • User test
      • Overall it went smoothly, despite having some complications during our first test. We originally had an issue where the LED would turn off but the motor would not vibrate, but that issue was miraculously fixed by shaking the device.
    • Field test
      • Overall it went smoothly. Some of us had to fix our device as it came off of the arm band but other than that, we were able to make some observations from the test and was able to fill out the survey we made for ourselves
    • reflections on your findings
      • User test
        • A few testers thought that our device was rather bulky, which inspired us to think of a way to make our device smaller. We also received some suggestions for situations where this device could be used.
      • Field test
        • We found that the device proved to be useful, especially at home when we don’t use our phones to set alarms for ourselves. It was surprisingly comfortable, even though it looked rather bulky. From this test, we concluded that the device excels for relatively short term and non-habitual tasks. The biggest improvement that the device needed was a shrink in size. Though wearing the device was comfortable and the casing durable, over time the large and somewhat cumbersome casing was obstructing some tasks. With it’s size it is difficult to conceal and can be problematic during dynamic activities. In future iterations, A Gentle Reminder would probably utilize a smaller microcontroller board than the Adafruit Feather in order to make the piece more compact.

Revised Pitch – It’s 5 o’clock somewhere

It’s Five O’Clock Somewhere

Group members: Jacob Cram, Nathaniel Leslie, Colin Borins, Luke Garwood

Concept: A portable device which straps around a flask and indicates via OLED display where in the world it is currently 5 o’clock. When the user is in the 5 o’clock timezone, they get an indication via vibration motor.

Form: The device is meant to slip onto a flask and be worn inside a pocket. Because the device has an elastic component, it could also be wrapped around other objects including an arm or wrist.


Part Number Part Name Supplier Name Link Cost Per Unit Quantity Needed Total
particle photon $19.00 1 $19.00
delivery $5.00 0.25 $1.25
13626 particle breakout for battery sparkfun $12.95 1 $12.95
delivery sparkfun ? 1
LCDMD-006405 oled display creatron×64-spi-oled-display $17.00 1 $17.00
PCBDA-000370 protoboard creatron $2.80 1 $2.80
flask amazon $11.99 1
elastic king textiles
LEDMU-012987 box/cover
battery lipo creatron $15.55 1 15.55
SPEDE-001201 mini-vibration motor creatron $3.59 1 3.59

Multiples: Revised Pitch – Tech-Charade


Group Members: Janelle, Alessia, Thomas and David

Pitch created by Alessia and Janelle


Tech Charade is a game meant to be played by two or more people. Player one would wear the headband displaying images for player two to act out while the first player guesses the image. If correct tilt left for a point or tilt right to skip!



Bill Of Materials and Parts



Tech Charade is meant to be a wearable game similar to a headband. Intended to be used in social settings the outer casing will be comfortable to wear, but also durable and adjustable so it can be worn by many different users.

Production Process

The enclosure will be a headband made out of Sport/Comfort Dry Lycra. There will be either buttons or snaps at the back for the wearer to adjust the size of the band to their head. In addition, the fabric is a good wickaway, keeps its shape, and has properties meant for moisture management.

Proposed Production Schedule

Wednesday 18th – Finalize parts and materials and make the purchase. Begin code, as well as drafting for the fabric pattern and circuit.

Friday 20th – Sew fabric band and complete part one of the enclosure. Continue on logic.

Wednesday 25th – Circuit completed. Initial test and bug fixes. Assembly

Friday 27th – Completed.

Proof of Tech

Processing Sketch to demo functionality – left button to change the picture, at random, and right to add a point!
color fillVal = color(126);

PFont f;

int win = 0;
void setup() {
size(640, 360);
f = createFont(“Arial”,16,true); // Arial, 16 point, anti-aliasing on

void draw() {


rect(25, 25, 50, 50);
text(“Left button to change the image, and right to add to the score. This would be done with tilt sensors.”, 200,200);


void keyPressed() {

if (key == CODED) {
if (keyCode == LEFT) {
fillVal = int(random(0, 255));
} else if (keyCode == RIGHT) {


Pocket Breathalyzer – Janelle


A simple and easy way to drink and serve alcohol responsibly. To be used at house parties with your friends or by bartenders at work. A pocket breathalyzer, while not as accurate as the ones used by police, can be used to gage the amount of alcohol consumed.





A small and compact box either laser cut or 3D printed. Small enough to easily be carried around in the user’s pocket or attached to their keys. The measurements will be easy to understand by using red, yellow, and green LED lights which are commonly used as good, bad, and on the line.


Electronic components:


Bill of Materials    
Part Name Part Quantity Supplier Name Part Number Link Cost Per Unit
Alcohol Gas Sensor – MQ-3 1 Sparkfun SEN-08880 $4.95

(1+ units)

Mini Pushbutton Switch 1 Sparkfun COM-00097 $0.35

(1+ units)

LED – Basic Red 5mm 1 Sparkfun COM-09590 $0.35

(1+ units)

LED – Basic Yellow 5mm 1 Sparkfun COM-09594 $0.35

(1+ units)

LED – Basic Green 5mm 1 Sparkfun COM-09592 $0.35

(1+ units)



Materials and Production Process:

  1. 3D print a box, slightly bigger than the board being used, in two parts (the body and the lid) so that it can easily open and close to change parts as needed


laser cut all pieces for a similar box and glue all pieces together.

  1. Attach a key ring to allow the box to easily attach to things.


Proposed Production Schedule:

Friday 13th -vote for multiple

-determine parts needed

Saturday 14th –    Order parts

–    Begin 3D model/laser cut file

–    Modify/debug code

Wednesday 18th –    files sent to rapid prototyping

–    Code finalized

–    Proto board soldering and wiring begin

Friday 20th – Assembly begins
Monday 23rd –    Assembly finished

–    Testing begins

Wednesday 25th –    Testing finished

–    Modifications made

Friday 27th – Final in



Proof of Tech:


int sensorValue;

int REDled = 7;

int YELLOWled = 8;

int GREENled = 9;

int button = 2;

int buttonState = 0;


void setup()



pinMode(REDled, OUTPUT);

pinMode(YELLOWled, OUTPUT);

pinMode(GREENled, OUTPUT);

pinMode(button, INPUT);



void loop()


buttonState = digitalRead(button);

sensorValue = analogRead(0);




if (buttonState == HIGH)


if(sensorValue <= 350)


digitalWrite(GREENled, HIGH);

digitalWrite(YELLOWled, LOW);

digitalWrite(REDled, LOW);



else if(sensorValue > 350 && sensorValue <= 700)


digitalWrite(GREENled, LOW);

digitalWrite(YELLOWled, HIGH);

digitalWrite(REDled, LOW);





digitalWrite(GREENled, LOW);

digitalWrite(YELLOWled, LOW);

digitalWrite(REDled, HIGH);






digitalWrite(GREENled, LOW);

digitalWrite(YELLOWled, LOW);

digitalWrite(REDled, LOW);




‘NASA’ Zdrowie – Hugh Ritchie Pedro Betti Karolina Baran

Pedro Betti, Karolina Baran and Hugh Ritchie have an excellent new project in mind.

We want to generate a small physical object that encourages community involvement in space research and community support for NASA.

So What Happens When We Combine…


The International Space Station



Arduino/SparkFun Microcontrollers






The Idea

We want to produce a drinking vessel that tracks your position, compares it to the publicly broadcasted location of the ISS, to produce a science-like method to enjoying alcohol with friends. The vessel, probably a flask, would look like this :


It would consist of:

  •  eight directional lights (for the points on a compass)
  • a button to initiate a request for the ISS location, thus telling the user where the ISS is
  • a ‘pulsing’ function to inform the user how far away the ISS is
  • a full ring ‘pulse’ if the ISS is overhead (within some range)
  • a re-sealable chamber, fit for the containment of alcohol.


Our materials for the flask would need to be investigated further. We are currently considering:

  • 3d Printing
  • laser-cut wood
  • other ideas?

We would also use:

  • Particle Photon Microcontroller Board  (already included in our kits)
  • Short Proto-Board ($0.80)
  • Round Proto-Board ($1.15)
  • Insulative Hot Glue (already own)
  • A Lithium-ion Battery (already included in our kits)
NASA Parts List
Part ID Count Cost Cost + Tax Cost (group)
Particle Photon Wifi Dev Module PHOTONNOH 1 $19.00 $21.85 $87.40
2X8cm Prototyping Board PCBDA-000280 1 $1.25 $1.44 $5.75
4X6cm Prototyping Board PCBDA-000460 1 $2.95 $3.39 $13.57
5mm LED (10 pack) LEDTU-596100 1 $2.20 $2.53 $10.12
2PDT small latching switch SWTCB-001872 1 $0.30 $0.35 $1.38
Plastic Flask NA 1 $10.00 $11.50 $46.00

The Data

Some are wondering, “Seriously guys? Wtf. A spaceship tracking flask?”. Our response is in two parts. The first is, Yes . The second part has to do with how we will track a space ship. As previously stated, NaSa publishes the location of the ISS here:

And the result looks like this:

  "message": "success", 
  "timestamp": 1484262554, 
  "iss_position": {
    "latitude": "30.7694", 
    "longitude": "144.0449"

This sort of JSON file is easy to use and provides all the information we need to make this work, with some simple math.

We would use a similar JSON file from this address: This would help us find OUR gps location. The result should look like this:


    “as“: “AS33130 Internet Access Solutions Ltd.”,

    “city“: “Toronto”,

    “country“: “Canada”,

    “countryCode“: “CA”,

    “isp“: “Internet Access Solutions”,

    “lat“: 43.6898,

    “lon“: -79.5582,

    “org“: “Internet Access Solutions”,

    “query“: “”,

    “region“: “ON”,

    “regionName“: “Ontario”,

    “status“: “success”,

    “timezone“: “America/Toronto”,

    “zip“: “M9R”


All we do is compare the latitude and longitude values from the ISS and our own values, and we have our direction!

In Conclusion

We think this assignment would be lots of fun, and we think everyone could go together and chase the International Space Station with a small drink in their hand!

Thank You For Reading

Use of this service is governed by the IT Acceptable Use and Web Technologies policies.
Privacy Notice: It is possible for your name, e-mail address, and/or student/staff/faculty UserID to be publicly revealed if you choose to use OCAD University Blogs.