HAcK is designed to provide incoming engineering transfer students an opportunity to 'get their hands dirty' on a technical engineering design project, to utilize their math, science, and engineering concepts, to gain some professional development, and to have some fun.

During Basic Training, HAcKers received a crash course on engineering design tools that they will use during HAcK's technical competition. Through this experience you will hone these skills, better understand the iterative design process, and engineering work.

HAcK is designed to challenge you. Not just with utilizing the skills you've learned; but, also in applying them in an effective way with the time that you have. Let's see what you and your group can do in these few days. What will you walk away with?

Through this challenge you will learn what it's like to be an actual engineer! How are you going to deal with hardware issues? How are you going to work with someone on the other side of the planet? How are you going to make sure that everyone has something to do? But most importantly, you guys are going to have fun with your friends in the accelerator program and build something all by yourself.

Friday, August 13, 2021 | 6 - 7 PM - Welcome, Orientation, and Introductions

Friday, August 13, 2021 | 7 - 9 PM - Hack Training Day 1: CAD

Saturday, August 14, 2021 | 9 - 12 PM - Hack Training Day 2: CAD

Tuesday, August 17, 2021 - Thursday, August 19, 2021 | 6 - 9 PM - Advanced Training

Friday, August 20, 2021 | 6 - 7 PM - HAcK Reveal & Teams

Friday, August 20, 2021 | 9 PM - Sunday, August 22, 2021 | 9 PM - 2021 HAcK at the Accelerator for eTransfers

Sunday, August 22, 2021 | 9 PM - Deadline to submit project for competition

Thursday, August 26, 2021 | 5 PM - Deadline to submit design review presentation

Saturday, August 28, 2021 | 9 - 12:30PM - HAcK Judging Q&A

Saturday, August 28, 2021 | 3 - 5PM - HAcK Awards Ceremony

Please read the entire technical challenge prior to starting.

Part I - Prototype Build, Test, and Performance

For this part, there are submissions required for every italicized bullet point below. More information in Submission Guidelines

First, build the base car provided to you using the instructions at this link. There are extra 4-40 screws if needed.

The technical challenge is to transport and unload an object with an Arduino-controlled car that you will construct. To complete the challenge, teams will have to navigate their vehicle through the field of play in the following tiers (you must do the tiers in order):

Tier 1: Drive the remote-controlled car with Bluetooth through a Python Script.

Tier 2: Assemble a joystick controller to drive your remote-controlled vehicle.

Tier 3: Augment your car to make it drive autonomously.

For the RC tiers, Tiers 1 and 2, you must use what you learned at training to make and record (take a video and upload to YouTube) your car do the following:

1. Make simple driving motions, like forward, stop, backwards, turn

2. Make simple driving motions, like forward, stop, backwards, turn while carrying and unloading an object

3. Must drive your car in a track/course that we specify (this requires construction of a course). You must show your car working in Maze 2.

4. Must drive your car in a track/course that we specify (this may require construction of a course), while carrying and unloading an object. You must show your car working in Maze 2.

*Please follow the Submission Guidelines below. Note, for this step if you are able to guide the car in directions that are not limited to forward, left, right, backwards - notify us, that's awesome!

For the autonomous tier (tier 3), you must record your car:

1. Navigating a narrow maze (should work for any of the mazes we have) properly, with no human interaction. You must show your car working in both mazes.

2. Solve the maze, and by the maze's end, your car should stop and unload an object. Both Mazes.

3. Navigate a narrow maze properly. By the maze's end, the car should stop and unload a round object (such as a ping pong ball or an egg). You must show your car working in both mazes.

Your team must have a Google Drive that is public. The Google Drive will contain the code and a video of each of the above bullet points. The files must follow a naming convention as follows or we will not be able to grade them. Please limit the videos to 20 seconds, we will only be looking at them for that long:

<team_name>_Tier#_Step#_code

<team_name>_Tier#_Step#_video

When you take your videos of the drive, make sure the RC working method is in the video frame, to display your RC as operational.

Part II - Prototype assembly in SolidWorks

Version 1.0 - Prototype

1. Look thru the given parts on SolidWorks and make the parts that have not been given to you. These include the 2 back wheels, the caster wheel, and the L mounting bracket. Make engineering drawings for each part that you make.

2. Assemble your car in SolidWorks with all of the v1.0 parts (these include your 3 created parts), including all the necessary mates and constraints to ensure the car behaves as it would in the physical world, and for your Hack.

FEA Study

