From: John Larkin on
On Sat, 10 Nov 2007 19:55:00 -0600, John Fields
<jfields(a)austininstruments.com> wrote:

>On Sat, 10 Nov 2007 14:40:51 -0700, Jim Thompson
><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>
>>On Sat, 10 Nov 2007 11:42:31 -0800, John Larkin
>><jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:
>>
>>>On Sat, 10 Nov 2007 11:57:19 -0700, Jim Thompson
>>><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>>>
>>[snip]
>>>>
>>>>Now please present us with your "solution" with component names and
>>>>values and I'll simulate it side-by-side with my design.
>>>
>>>
>>>I rarely simulate. Design is the reverse of simulation. Design forces
>>>the desired results, so why simulate?
>>>
>>[snip]
>>
>>So you've been converted to the Bob Pease school of hand waving ?:-)
>>
>>My POV: Design puts the idea onto paper. Simulation proves that what
>>is on the paper really works. But simulators don't "design". In my
>>business, simulation "proof" is required for each and every process
>>corner, otherwise the customer doesn't "buy".
>
>---
>I used to be in Larkin's corner, defending "build and test" over
>"simulate", but after writing a few simulators to solve specific
>problems posed here on sed, which couldn't be solved, practically,
>any other way, I decided to lay down my wire-wrap gun until the
>machine worked in the computer.
>
>Then, along came wonderful, free LTSPICE.
>
>I've designed stuff using it which I never had to physically build,
>but which worked and which I got paid for, which is a joy.
>
>A feeling I'm sure you enjoyed before I did. :-)

An asynchronous circuit like this, and even moreso some of the others
that gave been posted, has internal delays and is subject to all
possible timings in the chatter zone. Spice can't really test all the
possible combinations of timings. You can generate a chatter
simulator, but you can't be sure its deterministic behavior represents
the real world of arbitrary timings. Complex async circuits can have
low-probability picosecond-wide windows of hazard.

John

From: D from BC on
On Sat, 10 Nov 2007 19:35:26 -0800, John Larkin
<jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:

>On Sat, 10 Nov 2007 19:55:00 -0600, John Fields
><jfields(a)austininstruments.com> wrote:
>
>>On Sat, 10 Nov 2007 14:40:51 -0700, Jim Thompson
>><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>>
>>>On Sat, 10 Nov 2007 11:42:31 -0800, John Larkin
>>><jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:
>>>
>>>>On Sat, 10 Nov 2007 11:57:19 -0700, Jim Thompson
>>>><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>>>>
>>>[snip]
>>>>>
>>>>>Now please present us with your "solution" with component names and
>>>>>values and I'll simulate it side-by-side with my design.
>>>>
>>>>
>>>>I rarely simulate. Design is the reverse of simulation. Design forces
>>>>the desired results, so why simulate?
>>>>
>>>[snip]
>>>
>>>So you've been converted to the Bob Pease school of hand waving ?:-)
>>>
>>>My POV: Design puts the idea onto paper. Simulation proves that what
>>>is on the paper really works. But simulators don't "design". In my
>>>business, simulation "proof" is required for each and every process
>>>corner, otherwise the customer doesn't "buy".
>>
>>---
>>I used to be in Larkin's corner, defending "build and test" over
>>"simulate", but after writing a few simulators to solve specific
>>problems posed here on sed, which couldn't be solved, practically,
>>any other way, I decided to lay down my wire-wrap gun until the
>>machine worked in the computer.
>>
>>Then, along came wonderful, free LTSPICE.
>>
>>I've designed stuff using it which I never had to physically build,
>>but which worked and which I got paid for, which is a joy.
>>
>>A feeling I'm sure you enjoyed before I did. :-)
>
>An asynchronous circuit like this, and even moreso some of the others
>that gave been posted, has internal delays and is subject to all
>possible timings in the chatter zone. Spice can't really test all the
>possible combinations of timings. You can generate a chatter
>simulator, but you can't be sure its deterministic behavior represents
>the real world of arbitrary timings. Complex async circuits can have
>low-probability picosecond-wide windows of hazard.
>
>John

You've posted the hazards of asynch..ummmm..I'd say 5x.
Now that persistence. :)


D from BC
From: D from BC on
On Sat, 10 Nov 2007 19:35:26 -0800, John Larkin
<jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:

>On Sat, 10 Nov 2007 19:55:00 -0600, John Fields
><jfields(a)austininstruments.com> wrote:
>
>>On Sat, 10 Nov 2007 14:40:51 -0700, Jim Thompson
>><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>>
>>>On Sat, 10 Nov 2007 11:42:31 -0800, John Larkin
>>><jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:
>>>
>>>>On Sat, 10 Nov 2007 11:57:19 -0700, Jim Thompson
>>>><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>>>>
>>>[snip]
>>>>>
>>>>>Now please present us with your "solution" with component names and
>>>>>values and I'll simulate it side-by-side with my design.
>>>>
>>>>
>>>>I rarely simulate. Design is the reverse of simulation. Design forces
>>>>the desired results, so why simulate?
>>>>
>>>[snip]
>>>
>>>So you've been converted to the Bob Pease school of hand waving ?:-)
>>>
>>>My POV: Design puts the idea onto paper. Simulation proves that what
>>>is on the paper really works. But simulators don't "design". In my
>>>business, simulation "proof" is required for each and every process
>>>corner, otherwise the customer doesn't "buy".
>>
>>---
>>I used to be in Larkin's corner, defending "build and test" over
>>"simulate", but after writing a few simulators to solve specific
>>problems posed here on sed, which couldn't be solved, practically,
>>any other way, I decided to lay down my wire-wrap gun until the
>>machine worked in the computer.
>>
>>Then, along came wonderful, free LTSPICE.
>>
>>I've designed stuff using it which I never had to physically build,
>>but which worked and which I got paid for, which is a joy.
>>
>>A feeling I'm sure you enjoyed before I did. :-)
>
>An asynchronous circuit like this, and even moreso some of the others
>that gave been posted, has internal delays and is subject to all
>possible timings in the chatter zone. Spice can't really test all the
>possible combinations of timings. You can generate a chatter
>simulator, but you can't be sure its deterministic behavior represents
>the real world of arbitrary timings. Complex async circuits can have
>low-probability picosecond-wide windows of hazard.
>
>John

