Category: Katherine’s Status Reports

ACCOMPLISHED: 

This week, we worked on our final presentation and testing. We had to collect all testing numbers for our presentation. I put together the slides for the presentation and delegated tasks. I finished putting together and rehearsing slides. I also started designing final poster and decided on what will go into the demo video.

PROGRESS / SCHEDULE:

My progress is on schedule as we made a few changes last week.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Finish full integration testing
• Finish poster
• Finish Report
• Work with Brandon and Lata on video

ACCOMPLISHED: 

This week, we worked on our final presentation. We went through feedback from the last presentation and decided we needed better documentation for software tradeoffs and software system structure. We also created plan for user surveys as oppose to full on user testing. This rescoping was necessary because we are still working on software firmware integration, and hardware firmware integration.

PROGRESS / SCHEDULE:

My progress is on schedule.  However, we are a few days behind integration, which is why we needed to rescope our testing plan.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Finish final presentation
• Begin working on final deliverables
• User test

ACCOMPLISHED: 

This week, we had our interim demo. I helped create the gantt chart. I also finalized my dashboard. I created a powerpoint for the demo and a script that allowed my part to be under 3 minutes. I also planned for the next deliverable and solidified plans for integration.

PROGRESS / SCHEDULE:

My progress is on schedule.  The software and software demo is complete.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Create readme for software so lata can create firmware code based on my software endpoints
• Start working on final design report

ACCOMPLISHED: 

This week, I focused on getting everything ready for the interim demo. I hosted  the server on Google Cloud and created a simulation dashboard. The dashboard mimics the entire registration, invite, and navigation process. I created a map that shows all users within 75m radius. I also had the dashboard show the UI and arrow direction as the 2 users navigate towards each other. I also worked on documentation. Brandon and I discussed what information will be stored on firmware (RAM and local vars) and what will be stored on the server (sqlite and local vars) . We also met with Prof.Theo to discuss libraries and how hardware will interact with software

PROGRESS / SCHEDULE:

My progress is on schedule.  The software and software demo is complete.

Software Dashboard

Brainstorm of what will be stored where for firmware

Document for firmware and software interactions

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Integrate firmware with my software

ACCOMPLISHED: 

This week, I focused on restructuring the route planning system and establishing a clear separation between firmware and software, which allowed me to define the necessary API endpoints for the software. I also implemented a few unit tests targeting these endpoints. I met with Prof. Theo for guidance on how to best separate firmware and software systems. Previously, I had been thinking about it as full systems (route planning system, friend system). However, these full systems involved both firmware and software, which meant I was creating software, but also trying to integrate it with firmware at the same time.

I received feedback that the software was underdeveloped compared to the hardware, so I prioritized technical documentation. I developed a breakdown of design choices and trade-offs for each software component. This documentation is not part of the live demo (which is our next deliverable), it provides a framework for my design choices and satisfies requirements for the final report.  I will continue iterating on these documents based on team and advisor feedback.

PROGRESS / SCHEDULE:

My progress is on schedule. This week I took some time to step back and reflect. However, it follows the schedule we have laid out and doesn’t impact plans.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Get feedback/ iterate on software documentation(tradeoff, use survey, test plan for individual software components)
• Create more comprehensive unit tests for software features
• Help w the firmware integration process

ACCOMPLISHED: 

This week, I debugged and tested my code for the route planning system. Currently, the microcontroller can communicate with the server, it can connect to wifi, after a few minutes of standing outside, the gps starts to output location data. This data gets sent to the server, and it creates nodes between the microcontroller and a hard coded destination location. It sends back an arrow direction that points towards the next node in the route. When I get to the next node (within 3m), the server updates and points to the next node. The current issue I hope to address is when wifi goes out. During testing, this happened more frequently than I had anticipated. I will need to further test the system to see if this is something we need to fix, or if the wifi outage is short enough so that navigation is not impacted.

PROGRESS / SCHEDULE:

My progress is on schedule. I aimed to finish debugging and start testing this system last week and I was able to accomplish this goal.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Integrate Lata’s firmware PDR code into my gps code
• Create user testing plan 
• Write out justifications/ come up with justifications to all our assumptions in our design writeup.
• Continue testing my route planning algorithm

ACCOMPLISHED:

This week I received the microcontroller, the IMU, and the GPS. I was able to start testing with these three pieces. I also was able to register the microcontroller to the school’s wifi. This will allow the microcontroller the communicate with the server.

PROGRESS / SCHEDULE:

I wrote out the arduino code to send gps location to server and receive direction arrow from the server. I’m still debugging the logic for this code. The goal is to have the route collection process done by the end of this week. I am on schedule as I was able to figure out wifi registration.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Have the arduino code for sending location and receiving arrow direction working

ACCOMPLISHED: 

This week I worked on setting up the server, integrating the Google API, creating designs for firmware and software (block diagrams), and creating user flow diagrams. For the design presentation, I created slides for design requirements, overall system diagram, firmware system diagram, and software system diagram. For the design presentation, we heavily focused on creating the user work flow that was easy to follow and also calculate power consumption in order to meet user requirements. I have also started testing our server system with our gnss module. 

PROGRESS / SCHEDULE:

My progress meets the schedule. I was able to finish Google maps API integration this week as well as the design presentation. Because of the design presentation, we also have a good idea of what the next few weeks looks like for software. We also were able to solidify task delegation since we decided what is going to be on firmware and what is going to be on software. This makes separating work and responsibilities a bit easier going forward. 

 DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Learn how to connect devices (microcontroller) to wifi
• Implement the route planning system
• Implement database
• Learn how software will communicate with firmware 

ACCOMPLISHED: 

This week, I worked on the design presentation. After meeting with Prof. Theo on Monday, we decided that we need to scope down our MVP. My team and I worked on creating the user walk through and aligning on a few major details. The first one being whether or not we want to include indoor tracking as a part of our MVP. We ultimately decided against it as we were still unsure of how we wanted to implement indoor tracking and at this point we needed to be certain of our MVP. I also worked on understanding the server side. I researched into API integration with Google Maps and how to set up our servers. We also spent a while on UI designs and user journey. Our product has many states (sleep, searching, etc.) and we wanted to draw out exactly what these states meant and how our interface will allow users to go from one state to the next. 

PROGRESS / SCHEDULE:

My progress is on track. My tasks for this week was to set up servers, research API integration, and create user journey and UI. Our major goal this week was to design + order to PCB, which would allow us to integrating and testing our UI and communication.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Integrate API to node.js
• Decide on communication protocols