Risks The main risk we foresee right now is the required tile clock speed being too fast to be driven by IR LEDs. As a contingency, we would have to loosen our requirement on our compile time. However, we are fairly confident that we can overcome this issue by reducing parasitic capacitance and specing out higher quality components. Changes Our backup battery circuit turned out to be not as trivial as we thought, and will require some more research and…
What did you personally accomplish this week on the project? Finalized the inter-tile communication protocol with Melodee Result: The protocol should be able to work with only three simplex communication channels per side Wrote a tile-to-tile python simulator for Melodee to use to implement the tile’s internal state machine and prove the communication protocol. Result: The simulator allows you to connect arbitrarily many tiles together and configure them with any encoding. Each tile operates in its own thread and the…
Progress Eric and I worked together on writing the Python simulation of the tiles (representing a tile’s sides, connections between its neighbors, clocks, etc). Then, after establishing the communication protocol with Eric, I began working on writing the actual firmware logic in Python to test our embedded logic. So far, I have some aspects of the state machine logic for what each tile’s side should do during a falling and rising edge of the clock, and what they should do…
Happy Valentine’s Day and happy first blog post! At the beginning of this week I worked on getting set up with the Pololu 3pi robot. Since I’m working from a Macbook with USB-C ports, the USB to USB-C adapters interferes with the communication ports with Arduino, which is why I’ve been working out of the HH 1303 lab this week. This is probably not sustainable, so I’ll be looking for a solution where I can work on the Arduino code…