Edit intro.
This commit is contained in:
parent
55d7c94564
commit
febe73e925
12
intro.tex
12
intro.tex
|
@ -64,11 +64,9 @@
|
||||||
An HTTP-based JSON API server is hosted on the same hardware as the gateway, and applies configuration
|
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.
|
changes to collars through an application built for Android mobile devices.
|
||||||
A MariaDB SQL database management system is used to store the data
|
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,
|
received from the collar for viewing and analysis. This document
|
||||||
tested, and implemented in anticipation for the completion of the project. This document
|
contains all information and major documents gathered and created during
|
||||||
contains all information and documents gathered and created during the design and
|
the process of implementing the Fenceless Grazing System.
|
||||||
implementation of the Fenceless Grazing System in an effort to maintain an archive
|
|
||||||
of all of the work that was accomplished.
|
|
||||||
\end{abstract}
|
\end{abstract}
|
||||||
\end{singlespace}
|
\end{singlespace}
|
||||||
\end{titlepage}
|
\end{titlepage}
|
||||||
|
@ -89,7 +87,7 @@ The team consisted of three members:
|
||||||
|
|
||||||
\begin{itemize}
|
\begin{itemize}
|
||||||
\item \textbf{Ryan Alder} served as the liaison with Prof. Hamdaoui, and as a LoRa expert. Being the
|
\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
|
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
|
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.
|
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
|
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
|
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
|
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
|
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
|
for an explanation of why only a single device is currently supported). The next step for the
|
||||||
|
|
Loading…
Reference in New Issue
Block a user