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

03/21 – March 21st

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours). 

I fixed my mistake in my first soldering of our pcb and tested the hardware and confirmed that our PCB worked together. I also started the design of the hardware enclosure with the current dimensions.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

 

We are still on schedule, but need to work hard leading up to the demo this upcoming week.


What deliverables do you hope to complete in the next week?

 

Hardware enclosure, battery connection, Integration

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 currently is just not completing the work on time, we have had problems identifying exactly how the system is going to be built in terms of firmware and software and the way they interact. We have a plan to implement, so this next week will be integral into meeting the demo goals.

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 only change we’ve made is separating some more components from the firmware to the software. This isn’t a large change, but it is one we need to acknowledge.

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.

Posted on

Lata’s Status Report 03/21

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

Brandon’s Status Report for 03/14

03/14 – March 14th

 

 

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

 

We received our pcbs, I tested and soldered the pcbs, one issue that I had was that I actually layered two components on the same area but on different sides which required some creatively oriented soldering. Other than that I setup our github and I will now be making sure that the integration is complete meshing our test code together into well documented code.

 

 

 

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

 

We are on schedule but this week will be busy so lots of work has to be front loaded.

 

What deliverables do you hope to complete in the next week?

 

I hope to solder the second pcb and set of components together and to work on helping either with the user interface or fusing GPS data and IMU data together.

 

Posted on

Team’s Status Report for 03/14

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?

Our most significant risk is that for the interim demo, when we go to integrate our hardware and separate software services, it won’t work; however, I do think we will be able to have our parts working such that each thing can work in its own, and we are working to. We are mitigating some of these risk but splitting up tasks more so that one person is not struggling to finish everything at once. Currently, our plan is to haven’t everything working at a very base level; however, if we are unable to integrate, then together/ don’t have time, we will still show that they work separately, and we will integrate after the interim demo. 

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?  

We currently don’t have any major changes to the design except that we now want a bigger screen the cost should not be to significant as the screen only costs around $20. We did get some responses to our design report in regards to it not being as fleshed out as it should be for certain things such as design requirements and data to justify why we are working on adding more justification. 

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.

This week we met as a group and decided that our current screen is smaller than we want it to be for our project, so we have pivoted from a circular screen to a rectangular screen. Additionally with the intern demo coming up we have split up the work a bit more in terms of the software and what each of us needs to do for the project. 

No changes to our schedule. 

Posted on

Katherine’s Status Report for 03/14

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