Presentation Criteria (10/16/24)

 Date

Oct 16, 2024

 Participants

• @Benjamin Williams

• @Zoe Edgington

• @Emily Lopane

• @ziemer

• @Kiana Fan

Rubric: https://moodle.rose-hulman.edu/mod/url/view.php?id=4613072

Questions for McCormack?

1. Business Casual?

   1. Not a requirement – whatever is appropriate for the client

2. Candidate designs?

   1. Not applicable

3. Poster?

   1. Put it together soon before the snapshot presentations

   2. Should be an accurate representation of where we are in our project at that moment

Presentation Criteria

• Put in an Agenda (Add Agenda to Agenda)

• Show Confluence Pages & Diagrams

  • Requirements

  • Maybe software diagrams

• Summarize The Outcomes?

• Live Demo (Demonstrate something has been done)

• Must be useful!!!

Rubric:

• Design team considers stakeholders

  • Talk about interviews with stakeholders, maybe talk about personas?

• Complete set of basic and performance requirements

  • Just talk about what we targeted for Alpha bot, and eventually want to change

• System is represented clearly and completely, and have candidate ‘solutions’

  • We don’t really have mechanical candidate solutions, but maybe software can tlak about different things, or maybe we can talk about different configurations for class room settings vs. hobbiest

  • Maybe show system diagrams?

• Translation of product requirements allow for judging of conceptual designs

  • So talk about mechanical requirements and how we hit them (<30 lbs, etc)

• Design team performed substantial learning and converted knowledge into project assets that will be

  • Get ROSS running, and have physical parts of robot

• Goal is clearly stated and valuable for project

  • Does this mean just get feedback, and show that we are knowledgeable?

• Design review was structured to get substantial value - structure includes audience invited, information provided, questions asked, and discussion prompted

  • Tough to view how this is done, are we meant to collaborate with Bryson mid presentation?

• Language shows knowledge; very good word choice; persuasive. Visuals attractive, excellent quality. Excellent rapport with audience; very effective listening and answering Q&A

  • Make attractive visuals, not sure exactly what is meant by this.

Game Plan:

1. Introduce Goals/Agenda for the meeting

2. System Overview

   1. What's on the robot

      1. Mechanical talks about fabrication

         1. Ensuring simplified system

         2. Designing for 3D printing

      2. Electrical talks about power system

         1. Simplifying connections

      3. Beaglebone setup

         1. “Wireless configuration”

            1. Out-of-date drivers for current kernel version

            2. Switching hardware to USB interface

               1. Building drivers for USB wireless

         2. “ROS configuration”

            1. No ROS distributions prebuilt for 32-bit ARM systems anymore

            2. The saga continues

      4. Software talks about ROS

         1. figuring out how ROS works

         2. Using GPIO library

3. Status update and Live Demo

   1. Here’s what works

   2. Here’s what we are still working on

      1. Packaging electrical system efficiently

      2. Belt tension

      3. Building ROS on BBB

      4. Testing ROCKO project on the robot

      5. Sensor integration

   3. Next quarter preview

4. Questions and feedback

Presentation Agenda (for real):

1. System/design Overview

   1. Mechanical System

   2. Power System

   3. Beaglebone setup

   4. Software

2. Live Demo

   1. Run Motors using Python script

   2. Run ROCKO ROS environment on laptop

3. Next steps

4. Questions and feedback

Feedback:

• Analysis of electrical and mechanical components-- are they suitable for a “beefier final version”?

• Propose a solution for the onboard computer that accounts for the reality of open-source development

• Put mechanisms in ROS sim

• Install sensors and get some data recorded, are readings low-quality, what kind of patterns do we notice?

• Hardware needs to be SOLID!!!

• McCormack: Unclear on “how hard the hobbyist user is going to crash”-- does there need to be a mechanical solution for people getting to grips with the system that can prevent them from breaking things?

 Goals

 Decisions

1. Likely not doing Slides
2. Present whatever we have (hopefully full mechanical system)