Posted on

Brandon’s Status Report – April 4th

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). 

This week I finished designing our second iteration of the pcb, this time with proper breadboarding and spatial checks in order to make sure we have a correct design, one other error I forgot to mention was putting our breakout module in a different orientation in order to enable the screen to be in the correct orientation.

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 slightly behind as we needed to start testing the battery. It will just have to be a rush lol.

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

I hope to order the pcb and battery, and fully integrate the hardware with the firmware.

Now that you have some portions of your project built, and entering into the verification and validation phase of your project, provide a comprehensive update on what tests you have run or are planning to run. In particular, how will you analyze the anticipated measured results to verify your contribution to the project meets the engineering design requirements or the use case requirements?

One test for validation that I’ve used is completing a whole user flow using both the PCB and the breadboard circuit.

For verification there is are CDC checks that make sure that my pcb doesn’t violate or forget any important nets that need to be included in the design.

 

Posted on

Brandon’s Status Report – March 29th

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 finished debugging our PCB, there were a couple of issues, mostly during development I didn’t comb through our MCU’s documentation’s well enough. So in summation I put SPI connection on pin 15 which is used to communicate to memory in the GNR8, another issue I created was putting signals on the usb differential pins, I thought that the differential pins were used for controller peripherals with them, not to literally control the MCU. Another issue is that I spatially created an invalid design, the IMU cannot sit where it should if there is a physical buzzer in the way. I have soldered and prepared the pcb for the interim demo.

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

Because i have a solution for the hardware, it doesn’t put the whole team behind, but it does put me behind. This pcb will be our screen and IMU testing board, so it does serve some purpose.


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

I hope to finish the updated design for the pcb and get started with integrating all the code from firmware and software.

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.