Welcome
Username or Email:

Password:


Missing Code




[ ]
[ ]
Online
  • Guests: 42
  • Members: 0
  • Newest Member: omjtest
  • Most ever online: 396
    Guests: 396, Members: 0 on 12 Jan : 12:51
Members Birthdays:
One birthday today, congrats!
Frog_Qmak (34)


Next birthdays
03/01 mostlymacros (46)
03/02 Staff (31)
03/02 Doubl3 Helix (33)
Contact
If you need assistance, please send an email to forum at 4hv dot org. To ensure your email is not marked as spam, please include the phrase "4hv help" in the subject line. You can also find assistance via IRC, at irc.shadowworld.net, room #hvcomm.
Support 4hv.org!
Donate:
4hv.org is hosted on a dedicated server. Unfortunately, this server costs and we rely on the help of site members to keep 4hv.org running. Please consider donating. We will place your name on the thanks list and you'll be helping to keep 4hv.org alive and free for everyone. Members whose names appear in red bold have donated recently. Green bold denotes those who have recently donated to keep the server carbon neutral.


Special Thanks To:
  • Aaron Holmes
  • Aaron Wheeler
  • Adam Horden
  • Alan Scrimgeour
  • Andre
  • Andrew Haynes
  • Anonymous000
  • asabase
  • Austin Weil
  • barney
  • Barry
  • Bert Hickman
  • Bill Kukowski
  • Blitzorn
  • Brandon Paradelas
  • Bruce Bowling
  • BubeeMike
  • Byong Park
  • Cesiumsponge
  • Chris F.
  • Chris Hooper
  • Corey Worthington
  • Derek Woodroffe
  • Dalus
  • Dan Strother
  • Daniel Davis
  • Daniel Uhrenholt
  • datasheetarchive
  • Dave Billington
  • Dave Marshall
  • David F.
  • Dennis Rogers
  • drelectrix
  • Dr. John Gudenas
  • Dr. Spark
  • E.TexasTesla
  • eastvoltresearch
  • Eirik Taylor
  • Erik Dyakov
  • Erlend^SE
  • Finn Hammer
  • Firebug24k
  • GalliumMan
  • Gary Peterson
  • George Slade
  • GhostNull
  • Gordon Mcknight
  • Graham Armitage
  • Grant
  • GreySoul
  • Henry H
  • IamSmooth
  • In memory of Leo Powning
  • Jacob Cash
  • James Howells
  • James Pawson
  • Jeff Greenfield
  • Jeff Thomas
  • Jesse Frost
  • Jim Mitchell
  • jlr134
  • Joe Mastroianni
  • John Forcina
  • John Oberg
  • John Willcutt
  • Jon Newcomb
  • klugesmith
  • Leslie Wright
  • Lutz Hoffman
  • Mads Barnkob
  • Martin King
  • Mats Karlsson
  • Matt Gibson
  • Matthew Guidry
  • mbd
  • Michael D'Angelo
  • Mikkel
  • mileswaldron
  • mister_rf
  • Neil Foster
  • Nick de Smith
  • Nick Soroka
  • nicklenorp
  • Nik
  • Norman Stanley
  • Patrick Coleman
  • Paul Brodie
  • Paul Jordan
  • Paul Montgomery
  • Ped
  • Peter Krogen
  • Peter Terren
  • PhilGood
  • Richard Feldman
  • Robert Bush
  • Royce Bailey
  • Scott Fusare
  • Scott Newman
  • smiffy
  • Stella
  • Steven Busic
  • Steve Conner
  • Steve Jones
  • Steve Ward
  • Sulaiman
  • Thomas Coyle
  • Thomas A. Wallace
  • Thomas W
  • Timo
  • Torch
  • Ulf Jonsson
  • vasil
  • Vaxian
  • vladi mazzilli
  • wastehl
  • Weston
  • William Kim
  • William N.
  • William Stehl
  • Wesley Venis
The aforementioned have contributed financially to the continuing triumph of 4hv.org. They are deserving of my most heartfelt thanks.
Forums
4hv.org :: Forums :: Tesla Coils
« Previous topic | Next topic »   

A curious bug when using battery powered 555 interrupters

