Welcome
Username or Email:

Password:


Missing Code




[ ]
[ ]
Online
  • Guests: 104
  • Members: 0
  • Newest Member: omjtest
  • Most ever online: 396
    Guests: 396, Members: 0 on 12 Jan : 12:51
Members Birthdays:
All today's birthdays', congrats!
Barry (70)
Snowcat (37)
wylie (43)


Next birthdays
02/01 Barry (70)
02/01 Snowcat (37)
02/01 wylie (43)
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 »   

Need help: Overcurrent protection in a DRSSTC

Move Thread LAN_403
101111
Wed Nov 12 2008, 02:38PM Print
101111 Registered Member #575 Joined: Sun Mar 11 2007, 04:00AM
Location: Norway
Posts: 263
Hi, I am now planning building my first DRSSTC. I am aiming for a little one like Steve Ward's DRSSTC-.5.

Now to the question: I have been looking on a circuit that Dan made: Link2 And I think it is interesting. But I am going to use one of Steve's schematics to drive the DRSSTC and I want keep the CT's used to a minimum. Is there anyway I can connect only the LM3914 circuit to fit into Steve's typical LM311 over current circuit and still remain a good accuracy?
I remember I saw a circuit that Reaching made, that was very interesting but I didn't manage to find it mistrust

Happily regards Christian K. smile
Back to top
HV Enthusiast
Wed Nov 12 2008, 06:21PM
HV Enthusiast Registered Member #15 Joined: Thu Feb 02 2006, 01:11PM
Location:
Posts: 3068
No.

I'm sure you can easily connect the LM3914, but you won't correct the offset / gain due to the bridge rectifier diodes, etc...

Also, my circuit does require that expensive LT1630 op-amp as its rail-to-rail output unless you are using pos and neg rails.

Also, in my circuit, you can DELETE the U3 op-amp branch. All that is doing is giving you a setpoint display of the current limit. You don't need that. In fact, i don't use that portion either.
Back to top
101111
Wed Nov 12 2008, 09:38PM
101111 Registered Member #575 Joined: Sun Mar 11 2007, 04:00AM
Location: Norway
Posts: 263
Ok, thanks.

In the thread you presents the over current protection you mentions that LM741 can be used instead of LT1630. If so do I need to do any adjustments to the circuit or can I just leave it as it is?

Also, If I decides to use your circuit can I then just connect it to the CT already used in the main driver circuit over current protection?
Back to top
Dylan
Wed Nov 12 2008, 09:39PM
Dylan Registered Member #1024 Joined: Sun Sept 23 2007, 10:56AM
Location: Northern NSW, Australia
Posts: 95
Hi Christian,
I may be wrong but I think you have answered your own question.
You say your goal is to add LM3914 based led display to Steves LM311 based OCD whilst minimising CT count.
Well pdf you posted is essentially exactly that.
As DG mentioned above, you do not require U3 opamp section.
----------------------------------------- ---------------------------------
The U1 section is basically the same as Steves LM311 section.
So by adding the U4 branch, which provides the sample/hold required, and LM3914 page, you will have what you are after without having to have another CT.
---------------------------------------------- ----------------------------
I have done this in my driver. --==Link==--
I DO NOT reccomend you use the circuit presented in my thread, stick to what is in the pdf you posted (I have since had to undo all my little cheats and corner cuts)
Back to top
101111
Wed Nov 12 2008, 09:51PM
101111 Registered Member #575 Joined: Sun Mar 11 2007, 04:00AM
Location: Norway
Posts: 263
Dylan wrote ...

Hi Christian,
I may be wrong but I think you have answered your own question.
You say your goal is to add LM3914 based led display to Steves LM311 based OCD whilst minimising CT count.
Well pdf you posted is essentially exactly that.
As DG mentioned above, you do not require U3 opamp section.
----------------------------------------- ---------------------------------
The U1 section is basically the same as Steves LM311 section.
So by adding the U4 branch, which provides the sample/hold required, and LM3914 page, you will have what you are after without having to have another CT.
---------------------------------------------- ----------------------------
I have done this in my driver. --==Link==--
I DO NOT reccomend you use the circuit presented in my thread, stick to what is in the pdf you posted (I have since had to undo all my little cheats and corner cuts)

Thanks, and I think you are right. The thing is that it wont be calibrated then. And I don't have a clue how I am going to calculate the right components to calibrate it. And I don't have CT to a oscilloscope so I can't measure that high currents.

Again, Thanks smile

Regards
Back to top
Dylan
Wed Nov 12 2008, 10:01PM
Dylan Registered Member #1024 Joined: Sun Sept 23 2007, 10:56AM
Location: Northern NSW, Australia
Posts: 95
Mmm, well, its really not that hard to calibrate everyting.
I assume one of your concerns is the accuracy of homemade CT's?
If so , that was also one of my concerns, --==Link==--
So , you can pretty much do the math, and all you should need for reasonable accuracy is a multimeter to set the opamp pots.
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.