This week we worked on the specific background research for different idea choices. This helped us narrow down which ones don't have patents because we are doing further research. This included splitting it up between the entire class so that we could complete it in a short amount of time. We also split up the different sections of the application. My group worked on the Invention Statement. We just found the different areas in which information needed to be included and split it up between the people in the group. We were able to also go back and help those that needed help completing their sections. This invention didn't end up being chosen because we found a similar patent.

For week five we divided the the background research document among the entire class because this was our final invention choice. Completing the background research gave us a chance to go into more detail on how the invention will work as well as give us an idea of what we would do in order to make it work correctly. We also completed our sections of the team video. We had to split it up because of our current situation. Through the weekend we worked on finalizing the Invention Statement as well as the application as a whole. The video was edited together and we were able to submit all of the application pieces by Tuesday afternoon.

These are the different technical teams that will be necessary during this process. On this slide there are descriptions of each one and we were told to choose which one we would want to work under. I chose the hardware team because I have always been more comfortable with working with the materials of a project.

Prior to the voting process, each student submitted a flipgrid where they had to explain what leadership role they wanted and why they were fit for that position. Once all of the flipgrids were submitted we voted for who we thought would be the best for each role. Those not picked for a leadership role became team members. All of the rows marked (ind) had to have two roles, a main role and their secondary role. This was because they wouldn't always have something to work on in their main roles.

Our planned steps are to start working with our materials. We should receive our materials later in the week. Once all of the materials are gathered they will be organized and distributed to all of the team members. We want to familiarize ourselves with the materials and the software. We split up responsibility throughout the group members so that each person can master a section and then be able to help the others. Chanel will be focusing on learning python, but we want all of the members to try and take the python courses so that everyone has a starting base for the code.

We created a list of things that need to be completed. The entire team needs to have their Raspberry Pi working, sadly we were set back because we bought some wiring that was for a different Raspberry Pi board so we had to reorder the correct piece. Now that the correct piece has arrived, we are now able to start working with the board and should reach all of these goals by the deadline. We decided to split up the roles so that we would be able to get everything completed in the given amount of time. My main focus is to collect video and audio data and once that is completed to make sure that that data can be uploaded to a phone via Bluetooth.

The entire hardware team needed to get their previous modules, from our December goals, to connect with a Bluetooth device. I needed to get the Raspberry Pi to transfer video data to a device via Bluetooth as well as have it collect audio data. I was unable to complete these goals by December 6th because there is a common error that I am experiencing when attempting to connect a phone to the Bluetooth of the Raspberry Pi. I am also working on collecting the audio data. I have the microphone connected to the Raspberry Pi, but I am still attempting to get the code working.

Here I attempted to connect my phone to the Raspberry Pi using Bluetooth. The issue that I encountered was that once the device was paired, it was unable to connect because there are "no usable services" which basically means that the Raspberry Pi refused to connect because it had no reason.

During weeks two and three, I continued to work towards being able to record audio using the Raspberry Pi. The main issue that I am coming across is that Python is not recognizing the libraries that I have installed. In my prior code, shown above, I had the issue of the library not being compatible with the newest version of Python. I have since found a new code with compatible libraries. I installed the necessary libraries, but I am continuously getting the error message saying that the necessary modules can not be found.

This is the circuit diagram that I made on circuit-diagram.org. My diagram includes diodes that represents the LED Matrix. I then connected the same points on the Matrix to the points on the Arduino Nano. I connected it in the same way that I connected it in person. I also made each wire a different color (alternating between the color options) so that it was easy to see which point was connected where since there were areas where they overlapped.

In my code, I made it possible for my LED Matrix to fully light up, make a heart, make a circle, and make the letter "A". I put a time count within my code so that the matrix knows to change after a certain amount of time. The pattern also repeats, because after a certain amount of time the arduino is told to reset the time to 0 and start from the beginning.

This sensor works similar to how a bat detects how far something is from it. This means that the sensor detects distance based on sound. In Arduino, you are able to pull up a mini screen that tells you the distance that is being recorded by the code. This window shows you how far an object is from the sensor in both inches and centimeters. I used a small brush and held it away from the sensor between 2 and 5 inches.