D
Don Y
Guest
On 6/28/2022 12:35 PM, Joe Gwinn wrote:
Sadly, there isn\'t much that can really be done to improve things,
short of insisting on \"process\" -- and \"proof\" of adherence to same.
Some of my customers were even more zealous -- checking into the
qualifications of the engineers working on the design, wanting to
review component choices (for suitability as well as long-term
availability/second sources), insisting on placing the complete
design in escrow, etc.
I guess when it\'s YOUR ass on the line, you can never be too careful!
OTOH, you CHARGE them for these \"inconveniences\" (even though they
improve the quality of YOUR product!)
On Tue, 28 Jun 2022 07:16:13 -0700, jlarkin@highlandsniptechnology.com
wrote:
On Tue, 28 Jun 2022 16:19:23 +1000, Chris Jones
lugnut808@spam.yahoo.com> wrote:
On 28/06/2022 13:28, jlarkin@highlandsniptechnology.com wrote:
On Mon, 27 Jun 2022 20:49:18 -0400 (EDT), Martin Rid
martin_riddle@verison.net> wrote:
John Larkin <jlarkin@highland_atwork_technology.com> Wrote in message:r
On Mon, 27 Jun 2022 14:27:07 -0400 (EDT), Martin Rid<martin_riddle@verison.net> wrote:>Don Y <blockedofcourse@foo.invalid> Wrote in message:r>> I usually build a document that describes the hardware,nominal voltages, waveforms, timing relationships, etc.Plus, captured waveforms under different operating conditions(along with those expected during specific diagnostics)I\'m getting some pushback to move these onto the schematics,directly, instead of in a supplementary document.I\'m not keen on this as it means schematics have to make roomto accommodate these annotations. And, I can\'t see how tomaintain such a document if light of potential changes todiagnostics (which may be numerous for a given circuit).Any folks preparing comparable documentation have suggestions?>>I would imagine a separate service manual would apply.>>CheersDoes anyone still do that?-- If a man will begin with certainties, he shall end with doubts, but if he will be content to begin with doubts he shall end in
certainties.Francis Bacon
Medical equipment.
Cheers
Yikes. It scares me to imagine anyone doing field repairs to medical
equipment.
It is also a bit scary to imagine being treated in a hospital during an
emergency, full of equipment that when it fails, cannot be repaired in
the field, but must instead be sent to the same overseas facility that
every other hospital in the world is trying to send their dead units to,
(especially bearing in mind that whatever emergency may well put all the
freight aircraft or their pilots out of action).
There is an argument for only procuring medical equipment with proper
service manuals, resistors big enough to have values marked on them, and
a stock of spares of any programmable devices, or spares of any boards
with massive BGAs, and no parts locked to each other by serial number.
Those countries with nationalised healthcare do have sufficient buying
power to dictate those terms if they want to, (much like the US military
to test equipment manufacturers in the past).
No surface-mount?
Our FDA is absolutely fascist about quality. They pulled a pop
inspection on one nearby outfit that made cancer-treatment gear. They
discovered some new pcb\'s on the same bench as some repair units,
which is against the rules. They shut down the facility for a year of
re-training and re-qualification, and some of the engineers quit from
boredom.
Yes. Here\'s why:
.<https://en.wikipedia.org/wiki/Therac-25>
I read the what-happened reports from the day. What a bunch of hacks,
even by the standards of that day.
Sadly, there isn\'t much that can really be done to improve things,
short of insisting on \"process\" -- and \"proof\" of adherence to same.
Some of my customers were even more zealous -- checking into the
qualifications of the engineers working on the design, wanting to
review component choices (for suitability as well as long-term
availability/second sources), insisting on placing the complete
design in escrow, etc.
I guess when it\'s YOUR ass on the line, you can never be too careful!
OTOH, you CHARGE them for these \"inconveniences\" (even though they
improve the quality of YOUR product!)