Design Tool & Skills Workshop Overview ppt - https://drive.google.com/open?id=1zf7gYE5hUr99_PSHuaGi2hdNMC6mPWwokYRwIHS-exQ

Design Tools & Skills Workshop Training slide-set & materials - https://drive.google.com/drive/folders/1gZm-NWUnUH1x-METmRAdF1emFsCwnWim?usp=sharing

Upload Technical Presentation Slides here: https://docs.google.com/forms/d/e/1FAIpQLSfqNfbOelW7RIG3-Wdw_nQDgBOKN0jE0zvybtqRBFWPNW8hPQ/viewform

Do you ever stop to think about what being at the UCLA Samueli School of Engineering actually means? It’s more than just being at one of the most prestigious universities in the country and taking classes with distinguished faculty.

As every UCLA student knows, it means learning more than you ever thought possible. It means being challenged to grow and gaining the skills to solve not just today’s problems, but also tomorrow’s problems. It means being able to engineer change.

Before going out into the world to engineer change, you first need to gain engineering experience. Some of you might have experience already, but one of the main goals of the program is to provide every student with that opportunity. With that in mind, we have designed the Hack at Transfer Bridge to UCLA Samueli to help you practice skills that every engineer needs, regardless of major.

Over the course of the next three days, your team will develop a mechanical arm that can be controlled via Bluetooth. This iterative project will be created with the provided materials (see below). The completed mechanical arm must be able to pick up a selection of small objects unassisted, receiving input from a user’s smartphone. Teams will be awarded points for the number and variety of objects that their prototype is able to place into the designated receptacle. Additionally, each team will be required to give a short technical presentation on their design for a panel of judges.

Your prototype MUST arrive at the competition venue no later than 3 PM on Saturday, September 21 to be eligible for the competition.

All students will be required to use the pre-designed arena. All arenas will be set up in an identical manner with the same number and type of objects placed at the same locations throughout. Teams will be allowed to test the abilities of their prototype with the different objects in the arena before officially competing. Teams will be assigned to 1 of 3 arenas for testing and competition. No team will have a monopoly on any of the test fields and use of the test fields will be regulated by a sign-up sheet with 15 min time-slots. If there isn’t another team signed up for the following time slot, the team testing at the time can continue testing until another team requests to use it.

The arm can be designed and created entirely using skills taught during Transfer Bridge. Any notes taken on the provided workshops may prove to be helpful. Additionally, undergraduate mentors will be present for the duration of the competition to answer technical questions. Research on different designs is permitted, however, replicating any project found online or elsewhere piece-by-piece is prohibited. Replicating the test model is also prohibited.

Mechanical parts can be 3-D printed in the MakerSpace and Solidworks will be available for the duration of the Hack-a-thon in the computer lab. Other miscellaneous parts, like screws, nuts and bolts, in the MakerSpace will also be available for assembly of your prototype. Please refer to the table below for information on access to tools.

A selection of JavaScript and HTML/CSS has been blackboxed and can be found HERE. Remember that these files are not exhaustive, and can be improved upon as desired. The Evothings environment and a Bluetooth module for Arduino will be used to implement the Bluetooth functionality. Training materials from our skills workshops can be found HERE.

Each team will receive:

• 1 Arduino UNO + USB Cable
• 12 male to male wires
• 8 female to male wires
• 12 22-gauge wire pieces
• 1 Bluetooth module
• 2 large servo motors
• 2 small servo motors
• 2 stepper motors
• 2 breadboards and circuit components
• 5 ft of PVC pipe

*Do NOT break your servos or motors. We have a limited supply.*

SEASnet Lab

• Bridge Mentor or Staff must be present when students are using the lab. Door will be locked when unoccupied.
• No food or drink allowed
• Use your given SEASnet account only
• SEASnet Lab policies: https://www.seasnet.ucla.edu/seasnet-lab-policies/

MakerSpace

• See Gabe for 3D printing
• Bridge Mentor must be present when operating power tools or machines
• Posted guidelines for personal protective equipment (PPE) must be followed at all times
• Generally: closed-toed shoes and long pants recommended, hair bands required for long hair
• No food allowed, water bottles are OK

Safety 101

• Our goal is to have zero injuries or accidents
• Listen to instructions or reminders regarding safety and PPE given by the mentors
• Start each task by thinking about potential hazards and the impact to those around you
• When in doubt, speak to a Bridge staff or mentor
• Injuries must be reported to a mentor immediately
• A first aid kit is available
• While we are here to compete, we must always prioritize safety

Students will NOT be allowed to bring in personal hardware components, as this provides an unfair advantage to teams with members that have worked on similar projects who may have more advanced components. Use of outside software is allowed for design analysis, however Transfer Bridge will not provide training for any software other than the ones mentioned previously in workshops. Since there is ample time given during the day for students to work on their projects, it is expected that students are not working with any software or coding after Hack-a-thon hours. Students are encouraged to rest, relax, and get enough sleep to be ready for the next day during their limited free time.

The teams have been preselected by the Transfer Bridge mentors. Please remember that every member of the team must contribute significantly to at least one component of the Hack-a-thon. Teamwork is an essential part of engineering and will be critical to each team’s success during the Hack-a-thon. Team assignments are non-negotiable.

Your team must register their official team name and team icon by completing the online registration form no later than 11:59PM on Wednesday, September 18, 2019. Refer to the instructions in the form for how to format the team icon and Please choose school appropriate images https://forms.gle/yU1AZf7KqBcoRdWX6.

1. Your prototype must physically be at the Competition site in Engineering VI by 3 PM. No additional work will be allowed past 3 PM.
2. Each team will be provided 5 minutes to install their prototype to the arena when it is close to the team’s turn. Your prototype MUST couple to the arena mount. Here are the guidelines:
   1. The base-board to mount each prototype to the arena is an 8”x8” platform
   2. Bolts are located on the diagonal, with the spacing of the bolts dependant on the board. Boards Blue and Gold have bolts 8” apart. Board Bruin has the bolts spaced 7” apart.
3. Each team’s prototype will have five minutes to compete. Every object lifted by a team’s machine and deposited in the box will receive a set number of points, as outlined in the table below.

Following their prototype competition, each team will be required to give a 3-5 minute technical demonstration of their project. Each member of the team must say at least one sentence summarizing their contribution to the overall project.

Technical Presentation Guidelines

We have asked our judges to look for and score the following elements during each team’s technical presentation:

• Description of manufacturing process and design choices
• Description of improvements and iterations
• Theoretical and empirical rationale for design choices
• Technical bugs to fix and improvements to be made on design
• Participation of each team member
• Professionalism and coherency of presentation

Awards

First Prize - The team determined to have the best total score will be the winner of Hack at Transfer Bridge to UCLA Samueli. Points will be tallied from the Prototype Task Challenge and the Technical Presentation. Each team member will win a $100 UCLA Store Gift Card.

Best Prototype Task Challenge - This award will be given to the team with the highest number of points following the Task Challenge portion of this competition. Each team member will receive 50$ to the UCLA Store.

Best Technical Presentation - Following the Technical Presentation portion of Hack at Transfer Bridge to UCLA Samueli, the team determined by our panel of judges to have given the best presentation will receive this award. Each team member will recieve 50$ to the UCLA Store.

Disqualifications

• Teams found plagiarising will be automatically disqualified. Such actions include:
  • Replicating any project found online or elsewhere piece-by-piece
  • Replicating the test model
  • Downloading CAD files, individual parts or assembly.
• Working outside Hack hours - As stated before, do not take parts home t0 work on the project outside of the allotted time. Please go home and sleep :)
• Not following facility rules and guidelines (such as safety guidelines).
• Damaging other team’s prototypes or purposely undermining another team’s progress
• Not contributing to the team.

Please ask a mentor if you have any questions!

All meals will be served in Boelter Hall 2808. The Snack Shack will also be in Boelter 2808 and have snacks and coffee during non-meal periods. Breakfast will not be served.

Please post any questions to the #hack channel in Slack. Mentors will try to answer the questions as they appear as long as the same question hasn’t been posted previously. Every competitor will be invited to this channel before the start of the competition, and all are advised to monitor this channel for the duration of Hack at Transfer Bridge to UCLA Samueli.

• Do not make shoulder too long. Torque will apply too great of a force on the servo for it to act reliably.
• Focus on JavaScript rather than HTML/CSS; functionality over design
• Ensure clearance between parts - measure twice, print/cut once
• Make sure you can talk about the parts you contributed ( you don’t have to be a master of every part)
• Try to finish at least the skeleton code and the CAD of the prototype by the end of the first day to ensure that there is time for you to test and iterate if everything doesn’t go as planned