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, 10 Aug 2020 15:20:28 -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 07AMBrk4013937; Mon, 10 Aug 2020 18:12:23 -0400 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 07AMBrOI013934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 10 Aug 2020 18:11:53 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 07AM9PPF003781 for ; Mon, 10 Aug 2020 18:09:52 -0400 Received: from oc11expo31.exchange.mit.edu (18.9.4.104) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 10 Aug 2020 18:11:10 -0400 Received: from oc11exhyb1.exchange.mit.edu (18.9.1.60) by oc11expo31.exchange.mit.edu (18.9.4.104) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 10 Aug 2020 18:11:35 -0400 Received: from NAM04-MW2-obe.outbound.protection.outlook.com (104.47.73.177) by oc11exhyb1.exchange.mit.edu (18.9.1.60) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 10 Aug 2020 18:11:35 -0400 Received: from DM5PR19CA0013.namprd19.prod.outlook.com (2603:10b6:3:151::23) by BYAPR01MB4310.prod.exchangelabs.com (2603:10b6:a03:5d::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.22; Mon, 10 Aug 2020 22:11:33 +0000 Received: from DM3NAM03FT065.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:151:cafe::5f) by DM5PR19CA0013.outlook.office365.com (2603:10b6:3:151::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.16 via Frontend Transport; Mon, 10 Aug 2020 22:11:33 +0000 Received: from mail-ej1-f42.google.com (209.85.218.42) by DM3NAM03FT065.mail.protection.outlook.com (10.152.82.254) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3261.16 via Frontend Transport; Mon, 10 Aug 2020 22:11:33 +0000 Received: by mail-ej1-f42.google.com with SMTP id kq25so10977970ejb.3 for ; Mon, 10 Aug 2020 15:11:33 -0700 (PDT) From: Sean Breheny To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Mon, 10 Aug 2020 15:11:20 -0700 Subject: Re: [EE] averaging multiple samples to reject AC interference Thread-Topic: [EE] averaging multiple samples to reject AC interference Thread-Index: AdZvZHRoyFgXRqL5QXilDc3gZWz0Ow== Message-ID: References: <87ebbde6f2952158e80cf62518bc8745@mtlp000083> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <87ebbde6f2952158e80cf62518bc8745@mtlp000083> 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: TempError 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.42 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.42; helo=mail-ej1-f42.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cornell.edu; s=g.20171207; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ALbmcnKfqaA7YAIOIny8nrPo88GhBux3euob3ESVH7A=; b=bUGAJnRnhfRlFV7yhaR7QnoGs6+jjYnmdQhMAxZDt78fJ8fR/9SiO7Z4joIJKws61h LhcXQntsNeat4xTDawnXlGVcveVEWu8Q7M+qoSKoMLDScvlbUq0Z364xfgAGflvBTvTV mV60DJvCV9Pe5DiriwgbrLxK5RD3lfVKVHUMoFfOC0aiXaF4m/j4kKSzpgohe1FB+hHJ DTPnblGCJ64siQP4bB0fZjxhZkmEcXJtduNdM5xw0ANrZbc8QyJQO8DuqZ+aWOUHLweY n1bEulrxFmehflgzb1mPvTLbGveaIMB4ZSNA0Y2E8qgTBrYrQaT+Cjar7Bf0TZhwJqE6 VTMw== authentication-results: spf=pass (sender IP is 209.85.218.42) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=cornell.edu; mit.edu; dmarc=pass action=none header.from=cornell.edu; 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:d9db:: with SMTP id qk27mr23177517ejb.37.1597097491994; Mon, 10 Aug 2020 15:11:31 -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 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 up 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 continuousl= y. > > > >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 > --=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 .