Have you checked uModules and such?
I didn't know of them until now.
Remember, I am at the hobbyist level, with very little practical knowledge. So, if I need a DC-DC converter, I go to Digikey, Mouser, my local component sellers, and do a search on each. (When I know a component or type details, I can do a search on eBay, but I'm well aware of the prevalence of fakes and substrandard clones.) I do a web search for the problem at hand, and trawl discussions here, and project logs e.g. on Hackaday, to find practical solutions. I don't usually do an appnote trawl then, because I'd be too easily distracted; they're actually pretty hard to search for when you have a particular problem at hand.
These things are biased with an electric field while hot, then cooled below Tc, "freezing in" the field -- making an electret.
Yes; it's the electrostatic equivalent of a magnet. I was trying to say that even when the behaviour of something looks mathematically simple, it tends to be rather easy to use those in very complex ways. This means that while "rules of thumb" are useful, they never capture all of the behaviour, and often there is a completely unintuitive (from the "rule of thumb" point of view) way to use the same material or phenomena. You can see this in some clever circuits, where jellybean components are used for odd purposes.
Prince Rupert's drops is another good example. The way they're made causes huge opposing internal stresses; i.e lots of potential energy stored in the atomic structure. The bulb end of the glass drop can withstand a blow from a hammer, because the internal stresses are even greater, and easily withstand the additional stress of a hammer blow. But a small ping on the tail end creates a wavefront of collapsing opposing forces, and the entire thing explodes.
One of the very first simulations I wrote, modeled
Morse copper. (It is a very simple model of the interactions between copper atoms.) I had a a block of atoms in a perfect lattice, and another as a liquid (simulated to move the atoms to random locations, but keeping the total energy constant). Unfortunately, I miscalculated their location by about one interatomic distance, so the blocks basically intersected. This means some atoms were way too close to each other, corresponding to either insane temperatures or ion bombardment. To my amazement, after about ten thousand simulation steps, the simulation stabilized with a drop of molten Morse copper inside a solid lattice, with the entire solid lattice vibrating at wavelengths much longer than any dimension in the system, and was stable like that for tens of thousands of time steps. That was not what one would expect from such a simple model, and it took me quite a while to find out exactly what and why it happened.
To me, it felt like the first time I wrote a program to draw the Mandelbrot set on screen. (Or rather, colored the outside of the Mandelbrot set depending on the number of iterations.) It is just a dozen or so lines in any programming language with floating-point number support and a putpixel() function, but the images are mesmerizing.
Dimensional analysis is such a useful sanity check.
So very true.
I think it was a high school physics teacher, who showed that keeping units with the quantities when applying some formula, ensures you use the correct units. For SI units, this is especially useful, because all units can be expressed in base SI units, and there are very few numeric constants to remember or look up. I've caught my own errors countless times that way. It even helps locate the errors. When you calculate a velocity, and get a result with units
[kg m/s], you know you made a booboo somewhere; probably missed a mass term.
Dimensional analysis sounds fancy and advanced, but at the core, it is about dropping the quantities, and applying the formula to the units only, to see what units pops out as the result.
It isn't that useful in electronics, unless you add conservation of energy. The SI unit for energy is joule,
[J] =
[W s] =
[V A s] (where
W is watts,
s is seconds,
V is volts, and
A is amperes). So, when a component drops 1 V at 1 A current for one second, it spends 1 J of energy. Some of that will do something useful, but because no component is perfect, at least a fraction of that energy will be converted to heat. One watt-hour of energy is 1
W h = 1
W · 60 · 60
s = 3600
J, so one kilowatt hour is 3.6 million joules.
When you examine the system at a point in time, instead of energy you examine power, usually in watts
[W] =
[J / s] =
[V A] -- but note that the voltage and current units here refer to that particular instance in time, and it does not hold for example for average or RMS voltage and current (see e.g apparent power vs. true power for the difference).
Many of the debunking videos Dave has posted are based on this simple approach. You take the input voltage and current, or power, or available energy; estimate the efficiencies of the components (they're pretty well known, and you can always do min/max estimates based on known technology limitations); and you'll find out what is possible and what is not.
This is so basic, simple, and utterly robust way to examine devices, ideas, and formulae, that I think it is a crime to nowadays not teach this in high schools.