Move Thread LAN_403
plazmatron
Mon May 21 2012, 10:10PM Print
plazmatron Registered Member #1134 Joined: Tue Nov 20 2007, 04:39PM
Location: Bonnie Scotland
Posts: 351
For a while now, I have been developing a 'Dead simple DRSSTC' and recently boxed the thing, and tidied it up.
Normally, I have it computer controlled, but decided to build the ubiquitous 555 interrupter for it, for when I don't use the laptop with it.

I built a circuit using 3 555's, one for BPS, one for PW, and one for burst mode. The output is fed to a transistor switched LED, since I like to send my signals over fiber optic.

The circuit works fine, except, that when I happened to use a half dead 9v battery to run it, it ran for a little while, and as the battery became flat, the circuit stopped oscillating, and the output pin went high, and remained high!

If I had run this attached to a coil, and the battery had gone flat, I imagine the consequence would have been a smouldering mess!

The solution was to replace all of the 555's with their CMOS counterparts.
In this scenario, when the voltage dips low enough, the LED goes out first, protecting my DRSSTC.
Secondly when the voltage dips low enough for the 555's to stop functioning, the output doesn't go high, it goes low!

I wonder of anyone else has come across this, or destroyed a bridge because of it?

Les
Back to top
Sigurthr
Tue May 22 2012, 08:32AM
Sigurthr Registered Member #4463 Joined: Wed Apr 18 2012, 08:08AM
Location: MI's Upper Peninsula
Posts: 597
I had heard of this issue (555's putting out a HI signal when Vin is below nominal) back when I first started learning electronics, but I've never encountered it in person. Though, most of the 555's I use are CMOS based. A good reminder anyway!
Back to top
Steve Conner
Tue May 22 2012, 10:03AM
Steve Conner Registered Member #30 Joined: Fri Feb 03 2006, 10:52AM
Location: Glasgow, Scotland
Posts: 6706
My DRSSTCs all have a wired connection between the interrupter and the driver, using 9-pin serial extension cables.

The interrupter is powered off the driver's 15V supply, which is monitored by an undervoltage lockout circuit that inhibits gate drive if the voltage is too low.

Later I added an optical input, but I AC coupled it. A constant high level would only make a burst that lasted 10ms or so.

In industrial power electronics these things are really important. You don't want all your expensive IGBTs exploding because of a brief power dip.
Back to top
plazmatron
Wed May 23 2012, 01:18PM
plazmatron Registered Member #1134 Joined: Tue Nov 20 2007, 04:39PM
Location: Bonnie Scotland
Posts: 351
Steve Conner wrote ...

In industrial power electronics these things are really important. You don't want all your expensive IGBTs exploding because of a brief power dip.

I can imagine sitting down, working out what can go wrong, and mitigating it, is a significant portion of the design process in industry. Especially in critical applications such as life support!


Back to top
Neet Studio
Wed May 23 2012, 07:45PM
Neet Studio Registered Member #4037 Joined: Fri Jul 29 2011, 03:13PM
Location:
Posts: 86
I always ask the vendors what are the default state of their unprogrammed parts (i.e. pins floating, high, low, pulled up, down or unknown) as we tend to program them in system if it is not documented in the datasheet or user manual. Knowing the conditions of how the pins react to active signals without power (aka "hot-socketing") is important if you design cards that can be hotswap.

One time there was a sales guy from Analog Device when they said they carried those RS232 parts that are the same as Maxim. He wisely STFU when I told him the part number of an Analog Device 232 part that did a latch-up when externally connected to an active signal un-powered where as a Maxim part doesn't. So do not expect the generic jelly bean part all have the same behavior from all vendors.

Checking for all of these conditions are just part of a good design.
Back to top

Moderator(s): Chris Russell, Noelle, Alex, Tesladownunder, Dave Marshall, Dave Billington, Bjørn, Steve Conner, Wolfram, Kizmo, Mads Barnkob

Go to:

Powered by e107 Forum System
 
Legal Information
This site is powered by e107, which is released under the GNU GPL License. All work on this site, except where otherwise noted, is licensed under a Creative Commons Attribution-ShareAlike 2.5 License. By submitting any information to this site, you agree that anything submitted will be so licensed. Please read our Disclaimer and Policies page for information on your rights and responsibilities regarding this site.