SEPTEMBER 15, 2013 5-7PM
-Structure and Levitation: Mike, Josh, and David -Propulsion and Power: Julie and Michael -Finances: Julie?
|
Base CAD Design:
base1.sldprt | |
File Size: | 226 kb |
File Type: | sldprt |
base1josh.sldprt | |
File Size: | 161 kb |
File Type: | sldprt |
September 22, 2013 5-6PM
- Members present: Julie, Bryan, Michael, Mike, Josh, David and Alexa
- Members absent: Kushal, Charles, and Steve
- organize the groups and subgroups more, 2 more people need to decide, something that needs to get done today
- everyone bring $10 for next time
- Alexa in charge of fiinance/budget $
- Alexa will put notes on website/blog
- soft skirt vs. hard skirt = soft skirt
- use spray adhesive of some kind to attach the skirt (Elmers $5)
- figure out materials, look up online price and where it can be bought, budgeting person go and get the stuff, in person no shipping cost
- how to adjust fan speed, min and max current and output of fan?
- plan on using foam for base, figure out foam thickness
- use cnc mill for the foam , indents for battery and other components on the deck to fit in
- use Inventor for CAD
- need fan with high volumetric flowrate and low pressure
- team organization
- Julie wants to to Gantt chart
- contract system, discuss, steps to resolve participation problem
- 2-3 meetings in a row missed, let know if not coming, rules apply to subgroup meetings too
- subgroups bring up issue with entire group as a whole
- Kushal needs to tell us about robotic arm/sensors stuff
- divide powerpoint, different slides for groups
- ppt Bryan do team organization
- Kushal = Sensors and Control, payload delivery
- Structure and skirt = David
- Levitation and Propulsion = Mike
- Introduction and Objectives = Josh
- power, sensors, control and programming = Alexa and Charles
- using resistors with heavy duty fans
- ripstop nylon for the soft skirt
- Joanne's Fabric ripstop nylon
- financing and human resources Alexa
- higher gap height easier to add weight on than remove it after the fact
- 1-3 mm
- 1 mm gap
- 2 propulsion fans
- Action Items: (underlining means completed) Next Meeting September 29th
-$10 for next meeting (everyone)
-individual subgroup meetings (subgroups try to meet before main group meeting then can convene together and discuss what subgroup talked about)
-finalize subgroups by next meeting
-Byran figure out full group meeting time through Facebook poll what time on Sunday is good for everyone to meet as well as weekdays when everyone can go to the consultation/presentation
-Bryan make ppt in Google Docs
-Josh, Mike and David choose levitation fan by next meeting
-Julie, Brian, Michael, and Steve look into propulsion fans for next meeting and start looking into batteries
- Kushal needs to do an arm breakdown fill us in on the robotic arm (how is it/could it work)
-subgroups meet to discuss the steps needed for the Gantt Chart dates to complete all the steps as well as who is the subsystem leader
-next week have PowerPoint slides to put together into one presentation (subgroups and everyone involved)
Team Organization:
Project Leader: Bryan
Subsystem Leaders:
Subsystem Members:
-Sensors and Control: Kushal, Charles, Alexa
-Structural and Levitation: Mike, Josh, David
-Propulsion and Power: Julie, Michael, Bryan, Steve
Team Meeting Arrangements:
Project Leader: Bryan
Subsystem Leaders:
Subsystem Members:
-Sensors and Control: Kushal, Charles, Alexa
-Structural and Levitation: Mike, Josh, David
-Propulsion and Power: Julie, Michael, Bryan, Steve
Team Meeting Arrangements:
September 29, 2013 5-6:30 PM
- Members Present: Julie, Michael, Charles, Alexa, Bryan, Josh, David, Mike (came late), Steve (came late)
- Members Absent: Kushal
- Agenda:
-Friday = review deadlines and who is working on what
-Tuesday = when each part will be done
-Thursday =when final parts will be done
-subgroups and meetings
-money
- Subgroup Leaders:
-Structural and Levitation: Josh
-Propulsion and Power: Michael
- Levitation Fan
- Bryan writing group rules
- Joanne's Fabric ripstop nylon
- Perimeter: 1393 mm
- Area = 146200 mm^2
- Subgroup Meetings:
-Sensors and Control: ?
-Propulsion and Power: Tuesday?
- Action Items: (underlining means completed) For PowerPoint Completion
-Rough Slides Tuesday October 1
-Finalized Slides Thursday October 3
-schedule consultation (everyone needs to be there even if not presenting)
- Action Items: (underlining means completed) Next Meeting October 6 -$10 by next meeting (David, Kushal, Michael, and Josh!)
Group Rules
1. Must check blog if group meeting is missed.
2. Inform group members if you are not able to make a scheduled meeting, ideally 24hrs in advance. Facebook post should be made.
3. Missed Meetings:
Subgroup Meetings Missed:
If member is unable to make subgroup meetings to the point where it is a concern (ideally two meetings unexcused), subgroup should bring concern to specified person. If specified person does not respond to subgroup meeting (3 meetings total missed unexcused), attention to be brought to full group. If specified person does not respond to full group meeting (4 meetings total missed unexcused), professor should be notified. This rules are not definite and, depending on the scenario and how much effort specified person is doing to stay in touch and up to date with group members, the rules may be altered by a consensus amongst full group members.
Full Group Meeting Missed:
If member is unable to make two subgroup meetings, unexcused, group should warn specified person of their concern. Four meetings, unexcused, professor may be notified. Just as with the subgroup meetings, the rules may be altered depending on the situation by a consensus amongst full group members.
4. If member of subgroup is not completing their assignments by their assigned deadlines, their designated subgroup determines the consequences. These may include but are not limited to: addressing the subgroup’s concerns to the professor, addressing their concerns to full group, ect.
2. Inform group members if you are not able to make a scheduled meeting, ideally 24hrs in advance. Facebook post should be made.
3. Missed Meetings:
Subgroup Meetings Missed:
If member is unable to make subgroup meetings to the point where it is a concern (ideally two meetings unexcused), subgroup should bring concern to specified person. If specified person does not respond to subgroup meeting (3 meetings total missed unexcused), attention to be brought to full group. If specified person does not respond to full group meeting (4 meetings total missed unexcused), professor should be notified. This rules are not definite and, depending on the scenario and how much effort specified person is doing to stay in touch and up to date with group members, the rules may be altered by a consensus amongst full group members.
Full Group Meeting Missed:
If member is unable to make two subgroup meetings, unexcused, group should warn specified person of their concern. Four meetings, unexcused, professor may be notified. Just as with the subgroup meetings, the rules may be altered depending on the situation by a consensus amongst full group members.
4. If member of subgroup is not completing their assignments by their assigned deadlines, their designated subgroup determines the consequences. These may include but are not limited to: addressing the subgroup’s concerns to the professor, addressing their concerns to full group, ect.
October 6, 2013 5-6 PM
Members present: Bryan, Mike, Michael, Alexa, David (late), Steve, Josh, Charles (late)
Members absent: Julie, Kushal
-David gave $
Agenda:
-what does D mean
-finish ppt
-finalize who is presenting
-look at calendar to see what is ahead
-anything we need to order?
-D means Dream
Presenters:
Kushal = Sensors and Control, payload delivery
Structure and skirt = David
Levitation and Propulsion = Mike
Introduction and Objectives = Josh
Power, sensors, control and programming = Alexa and Charles
Meeting Times:
Sensors and Control: Tuesdays 8 pm
Structural and Levitation: Sundays 4 pm
Propulsion and Power: Sundays 6 pm
What is ahead:
October 10: 11-11:20 meeting
October 22 MS #2 +MS#3: PowerPoint Presentation and Written Report
October 24 MS #4: Prototype Fabrication Start
Charles' design for a payload delivery system: Extendable Arm
-closer center of gravity and lighter, easier to maneuver than the arm
-the spring contracts to extend
-wire or switch holding in place before release
-sensor
-servo could move piece in and out
-spring can be made of plastic, legos, or wood; whichever is lighter
-3D print or make our own
-battery
-payload
-propulsion
Charles and Steve work on Payload
*check calculations for propulsion fans
*need to check these so a battery can be found that works
*find out what exactly this extendable arm really is called
Presenters be ready to present!
Members absent: Julie, Kushal
-David gave $
Agenda:
-what does D mean
-finish ppt
-finalize who is presenting
-look at calendar to see what is ahead
-anything we need to order?
-D means Dream
Presenters:
Kushal = Sensors and Control, payload delivery
Structure and skirt = David
Levitation and Propulsion = Mike
Introduction and Objectives = Josh
Power, sensors, control and programming = Alexa and Charles
Meeting Times:
Sensors and Control: Tuesdays 8 pm
Structural and Levitation: Sundays 4 pm
Propulsion and Power: Sundays 6 pm
What is ahead:
October 10: 11-11:20 meeting
October 22 MS #2 +MS#3: PowerPoint Presentation and Written Report
October 24 MS #4: Prototype Fabrication Start
Charles' design for a payload delivery system: Extendable Arm
-closer center of gravity and lighter, easier to maneuver than the arm
-the spring contracts to extend
-wire or switch holding in place before release
-sensor
-servo could move piece in and out
-spring can be made of plastic, legos, or wood; whichever is lighter
-3D print or make our own
- Action Items: (underlining means completed) For PowerPoint Completion NEEDS to be DONE by Thursday October 10, 2013
-battery
-payload
-propulsion
Charles and Steve work on Payload
*check calculations for propulsion fans
*need to check these so a battery can be found that works
*find out what exactly this extendable arm really is called
Presenters be ready to present!
Charles' design for payload Delivery arm:
October 13, 2013 5-5:45 PM
Members Present: Kushal, Charles, Steve, David, Josh, Alexa
Members Absent: Julie, Bryan, Mike, Michael
-reviewed what is ahead MS2, MS3, and MS4
-discussed what the milestones consist of
-plans for the subgroups to have meetings this week in order for them to decide what they need to get done and make a plan to get it done
General Things that need to get done:
-finalize design plans, can have backup plans or other ideas but come to consensus on what we would like to do
-materials, their cost, and where to get them from need to be decided upon
-updating/finalizing the PowerPoint
-figuring out who will contribute what sections to the written report
-checking calculations
-finding all the fans we need
Question:
Is it possible to stop levitation during payload delivery?
Check the Calendar to see the due dates:
October 22: MS 2 and MS 3
October 25: MS 4
Action Items: EVERYONE
-subgroup meetings this week before the next meeting to decide what they need to get done and make a plan to get it done
-also notes should be taken during the subgroup meetings and emailed to Alexa so they can be put on the site/blog
Members Absent: Julie, Bryan, Mike, Michael
-reviewed what is ahead MS2, MS3, and MS4
-discussed what the milestones consist of
-plans for the subgroups to have meetings this week in order for them to decide what they need to get done and make a plan to get it done
General Things that need to get done:
-finalize design plans, can have backup plans or other ideas but come to consensus on what we would like to do
-materials, their cost, and where to get them from need to be decided upon
-updating/finalizing the PowerPoint
-figuring out who will contribute what sections to the written report
-checking calculations
-finding all the fans we need
Question:
Is it possible to stop levitation during payload delivery?
Check the Calendar to see the due dates:
October 22: MS 2 and MS 3
October 25: MS 4
Action Items: EVERYONE
-subgroup meetings this week before the next meeting to decide what they need to get done and make a plan to get it done
-also notes should be taken during the subgroup meetings and emailed to Alexa so they can be put on the site/blog
Milestones coming up:
|
|
|
October 20, 2013 5-8 PM
Members Present: David, Bryan, Kushal, Steve, Mike, Michael, Charles, Julie, Alexa, Michael
-assigned jobs for the completion of Milestones 2 and 3
-searched for propulsion fans
-worked on bill of materials
Ordered:
-propulsion fans
-assigned jobs for the completion of Milestones 2 and 3
-searched for propulsion fans
-worked on bill of materials
Ordered:
-propulsion fans
10.20_meeting_assignments.docx | |
File Size: | 14 kb |
File Type: | docx |
October 21, 2013 7-10:30 PM
Members Present: Bryan,
Members Absent:
Late: Alexa, David, and Mike from shopping
-worked on bill of materials
-worked on circuit design
-worked on finding levitation fan
-worked on designing payload delivery system
-worked on gantt chart
-worked on pseudo code/ code
Members Absent:
Late: Alexa, David, and Mike from shopping
-worked on bill of materials
-worked on circuit design
-worked on finding levitation fan
-worked on designing payload delivery system
-worked on gantt chart
-worked on pseudo code/ code
October 21, 2013
Shopping trip to Home Depot and JoAnn Fabrics
Members Involved: Mike, David, Bryan
Purchased:
-2 yards of rip stop nylon
-3/4" x 36" square dowel
-1" x 36' square dowel
-2 foam boards
-Gorilla Glue
Members Involved: Mike, David, Bryan
Purchased:
-2 yards of rip stop nylon
-3/4" x 36" square dowel
-1" x 36' square dowel
-2 foam boards
-Gorilla Glue
October 22, 2013 7-10:30 PM
Members Present: Bryan, Charles, Steve, Kushal, Julie, Alexa, Josh, David
Members Absent: Michael, Mike
-redesigned payload delivery system
-ordered various materials for the hovercraft
-worked on circuit design
-worked on gantt chart
-worked on writing individual approvals
-worked on bill of materials
-worked on task list
-worked on pseudo code/code
-cad drawing of payload and hovercraft
Ordered:
-battery
-battery charger
-continuous rotation servos
-micro-servo
-levitation fan
-levitation fan guard
Members Absent: Michael, Mike
-redesigned payload delivery system
-ordered various materials for the hovercraft
-worked on circuit design
-worked on gantt chart
-worked on writing individual approvals
-worked on bill of materials
-worked on task list
-worked on pseudo code/code
-cad drawing of payload and hovercraft
Ordered:
-battery
-battery charger
-continuous rotation servos
-micro-servo
-levitation fan
-levitation fan guard
October 23, 2013 7-10:30 PM
Members Present: Bryan, Alexa,
Members Absent:
-finished and discussed finalized Bill of Materials
-ordered various materials for the hovercraft
-mass moment of inertia calculations
-finalized circuit diagram
-finished task list
-finished pseudo code/code
-cad drawing of payload and hovercraft
-formatting of Milestone 3
Purchased/Ordered:
-Arduino Sidekick Kit: Alexa went to Keystone Office
-photo resistors
-stranded wire
-rf transceiver
Members Absent:
-finished and discussed finalized Bill of Materials
-ordered various materials for the hovercraft
-mass moment of inertia calculations
-finalized circuit diagram
-finished task list
-finished pseudo code/code
-cad drawing of payload and hovercraft
-formatting of Milestone 3
Purchased/Ordered:
-Arduino Sidekick Kit: Alexa went to Keystone Office
-photo resistors
-stranded wire
-rf transceiver
bill_of_materials_v3.xlsx | |
File Size: | 12 kb |
File Type: | xlsx |
milestone_3.docx | |
File Size: | 1649 kb |
File Type: | docx |
milestone_4.docx | |
File Size: | 15 kb |
File Type: | docx |
October 27, 2013 5-6 PM
Members Present: Bryan, Charles, Steve, Kushal, Mike, Michael, Alexa, David, Josh
Members Absent: Julie
-collected $10 from everyone present
-discussed what needs to be accomplished for Milestone 5
-discussed what each of the subgroups needs to do in preparation for Milestone 5
Milestone 5 November 14
Members Absent: Julie
-collected $10 from everyone present
-discussed what needs to be accomplished for Milestone 5
-discussed what each of the subgroups needs to do in preparation for Milestone 5
Milestone 5 November 14
100f13_ms_5_preliminary_testing.pdf | |
File Size: | 84 kb |
File Type: |
october 27
Shopping Trip to Home Depot following the Group Meeting
Members Involved: Mike and Alexa
Purchased:
-cotter pins
-1/2" x 36" square dowel
-18" x 18" x 24" cardboard box
Returned:
-3/4" x 36" square dowel
-1" x 36' square dowel
Members Involved: Mike and Alexa
Purchased:
-cotter pins
-1/2" x 36" square dowel
-18" x 18" x 24" cardboard box
Returned:
-3/4" x 36" square dowel
-1" x 36' square dowel
November 3, 2013
No meeting
November 10, 2013
No meeting
bom.xlsx | |
File Size: | 11 kb |
File Type: | xlsx |
November 17, 2013
No meeting
Trip to Radio Shack
Members Involved: Mike
Returned:
-micro servo
Members Involved: Mike
Returned:
-micro servo
November 24, 2013
No meeting
November 26:
Trip to Home Depot and JoAnn Fabric
Members Involved: Mike and Alexa
Returned:
-1 foam board
Could not be Returned:
-1 yard of rip stop nylon
Trip to Home Depot and JoAnn Fabric
Members Involved: Mike and Alexa
Returned:
-1 foam board
Could not be Returned:
-1 yard of rip stop nylon
December 1, 2013
No meeting
December 8, 2013
discussed milestone 8+9
Tiger Team hours for help with ESC 6-6:40
Tiger Team hours for help with ESC 6-6:40
bom.xlsx | |
File Size: | 11 kb |
File Type: | xlsx |
Copyright © 2013 by Alexa Tsintolas. All rights reserved.