loading
Recently, I have been experimenting with microcontrollers. A project that really caught my eye was the Chronulator at http://www.sharebrained.com. At the same time, Texas Instruments released an experimenter's kit called the Launchpad for the outstanding price of $4.30 plus shipping. This kit comes with everything you need to get started, including 2 microprocessors. One microprocessor is fairly decked out with lots of features. The other chip, a MSP430G2211, is more plain.


I decided as a learning experience to use the MSP430G2211 from the Launchpad kit to build a Chronulator. It turns out that this is a really fun project, and yes, I learned a lot!

See the plans for the mantel clock case that I built for this Chronulator.
    

Step 1: What You Need - Materials / Tools

The first thing you need is a Launchpad kit from Texas Instruments. You will also have to download the free compiler/debugger. They have 2 different options for compiler/debugger. I used the IAR Embedded Workbench KickStart.

The details on how to get a Launchpad are at http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_%28MSP-EXP430G2%29?DCMP=launchpad&HQS=Other+OT+launchpadwiki

List of Materials to make Chronulator:

  1  -   Radio Shack General Purpose Printed Circuit board part # 276-150 (project board)
  4  -   0.1uF capacitors
  1  -   1nF capacitor
  3  -   47k resistors
  3  -   push buttons
  1  -   14 pin DIP socket
  2  -   panel meters with any combination of full scale values of 50uA, 100uA, or 1mA
          note: I'm using a 50uA (mins) and a 100uA (hrs) because that is what I had on hand.
                   Higher sensitivity meters will result in using less power - longer battery life.
  1  -  4 pin male single in-line 0.1 inch header (to connect meters)
  1  -  4 pin female single in-line 0.1 inch header with wire
          note: I got mine by cutting off a small power connector from an old PC
                   power supply.
  1  -  battery holder for 3 AA sized batteries (Radio Shack)
  3  -  AA batteries
  1  -  battery leads for 9V size battery (the battery holder required this)
  1  -  MSP430G2211 (part of Launchpad kit)
  1  -  watch crystal - 32.768 kHz (One comes with the Launchpad - but I would
          suggest keeping that one on the Launchpad and getting another for this project.
          I went to Target and bought a watch from their dollar bin and took the 
          crystal from it. BG Micro sells them for $0.65, but you have to pay shipping.)
  1  -  LDO, low Iq, 2.5V voltage regulator (I'm using a Seiko S-812-C series regulator
         Mouser part # 628-812C25AY-G, Manuf # S-812C25AY-B-G  price: $0.51)
         The key is to use a LDO regulator with low quiescent current (Iq).  
         Note: Another alternative is to use 4 AA batteries and a 3.3 V LDO, low Iq, 
                   voltage regulator.

  2  -   resistors (values depend on meters used - see next step)
 
Misc:
         hookup wire
  

Tools Required:

   Solder gun and solder suitable for working with printed circuit boards
   Desoldering tool
   Multi-meter (optional, but great in troubleshooting - Harbor Freight price: $3.97)
   Screw drivers (for working with panel meters)
   needle nose pliers
   wire cutter

   
 

Step 2: The Circuit

Below is the schematic for the Chronulator. It has 3 push buttons, two of which allow you to adjust the minutes and hours. Pushing the minute or hour buttons will increment the minute or hour values by one. The third button is a reset button. The circuit diagram shows the meter current limiting resistors that I used for my particular meters. I have a 50 uA full scale meter for my minute meter, and a 100 uA full scale meter for my hour meter. The value of the resistor installed between the meter plus terminal and the microcomputer pin depends on the full scale of the meter used.

Here is a table of what resistor you should use based on the meter FS value.
It assumes you are using the 2.5V Vcc that the author originally used.
          
                Resistor           mAh used by                   mAh used by
    FS         value         Hour meter per 12 hrs     Minute meter per 12 hrs
--------------------------------------------------------------------------------------------------
  50 uA        33k                 0.025                                    0.3                                 
100 uA        18k                 0.050                                    0.6
   1 mA       2.2k                 0.5                                        6.0

More sensitive meters are definitely better. If you have to use a FS=1mA meter
use it for your hour meter.

With the 2.5V voltage regulator you should be able to take the batteries down to about 1V and get at least 80% of the batteries' energy (~2000 mAh) without any calibration shifts.
Note: If you are using 4 AA batteries and a 3.3V voltage regulator the results are the same.

If you are using a 3.3V Vcc use these resistor values:


                   Resistor
   FS             value
-------------------------------
  50 uA            47k
100 uA            22k 
   1 mA           2.7k 



If for some reason later when we calibrate m_cal and h_cal, the sum of the elements of your m_cal array or your h_cal array are not between 8000 and 9500 adjust your resistor value. If the sum of the array is above 9500 reduce the resistor value. If is below 8000, increase the resistor value.  


 Note: The capacitor that is wired parallel to the Reset button has been changed from 0.1uF to 1nF. This change was made to make "spy-by-wire" work.    dp-09/10/10

Step 3: Using IAR Embedded Workbench KickStart


In this step I would like to give the basic procedure for using the IAR compiler/debugger. Later in the project we will be tuning the adjustment arrays for the meters to compensate for nonlinearities. We will end up going through this process several times. Also, I wanted to point out steps 3 and 4, which caused me to do some head scratching because I didn't know about them.

  1.   Open existing or create new workspace.
  2.   Create new project for Chronulator.
  3.   Select Project -> Options... -> category: general options and change
        device to MSP430G2211.
  4.   Change Category to "Debugger" and change "Driver" to FET Debugger.
  5.   Hit ok.
  6.   Create new file (file -> new -> file)
  7.   Copy/paste code into new file and name file.
  8.   Go to the workspace window, your Chronulator project should be there. If not
        select the correct tab at the bottom of the window.
  9.   Right click the project in the tree and select add -> file "your file name .c".
        Your file should be added to the project tree.
10.   Right click the project again and select Rebuild all.
        You can now expand the "your file name.c" branch of the tree and see the
        h files that are added.
11.   Now to put the code on your chip, select the "make" icon or menu:
        Project -> make, or F7 (to make).
12.   Make sure that your Launchpad is plugged in to a USB port and that the
        Launchpad board has the MSP430G2211 chip on board (or has been connected via
        "spy-by-wire" with the project board) and the 32K crystal has been installed.
13.   Select the "Download and Debug" icon or menu: Project -> Download and Debug,
        or Ctrl+D.  This will download the code to the chip and start the debugger.
14.   If everything is ok, your computer will pause for a brief time and then a new set
        of toolbars will show up. This is the debugger. For the simplest case, we can
        hit the "Go" toolbar icon, watch the circuit operation and then hit the
        "Stop Debugger" toolbar icon. When you stop the debugger, the toolbar
        will return to their normal state.

If you make changes to the code you cycle through steps 12 to 14.



Step 4: The Code

The c code for the project is below in an attached file. You will note 2 different lines in the code that contain arrays of 12 numbers, one for minutes (m_cal) and one for hours (h_cal). After you load the code into your microprocessor via the Launchpad, you will need to adjust the numbers in these arrays. That will be covered in the later step.


Step 5: Helpful Gizmos

While I was building the Chronulator, I ended up constructing a few useful gizmos. They are not necessary, but I have found them helpful. They also can be used over again on other Launchpad projects that use batteries and require a regulated voltage. The gizmos consist of a small 2.5V regulator that can be piggybacked to the Launchpad, a power line for the battery pack to the regulator, and a super glued block of 5 jumpers to speed putting in and removing the jumpers on the Launchpad. The schematic for the little piggybacked regulator is the same as the power supply shown in step 2.


 

Step 6: Changing the Scales of the Panel Meters

Before you can change the scale of a panel meter, you must have a panel meter. One way to obtain panel meters is to visit swap meets or industrial surplus locations. Ideally you find meters that have a full scale of 50 or 100 uA. The more common full scale is 1 mA. Often you find panel meters with odd scales, for example pH, or scales marked for high currents like 5 A or  odd voltages.  These may still be usable. If you are lucky, the full scale value (ex. FS=100uA) will be on the meter face in small letters down below where you would normally view.  The neat thing about surplus or junkyard meters is they are often very unusual looking. So I suggest you keep a look out for these types of panel meters. 

You can always buy new panel meters, the going price is about $9 for a 2 - 2.5 inch meter made in Asia. The nice thing about these meters is you can select sensitivities from 50 uA through 1mA for the same price.   One source is BG Micro (http://www.bgmicro.com). The downside is they are a little boring.

When you select a meter, make sure that you can easily remove the front. If the front is glued to the back of the meter, pass on it and move on. When you remove the front of the meter, you typically find that the face is attached with a couple of screws to the meter movement.

I used 2 different methods to change the scales on the panel meters of my chronulator. On the minute meter, I printed out a new scale on plain paper and used a glue stick to stick it over the old scale. On my hour meter, I printed out a new face the same size as the old face on photo paper and flipped the face plate and used a glue stick to attach the new face to the backside of the plate. In this case, I wanted to retain the look of the original face plate by keeping the manufacturer's name and "Direct Current" heading. The best way to do this is to scan the original face plate using a flat bed scanner. The scanned image then becomes the background layer of your new meter face in the graphic program you use.  

The ShareBrained Technology site has several meter faces that you can download. They fit the meters used in their Chronulator kits. You might get lucky and be able to use one of them.

There is also a meter scale program that can be used that has a free limited version available from Tonne Software, http://www.tonnesoftware.com . I haven't used it.

One last note, the hour meter scale goes 12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12. It does not go 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12. This is because the Chronulator works like an analog clock and sweeps the hour hand as the hour progresses.

Step 7: Prep for Using "spy-by-wire"

Once you have your panel meters with their new scales, you are ready to tune the calibration arrays for m_cal and h_cal in the C code.

There are several ways that you can proceed. One way is to fabricate the circuit on the breadboard and move the chip to the Launchpad each repetition of adjusting the array. The other way is to keep the chip in the Launchpad and isolate the prototyping portion of the board. This is done by removing the 5 jumpers from terminal block J3 and supplying 2.5V to the external power terminal block J6. When you want to program the chip you have to restore the jumpers and remove the external power supply. If you use this second method you have to hookup the meters and the buttons.

There is a third way, using the "spy-by-wire" interface. In this method when we build our project breadboard, we include some test points. The test points allow us to connect between the project breadboard and the Launchpad. We can program our microcontroller without ever removing it from the project board. The Launchpad is used simply as a programmer. This is the method that I recommend you use.


Adding the Test Points:
There are 4 test points that need to be added.
      1.  Vcc  (IC pin 1)
      2.  Gnd (IC pin 14) 
      3.  Test (IC pin 11)
      4.  RST (IC pin 10) 

The simplest way to add a test point is to make a little U of wire and attach it at the desired location. See the pictures below.

Step 8: Using "spy-by-wire"

"spy-by-wire" is a two wire interface to program the flash memory on the MSP430 microcontroller. It is available on the newer MSP430 chips, including all of the chips that can be used on the Launchpad. The two pins used in this interface are RST and TEST. We will also bring over the power connections, VCC and GND, from the Launchpad when we program.

Below is a picture of the connections required to use the "spy-by-wire" interface.

Programming Connections:
    1.  Disconnect the battery pack from the project board.
    2.  Connect jumper from Launchpad J6 terminal "Vcc" to project board Vcc test point.
    3.  Connect jumper from Launchpad J6 terminal "Gnd" to project board Gnd test point.
    4.  Connect jumper from Launchpad J2 terminal "TEST" to project board TEST test point.
    5.  Connect jumper from Launchpad J2 terminal "RST" to project board RST test point.
    note: All 5 jumpers of Launchpad terminal J3 should be in place.

When the two boards are connected in this manner, you can program the microcontroller while it is in the project board.  You use IAR Embedded Workbench KickStart just as you would if the whole project was on the Launchpad.

Since we are using a different voltage supply voltage (2.5V instead of 3.3V) in this project, you must break the connections when you are testing the project board. Note: If you are using 4 AA batteries and a 3.3V regulator I would still break the connections to be sure that voltage you use to calibrate the meters with is correct.  

Testing Project Board Connections:
    1.  Disconnect all four of the project board connections to the Launchpad.
    2.  Connect the battery pack to the project board.
    3.  Press the Reset button.    


Step 9: Basic Checks Before Putting MSP430 Into Project Board

Here are some basic checks that you should make to your wired up project board before inserting the MSP430 chip. They can all be done from the top side of the breadboard.

Using an multi-meter as an ohms meter:

  1. Visually double check that you have placed the right pins of your regulator into
      Vin, Vout, and Gnd.
  2. Check between the pins in the IC socket for pin to pin shorts. There should
      not be any shorts. You will see ~94k ohms between pins 6 and 7 (2 x 47k).
  3. Check between pin 1 of the IC socket and Vcc. You should see a short.
  4. Check between pin 14 of the IC socket and Gnd. You should see a short.
  5. Check between pin 1 and pin 14 of the IC socket. You should see an open.
  6. Check across Vcc and Gnd and push each button in turn. As each button
       is pushed the meter should read from infinity to 47k.
  7.  Place the multi-meter positive lead in pin 6 of the IC socket and the negative
       multi-meter lead on the junction of the 47k resistor and the minute advance
       button. You should see a short. Do the same for pin 7 and the junction of
       the 47k resistor and hour advance button. Also do the same for pin 10 and
       the junction for the 47k resistor and the Reset button. 
  8.  Place the positive multi-meter lead on the positive minute meter pin of the
       meter junction block and the negative multi-meter lead on IC socket pin
       3. You should see the resistive value of your minute meter's current
       limiting resistor.
  9.  Place the positive multi-meter lead on the positive hour meter pin of the
       meter junction block and the negative multi-meter lead on IC socket pin
       4. You should see the resistive value of your hour meter's current 
       limiting resistor.
10.  Place the positive multi-meter lead on the negatives (2) of the meter
       junction block and the negative lead on Gnd. You should see a
       short for each negative.
10.  Make sure that the 32k Hz crystal is installed at IC socket pins 12 and 13.
11.  Visually triple check that you have placed the right pins of your regulator into
        Vin, Vout, and Gnd.
12.   Plug in the battery pack, place the multimeter on a voltage scale and 
        measure the voltage between Vcc and Gnd. You should see 2.5V.
13.   Unplug the battery pack.
14.   Install the MSP430 chip.  Make sure that pin 1 of the chip (upper left pin
        with the u shaped indent to the top, and top of chip facing you) is installed
        in pin 1 of the IC socket.


 

Step 10: Tuning the Meter Calibration Arrays

Analog panel meters have inherent nonlinearities, especially cheap or old meters with wear and dirt. We also add nonlinearities to the meter by driving them using PWM (pulse width modulation) and by our homemade meter scales. The c program for this project handles this by providing 2 arrays that are used to individually tune the meter readings.

The 2 arrays are named m_cal (used with minute meter)  and h_cal (used with hour meter). The 12 members of the array represent the number of clock pulses required to move the meter movement one major division. In the case of the hour meter, this is one hour. In the case of the minute meter, this is 5 minutes. The period for the PWM for both meters is the same. It is 10000 clock pulses.  The sum of all 12 members of a given tuning array will be less than the period. I tried to leave about 10% of the PWM period as head room. So typically the arrays will sum to about 9000.

The minute scale has 5 sub-divisions (1 min) per major division (5 mins). The hour meter sweeps every major minute division (5 mins), so there are 12 sub-divisions for the hour meter per each major division (1 hr). For this reason the numbers in m_cal should be divisible by 5, and the numbers in h_cal should be divisible by 12. This isn't an absolute requirement, but  using other numbers will result in remainders being dropped and could cause confusion.

Let us look at an example. If the hour array (h_cal) is equal to h_cal[] = {720, 708, 696, 736, ...}, to move the meter to 3 O'clock you need to set the PWM pulse count to the sum of 720, 708, and 696, which is equal to 2124. If you were at one O'clock and wanted to go half way between one and two you would add 360 (708 divided by 2 and rounded up to the next number divisible by 12) to 720.

The arrays that are in the program should be close to what you need regardless of the meter sensitivity you use, since you change the resistors to change the current provided to the meters. You should only have to tune them up.

How to tune the meter cal array:

Step 1:
We will start with the minute meter. To make things easier we will change the minute advance from 1 minute per button push to 5 minutes per button push. Locate in the code the following lines and un-comment them. They are part of the port_1 interrupt service routine.

// for (int j = 1; j <= 4; j++) // inc 4 mins Uncomment these 4 lines when tuning m_cal
// {
// one_min();
// }

Disconnect the battery pack of the project board and make the "spy-by-wire" connections between the project board and the Launchpad. Load the modified program onto the MSP430.  Now everytime we push the minute increment button the minute meter will jump 5 minutes instead of 1.


Step 2:
Remove the "spy-by-wire" connections form the project board test points and reconnect the battery pack. Press the Reset button. Next adjust the zero of the meter. Then press the minute increment button and observe where the meter comes to on the scale. It should be close to 5 minutes. Write down whether it is less than 5, exactly at 5, or greater than five. Press the minute increment button again and determine how close to 10 minutes it is. Do this to about 20 minutes (4 button presses).

Step 3:
Disconnect the battery pack of the project board and make the "spy-by-wire" connections between the project board and the Launchpad. Using your notes adjust the first four members of m_cal based on what you observed. If the meter was higher than expected then adjust the member down. If the meter was below what you expected adjust the member up. Start from the lower end of the scale and move up. If you see a trend where each time you push the button the difference becomes greater from the desired point reduce all the numbers. If the first one is off a little and the others seem to be off about the same offset, than adjust the first member that is off. I usually make adjustments of 5 or 10, unless I am way off then I make adjustments of 20. After you have made the adjustments to m_cal, enter the debugger and download the changes to the chip.

Step 4:
Remove the "spy-by-wire" connections form the project board test points and reconnect the battery pack. Observe the results of the changes you made. Repeat steps 2 (without adjusting the meter zero), 3, and 4 as needed, slowly moving up the scale (25 minutes to 60 minutes) until every time you hit the minute increment button, the meter goes exactly to a 5 minute major division of the scale.

Step 5:
When you are happy with the tuning of the minute meter you can move to the hour meter. I suggest that you re-comment the 4 lines we uncommented in step 1 and make sure the changed code gets back on the chip.

Step 6:
The tuning of the hour meter h_cal array is similar to what you did on minute meter. When you hit the hour increment button it should jump to the next hour on the scale. The adjustments should be multiples of 12 instead of multiples of 5. I typically make adjustments of 12 and 24.


I know this procedure sounds difficult, but it is really simple once you determine how much the meter will move to your adjustment. The whole thing should take no more than 30 minutes.

 





Step 11: Determining the 32.768 KHz Crystal's Load Capacitance

One of the potential gotchas of this type of project is selecting the correct load capacitors (C_load) for the 32.768 kHz crystal. You often have little data about the crystal. Different crystal manufacturers design the crystals with different load capacitor requirements. Searching the web I have seen a range of 6 - 22 pF recommended. The most common one appears to be 12 pf.

Differences in circuit layout on the project board (or PCB) complicates the problem by adding more capacitance. On the plus side, the MSP430G2211 has the ability to provide different capacitance values to the circuit. We can change the capacitance value within a range by software. In the code you will find the following lines. We will select one based on the result of our tests.


// crystal Cload capacitor adjustment - only one line of next four should be uncommented
// BCSCTL3 = LFXT1S_0 + XCAP_3; // 32768KHz crystal, 12.5 pF
// BCSCTL3 = LFXT1S_0 + XCAP_2; // 32768KHz crystal, 10 pF
   BCSCTL3 = LFXT1S_0 + XCAP_1; // 32768KHz crystal, 6 pF
// BCSCTL3 = LFXT1S_0 + XCAP_0; // 32768KHz crystal, 1 pF


Impact of an incorrect selection of C_load:

When C_load for a crystal is too high the crystal oscillates at a slightly lower frequency. Likewise, when the capacitance is too low the crystal will oscillate slightly faster. For a 32.768 kHz crystal, we are generally talking about 1 or 2 Hertz. One or two Hertz, you say, that doesn't sound like much. What is the big deal?

The MSP430's 16 bit timer resets every 2^15 or 32,768 pulses. If we use a crystal that provides exactly 32,768 pulses per second, then the timer will reset every second. If the crystal is actually running at 32,766 pulses per second, the effective MSP430 "second" is

1 sec + 2/32766 sec = 1 1/16383 sec

After 16383 seconds (~4.55 hours), the Chronulator would be one second behind a clock with a crystal running at 32,768 Hz. In other words, it would lose a minute every 11.375 days.


    Crystal            Pulses       Time to be       Time to be        Fast /
  Frequency           Off            off 1 sec.           off 1 min.       Slow
----------------------------------------------------------------------------------------
   32,766                -2              4.55 hrs.         11.375 days     Slow
   32,767                -1              9.50 hrs.         22.750 days     Slow
   32,768                 0                 -- should keep good time --
   32,769                 1              9.50 hrs.         22.750 days      Fast
   32,770                 2              4.55 hrs.         11.375 days      Fast


How to select the proper value of C_load:

Step 1:

Select a watch that keeps very good time, or use your computer or cell phone clock, to be your standard. Place your standard next to the Chronulator. Wait until your clock' second hand is at about at 20 seconds and quickly set your chronulator time to just one minute behind your clock. When the clock's second hand approaches 12 (or 60 if digital) push the chronulator's minute increment button to bring the two clocks into sync. Since you will most likely be off a second or two, observe both clocks another minute to get the exact second that the Chronulator's minute meter advances ("ticks"). Write down the date, time, and the second of the "tick". You will not remember.

Step 2:
Wait a day or two, then check to see if the both clocks are still in sync. If you are not sure wait a few more days, by that time if they are off, you should be able to tell. If you still can't tell, then things are ok and no adjustment will need to be made.

Step 3:
If the clocks have lost sync, adjust C_load capacitance by changing one of the commented lines above in the c program and commenting the setting that was in use. If your standard clock is ahead of the Chronulator, the Chronulator is slow. Decrease the capacitance value. If your standard clock is behind the Chronulator, the Chronulater is fast. Increase the capacitance value.

What if your clock is still fast and you can't increase the capacitance any higher? In this case, you could add 2 very small capacitors (6-12 pF) from each of the crystal's leads to ground. I would just try another crystal. If you decide to add capacitors you can get them from Mouser (6 pf - Mouser part # 81-RPE5C1h6R0D2P1B03 $0.18, 12 pF - Mouser part # 81-RPE5C2!120J2P1Z03 $0.23).

What if your clock is still slow and you can't decrease the capacitance any lower? In this case, check if you can reduce the capacitance on your project board. This can be done by making sure that the crystal is close to IC pins 12 and 13. Also make sure that the runs for the crystal are short. If this doesn't help, I would try another crystal from another source.


By the way, if you have a pulse counter, you can make ACLK available at P1.0 with a simple program (attached below) and check the crystal's frequency in the project board directly. I used this technique to observe changes on my Launchpad / crystal setup. I found that the recommended setting of 12 pF (XCAP_3) was a little too high C_load. Look at the different photos below to see the results of different XCAP settings. You might wonder about my counter calibration. I feel very comfortable that it is correct, because I was able to achieve a 32,766 Hz setup on my project board / crystal combination. With this setup, I observed the 1 second loss every 4.55 hours shown in the table above. When I optimized it for C_load (i.e., observed freq = 32,768 Hz), the clock was right on the money.

Step 12: FAQ

Q: What about a case?
A:
See my mantel clock case for this project at:
     https://www.instructables.com/id/Mantel-Clock-Case-for-Chronulator-Meter-Clock

Q: How does the code work?
A:
  The watchdog is set to delay mode and creates interrupts at 1 second intervals, using ACLK and the 32.768 kHz watch crystal. This allows you to count seconds. Timer_A interrupts are used to generate 2 independent PWM outputs which drive the meters. Port_1 is used to provide interrupts for the minute and hour increment buttons. You will note that there is no loop in the main subroutine. The program is completely interrupt driven after it reaches the end of main(). When not servicing an interrupt the MSP430 is in LPM0.

Q: Why doesn't "spy-by-wire" work?
A:
  The most likely cause is that you have a 0.1uF capacitor parallel to the Reset button instead of a 1nF (0.001uF) capacitor.

Q: Can I use a 3.3V voltage regulator instead of a 2.5V one?
A:  Yes, a 3.3V voltage regulator can be used, but you should use 4 AA batteries (6V) instead of 3 (4.5V). The battery count is increased so the batteries can age with out causing PWM calibration problems. The regulator should be LDO and low Iq.

 

<p>Thanks for sharing .... Very good Explanation .... :)</p>
Just got a couple of them. For less than five dollars they are a steal compared to the Arduino stuff.
Since several comments on this Instructable asked battery related questions, I just wanted to note that&nbsp; the three off brand AA batteries in the original clock died on May 5, 2012 after -21 months of service. The clock kept accurate during the whole life of the batteries.
Any chance it might work using only 2 AA batteries and the same Seiko S-812-C regulator ? I am a bit short of real estate for my project so saving a battery would be helpfull... And the LDO datasheet states a 0.12V drop so it should work no ?<br>
It would work with 2 batteries, however when the batteries were depleted to 2.62V (i.e., each battery at 1.31V) the regulator would drop out. At a battery terminal voltage of 1.31V you have used less than 1/3 of the energy stored in the battery. So if you were using only 2 batteries the clock would stop working correctly way before the batteries died.<br> <br> Using 3 batteries, and allowing them to drop to 2.62V (i.e., each battery at ~0.87V), you use all of the batteries' energy.<br> <br> You would be better off using 3AAA batteries , than 2AA batteries. The AAA batteries have about 1200mAh vs. the 2400mAh of the AAs. So the 2AA batteries would drop out at ~800mAh (about 1/3 of life), where the 3AAAs would be exhausted and use their full 1200mAh<br> <br> Have you considered two small Li Photo 1/2AA size batteries? They are more expensive than the alkaline batteries, but they have a small form factor. The Li battery's voltage/energy curve is more flat and I believe they would fit your needs. They have a nominal voltage of 3V. You would want the one that is a little longer (EL123), not the shorter one (EL1CR2). You would need 2 of them in series Both together would take up the space of a single AA battery.<br> <br> The reason that you need the regulator is to keep the PWM &quot;on&quot; voltage the same during the life of the batteries. If the voltage magnitude changes, the current to the meter will also change.
Using a switchmode power supply chip, namely the 34063, you can step down or step up the supply voltage to suit your clock's requirements. I have his chip configured in the buck circuit shown below, and by doing so i have reduced the total current draw of the project from 10.05mA (317T adjustable linear regulator) to 2.82mA(nominal clock requirement).<br>This is could be a great way to increase the battery lifetime of your circuit if the prescribed 2.5v reg draws more than this. Switch mode power supplies love efficiency.<br><br>the below schematic was generated by this webpage:<br>http://dics.voicecontrol.ro/tutorials/mc34063/<br><br>and and accompanying video tutorial helps you understand the function and method of inputting correct data into the above link.<br>http://www.eevblog.com/2010/09/10/eevblog-110-lets-design-a-dc-to-dc-switchmode-converter/<br><br>It's a long video, but has a lot of insight into a very useful and reliable component.<br><br>As mentioned by me earlier, a problem i had was finding a dc adapter that had a clean DC output. With this chip you can SELECT how clean your output is in the order of mA ripple.
Note: The above image is a BELOW view of the chip. I don't know why the creator decided this was a good idea.<br><br>Using a step-up configured circuit with the 34063, it would be quite possible to run the project (or any) off a single AA (or D for longevity) cell. My above circuit is suited for 3 D cells in series as the input.
The thing is that 2.82 mA is huge compared the MSP430 ~0.1uA in sleep mode and the Seiko S-812-C ~1uA consumption. My project is not exactly a clock but more like a tea timer so it'll be sleeping most of the time. I would like to keep the &quot;standby&quot; consumption as low as possible.
Miko's idea of a charge pump type regulator is a good one for single battery operation, but you need to use a low quiescent current (Iq) regulator.<br> <br> A good candidate would be Texas Instrument's TPC60310. The regulator circuit is slightly more complex than the Seiko regulator specified in the project since you need a few more capacitors and an inductor. Also, these type of regulators are generally surface mount packages.<br> <br> Since I tend to make my own PCB boards, the surface mount package would not be an issue. Texas Instruments also has a very generous sample program. So you would most likely get the regulator for free.<br> <br> The TPC60310 can be run in &quot;Snooze&quot; mode if the load is less than 2 mA. In this mode the Iq is ~2 uA. The load presented by the clock in the instructable meets this requirement if the right meters are used.<br> <br> If anyone knows of a similar regulator that has a through-hole or larger pitch SM package, please shout out.
I guess you meant TPS60310 and not TPC60310. I'll try to find a couple of these.<br>Else I came accross this one: LTC1502 from Linear Technologies (http://www.linear.com/product/LTC1502-3.3). It seems it is available in SOIC , which is larger than the TI one, right ?
I&nbsp; did mean TPS60310 not TPC. Sorry for the confusion. The Linear Technologies part looks like a good candidate also. The SO package has a center of lead to center of lead pitch of 50 mils. The package for &nbsp;the TPS60310 is 20 mils center lead to center lead pitch.. The SO package would be much easier to deal with.
Thanks for the detailed answer, I understand better now. I think I'll go for 3xAAA. It's not that I do not like the EL123 but I would try to use batteries as &quot;standard&quot; as possible. So that I have no troubles finding them at the shop around the corner :-)
Using a 317T adjustable linear reg for my power supply circuit has worked out well for me when running off batteries, instead of the preset 2.5v reg in your original design. However, i decided to convert the setup to be able to run off a 6V regulated power adaptor.<br>There were initial troubles with the chip not responding to any inputs when run off the adapter. I suspected that the very low reset cap value was the culprit in this issue. By replacing the reset cap to 100N (as per the authors original design) and then later removing the reset cap entirely, i have been successful in operating the clock off the mains adapter. Soon i will be following the steps for calibration for the crystal load capacitance and hopefully we won't see any accuracy shift between running from perfect DC put out by chemical cells, and less clean adapter power.<br><br>During my troubleshooting process i also added a blocking diode across the micro-ammeter terminals, even though the very low voltage and current shouldn't be a problem. Due to the low voltages involved i suspect the diodes will be doing nothing at all, but hey, why not.
Unsuccessful. This project requires a very, VERY clean DC to run properly. Looks like if i can't find an ultra clean 2.5v supply i'm stuck with batteries for this clock.
miko,<br> &nbsp;&nbsp;&nbsp; Completely removing the capacitor from the reset line is bad idea. It buys you some immunity to power supply glitches. The 47k resistor pullup with 10nF capacitor is the same circuit used on the Launchpad.&nbsp;<br> <br> &nbsp;&nbsp;&nbsp; I have run versions of this clock using a wall wart and a USB wall plug (eBay about a $1) with no issues. I would suggest that you try addng a 1-10 uF capacitor connected to the power regulator's output to ground. Depending on your layout and the regulator that you use this might be necessary.<br> <br> &nbsp;&nbsp;&nbsp; BTW, with&nbsp;low current meters this clock should run over a year on the&nbsp;same set of batteries.<br> <br> &nbsp;&nbsp;&nbsp; Let me know if this&nbsp;helps.&nbsp;I would like to see your clock be successful.<br>
Should have said 1 nF not 10 nF&nbsp; and the suggested 1-10 uF capacitor should be a tantalum (Ta) capacitor in your final circuit. You can test with a non-Ta cap.
You're absolutely right. And using a usb wall wart is a very good idea too. They are quiet and still meet the 2.5v difference required for the 317 regulator. I will be trying this tonight. My clock definitely won't run for a full year round thanks to my use of the 317. The total circuit draws 10.9mA average which is enough to drain a AA in a week or so.<br>I will be replacing the power supply with a 5v usb supply i have around here somewhere and returning the circuit to it's previous prescribed state. At the moment though it runs very well off batteries, with 0.99974 seconds on the crystal corresponding to one second in reality. So once this power supply issue is sorted i should be ready to construct a case.<br><br>The attached image shows the two micro-ammeters that i'm using for the project, the left hand one dating 1959. To do these gorgeous meters justice, I'm determined to complete this project in its entirety.
miko,<br> &nbsp;&nbsp;&nbsp; Those are beautiful meters. That is going to be a stunning clock.
Hi ! What can i do if i accidentally broke the reset pin on the chip ? i have a small tssop chip , i managed to program it , i placed it where i wanted but i forgot to pull-up the pin and when i soldered it , it broke. And without that pull-up the chip isn't powering .
Well.. i managed to cram a little solder in there and it made contact . I don't think there was much to do but throw the chip. Unfortunately for me it was the only one in the tssop form and i needed it so i did my best to fix it. The next two pins are also covered in solder but i didn't need them in my project so it was ok .<br>
&nbsp;&nbsp;&nbsp; Sounds like you made the best of a bad situation. You do need a pull-up resistor on the reset pin or the chip will just keep resetting.<br> <br> &nbsp;&nbsp;&nbsp; If you have a solder bridge to the test pin you will have programming issues. Spy-by-wire programming&nbsp;uses both test and reset pins.
Yeah, but i wasn't going reprogram it anyway so it all worked out ok .
Now that it's been a good few months since you created this clock, how has the accuracy and precision held up?<br>I have wanted to make an ammeter clock for quite a while now and have toyed with the idea of digital to analog converters, but they don't had a high enough resolution. This instructable seems like the best bet for making a clock, and seeing as i have a launchpad and two remarkably pretty microammeters, I'd like to give this design a try.<br><br>There seems to be a lot of fiddly calibration and trial + error in this i'ble, but what else can you expect from analog circuitry. The theory you have applied in the construction of this clock is impressive.
&nbsp; Thank you for the kind words.&nbsp;<strong>&nbsp;<br> <br> &nbsp;&nbsp; The clock is still right on the money.</strong> Sometimes when the weather changes drastically I have to touch up the zero on the hour meter. The hour meter&nbsp;is pretty old and has gone through some hard times. I have not had to adjust the time except for daylight saving time. The original akaline batteries are still working.<br> <br> &nbsp;&nbsp;&nbsp; I have since made another clock (see secondary picture on last step). This new clock used brand new meters and had more accurate meter faces. Setting up the minute and hour calibration arrays was a piece of cake. All I had to do was find the full scale deflection value and divide it by 12, then made a few minor tweaks of some of the values to fine tune. Remember to keep the minute array members divisible by 5 and the hour array members divisble by 12.<br> <br> &nbsp;&nbsp;&nbsp; Do not be afraid of the tuning procedure. Once you start getting visual feedback from the meters, it goes quickly.<br> <br>
thanks for the effort of detailing everything. just finished building it, it works perfectly!!!
Fantastic! I would love to see a picture of your clock.
Awesome clocks!
Those Launchpad kits seem to be pretty popular; I ordered one from Mouser and it's back-ordered for 13 weeks. Does any one know of a comparable chip?
You might try to order directly from TI. The link to start from is<br> <br> <a href="http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_%28MSP-EXP430G2%29?DCMP=launchpad&HQS=Other+OT+launchpadwiki">http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_%28MSP-EXP430G2%29?DCMP=launchpad&amp;HQS=Other+OT+launchpadwiki</a>
Great! That's the project I was looking for to start with my launchpad.<br>But I did not really understood why you made an extra board an not use the lauchpad. I think, feeding the USB plug with 4 AAs should work well @3v6.<br>Is it only saving power to run @2v5, or is it completely impossible to use the lauchpad?
This project was a lot of fun and I learned a lot. I transferred the project to another board so that my Launchpad would be available for the next project. I originally used a proto board and the launchpad to setup the circuit. <br> <br>Using 4 batteries and a LDO low Iq 3.3 V or 3.6 V regulator, such as the TPS77301DGK used in the Launchpad, would work just as well as the 3 batteries and a 2.5 V regulator. <br> <br>It was just a personal choice. I should have made it clear that a 3.3 V regulator could be used if you increased the supply voltage to 6.2 V (4 batteries). That would allow the batteries to run down to about ~ 0.9 V before the PWM outputs lose calibration. <br> <br>Thank you for the input! I will edit the instructable to make this option clear.
Your Chronulator got featured on <a href="http://www.43oh.com/2010/09/an-msp430-based-chronulator-interesting/">43oh</a>. This is a sweet project and will make a fine desk clock.&nbsp;<br> One question - why did you not use the crystal that comes with the kit?
The main reason was that I already had it soldered to my Launchpad. They are so cheap, it seemed easier to just get a new one.
great work! great instructable as well!
Excellent work sir. The DPRG would enjoy having you perform a demo at one of our RBNO's, especially since you are a dues paying member. Doug Emes Dprg.org Dallasmakerspace.com
Nice. Clock/time based projects are an excellent application for the low-power LaunchPad micros. When TI finally decide to deliver to Australia I will definitely be referring to your project.

About This Instructable

30,548views

50favorites

License:

More by Doug Paradis:The Sprintronic - Clock with Laser Cut Case Cheap Tires for Robot Wheels Cheap Motion Detection Wildlife Camera 
Add instructable to: