Category: Steven’s Status Reports

This week marked our interim demo, where we completed our first full system integration. Overall, the demo was quite successful, and we received largely positive feedback from both our instructors and TAs. While the LED display has not yet achieved 3D image rendering and we are not operating at our target RPM, we were still able to present a strong proof of concept. I was honestly surprised by how much we were able to accomplish in time. Andrew and Kendric both put in significant effort to make the interim demo a success.

One major challenge I overcame prior to the demo was getting the hall-effect sensor to work with the Adafruit HUB adapter. Because the adapter occupies all of the Raspberry Pi’s GPIO pins, we needed to route the hall-effect sensor through the HUB itself. Although the adapter supports up to three LED panels and we are only using two, leaving some pins physically available, we initially overlooked an important detail: data direction. LED panels are designed to receive data, while hall-effect sensors transmit data. As a result, when we first connected the sensor to the available GPIO pins, we were unable to read any signal.

After further debugging, we discovered that the Adafruit HUB adapter only supports unidirectional data flow on most pins, with the exception of the SDA and SCL lines. We then rerouted the hall-effect sensor to these pins, allowing proper data transmission back to the Raspberry Pi. Fortunately, this resolved the issue, and we were able to demonstrate a fully functioning hall-effect sensor during the interim demo.

After having a working project for the interim demo, I’m much more confident about where we are in our progress. I feel that we are now back on schedule and in good shape for the final demo.

Next week, I’m planning on working on the Raspberry Pi software to drive images to display as well as preparing final demo logistics.

 This week, my main focus was getting the motor running predictably. After digging through the ESC documentation, I figured out it’s controlled by a 50 Hz PWM signal (1ms for minimum power, 2ms for maximum). With that in mind, I wrote an Arduino program that lets us customize the motor speed using a simple percentage input. I also wired up a two-button setup on a breadboard: one to turn the motor on, and one to turn it off, which safely lets the motor coast to a slow stop at any point during operation.

Hardware-wise, I think we are finally back on track. Andrew and Kendric did some great work on the CAD side this week. The 3D-printed clamps are working surprisingly well and have pretty much solved the mechanical fit issues we were stressing about last week. We also finally got our microSD card, so the Pi is fully functional. But, ironically, we hit a massive new roadblock: both of our displays are dead (one is bricked, the other shorted out). So even though the Pi is ready to go, we can’t actually test any of our display code. We’ve express-ordered new 64×128 LED panels from China, but they definitely won’t be here in time for the interim demo.

Even without the physical screens, my goal for next week is to keep pushing forward on the software side. I’ll be writing the display code blind and working on integrating the Jetson Nano output so we’re completely ready to display real images the second those new panels arrive.

This week, following the return from Spring Break, my primary focus shifted from documentation to hardware integration and assembly. With the arrival of our remaining components, I was able to begin the end-to-end assembly of our power system. I started by validating the rocker switch’s functionality directly with AC power before integrating it with the PSU. After verifying the PSU’s output voltage via multimeter, I successfully tuned and tested the buck converter against its datasheet specifications.

The most complex undertaking this week was the synchronized integration of the servo tester, Electronic Speed Controller (ESC), and the motor. This required extensive research into various datasheets to ensure signal and power compatibility. I am pleased to report that the integrated electrical system is now fully functional, with all components operating safely and as intended.

While we are technically back on track with our original timeline now that the hardware is in hand, the post-break reality is hitting hard. Although we are currently meeting our milestones, the approaching final deadlines have significantly narrowed our remaining buffer. The schedule feels much tighter than it did earlier, and there is a heightened sense of urgency to maintain this momentum to avoid further delays during the final integration phase.

Next week, my primary goal is to integrate and drive the LED display. I will focus on establishing the correct wiring and developing the initial test logic to ensure we can accurately output system data to the display. This remains a critical step in providing the necessary user interface.

This week, my primary focus was on writing and refining our formal design report. I was responsible for drafting the electrical subsystem section, ensuring that our power distribution architecture, current calculations, and safety margins were clearly justified and consistent with our earlier design trade studies. In addition to the electrical content, I also contributed to several of the general project management sections, helping document our schedule, team responsibilities, risk mitigation plans, and validation strategy to ensure the report accurately reflects our current system status.

Regarding our schedule, we are now facing a more significant delay than anticipated. Our most critical outstanding component—the rocker switch—has still not arrived. This part is essential for safely connecting our PSU to the rest of the system, and without it, we are unable to power and test the electrical subsystem in an integrated manner. Since next week is Spring Break, active progress will temporarily pause. While we are hoping all remaining components arrive during this time, our previously allocated buffer has now been fully consumed. As a result, we are slightly behind the schedule I originally planned for electrical validation and subsystem testing.

Next week, my primary goal is for all remaining components to arrive so we can immediately begin electrical testing upon returning. It is critical that we validate the electrical subsystem as soon as possible, since software development and debugging depend on having a stable, powered hardware platform. Beginning testing promptly will ensure we still have sufficient time to implement and refine the necessary control logic before final integration.

Part B:

Our volumetric display allows users to be immersed in a 3D experience with friends, rather than isolated from them. Rather than being forced to enjoy the experience alone, much like many VR headsets, the hologram display allows friends to interact and enjoy the experience together.  Moreover, our display transcends the language barrier, enabling individuals from various backgrounds to immerse themselves in the technological feat of a 3D display and bond over their shared fascination with making science fiction our reality.

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.

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.

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.