Team Status Report for 2/7

We have not made any significant decisions that could cause large risks yet. Our main risk is that the project will either work or not work. There is no partial success if the volumetric display breaks. We are mitigating this by being very detailed in our design decisions and talking them through. For example, we spent some time reviewing the parts list.

One design change we made was moving from an ESP32 for the display controller to a Raspberry Pi. This is due to the fact that the ESP32 only has enough GPIO pins to control one display. One slight downside is that without RTOS, it is possible our display driving logic could have slight jitter. However, looking at previous volumetric displays, using Raspberry Pi’s did not cause any visible image tearing.

 

Andrew’s Status Report for 2/7

I spent the week mainly working on creating a thorough parts list. I made it pretty detailed down to the specific screws we needed and electrical connection components. I also got a Jetson Orin Nano from the ECE inventory so we could do some preliminary software work.

The software work is pretty ahead of schedule as I have a good idea of the exact libraries/languages we need.

Next week I’m looking to do some digging around and see if I can get any machine learning models to work on the Jetson to do hand tracking.