1234567AA (the
and the second 1234567AB,
Gerbers, and everything in
1234567AB will just beboard #1234567A.
different one versus
different BOM (a
documenting the board. If
may or may not
the bare
it
set and the CAD
typically do) have a
isn't a requirement.
schematic file
themselves are the
footprints, all
schematic that
and the
original design.
same
of those
needed.
separate P/N and
new rev B
boards
board. It's a BOM
document for an
working in
in
the latest
integrity of the
are
those
The first
documentation
issued.
service wants
because
not be
next
use and
Now
many
they're the
that's
Ok, if they couldn't read schematics anyway that explains your reluctance here. We needed top-notch guys because most med gear is rather complex and requires techs to have a basic understanding of how amplifiers, uCs, logic chips and such work. Many of our techs had associates degrees. We also fostered (via hefty financial aid) a path to a bachelors degree so they got a chance to move into engineering. That was a major morale booster, one of the best things we ever decided.
another
How can QC do their job, a.k.a. quality control, if they do not understand the innars of your products? You guys really seem to be flying seat of the pants here :-)
In fact, the VP of QC asked me to personally interview his short list of candidates when he hired an EE.
in
aP/Ns
As I said, then folks in your company must have violated procedure. I have never seen it happen. 25 years and counting.
the
to
If you change R92 from 12.1k to 14.3k plus some other changes like that this does _not_ require a new PCB.
in.
That is why we, for example, have rigid netlist checks. Even back in
1986 when DOS was ruling the world it was a piece of cake to have the computer do a 1:1 file compare. So if someone screwed up in the rev C schematic edits the warning would pop up right there on the old green CRT. Because it as manadatory that it had to match the netlist from rev A since that's what the board layout was based upon.We also did them by hand back then but never caught the computer to err.
... and they missed out on the best solution they could have had. Big time. If they don't read this thread they may never know :-)
up
the
So you never repair anything? Sounds rather eco-unfriendly and wasteful in terms of gross margins.