Electronics > Beginners

When you follow the schematic but it doesn't work

(1/11) > >>

lordvader88:
I'm reminded of 2-3 times I tried to make a C-R oscillator w/ a BJT and maybe an op-amp once, and they never worked. I didn't try changing much, but it never worked. I bet the schematics were fine tho.

Then 1 utuber, an old radio guy, with proper schematics from an old book, I tried 2-3 little circuits and they never worked but his did. With those it was probably the BJT or JFET not being quite right, and not getting the loop gain right.



Don't you hate it tho when you follow a schematic and it doesn't work and you don't know why ? (time to re-try some)

bd139:
yes very annoying. This is what got me interested in the design side of electronics if I'm honest.

I built some stuff from Practical Wireless magazine in the early 1980s that didn't work. I learned pretty quickly that a lot of the designs out there are total shite and nothing is trustworthy. The design may have worked for one person once. In some cases, I don't think the design ever worked even if the author said it did and in other cases it was actually misprinted and you'd find out two months later in a footnote on a page after you had recycled the thing for parts anyway.

Putting effort into learning why things don't work and actually looking at a design and going "huh?" has been a valuable set of lessons though.

To note, a lot of stuff we were taught at university didn't work either!

Finding stuff that should work but doesn't and making it work again is the best analytical training you can get I think.

lordvader88:

--- Quote ---To note, a lot of stuff we were taught at university didn't work either!
--- End quote ---
You mean schematics out of text books ?

bd139:
Yes out of textbooks and as advised by the lecturers. It's almost as if they'd never built the things  :palm:

GeorgeOfTheJungle:
We're well into the internet era, and a few years back many unis still didn't teach javascript, students can't even tell apart JS from the DOM, write async code, and barely know what's a closure if at all. If at least C were mandatory curriculum you could be assured they know well what's going on under the hood. But no. Java has been/was mandatory instead. Is it still? (IDK). On the plus side, it's no more any longer everything Windows, all Windows and no more than Windows.

Navigation

[0] Message Index

[#] Next page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod