IPC-600-6012 Archives

December 2009

IPC-600-6012@IPC.ORG

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

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

Print Reply
Sender:
IPC-600-6012<[log in to unmask]>
X-To:
Combined Forum of D-33a and 7-31a Subcommittees <[log in to unmask]>
Date:
Wed, 9 Dec 2009 15:11:41 -0800
Reply-To:
"(Combined Forum of D-33a and 7-31a Subcommittees)" <[log in to unmask]>
Subject:
From:
Karl Sauter <[log in to unmask]>
Content-Type:
text/plain; charset="US-ASCII"; format=flowed
In-Reply-To:
Content-Transfer-Encoding:
7BIT
MIME-Version:
1.0
Parts/Attachments:
text/plain (44 lines)
Jack,

As an OEM, we view the existing wording as what is needed.  If haloing 
would be an issue, then the PCB fabricator should notify their customer 
of whatever traces or features are too close to the board edge.  OEM 
approval allowing boards to be built with haloing encroaching on 
circuitry should be documented.

Regards,

Karl Sauter
Sun Microsystems, Inc.


Jack Olson wrote:
> Fabricators,
>
> This is an opportunity to influence the acceptability of your product!
>
> The IPC Standards Development Committee is working on the next
> revision to IPC-A-600 (Acceptability of Printed Boards) which is a
> visual reference companion to IPC-6012.
>
> One of the items we are currently discussing is the acceptability of
> haloing along the board edge. Here is a link to where we stand now:
>
> http://frontdoor.biz/PCBportal/IPC-A-600H213.jpg
>
> The problem is, if the designer violates the recommendation in the
> current IPC-2221 design guideline and puts traces or planes too close
> to the board outline, with the current wording of "whichever is less"
> your boards can be considered rejectable with even a very small
> amount of haloing. Even intentional features like edge fingers can
> make your boards rejectable.
>
> We aren't sure if we should reword this (and if so, how?)
>
> So the ball is in your court (because unless there is a logical consensus
> we probably won't change it).
> I'll compile and submit any responses to the next committee meeting.
>
> Jack (aka "the new guy")
>   

ATOM RSS1 RSS2