Look who's talking!
This week we actually got started on setting up and working with the raspberry pis. A major issue we realized this week was again … lack of time. We didn’t realize how long it would take to do some of the tasks we assumed would …
UPDATE from 02/19 Meeting 2 at 213 conceptual OH: It worked woohoo! We did nothing different. We are able to ssh into Sam both through pi@172.26.213.148 and also pi@comovosam.wifi.local.cmu.edu. Will make this work for Sandy on Friday. In theory this should work since we registered it today.
No idea why it worked in the evening and not in the morning. We think it might be because it took time to “actually” register (but then ping worked before… so unsure).
First status report! We had multiple meetings this week to discuss which parts to order, collect and evaluate whether the RPi ZW would work for our project, read and figure out how to set up the SD cards to boot Raspbian OS onto the RPi …
Weekly post #1!
This week was a lot of working together as a team to make major decisions – we had several meetings including outside of class time to choose and order parts, and begin to work with what we have. We aren’t really behind schedule yet – the problem is we had several tasks starting this week that didn’t because of the time taken to order and receive parts. But hopefully we factored in enough slack time to make sure things get done by the dates we set to finish the specific tasks. I think next week as long as we put in the time we can catch up to schedule.
In the next week, I want to begin to design the actual platform – I have mech-e who said they would help me with the laser cutting, and figure out how to best attach parts. I think because we (Gauri and Neeti) have done motor control in embedded, writing the drivers and getting the motor working should go relatively quickly and while they set that up I’ll begin making the platform and figuring out pi-pi communication (as soon as the Pis come in).
This week we ordered several parts, including the Raspberry Pi 4 Model B (x2), got the cables necessary to connect them, formatted the SD cards that will go into the Pis once we get them, and put NOOBS on them. We met with a mechanical …
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.
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 …
