Step 10: Assembling the Project

Step 11: Using the Camera and FAQ

Operation To transfer pictures from the camera you must install the driver and MyPicture application that came with it on to your computer. You do ...

I have always wanted an inexpensive way to take unobserved pictures of wildlife in my neighborhood. This instructable takes parts of two existing instructables and brings them together with added features to create a cheap motion detection wildlife camera.

This project uses a re-purposed PIR sensor module from an air freshener to provide motion detection, an inexpensive key chain camera to capture images, and a TI msp430 microprocessor to provide the necessary brains. The microprocessor comes with TI's $4.30 Launchpad experimenter kit.

We Gill Instruments Pvt. Ltd. have a requirement for an engineer with a strong expertise and hands on experience in the field of MSP430. Candidates who are willing to relocate in Bangalore can send us their CV on - ankur@gill-instruments.com.

What a great project. I am really enjoying connecting the dots and want to make sure of a few things before I flip the switch and fry the whole thing. At top left of your schematic VCC goes to ground through two capacitors. One of them is marked (Tw) -- what does Tw mean? I wonder why there are two capacitors there? Thanks!

Doug, Thanks for your reply, error message number 2 persisted till then, but now OK. I have another problem now, of my own making - I have ripped off the right-side bit of copper trace from the camera circuit board, the one to which the shutter switch was attached. Is there an alternate spot in the circuitry at which I could solder the emitter pin of the transistor to get the unit to function? Or is it now hopeless?! Many thanks for a reply.

Thanks for posting this project Doug! I am trying it out but have been having some difficulty with uploading the code onto the chip, which in my case in an MSP430G2553. The compilers (I’ve tried with both the IAR and CCSv5 compilers) throw up three “error” messages and I am unable to fix these and proceed further for lack of programming knowledge. The details are as follows: Error 1. For the line marked in bold below, the message says "../main.c", line 148: error #29: expected an expression Error 2. Also for the same line, and the message says "../main.c", line 148: error #20: identifier "j" is undefined (I managed to ‘lose’ the second error message by inserting a line that said “unsigned int j = 1”/0 near the beginning of your code, but without really knowing what I was doing.)

Letria, It looks like that you found the solutions to your problems. The reasons for the differences in code when moving from the MSP430G2211 to the nicer MSP430G2553 microprocessor is that the MSP430G2553 has two timers instead of the single timer in the 2211.

