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, 25 Jan 2020 13:50:27 -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 00PLdpn3005468; Sat, 25 Jan 2020 16:42:16 -0500 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 00PLdoaL005465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 25 Jan 2020 16:39:50 -0500 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 00PLeNes029440 for ; Sat, 25 Jan 2020 16:40:28 -0500 Received: from w92expo21.exchange.mit.edu (18.7.74.75) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sat, 25 Jan 2020 16:39:30 -0500 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92expo21.exchange.mit.edu (18.7.74.75) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sat, 25 Jan 2020 16:39:49 -0500 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.168) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sat, 25 Jan 2020 16:39:49 -0500 Received: from SN2PR01CA0082.prod.exchangelabs.com (2603:10b6:800::50) by BL0PR01MB4468.prod.exchangelabs.com (2603:10b6:208:82::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.24; Sat, 25 Jan 2020 21:39:47 +0000 Received: from CO1NAM03FT043.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::203) by SN2PR01CA0082.outlook.office365.com (2603:10b6:800::50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.22 via Frontend Transport; Sat, 25 Jan 2020 21:39:46 +0000 Received: from mail-wr1-f51.google.com (209.85.221.51) by CO1NAM03FT043.mail.protection.outlook.com (10.152.81.125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.18 via Frontend Transport; Sat, 25 Jan 2020 21:39:46 +0000 Received: by mail-wr1-f51.google.com with SMTP id g17so6325633wro.2 for ; Sat, 25 Jan 2020 13:39:46 -0800 (PST) From: c h To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sat, 25 Jan 2020 13:39:33 -0800 Subject: Re: [EE] Locating object position by radio Thread-Topic: [EE] Locating object position by radio Thread-Index: AdXTyXT99VBTSfSIRdyh8klvYCuKMw== Message-ID: References: <5D9B4DF8.8070801@narwani.org> <523012308.3019897.1570461495196@mail.yahoo.com> <5D9B7E46.1010901@narwani.org> <5D9B86DF.9080905@narwani.org> <5D9BA675.2090509@narwani.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5D9BA675.2090509@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.221.51 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.221.51; helo=mail-wr1-f51.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=xWt5+wakWINg2Sldr7QJ/7cUUAq1xNe1jAbiyt8zytA=; b=J9HJFVgcwnBrEKqlvDt7a9jTz1drxMXRcbzm3Ma0JKUFx8RJbdjbNfkLjewW7SC2pn jDUYSl8sgptuWSu6WoczYeIONqEzXFh2X6Q4Aadrd4SrXploCPj1RRxSxm200DYUH0Fu RlyXnttuAehq+nC/BCFLA5PMuO6Is117Hc7YJFnxHbS2NFLo00HRKhuwgAr/yJsF0+Md khmiVHHCW48XkLum+vU3j5IB/2U8tcNVZ+d9mNaN3oo19uqhJC+JIwWUSHswPsKK4g53 djQETMLI953s95t3r1Co+MTiFD7ygLl+jhznDzJtgz+fHGOIaOP3qUv3kSitIa7wVQcX So0Q== authentication-results: spf=pass (sender IP is 209.85.221.51) 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;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:adf:f606:: with SMTP id t6mr11515418wrp.85.1579988385151; Sat, 25 Jan 2020 13:39:45 -0800 (PST) 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 Mon, Oct 7, 2019 at 11:59 PM Neil wrote: > > "precise" (within a few feet) location. I want to calculate the > trajectory afterwards, so it doesn't need to be live. > That's the job for AI. Move the transmitting robot all over the field and have him record its position in time. Record the signal on all stations. And let AI to deep learn the patterns. And later, over the pattern of other transmitting device the AI would figure out the position of the device. --=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 .