NE555 Pin Diagram

Key Specifications

Per the TI NE555 datasheet (Rev K, SLFS022K) and ST TS555 datasheet (Rev 8, DocID 2182):

Typical Application Circuits

Circuit 1: Astable Multivibrator (Square Wave Oscillator)

The most-used 555 circuit. Generates a continuous square wave - no trigger signal needed. The frequency and duty cycle are set by two resistors and one capacitor.

Schematic connections:

• Pin 1 (GND) → Ground
• Pin 2 (TRIG) and Pin 6 (THRES) → Connected together → Timing capacitor C1 → Ground
• Pin 3 (OUT) → Output (to load)
• Pin 4 (RESET) → VCC
• Pin 5 (CONT) → 0.01 µF ceramic capacitor → Ground
• Pin 7 (DISCH) → Junction of R1 and R2. R1 → VCC. R2 → Pin 6/2 junction
• Pin 8 (VCC) → Supply (4.5–16V)

Design formulas:

• Output HIGH time: T_high = 0.693 × (R1 + R2) × C1
• Output LOW time: T_low = 0.693 × R2 × C1
• Frequency: f = 1.44 / ((R1 + 2×R2) × C1)
• Duty cycle: D = (R1 + R2) / (R1 + 2×R2)

The duty cycle trap: In the classic astable circuit, the duty cycle can never be 50% or less - because T_high always includes R1+R2 while T_low only includes R2. D > 50% always. If you need exactly 50% duty cycle, add a signal diode (1N4148) in parallel with R2 (anode to pin 7, cathode to pin 6) to bypass R2 during charging. Then T_high = 0.693 × R1 × C1 and T_low = 0.693 × R2 × C1. Set R1 = R2 for 50% duty.

Circuit 2: Monostable (One-Shot Pulse Generator)

Trigger it once, get one output pulse of a precisely defined width. Used for debouncing, time delays, missing-pulse detection, and turning a short button press into a clean logic pulse.

The trigger rule that trips everyone up: The trigger pulse on pin 2 must be shorter than the output pulse width. If the trigger stays LOW longer than the timing cycle, the output stays HIGH and never resets. This is the single most common monostable bug. Fix: AC-couple the trigger through a small capacitor (1–10 nF) with a 10kΩ pull-up to VCC, so the trigger pin sees only a brief negative spike regardless of how long the button is held.

Design formula:

• Output pulse width: t = 1.1 × R × C

Schematic connections (monostable):

• Pin 2 (TRIG) → Trigger source (AC-coupled or short negative pulse)
• Pin 6 (THRES) and Pin 7 (DISCH) → Connected together → Timing resistor R → VCC, and → Timing capacitor C → Ground
• Pin 4 (RESET) → VCC
• Pin 5 (CONT) → 0.01 µF ceramic → Ground

Common Mistakes When Using the NE555

Mistake 1: Leaving Pin 5 (CONT) Floating

This is #1 for a reason. The control voltage pin is a high-impedance node connected directly to the internal 2/3 VCC reference. Without a decoupling capacitor to ground, any noise on the supply rail - or even ambient EMI - modulates the threshold comparator's reference voltage. The result: jitter on your timing, false triggers, and frequency that drifts with your hand proximity to the board. The fix is a single 0.01 µF ceramic capacitor from pin 5 to ground. Always. Even in a breadboard prototype.

Mistake 2: Forgetting to Pull RESET (Pin 4) HIGH

Pin 4 has a weak internal pull-up - but "weak" means it can be pulled LOW by leakage currents on a PCB, especially in humid environments or after flux residue. If RESET floats just below the threshold, the 555 sits in permanent reset - no output, no oscillation. Connect pin 4 directly to VCC if you're not using the reset function. Don't rely on the internal pull-up.

Mistake 3: Using an Electrolytic Capacitor for Precision Timing

Aluminum electrolytic capacitors have terrible tolerance (−20% to +80% is not uncommon), high leakage current (which acts as a parallel resistance and skews the RC time constant), and significant temperature drift. If you're building a 555 timer that needs to be accurate, use a film capacitor (polyester or polypropylene) for the timing capacitor. If you must use an electrolytic, calculate the worst-case tolerance range before assuming the circuit works - your "1 second" timer might actually be anywhere from 0.8 to 1.8 seconds.