I got inspired by that differentiator + schmitt invertor sketch of
yours.
The idea was to move the signal into the hysteresis levels.
I though I'd try doing the opposite..Moving the hystersis levels to
meet the signal..

Check out my hysteretic hairball! :O *
http://www.members.shaw.ca/chainsaw/SED/compsolution.jpg
569Kb

Notes:
* Top wave is the inverting input of U1.
(It's a cool waveform. 4 levels! :) )
* Prop delay is from a single device at less than 10nS.
* This can be a 1 chip solution with a fast dual comparator.
* I picked the LT1713 just because it's fast.
* The integrator + U2 could be replaced by some 'one shot' IC solution
* This circuit is not quite baked because I skipped on the math and
did best guesses on the resistor values.

With some tweaking, I think this might be a good circuit.

D from BC
From: Jim Thompson on
On Sat, 10 Nov 2007 17:44:09 -0800, John Larkin
<jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:

>On Sat, 10 Nov 2007 18:03:07 -0700, Jim Thompson
><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>
>>On Sat, 10 Nov 2007 16:19:54 -0800, John Larkin
>><jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:
>>
[snip]
>>>>>
>>>>>Your Sysreset sets Q high, but your sim starts with Q low. Why?
>>>>>
>>>>>John
>>>>>
>>>>
>>>>The default set-ups included FF initial conditions Q=0. If I uncheck
>>>>that box it starts, as would be expected, with Q=1.
>>>>
>>>> ...Jim Thompson
>>>
>>>Well, run that. It's more interesting.
>>>
>>>John
>>
>>Yep. It takes one cycle for the output to be correct.
>>
>> ...Jim Thompson
>
>
>It seems to work, but it's awfully convoluted. It would be, for me,
>like one of those things that I designed but that I can barely
>understand myself; there are too many possible states, and the dflop
>clock sometimes comes from the input, and sometimes comes from the
>input xored with the internal delay.

Think of the XOR as a device that is switched from being an inverter
to being a buffer. The switching does not occur while clock (input)
edges are present.

>And the input can chatter, or it

Does nothing after the first transition... it's an edge-triggered
flop.

>could be a single edge of either polarity. All those conditions have
>to be proven to work, and proving it is too much work.
>
>I avoid clever stuff like that, in hardware and in software. Sorry,
>but I prefer my first circuit, because it's a lot easier to
>understand.
>
>John

When I feel confused I drinks a glass of wine ;-)

...Jim Thompson
--
| James E.Thompson, P.E. | mens |
| Analog Innovations, Inc. | et |
| Analog/Mixed-Signal ASIC's and Discrete Systems | manus |
| Phoenix, Arizona Voice:(480)460-2350 | |
| E-mail Address at Website Fax:(480)460-2142 | Brass Rat |
| http://www.analog-innovations.com | 1962 |

America: Land of the Free, Because of the Brave
From: Jim Thompson on
On Sat, 10 Nov 2007 19:55:00 -0600, John Fields
<jfields(a)austininstruments.com> wrote:

>On Sat, 10 Nov 2007 14:40:51 -0700, Jim Thompson
><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>
>>On Sat, 10 Nov 2007 11:42:31 -0800, John Larkin
>><jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote:
>>
>>>On Sat, 10 Nov 2007 11:57:19 -0700, Jim Thompson
>>><To-Email-Use-The-Envelope-Icon(a)My-Web-Site.com> wrote:
>>>
>>[snip]
>>>>
>>>>Now please present us with your "solution" with component names and
>>>>values and I'll simulate it side-by-side with my design.
>>>
>>>
>>>I rarely simulate. Design is the reverse of simulation. Design forces
>>>the desired results, so why simulate?
>>>
>>[snip]
>>
>>So you've been converted to the Bob Pease school of hand waving ?:-)
>>
>>My POV: Design puts the idea onto paper. Simulation proves that what
>>is on the paper really works. But simulators don't "design". In my
>>business, simulation "proof" is required for each and every process
>>corner, otherwise the customer doesn't "buy".
>
>---
>I used to be in Larkin's corner, defending "build and test" over
>"simulate", but after writing a few simulators to solve specific
>problems posed here on sed, which couldn't be solved, practically,
>any other way, I decided to lay down my wire-wrap gun until the
>machine worked in the computer.
>
>Then, along came wonderful, free LTSPICE.
>
>I've designed stuff using it which I never had to physically build,
>but which worked and which I got paid for, which is a joy.
>
>A feeling I'm sure you enjoyed before I did. :-)

It took me MANY years to trust simulators. Initially even bipolar
device models were bad.

But I still "design" by first "sketching", even if the "sketching"
does use a schematic capture program... I'm faster that way, no
erasing... drag stuff around... such fun!

Then I simulate.

...Jim Thompson
--
| James E.Thompson, P.E. | mens |
| Analog Innovations, Inc. | et |
| Analog/Mixed-Signal ASIC's and Discrete Systems | manus |
| Phoenix, Arizona Voice:(480)460-2350 | |
| E-mail Address at Website Fax:(480)460-2142 | Brass Rat |
| http://www.analog-innovations.com | 1962 |

America: Land of the Free, Because of the Brave
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13
Prev: TL499A boost converter question
Next: PIC sanity test