>> In older (TTL) times such a small RC delay would have been
>> accomplished using a small RC integrator,

> Your statement makes no sense out of context. =A0Trimming large chunks of=
 what
> you are replying to is good, but it's also important to leave some contex=
t.

Black pots and not so obviously black kettles parade past.
Quoting without context can render  the response obscure BUT the
context is and was so immediately available and obvious and, in any
case, so inferrable, that few who are interested are liable to be
bothered by it.

I do agree that quoting some of the context is liable to be useful.

But, biting my tongue and trying valiantly to avoid inserting a "Duh",

> This of course is all obvious and well known, duh.

Vot is dis this which you refer to?
Is dis this der delay constant creation method, or der need for
quoting or summat else?
What one refers to is often more obvious to one than to others, as you
have just, effectively, finished saying.
This this is no more obvious in intent than that delay et al was.

Strangely:

>> To work around glitches and runtime problems I'd try to
>> implement the XOR using the gates in a single 74HC00 package.
>> Simulation may help here... usually implemented XOR gates are
>> glitch-prone due to the different propagation times through the
>> negated and straight paths. In this case, that glitchiness can be put
>> to good use after stretching it a little with a RC delay element, I
>> think.

Was about 100% clear in meaning and intent when I read it.
So

> Again, it's not clear what they heck you're talking about, but it sounds
> like a bad idea. =A0Using a XOR gate as a edge-to-glitch converter is rea=
lly a
> kludge. =A0Most likely there is a real solution available if you explain =
what
> problem you are trying to solve one or two levels up.

seems very strange.
One (whoever that may be :-) ) gets the impression, here as often
elsewhere, that you leap into the midst of threads like this without
having read the prior material, at all. His "kluge" is excessively
time honoured fwiw (not too much ;-) ), it's not his problem, he's
answering the problem, and in his next email he provides a standard
fully digital solution. On threads like this, assuming your
email-reader is capable of displaying the thread as a contiguous
sequence, it's often quite useful [tm] to read all that has been said
to date before adding one's gems of wisdom.

Whatever.


                R



>
>
> ********************************************************************
> Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
> (978) 742-9014. =A0Gold level PIC consultants since 2000.
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.