The include line (#include msp430.h) at the beginning of the code, calls a file based on the microprocessor used. This file defines all of the interrupt vectors for the specific microprocessor.

The file for the 2211 (with a single timer) uses TIMERA0_VECTOR to define the timer. The file for the 2553 (two timers) uses TIMER0_A0_VECTOR and TIMER1_A0_VECTOR.

Note: There are other timer related interrupt vectors, but that would only add confusion to this situation.

Luckly, the pin functionality used by this project is the same between the two processors.

The other error involving the for loop (for (int j = 1; j <= 8; j++)), I have seen before. Some compilers will accept declaring the loop variable in the for statement and some compilers will not. The version of IAR workbench that I originally used did accept this form. Apparently Code Composer 5 doesn't. You mentioned getting the error using IAR, I can only guess that they changed to be compatible with CC5.

The solution is as you discovered, is to declare j before the for loop:

From: for (int j = 1; j <= 8; j++)

To int j; for (j=1; j<=8; j++)

It is interesting that CC5 recommends that the loop count down instead of up. In that case, you could use;

If your DSLR has a method of processing an external electronic shutter trip, you could modify the project to provide that signal based on activation of the PIR module. You would to need to know the specifications of the specific camera.

So after looking all over for the I motion, I decided to order it online and accidentally bought the scented oil one that plugs in. What would i need to do differently to make this work? I have almost no knowledge of programming or small electronics.

The scented oil product was designed to work on 120VAC. The circuit is extremely different from the air freshener used originally in this project.

Your best options are either use the original product (~$8), or use an inexpensive Chinese PIR module from eBay (search eBay with: "PIR module", ~$2 with free shipping), or use a Parallex PIR sensor module from Radio Shack (Cat# 276-135, ~$11). PIR sensor prices have dropped since this project was published, and the modules are easy to use.

All of these sensor options use 3 connections to hookup: Vcc, Gnd, and Sensor Output (marked PIR on circuit diagram).

If you use the original camera, the microprocessor program should work for all of the above options without modification.

If you have none of the parts, the cost would be about $25 to $40. The major expenses were the air freshener unit (~$8), the project box (~$7), the camera (~$10), the MSP430 kit ($4.30), prototype board and electronics (~$5-10).

My costs were very low because I was reusing parts from other projects, had the project box already, and bought the camera on sale ($5).

If you can't find the air freshener unit, Chinese built PIR sensor modules are now selling on eBay for $2. They can be substituted without much hassle. Also, keep your eye out for older digital cameras that can often be picked up at garage sales or thrift shops for a few dollars. These older cameras offer higher resolution and better images storage. You do have to figure out how to interface them, but that is often fairly simple and fun.

The Vivatar camera used in this project was very easy to re-purpose. I later played around with an Aries key chain camera for another project. The Aries camera was similar in functions and look, but the internals had been engineered to lower cost. It was much harder to interface the power and shutter.

Using an alternate project enclosure is another area that could be used to cut costs.

Could you use an ATtiny45/85 with arduino software to do this instead of the TI launchpad controller? I see it is only using 4 pins (not including vcc and ground), and the ATtiny45/85 controllers have 5 analog/IO pins, so i think it could work. They are like $1.60 on digikey and i mainly use arduino, so these are better for me. I have been wanting to do a cheap security camera setup for some time but was looking for a cheap and compact option and this looks like it is perfect. Just got to get the camera and freshener.

There should be no issue using an ATtiny45/85 as the microcontroller for this project. Of course, you would need to make approprate changes to the code and wiring.

I used the MSP430G2211 because it came as part of the TI Launchpad board. They send you the board which has a built in programmer and two MSP430 micros for $4.30. Since this Instructible was written, TI has upgraded the two microprocessors included with the Launchpad to one each of the MSP430G2553 and MSP430G2452. If this class of micros meets your needs, it is a heck of a deal.

With an AA battery you could expect the camera to be active for about 2 weeks of continous use. Using a D cell battery would give you about 135 days. It is important that you never lose power, since the camera uses SRAM to store the images. In other words, if you lose power before downloading the images to your computer, you lose the images.

Your idea of solar powered yard lights is interesting. These lights actually work by recharging a single rechargeable battery and using a joule thief type circuit to boost the voltage high enough to light the LEDs that provide the light. The internal battery used in these lights are generally pretty crappy and have very low mah ratings (usually less than 600 mah).

The Vivitar camera used in the project has a boost power regulator, so the joule thief part of the circuit of the yard light should not be used.

A issue with rechargeable NiMH batteries is that internal resistances cause them to discharge if not used. Older technology batteries would discharge in a matter of days if not recharged. Newer technology batteries are much better. This means that you could possibly replace the original yard lamp batteries, strip out the joule circuit, and only use the solar cell part. I would use a high mah new technology NiMH battery in the camera with the solar cell portions of the yard lights connect via an external plug. I would also use multiple modified yard lights in parallel (most likely at least 4) to provide a higher current for recharging. You do not need a blocking diode, if setup this way.

Neetz, The best picture I have is the one I added to step 6. The most likely way to mess up this board is if you have the wrong perspective of the IC socket. Remember the IC socket is on the opposite side of the board from the copper wiring. The pins are labeled as if you were looking through the copper side of the board. You can't see the IC socket when you are looking at the copper side of the board.

Here are some checks that you can make with an ohm meter. Refer to the primary image on step 6.

1. Place circuit board on a table with the microcontroller facing up. 2. Remove the microcontroller and put it aside. 3. Set your meter to 100k ohm scale. 4. Place the positive (red) lead in the IC socket at pin 1. 5. Place the negative (black) lead in the IC socket pin 2. The reading should be max scale. 6. Repeat by moving the black lead to pins 3, 4, 6, 7, 8, 9, 11 ,12 ,13 ,14. All of these piins should also read max scale with the red lead in pin 1. 7. With the red lead still on pin 1, place the black lead on pin 5. The reading should be about 47K ohms. 8. Repeat by moving the black lead to pin 10. It should also read 47K ohms. 9. Place the red lead on pin 5 and the black lead on the wire marked PIR in the picture. The meter should show a short or about 0 ohms. 10. Place the red lead on pin 6 and the black lead on the wire marked Shutter in the picture. The meter should show a short or about 0 ohms. 11. Place the red lead on pin 7 and the black lead on the wire marked Mode in the picture. The meter should show a short or about 0 ohms. 12. Place the red lead on the pin 14, now touch the black lead to each lead of each capacitor, one side of the capacitor at a time. Each capacitor should have a zero ohm side and a max scale side.

When working with perfboard, I usually make runs on the copper side of the perfboard with non-insulated wire. I then make jumpers on the non-copper side with insulated wire.

When soldering the non-insulated wire, I solder at the corners of a straight run and where component leads or jumpers touch the run. It helps to use a pair of pliers or a soldering heat sink clip between a previous soldered joint and the one I'm working to prevent the first solder joint from coming undone.

On this particular project, I was experimenting with copper foil glazing tape that is used by stained glass hobbyists. You can get a lifetime supply for about $6 at hobby shops. I cut the tape I had lengthwise in half to make the runs. I use this tape for various odd connections in some of my projects. It can come in handy.

The tape worked and I think it looked neater. I have now moved on to making my own PC boards using the toner transfer method.

I'm planning on using the Radio Shack PIR module, which goes high on motion detection. If I read your code correctly, the PIR module you use goes low on motion detection. C isn't my native language. How do you modify that piece of code to change the polarity of the interrupt edge select?

boiyas, Port 1 interrupts on the MSP430G microprocessors are set only on transitions, not static levels. P1IES is the Port 1 interrupt edge select register. So I believe the only 2 portions of the code that would need to be changed is:

Portion #2From: // if band time is reached and p1.3 still 0 else if ((band_flg == 1) & ((P1IN & BIT3) == 0))To: // if band time is reached and p1.3 still 1else if ((band_flg == 1) & ((P1IN & BIT3) == 1)

I haven't actually tried these changes, but I feel confident that is all it will take.

For some reason, I couldn't get the code to work with low to high transitions. I was using the LaunchPad and a breadboard to simulate the camera.

But for future reference, the Radio Shack PIR module produces enough pulses that it works with your original code despite outputting a low-high detection transition.

The one thing I had to do to make it work was add an NPN transistor between the PIR and pin 5 of the microprocessor as a switch. Base to PIR output, emitter to ground and collector (pulled up to Vcc with the 47 k resistor) to pin 5. That's because the output level was about 70% of Vcc, which doesn't seem to be enough to trigger the microprocessor. With the switch added, the system seems to be working fine.

bioyas, The Radio Shack PIR module is made by Parallax. Parallax has updated the sensor to a Revision "B" which extends the Vcc range to 3.3 - 5 V among other improvements.

I am curioius, Is your sensor a Revision "A" or "B"? There should be small text on the side with the lens that says "REV A" or "REV B".

The use of a NPN inverter between the module and the MSP430 would invert the logic of the module so that the MSP430 would see a "high to low" transistion on a PIR trip. So the original code should work without issue.

Did you try using either an external or the internal pull up resistor in the MSP430 on pin 5, instead of the transistor? The logic would then be "low to high".

I don't see any rev info on the lens or the pcb, although it's packaged now, so I don't have complete access. The slip of paper that came with it specifies a voltage range of 3.3-5 volts, so perhaps it's a rev B.

Any inversion from the transistor is irrelevant. The PIR module puts out a high level pulse when motion is detected, which returns after a period of several seconds, so for each detection, you get both a rising and falling edge. The falling edge is delayed by the length of the pulse, which for my purposes doesn't matter. So it should work no matter which polarity of pulse edge you set up the MSP430 for. I just couldn't get the low-high transition setup to work at all - not sure why.

The purpose of the transistor switch wasn't to invert the signal, but to bring the high level output of the PIR closer to Vcc. Even with the 47k pullup resistor (external only - I'm aware of the internal pullup option but didn't try it) it only went up to around 1.8 volts when directly connected, which wouldn't trigger the MSP430. The transistor brought the high level up to close to Vcc, and allowed the MSP430 to trigger properly.

So in any case, the code works with the Parallax PIR, provided the extra transistor switch is inserted between the PIR output and the MSP430 input. Further work might result in a simpler solution, but I'm out of time and it's working ...

Thanks! I think I got the Portion#1 but didn't pick up on the Portion#2 part. I'll work it and see what happens. I don't have the camera yet, so I'm still working in emulation and trying to understand the CCS compiler.

Hello (Sorry if i'm hard to understood. English isn't my mother langage).The download link for the code seem to be broken.It only allow you to download a .tmp file. I don't know for what it's useful. It appear in the link too.

Scelos, You are the second person who indicated that they had issues downloading the code. I decided to investigate a little farther. I bet you are using Firefox as your browser.

Since the file has a .c extension, Foxfire opens a window titled "Opening F8UY5....YYY.tmp" and asks "What should Firefox do with this file?". You should click on the the "Browse..." button and select Notepad (Window) or gedit (Linux). Hit the OK button once or twice, then save the file with the name that you desire.

I will add a .zip version of the file to prevent confusion in the future.

Doug,I just wanted to thank you for this "ible" and for introducing me to the Texas Instruments MSP430-series micro controller at $4.30/shipped each! Who knew a fun and versital little controller could be bought so cheap so I bought several! I am well on my way to collecting all items necessary to complete the motion camera. I also wanted to tell you and audience that I found a cheaper source for the PIR on Ebay if you can wait for it to be shipped from China. It's from seller "hi-etech" and is less than $5 (or offer) called "Pyroelectric Infrared PIR Motion Sensor Detector Module". If you want a PIR with LED lights that can be used at night, there is another ebay source item called the "Infrared PIR Sensor 6-LED Light Lamp Motion Detector" for cost of $4.15/shipped from seller "700store", also from China. Use as is or swap out the LEDs for 850n infrared LED so you don't startle the critters! With the PIR detector mocule you don't hack anything to obtain it. (it's not just the PIR but the whole module!) The other one just needs disassembly. With either one you just give it power and tie the output lead into your "ible"! With your camera sourced at $10, the micro controller at $4.30, and the PIR sourced under $5, that comes to $19.30 which leaves plenty of wiggle room for purchase of project box, breadboard, transistors, etc. One other thing. If you spend just $3.88 over the recommended camera, you save 2/3rds the space making it possible to use a project box 1/2 the recommended size. The cheapest miniature "spy" cameras can be had on Ebay, again from China, for $6.98/shipped plus Sandisk 2gb memory card for $6.88/shipped. Note: by changing to different camera, you may need to modify the source code for the MSP430 and if you do, please post it? Happy snipe hunting!

neetz, I finally got around to checking the menu on both cameras. They both take the same number of button presses to get to the high resolution/compressed mode that the wildlife camera uses.

One differences is the code that you see in the mode LCD located on the front of the camera. For the Vivitar, the mode code is CP, which gives you 60 images at 352x288 compressed. For the Aries, it is Hd, which gives you 76 images at 640x480 compressed.

neetz, In addition to the Vivitar camera that I used in the Instructible, I believe that the newer Aries 3-in-1 camera (without preview screen) being sold by Walgreens will also work without any changes to the instructible. I haven't actually tried it, but the instructions and features appear to be the same. The original Vivitar camera is available at CVS and some Walgreens.

The advantages of the Aries is that the resolution is a little higher (640x480). It also has a slighly faster shutter and can take 25 hi res- no compression pictures instead of only 20. The cost is the same.

There are some differences in color balance and sharpness. Below are pictures of the same objects taken at night under CFL lights on my kitchen table. The pictures were taken hand held (no tripod). The first one (bluer one) is from the Aries and is 640x480. The second one (greener) is from the Vivitar and is (352x288). When I look at the mat and objects under CFL lights the mat is closer to the green. During the day under daylight, the mat looks more like the blue. Both images were uploaded uncompressed, I don't know what Instructibles does to the images.

I would use the Aries if I was doing it again due to the higher resolution.