This week I brought up the IMU and microcontroller: I soldered on the pin headers and the jumpers on the IMU, got them all wired up and then tried to get them to talk to each other. Getting this all to work took a bit of debugging, but I was able to read data from the IMU onto the microcontroller. I have it working over USB, no bluetooth yet. It currently prints out the acceleration in x, y, and z as well as the gyroscope data in x, y, and z. I was very happy once I was able to actually see the IMU data printed out over serial.
I also spent time working on the prototype version of the buttcap attachment. It is currently just a prototype and much larger and bulkier than the final version will be, we just wanted to get something working with the dev boards so that we can start collecting data as quickly as possible. The size is heavily constrained by the dev boards vs having just the bare components. The most important design constraint to determine is how we actually attach our device to a tennis racket in the least intrusive way possible and also make it adaptable to a variety of tennis rackets. I plan to visit a tennis store to look at a bunch of rackets and hopefully talk to a worker there who can tell me some of their ideas.
My progress is currently on schedule but I foresee challenges adhering to the planned items this week. In our schedule I am supposed to finish the hardware design next week, but I think this will take multiple iterations and not be done until we have the bare components. Our team is meeting tomorrow to revise our schedule and adjust. I do not think we planned enough time for hardware design iterations. We have physical prototyping as a multiple week item and I think we can adhere to that but the final enclosure design task should be broken down into more tasks and better scheduled.
In the next week I hope to get a more polished version of the prototype hardware done, and start collecting some initial data from the IMU while it is attached to the tennis racket. Part of this involves ironing out the specifics of the data flow, which Mario is doing. It is important for me to sit down and go through the design process of our hardware design with higher fidelity next week. I want to have a clear actionable design that I can work on some over spring break, and do PCB board design, etc. other CAD as needed. 
