Posted on

Andrew’s Status Report for 3/7

I spent more time flushing out all of the software for the Jetson. Beyond the computer vision Python code, I made the C++ environment for using OpenGL to render 3D geometry from OBJ files, implemented a compute shader to sample 2D slices, and developed some networking logic for compressing and sending data over UDP. Progress is visible on Github where all the source code is.

I think the software is overall on schedule. The current code should be enough to get the MVP working on the Jetson side, so all that’s left is the Pi code. Once initial implementations are done we can do more testing and optimization. Next week I want to try testing some of the software more.

Part A: Our product mainly addresses global factor through our implementation of interactivity. We want 3D interaction to feel natural and smooth compared to commonly available methods. For example, traditional 3D manipulation occurs in complex CAD software with unintuitive controls or VR environments with complex controller mappings. Using simple hand gestures to spin an object around removes these kinds of barriers for access.

Posted on

Kendric’s Status Report 2/21

This week I focused on refining the base design and responding to feedback about lowering the center of gravity. Since we’re spinning the motor at high RPM, stability is critical. I adjusted the layout so heavier components sit closer to the base plate and slightly widened the design to improve resistance to tipping and vibration.

I also began designing the wooden structural components we plan to fabricate. I finalized the plate and mounting locations for the motor and bearing supports so that once parts arrive, we can move directly into cutting and assembly.

We’re still on schedule. While we’re waiting on a few components, figuring out the base design now should make integration easier in the future.

Posted on

Andrew’s Status Report for 2/21

This week I began some work on the software side. I did some more in depth analysis for what ML models would work well. The final 2 choices were between trt_pose and mediapipe. trt_pose was made by Nvidia and was optimized for our Jetson hardware, making it much quicker. However, it had much worse accuracy compared to mediapipe. By default, the mediapipe installation doesn’t use the GPU on the Jetson, so I worked a bit on building the package from source to optimize performance. I think I got it working, so now the performance is more comparable to trt_pose while having much better accuracy, making it a clear winner. I also did some research into OpenGL for much of our graphics logic as well as some possible compression protocols to improve networking performance.

I think we are still on schedule overall as the software design is pretty mature, so the only big hurdles left for software are implementing and integrating.

Posted on

Team Status Report for 2/21

As we anticipated last week, we are currently experiencing shipping and logistical delays that are bottlenecking our testing phase. Fortunately, because we ordered our most important components early and built buffer time into our schedule, we have more than enough time to manage these delays without falling behind our final deadlines. Since we are stuck waiting for a few key items, our biggest risk remains the possibility of those delayed parts arriving broken or incorrect. To mitigate this risk as much as possible, we are actively bench-testing all the parts we currently have on hand. By making sure our existing components work properly right now, we can prevent a pile-up of technical issues later when the rest of the system finally comes together.

We did not make any major changes to our system design or incur any new costs this week. We just finished presenting our formal design review and are currently waiting to receive official feedback. We plan to keep the system architecture as it is until we hear back, and we will likely make any necessary design changes next week once we can review that feedback and incorporate it into our project plan.

Posted on

Steven’s Status Report for 2/21

This week, my primary focus was on preparing for our upcoming design review presentation. We dedicated significant time to reviewing and finalizing our overall system design, making sure our calculations for gear ratios, target RPM, and power constraints were fully validated. Since we have spent the past few weeks solidifying these technical details, the majority of my time was spent translating our system models and mathematical considerations into a clear, comprehensive slide format for the formal review.

Regarding our schedule, we are currently having some minor testing delays but remain on track overall. I had planned to begin validating the electrical components this week, but key items such as the Raspberry Pi and the main power socket have not yet arrived. Fortunately, since we were slightly ahead of schedule previously, this is not a major cause for concern. The buffer we built into our Gantt chart is currently absorbing this shipping delay, and other than the two missing components, the majority of our other parts have arrived in working condition.

Next week, I am hoping the delayed parts will be delivered so that we can begin assembling the components and I can conduct a full electrical safety test on the integrated system. Additionally, we will do a final inventory check; if we realize we are missing any minor components or hardware, we will place those orders immediately so they can arrive over Spring Break while the team is away.

Posted on

Kendric’s status report for 2/14

This week was focused on refining the mechanical transmission and structural design. I joined the team for a comprehensive Bill of Materials review, where I provided technical insights regarding the mechanical efficacy of our chosen components, specifically ensuring our shaft and bearing selections can handle the dynamic loads of the spinning array.

I also redesigned our transmission system, recalculating the gear ratios (pulley sizes) to ensure we can achieve our target RPM without over-torquing the motor. Following this, I began the CAD modeling phase for the custom structural components. I have drafted the initial designs for the main system mount and the rotor hub interface, focusing on ensuring the geometry is optimized for 3D printing and maintains the strict balance requirements we need for stability.

I believe we are on schedule. Our current progress follows the Gantt chart. In fact, with the CAD designs coming together faster than anticipated, we might be slightly ahead of schedule regarding the mechanical fabrication timeline.

Next week, I intend to move from design to rapid prototyping. My goal is to run a preliminary 3D print of the mount and gear components to perform a physical “fit check” and validate the tolerances. If the 3D prints are successful, I also plan to start laser cutting components for the hologram chassis so we can begin assembly immediately.

Part B:

The Hologram solution addresses social factors by catering to the culture of the Maker Movement and the Open Source community. These social groups are organized around the values of collaborative innovation, knowledge exchange, and “learning by doing.” By providing an accessible, transparent hardware platform, the project fosters social interaction among students, hobbyists, and engineers, creating a shared space for experimentation that strengthens these community bonds. Economically, the project addresses the “digital divide” in advanced visualization. While volumetric displays are typically restricted to elite corporate or research institutions due to high cost, this low-cost implementation democratizes the technology. This lowers socio-economic barriers, allowing wider social groups to access and develop for 3D interfaces. Culturally, the product taps into a collective imagination shaped by decades of science fiction. By creating the “holographic communication” tropes found in Hollywood classics like Star Wars, the device serves as a social bridge, uniting diverse demographics through a sense of nostalgia and technological wonder. This shared cultural language allows the product to function not just as a tool, but as a social centerpiece that facilitates engagement and communication across different age groups and technical backgrounds.

Posted on

Team Status Report for 2/14

The biggest risks to our project right now are shipping delays or receiving parts that are dead on arrival. Since the semester is short, a delay of two or three weeks to get a replacement part could make us miss our deadlines. To manage this, we ordered all our important components early rather than waiting. About half of our parts have already arrived, and we are testing them immediately to make sure they work while we can still return them. Our budget is also very tight, so if we accidentally break an expensive part and cannot afford a replacement, our backup plan is to build a simpler frame using scrap materials instead of buying new materials for a polished enclosure.

We made a few changes to our system design this week to improve reliability and safety. First, we updated our electrical plan to use a specific, high-quality power supply instead of a generic one. This costs about $15 more, but it is necessary to stop sudden power spikes from shutting down our main computer when the lights turn on. Second, we updated our system diagram to verify exactly where the physical frame sits in relation to our electronics. This change didn’t cost anything, but it was necessary to ensure the wooden frame is strong enough to support the entire hologram system.

A was written by Steven Guo, B was written by Kendric Terry and C was written by Andrew Yu.

Posted on

Andrew’s Status Report for 2/14

This week I mainly worked on the Design Review presentation. This involved ironing out some design decisions like how the actual hardware components might go together. This also helped mostly finalize our parts list.

I think we are on schedule since we have our design pretty detailed, which means we can proceed already with implementation as integration should hopefully be easier. Next week I hope to begin implementing some of the software. I will try to get one of the machine learning models to work and successfully detect hand landmarks.

Part C: Our project is not really meeting the economic need of any existing product market, as it is relatively unique. However, we are aiming to have it be cost effective compared to any similar solutions. For example, the best possible industry standard for volumetric displays is produced by Voxon and costs $6800. We have also made sure our device can operate by itself without an external computer or any other devices, making it economically easier to use the product once you have it.

Posted on

Steven’s Status Report for 2/14

This week, I focused on transitioning our hardware design from a purely theoretical to a physical level, documenting the process. I finalized and submitted the parts request forms for our critical components, locking in our design choices for the motor and power systems.

I also dedicated significant time to system modeling, creating a detailed electrical diagram that outlines our power distribution network, specifically mapping out how the power supply will independently feed the Jetson Nano, the motor controller/motor, and the LED display to prevent voltage sag. Additionally, I designed a high-level block diagram to define the interfaces between our microcontrollers and peripherals. To prepare for our upcoming review, I have also begun drafting the Design Document presentation with Andrew and Kendric.

I believe we are on schedule. We are tracking well against our Gantt chart, and with the administrative work of ordering parts out of the way, we might even be slightly ahead of schedule.

Next week, as our components begin to arrive, I plan to shift focus to hardware validation. My primary goal is to test the electrical components to ensure they are functional and properly spec’d for the load before we integrate them into the mechanical assembly.

Part A:

The Hologram design prioritizes safety by rigorously mitigating the physical hazards associated with high-speed rotating machinery. The spinning LED array will be fully enclosed within a transparent, impact-resistant polycarbonate shield, ensuring that users, particularly children, cannot accidentally contact moving parts. To further prevent mechanical failure or instability, the chassis will be securely clamped to its support surface and equipped with vibration-dampening rubber feet. Regarding health, the system promotes psychological well-being by providing a mentally stimulating, interactive 3D interface that encourages cognitive engagement. Physiologically, the display is calibrated to safe brightness levels and refresh rates to minimize eye strain, and the visual fidelity is intentionally designed to be distinct from reality to prevent user disorientation. Finally, the project supports welfare by democratizing access to volumetric visualization technology; this contributes to the user’s quality of life by fulfilling needs for advanced education, communication, and entertainment.

Posted on

Steven’s Status Report for 2/7

This week was dedicated to finalizing our system architecture and preparing for our formal proposal. I worked closely with Andrew to thoroughly review our materials. We spent a significant amount of time debating the system constraints, for example, whether a 12V or 24V power supply would better suit our slip ring limitations while still providing enough current for the LEDs. We also performed a torque-speed analysis to determine the optimal motor speed between a 750KV and 360KV motor, aiming to minimize heat while maintaining 900 RPM.

I think we are comfortably on schedule. We have successfully defined the critical hardware specifications (motor torque, slip ring current, and power voltage), which was the major blocker to ordering our parts.

Next week, my primary goal is to submit the final purchase orders for the motor, slip ring, and power supply now that we have made our decisions. While waiting for parts, I also plan to start work on investigating the LED panel driver so that when the parts arrive, we can hit the ground running.