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; Sat, 18 Jan 2020 14:19: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 00IM7e73024887; Sat, 18 Jan 2020 17:10:06 -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 00IM7dUr024884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 18 Jan 2020 17:07:40 -0500 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 00IMAG28009541 for ; Sat, 18 Jan 2020 17:10:16 -0500 Received: from w92expo22.exchange.mit.edu (18.7.74.76) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sat, 18 Jan 2020 17:05:59 -0500 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by w92expo22.exchange.mit.edu (18.7.74.76) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sat, 18 Jan 2020 17:07:39 -0500 Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.102) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sat, 18 Jan 2020 17:07:38 -0500 Received: from SN2PR01CA0059.prod.exchangelabs.com (2603:10b6:800::27) by DM6PR01MB5578.prod.exchangelabs.com (2603:10b6:5:17c::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.24; Sat, 18 Jan 2020 22:07:37 +0000 Received: from CO1NAM03FT040.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::201) by SN2PR01CA0059.outlook.office365.com (2603:10b6:800::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.21 via Frontend Transport; Sat, 18 Jan 2020 22:07:37 +0000 Received: from mulvey.us (24.169.71.174) by CO1NAM03FT040.mail.protection.outlook.com (10.152.81.183) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2644.19 via Frontend Transport; Sat, 18 Jan 2020 22:07:36 +0000 Received: from Win10Pro ([192.168.100.56]) by mulvey.us with MailEnable ESMTPA; Sat, 18 Jan 2020 17:07:34 -0500 From: Allen Mulvey To: 'Microcontroller discussion list - Public.' Sender: "piclist-bounces@mit.edu" Date: Sat, 18 Jan 2020 14:07:34 -0800 Subject: RE: [CAUTION: Failed DKIM Test][EE] Magnetic lock Thread-Topic: [CAUTION: Failed DKIM Test][EE] Magnetic lock Thread-Index: AQK+Y/I4/t93DYqUdkj2PWXJobLWf6YfzrgQ Message-ID: <001c01d5ce4b$afa28370$0ee78a50$@amulvey.com> References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-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 amulvey.com designates 24.169.71.174 as permitted sender) receiver=protection.outlook.com; client-ip=24.169.71.174; helo=mulvey.us; dkim-signature: v=1; c=relaxed/relaxed; h=from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding; d=amulvey.com; s=amulvey; a=rsa-sha256; bh=oDMfT8YUfBPwieRDl5NueZbIP91GkTfhe5bicoft5Fg=; b=T/FDW2jAubuU9Eim9sq2NEFwKlA0eYIkxBNsKItAtyM1+Mn/MKztFtrOJW4quttO8 DWH/g+4RKhxlGDYMEG6E7bqzs4DQwga4uLVNhtDNKdgS/4HQqqGsyVa4airViC989aP AyT8sW/igz4DLIvR8kHmBrdWobcPD1CgzsV+ftU=; authentication-results: spf=pass (sender IP is 24.169.71.174) smtp.mailfrom=amulvey.com; mit.edu; dkim=pass (signature was verified) header.d=amulvey.com;mit.edu; dmarc=bestguesspass action=none header.from=amulvey.com;compauth=pass reason=109 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: [EE] x-me-bayesian: 0.000000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Is there a small plunger connected to a microswitch which detects the physical contact? Allen PS: I use a pair of 600 pounders on my front door with magnetic strikes everywhere else. -----Original Message----- From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of David C Brown Sent: Saturday, January 18, 2020 4:27 PM To: Microcontroller discussion list - Public. Subject: [CAUTION: Failed DKIM Test][EE] Magnetic lock I have just purchased a magnetic lock for my workshop so that I can dispense with using metal tokens to free the door. The lock consists of an armature plate which bolts to the door and an electromagnet which, when energised, grabs the armature with a force of several hundred pounds. I splashed out an extra fiver for the "monitored" version which lights an LED anf operates a relay when the device detects that the armature is held by the magnet. But how does it detect the locked condition? Does the current in the magnet increase when something is attracted by it? Or what? __________________________________________ David C Brown 43 Bings Road Whaley Bridge High Peak Phone: 01663 733236 Derbyshire eMail: dcb.home@gmail.com SK23 7ND web: www.bings-knowle.co.uk/dcb *Sent from my etch-a-sketch* --=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 --=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 .