-
#14: version 2, COMPLETED
01/10/2026 at 21:03 • 0 commentsPlasma Toroid Version 2 is complete. You can even buy an assembled board!
![]()
Here's the full schematic. You'll probably need to open in a new tab and zoom in.
What's Changed from V1?The new canonical home for this project's design files is a Codeberg Repository.
Here's an overview of improvements in Version 2:
Adjustable Current Limit
The new on-board buck adjustable current limiter is discussed in-depth in Project Log #12.
Since that log was written, I've changed the switch regular to a slightly-higher-power 5A module for folks who want to try running at higher voltage/amperage than USB 65W. I've also added solder jumpers to switch the knob to a "higher gear" adjustment range, or bypass the regulator altogether.
Soft-switch Enable Toggler
It's nice to shutdown the oscillator while the device is still connected to power. Using a soft-switch toggle rather than a physical switch also should (in principle) make the oscillator always start off when power is first connected. In practice the capacitor does seem to retain enough charge that there's some "stickiness" to the previous state.
This implementation was inspired by a helpful StackExchange post. Thanks, Endolith.
Prototyping was done on a standalone breadboard.
Input Power
I've re-added a TVS / reverse polarity protection diode (D5) at the power input. There's also now 100uF alupoly capacitors used throughout the board, where previously I'd tried to exclusively used ceramic SMT caps. These through-hole alupoly capacitors are soldered to the underside so a sleek topside appearance is preserved. More bulk capacitance at the power input makes oscillator and arc starts much more consistent and stable.
Simplified Arc Start
Version 2 uses a simpler high-voltage flyback. Full details are in project log #13.
One thing I've discovered is the polarity of the HV output really does matter. One polarity of primary winding works magnificently at ionizing the xenon, but the other struggles. I think the proper configuration is first-pulse-negative but it's been a bit confusing to 100% match the schematic and pinout of the HV transformer, so do your own tests.
The final transformer selection ZH1052-1(H) is oriented for high galvanic isolation, and even has a wire lead suitable for a striker!
Aesthetic Changes
The new version is planned for black soldermask PCBs, rather than the fancy transparent soldermask stackup of version 1. If you fab it in transparent soldermask I'm sure it'll still look great, but I didn't go nuts optimizing the precise trace routings as an aesthetic concern.
Indicators are now using neutral-white and sky blue LEDs, plus red for overheat alarm. The overall vibe is more "alien technology". I know blue LEDs are frequently abused but trust, me it looks great.
The BoM has been updated for a sleeker control knob, and I've designed a printable potentiometer cover for even cleaner aesthetics.
Monolithic support print
Version 1's support structure was designed as collection of flat-printed parts, assembled together with heat-press inserts and machine screws. This was a compromise design meant to avoid quality limitations of the Ender 3 I'd been using, along with a vague notion of flat-pack shipping.
The updated design is a single monolithic 3d print. I've upgraded to a much more modern printer and no longer suffer from degraded quality/reliability on tall, spindly parts. A unified monolithic print skips an entire assembly step and permits a curved face for the heatsink shroud. The PCB attaches to the support structure with thread-forming screws so heat-press inserts are no longer needed.
Refining the Oscillator Core
The oscillator core is almost unchanged!
Upgrading to adjustable current control meant I could convert the gate bias control knob to a set-and-forget trimmer potentiometer.
MOSFET gate resistors have been upgraded to much more robust 1020 "wide" components rated for two watts. I'd spent ages chasing overheating with the dual 2125 resistors in v1, thinking it was some kind of flaw. However when at last I actually calculated expected gate current from gate charge and switch frequency it was obvious that the gate restors really need to be >1W devices. The irony is the gate resistor was explicitly called out as "2W" in BacMacSci's original schematic but I apparently hadn't taken the rating seriously.
Mosfet selection: unchanged.
I did a whole series of tests investigating different driver MOSFETS. My interest was focused on Infineon's IPB320N20N (D2PAK) and IPD320N20N (DPAK, smaller) based on a tip sent in via email, claiming they could run cooler. Their spec sheets were compelling and it seemed extremely plausible.
I pursued the smaller DPAK fets for a while but they couldn't quite dissipate enough heat. Perhaps if I'd run three in parallel it'd work, but that was getting a bit goofy. IPB320N very nearly took home the crown, but there was an odd little issue. With my existing IPB17N25 mosfets, setting a bias voltage just higher than the threshold for starting oscillation resulted in a near-perfect duty cycle for maximum drive power. This allowed all throttling to be done by the current limiter. However with the IPD320N, getting maximum drive power required first increasing the bias voltage to oscillation start threshold, then reducing bias a bit for best duty cycle. This was unsuitable for a set-and-forget bias voltage.
I did many more searches for good parts, but no other candidates came close unless I made a switch to GaN or SiC. That was a change I wasn't going to pursue since suitable parts were much more expensive and switching characteristics are different enough to likely need multiple rounds of prototyping.
So in the end, my mosfet selection was correct the first time around. Nice!
Design for Manufacturability
I've decided to offer this board as a very small-run kit with the PCB pre-assembled. Multiple people fabricated their own builds of Version 1, and collectively it's much more efficient to do one batch of PCB fab and assembly rather than having every individual person procuring their own. This is intended to still be a project for electronics enthusiasts rather than mass-market consumption.
DFM in Version 2 is considerably better than Version 1 but still not perfect. A plurality of the components are either not substitutable or have less-than-commonplace specs. The MIC1557 oscillator in particular seemed like a good idea at the time, but for manufacturability I'd be better off with a traditional 555 and a few more support passives. It's a high candidate for replacement if I decide to do minor board revisions.
I've spent many rounds chasing down parts availability on JLCPCB, alongside "patch" release version updates for the substituted part numbers. I'll also still need to do a little bit of hand-assembly even for the production boards. Overall BoM cost is comparable to version 1, but version 2 is far more feature-rich.What's Next
Watch this space -- there's one more project update coming very, very soon.
-
#13: v2, pushbutton arc start that isn't terrible
09/20/2025 at 21:27 • 0 commentsThe pushbutton arc start in version 1 was cool, but also kinda trash. First, it was super inconsistent with starting ionization on a cold xenon globe, and often took several seconds of button-pressing to do so. Secondly, the subcircuit had a bill of materials that was way too expensive and was over-reliant on specialty components. The photoflash IC in particular both cost >6USD each (at quantity ten) and is an out-of-production last-time-buy part. The arc start module also needed two different specialty transformers and a particular model of gas discharge tube. Ridiculous.
Design for Production
What the arc start module actually needs to do is produce several kilovolts. A pulse of DC is fine, a few milliseconds of HV AC is fine, whatever.
It took me a weirdly convoluted series of steps, but the end solution is easy: a donkey-simple flyback converter using one of the same xenon trigger transformers as the last design.
![]()
MIC1551 (U1) is a spinoff from the classic 555 timer but reconfigured to generate a 50% duty square wave with only two external components. The values shown here run at ~43kHz which was chosen as an arbitrary ultrasonic frequency. This hasn't been optimized at all, and doesn't really need to be.
T1 is running as an autotransformer which is a bit unusual for flyback converters, but that's how the component is pinned so it's what we've gotta run with. I've done quite a bit of searching for other candidate transformers, but there's very few which are designed to withstand such a high output voltage in a compact package.---------- more ----------Here's the scope, zoomed in to one pulse:
![]()
Yellow is mosfet gate, purple is mosfet drain. With a transformer turns ratio of 1:10 that's theoretically 5kV+ of output, which roughly corresponds to the maximum arc length I can draw.
Toroid ignition is 100% reliable with this design. It works every single time, and it works no matter where on the globe I touch the HV output.
Running 1A @12V can create a hot and sizzling continuous arc. If there's nowhere to arc to, the output instead produces distinct corona discharge and a strong smell of ozone. For the plasma toroid striker I'll be limiting the entire module to something like 300mA input, which is plenty to create a couple milliseconds worth of HV from the energy stored in the 100uF capacitor.The board is very generously spaced for such a simple circuit.
![]()
Ok, but what's up with the footprint at the north edge clearly designed for a totally different transformer? Well...
A goofy path to get here
During development of plasma toroid v1 I tested using a generic "arc lighter kit" to start ionization. See example listing photo:
![]()
It didn't work well at all, so I abandoned the line of inquiry. Only later did I realize I missed something very obvious: I needed to tie one of the transformer secondaries to the toroid driver's ground. Having done that, it became a fully reliable ignition method.
Obviously I didn't want to just ziptie this piece of tat on to my PCB, so instead I set to re-implement their circuit. Here's a handy reference schematic from Quartz Components![]()
The transformer is an inscrutable black potted cuboid with primary, feedback, and output windings. The primary and secondary irregularly emerge from the potted block as thin wires coated with an enamel that's basically impossible to solder through. BJT D880 uses the feedback winding to self-oscillate. Based on measuring output inductance I estimate a primary:output turns ratio of something like 1:65. These transformers are available all over aliexpress for very cheap, but it took me ages to track down the actual part number as XR000425 from shenzen yuandongan electronics.
The specific D880 BJT isn't available from US vendors. For my test implementation I chose a BJT that seemed probably close-enough.
My trial board did oscillate and produce a mediumish high voltage, but way less than what I needed. Changing values of the feedback resistor didn't help much.Asking myself "what problem am I actually trying to solve here?" lead to grabbing breadboard, a same-footprint mosfet, and a 555 to drive with a fixed duty cycle.
![]()
which worked quite a bit better, starting the toroid reliably.
So I spun a new PCB, now using the MIC1551 timer. This version was very zappy. The grey not-square thingy is a printer cover / hold-down bracket to secure the transformer block to the board using screws (instead of a ziptie or glue).
![]()
So zappy that if the outputs where too far away to arc, the transformer would instead breakdown either internally or through the insulation+air where the wires emerged, causing immediate destruction.
I could obviously ramp down the power or run at a lower duty cycle or something, but to be honest a design based on the "arc lighter" potted block transformer didn't actually fulfil the goals of "design for manufacturability". Its angel-hair leads were incredibly annoying to solder and I really don't want to say "search aliexpress for a part which looks kinda like this" in an assembly BoM.
Another round of searching for suitable transformers lead me right back to the specialty xenon trigger transformer I'd been using originally. Funny thing is I'd completely misremembered the ZS 1052-S (and friends) as being in the "not recommended for new designs" lifecycle, but nope, it's an active part which is reasonably priced. Good news is I already had some on-hand to test with.
That's how I ended up with the bodge-job shown earlier in this post.
Thanks for reading. Next up: further refinements of the toroid oscillator core. -
#12: v2, current control
09/20/2025 at 19:52 • 0 commentsAfter a year away, I'm returning to this project. It's time to come back and fix the deficiencies of Version 1.
The Problem
Version 1 of the plasma toroid controlled drive intensity with a potentiometer that adjusted oscillator mosfet bias voltage, which in turn changed the switching duty cycle. This isn't a great method of control. Changing the duty cycle introduces a variable phase delay which is harder to tune for. Also, since the drive is a sine wave running a low duty cycle leaves the mosfet in an intermediate half-switched state for longer, which isn't great for efficiency. Finally, low duty cycles would often result in loss of oscillation if the plasma was extinguished for any reason.
The better method is a dynamic high-side current limit.I'm accomplishing this with a buck converter based on TI's "Simple Switcher" line of ICs, specifically LMR14030SDDAR. This chip is a monolithic buck converter with integrated mosfet, and it really is simple to implement. It's also capable of running at up to 97% duty cycle which is perfect for a low minimum dropout. Here's the reference circuit from their datasheet:
---------- more ----------![]()
This is a perfectly normal buck converter topology. Most buck converters are designed to hold a fixed output voltage -- in this case, the ratio of resistors Rfbt and Rfbb create a voltage divider. Voltage at the pin FB is compared to an internal 0.75V reference, and the switching duty cycle is adjusted accordingly.
But we don't want a fixed output voltage. Instead, we want to measure the device current, and if the drawn current is too high we want to reduce the output voltage until current falls to the desired limit.
The Solution
Here's my circuit:
---------- more ----------INA139 (ic U2) is a current-sense amplifier. It measures the voltage drop across the shunt resistor R3 and outputs a small voltage, with gain set by the combined value of R5 and RV1. This voltage is fed back to the feedback pin of the buck controller IC. The small capacitor C6 adds some low-pass filtering to reduce oscillation, plus some noise rejection.
If the measured current is low, a correspondingly low voltage is produced by U2 and the gain-set resistors. As a result the buck controller thinks it needs to raise the output voltage and increases the duty cycle (up to the 97% maximum). If the measured current is high and U2 outputs a higher voltage than the FB pin internal ref of 0.75v, the buck controller reduces the duty cycle until equilibrium is reached. RV1 being a potentiometer makes this current limit adjustable.
I'm leaving in my messy notes about trying to work out component values to make this transfer function do what it's supposed to. Seems like a good illustration of the design process -- these circuits don't come fully-formed from pure inspiration. These component values will probably still change!On The Bench
![]()
Although I had some initial befuddlement due to soldering the controller IC on backwards, the circuit worked perfectly. I'm able to fully and smoothly control the allowable current all the way from USB-PD supply max down to below the minimum needed to sustain the toroid. This control method is much more stable and robust than shifting the mosfet bias voltage. Hooray!
I didn't start testing this module directly with a plasma toroid driver board. Initial basic functionality was verified using a li'l 12V peltier module as a load -- it's the closest thing I had on-hand to something purely resistive.Here's the scope view:
![]()
Yellow is the buck switch, purple is the feedback voltage, blue is the output voltage (input is 20v). Switching frequency is about 500kHz. Everything is nice and well-behaved.
Next up: a better arc start. -
#11: Design deficiencies, and what you can improve
08/28/2024 at 00:49 • 2 commentsI'm considering this project Completed, at least for the time being. I'm incredibly proud of what I've created -- every design goal was achieved, and it looks even better than I'd dared to hope.
However, this is far, far from perfect. If I were to continue this project, I have a real hit-list of what could be improved.Overall System
The biggest issue is that controlling drive intensity by adjusting mosfet feedback bias voltage is janky and unstable. A proper system would leave a bias voltage set with a trimmer, and use high-side limiting on the primary input current for primary drive control. I realized this kinda late in the design process, and wanted to reach "done" rather than do another round of prototyping.
Also, having a breakout board for the USB-PD trigger module is pretty inelegant. Having a trigger module on-board would be better, but when I started this project I was having trouble finding a suitable IC with decent availability in the US. Several folks have since suggested good candidate ICs.MOSFET and driving
A straightforward error is that the gate-drive resistors have been undersized. The design shown in the video uses two 10-ohm 1206-size resistors in parallel (per mosfet), and they get incineratingly hot if there's no ionization/plasma to load the circuit. For the published release version, I increased those to a pair of 1-watt 2010-size resistors which should hopefully fare a bit better.
I probably ought to be using an asymmetric resistor / diode pair on the gate pins. Almost wish I'd investigated that sooner since the footprints are already there, but, hey, like I said I'm declaring this project Done.More generally: I'm convinced my mosfets are running hotter than they really ought to be.
I still don't feel like I have a sufficiently deep understanding of mosfet switching behavior, especially when driven from a sine-wave rather than a proper square wave. Using two parallel mosfets for the final version was a callous attempt at reducing heating. In prototypes, heat was observed as being heavily dependent on how much current I was drawing and that made me hope that parallel would help, but I also should have known that I was looking at switching losses rather than anything Rds(ON) related. I did some quick math before going parallel which made it seem promising, but like I said there's aspects of mosfet switching that I'm still learning.
EDIT: After initial publication, I decided to de-solder one of the two mosfets from an earlier prototype. With only one remaining mosfet, heating was much worse. This vindicates using dual mosfets.
The most-correct version of this circuit would probably use an actual mosfet driver IC, with something like a PLL as part of a feedback loop. Would be lovely to have both a nice square-wave drive and finely adjustable phase offset.
Using something like a GaN mosfet might also perform a lot better!Arc Start
For the first start when the glass vessel is room-temperature cold, button-press arc-start reliability isn't as good as I'd like -- sometimes it does take several tries to get the toroid running.
This particular arc start method is too expensive. If I were designing for even small-run production, it'd get a major overhaul.
Both arc-start transformers and the GDT are all what I'd call "kinda-specialty components" which isn't ideal even if their BoM cost is modest. More seriously though, the flyback controller chip LT3420 is both expensive ($6.75/ea at qnty 10) and has limited availability. The good news is that the fancy chip is probably completely unnecessary. I initially thought I might be using the advanced functionality like keep-charged and the "done" signal, but the system I ended up with would probably be just fine with a fixed-duty-cycle flyback charger.
There's a lot of different ways of getting pushbutton arc start though. I know one person who reports success using a cheap aliexpress "arc ignitor" module with one leg of the output tied to ground and the other pressed up against the globe. Another promising idea which was suggested to me would be to have an entire autotransformer-style secondary winding driven by the primary inductor, which would offer the benefit of automatic start!
I'll continue to edit this post as I think of more improvements, and as improvements are suggested :)EDIT 2024-09-19
Matthew Sylvester assembled this project from the PCB, and let me know that they experienced arcing underneath the xenon flash trigger transformer. I've increased the clearances, and released the changes as v1.03
Double-checking against IPC 2221, the clearances still aren't "enough" but it's the best I could do without a redesign of the entire arc start section. -
#10: AND IT IS DONE
08/25/2024 at 22:31 • 0 commentsThanks for following along :)
-
#9: Black FR-4 and transparent soldermask, by PCBWay
06/01/2024 at 21:33 • 1 commentFor the final build of this project, I wanted something special.
![]()
Typical PCBs use a olive-green fiberglass core, layers of copper, and a (traditionally green) soldermask layer to protect the copper and define areas where solder/component pads should stick. This board instead has a dyed-black fiberglass core and a transparent soldermask layer. This means that all traces are visible as their natural copper color, which is delightfully high-contrast against the black substrate. Component pads and other areas left uncovered by the transparent mask are plated (ENIG) gold.
This order of circuitboards was (partially) Sponsored by PCBWay! They covered about 60% of the cost of these boards, and I paid the remainder out-of-pocket.
There's very few photos out there of real PCBs made using this stackup, so I'm taking the time to write out a review.
(Transparency: being partially sponsored will likely bias my opinions, but I did also pay enough to feel like I have skin in the game. I have not given PCBWay any editorial control and they will not have seen this review prior to publication. Photos have been lightly post-processed and are broadly representative of how things look irl under good lighting. An order number [visible on the unpopulated board] has been blurred out for privacy.)An in-depth look
This is going to be mostly photos.
Here's how the board looks straight out of the packaging
![]()
That looks really good, yeah??
The copper is a matte tan, not shiny at all. ENIG gold finish looks like it always does, and creates a neat kind of sandy two-tone.
For scale, the smallest traces on this board are 8mil with fairly generous spacing and the finest pitch component is 0.5mm. Components are D2PAK through 0603.![]()
There's a sort of white ghostliness visible around the copper areas -- I'm guessing due to the transparent soldermask being not pressed quite as deep into the fiberglass. Under certain kinds of lighting, a faint weave texture of the fiberglass can be seen.
![]()
I absolutely love the way that text looks in copper. (This example has a character height of 1.2mm.) Super sharp! There's also a subtle dimensionality visible due to the thickness of the copper and the drape of the overlaying soldermask.
![]()
Text in copper+soldermask also looks nice and sharp (although is some slight cruft visible in the notches on the N and W). Contrast is more variable than copper-only as lighting changes, as the gold catches ambient light and reflection differently than the semi-gloss transparent mask.
The grey silkscreen ink is a bit mis-aligned from the other layers. This photo above shows it especially clearly: take a look at the holes on the left side and the silkscreen circles are distinctly off-axis. Silkscreen alignment has been better on my other PCBWay boards, which makes me wonder if the layer required some kind of hand-alignment that's less automated for their higher-order-volume stackups. Not an actual problem but definitely a bit unfortunate.
EDIT, ADDENDUM: My PCBWay sponsorship point-of-contact was perturbed by the soldermask alignment and raised it as a possible issue with their production team. In email correspondence with one of their customer service reps, PCBWay stated that while white silkscreen is aligned by machine, other colors (including grey) are aligned manually and "there will be +/-6mil offset which can not avoid. QC is based on the standard that the silkscreen are not on the pad."
Their Advanced PCB overview lists silkscreen offset as ±2mil, which is presumably representative of their alignment standards for white silkscreen.![]()
Here's the board backside with its large ground plane. They grey silkscreen QR code is plenty legible against the black FR4. (White silkscreen would be more typical against black, but I thought grey would be a bit more elegant and am happy I made that choice.) The bottom silkscreen is equally mis-aligned as the top.
Grey silkscreen over a copper fill is nice and high-contrast, but readability on the "12V" marking has suffered a lot where I placed text overlapping the edge of a trace.
![]()
An art layer in soldermask on a copper plane also looks pretty good. The "sky-guided, 2024" text is 1mm high and 0.2mm stroke width -- I personally wouldn't go much smaller than that for soldermaskmask graphic strokes over copper. I didn't try gaps in mask over FR-4 because I didn't think it would be usefully contrasting.
Throughout this board, I used the KiCAD plugin "rounded traces" to make the traces curved and flowy rather than angular.
The Cost
Here's the catch though: this board stackup was much more expensive than a standard PCB.
Instead of the quick-turn "Standard" service, getting the black FR4 and transparent soldermask requires the "Advanced PCB" board fab. This run of five 190x145mm boards cost about nine times as much as if I'd purchased a normal stackup (not including the fixed costs of shipping).
As I mentioned up top, sponsorship covered a big chunk of that, but the sponsorship took the order from "nonviable" l;to "still quite expensive". Also as a note, the web order form under-estimated the cost until PCBWay Sales was able to review and give me a final quote. (Their sales team seems distinct from the representative I've been in contact with for sponsorship.)
I suspect that the cost differential would be a lot lower had I been ordering 50,000 boards (or maybe even just fifty) instead of a mere five. I don't have insight into what that pricing might look like.
I also don't know how the costs would change for a much smaller board area.
PCBWay sent a full test report for the board -- the "send me a test report" boxes on the order page were checked by default, and un-checking them didn't change the initial cost estimate so I figured why not.![]()
Here's just one page of the extensive test report, plus the two included section boards,one of which was a slice embedded in resin! Quite honestly I didn't need any of that testing -- this board isn't even high-speed enough to be impedance control. I think this is all standard practice for the "advanced" fab service.
Which all raises the very important question: as currently priced,Who is this stackup meant for?
If I'm correct that the cost differential would be a lot less with a large-volume order, that suggests a commercial client might find this stackup a lot more worthwhile. However, I don't imagine there's not a lot of production-quantity products which would benefit from a highly ✨aesthetic✨ PCBs. Enthusiast computer motherboards, maybe? But in most cases, I doubt companies would want to pay even a modest premium for this kind of prettier board.
And on the other hand, I can see a lot of hobbyists who would be super-excited to have a project board (or limited-market production run) looking this swag, but for whom the high cost is totally prohibitive. I would be willing to pay maybe 3-4 times as much for this stackup in select projects, but not 9x as much.
Perhaps this kind of pricing would be fine for convention badge PCBs, which could make use of the unique look while also being both physically smaller and ordered in large enough quantity to offset setup cost.The tooltip for the Black FR-4 option on the PCBWay order page suggests the opacity could be useful for some LED applications, but that seems a separate concern from buying black FR4 + transparent mask for visual appeal.
US-based PCB fabricator OSHpark also sells this stackup (under the delightful name "OSHpark After Dark"), but their per-square-inch pricing model would have made a board as large as mine even more expensive. They're also slower. If your board is a lot smaller, you might consider them as an option.Final Thoughts
I absolutely love the way this board looks, and I'm glad I'm able to use it for my project.
I also wish it were more accessible for other hobbyists. My hope is that PCBWay could figure out a way to get this stackup out of the super-bespoke Advanced PCB production pipeline, since a lot of that functionality is completely tangential to "pcb looks really neat". My suspicion is right now there's the catch-22 of it's too expensive for folks to order, and lack of orders makes it stay an expensive specialty product. Perhaps some kind of special promotion could break the deadlock?
I should also emphasize, these thoughts on pricing are based on the pretty limited sample of this specific large, prototype-quantity board. If that pricing is wildly anomalous, then these hot takes are probably off-base.To wrap things up, here's one more photo:
![]()
Being hyper-conscious of "I want to make this board look exceptionally good" did make laying out and routing the PCB take much longer than it would have otherwise.
I'm happy I took the time to do so. It does look exceptionally good!
Coming in the next update: project showcase, wrap-up, source files, and thoughts for anyone looking to make a toroid of their own. -
#8: A Unified Board
05/27/2024 at 18:08 • 3 commentsIt's been a busy couple of months behind the scenes -- this project is basically finished! I'll be breaking the final few updates into a couple posts, while I wrangle loans of camera equipment for the beauty shots.
Circuit Unification
Taking the different prototyped modules and banging them together:
![]()
(you might have to click to embiggen)
I've paralled the mosfets for better heat dissipation. This doesn't help quite as much as one would like (since a lot of the losses are switching and not resistive), but it does help. The mosfet gate resistors are also paralled since they get quite hot before the arc is struck. I'm not sure why that behavior is occurring -- if you know, drop me a line!
The 4.3V zener diode (D5) for regulating gate bias is a carefully chosen value for this particular mosfet and circuit. Cranking the knob full-clockwise guarantees oscillations start, but doesn't set the bias so high as to cause excessive power draw and heating. The use of full knob range also makes adjustments more precise and controllable.A bank of four 33pF capacitors is a balance between heat distribution and board space. While the board itself has plenty of room (see below), I ran into some odd layout constraints due to things like the under-board heatsink mounting holes. The cabs do get pretty hot before the arc is struck, but are plenty cool during operation.
There's a total input bulk capacitance of 30μF (shown as two caps on main power and one before the 12V regulator). Less bulk capacitance caused occasional power supply brownout/shutdown.
The oscillation sense coil from Update #6 has been brought on-board, shown in the dotted area within the main driver section.
Arc start is basically the same as discussed in Update #7. I keep waffling on whether a GDT value of 300V or 470V is preferable here -- 470V may be shown, but keep your mind open.
The only real new addition is the overheat sense. There's nothing special here; it's almost exactly per the datasheet for the TMP708 IC. The one bit of oddness was having to add a small decoupling capacitor in parallel with the programming resistor, because the overheat IC was placed as close as possible to the mosfet drains and it was picking up EMI. Debugging that was fun -- while poking around with scope probes, I noticed that merely touching the sense pin fixed the problem.
Here's a delightfully goofy photo from a prototype board, showing a 0603 capacitor bodged directly on to the IC pins:![]()
Programming a trip value of ~56C was about right for raising alarm when the mosfet case temperature hit 100C.
PCB Design
An overview:
Details might not be super visible at this far out a zoom, but here's the overall layout. Power input and status LEDs are far left, overheat sense is lower center-left, main driver is center (with knob lower center-right), and arc start is far right. The heatsink is mounted to the board bottom, outline indicated by the cyan square around the center area.
Most of this layout is relatively low-density. The minimum size was constrained by needing to fit a heatsink underneath which could accomodate a 40mm fan. There's a handful of components which are 1206-sized even though 0603 would have worked, simply because that larger size looked better.
The rounded traces were made using the KiCAD plugin "round traces".
MOSFETS were placed on a large copper fill, stitched to the heatsink on the bottom with a lot of thermal vias. The thermal tab on the mosfet is attached to Drain (and not GND), so rather than having truly a massive cut in my backside ground plane for the backside Drain copper pours, I split the drain pours into smaller sections with cruciform GND traces.
The TMP708 overheat sense IC was put within a small cutout on the thermal fills, to maximize thermal coupling. A SMD thermal jumper would have been "better" but I didn't want to add it to the BoM.The main driver section in the board center is arranged to prioritize visual symmetry. One detail here is that each test point has a paired ground point to make probing easier. (This project is really sensitive to interference from large loop areas on probe leads!)
A cutout under the primary capacitor bank isn't directly for high-voltage creepage/clearance reasons, but mostly to allow for picking up any excess solder balls or flux residue and is recommended by TDK as best-practice for higher voltage SMD caps.The far right side of the board hosts the arc-start portion of the circuit. It's mostly notable because I didn't give quite enough clearance for the high-voltage arc start fly-wire contact (J1, visible inside the yellow circle near the top). It's prone to arcing over to the primary inductor. I don't think that's going to hurt anything but it doesn't feel great -- conformal coating or a dab of hot glue might help.
I am going to open-source this project as soon as I finish this round of update blogs.
Physical Design
Since the start, a key goal was to have a finished product that didn't look like a workbench prototype.
Here's what I came up with:Rather than the "layer cake" of most folk's designs, I'm going for something more reminiscent of early 20th century engineering.
Early drafts included a lasercut or printed no-finger-poking safety shield over the electronics, but I decided it looked terrible. Please don't touch the zappy parts.
Components are printed as individual flat pieces, and attached together with heat-press inserts and M2 screws. While a single-piece print would be possible, using multiple parts allows stronger layer-line orientation and avoids print head jump moves which can visibly affect surface quality.
The blocky section in the front-right is a shroud to cover the heatsink (mocked up in blue), and an attachment point for the (brown) 40mm fan. The USB-C power supply module screws down to two of the four semi-conical mounting points.
While I'd have preferred to have the USB-C-PD power supply integrated on to the main board, availability for USB-C-PD trigger ICs in the is currently terrible within the United States. I've decided to use the Adafruit HSUSB238 power delivery dummy breakout as a standalone module. It's a touch larger than some others out there, but it has mounting holes. A standalone board does allow plugging a USB cable in at closer to desk surface height, which in my opinion is a bit nicer.Coming in the next update: an excessively fancy circuitboard, sponsored by PCBWay.
-
#7: how to ionize xenon: the arc start module
03/23/2024 at 19:24 • 0 commentsThe electromagnetic fields generated primary inductor aren't strong enough to ionize neutral xenon gas into plasma. Once any infinitesimal part of the gas is ionized, those charged particles almost instantaneously cascade into their neighbors and the whole globe lights up. But getting a bit of gas to ionize in the first place is the tricky part.
The "standard" way to do this (as demonstrated by BacMacSci) is to forcefully twist the glass globe against the induction coil. The triboelectric effect causes miniature "static electricity" shocks which are enough to kick off ionization. Alternately, one can use some kind of external high voltage source like a handheld tesla coil zappy gun.
Either manually twisting the globe or using an external device is a bit dissatisfying to me. I wanted to integrate arc start directly into the device, activated by the push of a button.
This log is going to be longer than most, because it's been an adventure.---------- more ----------An external zap?
My first attempts were using cheapo "arc lighter ignition modules" sold on aliexpress or amazon. (I won't bother linking, because those listings seem to have a half-life of like six months and dead links suck.)
![]()
zap
BigCliveDotCom has a great video explanation into how this circuit works. I think it could be best described as "aggressively cost-optimized.
Holding the contacts against the globe could occasionally start ionization, but that was rare. Most of the time it did nothing, regardless of positioning.
This was a dead end.
So I thought, well, xenon flash tubes for cameras and strobe lights and stuff exist. How do those work?Triggering xenon flash lamps
BigCliveDotCom also has a video on how xenon flash lamps are fired, titled "Unwinding a tiny 6kV xenon trigger transformer". He's phenomenal at concise explanations of how circuits work and this is no exception -- I'm going to embed it here, because his description is better than what I can muster. The circuit diagram and explanation is from about 1:53 to 4:30
The shortest version is that a small capacitor is charged to the neighborhood of 300V, then rapidly discharged through the primary of a high-turns-ratio transformer. This creates a very high voltage pulse on the transformer secondary, which is fed to a fine wire wrapped around the glass of the xenon flash tube. The high voltage causes capacitive coupling to the xenon through the dielectric of the glass, strong enough for ionization.
Here's my implementation:![]()
It's the same circuit BigClive drew. No magic here.
Component D2 is a thyristor, an old-school cousin of the BJT. When a voltage is applied at the gate it latches closed until current flow drops below a low threshold value.Getting 300 volts
There's lots of ways to get 300-ish volts from low-voltage DC, and most of them are some variant of flyback converter.
Properly engineering a flyback converter is a bit of a rabbit-hole, and these days it seems like most commercial applications are in low-volt-dc switch-mode power supplies. I decided to take the shortcut of using the LT3420, an IC purpose-built for charging photoflash capacitors.![]()
This is very nearly the same circuit as the reference design in the datasheet. I'm even using the same flyback transformer that they recommended. (That's one thing I love about hobby electronics -- device manufacturers actively do what they can to make implementation of their parts as easy as possible.)
There's a couple of deviations from reference, though. R1 is a current limiting resistor; since I'm only charging the teeny 47nF trigger capacitor and not a larger flashtube cap, I can store the needed energy in a "slow"-charged onboard 10uF cap rather than the transformer drawing directly from the 12V rail (and correspondingly needing a 12V regulator with a higher current rating).
The DONE pin goes high when the IC thinks that the transformer output has been charged to the nominal voltage. My design intent here was to use this signal to automatically fire the triggering thyristor when the threshold was reached. Normally DONE has a pullup, but I decided to get overly clever and pull it up to the CHARGE line so that in theory it could only go high when the arc start button is pressed.JP2 is a cuttable jumper trace, since I figured that I might have issues with thyristor trigger reliability and need to try external trigger signals. This ended up being a prudent bit of defensive design.
Putting the 300V charger and the trigger circuit together, here's what we get:
![]()
A downside to this approach is parts availability and cost. Xenon flashtubes for photos have fallen out of favor so these have become "specialty components". In particular, the LT3420 costs like $8 each, and the transformers together are about $7. That might not seem like much but it adds up when buying prototyping quantities of even just five or ten pieces.
Circuitboard
As previously, this board was sponsored by PCBWay! Their product quality is, as always, solid.
![]()
The actual contact point for the xenon globe is a little spring-steel AAA battery terminal, extending to the upper-right. A little bit of of hand forming is required, but the springy contact is great for gently conforming to the globe's surface. A wire wrapped around a cylindrical flashtube may be traditional, but trying to wrap around a spherical glass vessel is misery.
Unfortunately, I made no less than four different errors when laying out this board:- There was supposed to be a 12V regulator on board, but it's unpopulated (the large footprint at the board's bottom). This was because I made a last-minute decision to swap the regulator I had on order from one with a DPAK footprint to a smaller SOT89, and I neglected to update the layout.
- The Pin 1 marker on the (octagonal) flyback transformer is on the wrong side -- I had primary and secondary backwards. Probably a mistake in the "alternate pin assignments" options in KiCAD.
- The footprint of the flyback transformer is also wrong -- the spacing is too wide. I suspect when laying out the footprint I was entering pad edge-to-edge dimensions as if they were center-to-center.
- The thyristor (D2) had gate and cathode pins swapped. This last was fixable with a bit of bodge wire excellence:
![]()
With the board assembled and the bodges all bodged, did it work?
Well... kinda.
First iteration: almost working, but not quite
The flyback was successfully able to charge the trigger cap up to >300V. Quite a bit higher, in fact -- the voltage was going literally off the scale that my scope would display. The charge control IC should have automatically ceased charging when the output hit a voltage threshold programmed by a feedback resistor, but in practice I think it was charging the 47nF trigger cap fast enough that the IC control got kinda wibbly -- in a usual application it'd have caps which would charge on the order of several seconds, not a few milliseconds.With full charge, I could manually short the high side of the trigger cap to ground, and produce the sharp-edged pulse to drive the trigger coil. Doing this could sometimes cause the xenon globe to ionize, but it was very inconsistent.
Getting the thyristor to switch consistently was a minor ordeal. First there was the aforementioned "gate and cathode were wired backwards" problem. Then there was a bit of a wild goose chase seeing if an external 555 timer circuit could produce more reliable results than the DONE signal from the IC. Eventually I determined that the thryistor could switch just fine when the board was sitting on the bench, but when I tried to actually use it to strike the toroid arc, the driver's primary inductor was causing electromagnetic interference so intense that the thyristor was firing prematurely. Replacing the 10kΩ pulldown resistor with a 1nF bypass capacitor helped a bit, but it was still never able to get the xenon to ionize.
Second iteration
I had to take a step back and ask myself, "what problem am I actually trying to solve here?" The goal was to discharge the capacitor in a sharp pulse when it reached 300-ish volts. A DIAC could do this, but that would be yet another specialty component with terrible selection and availability. Alternately someone named Pagurja has a youtube video titled "The simplest xenon flash circuit" which demonstrates forcing a BJT into avalanche breakdown to create the fast pulse required. This is apparently a secret-sauce way of creating ultra-fast pulses for things like oscilloscope bandwidth characterization, but I wasn't excited by the idea of relying on semiconductors pushed so far outside of their designed and characterised regimes.
The breakthrough came when I saw this note from Lewis Loflin at bristolwatch.com describing using two ne-2 neon bulbs as part of a trigger circuit.![]()
I figured, heck, why not use some kind of spark gap type thing as the trigger switch itself?
Web searching things like "specific voltage spark gap" etc lead to my discovery of a device called a gas discharge tube arrestors. These little guys are perfect -- it's a sealed tube with some magical gas mix inside, specifically designed to break down and conduct at a particular voltage. GDTs are generally used for circuit protection; they sit at near-infinite resistance unless a high-voltage transient comes down the line, at which point they function as an overvoltage crowbar. They even come in tiny surface-mount packages, at prices of well under a dollar.
I should give specific credit to this 2021 post on the EEVBlog forum from a user named Gyro. They link to a PDF copy electronics hobbyist magazine from way back in 1978, presenting a circuit that's conceptually nearly identical to what I need!
Here's what the revised trigger section looks like:![]()
And here's the actual GDT, bodged in to the board in place of the thyristor. It's only a 1812-sized SMD part!
![]()
I double-stacked two of the 47nF capacitors during earlier testing, and didn't feel any strong need to change back to a single cap.
Results
Here's the scope waveform measured at the "300V" test point.![]()
Exactly as intended. The capacitor is charged up by the flyback, then automatically discharges through the GDT when it hits 300 volts. Not pictured here is the corresponding high voltage pulse on the trigger transformer secondary. This happens at a frequency of 35Hz, so you get that nice clicky-buzzy noise reminiscent of a stun gun arc, but much quieter.
Zooming the timescale wayyyyyy in, here's a single discharge:![]()
The pulse time is under 5ns. Not gonna set any records, but pretty quick.
Video demonstration:As you can see, from a cold turn-on it takes a few bursts of the zappy to get going -- the xenon seems a bit harder to ionize before it warms up. Once the globe is warm, the module can strike an arc almost instantly.
In the final build this module will be integrated as part of the single driver PCB.
WHAT'S NEXT
Getting the arc start module working is a big deal. All of the individual subsystems are functional and core design milestones have been hit:
- Initially achieving the plasma toroid effect.
- Refining the driver to run continuously without melting.
- Tuning a plasma donut that can be either eerily stable, or intriguingly mobile.
- Powering the driver via USB-C (which I haven't yet described, since I'm using an off-the-shelf USB-PD board which Just Works in a delightfully boring way.)
- An indicator light for whether the circuit is in oscillation.
- Pushbutton arc start.
Now I gotta put all the pieces together. I'm certain the result is going to be gorgeous.
See you next time! -
#6: status LED, galaxy brain style
03/22/2024 at 16:20 • 1 commentSince a key goal of this project is to run standalone -- no o-scope, no bench PSU, no amperage panel meter -- it's crucial to have some sort of indication of whether the circuit was in oscillation or just sitting idle.
Overall power draw reliably reflects the circuit's state. When not oscillating, there's near zero draw -- just LEDs, leakages, etc. While running the draw is more like 2-3 amps, and can be reduced down to as little as ~1.2A by lowering mosfet gate bias.
The normal approach
I had initially planned to use the pretty typical current monitoring method of a differential op-amp measuring voltage across a low value shunt resistor. Since I'm looking for a threshold current indicator rather than a continuous analog signal, the op-amp is fed into a comparator, against a reference voltage.
![]()
Yes, this diagram is kind of sloppy, but you won't need to linger on details here anyway. If the text is unreadable due to aliasing you can click to embiggen.
The TSM102 IC seemed like a neat combo-wombo of packaging two comparators, two op-amps, and a 2.5V reference all in one. It's also relatively inexpensive and can run off of a 40V Vcc. Purpose-built current monitor ICs also exist, but I didn't necessarily want to add a 5V regulator just for one chip, plus I thought the extra op-amp/comparator channels might also be useful for other functionality.
As mentioned in the previous project log, PCBWay sent me a sponsored board and solder stencil! Assembly was quick and easy. Thanks, PCBWay!Well?
It didn't work.
Output voltages from the op-amp do move in response to changes in the drive power, but not in any way that's intended. I suspect that the choice of 25mΩ shunt resistor is just way too low for this application, and is getting drowned out by common-mode influences and amplifier limitations. Using 130kΩ resistors as part of the op-amp network was definitely a warning sign that things might be getting a bit too off-road. 45mV seemed an ok enough differential when I thought a 1.8A current threshold would be good, but lowering that threshold down to 800mA / 20mV certainly didn't help. (Or maybe I'm just not very good at this, and there's a fundamental design error that's gone unnoticed.)
That's all ok though, because I had a better idea.---------- more ----------Going Wireless
While testing out the (still-not-yet-documented) arc start module, I had to start up the main driver circuit and decided to not even hook up my scope leads for monitoring, since I figured that the primary inductor oscillation was electromagnetically noisy enough to be perceptible without a direct connection.
And that's when the inspiration hit.
Just by wrapping a clippy test lead into a li'l coil, there was more than enough inductive coupling from the primary to wirelessly light an LED. In fact, this video is of my second test of this method -- the first time I used a raw 5mm LED which burned out within a few minutes from being overdriven. (The LED shown is an "E-Cell" breadboard-friendly LED + resistor, sold by DFrobot. Super handy prototyping aid.)
This video also shows how ghostly the toroid looks with daylight filtering in through living room windows. Very different from the dimmed-room beauty shots!
IMO this monitoring method is better than a fixed yes/no threshold on current draw, since the LED brightness visibly changes in proportion to the drive intensity. It's also a much more direct measurement of what the coil is actually doing.
Feeding an inductive pickup directly into an indicator LED is either the cleverest or the most knucklehead way of solving the status monitoring problem. Probably both at the same time, really.
I can design a PCB coil trace as part of the finalized circuitboard assembly, for zero added cost. That brings the subcircuit component count from ten (including one not-recommended-for-new-designs IC) all the way down to a mere two.
Nice.
Coming next, we finally grapple with push-button arc start. -
#5: Version 0.3 is calm, cool, and collected
03/11/2024 at 04:20 • 6 commentsRevision 0.3 of the induction driver creates a plasma toroid that's stable and controllable, and does so without overheating.
I'm closing in on a finalized version of the driver. Soon, both the induction coil and driver circuit will be unified into a single monolithic PCB.
This round of prototyping was...Sponsored by PCBWay!
Entirely to my surprise, a representative from PCBWay contacted me with an offer to cover the costs of a batch of boards.
![]()
Four boards! Three solder stencils!
(This project log will cover design updates to the induction coil and driver. The other two accessory boards will be featured soon, but there's still a few circuit details I need to refine first.)Some stuff I like about PCBWay:
- Fast. Eerily fast, sometimes.
- Inexpensive!
- Their instant quote functionality can be super handy for design planning, even before a board layout is finished. For example, it's great to be able to test out possibilities for things like "how much would it cost to make the board 50mm wider? What if I want to use 2-oz thick copper?" Etc.
- Quality is solid. Admittedly I haven't plumbed the depths of BGA or wafer-level-packages yet, but for everything I've done so far I've been totally happy with PCBWay boards.
- If there's something malformed in the manufacturing file, a member of their production team will email asking for clarification of design intent. This has happened to me twice!
- I like they that sponsored me. I'm saying that very sincerely, not just because the monetary windfall is nice (although it really is). It's incredibly endearing that PCBWay is seeking out and financially supporting small, independent projects like this one, and not just big-name makers and youtubers that already attract 100k+ eyeballs.
Assembly
Just like previous versions, solder paste was smeared across the laser-cut stencil, components were placed with tweezers, and the board was reflowed on a budget hot-plate.
![]()
(Kapton tape was used to keep the board in place during assembly, but not during reflow.)
Minor soapbox time: I spent quite a while as an electronics hobbyist being intimidated by surface-mount parts. Secret is, SMD assembly (at least for relatively large components) is faster and easier than strip-board and through-hole. This is especially true with a solder stencil and hotplate (or presumably toaster oven) reflow. Through-hole parts are decidedly obsolescent, and these days most interesting ICs are only available in surface-mount. For this project, using an actual PCB is also hugely important for minimizing parasitic inductances.
![]()
With a larger inductor coil (115mm center-span x 12mm width) and some neater connecting wire bundles, the assembly looks pretty slick!
Here's what changed in driver version 0.3:---------- more ----------No more overkill SiC MOSFET
I'd been considering replacing the Qorvo UJ4C0750 - series SiC mosfet for a bit now. Some of that motivation was due to their cost (at ~$11 each), but performance characteristics drove the change.
I'm now using the Infineon IPB17N25S3-100 "OptiMOS" Si mosfet instead.
For this application there were a few key parameters, at least as I understand them:Drain-Source voltage: Never seemed to rise above 200V in either simulation or on the bench. Absolutely no need for the 750V-rating of the UJ4C0750. The IPB17N offers 250V, which is plenty.
Drain Current: Needs to be anywhere upwards of 6 amps or so. Again, the new mosfet has plenty of headroom at 17A.
Gate Charge: Without a proper high-current mosfet driver, it seems worthwhile to minimize the amount of charge that needs to be shoved in and out of the gate pin before the device switches. The UJ4C's 37nC is ok, but the IPB17N has a gate charge of only 14nC.
Switching speeds: Longer switching times could result in greater switching losses. Delay and rise/fall times on the IPB17N are as little as a couple of nanoseconds, compared to low tens of nanoseconds for the UJ4.
Output Capacitance (Coss): Steve Ward stresses the importance of C(oss) being fully discharged before switching, and discusses the (possibly substantial) heating due to capacitively stored energy. The UJ4C has a quite low C(oss) value. I almost certainly overemphasized C(oss) as a parameter, which is a big part of what lead to using the UJ4 in the first place.
On-resistance: The UJ4C has an quite low On-resistance of only 58mOhm. It's a bit higher for the IPB17N at 85mOhm, but not that much higher. At the low operating currents of 2-3 amps, it hardly makes a difference.
Basically, parts in the OptiMOS series look super good enough, at about a fifth the price. A lot of the offerings in Infineon's CoolMOS product line also look quite compelling by the numbers, but Steve Ward warns about that SuperFET type device often having unexpected energy losses. I'm increasingly unsure how much I trust that (especially given the CoolMOS datasheets explicitly list C(oss) energy figures that are rather low), but for the moment I'm using the OptiMOS -- and a lot of that decision was fueled by seeing someone else's highly successful build using parts from the OptiMOS series, as I'll discuss in a moment.
Unfortunately, the device footprint of the IPB17N wasn't compatible with the UJ4C, otherwise I'd probably have just bodged other design changes on to the version 0.2 board.
Lesson learned: do not be seduced by new hotness semiconductors unless I have a specific reason to need their characteristics.The magnificent plasma toroid of Humxn
Recently, a youtube user by the name of Humxn posted a video of their own plasma toroid. Not only is their build cool and clean, they also do a fantastic job of walking through both design details of their (very tidy) circuit, as well as a number of implementation tips and tricks. Humxn also showcases a beautifully stable toroid that can float perfectly in the middle of the xenon globe.
I'm borrowing several design elements directly from them:
- Use of the OptiMOS series mosfet, rather than the CoolMOS I'd been eyeing.- Using a zener diode to create a voltage reference for the gate bias, rather than just a raw voltage divider from the supply line (which destabilizes if voltage sags due to hitting supply limits). As soon as I saw the zener, I mentally facepalmed at not having considered it sooner.
- Understanding that reduction in driver power helps the toroid float and stabilize. I had assumed that floating was due to high drive power and lots of convection from plasma heating. I'd had it exactly backwards!
- Adding a mm or two of separation between the drive coil and the glass globe (my new inductor revision has a bit of blank space between the inner diameter and the copper trace).
- A greater appreciation for current-control as a way of manipulating toroid behavior.
If you're at all interested in building your own plasma toroid machine, the Humxn video is absolutely essential.Testing Results
Video is at the top of this log :)
Here's the scope traces with the xenon going full donut.
As previously, the yellow trace is gate, purple is drain, and blue is gate bias (note the different y-axis scale). Those waveforms look basically ideal (and I think some of the remaining wigglyness on the drain is due to mediocre scope probing, since I only have so many hands to use pokey leads and not clips). The shape on the drain trace does morph a bit in response to changing drain voltages.
The L1 input choke inductor value was increased to 6.8uH. The previous 2.2uH inductor had been chosen low in an attempt to constrain circuit power draw, but tbh I really should have just planned on setting limits on the supply side.
Adding a 1nF rf-bypass capacitor to the bias voltage network does indeed smooth out that waveform. (Also, turns out I had once again been seeing spurious wigglyness due to an over-large loop area with the ground clip.) Replacing the bias voltage divider with a zener reference also makes striking the toroid quite a bit more stable and reliable. I'm currently using an 8.2V zener but will swap it down to 4.7V soon, to make better use of the full potentiometer range.
I'm realizing that everything I said previously about the using a bias smoothing cap and increasing the impedance between bias and gate-drive causing "runaway oscillation" was total nonsense. Upon further testing, it now seems like the Miniware PSU just dealt poorly with rapid changes in current demand if the circuit ramped to full oscillating power too quickly. This was easily fixed by adding more bulk capacitance at the circuit's supply hookup.Thermals
Manageable! Running the stabilized toroid at 25-30 watts, the hottest part of the whole project is the globe glass.
![]()
Increasing the trace width of the PCB inductor has helped a lot -- temperatures stayed <50C, or even cooler when the toroid was running at low power.
Performance of the new mosfet is similar to the previous driver iterations. At low power, temperatures (measured infrared at device body) are <60C. Running at full 60-watt power the mosfet still gets probably too hot; 120-130C. I may end up using two mosfets in parallel in the final version. It's definitely not ideal to run at full power for very long (and it seems to offer very little visual benefit anyway), but tightening the envelop of maximum supplied amperage does seem to make the arc start a bit less reliable, when hitting the regulation limit causes the supply voltage to be lowered.
The under-board heatsink has also been mounted and re-mounted several times now, and it's possible that its thermal interface layer isn't making very good contact.
There's a teeny hot-spot on the gate drive resistor. I'll plan on two parallel 1206-size resistors for the next version.
When the toroid isn't ionized, there's quite a bit of heat buildup on the high-voltage side of the (now) four-capacitor primary bank. It's hard to tell for sure, but I think the copper itself is getting hot rather than the capacitors (especially since the gate side of the cap bank stays cool). I'm wondering if parallel-plate capacitive coupling to the ground plane might be causing dielectric losses in the fiberglass? I genuinely don't know if that conjecture makes any kind of sense -- please let me know if that's totally implausible.
Here's my favorite photo from this project so far:
![]()
When the toroid is stabilized it looks, honestly, unreal. A little ring of light that floats perfectly centered, still and silent. The dynamic range of the camera can't quite keep up with the plasma's brightness -- IRL it looks more nebulous, more ghostly. (It also plays havoc on camera auto-focus.)
NEXT STEPS:
A key design goal is running the toroid standalone off of USB-C. To that end, I'm implementing built-in power monitoring to indicate whether or not the circuit is in oscillation, rather than needing to read PSU loads or oscilloscope waveforms.
I also very much want to have push-button start for the plasma ionization, rather than the (kinda crude) method of twist-rubbing the globe against the coil.
Unfortunately, neither of those features is working quite yet.
Stay tuned.

What's Changed from V1?




































As previously, the yellow trace is gate, purple is drain, and blue is gate bias (note the different y-axis scale). Those waveforms look basically ideal (and I think some of the remaining wigglyness on the drain is due to mediocre scope probing, since I only have so many hands to use pokey leads and not clips). The shape on the drain trace does morph a bit in response to changing drain voltages.
