Sunday, September 20, 2015

Automatic Cat Feeder - Challenges

Below is an overview of the biggest challenges that I had when working on this project. FYI they're not listed in any kind of order.

Challenge #1 - The food dispensing system

My first challenge was what kind of mechanism to make to actually dispense out the food? My father-in-law helped me brainstorm about this and he came up with some pretty good ideas. The one I started pursuing was a system with a 4" diameter polystyrene coupling. I even had a couple of 'discs' laser-cut by Ponoko. They were both shaped like PacMan. One was going to be stationary and the other was going to be rotated by a servo or motor.

If you want to see a video demo of how this was a fail, check it out:
https://www.youtube.com/watch?v=Ic5kBQw_nG8

I did come up with the idea of having a small 'vibrating' motor inside of the cylinder, which is to 'agitate'/move the food so that it keeps dispensing instead of getting stuck. I believe this would have worked, but I was having too much trouble with mounting the motor properly centered, and what hardware to use to keep it mounted/stationary without being in the way of the food.

Shortly after I scrapped the idea, I came across this guy's homemade automatic cat feeder system. I loved it, so I based the dispensing system off of his. The actual dispenser is a commercial cereal dispenser. Oh, 1 more important requirement is that it had to be food safe.

Here it is mounted on my 'canvas':

Food dispenser mounted on the 'canvas'

