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; Thu, 30 Apr 2020 15:47:08 -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 03UMcapA021371; Thu, 30 Apr 2020 18:38:56 -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 03UMcYJA021348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 30 Apr 2020 18:38:35 -0400 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 03UMcw1q030497 for ; Thu, 30 Apr 2020 18:39:22 -0400 Received: from oc11expo19.exchange.mit.edu (18.9.4.50) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 30 Apr 2020 18:37:50 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by oc11expo19.exchange.mit.edu (18.9.4.50) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 30 Apr 2020 18:38:21 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.106) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 30 Apr 2020 18:38:21 -0400 Received: from MWHPR14CA0044.namprd14.prod.outlook.com (2603:10b6:300:12b::30) by BYAPR01MB5400.prod.exchangelabs.com (2603:10b6:a03:11f::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.20; Thu, 30 Apr 2020 22:38:20 +0000 Received: from CO1NAM03FT048.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:12b:cafe::d3) by MWHPR14CA0044.outlook.office365.com (2603:10b6:300:12b::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.20 via Frontend Transport; Thu, 30 Apr 2020 22:38:20 +0000 Received: from elasmtp-kukur.atl.sa.earthlink.net (209.86.89.65) by CO1NAM03FT048.mail.protection.outlook.com (10.152.81.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.24 via Frontend Transport; Thu, 30 Apr 2020 22:38:18 +0000 Received: from [73.119.178.164] (helo=localhost.localdomain) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from ) id 1jUHov-000F54-Hm for piclist@mit.edu; Thu, 30 Apr 2020 18:38:17 -0400 From: Dave Tweed To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Thu, 30 Apr 2020 15:38:16 -0700 Subject: Re: [EE] LED Matrix CC/CA Thread-Topic: [EE] LED Matrix CC/CA Thread-Index: AdYfQUfwtR/yxDsDQTCxd1NxE9LSFw== Message-ID: <1588271896@dtweed.com> References: <5EAB49D2.9060407@narwani.org> 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: Fail (protection.outlook.com: domain of dtweed.com does not designate 209.86.89.65 as permitted sender) receiver=protection.outlook.com; client-ip=209.86.89.65; helo=elasmtp-kukur.atl.sa.earthlink.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=F0OI4ky8BRETQkWV5LcVKbzADuve5T3fIV4lhQCzQSY=; b=h2LTsWgWbawgJDpAZes5H2cMr5XY4A683Kn07bV4Lzwb4CtR1fIgKdKRHfrx56lG1xXaPzmiH/dVTij47koBJmUCziLaYQf/7lPXklRsBzusD19xfnG2aEPJK4BKewKpvzGZtS7Gi9hn3AcEzwDOBx/2lNbqxczL5QhlKsmnVKY= authentication-results: spf=fail (sender IP is 209.86.89.65) smtp.mailfrom=dtweed.com; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=fail action=none header.from=dtweed.com; x-originating-ip: 73.119.178.164 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-elnk-trace: 5507fdf0269a8d2672cc1e1b0924a179239a348a220c2609da8bc31dfe1e355223d96a2f23d4211e2601a10902912494350badd9bab72f9c350badd9bab72f9c x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Neil wrote: > On 4/30/2020 4:20 PM, Josh Koffman wrote: > > I'm looking at using a small 8x8 LED matrix in a project. It's been > > awhile since I've dealt with them. If I recall correctly, in an 8x8 > > LED matrix what makes it common cathode or common anode is really just > > how it's wired, correct? Since I'm making my own board, I could get > > either and have it work as long as I adjusted the wiring for the > > correct pinout? >=20 > Yes, if all the anodes are wired together to the COM pin then it's=20 > common-anode. > And vice versa. Of course, an 8x8 matrix has common-anode along one dimension, and common- cathode along the other dimension. So you get to choose one or the other, depending on how you physically orient the device. -- Dave --=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 .