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; Fri, 18 Sep 2020 13:01:57 -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 08IJpUoi026123; Fri, 18 Sep 2020 15:51:49 -0400 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 08IJpSsH026035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 18 Sep 2020 15:51:28 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 08IJpJDu022419 for ; Fri, 18 Sep 2020 15:51:28 -0400 Received: from w92expo28.exchange.mit.edu (18.7.74.34) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 18 Sep 2020 15:50:53 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92expo28.exchange.mit.edu (18.7.74.34) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 18 Sep 2020 15:51:10 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.108) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 18 Sep 2020 15:51:10 -0400 Received: from DM5PR07CA0165.namprd07.prod.outlook.com (2603:10b6:3:ee::31) by DM5PR01MB2716.prod.exchangelabs.com (2603:10b6:3:f8::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Fri, 18 Sep 2020 19:51:09 +0000 Received: from DM3NAM03FT061.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:ee:cafe::f7) by DM5PR07CA0165.outlook.office365.com (2603:10b6:3:ee::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3391.11 via Frontend Transport; Fri, 18 Sep 2020 19:51:09 +0000 Received: from mail-wm1-f45.google.com (209.85.128.45) by DM3NAM03FT061.mail.protection.outlook.com (10.152.83.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3391.15 via Frontend Transport; Fri, 18 Sep 2020 19:51:09 +0000 Received: by mail-wm1-f45.google.com with SMTP id l9so6698348wme.3 for ; Fri, 18 Sep 2020 12:51:09 -0700 (PDT) From: Denny Esterline To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 18 Sep 2020 12:50:56 -0700 Subject: Re: [EE] light sensor array? Thread-Topic: [EE] light sensor array? Thread-Index: AdaN9pCKdGscxpyMTnajtKZZkBP5Tg== Message-ID: References: <5F65066E.6040408@narwani.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5F65066E.6040408@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: 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.128.45 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.128.45; helo=mail-wm1-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; bh=boMq45WKByWD5wLC1/iWFX1GpNrBTpRoV0EHmbDKeMU=; b=U8UwM0+Ak+vgUXMPc+NHaDhJdj5XiE1vdtBc+n0zdgtZLlyMlOVIRbpBRVbXdRJ2hA i1v3e+wmrCzuRQ8kLAFHvtXGxq574DX0XI6kBZDz8TElY2rVzHTf6njDhouDscpPq46Z SInsjwKc13Esytp8NMYvE04p6H3x4tdCrIkizcxxZICc2wDbUI9qATmWJ4+Rebu2U1eY x9XIvo/WUJSYGmDqWeZPzV9HoQMQXWx9+RvvZkGfC7sPsiGRXXzsYcd+2oUNGnfeew1D JUhs2EJx/SmhMXy98J0/9C2XJFUOsvJFMoAYy5wb3n+v6sFoajj+bi0HFBfL+d3VV1TJ 7H2w== authentication-results: spf=pass (sender IP is 209.85.128.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:a7b:c085:: with SMTP id r5mr18160595wmh.52.1600458668181; Fri, 18 Sep 2020 12:51:08 -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 That's a pretty wide open description, but one thought that occurs is construction surveying laser receivers. A couple different categories, some handheld with a display of some sort, the other type gets mounted to earthmoving equipment (bulldozers, etc) and has an output that is used to control the grade height. No experience with this company, but their web site shows several options of both types and has listed pricing: https://www.engineersupply.com/construction-lasers.aspx Look for "Laser Detectors" and "Machine Control Laser Detectors" Food for thought at least. -Denny On Fri, Sep 18, 2020 at 12:15 PM Neil wrote: > I want to measure the position (height) of a laser line level (device > that projects a horizontal line of light). 2" of measurement would be > nice, 1" I'd say is minimum. > > First thought is that I could use a light sensor array (such as in a > sheet scanner), but this is a one-off project, and I'm not up for > finding one that I can hack and then trying to reverse engineer it right > now. > The ones I'm finding on Digikey etc (which will have datasheets) are > low-cost enough ($10-$20), but either have a very short range (~0.5" or > less), or the longer ones are discontinued. > Any recommendations for one of these? I don't need high resolution > (even 1mm is fine). > > Yes, I could put the sensor on a linear servo, but then I'd have to > ensure that mechanism is tight and not introduce any noticeable errors > in the system. > > Alternate option is to let the light hit a diffuser (like say parchment > paper) and use a camera on the other side to detect the height of the > light line. I'd have to (finally) learn openCV perhaps, but that's prob > fine. > > Still thinking of other ways to do this too, even perhaps a curved lens > or mirror to compress a couple inches of range down to fit one of the > available sensors. > > Brainstormy thoughts appreciated. > > Cheers, > -Neil. > > > -- > 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 .