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.
Registered Member #42796
Joined: Mon Jan 13 2014, 06:34PM
Location:
Posts: 195
Currently i'm rebuilding my SSTC to handle more power than previously. Because of this i want to synchronize the interrupter signal with the coil resonant frequency to avoid hard switching. So i'll be using a D type flip-flop between the interrupter and gate drive IC.
In all the circuits i found the interrupter signal is connected to RST pin of the flip-flop while keeping D pin high but this will result in synchronization only on high to low transitions of the interrupter. I'm a bit concerned about this because it might result in quite short on times for the first half cycle which might create problems for the IGBT's...
So why not connect the interrupter signal to the D pin of the flip-flop and held CLR high so that both low to high and high to low interrupter transitions get synchronized with the coil resonant frequency and avoid those possible low on times?
Or it doesn't matter because the moment the interrupter goes high will be the moment the coil will start osculating so the low to high interrupter transition will always be synchronized regardless of the presence/absence of a flip-flop?
Registered Member #30
Joined: Fri Feb 03 2006, 10:52AM
Location: Glasgow, Scotland
Posts: 6706
Yes, the low to high transition of the interrupter signal is what starts the oscillations, so it can't be synchronised. There is no clock signal to synchronise it to until the oscillations have started.
Registered Member #42796
Joined: Mon Jan 13 2014, 06:34PM
Location:
Posts: 195
thanks Steve
I got mis-leaded when i tested my circuit because i used a signal generator tor the clock input and that why i saw the lack of synchronization on the low to high interrupter transition...
I've always wondered why the use of a D FlipFlop instead of an AND gate.
The only thing I can figure is that this would pulse the enable at the feedback frequency. To stop the enable being switched at fres you'd have to add a buffer on the feedback branch going to the AND gate and place a RC filter after the buffer that holds the signal above the switching transition voltage while feedback is present but doesn't extend the fall times by so much that you lose synchronization. This might be very difficult to do though.
That brings up why not just AND feedback and interrupter and feed that into gate drive input and just hold enable HIGH with a pull up. It should still transition HIGH to LOW as normal but with no feedback going to the AND gate there may not be a LOW to HIGH initialization.
You could pass raw interrupter to Enable instead of using pull up and this should provide the oscillation startup ping like normal. I think this would work as the normal state is no feedback signal and a LOW to HIGH on the Enable line causes an oscillation ping which starts feedback.
So if my train of thought is correct then a replacement for the D FlipFlop would be an AND gate to synchronize feedback and interrupter signals and feed raw interrupter to Enable as normal.
I've always wondered why the use of a D FlipFlop instead of an AND gate.
The only thing I can figure is that this would pulse the enable at the feedback frequency. To stop the enable being switched at fres you'd have to add a buffer on the feedback branch going to the AND gate and place a RC filter after the buffer that holds the signal above the switching transition voltage while feedback is present but doesn't extend the fall times by so much that you lose synchronization. This might be very difficult to do though.
That brings up why not just AND feedback and interrupter and feed that into gate drive input and just hold enable HIGH with a pull up. It should still transition HIGH to LOW as normal but with no feedback going to the AND gate there may not be a LOW to HIGH initialization.
You could pass raw interrupter to Enable instead of using pull up and this should provide the oscillation startup ping like normal. I think this would work as the normal state is no feedback signal and a LOW to HIGH on the Enable line causes an oscillation ping which starts feedback.
So if my train of thought is correct then a replacement for the D FlipFlop would be an AND gate to synchronize feedback and interrupter signals and feed raw interrupter to Enable as normal.
Registered Member #42796
Joined: Mon Jan 13 2014, 06:34PM
Location:
Posts: 195
if this is the circuit you are talking about then it will not work
the waveform will look something like this F _____──__──__──______──__â”
€â”€__──______──__──__──___ I ____
_─────────______─────â
”€â”€â”€â”€_______─────────____
1 _____──__──__─_______──__──__â
”€_______──__──__─_____ O _____──__â
”€â”€__─_______──__──__─_______──_
_──__─_____ so you will have hard switching so no synchronization
a flip-flop is used because it transfers data present at D pin on a low to high clock transition, the same happens with CLR pin. By holding D high all the time and controlling RST with the interrupter signal a constant HIGH will be present at output when interrupter is high and when the interrupter goes low the output will go low only on a low to high clock transition aka synchronization
Aha, I see now, the on time of the last pulse in the train isn't transfered. Thanks a ton for the detailed explanation!
My coils have all been overengineered to eat hard switching so I haven't needed the interrupter synch, but I'd always wondered if there was a smaller footprint and lower parts count alternative.
It looks like even if you found a scheme of discretes and/or gates to do what we want it would end up being more complex and parts heavy than the flip flop.
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.