Camera Struggles

Sometime between the end of our last sprint and when we were ready to start testing our finalized code, our raspberry pi camera stopped working. We began getting messages telling us to check all our connections and update our firmware. We googled all the messages we were getting and checked all our connections several times but were not able to resolve our errors. In class on Friday, we told Aaron what was going on and he gave us two more raspberry pi cameras to try. We tried both of those cameras (or so we thought) and nothing was working. We were getting different error messages with different cameras but still error messages nonetheless. Katya and I spent several hours last night trying our camera on three different raspberry pis (but still with our SD card) and trying to disconnect and reconnect all camera connections. Instead of running our code, we simply tried (and failed) to take a still image with each camera. Finally, we met this morning and decided we should start documenting all the errors we were getting. We were very frustrated and had a new SD card that we thought we might need to use to start fresh and download our code over again. As we were going through and documenting things we wanted to make sure we tried each camera with our raspi and our SD card before we started with a new SD card. Upon trying to take a still image with the third camera we found that it worked! We then tried running our code and that worked as well. We even tried our newest code that could detect motion in six panes and be started from the web app that had not been tested yet and found it worked after correcting one small typo! As frustrating as this experience was we were very glad to find that everything was working. Now all we need to do is get our serial messages working and our whole system will be done! I am excited to see how it all comes together!

- Vicky

Comments

Post a Comment

Popular posts from this blog

Where Mechanical At

Sprint 2 ended on Friday and we have our MVP! What that means for mechanical is that we have a box that can move nine different nodes, but control 3 sets independently, using three actuators. We made our prototype with some scrap .21" hardwood with the laser cutters. We converted the rotational motion of the sliders into linear motion with a pin and rack design, with the rack mounted on a slider with ball bearings to reduce the friction. The three gears were connected with a rod so that as one gear rotates the rest rotate as well. Our challenge coincided with retaining the gears with the bearings linearly, since the gear shaft would often tilt down (it was not a perfect press fit. We ended capping both sides of the shaft to retain it, but due to a misprint, the final design was switched, so the cap was not as effective as it should have been. The biggest issues with this design is that there was a lot of friction in the gears, and the system was too constrained, which made rotatin
Read more

Mid Sprint 4!

The final sprint has come to pass and demo day is just around the corner! The mechanical team has worked hard to get the entire mechanical system up and running and the software/electrical team is currently working toe get the system flawlessly integrated with the web app and integrating the sound detection code into the system. We are really excited about the final demo day and we think we are in good shape for getting all of our ducks in a row in time. Stay tuned!
Read more
Image
Today Peter and I worked on reading and interpreting audio signals using pyaudio. We made use of functions from Allen Downey's ThinkDSP book to help us extract frequencies and magnitudes for .wav files. We were able to graph the distribution of the frequencies and their magnitudes and were able to see a difference when we recorded a sound with a low frequency and one with a higher frequency. Our next steps are going to involve figuring out how we can extract useful information (frequency with highest magnitude) as our code is running. We might also try to use threading so that we can be recording and interpreting sound data at the same time.  - Vicky
Read more