Welcome
Username or Email:

Password:


Missing Code




[ ]
[ ]
Online
  • Guests: 70
  • 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!
Mathias (41)
slash128v6 (52)


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 »   

question about oscilloscope and basic terms

Move Thread LAN_403
Physics Junkie
Sun Nov 11 2012, 03:47AM Print
Physics Junkie Registered Member #7267 Joined: Tue Oct 16 2012, 12:16AM
Location: Detroit, Michigan
Posts: 407
Hi all. I am currently working on building my second tesla coil and so I have a few elementary questions. First questions are regarding the driver. The coil I am building now is a drsstc and I'm using Steve Ward's controller 1.3b. I also bought a 100mhz 2channel oscilloscope to help me with this project and all future stuff. So my question about the driver is: what are some important parts to probe on the driver?. I've started with probing the interrupter signal at both the interrupter side and pin 5 of 74hc14 and everything is nice there. Would just like to know what other parts of the controller should be probed and what I might expect to see.

Second question is regarding some basic terminology that I see everywhere which I'm confused about and cannot seem to find any explanations for. Forgive my ignorance as this is only my second tesla coil build and I am still learning a lot and trying to understand everything. The term "cycles" is what I am confused about. I see the term "cycle", primary cycles", "RF cycle" used a lot. Do all of these terms have the same or similar meaning? Or how might they be different?. When I look up the term RF cycle, I only find information of duty cycle.. is RF cycle and duty cycle the same thing?. Next regarding primary cycles and cycles, I often see phrases like "the coil operates best at 6 primary cycles" or "had MMC failure pushing 10 cycles". All of the information I come across has lead me to believe that these terms are related to BPS. If anyone can enlighten me on this It is much appreciated.

Thanks,
Harry
Back to top
Ben Solon
Sun Nov 11 2012, 04:02AM
Ben Solon Registered Member #3900 Joined: Thu May 19 2011, 08:28PM
Location:
Posts: 600
all of those terms mean the same thing. one cycle is one period of oscillation in the primary circuit. one period is 1/coil frequency, so if your coil runs 100khz, one cycle will be 10uS long. the number of cycles run is dependent of how long your interrupter's on time is set to. the more cycles you run, the larger the ring up in current is based on the primary impedance. take a look at the characteristic rf envelope for a drsstc's primary current. on the rising edge of the envelope you can see that each cycles amplitude is greater than the last.
Back to top
Steve Conner
Sun Nov 11 2012, 08:02AM
Steve Conner Registered Member #30 Joined: Fri Feb 03 2006, 10:52AM
Location: Glasgow, Scotland
Posts: 6706
Back in the old days, hertz were called "cycles per second".

Duty cycle is something different. It refers to the percentage of time that a pulse waveform spends in the "on" condition. For example, a square wave has a duty cycle of 50%.
Back to top
Physics Junkie
Sun Nov 11 2012, 11:09PM
Physics Junkie Registered Member #7267 Joined: Tue Oct 16 2012, 12:16AM
Location: Detroit, Michigan
Posts: 407
The first coil I built, a sstc mini runs cw or duty cycle of 1(100%). Still learning about lower duty cycles for pulsed systems. This might also sound like dumb question , can a drsstc run in CW? From most of what I have read I see all sorts of duty cycles used, most of which are <20%, but most 5-10%.

Ben, thanks for the clarification. That explanation was great and helped me understand it better, much appreciated. I had a feeling they were all similar.
Back to top
HV Enthusiast
Sun Nov 11 2012, 11:23PM
HV Enthusiast Registered Member #15 Joined: Thu Feb 02 2006, 01:11PM
Location:
Posts: 3068
For your typical DRSSTC design, you cannot run a DRSSTC in CW. You would certaintly blow it up as thats a tremendous amount of power you are running. For example, if you're coil was operating at 10kW and 5% duty cycle, if you were to run that at CW you would be exceeding 200kW!!!!

Plus, recall that DRSSTCs have a large storage capacitance. During the ON time, almost all the energy being driven into the DRSSTC primary is coming from the electrolytic dc bus capacitors. During the OFF time, these capacitors are then charged up by the line voltage. If you were to run at very large duty cycles or CW, you would simply need an incredible amount of capacitance and/or a very low impedance line input which just isn't practical.

