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 12:43:19 -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 17IJX1bU008463; Wed, 18 Aug 2021 15:33:55 -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 17IJWnqv008397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 18 Aug 2021 15:33:00 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 17IJWmXJ030931 for ; Wed, 18 Aug 2021 15:33:00 -0400 Received: from oc11expo22.exchange.mit.edu (18.9.4.84) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 15:31:44 -0400 Received: from w92exhyb3.exchange.mit.edu (18.7.71.73) by oc11expo22.exchange.mit.edu (18.9.4.84) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 15:31:59 -0400 Received: from NAM04-MW2-obe.outbound.protection.outlook.com (104.47.73.171) by w92exhyb3.exchange.mit.edu (18.7.71.73) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Wed, 18 Aug 2021 15:31:59 -0400 Received: from BN9PR03CA0533.namprd03.prod.outlook.com (2603:10b6:408:131::28) by PH0PR01MB6246.prod.exchangelabs.com (2603:10b6:510:b::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.14; Wed, 18 Aug 2021 19:32:11 +0000 Received: from BN8NAM11FT029.eop-nam11.prod.protection.outlook.com (2603:10b6:408:131:cafe::74) by BN9PR03CA0533.outlook.office365.com (2603:10b6:408:131::28) 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 19:32:11 +0000 Received: from mail-il1-f181.google.com (209.85.166.181) by BN8NAM11FT029.mail.protection.outlook.com (10.13.177.68) 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 19:32:11 +0000 Received: by mail-il1-f181.google.com with SMTP id r6so3381786ilt.13 for ; Wed, 18 Aug 2021 12:32:11 -0700 (PDT) From: Jim Ruxton To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Aug 2021 12:31:59 -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: AdeUaUw0v9oaLjWgSkWknZtaUAnhrg== Message-ID: References: <611d4447.1c69fb81.5395c.1877@mx.google.com> <20210818185107.0d61286e@raspberry> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <20210818185107.0d61286e@raspberry> 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 gmail.com designates 209.85.166.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.166.181; helo=mail-il1-f181.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=iAvDxbXE1/Xw3/xYaKGfANtjVkX7jKZs98NwYMXc1lA=; b=OqZ+GoKfLJTSvBHXM0JghXRN+xalI9dqthinWPvPPzqWbU+WMHR5W3+F89Y2BbpGDC Jl8j6ZlR6ujS5w9rs+M2Y0jRtyh0ejg0w9JufhTOn9v9MbBExLNzC0T1GPzl/Zi8wvGC 4UaSHzLDMK1KmLRPXsI+SEHnBLVsISG2vBn9ciw7zP1Drbcq8hQOYzSnVNr7klW9YXfN biw33oSmmYfOu1H4PsQUwV/oeM7XAFbYSbUisbGdtaxYF45FZJKSrCDNGIfOlWoa+WSF /BGkSxv+Kj2hBzGWzCxv6VyQy4I9zInzMmP1gxE+QEyGsxhqPRx7OjIG3ARBBptVaHxq 2+Tw== authentication-results: spf=pass (sender IP is 209.85.166.181) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.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:a92:6a0f:: with SMTP id f15mr7096811ilc.195.1629315130741; Wed, 18 Aug 2021 12:32:10 -0700 (PDT) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Not an answer to your question but there is a very active JLCPCB Facebook group where a lot of people discuss and resolve issues about the service. The moderator appears to work at JLCPCB and is very responsive. Jim On Wed., Aug. 18, 2021, 1:52 p.m. Alan Pearce, < kiwiantipodean@googlemail.com> wrote: > 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 > > specify that the PCB material must be UL certified **AND** that the > > PCB manufacturer must add the UL mark to the boards when they are > > manufactured? > > > > How do I go about ensuring that JLCPCB does what I ask? > > > > Opinions greatly appreciated. > > > > Many thanks! > > > > dwayne > > > > 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 :) > > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=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 .