[Charlotte] Status Update 11.2.2019

[Charlotte] Status Update 11.2.2019

What did you personally accomplish this week on the project?
This week I was able to get wifi communication working between the Rpis.  Our focus for this past week/weekend was to get the pipeline of our system working.  By that I mean getting a sub hub to send information about the status of a PIR sensor to our main sensor hub that will then send this information to our UI built using React.  The majority of the pipeline is now complete.  I have written the necessary code to get the sub hub Rpi to send information based on the status of the PIR sensor to the main sensor hub.  Now the main sensor hub is ready to send information to the UI.  I have not completed that step yet since it will require Alisha’s help since she is the one who has been focused on the React code for the UI.
Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?
We have not completed the work necessary for our demo yet, but I believe that is fine because I am confident we should be able to finish it tomorrow (Sunday) before our demo on Monday.  When we accomplish that I think we will still be in good standing to finish the project by the end of the semester.  We are a little behind according to our gantt chart; however, I am not too concerned because we built in grace time in the tasks we assigned to one another so we should still be fine.  Also, I have finished interviewing and Alisha have recovered from being under the weather so we both have more time to devote at our project.
What deliverables do you hope to complete in the next week?
By tomorrow night I expect that we will have our full pipeline working so that the information for a PIR sensor can be propagated to the UI of our React application.  From there, I hope to work with the Pi Cap library more this week and hook up multiple sensors to the Rpi so that the sub hub can send date about more than one sensor to the sensor hub.  Assuming that goes smoothly, I think it would be a good time to either focus on improving the PIR sensor performance or having 2 sub hub Rpis working in communication with the sensor hub.  To get this to work a believe a few changes would need to be made to the existing code.
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?
I still think the biggest risk in our project is the PIR sensors, but we have avoided spending more time on this because there are other more important part of our project that should be focused on.  Once we have our MVP working I think we can revisit improvements to the PIR sensor so that it preforms better.
I have tried to attach a video to this post but the size of the file was too big so I took screenshots a critical points in the video and have attached them.  Sorry the quality is a little weak but hopefully you can tell that the terminal output of the screen is indicating the state at which the sensor is in.  The sub hub is sending information the the sensor hub every 3 seconds.

I am triggering the PIR sensor by moving my hand in front of it.
pointing to terminal output indicating the status of the PIR sensor that is coming from the sub hub (client)
Sensor hub (server Rpi) look at the bottom left of the image
picture of the terminal output from the sub hub (server) that is receiving information about the PIR sensor over wifi from the sub hub (client)

Leave a Reply

Your email address will not be published. Required fields are marked *