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 10:45:46 -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 17IHXew4022215; Wed, 18 Aug 2021 13:34:31 -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 17IHXcW4022212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 18 Aug 2021 13:33:39 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 17IHWoK4009052 for ; Wed, 18 Aug 2021 13:33:38 -0400 Received: from w92expo33.exchange.mit.edu (18.7.74.45) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 13:32:50 -0400 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by w92expo33.exchange.mit.edu (18.7.74.45) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 18 Aug 2021 13:32:44 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.170) 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 13:32:44 -0400 Received: from MWHPR22CA0071.namprd22.prod.outlook.com (2603:10b6:300:12a::33) by BYAPR01MB4981.prod.exchangelabs.com (2603:10b6:a03:1d::21) 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:32:56 +0000 Received: from CO1NAM11FT058.eop-nam11.prod.protection.outlook.com (2603:10b6:300:12a:cafe::7) by MWHPR22CA0071.outlook.office365.com (2603:10b6:300:12a::33) 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:32:56 +0000 Received: from mail-pj1-f54.google.com (209.85.216.54) by CO1NAM11FT058.mail.protection.outlook.com (10.13.174.164) 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:32:56 +0000 Received: by mail-pj1-f54.google.com with SMTP id j1so3070797pjv.3 for ; Wed, 18 Aug 2021 10:32:56 -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 141sm399661pfv.15.2021.08.18.10.32.55 for (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 18 Aug 2021 10:32:55 -0700 (PDT) From: Dwayne Reid To: pic microcontroller discussion list Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Aug 2021 10:32:55 -0700 Subject: [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: AdeUWOCeLU+OySIZTSeQbQxerlwSEw== Message-ID: <611d4447.1c69fb81.5395c.1877@mx.google.com> List-Help: List-Subscribe: , List-Unsubscribe: , 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.216.54 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.216.54; helo=mail-pj1-f54.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:mime-version; bh=RiuNNgK5boh5xE/XAmkPhqS9icsZZY0Ks/dmR7KAWXE=; b=mmpNgbLJRdU9fvHlkL2CoJii2woEVFv4f61tGf/kAv+T9YcrW5nbgJypJTXVP61Lnn vZ2T4ThVQ6mYaLg+Dcm7foQQQQUHpSbIs/3DuBgvSCMiuKkjJv6+U0H612QA8Wvm+NVx sUTYB35Ek9B/LnZdTLnsFmaRvuWjEn65PqajQwMJakTOAwfKXStxQBm+/RRgzhKcrgYB aL0s3lN50il81ZSHl2gAdpGywmTaZiLPyk9JAI0Ny1qebzJASdH1M4ik4tCkbavHcoZ4 UfRGvd50ar5Nkn5/57BwxwPPrlfKhaYZUnrpgMdvZH2zpUv4R9jLleqEKa0Pc42hKnJa nKWA== authentication-results: spf=pass (sender IP is 209.85.216.54) 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:902:8c90:b0:12f:699b:27 with SMTP id t16-20020a1709028c9000b0012f699b0027mr1629052plo.28.1629307975694; Wed, 18 Aug 2021 10:32:55 -0700 (PDT) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Good day to all. I'm looking for advice. Because this advice requires opinions, I=20 can't ask on Stack Exchange. Good old PIClist to the rescue! We use a couple of Chinese PCB manufacturers to make our bare circuit=20 boards. Both have given us good service over the past many years but=20 prices have been increasing faster than other suppliers **AND**=20 delivery times have been getting longer. I keep seeing recommendations for a PCB company called JLCPCB. Their=20 prices gook good and the delivery times are also good. I've ordered from them a couple of times. The only problem is that=20 one of our production orders (600 pcs) did not have the UL flame=20 marking "94V-0" on the boards, even though that requirement was=20 clearly communicated to them both in the readme.txt file contained=20 within the ZIP file as well as direct remarks on the order page. Although I did raise this problem with them after the boards were=20 received, I never did get a reply. I've just ordered another 3 board designs from them - two are=20 prototype quantities (10 pcs each) and a tiny production run of 100 pcs. Again, I specified that the PCB material must be UL rated and that=20 the 94V-0 mark must be on the silkscreen. This time, they got back to me and stated "They cannot modify the=20 customer-supplied silkscreen." Quite frankly, that is a total load=20 of fooey. They do add a production number string to the=20 silkscreen. I pointed that out to the person with whom I have been=20 communicating - they just said the same thing. So far as I know, it is illegal for ME to add the UL mark to my=20 design files. The reason given to me was that the certifying=20 authority doesn't know if the PCB material does actually meet UL=20 requirements. What I have been told, and what has happened with=20 every other PCB manufacturer, is that the manufacturer adds the UL=20 mark to the silkscreen when the films are processed. 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 manufactu= red? How do I go about ensuring that JLCPCB does what I ask? Opinions greatly appreciated. Many thanks! dwayne --=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 .