Feed on
Posts
Comments

Amid all the fun and exercise of snow shoveling following the heavy snowstorm Nemo, I was able to finish and check in a new firmware update for OpenSprinkler. This new firmware, numbered 1.8.3, is a relatively minor update. You don’t have to update if you don’t need the new features explained below. There are two main changes:

The first is adding back the Sequential option that was available in firmware 1.7 but disabled in 1.8 due to a bug that was tricky to fix. This option allows you to set the controller to run in either sequential mode (where station runs are serialized) or concurrent mode (where stations are allowed to run simultaneously). The support for this option is now added back (with the bug fixed), and the Program Preview Javascripts have also been updated so you can easily check and verify the controller schedules in concurrent running mode. For most people this is probably not that useful, because sprinklers are typically set to run sequentially to maintain water pressure (similar to how people in the same house usually take showers in turn!) But there are times when you may need to run stations in parallel, say, if you want to speed up the overall watering time, or if you want to run master stations in a non-conventional manner, or if you want to use OpenSprinkler to control not only sprinkler valves but also home lighting and other devices. These are all cases where station runs have to overlap with each other. If this feature is useful to you, go ahead and upgrade to 1.8.3.

The second change is a new Device ID option which assigns the last byte of the controller’s MAC address. This new option allows you to run multiple controllers on the same network by giving each controller a different MAC address. Note that OpenSprinkler uses a software MAC, and is programmed with exactly the same MAC on every unit. I know, this sounds lame, but it’s just because I haven’t spent any time to figure out how to flash a random MAC address. Since most users won’t have more than one controller on the same network, it is not a serious issue. With the Device ID, you can easily customize the MAC address, albeit only the last byte. So again, if you find this feature useful, go ahead and upgrade to 1.8.3.

There are a couple of other minor changes. For example, the network status icon has been removed, instead, the LCD now displays no status icon if the network is on, and a question mark if the network is lost. Also, the Run-Once Program data is not stored in EEPROM any more; instead, you have to type in the water duration each time you start the Run-Once program. I know, this sounds a bit inconvenient, but I had to do it to make space for the new features. If you want to upgrade to 1.8.3, please follow the Firmware Update Instructions.

A slight annoyance I found recently is that I couldn’t compile the OpenSprinkler source code any more on my upgraded OS — Linux Mint 14. It turns out that Mint 14, based on Ubuntu 12.10, installs avr-gcc 4.7.2 by default, which apparently broke some of the Ethernet library code. This is quite annoying. My temporary workaround is to install Linux Mint 13 (based on Ubuntu 12.04 and installs avr-gcc 4.5.3 by default) on a VirtualBox in the host system, and then I can compile the code again in the virtual OS. I haven’t found an easy way to downgrade avr-gcc 4.7.2 to 4.5.3, so I will just stick to this option for now. Apparently next time I should really transition to use Arduino 1.x, which comes with its own avr-gcc compiler so I don’t have to worry about the OS installed avr-gcc breaking old code.

OK, that’s all. Back to snow shoveling tomorrow!

Dan K. from California wrote an excellent blog post about how to set up a Raspberry Pi to work with OpenSprinkler. The link to the blog post can be found here:
http://xperimentia.com/2012/12/14/setting-up-a-raspberry-pi-to-work-with-opensprinkler/

and you can download his scripts from the OpenSprinkler GitHub repository (link given in his post). The scripts basically consist of two parts: 1) storing and serving Javascripts required by OpenSprinkler on a Pi server (recall that currently these Javascripts are served on the rayshobby.net server); 2) using Pi to log OpenSprinkler status (this part is based on Dave Gustavson’s PHP scripts). As Raspi is compact, low-cost, and low-power, it is becoming an increasingly popular embedded Linux platform. The combination of Pi with OpenSprinkler also makes it possible to develop sophisticated features in the future like weather-based irrigation control, or leaning-based control like the Nest thermostat. Perhaps it’s time for me to think about an OpenSprinkler Pi Edition 🙂

