Safiya’s Status Report for 10/18

  1. I finished the CAD for the carriage subsystem. I started fixing my 3D printer to get ready to print rack and pinions. I also put in purchase requests for all items so far to assemble LivePin. I had to also redo the CAD for the frame because we went from 32×24 in the CAD to 32×32 pin board.
  2. Behind. Purchasing might take a bit. To get ahead I will ensure all items are ordered that we need for a working demo, and get the CAD to a point where all pieces are accounted for.
  3. Fully Finished CAD, 3D printed rack and pinions, and finished purchasing.

Tedd’s Status Report – 10/18

This week I worked on getting a visible plot from depth coordinates provided by the Intel Realsense. With my preliminary python script, I was able to run OpenCV and matplotlib to get a pretty good output of which pins should be actuated and the distances that each pin should be actuated. Here are a few examples below:

As you can see, the depth camera was pretty accurate and is able to capture simple objects and display them pixelated on a plot. However, I realized that more complex objects like faces are not well translated onto the plot. I might have to fix up the resolution of the depth camera and see if that could help us get better results. For now, this is a preliminary script and it seems to be working well. I will automate this process in the future as well.

 

Crystal’s Status Report – 10/18

I was able to get the LEDs to vary in brightness demonstrating a PWM signal. I am experimenting with different approaches to get 4 servos moving in parallel.

I am behind schedule. I will try to put in more hours to get more progress. Next week I hope to be able to have 4 servos moving in parallel.

Team Status Report – 10/18

A – Our product is a low cost alternative to other motorized pin displays. Our low cost and modular approach enables accessibility that can be sourced internationally, allowing replication in museums worldwide. This open and scalable approach encourages cross cultural collaboration in art installations. The ease of use enables users who are not well versed in technology.

B – LivePin is designed with sensitivity to cultural diversity and inclusivity in communication and collaboration. As an interactive system for museums and for children/adults, the device enables users to communicate three-dimensional ideas without reliance on a shared language or cultural context.  This visualization system reduces the potential for misinterpretation of visual or linguistic descriptions and promotes equality regardless of language proficiency. Moreover, by enabling hands-on, physical interaction with digital content, LivePin aligns with cultures that value craftsmanship and learning. The design also respects differing cultural expectations of professional communication by providing a neutral, technology-driven medium for expression and art.

C- Our solution addresses the need for rapid, tangible 3D visualization in classrooms and small exhibits without generating one-off physical waste. Instead of printing and discarding plastic prototypes for every iteration, the system renders forms on a reusable pin board, then resets for the next concept. This directly reduces consumables (no filament, supports, or failed prints) and cuts the time and material tied up in single-use models, while still giving viewers a clear, physical sense of shape and depth.

Environmental considerations are built into the design. The frame uses durable, recyclable aluminum. The guide plates are laser-cut for low scrap, and the pins are wooden dowels that are inexpensive, repairable, and biodegradable. During operation, staged actuation keeps power draw modest relative to continuous additive manufacturing, and the system produces no consumable byproducts once a visualization is complete, the board simply resets. Taken together, the design conserves materials, lowers operational waste, and supports responsible end-of-life handling through reuse and recyclability.

A was written by Crystal. B was written by Tedd J. C was written by Safiya

Safiya’s Status Report 10/4

This week I focused on our design presentation and hardware planning. I practiced the presentation several times, and moved the bill of materials forward by organizing parts by subsystem, choosing likely vendors, and building rough cost totals. I also updated CAD for the larger pin screen and produced visuals for the presentation.

I am a little behind on final pricing and carriage design. To catch up I will lock vendor choices, complete the latest bill of materials with totals and start the first round of orders so the build stays on track.

Next week I plan to finalize the bill of materials, finish the carriage design and  begin 3D printing the rack and pinions.

Crystal’s Status Report – 10/4

This week I started getting the STM32 setup by configuring the timers and GPIO pins to generate a PWM signal. This has not been successful yet, but I will verify the setup by output putting the PWM signal to an LED.

I am slightly behind on schedule due to workload from other classes. I will put in extra hours this weekend to get the LED to vary in brightness with duty cycle, demonstrating the PWM signal.
Next week I hope to be able to have 4 servos moving in parallel.

Team Status Report – 10/4

The most significant risks that could jeopardize the success of the project is the actuator and rack and pinion mechanism not working properly. In order to successfully actuate the pins, we will need this system to work or we will experience speed delays and inaccuracies. Another risk is the depth map not giving us accurate results. This could lead the wrong pins to be actuated even though they are just following the information from the depth map. The first risk is being managed by ensuring that we have proper design requirements so that the hardware does not run into any issues. The second risk is being managed by doing rigorous testing of the depth camera and ensuring that the heightmap from the camera is accurate. Further testing is currently being done to convert the heightmap to a depthmap. We have contingency plans set up to make sure that our product will still be successful. For the gantry system, we can sacrifice speed for more accurate actuation. For the depth camera, we can always find another camera to work with, ensuring that our options are not limited.

There were no changes made to the existing design of the system since the design presentation. We are pretty confident in our design, including the requirements, block diagram, and system specifications. We may run into issues that may require us to pivot from our current design, but so far we are confident in the design.

This is our schedule from the design presentation, and we are still on time with our work with no changes necessary.

A picture of visible progress this week:

Tedd’s Status Report – 10/4

This week, I started working on getting the Intel Realsense camera to work. While we were anticipating on using the Oak-D cameras, we realized that other teams have checked out the cameras already, leaving us with the Realsense camera. There is nothing wrong with the Realsense camera, but we found out that it wasn’t fully compatible with Macs. However, I have an Intel NUC that runs on Ubuntu 24.04, so there is no huge issue. After downloading the necessary libraries, I was able to run the realsense application and turn on the camera. The image below displays a heightmap of me sitting on a chair holding a guitar:

The next step after this is to actually get a good depthmap for different shapes and see if I can convert them into actual measurements.