This week our team focused on getting the logistics for the semester out of the way, finalizing our hardware and CV software requirements, and establishing a development workflow on the Jetson board. In order to facilitate a more productive semester we set up plans for meeting times outside of class and clamped down on our schedule to ensure that we’re working at pace and communicating regularly. 

All of our team members conducted research in their respective areas to determine what parts we will need to get started working. After finding suitable boards and components as well as backups for if they don’t work, we submitted our first orders. Overall our design still looks very similar to our original plans, but we are hoping that we will be able to deviate from our original design by driving all of our video output with the Jetson. We also began exploring the Jetson board and learning how to use it. We hope that this will help us in getting it set up for full development next week.

As of now we are ahead of schedule. We have been able to get a lot of research done, and we’ve already started setting up our various development environments. By the end of this week all members of the team should have conducted enough research to have a firm plan of attack for their sections, and ideally each person will have begun setting up their hardware and starting their implementations. However, since we’ve already done so much work preparing for our design, we will almost certainly spend a good chunk of the next week finalizing that work and preparing for our design review. 

We do not feel that at this stage of the project there are a large number of risks that we need to immediately concern ourselves with. Tomas has everything he needs to begin working on the CV side of our project, and Kevin and Harry have access to backup Arduino boards if there are shipping delays that prevent experimentation with sensor approaches. This means that even if we run into a delay we can still begin working on our various software and hardware implementations. 

Team Status Report for 2/12/22
Tagged on:

Leave a Reply

Your email address will not be published. Required fields are marked *