Author: lsharma

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

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

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

ACCOMPLISHED: 

Implemented some of the PDR in C++, still in the process of completing the translation and testing after fully translated, and began coding out some more of the UI for the screen so that we are able to use it for our interim demo on the 26th 

PROGRESS / SCHEDULE:

Slightly behind schedule, however, I want to finish translating the C++ by Sunday night/Monday and have UI mostly completed, maybe without the idle state if necessary, by Tuesday so that we can have the last two days to do some level of testing and last-minute fixes before the interim demo on the 26th 

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• C++ translated and slightly tested by Monday latest
• UI completed( without idle state) – Tuesday 
• Last-minute self-testing – Wednesday 
• Other major testing – next week 
• Finish UI by next week

ACCOMPLISHED: 

This week, I began PDR testing in the breadboard and began my implementation of the UI on Arduino for our March 26th interim demo. Additionally, we talked about the fact that our screen may be too small for the information that we want displayed on it, so we have decided to buy a larger square-shaped screen. I also began wiring up our current screen on the breadboard to the ESP and Eyespi breakout, so that we can confirm that the Arduino code is outputting onto the screen correctly I have not begun testing this yet. 

PROGRESS / SCHEDULE:

My progress is not mostly on schedule; however, some of the tasks I was initially doing have changed because we realized how much more work certain sections were than others. In the next 2 week I need to finalize setting up the UI stages and the interface of what each step of the process will look like, and we will integrate the PDR with the GPS code that we have. 

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• Fix the issues that I am having with my basic Arduino display code showing up on the Screen 
• Finish coding the main states for the UI 
• Implement the PDR from MATLAB into C++ and test it there to see if it works before we combine with the GPS code.

PDR code(matlab):

ACCOMPLISHED: 

This week, I worked on learning more about PDR and how to implement it in MATLAB for basic user testing, with that I began implementing it in MATLAB and need to test it with our Phones IMU so that I can have a basic understanding of it when we go in and implement it into our Firmware. Additionally, now that we are more set on what we want to do and how to approach our problem, I know what I need to work on with the UI for the different stages the User will see, depending on the device’s state. 

PROGRESS / SCHEDULE:

My progress is behind schedule because I wanted to have finished testing the MATLAB code with our phones by this week, because we were hoping to have the IMU’s by now to test on a breadboard but due to ordering time the IMU’s still haven’t arrived so as a whole testing PDR is behind because we don’t have all the pieces yet so being behind on testing on the phone doesn’t affect the timeline, but rather not having all the parts does. 

DELIVERABLES / NEXT STEPS:

Next Week, I will:

• PDR on Matlab – by Monday
• PDR test on Matlab with phone – by Monday
• PDR on breadboard – when IMU gets here 
• start to figure out the setup for UI and stages for firmware – Ideally by Friday