3. Conduct a study on the following 3d printed parts: "Platform" and "Mount". The "Mount" has 3 configurations, 0 ribs, 1 rib, and 2 ribs. You will analyze each configuration. For each of the studies, make your Word Report and add in your own Conclusion and Description sections.

Only until you figure out how to put the pieces together for your platform-servo-mount system will you understand what fixtures we are looking for on the parts, in addition to the locations and magnitudes (less important than locations) of your load. For your material on the platform, the "wood" options might not have a yield strength. Try any common material if you cannot find any usable wood option. For the material on the mount, there are a few plastics with yield strength. Select "Delrin" or "Acryllic".

In your conclusion, you should discuss:

3. 1. Discuss your Stress, Displacement, and Strain results.

   2. Answer these questions:

      1. Is this part safe? By what factor of safety?

      2. If it’s not safe, what is the maximum allowable applied force to be just barely safe? What is the maximum allowable force for a factor of safety of 2, 5, and 10?

      3. Where is the max stress/displacement/strain? (Include a pic in your conclusion)

      4. Make sure you compare the 3 configurations of the "Mount" in one of the Word Reports.

Version 2.0 - Real World Dump Truck

4. Teams must iterate on the version 1.0 to produce an improved model that includes alterations and features to resemble a functioning dump truck.

a. At a minimum, this must include rails on the platform to hold the object in place and a pick-up arm system on the side of the car to hoist up a trash can. Create complementary engineering drawings for this model.

• Other added functionalities may include: a stronger framework to hold up the platform (rather than the single servo arm), a cabin for the driver with a moving door, etc.

Part III - Create a website

Finally, for the entirety of the project, we want you to create a website (you do not need to host it online) using html, Javascript, and CSS that documents your development process. Think of the website as a diary for the car, you will document your entire construction process. All teams MUST include a video of your project progress, this video can be included on your website on Thursday, August 26, 2021 at 5 PM. However, the rest of the website must be completed at this point (i.e no stylistic changes or new content can be added to the website). Highlight what difficulties you had, what roadblocks you hit and your successes!

Deadline for Parts I, II, & III is 9 PM on Sunday, August 22, 2021

Part IV - Design Review Presentation & Q & A with Judges
Teams will have until Thursday, August 26, 2021 @ 5PM to record and submit their Design Review Presentations which will be played for the judges on Saturday, August 28, 2021. Judges will watch your videos and ask your team questions about your prototype and design logic. Teams will sign up for a timeslot for judging. Please follow these Design Review Presentation guidelines:

1) 10 minutes max video presentation (teams will have an additional 3 minutes for Q&A with the judges, for a 13 minute total slot)

2) Content that MUST be included:

• Website demonstration with:

a) Pictures of your prototype

b) Performance videos of all tiers completed (videos can be played at higher speeds)

c) Information about your team

• Prototype model and circuits with performance videos

• Code from one part of one tier with an explanation of your design choices (libraries used, algorithms, etc), efficiency, and documentation

• Controller design review with explanation of CAD design, outcomes during assembly, and ability to house interior.

• Fun "Project Progress" video which documents experience making prototype

- For your reference: https://www.youtube.com/watch?v=mvz3LRK263E or https://www.youtube.com/watch?v=tqsy9Wtr1qE

• Challenges faced and how you managed through it

• Next steps in design

3) All team members must speak an equal amount in your video

4) Save files as: DRPresentation_TeamName

5) Upload to your team's Google Drive

Please reach out to the mentors if there is confusion about the project. Remember, asking us early is preferable to realizing that you have been misinterpreting the project. Additionally, please refer to FINAL COMPETITION JUDGING & GUIDELINES for more specifics regarding this project.

Best of Luck! Have Fun! If you get discouraged/overwhelmed realize that this is meant to challenge you.

Remember, your performance in this Hackathon is not what defines you. The mentors designed this project to be challenging for even the most experienced student. It is totally ok (and entirely possible) if you don't manage to complete all of the tasks listed above. Do your best, learn lots, see what you're capable and have fun! You guys are already taking the right first steps by just participating in this competition. We can't wait to see what you guys come up with and to hear your 'breaking through walls' stories!

The maze path should be no wider than 1 ft at any point.

You can build the maze with any rectangular object handy in your house. We recommending reusing your cardboard boxes or books.

Include a picture of what your maze looks like.

For tier 1 & 2, drive/video your prototype on Maze 2.

For tier 3, drive/video your prototype on Maze 1 & 2.

Below, the "2ft" and "1ft" are minimum dimensions.

