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; Mon, 3 Aug 2020 05:40:19 -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 073CVEqh021845; Mon, 3 Aug 2020 08:31:38 -0400 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 073CVCVs021842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 3 Aug 2020 08:31:12 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 073CUmKc027866 for ; Mon, 3 Aug 2020 08:30:57 -0400 Received: from w92expo9.exchange.mit.edu (18.7.74.63) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 3 Aug 2020 08:30:32 -0400 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by w92expo9.exchange.mit.edu (18.7.74.63) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 3 Aug 2020 08:30:50 -0400 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.175) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 3 Aug 2020 08:30:50 -0400 Received: from DM5PR21CA0045.namprd21.prod.outlook.com (2603:10b6:3:ed::31) by BY5PR01MB5730.prod.exchangelabs.com (2603:10b6:a03:1bc::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.18; Mon, 3 Aug 2020 12:30:48 +0000 Received: from DM3NAM03FT003.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:ed:cafe::7) by DM5PR21CA0045.outlook.office365.com (2603:10b6:3:ed::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3283.1 via Frontend Transport; Mon, 3 Aug 2020 12:30:48 +0000 Received: from mail-ej1-f45.google.com (209.85.218.45) by DM3NAM03FT003.mail.protection.outlook.com (10.152.82.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.20 via Frontend Transport; Mon, 3 Aug 2020 12:30:48 +0000 Received: by mail-ej1-f45.google.com with SMTP id o18so38401819eje.7 for ; Mon, 03 Aug 2020 05:30:48 -0700 (PDT) From: RussellMc To: Microcontroller discussion list - Public. CC: ApptechNZ Sender: "piclist-bounces@mit.edu" Date: Mon, 3 Aug 2020 05:30:09 -0700 Subject: Re: [EE] "Tactile" spec? Thread-Topic: [EE] "Tactile" spec? Thread-Index: AdZpkz9U6dZfFzPHS2C4mfPruXSzOA== Message-ID: References: <5F2583C6.6070307@narwani.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5F2583C6.6070307@narwani.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 gmail.com designates 209.85.218.45 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.45; helo=mail-ej1-f45.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RmEvdecN/XOiIjTTNFRh4c5DFKs2xqFN1OsQ5QxVULI=; b=hCpW49kn3GN05th+SUDBuNW5GpO7B5qgvLEJ4X21kc44GPnQoLi6hDqpOTHWsKsOe7 OBjtLd3Nof41RUfVlXKT8Zf9+0T6NLec5plKoTRw2mu7dEMFHGR2NwydRESFnMzVtZba gy39sdoH9Xf+xMx/dTyxrdRQgXQwr6d03BVY+BjAcRbtB8BhQGbNPyrP6GD/kBCMe9M7 m68kMkSmb7pFIcCFA/1z3LnNQJi2gte4vyTTzN/Hs9cmnoKm1TEK/iiKtDf76YylMaKe yCA0cjSzC/eZZ1LV+HnE2CM+SrRogNOAPFqriPxsyjx0sPNbYRtMY55NiCpGgvEi7DKw rYaQ== authentication-results: spf=pass (sender IP is 209.85.218.45) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.com; 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:906:4c97:: with SMTP id q23mr3248633eju.11.1596457846640; Mon, 03 Aug 2020 05:30:46 -0700 (PDT) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Sun, 2 Aug 2020 at 03:02, Neil wrote: > Is there some way to tell from a datasheet if a switch is "clicky"/tactil= e? > > As others have noted - "tact" switches are liable to suit. Others may. Possibly worth noting - if operating force range is of concern then specifying it may be a good idea. I long ago had a batch of multi layer mylar keyboards made. Non tactile. Maybe 50? keyboards - NZ made so not overly cheap. 3 layers - x contacts on top layer , y contacts at 90 degrees on bottom layer and a hole at key locations in middle layer. Laminate / glue. Operating force depends on hole size, material and middle layer thickness. I had a very specific requirement for operating force. I wrote a spec re operating finger size and operating force. I took the really-didn't-care manufacturer through it line by line and got a spec signoff. The resultant keyboards were all several times higher in operating force than per spec. I had him redo them. The originals would have been usable in 'normal' applications but were non standard enough that odds are he just wrote them off. Russell --=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 .