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; Sun, 2 Feb 2020 04:52:08 -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 012Ce3x5015166; Sun, 2 Feb 2020 07:42:44 -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 012Ce2Oa015161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 2 Feb 2020 07:40:02 -0500 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 012CdZla016001 for ; Sun, 2 Feb 2020 07:39:52 -0500 Received: from oc11expo18.exchange.mit.edu (18.9.4.49) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sun, 2 Feb 2020 07:38:11 -0500 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by oc11expo18.exchange.mit.edu (18.9.4.49) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sun, 2 Feb 2020 07:39:58 -0500 Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.109) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sun, 2 Feb 2020 07:39:57 -0500 Received: from BYAPR01CA0019.prod.exchangelabs.com (2603:10b6:a02:80::32) by BYAPR01MB5414.prod.exchangelabs.com (2603:10b6:a03:11a::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.27; Sun, 2 Feb 2020 12:39:55 +0000 Received: from CO1NAM03FT020.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::201) by BYAPR01CA0019.outlook.office365.com (2603:10b6:a02:80::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.32 via Frontend Transport; Sun, 2 Feb 2020 12:39:55 +0000 Received: from mail-lj1-f181.google.com (209.85.208.181) by CO1NAM03FT020.mail.protection.outlook.com (10.152.80.178) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.26 via Frontend Transport; Sun, 2 Feb 2020 12:39:55 +0000 Received: by mail-lj1-f181.google.com with SMTP id f25so11715654ljg.12 for ; Sun, 02 Feb 2020 04:39:54 -0800 (PST) From: Alan Pearce To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sun, 2 Feb 2020 04:39:41 -0800 Subject: Re: [EE] Capacitive touch on glass ... Thread-Topic: [EE] Capacitive touch on glass ... Thread-Index: AdXZx5TBn01VBCIdTduiP+ecycj7LQ== Message-ID: References: <49367c50-b7dc-0c90-17c8-843744e0cf39@linuxha.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: 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 googlemail.com designates 209.85.208.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.181; helo=mail-lj1-f181.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=u3+Zm+kc3d/V8ERPTgT2UD14uRyjIfHzaXrnUvFmRtA=; b=CoSsWxeb50vRPjoeEeWtUHHZF7iKvVRDUSnUofgsLDxxhUKP0EYdZJvxy2rxRu9lGJ 4xgUQlN8XjIaZMIGHqKgNppKFKZIu+0tu13VcRbff+JdqQ1vT2G2Od4taOMiomuds5Es FfONiVPkZPPyHwNQg3oiXmzAIbUCPmDVJXBhDPwjU5Gu/gEuAjmKdxkovTuhe7SuidIF QUMgBIqp3JnMGhb+s6U8Ja90wfiziOt3oMhX4NxDMaMldE5Pxwos0yFYgKuGhlk+Hino hBoS+Nom+1BLW93sGAsr7rkjW5QCBksIbtZ4X7HWnpvOqgyUvSRCh3j+U3+Jx23kA2e1 PqYg== authentication-results: spf=pass (sender IP is 209.85.208.181) smtp.mailfrom=googlemail.com; mit.edu; dkim=pass (signature was verified) header.d=googlemail.com;mit.edu; dmarc=pass action=none header.from=googlemail.com;compauth=pass reason=100 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:a2e:7816:: with SMTP id t22mr11067327ljc.161.1580647192896; Sun, 02 Feb 2020 04:39:52 -0800 (PST) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 > In the 1970s or 1980s, I got a sample of a chip to do glass push buttons. > I thought the technique was very clever. On the user side of the glass wa= s > the conductive "button." On the other side of the glass were two > conductive areas covering the button, but split in half. This formed two > capacitors in series (inside pad to outside pad, then outside pad to the > other inside pad). One of the inside pads was driven with a square wave, > and the square wave was detected on the other inside pad. If you touched > the outside pad, the square wave would be shunted to ground and not > detected on the second inside pad. > > There was a special chip for this, but I think it would be easy enough to > do with a PIC. This is effectively how the PIC chips with CTMU work. On Sat, 1 Feb 2020 at 23:47, Harold Hallikainen wrote: > > I did not see the start of this discussion, but thought I'd throw > something in. > > In the 1970s or 1980s, I got a sample of a chip to do glass push buttons. > I thought the technique was very clever. On the user side of the glass wa= s > the conductive "button." On the other side of the glass were two > conductive areas covering the button, but split in half. This formed two > capacitors in series (inside pad to outside pad, then outside pad to the > other inside pad). One of the inside pads was driven with a square wave, > and the square wave was detected on the other inside pad. If you touched > the outside pad, the square wave would be shunted to ground and not > detected on the second inside pad. > > There was a special chip for this, but I think it would be easy enough to > do with a PIC. > > Harold > > > -- > FCC Rules Updated Daily at http://www.hallikainen.com > Not sent from an iPhone. > -- > 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 .