SSTCs which are designed for CW operation generally have much higher impedance tank circuits and therefore don't require such a large input capacitance (energy storage) or low impedance input drive.
Back to top
Physics Junkie
Mon Nov 12 2012, 12:25AM
Physics Junkie Registered Member #7267 Joined: Tue Oct 16 2012, 12:16AM
Location: Detroit, Michigan
Posts: 407
Ahh okay yes that makes sense, thanks for reply. Seeing as there are many settings you can make for an interrupter (pulse width, pulse repetition frequency, burst, one shot, etc...) are some settings more necessary than others, a must have, or just personal preference?
Back to top
Ben Solon
Mon Nov 12 2012, 02:05AM
Ben Solon Registered Member #3900 Joined: Thu May 19 2011, 08:28PM
Location:
Posts: 600
it really just depends of how elaborate you want the spark display/sound to be. the simplest controller will have a bps and pw control, while the most complex will be midi enabled with mode switching between settings. i'd get comfortable with a simple controller first,but it depends on your comfort level. you can do bps and pw with 2 555's and adding one more will give you burst mode.
Back to top
Physics Junkie
Mon Nov 12 2012, 03:30AM
Physics Junkie Registered Member #7267 Joined: Tue Oct 16 2012, 12:16AM
Location: Detroit, Michigan
Posts: 407
Working with 555's is where I am at now. The audio and MIDI interface stuff is beyond me at the moment, but something I hope to accomplish down the road. The interrupter I made for my mini sstc works well (same interrupter I used to check that my drsstc controller is receiving a proper signal via fiber optic) but it is only a single 555 timer and the mini sstc coil is really sensitive to it because the value for the potentiometers I used were excissive, although the spark effects are really cool wink. For the drsstc I'm building now I plan on going with Steve Ward's interrupter with burst mode as it looks simple enough for me at my experience level, and easy to build.

Regarding my first question about scoping areas on the controller, for example, the out pins on the UCC and the N and P channel mosfets. I'd think there would be an importance in scoping these areas, yes? So far as I can tell, the controller powers up just fine, everything's receiving proper voltage where it should be, no heating in any areas, except the 5v regulator which I can fix with a resistor at the Vin. Fiber optics work as mentioned before, the LED brightness changes as I mess with the interrupter. Also, I am unsure as how to check that the OCD will work? This is an area that I am still learning to understand as to how it works, I get the concept of what it is supposed to do, but still learning HOW. Maybe something that is testing once I am ready to fire up the coil. Since I am unsure as how to check the controller, I was going to just wait until I put together the bridge, mmc, and primary, then just probe the igbt gates, with controller attached of course. Still havn't decided if I want to wind up CT's for probing the bridge or just buy some (lazy). Any suggested methods for scoping controller's?

Thanks for replies, been very helpful.
Harry
Back to top
Physics Junkie
Sat Nov 17 2012, 10:08PM
Physics Junkie Registered Member #7267 Joined: Tue Oct 16 2012, 12:16AM
Location: Detroit, Michigan
Posts: 407
So I just got done constructing Steve's Interrupter with Burst Mode and I checked everything out on the scope. BPS and Pulse Control both work perfectly. I was having problems with the Burst Mode last night. The 555 was getting incredibly hot. It wasnt working at all either, scope was telling me that there was no signal from the Burst 555. I found that there was continuity between some pins on the Burst mode 555 where there shouldnt be, so I fixed that but that didnt change anything, still no signal. So I decided this morning to redo the whole Burst mode part, and this time I put an LED between the Out pin and the switch (555Out->resistor->cathode-anode->switch). The 555 no longer gets hot at all. But I get some odd waveforms that I have no idea if they are normal or not. It might just be my noobishly putting an LED Between the Burst 555 and switch.

This probe is clipped to the cathode, waveform seems normal enough to me.. Same as just probing the Out pin..

20 374


The probe is now clipped to the anode of the LED, switch is turned off.

1353189860 7267 FT146416 Out


This is same waveform as above, zoomed in.

1353189937 7267 FT146416 Zoom


When I turn the switch on, this is what happens (I have to zoom WAY out to see this).

1353189975 7267 FT146416 On


The only indication that I have is the LED I put before the switch, It blinks when I turn the switch on, and by turning the potentiometers I can change the rate of the strobe and the brightness.

1353189975 7267 FT146416 Led


Since the LED blinks, I'm assuming that that burst mode works properly. I only put it there in the first place because I though that when the switch was turned on it was causing power to flow through to the 555 and making it get hot, and I liked the idea of a blinking LED indicator. I turned out to be wrong when I removed the LED, no heating occured, and no more ugly waveforms. The LED must not allow the signal to travel from cathode to anode properly, which I didnt know but I tried it anyways... I'll try and see if I can use the blinking LED indicator somehow. Not quite sure what to think of the Flatline when I turn the switch on but I can only assume it works just fine now.
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.