HELP! I have tried every way possible to UNSUBSCRIBE from this group, can anyone
help, the repeated attempts per the instructions on site have failed.....
----- Original Message -----
From: Alan Melia
To: hp_agilent_equipment@yahoogroups.com
Sent: Wednesday, November 11, 2009 6:16 PM
Subject: Re: [hp_agilent_equipment] Re: HP3325A Confusion Believe it or not...



Yes and in the sub-cable field ...."you cant "test in" reliability (quality)
".... it has to be designed in.

Alan G3NYK

----- Original Message -----
From: "J. Forster" <jfor@...>
To: <hp_agilent_equipment@yahoogroups.com>
Sent: Wednesday, November 11, 2009 9:44 PM
Subject: RE: [hp_agilent_equipment] Re: HP3325A Confusion Believe it or
not...

> When I was bulding spacecraft payloads, there was an axiom:
>
> You CANNOT inspect in quality.
>
> -John
>
> ===========
>
>
>
> >> Even in the "good ole days" there were mixups. I have found typos
> >> and such on schematics and other documentation, as well as an odd
> >> assembly error -- a capacitor marked 200 pf on one side and 160
> >> pf on the other. It should have been 160, but it was a 200
> >> causing incorrect behavior subtle enough that I didn't notice
> >> until I was calibrating by the manual. This was an 8555A,
> >> probably built in about 1974 with the wrong part!
> >>
> >> It's quite possible a TL610 was accidentally substituted for a
> >> '601, which would keep the reference of the following opamp
> >> (U38?) from being properly grounded. But it may be grounded by
> >> the input impedance of the '610 part or something that may cause
> >> it to miss some spec (or not) but was never noticed by users.
> >
> > That's plausible. One of my 11848As was built with the wrong
regulator --
> > as I recall, they used an adjustable LM338K-style part where a fixed
> > 12-volt
> > regulator was called for (or vice versa, I don't remember now). By
> > coincidence the output voltage was almost correct, enabling the unit to
> > work
> > unless you turned on an oscillator that drew enough current to load down
> > the
> > supply. The factory test procedure evidently wasn't comprehensive
enough
> > to
> > trigger the failure.
> >
> > That was a really hard problem to find.
> >
> > -- john, KE5FX
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>






------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.60/2496 - Release Date: 11/11/09
07:40:00


[Non-text portions of this message have been removed]