Max’s Status Report for April 27, 2024

This week, I tested the sensor module circuit without the LM7805 and unfortunately got similar results as before with the circuit lasting about 2.5 days. I am now rerunning the test with different software since the HTTP requests were being sent at a 5-second interval, but I think that making the interval 1 minute more resembles how a bench is used and I’m confident we’ll get a better battery life this way. I also cut the pieces for the final people countercase, and I’ll be assembling it tomorrow as I have to work on other classes. Also, at the start of the week, I 3-D printed the sensor case with no issues. We’ve planned our demo as well for next week, and plan on showing a live feed with the help of a friend of the gym to show that our application works in real-time.

My progress is on schedule as I had allotted time for both debugging the sensor and creating the demo cases for the two sensor systems.

I look to have the cases finalized for the demo with everything soldered together inside and complete the final deliverables (poster, video, report) with my teammates.

Team Status Report for April 27, 2024

Max is still working on improving the battery life performance of the sensor so that it performs closer to our requirement of a week-long battery life. He continued testing this week without LM7805 linear voltage regulator, and the the results resembled the previous battery life of a little less than 3 days. We plan to test this again with different software so that the period between HTTP requests is longer to match the sensor behavior in the gym.

No changes have occurred, but Max is still looking to see if a voltage regulator is necessary in the sensor circuit.

Sid is currently working on improving the accuracy of both models being used for prediction. This week, he continued testing standard models to compare their accuracies, and experimented with using a variety of input variables to find correlations. We plan to use a larger amount of data, which would include points collected over the last month via the sensors.

We are looking to finalize our deliverables for this week, and are preparing for the final demo. The sensor case has already been made, and everything will be soldered and assembled at the start of this week.

 

Team Status Report for April 20, 2024

A risk we are currently working on mitigating is the battery of the bench sensors dying to early. To extend the battery life, several strategies were employed. The first strategy consisted of changing the software on the bench sensor module to only connect to WiFi when sending requests because WiFi is very power hungry. Additionally, an extra battery pack was added to the sensor module to increase the life as well.

Another risk was with how our occupancy data was being stored. There were many occasions where occupancy was being logged 2-3 times per hour instead of just one. These entries were merely duplicate entries. To solve this problem, I am currently working on a Python script that will clean all of our data.

As previously stated, more batteries were required for the sensor module.  No extra cost was incurred because we already had bought extra batteries. Additionally, we plan on adding a feature that predicts the probability of bench occupancy at a given time. No other changes were made to the existing design.

 

 

Max’s Status Report for April 20, 2024

Last week, I improved the power performance of the bench sensor modules, but I realized that reaching our use case requirement of 1 week for the sensor is unlikely. I modified the detection algorithm so that Wifi is only on when the device is sending a request. This is still not enough, and it seems that Wifi as a protocol is too expensive.

This week I worked on creating the models for both the people counter and the bench sensor.  For the bench sensors, I produced an initial version of the case using Rhino and am currently 3D printing it. The case should fit 2 mini breadboards, a battery pack, and the IR sensor.  I also collected material for the people counter, and I put it together this week.

I am currently on schedule.

I look to finish the case for the people counter and continue looking for ways to improve the power consumption in the people counter.

As someone on the software track, working with mostly hardware this project has been both rewarding and challenging. I’ve gotten better at reading datasheets for different components to understand how they work. I think that my experience in 18220 was useful in building the circuit. I’ve also found blogs written by fellow tech enthusiasts very useful when I was getting started as they gave me a base for understanding how the NodeMCU can read analog data, and how it communicates with outside devices.

<==== This is the layout of the bottom of the case.

The .stl file of the top.

The .stl file of the base.

Max’s Status Report for April 6, 2024

I have put aside my plan to build a case for the bench sensor and people counter hardware setups, and have spent time debugging the power issue with my bench sensor. It is running out of battery too quickly. After some probing, I narrowed the issue down to the NodeMCU being the problem, but I am still looking into how it can consume less power.

My progress is on schedule, but I would like to resolve the power issue soon. •

I am hoping to have a plan for fixing the power issue.

I have already verified the IR sensors by measuring my distance from them and reading the output voltage levels to verify that they work within the range they were advertised (100-550cm). I used equipment available in the ECE Lab of Hammershlag. I look to re-verify the accuracy of the bench sensor module detection algorithm by running 10 trials of someone arriving, 10 trials of someone leaving, and 10 trials of someone using the machine with a water break and with obstacles in the background.

 

Team Status Report for April 6, 2024

– 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?

Right now, our biggest risk is the battery life of the bench sensor module. We have concluded that some data has been missing because it dies prematurely. The NodeMCU is the cause of the batteries being drained, so Max is currently looking for ways to conserve power consumption.

– 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 immediate changes have been made, but one might have to be made this week. Our investigation will determine if it is necessary or not to make any significant changes.

• Provide an updated schedule if changes have occurred.

We updated our schedule for the interim demo this

Status Report 8 Answer:

We have already been able to validate our system with each subsystem that is set up in the UC gym being able to communicate with our server. To validate more rigorously, we plan on replicating several scenarios with both the people counter and bench sensor on our own, and ensure that results are both real-time (as we defined) and accurate as we defined.

Max’s Status Report for March 30, 2024

I finished testing the components for both the people counter and bench sensor, and implemented the hardware for both the people counter and the bench sensor. I also implemented the software for the bench sensor and worked with Sid to implement the software for the people counter. We were able to integrate everything together with the EC2 instance and we set everything up in the gym (check our Team Report).

My progress was behind, but setting up early this week has helped me go back to schedule.

I do not have any deliverables for the week, I look to just refine both the people counter and bench sensor casing by most likely using laser-cut wood.

Here is the link to the bench sensor code: https://github.com/maxcadams/capstone-bench-sensor/blob/main/bench_sense.ino

 

 

Team Status Report for March 30, 2024

There are no immediate risks that could jeopardize the success of our project. We have been monitoring the output of both the people counter and bench sensor systems, and they seem to be working well. We look to make a new poster and notify gym administrators to not move any equipment and also to not stand in front of the people counter as that can have an effect on the occupancy count of the gym.

No changes have been made to the existing design of the system. We have the bench sensor and the people counter as mentioned before running in the UC gym.

There has also been no updates to the schedule.

The two components set up in the gym^, people counter on the disk and the bench sensor is at the window sill.

Max’s Status Report for March 23, 2024

I finished testing all of our hardware components this week, soldering together the ADC for the people counter and performing tests on the IR sensors that will be used. I measured the distances with voltage readings and then compared these to the ADS1015 (the ADC) in the NodeMCU. I also set up the Raspberry Pi for the people counter. I have an algorithm for the bench sensors ready for set up this upcoming week.

 

 

My progress is slightly behind, I wasn’t able to set up the system in the gym with my group. Since we are finished testing everything and are putting our systems together, we are going to have the preliminary systems set up in the UC gym at the start of this week.

We’d like to have the systems up in the gym and begin analyzing the data we collect.

Team Status Report for March 23, 2024

There are no big risks right now that could jeopardize the success of the project. Any risk was mitigated this week through our testing of components and prototypes of our subsystems. The components also interact with the E2C instance with the backend API. We will be testing in the gym tomorrow and then setting up Monday.

The only change that occurred was the IR sensor being used with the people counter. We decided to use the longer-range sensors in practice because the actual range worked better with our tests.

We are slightly behind in setting up the system in the gym, but we will be doing this early the week of 3/23.

This is our people counter prototype^