Team Status Report for 2/21

This week, Bing crushed our Design Review presentation. After class, Hyong, our advisor, pointed out a critical component to our game, one which we identified ourself to be make or beak: the batting experience.

We aren’t trying to make this a baseball simulator, but we still feel we can achieve an intuitive, skill-based batting experience, similar to how other arcade baseball games do. Pitch delivery will be predictable, with just enough variability in speed and movement to make it difficult. Bat swing to flapper actuation will be accurate and low latency. Scoring outcomes will depend on how well-timed swings are.

A few risks that we discussed this week were:

  1. Pitch speed: Our current pitch system will be powered by belt-driven linear actuators that are powered by NEMA17 motors. By increasing our motor driver strength and operating at the upper end of current ratings, we believe we will get RPM from the motors and thus sufficient pitch speed. If not, we have discussed a machine similar to the “JUGGS machine” that is used to sling American footballs, using 2 DC motors and wheels. Another alternative would be to rely purely on gravity for the ball to fall fast, and increase the game board slope.
  2. Ball return: After a ball falls into a scoring pocket, it needs to be routed back to the “Pitcher’s Mound”. This is a challenge, since we want the ball to fall through the playing surface so that it can be detected by break-beam sensors, so it will need to climb back to the surface plane while avoiding under table obstructions like the Gantry. We discussed a few different methods to resolve this, including chute like paths for the ball to fall through the surface, then come back out down below, relying on the fact that the game board will be angled towards the batter. Once the ball pops back on to the surface below, the gantry can drag the ball back to the mound. An alternative would be to have shallowed grooves rather than fall-through pockets, again taking advantage of gravity and geometry to make a convenient pickup spot for the ball. If all fails, we can have a Air Hockey style puck drop-in and return, where the pitched needs to place the ball on the mound after it is returned to them below in a slot.

Little has changed with our design, as we are still waiting to receive our first round of components. Our schedule has changed slightly, as the gantry equipment won’t come in until after Spring Break. Thus, Aiden will shift his focus to the Coupling Mechanism and Game Board for now. The schedule here reflects that: gantt_chart_2_21

We look forward to beginning the development of some of our subsystems and finalizing the designs for others.

Aiden’s Status Report for 2/21

What did I accomplish?

I ordered my components for the gantry, starting with one axis. I began familiarizing myself with the control software I will be using, including FluidNC and G-Code. I also developed a 3D model of the game board.

Selecting the gantry took a lot of work, as it is a novel space to me, and it is quite complex. I tried to ensure the gantry architectures, firmware, motor controller boards, and motor drivers would be compatible and reach our performance targets.

Am I on schedule or behind?

I’m slightly behind schedule because my parts won’t arrive for another 2 weeks. Some of my parts weren’t approved when I put the order requests in, and some required much more research to understand their tradeoffs and compatibility.

What do I hope to complete in the next week?

I want to work on the coupling mechanism design, with a tentative parts list and at least 2 solutions to propose to my teammates.

Aiden’s Status Report for 2/14

What did I accomplish?

I did research on Gantry solutions, from fully assembled systems to various levels of “Do It Yourself”. I devised a plan to purchase the componentsseparately from Amazon and assemble them myself, taking inspiration from OpenBuilds, an open-source, DIY CNC machine community.

I worked with our team on our Design Presentation, contributing significantly to the block diagrams and Gantt chart.

Am I on schedule or behind?

I’m slightly behind where I wanted to be by today. I anticipated having my parts ready to order by Monday, but I still have some questions regarding the gantry design and have found little help from the CMU community with it.

What do I hope to complete in the next week?

I want to order all of my components for my gantry and have build plans ready for the Pitch subsystem and the game board.

Aiden’s Status Report for 2/7

What did I accomplish?

This week consisted mostly of project planning. I helped finish up the team report, developed the Gantt chart, and did some research on my subsystem, the Pitch subsystem.

Am I on schedule or behind?

I’m on schedule. We just developed our schedule around where we sit as of today.

What do I hope to complete in the next week?

I hope to have my first iteration of design done for my subsystem. This will consist of a hand drawing, a block diagram, and a parts list. I also want to work more on the Gantt chart.