1. Team Registration (Due Friday, August 20, 2021)

• Must include full names of all teammates

• Must include pictures of all teammates

• Must include your team name

• Save file as: FirstLastName(teammate 1), FirstLastName (teammate 2), FirstLastName (teammate 3)_TeamName. Example JoeBruinJosieBruinMonkeyBruin_3Stooges.jpg.

• Upload file here: https://forms.gle/kv6aW5HTHgeep56x9

The following submissions will be added to your team's Google Folder. You will upload the link to your team's Google Folder in the Team Registration above. Please make sure it is viewable and NOT restricted.

2. Photos of your prototype (Due Sunday, August 22, 2021 @ 9 PM)

• 6 Photos from every angle. Above, Below, Front, Back, Left and Right.

• A clear image of the platform-servo-mount system

• Clear images for each tier's circuit board

• Photos of the maze used for every drive

• Save file name as PrototypePhotos_TeamName (save all photos as one file in a single pdf/single location)

• Submit your photos collection in your Google Drive.

3. In your Google Drive you must have the following files, note the videos can only be 20 seconds (Due Sunday, August 22, 2021 @ 9 PM)

• <team_name>_Tier1_Step1_code

• <team_name>_Tier1_Step1_video

• <team_name>_Tier1_Step2_code

• <team_name>_Tier1_Step2_video

• <team_name>_Tier1_Step3_code

• <team_name>_Tier1_Step3_video

• <team_name>_Tier1_Step4_code

• <team_name>_Tier1_Step4_video

• <team_name>_Tier2_Step1_code

• <team_name>_Tier2_Step1_video

• <team_name>_Tier2_Step2_code

• <team_name>_Tier2_Step2_video

• <team_name>_Tier2_Step3_code

• <team_name>_Tier2_Step3_video

• <team_name>_Tier2_Step4_code

• <team_name>_Tier2_Step4_video

• <team_name>_Tier3_Step1_code

• <team_name>_Tier3_Step1_video_Maze1

• <team_name>_Tier3_Step1_video_Maze2

• <team_name>_Tier3_Step2_code

• <team_name>_Tier3_Step2_video_Maze1

• <team_name>_Tier3_Step2_video_Maze2

• <team_name>_Tier3_Step3_code

• <team_name>_Tier3_Step3_video_Maze1

• <team_name>_Tier3_Step3_video_Maze2

4. Website Code (Due Sunday, August 22, 2021 @ 9 PM)

   • Put a zip file of all your website code in your Google Drive titled <team_name>_website.zip

5. Video of Project Progress (Due Thursday, August 26, 2021 @ 5 PM)

   • Save file as <team_name>_ProjectProgress

   • Submit the video on your Google Drive.

6. Register for Design Review Judging timeslot (Due Thursday, August 26, 2021 by 5PM)

   • Pending

The CAD submissions will be added to your team's GrabCAD project. Make sure there is good file organization. Make sure that there are distinct Assembly v1.0 and 2.0 versions.

7. All CAD files (Due Sunday, August 22, 2021 @ 9 PM)

   • New parts for Assembly v1.0 (wheels + caster wheel + L mounting bracket) + associated engineering drawings

   • Assembly v1.0 zip file - current prototype version

     1. Needs an associated assembly drawing + exploded view

   • Assembly v2.0 zip file - actual dump truck version

     1. Upload your new parts that you made for v2.0, as well as any v1.0 parts that you have edited, along with the associated engineering drawings

     2. Upload your final Assembly v2.0 with associated assembly drawing + exploded view

8. All FEA Word Reports, as pdfs, for the FEA studies of the 3d printed objects "Mount" (all configurations) and "Platform" (Due Sunday, August 22, 2021 @ 9 PM)

   • The 4 Word Reports

   • Do NOT submit all of those "Static" files with weird filenames, we only need your pdfs

   • Reupload the 2 SLDPRT files (Mount and Platform) so we can see your analyses in one of the above folders

All major communication will be done through the HAcK Discord Team Channel. Various help channels is made to provide help by mentors. Please be noted that ONLY general questions would be answered during the HAcK. Mentors are NOT available to debug during the HAcK COMPETITION. Before the start of the competition, you will be placed into your team channel. Please also utilize all the online tools for file sharing and progress logging such as GrabCAD, Git, and Drive.

During the HAcK competition, we strongly recommend all HAcKers to turn on notifications for your team channel and be active on Discord to facilitate communications. Get the Discord app on your mobile device is recommended.

For an invite to the HAcK Discord server, please email: rrossmango@gmail.com

