Not to be anti semantic, but didn't you mean to say "the commended s/b committed"?
Dewey
-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Stadem, Richard D.
Sent: Wednesday, January 09, 2013 11:29 AM
To: [log in to unmask]
Subject: Re: [TN] TM 650 , Method 2.6.3.5 - Bare Board SIR
I don't know who the members are of the team who wrote IPC-5703, but I must certainly say that is one of the best most informative documents I have seen the IPC put out. That committee should be commended for an excellent job.
-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Stadem, Richard D.
Sent: Wednesday, January 09, 2013 11:59 AM
To: [log in to unmask]
Subject: Re: [TN] TM 650 , Method 2.6.3.5 - Bare Board SIR
IPC-5703 and 5704 should also be added. WP-008 should also be referenced.
-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Whittaker, Dewey (EHCOE)
Sent: Wednesday, January 09, 2013 11:49 AM
To: [log in to unmask]
Subject: Re: [TN] TM 650 , Method 2.6.3.5 - Bare Board SIR
Well SIR, so much for a clean getaway.
I have tried to get Method 2.6.3.5 added to IPC-6012 for awhile. We have had to add it as a required test for pre SMOBC application and a post HASL process, as well as the applicable cleanliness requirements/tests.
Dewey
-----Original Message-----
From: TechNet [mailto:[log in to unmask]] On Behalf Of Graham Naisbitt
Sent: Wednesday, January 09, 2013 10:39 AM
To: [log in to unmask]
Subject: Re: [TN] TM 650 , Method 2.6.3.5 - Bare Board SIR
Happy New Year everyone, WOW that got some attention!
I certainly recall the debate when we finalised 2.6.3.7 so....I went have a look at my files and: Sorry I am wrong!
When I checked all my files I evidently picked-up on the wrong document. It was in 2.6.3.6 wherein we have:
"This method, in conjunction with the supporting documentation in IPC-J-STD-004, is intended to be equivalent to Telcordia Technologies GR-78-CORE, Section 13.1..." (We tried to insert "Superseded" but it wasn't accepted.
I do however stand by my question of whether IPC 6012 will be reviewed - it is due and this would be a useful catch-up?
Graham
On 9 Jan 2013, at 16:06, Douglas Pauls <[log in to unmask]> wrote:
> Method 2.6.3.5 was a shameless copying of the SIR testing for bare
> board fabricators, required in Bellcore GR-78-CORE, as Graham
> indicated. At the time we drafted 2.6.3.5, Bellcore was devoting no
> technical resources to that document and was not supporting it, so IPC put the method in place.
>
> Graham, are you certain the SIR test in GR-78-CORE was superceded by
> 2.6.3.7? I know the J-STD-004 flux requirements went that way, but
> this would be the first that I had heard that Bellcore likewise
> adopted it. I agree that the GR-78-CORE test is quite old, but it was
> still a pretty good test to determine cleanliness. The almost
> impossibly high levels were very difficult to achieve if you had any
> detrimental residues present.
>
> Doug Pauls
>
>
>
> From: Graham Naisbitt <[log in to unmask]>
> To: <[log in to unmask]>
> Date: 01/09/2013 09:56 AM
> Subject: Re: [TN] TM 650 , Method 2.6.3.5 - Bare Board SIR
> Sent by: TechNet <[log in to unmask]>
>
>
>
> Hi Richard
>
> To the best of my knowledge that was called up by IPC 6012. I don't
> know whether this is under review - but it should be (2007 = 5 year
> rule). I will take this matter up with the group at APEX.
>
> I suggest you apply some caution to the veracity of any data you
> produce, as the method really needs to be updated. The old Bellcore
> GR-78-CORE was superceded by method 2.6.3.7
>
> Hope this helps
>
> Graham Naisbitt ? Vice-Chairman IPC TGs: SIR / ECM; CAF & 7-11 Test
> methods Sub-Committee, IEC TC91 WG3 Project Leader, BSi EPL 501, UK
> IAG
> E: [log in to unmask]
> T: 012 5252 1500
>
>
>
> On 7 Jan 2013, at 20:29, Richard Kraszewski
> <[log in to unmask]> wrote:
>
>> Can anyone tell me which IPC bare board documents references test
>> method
> 2.6.3.5 to meet a minimum SIR requirement?
>>
>> Rich Kraszewski - Plexus Engineering
>>
>>
>> _____________________________________________________________________
>> _ This email has been scanned by the Symantec Email Security.cloud
> service.
>> For more information please contact helpdesk at x2960 or
> [log in to unmask]
>> _____________________________________________________________________
>> _
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please contact helpdesk at x2960 or
> [log in to unmask]
> ______________________________________________________________________
>
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please contact helpdesk at x2960 or
> [log in to unmask]
> ______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] ______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] ______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask] ______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask]
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please contact helpdesk at x2960 or [log in to unmask]
______________________________________________________________________
|