Hello everyone, and welcome back to another weekly design challenge summary. It’s the tenth and final week of the Design for a Cause Challenge. As one would expect, a lot of progress has been made over the past seven days, so let's cut to the chase and learn more about the challenge before we get to our first three featured project updates!

 

Design for a Cause Design Challenge

 

The Challenge

 

Featured as the third Design Challenge of 2018, this challenge task its participants with designing a piece of assistive technology for individuals living with physical or mental impairments using the Arduino MKR1000 Dev Board.

 

 

While sixteen project proposals were chosen to be the official projects of the challenge, entering the challenge is not limited to just those sixteen community members. Anyone can join the Challenge as a non-sponsored Challenger, and still be eligible to win one of the prize packs. If you are a non-sponsored challenger all you need to do is integrate an Arduino MKR1000 into your project, and then post 10 blogs about your progress in the Design For a Cause Challenge space and then tagging those blogs 'Design for a Cause'.

 

 

The Official Kit

 

As mentioned earlier, the Design for a Cause Challenge is sponsored by Arduino and its Arduino MKR1000 Development Board. Each challenger will receive all of the components below plus a wide assortment of additional passive, and digital components to build their projects with. If you would like to enter the challenge for yourself, or if you just want to follow along at home, you can purchase all of the components in the kit right here at Element14.

 

 

To learn more about each of these components as well as the other components included in the kit, visit the official kit announcement page or click the links above.

 

The Prizes

 

To reward the creativity and innovation of the challengers in the Design for a Cause Challenge, element14 is offering some cool prizes that both sponsored and non-sponsored finishers can win. To learn more about each prize pack, visit the official Design For a Cause Challenge Prize Page.

      • Grand Prize: $900 USD to the winner’s favorite charity,  FLUKE 279 FC/IFLEX Digital Multimeter, and a  Tinkerkit Braccio Robotic Arm DIY Kit.
      • Runner-Up Prize:$500 USD to the winner’s favorite charity Tenma  72-8474 Oscilloscope and a Microduino Quadcopter w/Joypad
      • Finisher Prize:  It’s a surprise! To be eligible, challengers have to post at least 10 update blogs and use an Arduino MKR1000 in their design.

 

 

The Past Week In Review

 

Over the past 7 days, September 9th - September 15th, we have had a total of nineteen updates posted across seven projects. I will be choosing three of my favorite updates from the week and highlight them below, but before we get into that lets take a look at which projects were updated this week!

 

 

This Week’s Top Updates

 

Project: Anosmia  - Design for a Cause Challenge Blog  #11 -  Machine Learning and Demo

 

 

It’s been just over two months since Dixon Selvan first set out to build a device that would help those with Anosmia (the loss of the sense of smell) that not only used an Arduino MKR1000 as the heart of its smell sensing system but would use machine learning to improve on its reliability. “For machine learning the smell, I have used the AWS machine learning service. This will create a machine learning model from the data source we provide, which has to be placed in the AWS S3 storage service. Once the model is created, we can try real-time predictions of smell in the AWS machine learning console,” he wrote. “Also, we can create an endpoint using which we can request and receive predicted smell information in a JSON format. I have created a web service in my local which will make a request to the Machine learning endpoint with data inputs from the mq5 and the mq2 gas sensor connected to Arduino MKR1000.”

 

 

Project: Audio4Vision - Design for a Cause Challenge Blog  #8 - Deploying the Show and Tell model on a server

 

 

The number two spot this week was claimed by Pranjal Ranjan, and his project’s eighth update. This week he focused on the deployment of the “Show and Tell” module to the project’s server. Using FLASK, a micro web framework, Pranjal was able to successfully write a python script that would read image files that have been uploaded to the server. “In order to create a web application, we'll be using a Python microframework called Flask. Flask is a well-known and well-documented micro web framework which acts as a backend for any website. Many large websites like Pinterest, LinkedIn, etc. use Flask in their backend,” he wrote.

 

“Flask mainly revolves around a python file, which contains all the routing logic, and for our purpose will also contain the model loading and prediction logic. It has a bunch of helper html files, called templates. These templates are basically individual web pages on the website, and can be assigned to specific routes in the python file.”

 

 

Project: Blowing-Whistle as Controller(BWaC) - Design for a Cause Challenge Blog  #10 - Prototype Completed

 

 

F. Yao’s project, Blowing-Whistle as Controller, gets the honor of being my final featured update from this design challenge. In the project’s final update F. Yao shows off the complete prototype and explains how its systems work. He has included detailed explanations of the code that makes the whole project function and says that he has prepared an Android application that will allow him to receive push messages based on the status of the light, door lock, and curtains.

 

“For now, the prototype design can run with what I had meant to do. While there are still two parts missing. I have prepared the draft Android Application receiving Published message from MKR1000, supervising the status of Light, Doorlock, Curtains and other extended sensor value,” he wrote. “I have prepared data for Machine Leaning model, using Neurona library. This is can be used for Whistle Blow Authentication and multi-decoding process. There are still many improvements needed to be achieved for the project. I will make more try.”

 

 

That is going to wrap up my weekly summary coverage of the Design For a Cause Challenge. Check back soon for another weekly design challenge summary. If you would like to learn more about that challenge and to see what progress has already been made, head over to its official challenge page. I'll be back next week for another installment of my Design Challenge Weekly Summary series here at Element14.