You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
35 lines
3.6 KiB
35 lines
3.6 KiB
\documentclass[11pt]{article}
|
|
%Gummi|065|=)
|
|
\usepackage{graphicx}
|
|
\usepackage{caption}
|
|
\title{\textbf{ZMHW Uno Modector}}
|
|
\author{Steak Electronics}
|
|
\date{}
|
|
\begin{document}
|
|
|
|
\maketitle
|
|
|
|
\section{Goal}
|
|
ZoneMinder is a GNU/Linux FOSS CCTV program, and it has the ability to interface with external hardware sensors\footnote {https://wiki.zoneminder.com/ZMTrigger, also read the zmtrigger.pl found on ZoneMinder installations, as well as the official Documentation}. I wanted to build a simple, but functional, and practical board to use as a hardware motion detector. Onboard software motion detecting is faulty, and spotty. Transitions from IR to Non-IR, leaves blowing in the wind, bright lights - all these things can cause false alarms. Hardware motion sensors have the potential to mitigate hopefully 100 percent of false alarms, and give the user a reliable alarm and camera monitoring system.
|
|
\section{Revision One}
|
|
It was decided to create the hardware motion detector or modector in a frugal manner, for the average hobbyist, or homeowner to be able to build it. ENC28J60 was used for internet (thus a wired connection), UIPEthernet will be the Arduino Ethernet library (available from library manager), and a 5GHz microware motion detector was used. \footnote {the HFS-DC06H, which is similar in function to the HB100 board, but includes the circuitry needed to give a digital logic high, when motion is detected. Other options are PIR (prone to faulty alarms in sunlight, but works well in dark areas. Additional software programming needed, or a light sensor), Ultrasonic (possibly damaging to animals...), and laser or actually infrared diode sensors such as the Sick sensor (these work well, but can be stepped over), among others.}
|
|
\includegraphics[scale=0.5]{../pics/schem.jpg}
|
|
\captionof{figure}{Revision 1 schematic}
|
|
\vspace{0.3in}%line break
|
|
The first revision of this board came upon some problems, which were obvious upon soldering the first board. Originally, the board, which is an Arduino shield, was designed to make the assembly process easier. Early prototypes used protoboard, and required about 2 hours for building at least. The shield could be developed in the same amount of time, and then all future builds can be done within 30 minutes. However, the first shield had the first following problems:
|
|
\begin{itemize}
|
|
\item The ENC modules are designed with headers soldered on, and that makes removal of them quite difficult.
|
|
\item Users might want other sensors, and while feature creep is an issue that is to be wary of, I see no reason to throw a few other sensors on the board in a strictly optional sense (use them or not, no matter).
|
|
\item In the same idea, a microphone and speaker may be useful.
|
|
\end{itemize}
|
|
\includegraphics[scale=0.5]{../pics/DSCN0938.JPG}
|
|
\captionof{figure}{Proto Rev 1}
|
|
\vspace{0.3in}%line break
|
|
Being aware of feature creep, I built the new PCBs, and after a few revisions came up with the following shield. \footnote {I also plan to use this for other purposes (anywhere a barometer, temperature, humidity or sound sensor with internet connection is necessary (in my case, connecting to something like thingspeak, or some other self-hosted data server). That is for another project.}
|
|
\includegraphics[scale=0.3]{../pics/3dview2.jpg}
|
|
\captionof{figure}{Proto Rev 1}
|
|
\vspace{0.3in}%line break
|
|
It remains similar to the original shield, but flipping the ENC28J60 upside down, so that it can be simply put into the 0.1" headers, and soldered, without worrying about desoldering the pins (desoldering the pins is difficult without a hot air gun).
|
|
\section{Revision Two PCB}
|
|
|
|
\end{document}
|