Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Wed, 18 Aug 2021 11:01:25 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17IHq1pE024785; Wed, 18 Aug 2021 13:52:34 -0400 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17IHq0fH024780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 18 Aug 2021 13:52:00 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 17IHpbvG025245 for ; Wed, 18 Aug 2021 13:52:00 -0400 Received: from oc11expo20.exchange.mit.edu (18.9.4.51) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 13:51:17 -0400 Received: from w92exhyb2.exchange.mit.edu (18.7.71.32) by oc11expo20.exchange.mit.edu (18.9.4.51) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 13:50:59 -0400 Received: from NAM02-DM3-obe.outbound.protection.outlook.com (104.47.56.42) by w92exhyb2.exchange.mit.edu (18.7.71.32) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Wed, 18 Aug 2021 13:50:59 -0400 Received: from DM5PR13CA0036.namprd13.prod.outlook.com (2603:10b6:3:7b::22) by DM5PR01MB2444.prod.exchangelabs.com (2603:10b6:3:3b::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.19; Wed, 18 Aug 2021 17:51:12 +0000 Received: from DM6NAM11FT041.eop-nam11.prod.protection.outlook.com (2603:10b6:3:7b:cafe::e9) by DM5PR13CA0036.outlook.office365.com (2603:10b6:3:7b::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.11 via Frontend Transport; Wed, 18 Aug 2021 17:51:12 +0000 Received: from mail-wr1-f47.google.com (209.85.221.47) by DM6NAM11FT041.mail.protection.outlook.com (10.13.172.98) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.19 via Frontend Transport; Wed, 18 Aug 2021 17:51:12 +0000 Received: by mail-wr1-f47.google.com with SMTP id q11so4771224wrr.9 for ; Wed, 18 Aug 2021 10:51:12 -0700 (PDT) Received: from raspberry (cpc113460-oxfd27-2-0-cust322.4-3.cable.virginm.net. [86.24.157.67]) by smtp.gmail.com with ESMTPSA id h4sm483851wrm.42.2021.08.18.10.51.11 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Aug 2021 10:51:11 -0700 (PDT) From: Alan Pearce To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Aug 2021 10:51:07 -0700 Subject: Re: [EE] PCB manufacturer not wanting to put UL 94V-0 mark on boards Thread-Topic: [EE] PCB manufacturer not wanting to put UL 94V-0 mark on boards Thread-Index: AdeUWxAQDv3P0WdnRZuRfkS3b8tL7A== Message-ID: <20210818185107.0d61286e@raspberry> References: <611d4447.1c69fb81.5395c.1877@mx.google.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <611d4447.1c69fb81.5395c.1877@mx.google.com> Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of googlemail.com designates 209.85.221.47 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.221.47; helo=mail-wr1-f47.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=from:date:to:subject:message-id:in-reply-to:references:organization :mime-version:content-transfer-encoding; bh=+5toafzXFLd9MlUhS4YoHHyKh6ZLEJpAek9BAoI5im8=; b=DjBZ7kizZXO+kQ3TDh7bkwQ0FcWHlhAEihkawhm2tfWghT08rlAukzBO/6NLbR0Rtc MFm9b6NaWsXPCO+95IziZLtPM9JrI3Gumt2oZwDsOFX/vr0T18OP22pX+5bYVlSvw97+ madwdOEnRkiRpMApSrDhwsZ+KXwRCLXl4FA+vn5zumMNRByQ2Wyd5PdCIKLQSolU/TMx Lqtj/9fgLrG44d3S6DrxoaM6mq9Z+7RPVdAlvJUo3CffxCmUuOvMtaur+9TiL7Dx3gUv zZfF0Vg7lQY29RY2xzW/q9jK+YbnITGd4qTLGKlHCGaS/U4IRBElRqz+Q9A+cMPAx/ma 73GA== authentication-results: spf=pass (sender IP is 209.85.221.47) smtp.mailfrom=googlemail.com; mit.edu; dkim=pass (signature was verified) header.d=googlemail.com;mit.edu; dmarc=pass action=none header.from=googlemail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a5d:4c4e:: with SMTP id n14mr11763531wrt.226.1629309071251; Wed, 18 Aug 2021 10:51:11 -0700 (PDT) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Wed, 18 Aug 2021 11:32:55 -0600 Dwayne Reid wrote: .... > What I'm asking for is a reality check. Is it reasonable for me to=20 > specify that the PCB material must be UL certified **AND** that the=20 > PCB manufacturer must add the UL mark to the boards when they are > manufactured? >=20 > How do I go about ensuring that JLCPCB does what I ask? >=20 > Opinions greatly appreciated. >=20 > Many thanks! >=20 > dwayne >=20 Have you tried asking them for a certificate for the material they use? Do you make a specific area for them to put the UL mark on the PCB silkscreen and indicate this in your documentation? I do recall leaving an area specifically marked in the supplied documentation as being for "manufacturer production trace information" or words to similar effect which was never a problem with manufacturers we used - but they were used to the requirement as it was required as part of their ESA certification :) --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .