Team Status Report for 3/14

This week, we met as a team to work towards finishing the prototype for our project. Aiden and Vivian spent time in TechSpark to attach the 3D-printed flipper to the newly-arrived servo which should soon be ready for a demo, while Bing worked towards developing a prototype for the bat swing detection. We also made some design changes regarding the surface of the game board, opting for hardboard rather than acrylic due to cheaper costs and ease of fabrication. Additionally, we also discussed our ethics assignment in preparation for the upcoming ethics activity on Wednesday.

Unfortunately, we have also encountered road blocks in the past week in the form of exams and component issues, which slowed down our development process. Although we are currently behind in terms of progress, we are working hard to complete a working demo out as soon as possible. We will keep updating our Gantt chart as frequently as we can to reflect the state of our project and adapt accordingly.

Bing’s Status Report for 3/14

What did I accomplish this week?

This week, I worked on building a prototype for the bat swing detection with the ESP32 and IMU.  I ran into some driver issues on my laptop while attempting to connect the ESP32 to my laptop, which took a significant while to debug. I also spent some time reading tutorials and example programs for ESP-NOW, and writing the ethics assignment.

Am I on schedule or behind?

I am still behind schedule; I’ve made sure to tentatively update our project Gantt chart to reflect progress.

What do I hope to complete in the upcoming week?

I hope to finish my prototype by Monday and get to integrating as soon as possible. The missing shipments of microcontrollers have finally arrived, so hopefully we can quickly make up on the lost progress on that front.

Vivian’s Status Report for 3/14

This week, I focused on getting the new servo up and working in addition to the game board state code. In addition, me and Aiden attached the 3D printed paddle onto the new servo. We will get a demo up and working next week with the visual speed verification of the paddle so we can make sure it aligns with our expectations. currently, we are still using the Arduino as out current STM has not arrived yet (Bing has one for his bat but we need another, it was out of stock so it did not get shipped). I also did research on which sensor to order, and am going to order by Monday next week so I can have one sensor ready to test and further expand upon that for the other sensors we plan to have.

I am slightly behind as I missed class on Wednesday, but aim to get extra work done on Sunday to get aught up. I expect to have a working paddle demo by Monday and also further estimates for the torque. We do not have the metal ball yet, so I would like to have that order sand tested as soon as possible. I also need to communicate with Bing on getting the servo/bluetooth signal set up.

In the next week, I want to have a complete demo of the paddle working so I can proceed with the game state testing. I have the baseline code written, but it will obviously require testing and debugging for it to be fully functional and as robust as we would like for the final demo. I also want to order the sensors.

Aiden’s Status Report for 3/14

What did I accomplish?

I machined three prototypes for the game puck out of steel, and tried testing magnetism with small neodymium magnets I found, but they were far too weak, so I ordered some stronger magnets. I also drilled holes in the 3D printed flipper prototypes so they can be mounted on the servo horn, and planned revisions to the flipper.  I acquired and tested a small solenoid for linear actuation for the coupling mechanism, and the speed seemed fine. Thus, I have simplified the coupling mechanism design. For our board fabrication, I researched building materials and framing styles.

Am I on schedule or behind?

I’m on schedule, but I am getting concerned that the gantry still hasn’t come in yet. I will continue to make progress elsewhere until then.

What do I hope to complete in the next week?

I plan to make a prototype game board with a cutout for the flipper servo and at least one for a scoring pocket. This can serve as a test bench for all of our subsystems except the pitch. It will be like a slice of the real deal, so it should be a good proof of concept. 

Team Status Report for 3/7

This week, we formalized and integrated our subsystem designs to make a planned final vision, which was captured in our Design Report. Until now, a lot of our ideas had been hypothetical. This report forced us to rigorously analyze tradeoffs and defend our design with a mathematical basis. In addition, we updated our Gantt chart to adapt to logistical challenges and developed some prototypes for the flapper subsystem.

 

The following paragraphs discuss  how we are considering factors of public health, safety, and welfare, social, and economic. Part A was written by Aiden, Part B was written by Vivian, and Part C was written by Bing.

 

