3 ms·
The insight that the only serious constraint is R1 << R2 is clearly the point of the lab exercise, and it might be missed entirely in numerically searching the
by ncmncm 5y ago
The insight that the only serious constraint is R1 << R2 is clearly the point of the lab exercise, and it might be missed entirely in numerically searching the space. But adding a flip-flop to the output to divide frequency by two yields an exactly 50% duty cycle, regardless of R1/R2, so you may then optimize for some other quality. The right question to the TA would have been about which of the specs mattered more: duty cycle? power consumption? stability against variation in parts, temperature, supply voltage, noise? absolute frequency? parts count? parts cost? Each different answer yields a different design.
Nowadays a microcontroller might be best, e.g. if it meant you could get away without the resistors and capacitors.
- docfort 5y agoIn my experience, knowing what parts of a schematic can be ignored for understanding the core functionality is super important as a designer. Then I’m better able to compare two implementations that purportedly do the same thing on many different axes. Especially if I’m doing integrated circuit design as opposed to discretes. It also helps to build up conceptual complexity. For example, the post mentions briefly avoiding giant resistors for stability. Good enough rule to start out with. But eventually understanding how an op-amp does its thing using feedback is critical. Especially when comparing IC-equivalents, since now you also need to consider area as another metric of comparison. Brute force optimization avoids all of this learning, which is good in the short term (get the lab done) and bad in the long term (how to think about circuits).
- jason_s 5y agoor you throw away R1 and connect R2 between C and OUT.