analyti

The goals for this week were to finish the battery indicator, test the accuracy of the speed and start working with longer distances. 

​

Because we knew that after three hours one of four bars was lost on the battery, we decided to run the battery life indicator on a timer. Using a built in Arduino function, the battery indicator will lose a bar every three hours of run time. It was tested first with 5 minute intervals and then the timer was increased to 3 hour intervals after the successful test. 

​

A speed code was created that we believed to be efficient, but after further testing, we saw that it was producing incorrect readings. With some more research, we found a speed trap program utilizing the LIDAR-Lite v3 sensor. The initial tests seemed to show accurate readings and when we were able to calculate what the speed should be versus the readings we were getting, we found the code to be accurate with only a small window of error. 

​

An issue that arose, however, came when we started to test long distance readings. With the speed code, it would only update the readings between 10-20ft with no change occurring at greater distances. We also ran a program that converts the sensors cm readings to ft and we were unsuccessful in getting readings past 25ft. We tested with Sean and I in front of the sensor, a box and a car. The box seemed to work the best, with minimal to no success with the car. Our goal now is to increase this distance as much as possible and get it to read a car so we can collect our results.