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, 11 Aug 2020 02:19:09 -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 07B998i9031054; Tue, 11 Aug 2020 05:09:42 -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 07B996Kb031050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 11 Aug 2020 05:09:07 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 07B98gue029937 for ; Tue, 11 Aug 2020 05:08:49 -0400 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 11 Aug 2020 05:08:13 -0400 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Aug 2020 05:09:03 -0400 Received: from NAM02-SN1-obe.outbound.protection.outlook.com (104.47.57.49) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 11 Aug 2020 05:09:02 -0400 Received: from DM3PR12CA0048.namprd12.prod.outlook.com (2603:10b6:0:56::16) by BN8PR01MB5444.prod.exchangelabs.com (2603:10b6:408:b4::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.19; Tue, 11 Aug 2020 09:09:00 +0000 Received: from DM3NAM03FT014.eop-NAM03.prod.protection.outlook.com (2603:10b6:0:56:cafe::e5) by DM3PR12CA0048.outlook.office365.com (2603:10b6:0:56::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.20 via Frontend Transport; Tue, 11 Aug 2020 09:09:00 +0000 Received: from mail-ej1-f41.google.com (209.85.218.41) by DM3NAM03FT014.mail.protection.outlook.com (10.152.82.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.16 via Frontend Transport; Tue, 11 Aug 2020 09:09:00 +0000 Received: by mail-ej1-f41.google.com with SMTP id c16so12267764ejx.12 for ; Tue, 11 Aug 2020 02:09:00 -0700 (PDT) From: David C Brown To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 11 Aug 2020 02:08:50 -0700 Subject: Re: [EE] averaging multiple samples to reject AC interference Thread-Topic: [EE] averaging multiple samples to reject AC interference Thread-Index: AdZvwHi2YzQJ2d0RRWq+WUD4l8T+Cw== Message-ID: References: <87ebbde6f2952158e80cf62518bc8745@mtlp000083> 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 gmail.com designates 209.85.218.41 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.41; helo=mail-ej1-f41.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; bh=15waTnBHufit8aKJo5zDvBX4PKrcZSilZZVgMDcs6w0=; b=iugy4Uz7XKRqf+C0Q/e+cXBRSNo3UiiRTYp7gE7ofJR4CI9g6BOS32pHFU4EYUDmiH hzqMax8/L4rQ40FELEkDlYbSxZmZC2XKuCri5lYFXDGf33xZNxnaTQUlp0Xs/eRAkQJL Q7UqR/gxROlG8JN17bEKrxPkeM6IwgONmCFgLdRc1UjBuxcW66UsrhpOAEmq4DILQIN7 C2s8ri7oLmBDwZaInDcW3gAxsHkI2LWZo3rBMx0AR7ozNQoKjcGnvvOv+y3YGEUypqBJ XFcylP0p7CJFMufrKpOh4FMgoK2VNinZ5u4U5rUTcwamEHKUaVPYWYdQ065WE02YUZej JTUA== authentication-results: spf=pass (sender IP is 209.85.218.41) 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:c7c8:: with SMTP id dc8mr10103619ejb.399.1597136938721; Tue, 11 Aug 2020 02:08:58 -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 Does that mean that multimeters from America are disadvantaged in Europe? And vv? __________________________________________ 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* On Mon, 10 Aug 2020 at 23:12, Sean Breheny wrote: > Most multimeters still use dual-slope ADCs. One major advantage of this > technique (averaging over a multiple of the line frequency) is that it > actually places a notch (zero) of the transfer function at the line > frequency. It is MUCH better than simply a low-pass filter since it will > pass some frequencies above the line frequency and can pass frequencies u= p > to more than half the line frequency will very minimal attenuation. > > On Mon, Aug 10, 2020 at 4:15 PM Dwayne Reid > wrote: > > > Hi there, Bob. > > > > Old-time Dual-Slope digital meter systems did exactly what you > > describe, with great effectiveness. > > > > dwayne > > > > > > At 01:44 PM 8/10/2020, Bob Blick wrote: > > >I have sensors that feed an instrumentation amplifier running a > > >voltage gain of 10 before going into the A/D converter of a > > microcontroller. > > > > > >There is AC line interference. It is small, but if I can reduce the > > >effect, that would be good. I'm in the 60 Hertz part of the world, > > >but ultimately this will be used in both 50Hz and 60Hz locations. > > >Battery operated, this is not conducted interference or power supply > > >ripple. Shielding is not possible. I only need to process the signal > > >about 4 or 5 times per second. The signal is changing, so long-term > > >averaging is bad. Actually any averaging will result in a tradeoff > > >between response time and accuracy that I will need to evaluate. > > > > > >These sensors are multiplexed with others and I can't sample > continuously. > > > > > >If I average multiple samples taken at 1/300 second intervals over a > > >1/10 second period, that should give some improvement at 50Hz and > > >60Hz without getting too involved, correct? This would fit into my > > >existing multiplexing constraints. > > > > > >I seem to recall being in this situation before but forget what I > > >did at the time. > > > > > >Thanks for any suggestions. > > >Bob > > > > > > -- > > Dwayne Reid > > Trinity Electronics Systems Ltd Edmonton, AB, CANADA > > 780-489-3199 voice 780-487-6397 fax 888-489-3199 Toll Free > > www.trinity-electronics.com > > Custom Electronics Design and Manufacturing > > > > -- > > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > > View/change your membership options at > > http://mailman.mit.edu/mailman/listinfo/piclist > > > -- > 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 .