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 16:22:09 -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 17INC1n5007930; Wed, 18 Aug 2021 19:12:55 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17INC0w9007927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 18 Aug 2021 19:12:00 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 17INBjUV018996 for ; Wed, 18 Aug 2021 19:12:00 -0400 Received: from w92expo13.exchange.mit.edu (18.7.74.67) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 19:11:22 -0400 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by w92expo13.exchange.mit.edu (18.7.74.67) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 19:11:38 -0400 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.169) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Wed, 18 Aug 2021 19:11:37 -0400 Received: from DM5PR18CA0058.namprd18.prod.outlook.com (2603:10b6:3:22::20) by CH2PR01MB5798.prod.exchangelabs.com (2603:10b6:610:39::27) 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 23:11:50 +0000 Received: from DM6NAM11FT044.eop-nam11.prod.protection.outlook.com (2603:10b6:3:22:cafe::75) by DM5PR18CA0058.outlook.office365.com (2603:10b6:3:22::20) 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 23:11:50 +0000 Received: from mail-il1-f178.google.com (209.85.166.178) by DM6NAM11FT044.mail.protection.outlook.com (10.13.173.185) 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 23:11:50 +0000 Received: by mail-il1-f178.google.com with SMTP id y3so4002525ilm.6 for ; Wed, 18 Aug 2021 16:11:50 -0700 (PDT) From: Jim Ruxton To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Aug 2021 16:11:38 -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: AdeUh94ji3ea9v9iQjmupJ78y466Kw== Message-ID: References: <611d4447.1c69fb81.5395c.1877@mx.google.com> <20210818185107.0d61286e@raspberry> <611d7e39.1c69fb81.776d.3687@mx.google.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <611d7e39.1c69fb81.776d.3687@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 gmail.com designates 209.85.166.178 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.166.178; helo=mail-il1-f178.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=0yM8U60EbTiyn2I4ayPoQ/4isnCmTeRNhbxA/IYuJ0Y=; b=GSO5cyzMMaK/97oOR1fDmRTpCQZiS+qPx2t2y5MuLVf4w5UOL+yUdknFAqp5CDE8BZ d1CldIZGcYyVsX3cWk5enQP66ju2PN18fUcMhEgqZ/f/CgbTgM9mOVLDAX267hqfH31X dmQtpSeBoHXyWtP9WDKFX9glBEdoAl3SNSXbJlD03tsm7WBXl1fuVCCHSZiXZ5SPpff8 t5UPA0TwYTk8pGUTZ8ZOu7ITJkzA2zlyp5WeTZCzIeiQv2Agr3htRfjXJG9L8fvxjzhr +Rz6BSPFxb25zaDw1OkhR2gEnxyqpxDopTNuU42QmUTlQidNlskSFsC96VZhpCQbPmD2 JNag== authentication-results: spf=pass (sender IP is 209.85.166.178) 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:b012:: with SMTP id x18mr7412352ilh.255.1629328309938; Wed, 18 Aug 2021 16:11:49 -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 You can find the group here. https://www.facebook.com/groups/JLCPCB/ Jim On Wed., Aug. 18, 2021, 5:41 p.m. Dwayne Reid, wrote: > Hi there, Jim. > > I'm an old fart and do very little on Facebook. But I'm willing to > 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 Faceboo= k > >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 us= e? > > > > > > 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 leavi= ng > > > an area specifically marked in the supplied documentation as being fo= r > > > "manufacturer production trace information" or words to similar effec= t > > > 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 > > > -- > 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 > -- > 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 .