1. Be respectful of others and your teammates.

2. Be aware of teammates in different TIME ZONES and try the best to coordinate the tasks earlier.

3. Students are NOT allowed to be in each other's physical presence while at HAcK.

4. Turn ON notifications for your team and announcement channel at all time during HAcK.

5. CHECK other channels on discord regularly, as there may be information to help your group.

6. Communicate with your teammates as if they are right next to you even they are not.

7. Each member MUST contribute to the project.

8. Please sleep (recommended at least 6 hours per 24 hour period).

9. TRY your best and HAVE FUN!

10. Please contact Wes Uehara, Program Director, wuehara@seas.ucla.edu if there are any issues with rules of engagement.

A centralized location will be designated for one person on your team to pick up parts and supplies. Information will be provided as the HAcK competition approaches.

Please wash your hands every time after working on the prototype or handling the supplies.

Your parts list, data sheets, and helpful information will be provided at the HAcK Reveal.

If your part malfunctions, you can contact Wes in the #Parts Channel in the Discord Server to see if a replacement is available.

Full Parts List, with BT Parts included

Students will NOT be allowed to bring in or use personal hardware components or personal equipment (3D printers, etc.) otherwise specified, 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 or libraries is allowed for design analysis or algorithm enhancement. However, Accelerator Mentors will NOT provide training for any software other than the ones mentioned previously in workshops.

The teams will be selected by the Accelerator mentors and shared at the HAcK Reveal. Please remember that every member of the team must contribute significantly to at least one component of the HAcK. Teamwork is an essential part of engineering and will be critical to each team’s success. Team assignments are non-negotiable.

Things to do:

1) Exchange contact information & find your team channel on Discord.

2) Figure out where in the world everyone is and what time zone your teammates are in.

3) Figure out your resources. Your team is going to need to divide and conquer. Who is going to be responsible for what? Who is good at what?

4) Work backwards from the deadline to determine: a) what has to happen and in what order, and b) create a timeline to make sure you have time to make your videos and submit them in time.

5) Decide on a team name and submit your registration (see Submission Guidelines).

Along the way, please contact Wes or the mentors if you are having a problem (aside from project progress) that you need help with. While mentors will refrain from providing you solutions as you are working on your HAcK project; we will provide you Mentor Office Hours through the duration of HAcK. Mentors will be available during these hours to answer questions and provide guidance:

Saturday, August 20, 2021 | 2 - 3 PM

Allaine Taduran

JJ Choon

Saturday, August 20, 2021 | 4 - 5 PM

Ryan Rossmango

Sunday, August 21, 2021 | 9 - 10 AM

Aditya Mishra

Harvey Yu

Chris Jawetz

Mentors will also be checking Discord through the duration of HAcK.

1. Your materials for Part I, II, and III MUST be uploaded to Hack FINAL Submission no later than 9:00 PM on Sunday, August 22nd. Your materials for Design Review Presentation MUST be uploaded to HAcK Design Review Submissions no later than 5:00 PM on Thursday, August 26th. Both deadlines and all criteria in the Submission Guidelines (see above) must be met to be eligible for the competition. Please check Presentation Material Submission Guideline section for submission requirements.

2. RC and autonomous tier goals

• Tiers completed along with pictures and videos.

• Speed at which tiers were completed with an unloading platform

  • Time will be tracked through submission timestamps

• How well the given map/field is completed.

  • The car should not be running into walls or dropping your object before unloading

  • Autonomous cars will receive bonus points for being able to run along a straight path

• For each tier, need front, top, right, bottom, left, back, isometric view pictures of:

  • Prototype without platform system

  • Prototype with platform system (front, top, right, isometric)

  • Need clear image of the circuits you used

• For each RC tier, need a video of the car doing:

  • Simple driving motions

  • Driving through track

  • Simple driving motions + unloading

  • Driving thru track + unloading

• For autonomous tier, need a video of the track

  • With unloading platform

  • Without unloading platform

  • Make it go straight as possible

• Must have a picture of your platform-servo-mount system

