TECHNET Archives

1996

TechNet@IPC.ORG

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Date:
Fri, 10 May 96 13:19:55 PST
Content-Type:
text/plain
Parts/Attachments:
text/plain (83 lines)
John,

As long as you are not violating the minimum conductor spacing for your design 
and the icicle/spike is firmly attached to the solder surface.  Then record this 
condition a process variance, make sure it doesn't happen again (i.e. slap the 
operator on the hand) and go on.  If this condition happens all the time then 
correct the root cause and move on.

The views expressed are strictly my own.

Tom Carroll
Hughes Aircraft Company
(310) 334-4757
[log in to unmask]

_______________________________________________________________________________
Subject: ASSY-Flagging
From:    [log in to unmask] at CCGATE
Date:    5/10/96  10:57 AM

Happy Friday Technetters-

I've been tasked with justifying the enforcement of a long established
internal requirement, here at PBNI.   For as long as I can recall, we have
been considering solder flagging (aka icicles, solder spikes) a rejectable
condition, even when a solitary occurrence of as little as 0.8 mm.
(We based this rejection upon workmanship standards that we adopted
from a sister organization with a much more Class 3 and military 
orientation).

As we are manufacturing Class 2 products, and are re-evaluating the adopted
requirements, this 'reject' comes into question. I'm reviewing 
ANSI/J-STD-001A
and IPC-A-610B this morning, I find no reference to this condition other 
than
that shown in Figure 4-17 of the latter.

I certainly don't object to loosening up on our present standard if it is 
not
justifiable, but I can't help the feeling that I'm missing something.  Am I 
?

An anticipatory  ...Thanks !



The following is an attached File item from cc:Mail.  It contains
information that had to be encoded to ensure successful transmission
through various mail systems.  To decode the file use the UUDECODE
program.
--------------------------------- Cut Here ---------------------------------
begin 644 rfc822.txt
M1G)O;2!496-H3F5T+7)E<75E<W1`:7!C+F]R9PT*6"U%;G9E;&]P92U&<F]M
M.B!496-H3F5T+7)E<75E<W1`:7!C+F]R9PT*4F5C96EV960Z(&9R;VT@<VEM
M;VXN:7!C+F]R9R`H,38X+C$Q,RXR-"XV-"D-"B!B>2!%1$5.+DA!0RY#3TT@
M*%!-1$8@5C0N,RTW(",U.#@T*2!I9"`\,#%)-$I$5UHW0C5#,#`Q35I30$5$
M14XN2$%#+D-/33X[($9R:2P-"B`Q,"!-87D@,3DY-B`Q,#HU-CHR,"!04U0-
M"E)E8V5I=F5D.B!F<F]M(&EP8RYO<F<@8GD@<VEM;VXN:7!C+F]R9R!V:6$@
M4TU44"`H.30P.#$V+E-'22XX+C8N.2\Y-#`T,#8N4T=)*0T*(&ED($U!03(R
M,3`P.R!&<FDL(#$P($UA>2`Q.3DV(#$R.C4U.C$P("TP-S`P#0I296-E:79E
M9#H@8GD@:7!C+F]R9R`H4VUA:6PS+C$N,C@N,2`C,BD@:60@;3!U2'510BTP
M,#`P0S)#.R!&<FDL#0H@,3`@36%Y(#DV(#$P.C0W($-$5`T*4F5S96YT+61A
M=&4Z($9R:2P@,3`@36%Y(#$Y.38@,3(Z-34Z,3`@+3`W,#`-"D1A=&4Z($9R
M:2P@,3`@36%Y(#$Y.38@,3$Z,CDZ,#`@*S`P,#`-"E)E<V5N="UF<F]M.B!4
M96-H3F5T0&EP8RYO<F<-"D9R;VTZ('!B;FDN871T;6%I;"YC;VTA4$).(5!"
M3C$A2DUC1V5E0'-I;6]N+FEP8RYO<F<@*$IO:&X@36-'964I#0I3=6)J96-T
M.B!!4U-9+49L86=G:6YG#0I297-E;G0M<V5N9&5R.B!496-H3F5T+7)E<75E
M<W1`:7!C+F]R9PT*4F5S96YT+7-E;F1E<CH@5&5C:$YE="UR97%U97-T0&EP
M8RYO<F<-"E1O.B!T96-H;F5T0&EP8RYO<F<-"D-C.B!00DXA4$).,2%P8FYI
M(5!"3B%00DXQ(5-+96QL>4!P8FYI+F%T=&UA:6PN8V]M#0I297-E;G0M;65S
M<V%G92UI9#H@/")787`P1C(N,"YS6$,N:TMS86XB0&EP8SX-"DUE<W-A9V4M
M:60Z(#Q-4RU-04E,1RTR+C`P+4YO=&4M<&)N:2U*36-'964M,#@S,3<T,S0W
M,3X-"DU)344M=F5R<VEO;CH@,2XP#0I#;VYT96YT+71Y<&4Z(%1E>'0O4&QA
M:6X[(&-H87)S970]=7,M87-C:6D-"D-O;G1E;G0M=')A;G-F97(M96YC;V1I
M;F<Z(#=B:70-"D]L9"U2971U<FXM4&%T:#H@/'-I;6]N+FEP8RYO<F<A<&)N
M:2YA='1M86EL+F-O;2%00DXA4$).,2%*36-'964^#0I8+4UA:6QI;F<M3&ES
[log in to unmask]:7!C+F]R9SX@87)C:&EV92]L871E<W0O-#`T-0T*6"U,
H;V]P.B!496-H3F5T0&EP8RYO<F<-"E!R96-E9&5N8V4Z(&QI<W0-"@``
  
end



ATOM RSS1 RSS2