May’s Status Report for 11/22/25

This week I helped solder header connections for stable wiring and finished assembling the base board. I wired and soldered the save-state and turn-toggling buttons, plus a new set of LEDs for each board to light up ports and improve dice visibility. I worked on testing with the team, where we found a few small bugs to fix.

We had a setback when one LED strip lost connection and the copper pad ripped off. Because the button board and LED board were already joined, replacing that LED while keeping indexing consistent took time, but we were able to swap it and resolder everything more securely. I also helped assemble the ports and glue the visual pieces (water pattern and resource tiles) onto the board. We are ahead of schedule and have most of our stretch goals implemented. Next week I want to help finalize the presentation, record a better demo video, secure the button rods, and help debug remaining software issues.

I also had to learn more detailed CAD skills to design robust parts that could handle multiple iterations and different cut depths. I reviewed past course material, watched online videos, and asked TechSpark staff and friends for help, especially for modeling layered cuts and understanding the switch matrix. Most of what I needed came from knowledge in our earlier classes and projects, and I filled in the gaps with a few targeted videos, quick references, and small experiments.

Rhea’s Status Report for 11/15/25

Over the weekend, I worked with May to complete and finalize the first board. I led the button-to-LED mapping code and helped design the connection between the button board and the LED board. We assembled it and ran LED indexing and mapping tests. I also helped prep for the interim demo and updated the Gantt chart with May.

For the second board, I worked with Tanisha to secure the LEDs and route wires so they lay flat. I connected tokens to the buttons and helped set dowel height for reliable presses. I prepped the board for final assembly and assembled the two boards together with the team and conducted the final end to end tests.

 

Verification:

  • LED indexing/mapping: Thoroughly check every LED index against the board. Pass if mapping is 100% correct.
  • Robber rule logic: Test single press, adjacent pair, non-adjacent pair, and quick repeats. Pass if only one robber position is active and non-adjacent pairs are ignored without errors.

Team Status Report for 11/15/25

This week we finished the first board and got ready for the interim demo. We figured out how to connect the button board to the LED board and assembled the stack. We also finished the software that maps buttons to LEDs. It now enforces that the robber is in only one place. If two presses happen at the same time and they aren’t adjacent, we ignore them without an error.

After the demo, we built the second board using what we learned from the first. We cut and assembled the switch matrix, reworked the LED layout, and did the soldering. We fixed switch-matrix issues and a Raspberry Pi connection bug. We also glued houses, glued LEDs, cut dowels, and laser-cut extra pieces and tokens. We updated the software for the second board too.

Both boards are now fully assembled with full functionality, so we can shift our focus and prioritize software.

Validation:

    • Board synchronization: We will trigger the same action on both boards and compare LED states and game state after each step. The test passes if there are no mismatches in the test log.
    • End-to-end latency: We will measure time from a button press to LEDs lighting on both boards using timestamps or a simple stopwatch video. We will check the result against our latency target from the design report.
    • Full gameplay run (rule-agnostic): We will run a short game flow: setup, placements, resource rolls, robber moves, and a long turn. The run is valid if interactions work, states stay consistent, and no manual rework is needed to recover from normal play.
    • Usability check: Two people not on the team will set up the board and play a short game without our help. We will record task times and note any confusing steps.
    • User Study: We’ll ask 4–6 participants to rate (1–5 Likert) setup ease, feedback clarity, responsiveness, piece placement, and confidence to use without help, plus note one confusion and one change.
    • Safety and Durability: We will tug-test connectors and inspect for sharp edges or exposed wires on the final build. The build passes if nothing comes loose and there are no hazards.

Shared Verification:

  • Button board + dowels: Measure dowel height and press each site 20 times. Pass if each press triggers once (≤1 miss) and no double-triggers.
  • Switch matrix: Press every button 20 times and try adjacent/non-adjacent simultaneous presses. Pass if ≤5% misses, 0 ghosting, and non-adjacent pairs are ignored.
  • Solder/continuity: Inspect joints and check rows/cols and LED conncections with a multimeter. Pass if there are no opens or shorts.