(Note - I'm using the word 'canvas' to refer to the big piece of plywood)
(Note 2 - I use the word 'canvas' very loosely - I am in no way any kind of artist)




Challenge #2 - The food delivery system

This one was probably the 2nd most difficult (the first one was above) part of the project. If you saw the video in my Overview/Introduction post about this project, you may have noticed that I have 3 different food delivery systems in place. The first one was made of regular cardboard. I 'scored' the cardboard and bent/folded wings or rails. I had to play with different angles to make sure that the food doesn't 'bounce' out of the track. It seemed like no matter what I tried, food kept bouncing out. To prevent this, I made a cover much in the same way that I made the base part of the track. Here's what I started with:

Beginning of the first food delivery vehicle - before the cover

I have a generic 'L' bracket attached to the 'canvas' and one of the cardboard 'tracks' is resting on it, and I have a single machine screw with nuts to hold it securely on the bracket. The other track is attached directly to the 'canvas' with a couple of wood screws.

My 2nd method is utilizing a 'core' from a roll of vinyl that I brought home from work (I work at a sign shop so we are always tossing these cardboard tubes).

Vinyl core cardboard tube

As you can probably see, I attached this to my 'canvas' using a couple of carriage bolts (and accompanying hardware of course). On top of the tube is just a cut up plastic Listerine bottle, which just acts as a 'funnel'.

Side view to show a little more of the hardware

The last dispensing 'system' was done out of paper towel tubes, and the chopped-off/top part of a 2-liter soda bottle. The cut-up bottle also acts as a 'funnel' to catch all the food from the dispenser.

Paper towel tubes duct-taped together

I was a little weary about using these cardboard tubes as they're so small and thin, but it actually ended up working quite well. I probably didn't have to use any hardware to 'mount' it to my 'canvas' but I did anyway just to be safe. You see, it fit so tightly behind the 1st chute (the cardboard track), that it doesn't really move. However, I did use a couple of screws anyway:

Can you see the screw through the top hole? (It's too dark to see the bottom one, but there's one in there too)

The way I used screws was just cut a couple of holes out of the tube, drilled a small 'pilot' hole in the cardboard (and canvas of course), and screwed it in. Then I just put duct tape over the holes to cover it to make sure no food comes out:

Holes covered up with duct tape

The only other thing to show as far as the food delivery system is the bottom 'mouth' attachments:

End of the left and center tubes

You probably can't really tell, but for the one on the left, I took a piece of cardboard from a box of Mountain Dew Voltage, rolled it, cut it, duct taped it to the bottom of the vinyl core cardboard tube. For the one on the right in the picture (actually my center one), I just used more paper towel tube, cut a hole in it, duct taped it to the bottom of the chute.

I'm actually not finding any good pictures for the bottom 'mouth' part of the chute on the far right. I just made it out of the same standard cardboard, which I scored, folded, and duct taped.

One of the biggest challenges for all of these was getting it the right angle and the right length. I wanted to make sure that food won't get stuck in there, but didn't want the food to come flying out so fast that it wouldn't stay in the bowl. Additionally, I didn't want it to go too far over the bowl and get in the way of the kitties' heads. So it took some adjusting and testing, gut I finally got it working pretty well.




Challenge #3 - Stationary Bowls

Our cats tend to move their bowls all over the place...sometimes all the way off of the little platform. So my first idea of making the bowls stationary was to 'bolt' them down with a few holes in the bowls, a piece of plywood and some basic hardware:

1st method of keeping bowls stationary


A closeup:

Simple hardware - bracket, screws, washers, wingnuts

I used wingnuts because this is obviously a lot easier to unscrew by hand (as opposed to regular nuts). If nothing else, I knew this would be fairly easy to release the bowls so that we can wash them. Oh, and in case you're wondering why I am using a flathead screw (wrong kind of screw in this application), it's because I didn't have 'panhead' of the right size/length on hand.

Anyway, this seemed to work for a bit, but the screws got loose pretty quick (kind of like my head). I had to come up with something else. I'm not sure where I got the idea, but I thought if they had round (and tapered) bowls, I could make another little platform that would allow them to just 'drop in', so I headed to our local pet store, Petsmart. Found some nice round stainless bowls, so I got to measuring, measuring, then cutting. (Remember - always measure twice, cut once!)

This is what I came up with:

New platform


Side view with it propped up a bit:

Just showing how the bowl sticks down below the main piece of plywood,
but barely just under the entire 'height' of the plaform
I'm much happier with this - better bowls, stays stationary with no hardware, and very, very easily removable (and put-back-able)




Challenge #4 - Button issues

Below are the original buttons that I had put in place. I chose them because they're cheap, and easy to mount:

Original buttons

Well, I had major problems trying to get them to do 'double-click'. You see, I was wanting to have the buttons perform multiple actions - single-click to give the cats a 'snack', double-click to give the cats a bigger snack, and a 'hold' to continuously dispense food until letting go of the button.

I actually had already mounted the buttons before I got to that specific portion of the code. I tried other kinds of buttons and the double-click would work just fine in the code. The Arduino forum came to the rescue again. Someone suggested try using a different 'button handler' (my words, not theirs) - the 'OneButton' library. Well I did some tests with this library and the buttons worked a lot better. However, I had already implemented the 'other' button-handling code, and would have been a huge pain to re-implement the new code. (Remember, I'm a beginner at all of this)

Instead, I bought a couple new buttons and tested them out - they worked a lot better, so I decided to replace the really cheap buttons with not-as-cheap (but still pretty cheap) buttons since they work a lot better:

New/better/current buttons




Challenge #5 - Transferring the DS1307 chip

This was a bit of a strange one. It is purely an electronics problem. The problem is that, during development, I had connected everything up on a breadboard, so it looked something like this:

Circuit on a 'breadboard' (not the circuit for this project...just an example)


The main white rectangular with all the holes is called a breadboard. It allows you to build/prototype circuits, and is a common practice to use them while developing. During the creation of this project, I used a breadboard to build the different parts of the circuit (then finally combining them all).

Ok, so nothing unusual so far, everything worked great on the breadboard. The next step (for me) (I did not want to design an actual circuit board as I was not going to make multiple boards, or sell them.) is to 'move' (or recreate) the circuit on 'protoboard' (a more permanent substrate). An example of protoboard:

One kind of protoboard


Again, no problem, I've done this several times before. But wait a minute...the small chip (the DS1307 - the one that keeps the time) is going to lose power when I move it from the 'breaboard' and onto the 'final' circuit on the protoboard. Uh oh...we have a problem!

How do I move the chip from the breadboard to my actual board:

The eagerly awaiting chip holder on the actual board


Above you can see my mostly complete protoboard without the time-keeping DS1307 chip. Searching on Google gave me nothing. It's probably the search terms I was using. I did have a couple of ideas though. The first one was to build more onto my circuit - the parts that I would need to actually program the microcontroller directly on this board. You see, the way you 'program' the DS1307 chip is through another microcontroller...in my case, the Arduino. However, this seems like a waste of time and materials as I'll probably only ever do this 1 time (with this circuit). My 2nd thought was very 'hacky' but would be quick and fairly easy. The idea was to solder 2 wires directly to the chip (sitting on/in the breadboard), hook up a battery (temporarily) to the other end, remove the chip (with the wires and battery in-tow), insert the chip into the 'chip holder' (on the protoboard), desolder the wires, be done.

There was at least 1 possible problem with this approach, so I had to do a test. I was worried that if I had 2 coin cell batteries hooked up at the same time, the voltage would double and fry the chip. However, I was pretty sure that doing that would be fine because they would be hooked up in parallel (as opposed to series), which means that voltage would stay the same, but the run-time would double, which is fine. I did my little test with a couple batteries and my multi-meter, and confirmed my thoughts - it should be safe for the little guy to be transplanted!

Immediately after moving the chip from the breadboard to the proto board:

The chip still has the 2 wires soldered to it after moving the chip to the final board


A closeup:

The 2 wires still soldered to the 2 pins on the little chip


The completed transplant, wires removed:

The 2 wires have been desoldered


As you can see from the above 3 images, I followed the steps I outlined. Then I confirmed that the chip kept the time during this silly process - so we have a successful transplant! Now you can call me Dr. Nerd!

There you have it folks...my biggest challenges with this project and how I was able to overcome them. Hopefully this may help someone out there doing something similar.

Next up (and probably lastly for this project) we'll talk about the electronics.

Automatic Cat Feeder - Introduction/Overview



Completed Automatic Cat/Dog Feeder



Above, you will see my latest project - the Automatic Cat Feeder. It is Arduino-based, and built with various off-the-shelf hardware, and some parts that I modified.

How does it work? The Arduino is programmed to dispense food @ 5:15AM and 5:15PM for our cats' daily meals. The Arduino basically turns on the motors (1 at a time) to turn the food-dispensing paddle for a pre-determined amount of time to dispense the right amount of food. The food drops out of the dispenser and down the various chutes you see, and into the 3 bowls.

Before I go any further, I must give credit where it is due. First, I borrowed heavily from this guy for the actual dispensing system. Second, I had a couple of issues on the electronics side of things, but the great Arduino community over on the Arduino forums offered great advice to help get past the hurdles. Lastly, driving the motors was made very simple thanks to Sparkfun's motor driver board

Why I created it
Our cats like to be fed at consistent times of the day, and that's not always easy to do. For various reasons, we can't always feed them at the exact same times daily. Sometimes they may be fed hours later for dinner, and we feel really bad about this.

Now why didn't we just buy an off-the-shelf product? We looked into this and found that they were just too expensive, not very flexible, or were easily defeat-able, allowing the cats to gorge on the food whenever they please. I don't like the idea of an inflexible system that I have little to no control of (yes, I may be a bit of a control-freak). If I build my own, then I have complete control of it, so I can change it, add features, etc. myself.

Requirements
Before starting this project I had a few requirements in mind:

  • Must be food safe!
  • Must be reliable
  • Must cost less than comparable commercial feeders
  • Must be customizable
  • Must have some kind of audio notification to inform the cats that it's breakfast/dinner time

Is that asking too much? Nah

Ok, ok, I know you want to see a video of it in action, so here you go:




I had in my mind that I would build this with network connectivity to give us the ability to monitor/feed them remotely, but for a couple of reasons I didn't. First, this project already took me a long time to get everything worked out, and just wanted to get it installed for them. Second, an Ethernet Shield or Wi-Fi shield are fairly expensive ($35-$45), especially compared to the new ESP8266 (around $4) that's come out recently. I say recently because I actually started this project a couple of years ago. So why didn't I incorporate the ESP8266? I don't know how to use it just yet.

Ok, I'm sure some of you want to know just how much everything costed me. Price breakdowns are in the Bill of Materials (linked above), but the cost of everything was $190. Yes, that's expensive, and a lot more than I was anticipating. The 2 most expensive items were the motors (about $25/ea) and the cereal dispensers (also about $25/ea). That's $100!. Originally, I was going to come up with my own food dispensing system, which would have saved me over $50. Additionally, I feel that if I would have shopped around and done more research I could've cut the cost of the motors in half. As I'll talk about a bit in future posts, I got impatient and decided to just go the route I did.

Also remember that I'm feeding 3 cats with 2 different kinds of food...your situation may not be as complicated.

In conclusion, I wanted to let you know that there will be more info coming. In the next couple/few posts, I will go over some of the challenges I had with this project, hopefully saving you time in the future. I will also talk about the individual components in more detail (yes there will be videos). I'm not going to do a full tutorial like I did for my Garage Door Controller, but there will be some pretty good detail, hopefully enough for you to replicate if you want to.

Below are some links for you to use if you want to replicate this system, or parts of it.

Arduino code on GitHub
Fritzing file (actual .fzz)
Fritzing file, exported to .png image
Fritzing file, exported to .pdf file
Bill of Materials (Excel)
Bill of Materials (Open Office)

I haven't created a 'digital' schematic yet, but if/when I do, I'll update this post with the link to it.


Well, I hope you've found this post/project useful and/or interesting. Feel free to leave a comment if you have any questions/ideas/suggestions.


Want to know what the challenges I encountered, and how I overcame them? Well, that's exactly what my next article is about



Sunday, May 3, 2015

Source of electronics woes in my garage discovered

It's been around 4 years that I've been having strange problems with 'homemade' electronics devices in my garage.

It started off when I built a (semi) 'automatic cat door'. My little device allowed our cats to push one button (mounted to the outside of the door) when they want to come in, and another button (mounted on the inside of the door) when they want to go outside.

After I built a working prototype that worked flawlessly 100% of the time in my testing, I moved the circuit to a prefboard, installed everything on the door, and thought I had the project completed - http://www.youtube.com/watch?v=tNIsKxZJ9G8 (this is a video on my completed project). However, it didn't take long to notice that it was behaving strangely - it would not respond to button presses sometimes, the servo wanted to keep moving even though it hit a limit switch, the servo would go the wrong way, etc. I would have to power cycle it to get it to work properly again. I was never able to figure out what was wrong with it, but the light shone very recently and now I am confident that I know what the problem was...(don't worry, I'll reveal the problem/solution at the end of this post)

A little later in time I purchased this really cool Internet-connected sprinkler system:
http://rayshobby.net/opensprinkler/
But I had a very similar problem with it not behaving properly...see one of my threads about it:
https://groups.google.com/forum/#!topic/rayshobby/eeiMdxePBUs
Again, myself or the creator of that device was not able to figure out the problem. So I would have to constantly check on the status and make sure that it was working...when it stopped working I had to power cycle it.

Lastly, I developed an automatic Garage Door Controller. It took months and months of development, and I tested it a lot in my 'lab' (read: my very little bedroom in my house), and it worked wonderfully for months before I took it into the garage to test/install. When I did finally install it in my garage, it was so exciting, and it worked great for a couple weeks. Then I started having strange problems where it wouldn't respond to my commands, wouldn't let me connect to it, etc. I would have to power cycle it once or twice a week to get it back working. I took it back into my lab and tested and it would work for weeks with no problem. I couldn't figure out what was different in my garage and my lab. I spent months trying to figure out what it could be, posting on forums, etc. Recently, however, I figured out!

The suspense is killing you, right? Drum roll please:





Ok, so I don't know which one of the above 2 Insteon devices is the culprit. I had them connected together in my garage, and for the test, I pulled both of them out, and haven't tested 1 at a time yet. However, ever since I pulled them, I haven't had any problems with the sprinkler system or the garage door controller (and if I was a betting type of guy I would bet that if I reinstalled the automatic cat door, that would be working great too). It's been about 3 months now, and things are still looking great.

I plan on trying to isolate which device of the 2 is the culprit, then I will try to get in contact with Smarthome/Insteon and see if they know anything or have any useful information about it. I will report back here if there's anything useful I can share.


Saturday, April 26, 2014

Bad vibrations


Original vibration motor next to my Galaxy S3

Well, my vibrator stopped working. I dropped my Galaxy S3 the other day, and ever since, the vibration stopped working properly. And it would make weird noises. Sometimes it wouldn't even vibrate. If I shook my phone I could hear actual rattling in there.

So, like any hacker/cheapskate, I looked around online and found a $4 (free shipping) replacement on eBay. A few days later, it arrived in my mailbox.

Let me go backwards in time a little bit: I've never actually repaired a cell phone before. Because of this, I looked for some videos to see what I was getting myself into. To my surprise I wasn't overly intimidated, so I went forward.

It was a success! I actually shot the whole thing on video, but it's not edited at the moment. I will post it here when/if I ever get around to editing it for everyone (it definitely needs it).

To close this post, here's a closeup of the original motor:

Original vibrator motor


Sunday, January 12, 2014

Garage Door Controller Tutorial - Solder on your homemade circuit board

My home made circuit board

This post is an alternate to Garage Door Controller Tutorial - Step 2 - Soldering. The aforementioned post assumes that you bought the professionally made PCB from my store (or downloaded the files on my GitHub and sent them to your own board hours to be fabricated).

However, I'm all about saving money, so wanted to provide you with a way to save yourself a little money (about $9 if you buy from my store, or more $ if you get your own board house to make them for you). So if you made your own circuit board, or want to learn more about doing so, read on...

Tuesday, December 31, 2013

Garage Door Controller Tutorial - Using the app away from home

As I mentioned in different places throughout my tutorial, you can use your smartphone to check the status of, and open/close your garage door from anywhere in the world. However, as I mentioned in the last post (Step 9) of this tutorial, we set it up so that you can only access your Garage Door Controller from within your own network. This is because it is the easiest way to get you up and running. If you want to expand upon that and be able to access your garage door controller from anywhere, then we need to do a little more work...

Note - You should read this article in its entirety before drawing any conclusions about the path(s) you want/need to take to overcome any problems that you may have.

Please take a moment to look at the following diagram:

No, I do not claim to be an artist

Do you see that vertical red bar that is going through the center of the router? I'm trying to show that the LAN and WAN sides of the router are blocked off from each other. This is actually not entirely true because the router does allow computers from the LAN to access the Internet (WAN), but devices and computers from the Internet (WAN) cannot access the devices and computers inside the LAN. This is by design.

Monday, December 30, 2013

Garage Door Controller Tutorial - Step 9 - Smartphone app


Here we are - this is the last step, and it should be another easy one. You just need to download and install my free Android app now. (The icon for the app looks like the above image)

There are a few ways of doing this:
  1. You can just search for 'Garage door controller' in the Google Play (Google's app store) app. Download/install the app that has the above icon (there may be other garage door controller apps out there)
  2. Go straight to it from your Android smartphone using this Google Play link
  3. Scan the below QR code from your smartphone:


Once you have the app installed, then we just need to configure it, which should only take a few minutes. Go into the 'Settings' screen, by pressing the 'Menu' button on your Android smartphone. You'll see a screen that looks like:


Remember Step 3 - The microcontroller? Back in that step, we entered a few items into the Arduino sketch, then uploaded it to the Arduino. Well now we're going to need a few of those items. Namely, we need:
  1. IP address
  2. Server/port
  3. Password
Now here in the Android app, go through each option and enter the appropriate values (Note - there will probably be 'default' values in each option, so don't worry - just overwrite them). So for 'default IP/domain (url)', enter the IP address that you wrote down in Step 3. Then do the same for 'Default Port' (called 'server' back in Step 3), and then 'Password'.

The last option ('Milliseconds to pause') is a little different. Do you ever 'crack open' your garage door? What I mean is just open it a little bit (just a 'crack') - i.e. when your garage door is closed, you push the garage door opener button, then press it again a second or two right after, which partially opens it. Well that's what this option is for. You specify how many milliseconds between 'button presses'. So the larger the number (fyi: 1000 milliseconds = 1 second), the more the garage door will be 'cracked open'. So if you want a 2.5 second delay, you would enter 2500 milliseconds.

Now we can go back to the main screen, and it should have your information in there now:

Note - your information may be different - the above is just an example

Your IP address will almost surely be different than what you see above. The port will probably be the same though. Notice how it says 'Not Connected/Unknown' in red at the top. And it shows 'Disconnected' for the 'Connection status' below the 'Connect' button. This is because we have to connect to the garage door controller device before we can do anything, so go ahead and click on the 'Connect' button. After you do, you should get a screen that looks like this:

If your screen looks like this, then your garage door is closed

or maybe this:

If your screen looks like this, then your garage door is open

I think the app is pretty straightforward, but just to be thorough, I'll mention a couple of things.

  1. The 'Check here to 'crack' garage door' checkbox is grayed out (not clickable) when the garage door is open. When it's closed, you can check that box and click 'Open Garage Door' and it will 'crack open' your garage door for you.
  2. You need to click the 'Connect' button before you can do anything.
  3. If you did not perform Step 6 - Opened / closed sensor, the status will always show 'open'.
  4. You should click the disconnect button before exiting the app.


I would like to mention that if configuring the app to use the actual IP address of the garage door controller like we did here, you won't be able to connect to it from outside of your network (You won't be able to check the status of, or open/close the garage door outside the physical vicinity of your network). At least, not without some extra work. Please see my post titled 'Garage Door Controller Tutorial - 'Using the app away from home'.

Enjoy!

Return to previous - Step 8 - mount and connect.

Garage Door Controller Tutorial - Step 8 - Mount and connect

We have just a few more things to take care of:
  1. We need to mount your device
  2. Connect it to your actual garage door opener
  3. Connect to the reed (magnet) switch (optional)
  4. Connect your Ethernet
  5. Connect power
Sounds like a lot, but you've already done all the hard work of running wires and cables, so now it's just a matter of hooking everything up. Let's get started!

1. Mount device
I actually have a small area near my garage door opener that allowed me to mount mine on a vertical surface instead of on the ceiling (which should be no problem if you need to do this). Here it is mounted on the small surface:


See the screws at the 4 corners? I just pre-drilled some holes in the wood, then used standard drywall screws to attach it to the drywall, just above my garage door opener.


2. Connect your device to your actual garage door opener
Now we have to connect a couple wires to your actual garage door opener. You know that push button in your garage that you use to open/close your garage door?:


My button looks like the above, but yours will probably look different. The way that your garage door controller works is by simulating a button-push from this button. So what you need to do is hook up 2 wires that are going to connect your garage door opener to your garage door controller device. How do you know which terminals (you probably have 3 of them) on your garage door opener you connect to? An easy way is to just follow the wires from your existing switch to your opener. The back of my opener looks like the following:

Back of my garage door opener
You can see that the existing wire for the existing switch connects to the 2 terminals on the left. So I connected a red wire to the middle terminal, and a black wire to the left-hand terminal. The colors don't actually matter, so don't worry about using different colors or marking them or anything.

Connect the other end of  the wires to the top-left hand terminal block on your garage door controller:


Again, don't worry about which wire is which - it doesn't matter.


3. Connect to the reed (magnet) switch (optional)
If you ran 2 wires for your opened/closed sensor in Step 6, let's connect those now. We're going to connect those 2 wires to the terminal block just below the one we just used:




4. Connect your Ethernet
Let's connect our Ethernet cable to the jack that is on the far bottom right hand of the device:




5. Connect power
Your garage door opener is probably physically near an electrical outlet, so this step should be easy too. Plug in the AC Adapter into the outlet, and into your device, and your done with the hardware!

See the power cable plugged into the power jack at the bottom left of your device? Well plug it in!
I highly recommend that you use a surge protector instead of plugging directly into the outlet.

The power LED should come on and you'll start to see some lights flashing on the Ethernet Shield. Pat yourself on the back and rejoice - you are done! (With the hardware aspect anyway)

Well, hardware is no good without software, right? Right. That brings us to the last step - Step 9 - Smartphone app. (Don't worry, this is easy)

Return to previous - Step 7 - your network.

Garage Door Controller Tutorial - Step 7 - Your network

Your device is pretty much useless without being on your network. You have at least 3 options to get it on the network. The idea is that you need to connect a networking/patch cable from your device to your network.

Option 1 - If your garage door controller is going to be close enough to your router/switch, you can just use a pre-fabbed Cat5/Cat5e/Cat6 patch cable from the router/switch to your garage door controller.

I don't think this one really needs much explanation. Just tack up your patch cable from the garage door controller to your router/switch, plug it into your router/switch, and call it a day.



Option 2 - Very similar to option 1, except that this way is theoretically cheaper, but requires a little more work.

If you need to run the network cable a longer distance than a patch cable that you can get a hold of, or if you already have some, you can run un-terminated Cat5/Cat5e/Cat6 network cable (cheaper than pre-fabbed patch cables). Then put the end connectors (RJ45s) on the ends yourself.

This is the route I took for my own house...here's a couple photos:

White Ethernet cable tacked to the ceiling of my garage

The other end connected to my network:

Yes, it's a little messy


It's actually not difficult to put the end connectors (RJ45s) on yourself. This Instructable is pretty good and easy to follow. Or, if you prefer a video, this is a pretty good brief tutorial.



Option 3 - If running cable is going to be too difficult/inconvenient, and you have a wireless network already, you can use something like a TP-Link TL-WR702N Wirelss N150 Travel router. You configure it for your network as a 'client' instead of a 'router', then plug a short, inexpensive patch cable from it to your garage door controller, and you're all set.

Just to elaborate on this option a little bit:
If you do want to use a wireless device such as the above, there is a little configuring you need to do. You'll need some information about your wireless network, such as: SSID, MAC address of your existing router/access point, WEP Key Index (if using WEP), and the key/passphrase/password.

As far as how everything fits together physically, here's a photo of a finished installation that I did for one of my sisters:


The TP-LINK device is the blue square device near the top-right of the image above. It has an Ethernet patch cable coming out the bottom (it's the dark gray cable coming out the bottom-left of the device) connecting to the garage door controller. The lighter colored cable coming out the bottom to the right of that is the power cable. So adding this extra little device is actually pretty simple and straight-forward.

Now that that's done, let's go to Step 8 - Mount and connect.

Return to previous - Step 6 - opened/closed sensor (optional).

Garage Door Controller Tutorial - Step 6 - Opened / Closed sensor (optional)

This step is optional, but I highly recommend it. It allows you to know if your garage door is opened or closed. This in itself may be a highly valuable feature - do you ever get the feeling that you forgot to close the garage door when you left your house? Yeah, well, then you want to do this step.

First you need to decide where you're going to install your device, and where you're going to install your reed switch (this will probably be a stationary part of your garage door track or something that will be physically close to your actual garage door). Once you decide this, run your 2 wires from one area to the next, leaving some extra slack (I like to give myself an extra foot or 2). You should 'tack' them to the walls (using the appropriate staples, or wire-ties and screws, or whatever else you like to use), or whatever other surface they're against, so that they stay in place, and are clean-looking.

After the wires are ran, you'll need some way of physically attaching the reed switch and magnet. Here's what I used:

Bracket for the magnet on the left, reed switch in the center, bracket for reed switch on the right