Team Status Report for 4/12/25

General update
  1. Gantry progress has been good, although it was slightly delayed by issues with wood shops on campus. We have the box assembled and will be doing more testing over the coming days to verify proper movement of the chess pieces. We believe this part of the project is almost done! Just putting the finishing touches on the design now.
  2. Liam has been making good progress with the gaze detection, and he now has a better way to test the results as a person sits in front of the camera. He will continue to make this better over the coming days as he carries out more testing. This will also allow him to calibrate the model for better results overall.
Potential risks and risk management
  1. No new risks this week. We created a speech-to-text model that would act as a backup to the gaze estimation, although we are still confident in our ability to finish the gaze detection as expected. We believe the speech element would still meet our use case requirements as it does not require any physical motion by the user. This model has proven to be quite accurate as we speak into a computer microphone.
Overall design changes
  1. The one new design change is a small one. We will be using an NMOS in a small circuit to handle powering on the electromagnet. This is because the Arduino does not have a 5V output pin that can switch from high to low. We will use one of the 3.3V output pins to power the gate of an NMOS, which will act as a type of switch (although imperfect) to power on the electromagnet with the necessary 5V.
Schedule
  1. Our schedule does not have any major changes. We are ready to buckle down and do whatever work is necessary to finish this project and have a great presentation and demo at the end of the semester!

Validation

There are a few ways that we, as a team, plan to validate our design. This will look a lot at whether our project is still meeting the user needs.

  1. Revisit Initial Use Case Requirements: This will be talked about throughout the following points, but we want to go back and ensure we are hitting the use case we originally thought about. The idea was most clear at the beginning, and we want to be sure we did not stray from that concept.
  2. Accessibility of Gaze Model: We plan to bring in some of our friends and classmates to get a wide audience of people to test our camera model on. This will allow us to test all sorts of eye sizes and shapes to build a design that is accessible to as many people as possible. After all, our design sets out to make chess accessible to as many people as possible.
  3. Non-Physical Gameplay: As we carry out our testing, we want to make sure that every aspect of the gameplay is non-physical. This is to make sure that our system can be played by people who are not able to physically move certain aspects themselves, which is our entire use case. This means that the camera should not have to be adjusted, the pieces should be placed properly, and the electronics should work without physical interaction.
  4. Hidden Devices: One of the important needs that we set forward was an unobtrusive design. As we continue to assemble the system and test, we will be sure that all computational circuitry (and gantry components) are hidden away so that they do not detract from the game. This will continue to guide our decisions during assembly and placement.
  5. Speed of System: One major user need that we recognize is the speed of our system. We do not want moves to take too long for users to become uninterested and discouraged. Therefore, we plan to iterate during testing to improve any unneeded latency and make the game flow continuously as much as possible.
  6. Accuracy: Although this is mostly testing in verification, accuracy is the most crucial part of our user needs. If our system is not accurate, it will not be used. Therefore, as we go through testing, we will be sure that accuracy is at the forefront of our validation and make changes when necessary to prioritize this metric.
  7. Remapping our Stakeholders: As we look toward a completed design, we think it may be interesting to look back at the ethics assignment for this class. Are we considering the stakeholders properly? Are we keeping bias and our own pride out of our design? We want to be sure that we are still aligned with the people most affected by our system.

Team Status Report for 3/29/25

General update
  1. After completing the gantry assembly last week, we were able to complete the pulley system after receiving the belts this week. As some of our individual posts show, Tarek and I worked on testing this completed system to look at movement and gain an understanding of the motors with the Arduino code. The video can be found here: Gantry Testing Video. This was a super encouraging piece of progress and will be a great starting point for our demo next week.
Potential risks and risk management
  1. No new risks this week. Still exploring the gaze estimation, but the communication and data received from the camera are encouraging so far. There have also been more updates on the depth estimation side which should give us better ideas of the risk involved.
Overall design changes
  1. No new design changes this week.
Schedule
  1. Our schedule hasn’t really changed since last week. Our demo will be ready by Monday and we are excited to present this to the students and instructors in the class!

