Today was the first day of our prototyping and programming challenge. Members started the challenge off by reading the rules and objectives. They then worked in their sub-teams under the guidance of a team captain and started to brainstorm different ways to approach the challenge. The teams debated internally on what mechanisms should be tested and started making a proof of concept. In addition, each team started on a detailed build blog that can be used to keep them on track. Specifically:
Sub-team B decided that they wanted to have a forklift that uses pneumatics to clamp onto the cone as well as keep it upright while delivering it to the table. They decided to base their direction for the day on specific goals that they wanted to achieve in order to get the most points. Sub-team B was able to complete their back plate, drill their forklift on, and get bearing blocks drilled with a good fit. Their next step is to finish the frame and to at least start on attaching pneumatics. Here is an example of their brainstorming:
Sub-team E decided to split their group up with half of the team working on a forklift base while the other started working on roller arms. They were able to get dimensions for a roller arm and start to design it in Autodesk Inventor. The team ran into some issues with aligning to the cone but are planning on re-adjusting their design so that the cone slides in easier. Their long term goal is to create a forklift with roller arms that keep the cone stable while lifting.
Sub-team A worked on brainstorming as many ideas as possible. In the end, they came up with a very simple proof of concept but multiple problems arose from the simplicity of the design. The design is also not complex enough to work on all week, so they plan on expanding the design to be more complex in order to fill the week as well as fix some issues.
Sub-team R brainstormed with one of our mentors, Joseph O’Brien. They worked on creating a good structure by splitting work between certain people and pre-assigning jobs. They were able to make a proof of concept and start to make parts.
Towards the end of the day, we got together to talk about what went right and what we can improve on. One of our strengths was that each team made sure that everyone could comfortably voice their opinions and ideas even if people didn’t agree and was able to come to a final consensus. One of the good things that Sub-team R did was to give people outcomes rather than tasks so that they are working more on their problem solving skills. However, we hope to continue to improve on keeping people motivated and focused on the task by making sure that everyone has a job and continuously setting goals.
Secretary of Communications
Bear Metal Robotics