IMG_2372

The Making of the AASaver

A few weeks ago I received a new batch of the AASaver PCBs at home. I thought, now that I am fairly experienced, it would be interesting to document the process of how I assembled the circuit boards. As you will see below, my assembly setup is manual and is nowhere near the capability of making more than a hundred boards at a time (for that I would outsource the assembly to a professional company). Still, it’s reasonably efficient such that I can enjoy the process of making without losing my mind or temper :).

IMG_2264


Step 1. Stenciling

AASaver is designed with all surface mount components. So the first step is to apply solder paste by using a stencil. I used my recently purchased laser cutter to make a stencil out of a Kapton film sheet ordered from Amazon. There are plenty of online tutorials on how to use a laser cutter to make solder paste stencils, so I won’t repeat them here. If you don’t own a laser cutter, you can easily make a stencil using copper sheet with the standard toner transfer and etching method. The tutorial can be found in my previous blog post here. Before I had the laser cutter, I have always used home-made copper stencils, and they work just as good.

IMG_2265IMG_2300
(Left: stencil made from Kapton sheet; Right: stencil made from copper sheet with home PCB method).

Next, I used old PCBs to make a 3-sided frame that fits the PCB tightly. Then align the stencil with the PCB such that the holes and solder pads match together. I then taped the stencil to the frame for easy lifting up. This allows me to quickly insert and remove a PCB. Since the AASaver board uses fairly big components (0805 and SOT23-6), the alignment does not have to be extremely accurate. Now, before proceeding, you need some tools, including some gloves for hand protection and stencil wipes for cleaning (both are available from from Amazon),

IMG_2266IMG_2273

as well as solder paste (which I got from dealextreme.com) and a credit or membership card as applicator. Now, put a sizable amount of solder paste onto the applicator, and then start pressing it down onto the stencil. I usually do two passes: the first swipe leaves a thick layer of solder paste; then the immediate second pass scrapes the excessive paste off the stencil sheet. Use only medium pressure — you don’t need to press very hard. After stenciling, lift up the stencil and remove the PCB from the frame. Check the solder paste on each pad and make sure everything looks ok. If something is wrong, use stencil wipe to clean the solder paste off the PCB and start over.

IMG_2268IMG_2269

IMG_2270IMG_2272

The stenciling step doesn’t take much time. Once you are experienced, you can do it quite quickly: finishing 100 AASaver PCBs took me less than 20 minutes.


Step 2. Populating Components

The second step is populating components onto the PCB. This is the most time consuming step and you will probably want to take short breaks in between :). I used to do it with tweezers, which required a lot of patience. Recently I discovered a couple of tools that can help increase productivity quite a bit. The first tool is a vacuum pen. It comes with a portable vacuum pump, two plastic tubes, and a pen with several different needle sizes. This is available on eBay if you search ‘pick and place vacuum pen‘. Be careful that the unit only works with 220V (designed for Chinese market). So in order to use it with 110V, you need a step-up transformer, which I got from Amazon for about 7 bucks. Well, if you plug it directly into 110V power line, there shouldn’t be any damage, the pump probably just won’t start.

IMG_2274IMG_2275

The second tool I discovered is the SMT feeder. Again, this is available from eBay by searching ‘SMT feeder‘. These are similar to feeders found on automatic pick and place machines, except they are static and do not automatically advance the tapes. I made some labels to help me remember the components on each line.

IMG_2276IMG_2277

With these tools, placing components is much easier than using tweezers: I no longer have to dump components out of the tape, or flip components to face up, or spend a lot of time adjusting the orientation of the components. Such a time saver :).

So how do you use the vacuum pen? Notice that on the side of the pen there is a small hole. When you cover the hole with a finger, it creates vacuum suction pressure through the needle of the pen, which allows picking up components. Then when you remove your finger, the air flows through the hole, and releases the component from the needle. I typically use my index finger for this.

IMG_2279

