Risks No additional risks. Changes No changes. Schedule Embedded: Eric and Melodee will need to fix the one remaining firmware bug. Tile Enclosures: Eric and Melodee will need to finish constructing all the tile enclosures. Circuits: Eric and Melodee will need to finish soldering the remaining PCBs. Eric will need to create a master tile. GUI/Interpreter: No additional changes.
Progress I unfortunately was not able to work on capstone as much as I would have liked this week, because I was really busy with two projects from other classes. What Eric and I managed to accomplish was fix the reflective sensor reading bug (pad readings didn’t always update between compilations) and refactor the firmware in an attempt to fix the communication bug. Refactoring improved the accuracy of our communication tremendously, but we still have an edge case that only…
Progress Early this week, Eric and I debugged the firmware to the point that it was demoable for our Wednesday demo. There were still a few bugs we had to fix, however, that led to the compilation working correctly around 50% of the time (sometimes, tiles would report incorrect encodings, and other times, some tiles would be missing in the final topology). We spent the rest of the week trying to fix the bugs. We have yet to get the…
Risks No additional risks. Changes No changes. Schedule Embedded: Eric and Melodee will need to fix the one remaining firmware bug. Tile Enclosures: Eric and Melodee will need to finish constructing all the tile enclosures. Circuits: Eric and Melodee will need to finish soldering the remaining PCBs. GUI/Interpreter: Aarohi is good to go for the GUI Interpreter from the MVP point of view, but she will continue looking at a more interactive GUI, and function implementation.
Risks No additional risks. Changes No changes. Schedule Embedded: The only thing left to do is to debug the firmware, once we have more tiles constructed. Tile Enclosures: Eric and Melodee are in the process of gluing the wood pieces together. Circuits: Eric and Melodee are in the process of soldering all of the PCBs. GUI/Interpreter: Everything is on schedule with the GUI and Interpreter. Aarohi has a version ready for the final demo, and is working on another version…
Progress This week, I got the firmware to be code complete, but I wasn’t able to debug it yet because we didn’t have the tiles prepared. So, Eric and I spent the rest of the week cutting out pieces of the tile, drilling holes in them for the sensors, and gluing them together (see Eric’s status update for images). We are also in the process of soldering the PCBs. By Monday’s demo, we hope to have at least some aspect…
Risks Most of the technical risks have been resolved now. The few that remain are very small, but untested. Our target clock rate could be too fast. We have only tested 10Hz so far. This works, but we have not tested 1KHz yet. We run out of time soldering together the remaining 26 tiles. I am confident that we will have enough time if the digikey parts arrive soon. Changes Last week, we were unsure whether our own personal wood…
Progress This week, I mostly worked with Eric to complete the C++ hardware interface. We ran into a few roadblocks while writing it, including limitations in the ATmega328p’s memory. However, as of today the interface is done and I can now move on to writing the firmware. Since writing the hardware interface wasn’t as great of a bottleneck as we had anticipated, we decided that I no longer needed to write the tile simulation. A significant contribution that I made…
Risks Embedded: The biggest risk we have is that the C++ hardware interface will take a while to make; this would delay the start of writing the C++ firmware. To mitigate this risk, Melodee and Eric will write a C++ tile simulator (similar to the Python tile simulator), which should be quicker to write. It will allow Melodee to write and debug the firmware earlier. Tile Enclosures: A risk we foresee with the tile construction is that the slight differences…
Progress I wrapped up my work with the Python version of the firmware in the beginning of the week. It can be found in the python_firmware directory of our repository. Eric and I then moved on to working in the C++ Arduino environment. We spent a day learning C++ (since we need to do more advanced things with it than what we’re used to). Then we began working on writing a C++ interface to the hardware to decouple the firmware…