Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x6JHBYlV021290 for ; Fri, 19 Jul 2019 19:11:36 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1hoWKY-0005zI-6s for rs_out_1@blacksheep.org; Fri, 19 Jul 2019 18:06:02 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1hoWKW-0005z9-4U for rsgb_lf_group@blacksheep.org; Fri, 19 Jul 2019 18:06:00 +0100 Received: from smtp1-2.ilait.se ([82.99.18.59]) by relay1.thorcom.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1hoWKT-0005HV-OJ for rsgb_lf_group@blacksheep.org; Fri, 19 Jul 2019 18:05:58 +0100 Received: from [192.168.1.151] (89-160-13-79.cust.bredband2.com [89.160.13.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jhbodin@tele2.se) by smtp.tele2.se (Postfix) with ESMTPSA id 45qy7m4YqxzKmF8 for ; Fri, 19 Jul 2019 17:05:56 +0000 (UTC) To: rsgb_lf_group@blacksheep.org References: <0cdedd04-4fb3-b9ab-fcf6-9d0bc84ab53f@df3lp.de> <4029faa6-f4ae-1e1d-9a17-e4aa960ddc73@tele2.se> <457846e1-9ae2-57a8-6b30-1098bd51a0f6@df3lp.de> From: Johan Bodin Message-ID: Date: Fri, 19 Jul 2019 19:05:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <457846e1-9ae2-57a8-6b30-1098bd51a0f6@df3lp.de> Content-Language: sv X-Spam-Score: -0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Thanks Peter! I had a look at the diyaudio site and found a reference to this:     https://www.nxp.com/docs/en/reference-manual/RFSAS20EDRM.pdf See table on page 71, obviously 2Ap and 2AW are both valid. Content analysis details: (-0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [82.99.18.59 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 0b2d339ae1d48966556dfb6ad64e2bce Subject: Re: LF: Where to find BF862 JFET ? Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false Thanks Peter! I had a look at the diyaudio site and found a reference to this:     https://www.nxp.com/docs/en/reference-manual/RFSAS20EDRM.pdf See table on page 71, obviously 2Ap and 2AW are both valid. I took the risk to order 2*50=100 for $12.50 :-) 73 Johan P. W. Schnoor wrote: > Seller: "adeleparts2010", China, code "2AW". > > And yes, I had the same concerns, but according to all the lists I > found, both smd codes are valid for BF862. > Later I found that: > https://www.diyaudio.com/forums/parts/229827-nxp-bf862-warning.html > So I took the risc...