May’s Status Report for 11/15/25

This week I worked with Rhea to finish the first board. We finalized the button-board to LED-board connection and assembled them. Together we ran modular tests—LED and indexing, the button board, and both together—to check mapping and behavior. I also helped prep for the interim demo and updated the Gantt chart with Rhea.

For the second board, I laser-cut the LED board and two iterations of the button board. I worked with Tanisha to restructure the LEDs and run quick checks (LED pattern and switch-matrix tests). I helped assemble the button and LED boards, setting the dowel height so the buttons press reliably. With Tanisha, I updated Rhea’s mapping code for the second board and tested the full system to confirm it works end-to-end.

Verification of Board Design and Peer to Peer Connection Subsystems:

  • LED board tile fit: Place tiles and lightly tilt/tap the board. Pass if tiles don’t slide, are held by the engraved divot, and still lift off easily.
  • LED cutout alignment: Check that each cutout lines up with its LED centerline. Pass if alignment error ≤0.5 mm and no LED is occluded.
  • P2P connection: Peers connect and stay connected without errors.
  • P2P state match: After each action, both peers compute the same state (hash or event log matches).
  • P2P ordering/duplicates: Out-of-order or repeated messages are handled once only.

May’s Status Report for 11/08/25

This week, I worked with Rhea on building and testing the switch matrix. We ran into a few minor connection issues, which we resolved through testing and soldering. I also helped soldered the LEDs to fit the Catan board cutout, working modularly and testing as we went. We verified the switch matrix by testing each button individually and checked LED connectivity every few strips.

We encountered more soldering issues than expected when securing the LEDs, so to make debugging easier, we split the LEDs into two separate strips. Our original plan to minimize soldered segments made sense at first, but bending the LED strips to fit the settlement and city layout (three LEDs in a peace-sign shape) caused problems, so I resoldered the broken connections and replacement LEDs. For future builds, we plan to solder those connections separately to avoid bending the strips altogether.

Since both the hardware and software components, switch matrix and LED wiring, now work independently, we’re ready to connect the two boards and start testing how they interact. While assembling the board, we realized we need to add a frosted acrylic layer above the tokens (to mark robbers) and leave more space between the LEDs and buttons. We also decided to fill the engraved numbers with black ink for better visibility.

In addition, I laser-cut the second LED board cutout and the switch matrix. We tested alternate buttons with a higher height, but they proved unstable and sometimes got stuck when pressed. Through this week’s testing and design adjustments, we’re confident we can build the second board more efficiently with these improvements.

Next week, I’ll help finish assembling and testing the second board.

May’s Status Report for 11/01/25

This week I iterated on several CAD versions and made quick laser-cut prototypes to check size and fit. I created CAD for the base board, hex tiles, dice plate and walls, and tokens, and then used the laser cutter to cut and engrave those parts. For the dice plate, I made versions with different wall heights and different wall designs. With the team, I measured spacing between LEDs and cities/settlements and accounted for kerf and a bit of wiggle room so parts place easily – the board cutouts are slightly larger than the pieces. The prototypes confirmed fit and engraving depth and helped me find the best power, speed, resolution, and number of cycles settings for the Epilog machine. The new board has LED-only holes to hide wiring and a shallow divot so tiles don’t move. The dice plate has a locking rim and a smaller hex cutout so the camera can see through the clear plate from underneath.  I ran into issues separating engraving and vector layers because the part was 3D but the DXF export is 2D. I fixed this by redrawing some shapes in CorelDRAW and adding extra sketch outlines in SolidWorks before exporting. Additionally, each full board run takes about three hours, and TechSpark hours sometimes pushed cuts to the next day.