A. Globally, there has been a shift towards screen-based, single-player entertainment. Our solution addresses the downsides of this shift directly by making our playing experience physical and social.

Our game is intuitive and accessible. Our desire for simplicity enables an experience that anyone can quickly pick up and enjoy,  with intuitive inputs such as button presses and a bat swing. The components we use are easily accessible and affordable, and there is a plethora of open-source projects online that can be used for additional context. Our product is also designed to have a small footprint, which enables users to easily set up our board in a variety of environments, such as classrooms, arcades, community centers, and even homes.  — Aiden

 

B. Our product solution is designed to create a game experience that is accessible, familiar, and enjoyable for a broad range of users. Because games are often played in shared social settings, cultural values such as inclusivity, fairness, and ease of participation are important considerations taken into account within our design. The system is made to be playable by anyone, regardless of prior sports experience or familiarity with similar arcade games. In our game, this is illustrated through simple physical interactions, visual feedback, and straightforward scoring logic so that the product can be understood quickly without long instruction manuals. By lowering barriers to entry, the game better serves users and supports a fun community bonding experience. — Vivian

 

C. From the standpoint of environmental considerations, we of course plan to limit any unintended adverse affects that it may have on the environment. Although we have good reason to believe that the main purpose of our product would not have direct negative effects on the environment, we still take into consideration the power consumption, building materials, and longevity of the product. In terms of power consumption, the system should use the same amount of power as a typical electric appliance based on our design, which we believe is reasonable. We also plan to construct the main body of the system out of composite wood, which is highly sustainable. We understand that the electrical components of the gantry, microcontrollers, and sensors rely on materials that are obtained through environmentally destructive ways, however, the use of those components is strictly necessary and shall only remain as such. Finally, our product is designed to be played over and over again for as long as possible, and thus waste should be minimal. — Bing

 

Aiden’s Status Report for 3/7

What did I accomplish?

I designed the coupling mechanism and began 3D printing prototypes. I also designed the flapper and 3D printed prototypes for that. I improved the game board model and sought feedback from my partners.

I pondered alternative game board materials, such as hardboard. Acrylic will be very low friction, but it is expensive and can be tough to work with. Hardboard may have low enough friction.

Am I on schedule or behind?

I think after adapting my schedule to fit my delayed gantry arrival, I am on schedule. Over Spring break, I worked on the things I sought to beforhand.

What do I hope to complete in the next week?

If my steel rod comes in, I want to make a prototype of the game puck to enable Vivian to make forward progress with the flapper system. I want to pass off the coupling mechanism work to her as well so that I can focus on the gantry, as it should be arriving soon.

I want to meet with the team to finalize a game board surface design so that we can at least have a prototype to work with in the following week.

Bing’s Status Report for 3/7

What did I accomplish this week?

I spent most of my time working on drafting, editing, and finalizing the Design Review document in the week leading up to spring break. I also picked up the components that finally arrived, though there were some mistakes with the received order.

Am I on schedule or behind?

I am a little behind schedule right now, largely in part to the delay in shipment of the ESP32 and IMU.

What do I hope to complete in the upcoming week?

In this upcoming week, I am hoping to resolve the issue with the parts order while getting to work on prototyping the hitting system.

Vivian’s Status Report for 3/7

This week, I got the servo and started getting some code up and running on it just for testing purposes. In addition to this, I worked on our abstract by outlining the game board design and also the paddle design. As a byproduct, I ordered the new servo according to the calculations in the abstract for the torque and speed specifications and it came in on the Friday before break, so I will pick that up this week and continue working on it.

I would have liked to have the real servo working earlier along with the actual STM, but for some reason we were only delivered one instead of two so I temporarily used an old Arduino. I would not say that I am behind. Since I tested on the smaller servo, I have the logistics for how to upload and flash code onto the Arduino.

This week, I want to get the code for the game board logic up (ex start stop reset logic) and also coordinate with Bing for bluetooth packet specifics.

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.