But even with precision resistors (0.1%) and film capacitors, don't expect the 555 to match a crystal or a microcontroller timer. As one StackExchange discussion noted, users report "large inaccuracies with precision components" - the 555's analog RC timebase has inherent limitations in initial accuracy and temperature stability. For applications demanding better than ±2% timing accuracy, a microcontroller's hardware timer or a dedicated oscillator IC is the right tool. The 555 is a workhorse, not a precision instrument.

Mistake 4: Trigger Pulse Longer Than Output Pulse (Monostable Mode)

In monostable mode, if the trigger pulse on pin 2 stays LOW longer than the timing period (1.1 × R × C), the output stays HIGH indefinitely - the 555 re-triggers itself. This is guaranteed to happen if you connect a push-button directly from pin 2 to ground. The fix: AC-couple the trigger with a series capacitor (1–10 nF) and a pull-up resistor (10kΩ) so pin 2 sees only a brief LOW spike, regardless of how long the button is held.

Mistake 5: No Supply Decoupling Capacitor

When the 555 output switches state, it pulls a sharp current spike from the supply - up to 200 mA in a few nanoseconds for the bipolar version. Without a 0.1–10 µF ceramic capacitor across VCC and GND (placed as close to pins 1 and 8 as physically possible), that current spike causes a voltage dip on the supply rail. The voltage dip modulates the internal reference - and suddenly your stable oscillator has glitches. One capacitor. Always. Right across the power pins.

Mistake 6: Not Accounting for the Discharge Pin's Current Limit

The discharge pin (pin 7) is an open-collector NPN transistor. In the bipolar NE555, it can sink up to 50 mA - but with a VCE(sat) that rises with current. If your timing resistor R1 is too small (e.g., 100 Ω with a 9V supply), the discharge pin tries to sink 90 mA - exceeding its rating and causing the internal transistor to saturate poorly, which shifts timing. Keep the discharge current below 10 mA for reliable timing. This means R1 ≥ 1 kΩ at 9V, or proportionally higher at higher supply voltages.

Worse: shorting pin 7 directly to VCC - even momentarily during breadboarding - can destroy the internal discharge transistor. On StackExchange, one user reported a 555 where "shorting it will do bad things" after accidentally connecting the discharge pin to the positive rail, resulting in a permanently damaged IC. The discharge pin has no internal current limiting beyond the transistor's own characteristics. Treat it with respect.

Mistake 7: The 555 That Works on the Bench But Dies After a Few Hours

Several StackExchange threads describe 555 circuits that run fine for hours, then stop - and the IC is dead, not just oscillating wrong. The usual suspects: (1) supply transients exceeding the 16V absolute maximum rating - add a 15V zener clamp across VCC if your supply has any overshoot; (2) inductive kickback from a relay or motor on the same supply rail - add a flyback diode and a separate decoupling cap for the 555; (3) a timing capacitor discharging into the discharge pin through an R1 value that's borderline - it works for a while, then thermal stress accumulates and the discharge transistor fails. If your 555 is dying in the field, scope the supply rail under all operating conditions before blaming the IC.

Where to Buy NE555 ICs

Contact ICMASS for current pricing. We stock NE555 (bipolar) and TLC555 (CMOS) variants in SOP-8 and DIP-8 packages. Volume pricing available - the 555 is one of the most cost-effective ICs in production, and we carry inventory for same-day shipment from Shenzhen.

Frequently Asked Questions About the NE555

Q1: What's the difference between NE555, LM555, and TLC555?

A: NE555 and LM555 are functionally identical - both are bipolar designs from different manufacturers (TI originally, now multi-sourced). The TLC555 is the CMOS version: same pinout, same timing formulas, but dramatically lower power consumption (60–300 µA vs 3–6 mA quiescent), wider supply range (2–15V vs 4.5–16V), and higher max frequency (~2–3 MHz vs ~500 kHz). The tradeoff: CMOS output current is lower (10–100 mA vs 200 mA) and timing drift over temperature is slightly worse in early CMOS versions (modern LMC555 has closed the gap). Use TLC555 for battery-powered designs. Use NE555 when you need to drive relays, lamps, or high-current loads directly.

