Compare commits
4 Commits
ec7fc26f82
...
a4a46c8330
Author | SHA1 | Date |
---|---|---|
Danila Fedorin | a4a46c8330 | |
Danila Fedorin | febe73e925 | |
Danila Fedorin | 55d7c94564 | |
Danila Fedorin | 72c4dc7366 |
|
@ -1 +1 @@
|
|||
Subproject commit d3aae7368c44116be5967f0f8a9d2a34175a4a7e
|
||||
Subproject commit 001b280936e06bf4a74f97fbcb19d5ec5374813d
|
14
intro.tex
14
intro.tex
|
@ -64,11 +64,9 @@
|
|||
An HTTP-based JSON API server is hosted on the same hardware as the gateway, and applies configuration
|
||||
changes to collars through an application built for Android mobile devices.
|
||||
A MariaDB SQL database management system is used to store the data
|
||||
received from the collar for viewing and analysis. This system has been finalized,
|
||||
tested, and implemented in anticipation for the completion of the project. This document
|
||||
contains all information and documents gathered and created during the design and
|
||||
implementation of the Fenceless Grazing System in an effort to maintain an archive
|
||||
of all of the work that was accomplished.
|
||||
received from the collar for viewing and analysis. This document
|
||||
contains all information and major documents gathered and created during
|
||||
the process of implementing the Fenceless Grazing System.
|
||||
\end{abstract}
|
||||
\end{singlespace}
|
||||
\end{titlepage}
|
||||
|
@ -89,7 +87,7 @@ The team consisted of three members:
|
|||
|
||||
\begin{itemize}
|
||||
\item \textbf{Ryan Alder} served as the liaison with Prof. Hamdaoui, and as a LoRa expert. Being the
|
||||
most familliar of the three team members with the LoRa protocol, he oversaw and aided the
|
||||
most familiar of the three team members with the LoRa protocol, he oversaw and aided the
|
||||
implementation of the collar and gateway, each of which used the protocol to communicate with
|
||||
the other. Ryan also tested the system in practice, measuring the effective range of the
|
||||
components and verifying that data can be transmitted back and forth.
|
||||
|
@ -127,7 +125,7 @@ At present, the collar is capable of sending its position, retrieving valid graz
|
|||
that it is in a valid position. The next step on the collar side, then (after the hardware changes suggested
|
||||
above) would be to add to the collar a physical indication of whether or not it is in a valid grazing
|
||||
boundary (see the Design Document below for an idea of what that is). This physical indication can be
|
||||
an LED light, but the final goal would be to have that indication be a buzzer or an eletric shock.
|
||||
an LED light, but the final goal would be to have that indication be a buzzer or an electric shock.
|
||||
|
||||
The gateway software is capable of receiving and configuring a single collar device (See Appendix 4
|
||||
for an explanation of why only a single device is currently supported). The next step for the
|
||||
|
@ -145,4 +143,6 @@ of authenticating and working with the API server, viewing animal locations,
|
|||
and of modifying collar grazing boundaries. Next steps could include the display of additional
|
||||
statistics (this would also require changes to the API server).
|
||||
|
||||
Please refer to Appendix 4 for a description of all things that need to be done.
|
||||
|
||||
\end{document}
|
||||
|
|
Loading…
Reference in New Issue