Author: nganjur

Neeti’s Status Report for 03/14

Neeti’s Status Report for 03/14

The week before spring break some of parts arrived! Our motors as well as the cameras, arrived. We also figured out details for our audio input and solidified plans. Making this post now, our project and plans seem so distant. It’s difficult to figure out 

03/04

03/04

picked up the cameras and motors! ordered a usb to usb-c cable for Neeti installed OpenCV version running Python 3 on RPi Sam instead of using virtual environments Figuring out how to process keystroke input on RPi without using GUI TO-DO: waiting for the motor 

Team Status Update for 02/29

Team Status Update for 02/29

This week we ordered all our parts that we finalized in the design review except for the microphones. We checked in with the front desk to see if the parts had arrived but they have not been approved yet, so we are waiting on them! Until then, we were able to work on Pi-to-Pi communication through TCP and establish client-server connection. We also were able to us PyGame to process keystroke input from a USB keyboard connected to the Pi. We were able to successfully send messages from one Pi to another!

Important takeaways we learnt about PyGame: event processing worked and processing get_pressed() didn’t for some reason.  Also, the display (game console thing) is necessary to get keystrokes because the keystrokes are to the display and not to our machines.

Once we have the motors we will be able to work on rotation and using the motor hat library. We also asked professor Savvides whether a CNN is the best model for our use case. The peer reviews were actually very helpful in pointing out situations and edge cases we hadn’t thought about.

We also set up our private git repo and checked that all of us could commit and push to remote from both Pis!

Neeti’s Status Report for 02/29

Neeti’s Status Report for 02/29

This week I worked on making a lot of the design choices for our project as well as the slides for the design review presention. I spent last weekend researching the different parts available to us and the pros and cons of each of these 

Neeti’s Status Report for 02/22

Neeti’s Status Report for 02/22

This week I worked on doing research for the design review while Gauri and Shrutika figured out how to ssh into the Pis. This was due to the fact that there are only two Pis and I did not have a USB to USB-c cable 

Neeti’s Status Report for 02/15

Neeti’s Status Report for 02/15

First weekly status report! We met twice this week during mandatory lab time as well as one additional meeting yesterday. This week we researched and ordered various parts. We were able to hone in on the specific parts we intend to use for the project. We began by checking out two RPi Zeroes from the 18-500 inventory but discovered that the Zero models have too few ports for our purpose. We then ordered RPi 4s, which arrived yesterday. We discussed various motors we could use (such as those used in Lazy Susans and Microwaves) and checked out three different motors from the inventory. We were able to collect the HDMI to Mini HDMI cables we needed from the IT department and we also met our friend who is a mechanical engineer for guidance on designing the physical aspects of the device. Additionally, we reformatted and downloaded NOOBS onto the SD cards that will go in the RPis and boot Raspbian.

This week I also read chapters 1 to 3 of The Pentium Chronicles and completed reading assignment 1. Gauri and I also spent some time looking over the 18-349 labs that involved motor control and Pi-to-Pi communication. We looked into PWM as well as PID controllers. We believe that a lot of the motor control for our project will look fairly similar to our implementations in labs 2 and 4.

We anticipate faster progress once we collect the RPis. We also realized that designing the physical aspect of the device will take more time than we initially predicted. However, we should still be on track overall if we continue to work on the design in parallel. Finally, next week Gauri and I hope to play around with the Pis and get some basic motor control working.

02/12

02/12

wiped, reformatted Samsung SD card on RPi Zero and installed Raspbian using NOOBS checked out three different motors from 18-500 inventory Lab tables are permanent 24/7 decisions/ideas: 1. use visual and audio input in combination for automatic mode instead of attempting array processing (i.e. use 

02/10

02/10

Picked up RPi Zeroes from 18-500 Inventory Ordered RPi 4s Looked into requirements for motors – <50 RPM is fine and sturdiness of wheel is more important