Posted on

Lata’s Status Report 04/26

Lata’s Status Report  for 04/26

ACCOMPLISHED: 

The firmware is being integrated with the software, it is sending the correct updated, and the ESPs are detecting each other. Currently, in the process of debugging the GPS module and the navigation updates for the arrow; however, sending and accepting invite works as well as detection. 

PROGRESS / SCHEDULE:

In terms of progress, we are still slightly behind schedule; however, I do believe that I will finish up my last few sections by the beginning of next week, leaving enough time for testing. 

 

 

DELIVERABLES / NEXT STEPS:

Next Week I will: 

  •  Figure out the arrow mechanism for the UI so that it is smooth and does well with the updated of the user moving
  • Figure out the issue with the GPS module so that I can move away from using pre loaded locations
Posted on

Katherine’s Status Report for 04/25

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
Posted on

Katherine’s Status Report for 04/18

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
Posted on

Katherine’s Status Report for 04/04

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
Posted on

Team’s Status Report 04/04 – Lata

03/04 – Lata 

The whole team should answer the following questions in the Team Status Report:

 

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

 

The most significant risk that we are facing right now is getting the PDR properly integrated with the GPS and the new iteration of the PCB arriving on time with enough time for us to test the firmware on it as well. We realized with testing for the interim demo that there were some errors in our initial PCB. We are ordering the PCB this week, on Monday, when ordering opens, and ideally, it will be here within the week, and we will be able to begin soldering and integrating the firmware onto the PCB fairly quickly 

 

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?  

 

The design of the system is staying the same; we just had to make some changes to the PCB because we faced some wiring issues, but every piece on the PCB is staying the same. The cost of this change is just financial because we made an error initially. 

 

Provide an updated schedule if changes have occurred.

This is also the place to put some photos of your progress or to brag about a component you got working.

 

Link to video of UI: https://drive.google.com/file/d/1uB-YKRFpqOqrMi1vG3DI5HIbTuG1QIWU/view?usp=sharing

VALIDATION TESTING: 

 

For validation of the product, we will be sending out user surveys and having different users use the product for a few days to see if they enjoy it and if it results in less stressful and easier navigation that we are looking for. Additionally, we will also be testing the device once it is fully integrated before we user test it with others. We will be testing battery life through the use of a full day and seeing how long it lasts in that time frame. Additionally, all of us are currently individually testing all of our parts and testing everything as we begin to integrate them piece by piece through walking tests, navigation and routing planning comparisons, and direct tests by seeing if firmware is working on hardware and being sent to software.

 

Posted on

Lata’s Status Report  for 04/4

ACCOMPLISHED: 

This week, we had our interim demos, and for these demos, I finished coding out a major portion of the UI process. It was being controlled by my laptop due to the fact that, in testing our firmware and hardware together, we also found some major issues with our first iteration of the PCB, so the buttons that we have on our current PCB don’t work. Additionally, I have completely finished implementing the PDR in C++, added a Kalman filter to it, and began testing and tweaking it to detect straps and distance accurately, some things that I am struggling with is the fact that because I am the one strictly testing the PDR the stridelength and step tracking is adjusted and tuned to my steps specifically so I need to do some research on what values would be best for distance ad step length for an average person so that it can work for everyone who is using the device. 

PROGRESS / SCHEDULE:

In terms of progress, we are still slightly behind schedule; however, looking at our interim demo, I am not as worried as I was before about integrating our biggest issue, is getting our new iteration of PCBs here on time. For the next week, we will be integrating the PDR with the software and GPS so that routes are properly updated and tracked. 

TESTING PLAN: 

  • For PDR, I am currently testing both indoors and outdoors with different distances. I’m testing 5m and 10 m walking straight to see if it can detect my step counts correctly and the distance correctly. Additionally, I am also testing distances with 90-degree turns to see if it is able to detect a turn and step. This will meet the USE case requirements as our main functionality is our device being able to navigate you correctly to the next device and if step length and distance predictions are wrong the navigation to the other device will also be wrong. 
  • For the UI, there isn’t really much testing to be done; it is just stepping through a false/real navigation and seeing if the screens are outputting the correct screens at each state. 

DELIVERABLES / NEXT STEPS:

Next Week I will: 

  • Finish integrating the PDR with the GPS routing – next Saturday 
  • Finish implementing all stages of the GPS- need to implement the idle stage – next Saturday 
  • Figure out how to get the ESPs to detect each other and send the information between them, and depending on whether they are a receiver/sender, have the screens display differently – two weeks

Link to video of UI: https://drive.google.com/file/d/1uB-YKRFpqOqrMi1vG3DI5HIbTuG1QIWU/view?usp=sharing

Posted on

Lata’s Status Report 03/28

ACCOMPLISHED: 

PDR is completely implemented in C++, finishing up the last few tweaks so that it detects steps properly and has minimal missteps. UI implementation has begun, and we have the screen working, which was an issue for a little bit.

 

PROGRESS / SCHEDULE:

Slightly behind schedule, need to have the UI mostly complete by the Interim demo; however, it will not have all of teh features, even though that is what we wanted. We still have some issues with the PCB, so any UI button press detection will be coming from the laptop keyboard. 

 

DELIVERABLES / NEXT STEPS:

Next Week, I will:

  • Complete the UI and have it working
  • begin integration of PDR and GPS
  • connect the firmware hardware and software
Posted on

Team Status Report 03/21

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

The most significant risk is that firmware and hardware needs a certain amount of integration. Software is more of an isolated system, but in order for firmware to be ready for the monday interim demo, we need to make sure the hardware components (gps, microcontroller, screen) are all working properly.

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

No changes were made to the existing design.

Provide an updated schedule if changes have occurred.

This is also the place to put some photos of your progress or to brag about 
component you got working.

No schedule was updated. We are all working on completing our individual sections to make sure we can demo our full individual systems properly. We are on track to meet the interim demo deadline on Monday. 

Diagram showing Firmware and Software Interactions

Software Dashboard

Posted on

Katherine’s Status Report 03/28

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
Posted on

Katherine’s Status Report 03/21

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