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; Tue, 24 Nov 2020 18:51:20 -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 0AP2eWGt020662; Tue, 24 Nov 2020 21:41:09 -0500 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AP2eTle020642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 24 Nov 2020 21:40:31 -0500 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 0AP2e3Ch030767 for ; Tue, 24 Nov 2020 21:40:29 -0500 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 24 Nov 2020 21:40:09 -0500 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 24 Nov 2020 21:40:22 -0500 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.169) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 24 Nov 2020 21:40:22 -0500 Received: from BN6PR19CA0076.namprd19.prod.outlook.com (2603:10b6:404:133::14) by DM5PR01MB2330.prod.exchangelabs.com (2603:10b6:3:13::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3589.21; Wed, 25 Nov 2020 02:40:21 +0000 Received: from BN8NAM11FT040.eop-nam11.prod.protection.outlook.com (2603:10b6:404:133:cafe::f7) by BN6PR19CA0076.outlook.office365.com (2603:10b6:404:133::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3611.20 via Frontend Transport; Wed, 25 Nov 2020 02:40:20 +0000 Received: from omta03.suddenlink.net (208.180.40.73) by BN8NAM11FT040.mail.protection.outlook.com (10.13.177.166) with Microsoft SMTP Server id 15.20.3589.22 via Frontend Transport; Wed, 25 Nov 2020 02:40:20 +0000 Received: from wb5agz ([47.217.109.16]) by dalofep03.suddenlink.net (InterMail vM.8.04.03.22.02 201-2389-100-169-20190213) with ESMTP id <20201125024020.LVCY11381.dalofep03.suddenlink.net@wb5agz> for ; Tue, 24 Nov 2020 20:40:20 -0600 Received: from martin by wb5agz with local (Exim 4.92) (envelope-from ) id 1khkjD-00018A-G8 for piclist@mit.edu; Tue, 24 Nov 2020 20:40:19 -0600 From: Martin McCormick To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 24 Nov 2020 18:40:19 -0800 Subject: [OT] Hyperikon Retrofit LED Tubes Without Ballast Thread-Topic: [OT] Hyperikon Retrofit LED Tubes Without Ballast Thread-Index: AdbC1dr1UC71c5GORL2AXDoMWb7lng== Message-ID: 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 suddenlink.net designates 208.180.40.73 as permitted sender) receiver=protection.outlook.com; client-ip=208.180.40.73; helo=omta03.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=jWPKo1gDjx5YegiS6JDml6q9PbkbQlhA77KwKghCvA8=; b=ulETAmkAoLlbGjIgg0LiYh17oHeZSeVAMto3XI6LB7pVRzkAhT4mljhaa/Ie2JE9XiPJZTc+XI2EMdEs/i0YoqQ7FzPHT6lPnwHIRxy3t0Ey5Az8sCr2W/smX12Vk4yj4tgMlTD7Fj+xgnnPx3RgGL8TZOGwBXjveR+YX6ganOA= authentication-results: spf=pass (sender IP is 208.180.40.73) 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 We just bought 4 Hyperikon retrofit LED tubes to replace some 25-year-old tubes that gave up the ghost. Both pairs of tubes worked just fine so we got 4 more for another fixture that has 2 RF-type ballasts of different design. Both work properly with 2 pairs of old-school T8 fluorescent tubes but not with the new LED tubes. The new LED tubes are 48-inch drop-in replacements for the t8's and I seem to recall that the marketing information for the LED tubes indicated they could work without ballasts if one rewired the sockets. The LED tubes are stamped with information that they can work over a range of 100 volts to above 200 V so they could be fed directly from the AC line without ballasts. In the ballast configuration, two gas discharge tubes are in series on each ballast. It sounds like the ballasts must double the voltage so that each gas tube sees half that voltage or somewhere about or slightly above the AC power line voltage. The LED tubes don't need the cathode heat voltage which is somewhere around 1.5 to 3 volts and do need to see an end-to-end voltage within the recommended range for proper operation. Each old gas tube draws 40 watts and the new LED replacements draw 18 watts each. They also only shine in one direction so that you orient the tube so that the clear side points where you need the light. I was thinking about hooking one of the new tubes up to a variac and transformer to see if my understanding is correct before ripping out the 2 electronic ballasts in the fixture that does not work with the new LED's. =20 In theory, each tube has it's own current regulation which is why the marketing literature mentioned ballast bypass operation. The tubes come with stickers one can place on fixtures indicating that old-style fluorescent tubes must never be used here. Has anybody tried this already or is my understanding flawed? When I discovered that the electronic ballasts in one fixture didn't work correctly with the LED's, I picked out 4 newer glass tubes and was able to prove that both ballasts work. I would rather cart all the glass tubes off to our local recycler, though, and use the LED tubes which save energy and are not as fragile. At 48 inches or 1.2 meters, they are just begging to be accidentally hit/broken against some object when one is climbing a ladder or carrying them around. I've been working with these for 30 years and finally bumped one against the inside of a wooden box built around one fixture. The blow wasn't much but the tube shattered and made quite a low-grade hazardous waste incident in our house. Any constructive ideas as to documentation are appreciated. 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 .