To demonstrate: first, get the needle close to a component and cover the hole; then pick up the component (as long as your finger covers the hole, the component won’t fall off); finally, carefully approach the PCB, press down the component to where it should be placed, and release the finger. The placing step definitely requires some practice. You can use your other hand to help stabilize the movement and the ‘touch-down’.

IMG_2280IMG_2281

IMG_2282IMG_2283

The first few times I used the pen, I was shocked at how poorly the components were placed. I felt it’s a complete piece of junk. But then as I used it more, I realized that I do get more experienced with practising (feels kind of like playing a video game :). Anyways, now I can place components at pretty good speed and accuracy. Practice maker perfect. Note that sometimes you need to change the orientation of a component, and that can be done by simply rotating the PCB around with your other hand. Here is another example of picking and placing an SOT23-6 component, and lastly a picture of the fully-populated board:

IMG_2286IMG_2287

IMG_2288IMG_2284

These are 25 boards that have components placed and ready to be toasted:

IMG_2290


Step 3. Reflow Soldering

The next step is the fun step, which is the ‘cook’ the PCBs so that the components will be reflow soldered onto the boards. I used to do this step with a toaster oven and a digital thermometer to monitor the temperature. Because I was lazy, I didn’t implement any sort of feedback control. As a result, there were a couple of times that I ‘over-cooked’ the PCBs till they burned and smelled terribly. So I decided to buy a real reflow oven. The one I purchased is model T-962A from eBay (which used to sell at ~$400 but is now more expensive). Note that its sister model T-962 is cheaper but also has a much smaller soldering area.

IMG_2241IMG_2247

This reflow oven does the basic stuff: it lets you select a pre-programmed reflow temperature profile, or program a custom profile if you want; it follows the selected profile quite accurately, by using an internal infared heating element, a cooling fan, and microcontroller-based feedback control; it also has a glass slit window on the front to allow you to monitor what’s happening inside the drawer. The user manual even describes how to use it to solder double-sided PCBs, which I haven’t tried yet.

IMG_2242IMG_2245

The oven also has its drawbacks: the standard profile takes 7~8 minutes to finish one cycle of reflowing, which is not very fast but perhaps can be accelerated using a custom profile; also, the heating is not entirely uniform — the area close to the boundary is cooler than the center, causing PCBs placed nearby the boundary to be poorly soldered. But once I am aware of these limitations, I can cope with them.

One important thing to keep in mind is that you should place the reflow oven outdoors. Even with lead-free solder paste, the exhaust from the reflow process is unpleasant at least, and probably harmful to your health. So keep it out of your living area.

Once the reflow is done, I get back a tray of freshly baked ‘cookies’. Satisfied 🙂 Take a close look at the PCBs and see if everything looks ok. Especially check if there are any un-soldered paste. If so, put them back and bake again.

IMG_2291IMG_2293


Step 4. Testing

We are not done yet, so don’t bite. The last step is testing, to make sure the circuit board functions as expected. First, perform a quick visual examination. Occasionally components may drift off its position, probably due to insufficient solder paste. These are easy to fix with a hot air gun or even a standard soldering iron. To facilitate testing, I built a simple rig using an existing AASaver PCB and some pogo pins I got from eBay. Here is my setup:

IMG_2295IMG_2298

Because AASaver is a regulated voltage booster, the main things I need to test are whether its output voltages are within spec (5V and 3.3V), and whether it maintains the voltage levels (within 5-10% tolerance) under a given current load (320mA). So my test setup includes a multimeter, AA battery holder, and a power resistor to produce the required current load. If the board passes the test (i.e. outputs and maintains the designed voltage levels with load), it will be put into the ‘success’ bin; otherwise, it will be put into the ‘to-be-fixed’ bin for further checking. For a simple board like AASaver, the success rate (yield) is close to 100%.

IMG_2296IMG_2297

This is a picture of a fully-assembled AASaver in action. It takes two AA batteries, new or used, and can function as an LED flashlight as well as breadboard power supply with switch-selectable 5V and 3.3V output.