Q2: How do I get exactly 50% duty cycle from a 555 astable?

A: The classic astable circuit can't do it - charging always goes through R1+R2, discharging only through R2, so T_high > T_low always. For 50% duty: add a signal diode (1N4148) in parallel with R2, anode to pin 7, cathode to pin 6. This bypasses R2 during charging. Now T_high = 0.693 × R1 × C and T_low = 0.693 × R2 × C. Set R1 = R2 for exactly 50% duty. The diode forward voltage (~0.6V) introduces a small error at very low supply voltages - compensate by making R1 slightly smaller than R2 (e.g., 9.4k vs 10k).

Q3: Why does my 555 timer frequency drift over time?

A: Three likely causes: (1) You left pin 5 floating - add a 0.01 µF ceramic capacitor to ground. (2) You're using an electrolytic timing capacitor with poor temperature stability - switch to a film capacitor. (3) Your supply voltage isn't regulated - the 555's threshold levels are ratiometric (1/3 VCC and 2/3 VCC), so in theory the frequency is supply-independent, but the internal comparator propagation delays are not. A 9V battery that sags from 9V to 7V can cause noticeable drift. Regulate the supply or use a CMOS 555 which has better supply rejection.

Q4: Can I run a 555 timer from a 3.3V supply?

A: The bipolar NE555 - no. Its minimum supply is 4.5V. But the CMOS TLC555 or LMC555 runs happily from 3.3V, and some variants go as low as 2V. At 3.3V, the output drive is limited (a few mA), so you may need a buffer transistor for anything beyond a logic signal. Check the specific CMOS variant's datasheet for minimum supply and output drive at your operating voltage.

Q5: What's the maximum frequency I can get from a 555?

A: Bipolar NE555: ~500 kHz practical, though some datasheets claim up to 1 MHz. CMOS TLC555: ~2–3 MHz. But at these frequencies, timing accuracy degrades significantly because internal propagation delays (typically 100–500 ns) become a large fraction of the period. For stable operation above 100 kHz, use the CMOS version and keep timing resistor values above 1 kΩ to avoid overloading the discharge pin.

Q6: How many LEDs can a 555 drive directly?

A: The bipolar NE555 output can sink or source up to 200 mA - enough to drive 10–15 standard LEDs (at 15–20 mA each) when connected in parallel with individual current-limiting resistors. But at 200 mA, the output voltage drop increases (VOL rises, VOH falls), and the chip gets warm. For more than ~100 mA total, use the 555 to drive an external transistor (BJT or MOSFET) and let the transistor handle the current. The CMOS 555 can drive far fewer - typically 1–3 LEDs directly - before needing a buffer.

Q7: Can I use a 555 to make a voltage-controlled oscillator (VCO)?

A: Yes. Apply a control voltage to pin 5. The internal threshold voltage (normally 2/3 VCC) shifts with the applied voltage - the timing capacitor now charges to the control voltage instead of 2/3 VCC, changing the frequency. In astable mode, this gives you a VCO. The control voltage range is roughly 0.5V to VCC−1V with useful linearity. Keep the control voltage source impedance low (<1 kΩ) - an op-amp buffer is ideal. And still connect that 0.01 µF capacitor from pin 5 to ground (in parallel with your control voltage source) to filter noise without loading the source.

Q8: Why is my 555 inaccurate even with precision resistors and capacitors?

A: Welcome to the 555's fundamental limitation. The 555 is an analog RC timer - its accuracy depends on resistor tolerance, capacitor tolerance, capacitor leakage, comparator offset voltages, and the internal 5kΩ divider's accuracy (which is typically ±5–10% from the nominal 5kΩ values). On StackExchange, users report "large inaccuracies with precision components" because even with 0.1% resistors and film capacitors, you can't escape the IC's own internal tolerances. The initial timing accuracy of a bipolar NE555 is typically ±2–3% - and that's before temperature drift adds another 50 ppm/°C. If you need better than ±2% accuracy, use a microcontroller's hardware timer, a crystal oscillator + divider, or a dedicated timer IC like the LTC6992. The 555 is for when "about right" is good enough - and for most blinking-LED and time-delay applications, it is.