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.

Vivian’s Status Report 2/21

This week, we worked on the presentation for the design review. Bing and I met on Sunday night and did significant work on the slides and the diagrams. I re drew some schematics for the board. Our group also met outside of class and discussed new plans for the ball return mechanism regarding the gantry and the game board, and also briefly talked with Hyeong on his concerns regarding timing. This week, I also picked up the servo from the recieving lab and am waiting on Bing’s microcontroller to get in so I can fully test the servo’s capabilities. In the meantime, I aked Aiden to bring an exisiting Arduino microcontroller than I can use on Monday while I wait for our main one to arrive.

I would have liked the actual microcontroller we were using to have arrived by now,  but unfortunately that was out of our control as we ordered over a week ago. Otherwise, I am confident I can make sufficient progress with a temporary microcontroller as the code should remain the same.

In the next week, I hope to have code written fro the microcontroller and get an idea of how I will integrate the paddle into the game board. I also want to figure out power sources and re order different microcontrollers if needed. From Bing, I also want to understand the BT signal he is sendng better and read more into the library for that.

Bing’s Status Report for 2/21

What did I accomplish this week?

This week I completed our team’s design presentation and practiced the slides, which I presented in class on Wednesday. I also got meaningful feedback from the professor regarding our designs, which I appreciate. I’m currently looking at a setup guide for the Arduino Nano ESP32.

Am I on schedule or behind?

Due to the orders placed at the beginning of the week not arriving yet, I haven’t been able to get tangible work done, so I am slightly behind. However, I am extremely confident that I can comfortably get back on track after this speed bump.

What do I hope to complete in the upcoming week?

Same as last week, I am still patiently waiting for the components to arrive (should be any time this week), after which, I will immediately get to work with setting up the MCU and IMU through GPIO and learning how to transmit data from the MCU wirelessly.

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.

Team Status Report for 2/14

This week, we spent most of our time together finalizing the designs of our individual subsystems, and updated our project planning into a more detailed day-to-day Gantt Chart (linked here). We also submitted our initial orders for the components that we will be using for the project.

During our meeting with our capstone advisor, we received some follow-up feedback regarding the design of our project, and we feel confident in continuing with our current plans, while of course being cautiously flexible about any potential changes that may arise in later weeks. For now, we will keep working to deliver the product that we have promised: a fun, engaging, and immersive baseball arcade game.

As to how we are keeping in considerations of public health, safety, and welfare, social factors, and economic factors:

Our product is designed to provide a fun, physically engaging game that revives the spirit of retro arcades while combining it with exciting technology. From a safety standpoint, we mitigate hazards associated with a moving ball, moving mechanisms, and electrical power by implementing physical barriers and clear zones around any electrical components. The play area will include a defined batting box to prevent injuries in the swinging area and software safety implementations that prevent motion when the game is paused, reset, or when a fault is detected. We also plan to include an easily accessible emergency stop and a conservative safe state. Electrical safety is addressed with proper insulation and connections, keeping accessible surfaces at safe voltages.

From a public health /well-being perspective, the game encourages social play and stress relief through an interactive two-player experience. We also consider accessibility and user welfare by designing the interface to be simple and inclusive with clear visual cues and game states. The play experience doesn’t require advanced athletic skill and is easily enjoyed by all. —Vivian

In terms of social factors, the baseball theme of the game lends itself to a more North and Central American-centric audience. Given our mission to create a fun experience for all, we are designing the game with intent to appeal to a universal audience—with snappy mechanics and relatively simple rules—so that it could be enjoyed by all groups of people regardless of their experience or knowledge in baseball. In addition, we are also aware that the physical nature of the game can pose a physical barrier for people with certain disabilities. Although the physical hitting aspect of gameplay is something we do not want to compromise, we will make the bat as lightweight as we can in order to allow as many people as we can to engage with our game. —Bing

For economic factors, our system has been designed to fit with room to spare under our $500 budget, making it far more accessible than other arcade machines which typically cost thousands. Similarly, our components have been selected with easy of access in mind, as many of them are commonly used for hobby projects. These components have a lot of free and open-sourced peripherals that go with them, such as Bluetooth packages for our MCUs and build instructions for the aluminum extrusion hardware for our gantry. Many of our components have been purchased from Amazon for convenient, fast, and trustworthy sourcing. —Aiden

Bing’s Status Report for 2/14

What did I accomplish this week?

This week, I finished developing the design of the hitting subsystem and submitted the parts order for the IMU and MCU that I will be using. I spent time searching the web for tutorials on how to establish a connection between an ESP32 and an IMU. I also met up with my teammates three separate times to work on finalizing our subsystem designs, update our project planning, and draft up the Design Presentation.

Am I on schedule or behind?

I am still on track with the schedule that we have laid out. I just need to add finishing touches to the Design Presentation and review it by Sunday.

What do I hope to complete in the upcoming week?

Since I am presenting this week, I hope to spend some time rehearsing and familiarizing myself with the presentation in order for it to go smoothly. Once the components for my subsystem arrives, I will get to work with setting up the MCU and IMU through GPIO, and if time allows, also learning how to transmit data from the MCU wirelessly.

Vivian’s Status Report for 2/14

This week , I helped the team with the presentation and we all got together on call and edited the slides together.Throughout the week,  researched what parts would be best– this is documented within our group design documentation. Specifically, I outlined why I chose the specific parts I ordered. Additionally,  actually submitted the order form or my portion of the project and messaged our TA about getting those parts.  I drew out a diagram detailing the connections I needed in order for it to work. This diagram is included within our block diagram.

I would say my portion is on schedule. According to our Gantt chart, I just needed to have the parts ordered by this week and am focusing on prototyping and testing next week to make sure they work as expected. I want to make sure I have all the connections detailed properly so I can hit the ground running next week.

In the next week, i hope to have a rough prototype of the bat swing and to order additional parts if mine do not work as expected. A concern for me is the speed of the servo and the torque needed to hit the ball. I ordered some test servos for now just to get it up and running as the code will be similar no matter which servo I end up using. I want to have a prototype at the very least, even if the servo I ordered does not end up being the one I end up using.

Bing’s Status Report for 2/7

What did I accomplish this week?

I met up with my team members three separate times this week to finish hashing out the planning of our project. We completed an up-to-date Gantt chart for the project. I also spent time reading previous semesters’ project reports from teams that utilized similar technologies, namely IMU and wireless communication, that I was planning to use to implement the hitting sub-system.

Am I on schedule or behind?

I am currently on track with our development schedule.

What do I hope to complete in the upcoming week?

I am planning to finish the design of the hitting sub-system for the game, which will include the block diagram along with all the components needed. I will also be compiling all of our team’s design together into our Design Presentation by Sunday.

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.