Team Status Report for 3/22/25

General update
  1. This week, we finally got the gantry system assembled! This was an exciting step, and a picture will be attached below. The final step is attaching the timing belt to fully set up our pulley system, as well as wiring up the electrical systems that will control the gantry. Unfortunately, we have to wait for another timing belt to be delivered due to some size underestimates on our part. This should arrive on Monday, allowing us to finish up the entire system and begin testing early in the week. Trey and Tarek will work together to polish the final pieces of the design and then carry out testing on the basic movement mechanics of the system throughout the next week.                          
  2. Due to the nature of the gantry assembling, Tarek’s ability to test was limited. Therefore, he pivoted to finalize some of the details for our LED system, chess logic, and other peripherals. In particular, he was able to isolate and purchase some shift registers (74HC595) for the LED circuitry. The Arduino code is already written for the gantry movement, and it will be tested in more detail this week. There is also a new GitHub repository holding all of this code.
Potential risks and risk management
  1. No new risks this week. Still exploring the gaze estimation, but the communication and data received from the camera are encouraging so far. In the absolute worst-case scenario where we are left with little time to pivot, we would shift to an automated chess movement system where the user inputs their move and the piece is automatically moved.
Overall design changes
  1. The LED circuitry design for our project changed to use the 74HC595 shift register instead of the MAX7219 LED driver. Other than that, no other major design changes occurred this week.
Schedule
  1. We still expect to have a demo of the gantry system movement by our meeting with Professor Kim on Wednesday. The assembly of the gantry was an encouraging achievement that should enable various parts of our testing. As such, we did not have to make any major changes to our schedule. We plan to put in extra hours (when necessary) this week to stay on track for the upcoming demo deadline.

Team Status Report for 3/15/25

General update

Trey and Tarek’s work this week was focused on physical design and fabrication of parts. Tarek designed and 3D printed a stand for the stereo camera so Liam can continue testing on the device. Trey designed some parts for the gantry to be able to hold the electromagnet, which Tarek sent to 3D print at the IDeATe printers. Progress this week relied on these parts, but IDeATe has not yet approved and printed these parts, which has bottlenecked work for the team this week. Nonetheless, Tarek worked on chess logic code, Trey worked on cutting the gantry rails and beginning assembly of the gantry, and Liam worked on getting both depth and images from the camera. He is currently working on having two python programs to interface together due to version incompatibilities.

We also individually spent time working on our ethics assignments, which was time consuming.

We are still aiming to have a demo-able gantry by next weekend. At the very least, we will be able to move the gantry to a given coordinate and control the electromagnet.

Potential risks and risk management

No new risks this week. 3D printing was bottlenecked but we are working on resolving that with IDeATe or using TechSpark to get the parts printed and resume work within the next 48 hours.

Overall design changes

No design changes this week.

Team Status Report for 3/8/25

General update

This week, Liam got a gaze model working on a Windows Laptop. He still has to refine the depth calculation. This will be the focus of the early days of this week.

All pieces (including screws, washers, etc.) are now obtained to assemble the gantry system. This will be completed by the end of the week, with testing commencing once Tarek returns to Pittsburgh. Tarek also wrote some additional code to control the motors in our design, so these tests will verify the functionality of the code and the gantry design.

Potential risks and risk management

No new risks this week. The initial gaze model work from Liam is encouraging, but will be tested further once the proper camera stand is obtained.

Overall design changes

No design changes this week.

Initial Schedule

Schedule is still on track. Spring break was less productive as our team was away from the campus and our project, but we are refreshed and prepared to grind out some work to complete the design of our subsystems and initiate testing.

Additional Week-specific Items

Part A: Global Factors (written by Trey)

Check, Mate, Vision addresses the global need for increased accessibility in recreational activities, particularly for individuals with physical disabilities or limited upper body mobility. Chess is a globally recognized and widely played game, but its traditional physical requirements create a barrier for individuals who cannot manually move pieces. Our solution eliminates these barriers, allowing users to engage in strategic play without needing to touch the board physically. By creating an inclusive chess-playing experience, Check, Mate, Vision promotes cognitive stimulation, social interaction, and emotional well-being for people around the world.

