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; Thu, 1 Oct 2020 12:19:53 -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 091J9aS0014890; Thu, 1 Oct 2020 15:09:45 -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 091J9ZlW014887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 1 Oct 2020 15:09:35 -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 091J9KuY012534 for ; Thu, 1 Oct 2020 15:09:35 -0400 Received: from w92exhyb6.exchange.mit.edu (18.7.71.111) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 1 Oct 2020 15:08:35 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92exhyb6.exchange.mit.edu (18.7.71.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 1 Oct 2020 15:09:15 -0400 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.108) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 1 Oct 2020 15:09:14 -0400 Received: from DM5PR10CA0005.namprd10.prod.outlook.com (2603:10b6:4:2::15) by SN6PR01MB5247.prod.exchangelabs.com (2603:10b6:805:d2::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.35; Thu, 1 Oct 2020 19:09:13 +0000 Received: from DM3NAM03FT048.eop-NAM03.prod.protection.outlook.com (2603:10b6:4:2:cafe::2c) by DM5PR10CA0005.outlook.office365.com (2603:10b6:4:2::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.32 via Frontend Transport; Thu, 1 Oct 2020 19:09:13 +0000 Received: from mail-lj1-f178.google.com (209.85.208.178) by DM3NAM03FT048.mail.protection.outlook.com (10.152.83.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.34 via Frontend Transport; Thu, 1 Oct 2020 19:09:13 +0000 Received: by mail-lj1-f178.google.com with SMTP id u21so5588428ljl.6 for ; Thu, 01 Oct 2020 12:09:13 -0700 (PDT) From: Alan Pearce To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Thu, 1 Oct 2020 12:09:00 -0700 Subject: Re: [EE] RS-485 analyzer/sniffer? Thread-Topic: [EE] RS-485 analyzer/sniffer? Thread-Index: AdaYJ9dAgdOolWS+TCCCVMkLBbv+FQ== Message-ID: References: <5F7619A5.1030407@narwani.org> 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: TempError X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of googlemail.com designates 209.85.208.178 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.178; helo=mail-lj1-f178.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=MvtrKDZzIHpOmGi4V/ld6g0mvJm2AAuFXt5fMGeanKc=; b=r1F8KE7+pNQ6u4QyixaX1BCpWOSC2v/bi3BdNpS5FwXQK6Bn58h85RNBKv5MVfhh0+ gLNZU/GjP4xNdO5UYRgNQX/HK0RXZzH9oSz2qgKZ5W/tiCG335k877yoJhSHmWqF23ne CIHbJYpkOygJmPqRuyqd+u2y7LbC0e5UXBgg5XR6J66N9r7l+oFO9bBy/ZDk5zMIWbwW 6W1jxUzM7jOWXgYbHt27HwPntYdcxWH1XyvzrwIHuJOPZRMlv9kQib6yh+U7zvlznEZ2 SP6aG/JqIk0A848IBtejmEDdWK6QvJlmb8cZb15IfKK3Z6BTeaMr11VTCzjtcvJbkCJR kpGA== authentication-results: spf=pass (sender IP is 209.85.208.178) smtp.mailfrom=googlemail.com; mit.edu; dkim=pass (signature was verified) header.d=googlemail.com;mit.edu; dmarc=pass action=none header.from=googlemail.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:a2e:880d:: with SMTP id x13mr2946665ljh.20.1601579351575; Thu, 01 Oct 2020 12:09:11 -0700 (PDT) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Follow-up, here is one on Amazon ... https://www.amazon.com/DSD-TECH-SH-U11L-RS485-Chip-1-5M/dp/B08DXRKFZR/ref= =3Dsr_1_48?dchild=3D1&keywords=3DUSB+RS485&qid=3D1600139586&sr=3D8-48&pldnS= ite=3D1 On Thu, 1 Oct 2020 at 20:01, Alan Pearce wr= ote: > > There are USB-485 dongles out there, so use one of these with normal > terminal software? > Or come up with your own program to interpret the data stream if it > isn't printable characters. > > On Thu, 1 Oct 2020 at 19:05, Neil wrote: > > > > Anyone have a recommendation for a budget RS-485 sniffer/analyzer? > > With software, under $50 would be nice. Under $100 is workable. > > Will be testing some things for someone else for a few weeks, so it's > > not something I do regularly enough to warrany buying a fancy tester. > > > > 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 .