Posted on

Lata’s Status Report for 03/14

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

 

Posted on

Team’s Status Report for 03/07

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 risks is that our second iteration of the PCB isn’t going to work. Each iteration takes time, so we want to get it right. However, with the mid semester demo coming up, we need a working MVP of our project, which will heavily rely on our PCB doing its core functions. Our contingency plan is to have a bread board version done so we can test out our software, continue iterating on our PCB designs and rushing the shipping times so they arrive quicker.

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 changes to the 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 a component you got working.

We have delegated tasks for spring break. Lata is going to test the PDR algorithm in MATLAB, Katherine is going to work on the route planning system, and Brandon going to work and order the second iteration of the PCB.

No changes to our schedule.

This is the second iteration of our PCB design

This is our code for wifi registration and sending location data

 

Posted on

Katherine’s Status Report for 03/07

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

Brandon’s Status Report for 03/07

03/07 – March 7th

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 completed 2 iterations of our pcb and ordered the pcb which arrived on Friday. The team also worked together in order to complete the Design Report that was due last friday. These were very large projects that needed to be completed immediately in order to move forward to our interim demo and get started on finishing our project.

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 behind schedule because of the pcb ordering time and it was not cheap to order the pcb which might be a concern. To catch up we need to complete key integration that is planned for this week.What deliverables do you hope to complete in the next week?

I hope to solder all components together to get a size reference for our hardware shell along with starting to code the large state machine for the firmware. Because I am hardware lead a key component of my work is integrating all of our hardware to our firmware and confirming it works correctly to match our MVP.

Posted on

Lata’s Status Report for 03/07

ACCOMPLISHED:

This week I implemented an iteration of PDR on MATLAB additionally now that our order of the IMU has come in I can now test it on a breadboard to see if my implementation of PDR is accurate enough or if I need to update it to a bit to make it more accurate for tracking and drift reduction.

PROGRESS / SCHEDULE:

My process is a bit behind schedule because it took a bit for the IMUs to come in however now that they are here and and almost everything we need to order is here I can go through and set up and test on a breadboard now with the IMU.

DELIVERABLES / NEXT STEPS:

Next Week, I will:

  • setup for UI and stages for firmware
  • Test the IMU + PDR on a breadboard and tweak as needed