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, 2 Oct 2020 13:10:25 -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 092Jvh7w029826; Fri, 2 Oct 2020 15:58:18 -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 092Jvg5Q029822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 2 Oct 2020 15:57:42 -0400 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 092JvZI6008978 for ; Fri, 2 Oct 2020 15:57:41 -0400 Received: from w92expo26.exchange.mit.edu (18.7.74.32) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 2 Oct 2020 15:56:50 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92expo26.exchange.mit.edu (18.7.74.32) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 2 Oct 2020 15:57:36 -0400 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.176) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 2 Oct 2020 15:57:36 -0400 Received: from CO1PR15CA0069.namprd15.prod.outlook.com (2603:10b6:101:20::13) by CY4PR01MB2630.prod.exchangelabs.com (2603:10b6:903:e6::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.36; Fri, 2 Oct 2020 19:57:35 +0000 Received: from CO1NAM03FT011.eop-NAM03.prod.protection.outlook.com (2603:10b6:101:20:cafe::b8) by CO1PR15CA0069.outlook.office365.com (2603:10b6:101:20::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.32 via Frontend Transport; Fri, 2 Oct 2020 19:57:34 +0000 Received: from mail-lf1-f48.google.com (209.85.167.48) by CO1NAM03FT011.mail.protection.outlook.com (10.152.80.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.34 via Frontend Transport; Fri, 2 Oct 2020 19:57:34 +0000 Received: by mail-lf1-f48.google.com with SMTP id y11so3298797lfl.5 for ; Fri, 02 Oct 2020 12:57:34 -0700 (PDT) From: mike brown To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 2 Oct 2020 12:57:18 -0700 Subject: Re: [EE] RS-485 analyzer/sniffer? Thread-Topic: [EE] RS-485 analyzer/sniffer? Thread-Index: AdaY+BGB7NZzrQtDQ7mfQBORhEItZA== Message-ID: References: <5F7619A5.1030407@narwani.org> <5F762F17.2080803@narwani.org> <024701d69831$71ddd070$55997150$@gmail.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <024701d69831$71ddd070$55997150$@gmail.com> 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: None (protection.outlook.com: n5qmg.com does not designate permitted sender hosts) dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=n5qmg-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=fCuTANf32VxqrEyWGNrDXQasac7+5ckXzpJUfMxukJU=; b=fVayYz8Uk/qdTHQbGRccxNbM1LzrQpDujDdsHLAIDbhdB4ePcFDEwS4AspKGC85jK1 DjJ8/GlzltNE76CtXVZoX6Y9lxj07BNMMEFIFtkhTBVrRCc4vU1LKYy9/M1tM8sm8drA 9RRQmuSmmJLTBoArg1Mlmu6D9gLILnNRcK3quCVxLr2dGBrS8Uf5u+U1ZTIAl33SxDbl 6TJV/Drk6mqQeC2Q+eSQT3wkL+YXYvbGmtgAX4SfFaLVBJXp3fmKvzYA9KAzCqpnbrhY 1bMaL/UbX8tYtPBwfQjHlhGWO4KyjTeXht8KGJD3dexixq0KxpkxMrDTM5IVqYvv2b1E 5nXg== authentication-results: spf=none (sender IP is 209.85.167.48) smtp.mailfrom=n5qmg.com; mit.edu; dkim=pass (signature was verified) header.d=n5qmg-com.20150623.gappssmtp.com; mit.edu; dmarc=none action=none header.from=n5qmg.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:ac2:4c11:: with SMTP id t17mr1531097lfq.260.1601668651268; Fri, 02 Oct 2020 12:57: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 Disclaimer: This may or may not be a controversial statement. I'd recommend one of the super cheap ($10ish) Salae (sp?) clones. They do 8 channels at up to 24MHZ, no serious input protection or fancy probe connectors, just raw IDC pins. You might want to put some blocking resistors to limit input current, depending upon the voltages you anticipate. You'd have to verify, but I think the pins can survive + or - 20V, I just don't remember. If you burn out a channel, who cares, rig up something to protect the ones left. ;) Buy them by the dozen and throw one in every toolbox. But you don't have to use a $10 clone of an ancient analyzer, it works with all kinds of analyzers. I don't recommend using official Salae software, but Sigrok Pulseview instead. It runs in Windows or Linux, there's even an Android app. I've only tinkered with a bit, but I think it's pretty awesome for open source software. There's a jillian "stackable" protocol decoders built in. It's awesome, seriously. It "knows" the various UART, I2C and SPI protocols to talk to a plethora of various chips. The wiki write up on Sigrok Pulseview is very detailed. When I said stackable, that's what I meant, it's nice to look at I2C comms and not have to have a datasheet in hand for an ADC or some other IC that's on the bus, trying to figure out what's going wrong. Just take a look at this list: https://sigrok.org/wiki/Protocol_decoders It even flags missing acks, parity or framing errors. Did I mention that it's awesome? I'm still waiting for a Rigol scope, or any affordable scope, to embed this ability into their serial decoder functionality. Pulseview can even talk to oscilloscopes; it's not just limited to logic analyzers. You can capture analog signals, convert them to digital day streams (using thresholds of your choice) and feed them into the protocol analyzers. I even use Pulseview with my Hantek 6022bl, it's got a nicer interface. Capturing analog inputs and automatically converting them to a logic stream comes in handy. It can even guess at baud rates, if you're unsure. It can do timing analysis. I don't know what else it can do, but there's probably more. Be forewarned, capturing at 24MHZ from an unbuffered clone device requires a decent computer and a good USB cable, but it works. You can record as many samples as you want, as long as the PC can keep up transferring 24 megabytes per second. The clones seem to sample all 8 inputs, whether you need them or not. It's $10, what can you expect. Here's on for $9, but mine is by hiletgo and cost $12 for the "kit". It looks just like this one. As long as you don't use Salea software, no crime has occurred, nobody was harmed in any way, just a reappropriated USB VID and PID. It's certainly not the same quality hardware as the original version. https://www.amazon.com/Comidox-Analyzer-Device-Channel-Arduino/dp/B07KW445D= J/ref=3Dasc_df_B07KW445DJ/?tag=3Dhyprod-20&linkCode=3Ddf0&hvadid=3D36628958= 1070&hvpos=3D&hvnetw=3Dg&hvrand=3D2425961148164562015&hvpone=3D&hvptwo=3D&h= vqmt=3D&hvdev=3Dm&hvdvcmdl=3D&hvlocint=3D&hvlocphy=3D9052205&hvtargid=3Dpla= -804742835968&psc=3D1&tag=3D&ref=3D&adgrpid=3D71490160010&hvpone=3D&hvptwo= =3D&hvadid=3D366289581070&hvpos=3D&hvnetw=3Dg&hvrand=3D2425961148164562015&= hvqmt=3D&hvdev=3Dm&hvdvcmdl=3D&hvlocint=3D&hvlocphy=3D9052205&hvtargid=3Dpl= a-804742835968 On Thu, Oct 1, 2020, 15:38 mbaum7901 wrote: > I have used a free software package called TAL Breakout for over 15 years= .. > It is actually a demo of a commercial offering, but the free version work= s > very well > > https://www.taltech.com/blog/post/tal_breakout_software_freeware > > > -----Original Message----- > From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf > Of > Harold Hallikainen > Sent: Thursday, October 01, 2020 15:04 > To: Microcontroller discussion list - Public. > Subject: Re: [EE] RS-485 analyzer/sniffer? > > I've used a logic analyzer like the thech-tools DigiView to watch a 485 b= us > directly. No 485 receiver required since one wire or the other is 5V seri= al > data. Also, RealTerm can capture serial data and display it in hex. > I use an FTDI TTL-232R-5V-WE cable to get TTL or similar level data into = a > USB comm port. > > Harold > > > -- > FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an > iPhone. > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change > your membership options at http://mailman.mit.edu/mailman/listinfo/piclis= t > > -- > 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 .