Difference between revisions of "Hoverbear"

From ESE205 Wiki
Jump to navigation Jump to search
Line 21: Line 21:
 
February 15, 2019:  Present initial project proposal to the entire class. During this time, the goals of the project should be presented along with a condensed timeline for completion as
 
February 15, 2019:  Present initial project proposal to the entire class. During this time, the goals of the project should be presented along with a condensed timeline for completion as
 
well as anticipated challenges that have been or will be faced.
 
well as anticipated challenges that have been or will be faced.
 +
*Finish the night light in the first week or so (date TBD)
 +
*Build the physical board (date TBD)
 +
*Familiarize ourselves with the sensor and work on coding to make self sufficient (date TBD)
 +
*Present hoverboard (date TBD)
  
 
===Challenges===
 
===Challenges===
 
* Not a whole lot of experience in automation. There will a be a learning curve for this group.
 
* Not a whole lot of experience in automation. There will a be a learning curve for this group.
 
This will be a list of things here at some point, but I think those should be decided on by a group, not just by me
 
This will be a list of things here at some point, but I think those should be decided on by a group, not just by me
 +
*It may be difficult to familiarize ourselves with a raspberry pi if that is what we decide to use (however I’m pretty sure we are not)
 +
*It could be a challenge to learn how to utilize the ultrasonic distance sensor so our can be self dependent and navigate through obstacles
  
 
===Budget===
 
===Budget===

Revision as of 21:45, 8 February 2019

Link to Log

Hoverbear_Log

Project Proposal

Overview

We are going to be constructing a hoverboard that would be able to hover a few centimeters off the ground. It will be able to move to a destination by means of a beacon or vectors, and contain some measure of intelligence.

Team Members

  • Lucas Alcantara
  • James Shaheen
  • Michael Horwitz
  • TA: Tony

Objectives

  • To enable the hoverboard to autonomously detect obstacles
  • To enable the hoverboard to autonomously travel to a beacon
  • To enable the hoverboard to follow a predetermined trail / follow a trail marked out on the ground

List of Dated Goals

February 15, 2019: Present initial project proposal to the entire class. During this time, the goals of the project should be presented along with a condensed timeline for completion as well as anticipated challenges that have been or will be faced.

  • Finish the night light in the first week or so (date TBD)
  • Build the physical board (date TBD)
  • Familiarize ourselves with the sensor and work on coding to make self sufficient (date TBD)
  • Present hoverboard (date TBD)

Challenges

  • Not a whole lot of experience in automation. There will a be a learning curve for this group.

This will be a list of things here at some point, but I think those should be decided on by a group, not just by me

  • It may be difficult to familiarize ourselves with a raspberry pi if that is what we decide to use (however I’m pretty sure we are not)
  • It could be a challenge to learn how to utilize the ultrasonic distance sensor so our can be self dependent and navigate through obstacles

Budget

James will put the budget here at some point

Materials

  • An Arduino of some kind
  • Some other things that we will decide upon at a future date

Gantt Chart

We haven't made one yet, and I can't make it myself

Helpful Links

https://makezine.com/projects/diy-r-c-hovercraft-from-cardboard-and-trash-bags/