This week I made a lot of progress with the Raspberry Pi communicating with the PCB. Now that we have all the project components, the Pi is able to communicate very well with the PCB, and able to access all the sensor channels very quickly. What I plan on doing this week is incorporating a PWM output signal from the Pi to the buzzer on the PCB to give the user auditory feedback on the metronome tempo. Apart from that, I plan on helping my teammates with their tasks to make sure we finish the final project on time for the demo.
Olek’s Status Report for 11/25
I’m not sure if a report is due for this week. I wanted to post one to make up for the ones I missed while I was away. This week I spent working on the raspberry pi code. I am still waiting on the PCB, so I fully fleshed out the code needed to talk with the local software on the computer. All that we need now is the PCB to correctly converse with my i2c code, and my project portion of the mvp should be met.
Team Status report for 11/18
This week we made progress around the board towards our MVP. The PCB has been ordered and should arrive sometime early next week. Furthermore, the raspberry pi/pcb interface has been modeled using an Arduino in order to support further development while the pcb is being delivered. This allowed us to find that the i2c libraries available on the raspberry pi won’t meet the standard that we need to communicate with the PCB, so a standalone library is being written. Lastly, we found where we needed to inject code into the Muscore library in order to visualize the notes, progress should be made this week.
Olek’s Status Report 11/18
This week I made a lot of progress on the raspberry pi I2C sending and recieving. Due to our PCB board being delayed, I used a spare arduino that I had on hand to act as a PCB emulator, which allowed me to put together a model of the PCB, and verify that the raspberry pi i2C sensor polling is working as expected.
Jeannie and I had to put together 2 bi-logic converters in order to support the 3.3v and 5v difference of the arduino/rasperry pi, but things worked as expected.
However, in the process I found out that the existing raspberry pi i2C libraries don’t meet my specifications for communicating with the ADCs that will be on the PCB, so I’m writing my own i2C master interface.
Olek’s Status Report for 11/11
This week I made progress on the raspberry pi i2c code. I started by having a usable GPIO version of the pi code to demo, showing the design of the transmission protocol. Since the demos, I have made progress into using i2c. Since our PCB development is running behind, I decided to use an arduino from home as a PCB emulator until the PCB arrives. The polling rate will likely be much worse, but in the worst case we should still be able to put a product together. Furthermore, this should allow me to develop the Pi-side code enough to quickly implement once the PCB arrives.
Olek’s Status Report for 10/28
This week I returned to campus and met with the team about the state of the project. I set up a weekly time to meet with my team to catch up with the pace and get back on schedule. It will be on Wednesdays afternoons from 5:00 – 7:00. I also allotted a 2 hour window where I will be in the capstone lab on Sundays.
Apart from that, I have loaded an OS onto the Pi and have successfully set up a development environment. I am working on a i2C polling code right now.