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 14:48:36 -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 17ILeauw027762; Wed, 18 Aug 2021 17:41:06 -0400 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17ILeZPo027751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 18 Aug 2021 17:40:35 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 17ILe7ER022921 for ; Wed, 18 Aug 2021 17:40:34 -0400 Received: from oc11expo12.exchange.mit.edu (18.9.4.17) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 17:39:48 -0400 Received: from oc11exhyb1.exchange.mit.edu (18.9.1.60) by oc11expo12.exchange.mit.edu (18.9.4.17) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 17:40:03 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.102) by oc11exhyb1.exchange.mit.edu (18.9.1.60) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Wed, 18 Aug 2021 17:40:03 -0400 Received: from DM6PR02CA0144.namprd02.prod.outlook.com (2603:10b6:5:332::11) by CH2PR01MB5877.prod.exchangelabs.com (2603:10b6:610:42::15) 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 21:40:11 +0000 Received: from DM6NAM11FT015.eop-nam11.prod.protection.outlook.com (2603:10b6:5:332:cafe::d2) by DM6PR02CA0144.outlook.office365.com (2603:10b6:5:332::11) 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 21:40:11 +0000 Received: from mail-pl1-f169.google.com (209.85.214.169) by DM6NAM11FT015.mail.protection.outlook.com (10.13.172.133) 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 21:40:11 +0000 Received: by mail-pl1-f169.google.com with SMTP id d17so2649053plr.12 for ; Wed, 18 Aug 2021 14:40:11 -0700 (PDT) Received: from DAR5.planet.eon.net (d142-59-123-176.abhsia.telus.net. [142.59.123.176]) by smtp.gmail.com with ESMTPSA id i11sm765176pfo.29.2021.08.18.14.40.09 for (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 18 Aug 2021 14:40:09 -0700 (PDT) From: Dwayne Reid To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Aug 2021 14:40:09 -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: AdeUesxhe4J2ljzqQhWt47xS+k+gYA== Message-ID: <611d7e39.1c69fb81.776d.3687@mx.google.com> References: <611d4447.1c69fb81.5395c.1877@mx.google.com> <20210818185107.0d61286e@raspberry> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: 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 planet.eon.net designates 209.85.214.169 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.214.169; helo=mail-pl1-f169.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=planet.eon.net; s=google; h=message-id:date:to:from:subject:in-reply-to:references:mime-version; bh=ZcBswLIogFxIyRKG63ZhM0PiIzH9l3W+7qkOaFEZ8kg=; b=YInQ2ifmS3UfSijBQb9c0Kjjf1FeMV6QLf7kvcrwU+fpZwCpBQiYHckPF6cT/gMaF+ J5xeKhJE73np9PlJZPJIRpf/KrLFK2Pr1Ywc6uubIsjeagLjSfXBYeP/UcefMB4ETWZK MoYJtjdr6NNSgGmgf/Do5r9LRwKeF/+8p/wjGo1FElR4UisjJuC8uAPkAb/A6O/8euvO lYGuWUw1H4S1aMtFJv58C4WD4zl0/fHJU3yaZJ5k4LZAV93t9aTvhLPGeP42hzE27rOD LVD9Z19NCViLA+Gz/zfv89z0DbRYIlBQ3jiumzTzZYn1TBMmXeshUlaKBEO1ZbIViD0M 04Mg== authentication-results: spf=pass (sender IP is 209.85.214.169) smtp.mailfrom=planet.eon.net; mit.edu; dkim=pass (signature was verified) header.d=planet.eon.net;mit.edu; dmarc=bestguesspass action=none header.from=planet.eon.net; 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:a17:90b:4b12:: with SMTP id lx18mr11585197pjb.121.1629322810210; Wed, 18 Aug 2021 14:40: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 Hi there, Jim. I'm an old fart and do very little on Facebook. But I'm willing to=20 try. Can you give me a hint as to where I would go? Many thanks! dwayne At 01:31 PM 8/18/2021, Jim Ruxton wrote: >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 > > >-- >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 Dwayne Reid Trinity Electronics Systems Ltd Edmonton, AB, CANADA 780-489-3199 voice 780-487-6397 fax 888-489-3199 Toll Free www.trinity-electronics.com Custom Electronics Design and Manufacturing --=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 .