Errors
Errors
Human Errors
Human Errors
Throughout the extensive 3-week program period our project was filled with multiple unfortunate mishaps mostly consisting of third party disturbances or lack of better understanding from oneself, we like to call these disturbances, human errors.
For example, one of my many minor errors within the project was disordinance of the wiring when I tried to disassemble the data logger and reassemble it. As you can see each set of colored wires are in sections and connected in columns.
When I reassembled the the data logger I accidently connected the the red and black wires together which caused a short circuit and I couldn't upload my code.
When I reassembled the the data logger I accidently connected the the red and black wires together which caused a short circuit and I couldn't upload my code.
In this particular case we can see that there's an unnatural trough in the soil moisture/battery life graph but more specifically it's a disturbance with the soil moisture probe. From this we can deduce that it's likely someone pulled the probe from the ground and stabbed it back in quickly.
On this graph the air temperatures reach almost 60 degrees Celsius to, which clearly isn't feasible under the circumstances of our test sites.
Coding Errors
Coding Errors
For our data loggers to be programmed we needed to encrypt them with a certain for our sensors to work and for the data loggers to track them after every specific time interval.
Yet when verifying the code we ran into literal hundreds of error messages to the point where we need to use our mentor's code due to time constraints.
My partner on the other hand was just simply unable to open the Arduino file and had to use our mentor's code.
Yet when verifying the code we ran into literal hundreds of error messages to the point where we need to use our mentor's code due to time constraints.
My partner on the other hand was just simply unable to open the Arduino file and had to use our mentor's code.