On 06/18/2013 11:16 AM, Tony Duell wrote:
let me ask you a simple quesiton. You have to
flash an LED at about 1Hz
-- the exact frequency is not important. Nor is the duty cycle (within
reason). You also have a suitable supply line (so no need to consider 3
terminal regualtors, etc)
Now, off the top of my head there are 3 obvious solutions (there are many
more too, of course ) :
A discrete component multivibrator -- 2 transsitors, 4 resistors, 2
capacitors, LED
A 555 astable --555 Timer IC, 3 resistors, 1 capacitor (2 if you are a
purist and want to decouple 'control voltage), LED
An 8 pin microcotnroller, 1 resistor, LED
Which of those 2 you consider to be the simplest?
I count 3 choices.
EWrr, yes...
None of the above. A UJT, capacitor and resistor with LED would be
Can you still get UJts? I've not seen them i nthe catalogues for
years. But I rmmemebnr the TIS43.
simpler than your 2-transistor gizmo. A DIAC (or
other suitable 4-layer
diode) would be even slightly more simple. Perhaps a nitonol wire
comprising a thermal switch might even be simpler.
A pair of slugged relays? A motor, cam and switch?
You don't need nition wire. Car turn indictors over here used to use a
themal switch to flash them, a wire that expanded and operated a switch
contact.
Of course there were low-votlage filament lamps with a bimetalic strip
inside operated by the thead of the filament...
Now, let's talk about what's most flexible (i.e. bang for the buck).
The 8 pin MCU can generate *precise* pulses with a *precise* duty cycle.
I speciifcally said that was not importat.
Heck, you might even be able to get rid of the resistor if you employed
some PWM on the output, such that average maximum ratings on the LED
weren't exceeded.
I feel tyhat is a bad idea. If the microcontrolelr locks up you could end
up burning out the LED.
EDN (ISTR) had a column on this subject last year concerning replacing a
555 with 8 bit MCUs. It was a lot of "it depends", as I recall--and no
clear winner.
Indeeed...
Actually, the 'friendly votlage levels'
could be a minus-point in that it
is likely a USB interface conenctor is connected directly to some large
and complex IC, while an RS232 port will almost certainly invlove a
simple buffer IC or two. So that if you accidentally connect too high a
voltage to the cable, in the case of USB you have a lot of work to do, in
the case of RS232 it's one cheap IC that will take a few minutes to
replace (even if soldered in).
Interesting--I've seen more EIA 232 line receivers zapped by ESD than
USB devices, but that could be because 232 has been around longer.
I have only eve seen one set of RS232 buffers zapped. That was in an HP
9000/200 machien (I forget if it was the 9816 or 9817). The serial port
weas totally dead. What was odd was that not only were the 1488s and
1489s dead, so was the serial chip (oddly for a 68000 machine it's an
8250). But nothing else./
I suspect httaht RS232 has been used to drive much longer cables than
USB, unscreend cables, etc. I you used USB i nthe same way you would be
repalcing complex ICs all the time.
But who lives in a world where a single person writes
both sides (host
and client) software for a given USB application?
That is anotehr reason to dislike the thing!
-tony