3. Prototype assembly

   • • Circuitry

       • Must correctly use resistors to prevent burning out of components

       • LED for when platform is unloading for each tier

       • LED for when car is in motion

       • Tape is allowed for sensors + battery.

     • Coding

       • Good Arduino coding practices, including comments

       • Need to upload all coding files in organized fashion for each tier

     • Mechanical

       • All mechanical framework pieces must be fastened down properly. This includes the Chassis Base as well as the platform-servo-mount system. There should be no motion (aside from the rotating platform). If you think it's mechanical, it probably is: it must be tightened properly.

       • You will not be using each screw.

       • Platform-Servo-Mount system, what we are looking for:

         • Framework cannot use tape/epoxy without resulting in point deductions

         • Everything is tight, nothing moves/jiggles/wobbles. Of course, the platform can rotate.

         • Platform isn't hanging over the edge of the car, should be positioned relatively over the center

         • Car must drive with the object on (so the object should be sitting horizontally), and then you must unload it safely

         • The object should unload like a dump truck would (the payload pivots upwards to let the objects fall out)

(This consideration is not as important as these other points, but we have asked you to make a dump truck nonetheless)

4. Google Drive folder

   • • Must have main folders for each tier

       • Named “Team##_Tier#” (ex: Team01_Tier1)

         • Note: Should have smaller folders inside each main tier folder, such “IR-remote-pictures” or “IR-remote-platformtier”. Should NOT just have every picture + video + coding file thrown into the folder. Must have clear and reasonable organization.

     • Must upload all your pictures/vids/code files/circuit pics

5. Controller design and functionality

   • • Each team member must submit pictures of their controller from front, top, right, and isometric views

     • Material usage, did your controller need supports when printing?

     • Presence of proper supports in design

     • Functionality of joystick mount design, did you need tape/epoxy anywhere?

     • Functionality of sensor and cable holes

     • Functionality of top cover

       • Must cover the entire board and expose joysticks for full motion

     • Proper sensor position outside controller

     • Space efficient interior configurations

6. CAD

   • Assemblies of:

     • Version 1.0 - using all premade CAD designs + the parts your team introduces (back wheels, caster wheel, L mounting bracket)

     • Version 2.0 - using your own iterated designs of Version 1.0 parts to create an improved model, as well as any new parts

   • Must have drawings for all new and updated parts (any part that is different from the GrabCAD parts we provide)

   • Upload all files to your team’s GrabCAD project. The files must be zip files for assembly. Naming convention has to include team number + which part it is. Must have good file organization. You can upload based on which tier you are working on.

     • Note: not all parts for v1.0 are given. Teams must make exact replicas of the parts that are not given.

     • Assembly v1.0 must be fully mated

     • Make your new parts in folder v2.0 and drawings for each new/updated part

       • Include new features for your parts to make the car like a real dump truck

       • Platform must have rails on it

     • Assembly v2.0 must be fully mated and uploaded in a zip file

       • Must function as closely to a realistic dump truck

       • Must have moving payload that is unloaded

       • Must have four moving wheels

       • Side rails must move to bring a trash can up and doors must open

       • Include a bill of materials

     • Sketches and assemblies must be fully defined and constrained according to desired motion.

7. FEA studies of two parts: platform and mount

   • Must analyze three configurations of the mount: 0 ribs, 1 rib, 2 ribs

   • FEA Word report on each study with proper analysis

     • Discuss your stress/displacement/strain results

     • Max force/stress/deflection - which areas on the part are of most concern? Show where the locations of maxima are.

     • Questions to consider: Are we safe? Do we need to redesign? What is the factor of safety?

       • If not safe, what is the maximum allowable force to be just barely safe? What is the maximum allowable force for a F.O.S of 2, 5, and 10?

     • Add conclusion and description sections. In one of the Word Reports, you must compare the 3 configurations.

8. How does your website look/is it completed?

   • • Pretty (aesthetically pleasing), interactive (buttons, motion), creative + good style, hits all what needs to be hit (purposeful, with documentation + video links + each tier + pictures w/ captions and timestamps)

     • Include a fun Michael Reeves-like video (try to make it funny! Let your creative side show). This video will be shown at your Design Review

     • Include a team’s ABOUT page for everyone’s bio and experience

• Do NOT just upload pictures/videos of your final project. Your website should document your ENTIRE process, from development of the car all the way to the final drives - show us steps you took, parts you used, and explain how you put it together in small captions, etc. must include documentation for how you put the prototype together, all tiers

  • You need the required videos in the "Submission Guidelines" section, you may add more videos of other findings/breakthroughs if you'd like

8. • • Good coding practices + well documented code

9. Design review/presentation, 10 minutes prerecorded, 3 minutes for live Q&A

   • • Slideshow with pictures and short summary of each tier. Discuss your project's pipeline.

     • Video of your car doing every task (italicized bullet point in the spec).

     • Show your "fun/creative" video.

     • Summary of testing, debugging, and iterations