Next week I plan to finish the CAD and cut the middle board that holds the buttons so soldering is stable and aligned with the LEDs. We’re a bit behind because making the cutouts exact took time and we had a setback with the buttons, but we’ve ordered new parts. Now that we know the build, we can move faster and make a second board in parallel. After the middle board CAD and cutting are done, I’ll help with the switch matrix build.

Number Tokens

SolidWorks Board

CorrelDraw Board


The acrylic in the middle is clear, but above has a blue plastic cover on it.

May’s Status Report for 10/25/25

This week the team and I worked on the Raspberry Pi and the LED strip. I ran small test scripts on my laptop and on the Pi to learn the LED API and how to address colors. I brought up basic patterns and started checking timing and per-tile addressing. Early signs look fine, and I have more checks to finish.

I also worked on how to connect to the Pi. I tried SSH and a direct wired setup and wrote down the steps for each. I fixed a few small network and permission issues while testing.

Our last part arrived on Thursday, so full assembly can start next week. I plan to help assemble the switch matrix and bring up a small section first. I’ll write a simple scan test and check that the switch events map to the right LEDs. After that, we’ll scale to more tiles.

Rhea’s Status Report for 10/18/25

Finishing the design report and making sure all the feedback from the presentation was addressed took up most of the time this week. Besides that, I prepared for the hardware setup by finalizing the wiring layout and diode plan for the 11×11 switch matrix. Since most of the parts hadn’t arrived yet, I focused on setting up the Raspberry Pi and organizing the copper wire for the matrix. I also got ready for soldering and breadboard testing, which I’ll start once the remaining materials come in.

Part C: Environmental Factors

Our system considers environmental factors by reducing waste and energy use while keeping people connected. Because players can share a game from home, they do not need to travel to meet in person. This lowers transportation emissions over time, especially for groups that play often.

The design also uses materials and power carefully. The LEDs and camera run at low power, and the system stays quiet and cool during use. Its modular build lets users replace or repair parts instead of throwing away the whole board, which helps reduce electronic waste. The camera’s infrared light stays at safe levels for people and pets. Together, these choices make the system more energy-efficient, safe, and sustainable.

May’s Status Report for 10/18/25

Most of my time this week was spent working on the design report and reviewing sections for submission. In addition to that, I focused on the mechanical and structural design of the board. I completed the CAD models for laser cutting the game tiles and began testing different materials, including wood and acrylic, to determine which would be the most durable and visually consistent for fabrication. I also reviewed how the board layout aligns with the switch matrix and LED wiring to ensure proper fit during assembly.

Part A: Global Factors
Our project responds to how people around the world spend time together. Many games today use screens, which can make people feel distant. By bringing back real, physical play, our system helps people connect in a more natural way. It can also reduce screen fatigue and make shared time feel more personal. The design reuses hardware like Raspberry Pis and cameras that are easy to find and use anywhere. This makes the system simple to build and supports global goals for sustainability and better use of technology.

Our system also focuses on people outside local or academic circles. Many players live far apart or do not have access to in-person game groups. Some may not be comfortable with complex digital tools. Because the boards connect over normal Wi-Fi and use real pieces, anyone can set them up without special skills. This makes it easy for families and friends in different places to play together through a simple, hands-on experience.

Team Status Report for 10/18/25

During this week, the team mainly focused on completing and submitting the design report. We incorporated feedback from the design presentation and made sure all comments were addressed in the final version. Since the presentation did not cover all required material, we finalized the overall system architecture and design requirements in the report. We also completed trade studies for key components, confirming the use of the Raspberry Pi 5, OAK-D Short Range camera, diode-isolated switch matrix, and WebRTC for communication. In addition, the team created sketches for the board layout and wiring design, organized the bill of materials, and finalized the Gantt chart showing each member’s timeline and tasks. We also ordered the parts needed to build and test a smaller prototype section of the board before full-scale fabrication.

Part A was written by May, B was written by Tanisha and C was written by Rhea.