IMG_2299

That’s all. Feel free to leave your comments, questions, and suggestions. Thanks!


Recently I’ve received questions about how to check out a previous version of the OpenSprinkler repository. One reason to do so is to recover features that have been eliminated in the most recent firmware, such as the parallel / concurrent running mode. As in any version control tool, GitHub allows you to do this pretty easily. Here is how.

First, go to the OpenSprinkler Github page, at https://github.com/rayshobby/opensprinkler, and click on the ‘XX commits’ link on the right side, shown below:

github_version_demo1

This brings you to the commit history, which lists all previous versions of the repository. Next, from the commit message or date, figure out the entry that you need to check out. Say, I want to check out firmware 1.7, and I found the entry here:

github_version_demo2

After clicking on ‘Browse Code’, you will be directed to a new page, which looks just like the homepage but with a different version number. Now, simply click on the ‘.Zip’ icon on the upper left to download the whole repository as a zip file. That’s it. Simple, isn’t it?

github_version_demo3

As I’ve given you a heads up in the previous post, there is now an iOS app for OpenSprinkler called SprinklerAce, developed by Michael at FeedFriendly.com. I know many people have requested an OpenSprinkler mobile app. I haven’t been able to split time to work on it myself. I am happy that Michael went ahead and wrote the first version. Here I will give a brief overview of the app. For details please refer to the SprinklerAce website.

SprinklerAce is extended from its previous version called IC Sprinkler, which was dedicated to the IrrigationCaddy. IrrigationCaddy is another Internet-based sprinkler controller on the market. It has nice polished UI design, but on the other hand it’s closed-source, has no LCD display, no support for extension board, and a limited set of three programs. Well, what I am trying to say here is that OpenSprinkler is better, more flexible, and actually comes at a lower price tag :). Michael made a clever choice to extend the app to support both OpenSprinkler and IrrigationCaddy, so the same app can be used for both.

Once installed, you will see the SprinklerAce app on your iOS desktop. The app is pretty self-explanatory and simple to use. Below I am going to mix screenshots captured on my iPad and those from the app website. The homepage shows a list of the current controllers. You can add a new controller by providing a name, ip address, port number, and password. You don’t need to input UserName because OpenSprinkler does not require that. You can add many controllers: for example, you may have more than one controller units, or you may create one with internal ip and one with external ip so that you can use it both at home and remotely. Once you click on a specific controller, it will show the list of stations. If you have defined custom station names, they are also supported here.

The app is currently designed to only manually open and close stations with a specified amount of time. Basically it makes use of the OpenSprinkler’s manual operation mode to control sprinkler stations. Program mode is not supported yet, so you won’t be able to add/modify/delete programs in the app (you need to use a web browser to perform program changes). It is mainly used for manual control and troubleshooting purposes. Once a station is turned on, the homepage will show running status and display the remaining water time. Internally the app reads back the OpenSprinkler homepage once every 5 seconds and makes use of the returned data to update its status accordingly. This is somewhat similar to how Dave’s logging script works. For example, if the controller is running a normal program schedule, you will be able to see the station status and remaining time in the app.

That’s it. It’s pretty easy to figure out how to use it. The app doesn’t do a whole lot yet, but hopefully Michael will continue improving it, including adding support for program mode, changing options and stations names. Basically you can view an app as another way to format the webpages: a web browser makes use of Javascripts to format the pages, and currently OpenSprinkler requires these Javascripts to be stored externally due to its limited program memory space; an app can store formatting code natively so it doesn’t need to rely on a whole lot of Javascripts.

Anyways, if you are interested or cannot live without an app :), feel free to give it a try. The app is now available in Apple store and supports both iPhone and iPad.

DISCLAIMER: FeedFriendly.com is an independent company and is not associated with Rayshobby LLC by any means. If you encounter any problem using the app, or has comments/suggestions, please contact them directly.


« Newer Posts - Older Posts »