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, 25 Nov 2020 10:23:39 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0APIE7QT022453; Wed, 25 Nov 2020 13:14:21 -0500 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 0APIE69m022450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 25 Nov 2020 13:14:06 -0500 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 0APIE6Uu000752 for ; Wed, 25 Nov 2020 13:14:06 -0500 Received: from w92exhyb6.exchange.mit.edu (18.7.71.111) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 25 Nov 2020 13:13:21 -0500 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by w92exhyb6.exchange.mit.edu (18.7.71.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 25 Nov 2020 13:13:48 -0500 Received: from NAM02-CY1-obe.outbound.protection.outlook.com (104.47.37.55) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 25 Nov 2020 13:13:47 -0500 Received: from BN4PR13CA0007.namprd13.prod.outlook.com (2603:10b6:403:3::17) by BYAPR01MB4277.prod.exchangelabs.com (2603:10b6:a03:5d::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3589.29; Wed, 25 Nov 2020 18:13:46 +0000 Received: from BN8NAM11FT016.eop-nam11.prod.protection.outlook.com (2603:10b6:403:3:cafe::7) by BN4PR13CA0007.outlook.office365.com (2603:10b6:403:3::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3611.15 via Frontend Transport; Wed, 25 Nov 2020 18:13:45 +0000 Received: from omta04.suddenlink.net (208.180.40.74) by BN8NAM11FT016.mail.protection.outlook.com (10.13.176.97) with Microsoft SMTP Server id 15.20.3589.22 via Frontend Transport; Wed, 25 Nov 2020 18:13:45 +0000 Received: from wb5agz ([47.217.109.16]) by dalofep04.suddenlink.net (InterMail vM.8.04.03.22.02 201-2389-100-169-20190213) with ESMTP id <20201125181345.VHGC11314.dalofep04.suddenlink.net@wb5agz> for ; Wed, 25 Nov 2020 12:13:45 -0600 Received: from martin by wb5agz with local (Exim 4.92) (envelope-from ) id 1khzIW-0003Kh-Ou for piclist@mit.edu; Wed, 25 Nov 2020 12:13:44 -0600 From: Martin McCormick To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 25 Nov 2020 10:13:44 -0800 Subject: Re: [OT] Hyperikon Retrofit LED Tubes Without Ballast Thread-Topic: [OT] Hyperikon Retrofit LED Tubes Without Ballast Thread-Index: AdbDWBkNs1M40+WpRB+gOgwg+2zpPQ== Message-ID: References: <20201125040424.GL22162@laptop.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <20201125040424.GL22162@laptop.org> 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 suddenlink.net designates 208.180.40.74 as permitted sender) receiver=protection.outlook.com; client-ip=208.180.40.74; helo=omta04.suddenlink.net; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitprod.onmicrosoft.com; s=selector2-mitprod-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+E2/p97fvJCnbgwkkw+WTCZGguCYngGTIuaAIficqsw=; b=VthRlKGqnDJm+0PegwY6T8V70Sdhyuesb4v3XEB67YrzrbMcpkOQUAJijZlwZx5S4M1oATQzxbc3QZaTe7G/u1FAD7M88QpQTYCBKMHea+wHT160xo/baqhLGD0QvKk9paI1f9mpLLrQo1+PFNSnodzyyWpmExjYD3VaLdoqf2Y= authentication-results: spf=pass (sender IP is 208.180.40.74) smtp.mailfrom=suddenlink.net; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=bestguesspass action=none header.from=suddenlink.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-topics: [OT] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 James Cameron writes: > I can't confirm the data you have on your product, but I've changed two > fittings over to LED tubes and have another nine not yet changed. The > change for my tubes was to wire 240V to each end of the tube, > isolating the ballast and starter. Thank you. That sounds exactly like what I plan to do except that it will be 120 volts at both ends due to this being North America and 120 volts is within the voltage range specified on the tubes, themselves. First, out of cowardice on my part, I will connect one LED tube to an isolation transformer and variac set to around 120 volts to see if the tube both lights properly and draws the amperage necessary to dissipate 18 watts. If both these things happen without anything going poof! or catching fire, I'll be assured that I can junk the ballast which also contains the starter circuit. All that does is briefly give a shot of a low voltage of around 1.5 to 3 volts to the cathodes at each end so they start producing electrons and the gas ionizes. I am thinking the LED tubes probably leave 1 of each end pair of pins unconnected and the other caries 1 side of the high-voltage pair. The 120 or 240 volts potential is found at either pin on one end and either pin on the other. If my work bench mockup turns up anything potentially dangerous to us or things, I will post a message describing what not to try. Martin McCormick WB5AGZ --=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 .