playing with the NE556 chip again; more questions

Feb 28, 2012 9 Replies

This time I built two astable circuits, using different designs (from the same book), on the two timers in one TI NE556 chip.



Timer A:



reset pin --- Vcc discharge pin --- not connected



control pin --- not connected



output --/\/\-- trigger & threshold --|(-- ground



Timer B:



reset pin --- Vcc



Vcc --/\/\-- discharge --/\/\--- trigger & threshold --|(- ground | | |--|>|--| 1N4148


To avoid confusion (as generated by my previous post), I've used pin names rather than numbers. The 556's ground & Vcc pins are connected normally to a 9 V battery. The output of each timer is a 470 ? resistor in series with an LED (so 20 mA on each output, well under the 200 mA recommended limit in the specs).


Circuit A provides equal mark & space times, with a total of 1.4×R×C. Circuit B is supposed to have independent mark & space times, each



0.7×R×C.

I've wired them up with R=6.9k ~ (for A and for each resistance in B) and C=100 µF (on each timer), which gives a theoretical mark+space of



0.96 sec for both circuits.

At some point, I noticed that application note PDF for the Philips version of this chip strongly recommends connecting the control pin through a 10 nF capacitor to ground if you're not using the control function (to protect the timer from noise). So I wired one between each control pin & ground.


I've only seen circuit A in this book; other sources only give circuit B and say to use the same resistance in both positions if you want equal mark & space. Is circuit B better than A? Why?


The two circuits seem to interfere with each other, and the control bypass capacitors affect the time as well. Lacking fancy equipment, I measured the mark+space time by timing 10 pulses with a stopwatch & dividing, and got these results:



with the control bypass capacitors:



timer A with B off: 1.1 sec timer B with A off: 0.9 sec timer A with B on: 0.6 sec timer B with A on: 0.6 sec



without the capacitors:



timer A with B off: 1.2 sec timer B with A off: 1.0 sec timer A with B on: 1.3 sec timer B with A on: 0.9 sec



Should they interfere this way, or have I goofed something up?



Nam Sibbyllam quidem Cumis ego ipse oculis meis vidi in ampulla pendere, et cum illi pueri dicerent: beable beable beable; respondebat illa: doidy doidy doidy. [plorkwort]

The control input is sensitive and any little wiggle in the common circuit for that cap is going to propagate and cause some shift in the timer.

Try attaching the low side of the bypass caps to a common trace/path directly to the (-) rail with nothing else connected to that rail between..

Your readings with the use of the bypass cap on the control pin are most likely more accurate to what you should be getting with the set up you have also, you must remember the 556 uses a single power rail inside for both units, one unit could offset the other depending on what they are doing. In cases like these, you use 2 555's instead.

Jamie

A

B

"A" works best win CMOS devices where the output goes all the way up to the positive supply voltage and all the way down to ground.

"B" is better in Bipolar (like the NE555 and NE556) where the output is not symmetrical and the two resistors can be varied to balance the ratio.

They should be fully independant. check that the powersupply pins and timing capacitors are wired correctly.

?? 100% natural

The output has nothing to do with the charge and discharge times in "B".

That does make them a bit more consistent --- I wouldn't have expected breadboard leads to have much effect at low frequencies like this.

OK. I expected that by keeping the output current below 20 mA on each side, the single power rail effect would be insignificant.

As it turns out, though, I get the biggest improvement in consistency by using the reset pins properly to switch the timers on & off (reset to Vcc for on, to ground for off), instead of just pulling one of the wires so the LED stops blinking. Doing it that way (with the control bypass capacitors grounded more tightly gives these:

A with B on: 1.2 sec B with A on: 1.2 sec A with B off: 1.2 sec B with A off: 1.0 sec

which could be within stopwatch measuring error.

Thanks!

XML is like violence: if it doesn't solve the problem, use more.

It shouldn't at those frequencies.

I've never bypassed the control pin when I've used 555s.

Michael

That makes sense, thanks.

Aha, the TI data sheet shows the 0.01 µF from CONT to GND in the monostable example, but for the astable example circuit, it shows CONT open but with the note "Bypassing the control-voltage input to ground with a capacitor might improve operation. This should be evaluated for individual applications." Fairly ambivalent.

OK, I'll try those & see how they improve things.

Thanks! ISTR reading that the Rs in the R C timings can range from

1 k? to 1 M? and work, but I guess (other things being acceptable) higher resistances are better because they reduce those currents.

...

As it turns out, I've got a couple of spice & geda packages available already on Ubuntu, which I'm working out how to use. Thanks for the example.

Sure, that's the most important part after "don't set anything on fire".

:-)

...the reason why so many professional artists drink a lot is not necessarily very much to do with the artistic temperament, etc. It is simply that they can afford to, because they can normally take a large part of a day off to deal with the ravages. [Amis _On Drink_]

The reason for lowering the capacitance of C1 is the same reason that if you had to fill and empty a glass once a second, the smaller the glass you used, the less water you'd use, which equates to less energy used in the transaction. The lowest R1 can be is dictated by how much current the discharge transistor can take, while the highest R is limited by the leakage current of C1, TH, and TR\.

Thanks again!

Physics is like sex. Sure, it may give some practical results, but that's not why we do it. [Richard Feynman]

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required