This solution also reflects a growing global need for assistive technology and adaptive design. As populations grow and the number of individuals with physical disabilities increases, there is a rising demand for products that enhance independence and inclusion. Check, Mate, Vision addresses this need by empowering users to engage in a complex intellectual activity without relying on the assistance of another person. The system’s reliance on common and scalable technologies, such as electromagnets and microcontrollers, ensures that it can be adapted to different environments and production scales.

Part B:  Cultural Factors (written by Liam)

Chess has a rich cultural history spanning 1,500 years across numerous civilizations, and the physical experience of playing the game carries significant cultural value. Check, Mate, Vision preserves this traditional experience by maintaining the original chess environment instead of shifting to digital alternatives. The unobtrusive design requirement ensures minimal extra components are visible from above the table, maintaining the important classic chess that many cultures have experienced.

Part C: Environmental Factors (written by Tarek)

While our project is mainly geared towards accessibility, we have taken some decisions with regard to environmental factors. One key decision is optimizing energy efficiency by using stepper motors with precise motion control, reducing unnecessary power consumption. The embedded controller ensures that movements are executed only when necessary, preventing idle power drain. Additionally, the LED feedback system will be implemented with low-power LEDs to minimize energy use while still providing clear user communication.

Material selection is another factor in reducing environmental impact. The gantry system and enclosure are constructed using durable metals and recycled plywood, ensuring longevity and reducing waste from frequent replacements. Additionally, the modular nature of the system allows for repair and upgrades, extending its lifespan rather than requiring full system replacement. By designing Check, Mate, Vision with energy efficiency, environmentally-conscious materials, and longevity in mind, the system not only meets its accessibility goal but does so with minimal environmental impact, aligning with broader sustainability considerations.

Team Status Report for 2/22/25

General update

This week, the team spent most of our time assembling, bringing up software and devices, and doing initial proof of concept tests. Liam has been working with the Jetson and the stereo camera. He is evaluating the output of the camera and determining how to interface with the Jetson and our included models. Trey tested out the electromagnet functionality and began working on the gantry system assembly. Some CAD designs seem necessary, so Trey will also be designing and printing these components to support the ordered components. He also worked with Tarek to get the step motors spinning. Tarek is working in more detail on the Arduino program that will give precise control to our pulley system in the gantry.

Potential risks and risk management

No new risks have been identified this week. The same two (3D Gaze Estimation and the Electromagnet) will be prevalent until further testing is done. A proof of concept for gaze detection will ease worries about that subsystem. Liam is working studiously on that.

Overall design changes

No large design changes this week. Preliminary testing identified that an external DC power supply may be needed for the motor drivers. However, the overall design has not changed in any way. Further testing will be used to verify entire subsystems and the interface between them.

Schedule

Our schedule remains unchanged and we are on track.

Team Status Report for 2/15/25

General update
  1.  Jetson configured
    1. Packages installed and configured it to be connected through SSH
  2. Preparing for design presentation
  3. Parts ordered for the various subsystems which should begin to come throughout the next week. This will be particularly helpful for the Arduino and gantry system, as we can begin to assemble and test the interface between the two.
  4. New Gantt Chart
Potential risks and risk management
  1.  The same risk mentioned last week about the accuracy of the gaze model. If it fails horrendously we will switch to a screen or hopefully find a better model.
  2. There is a chance that the electromagnet is an ineffective solution. It could be too strong and attract nearby pieces during movement, or it could be too weak that it cannot move a piece through the board. In order to manage this risk, we will test this functionality as early as possible to allow pivots to other pickup mechanisms. The next option would be reverting back to an above-ground gantry that uses a mechanical grabber.
Overall design changes
  1. The gantry system design changed from an above-board system to a below-board. This decision benefits us in several ways, including eliminating the assembly and cost of a z-axis step motor and creating a more clean and accessible board (without the large rails on the sides). The below-board system will still meet all design requirements.
  2. No other design changes at this time. We expect many of our components to arrive throughout next week, which will allow us to determine if the design/parts are suitable.
Initial Schedule
  1. After a conversation with Professor Kim, we have decided to accelerate the schedule of our baseline design. Achieving a minimum viable product (MVP) earlier will allow us to find flaws in our subsystems while still offering enough time for testing and integration. As such, our schedule has changed to reflect the new deadlines that we would like to follow.

Additional Week-specific Items

Part A: Public Health, Safety, and Welfare (written by Trey):

Check, Mate, Vision enhances public health and welfare by making chess accessible to individuals with limited upper body mobility, promoting cognitive well-being and emotional resilience. Studies show that chess improves memory and problem-solving skills, yet its physical requirements can be restrictive. Our system removes these barriers, ensuring all players can access its mental health benefits. Beyond cognitive stimulation, Check, Mate, Vision creates meaningful recreational opportunities, reducing social isolation and fostering engagement. By providing an inclusive and interactive experience, it helps improve mood, alleviate stress, and combat feelings of loneliness.

Our product prioritizes user safety by employing a controlled gantry system that ensures precise and predictable movement of the chess pieces, eliminating any hazards associated with manual handling. The gaze-tracking model further reduces physical strain by accurately tracking eye position at all times. Check, Mate, Vision also enhances overall welfare by fostering independence and inclusion, allowing users to engage in strategic play on their own terms. This promotes self-sufficiency, personal growth, and confidence, extending to daily activities and empowering users to take greater control of their lives.

Part B: Social Factors (written by Tarek)

Check, Mate, Vision is, at its core, a system to enable more people to play chess. This game is enjoyed by millions of people around the world, connecting fans of the game and allowing them to find a new way to socialize with one another and share the human experience. As such, it is important to us that Check, Mate, Vision preserves this aspect of social interaction.

In our ideation stage, we thought about having players play against a machine; however, it was important to us to preserve the human aspects of the game. Playing with another human in front of you, seeing their face, talking to them, and connecting over an appreciation of the game, is a powerful and important element of chess.

We also thought about having users talk to the machine in order to select moves; however, we didn’t want to limit the system’s accessibility to English speakers or those familiar with chess coordinates. Our design ultimately removes as many barriers as possible for as many people as possible to enjoy chess with others, fostering human connection and enabling people to connect with others.

Part C: Economic Factors (written by Liam)

Check, Mate, Vision is focused on providing an affordable chess-playing solution for individuals with limited upper body mobility. Traditional assistive technologies in this field are often bulky and expensive, primarily due to specialized hardware and complex manufacturing processes. By utilizing common components like a camera, computer, and gantry system, we significantly reduce production costs. These readily available parts are less expensive to source and assemble, which lowers the overall price of the system for consumers.

Simplifying the production and distribution aspects also means we can scale up more efficiently, making the technology accessible to a wider market. Reduced manufacturing complexity leads to lower inventory and supply chain costs, which translates into savings for users. This cost-effective approach not only makes the game of chess more accessible to those with physical limitations but also opens up opportunities for educational institutions and rehabilitation centers to adopt the technology without incurring substantial expenses.

Team’s Status Report for 2/8

Risks

One of the most significant risks that could jeopardize the project is getting gaze detection working properly while the user looks at a chessboard. If at any point in the project, we realize that we can’t continue with on-board gaze detection we will switch over to looking at a simulated chess board on a screen. We are developing a proof of concept of this subsystem so that this change can happen as early as possible if this is the case.

Changes

No changes so far since we have not started the process of building the chess assistant. We will implement changes as needed once our actual testing begins.

Gantt Chart

We have created an initial schedule that breaks down our tasks to complete in the first couple of weeks. These include proof of concept work, research, and initial prototyping. No updates have been made to our schedule as of now. The Gantt chart can be found below.

C8 Initial Gantt Chart