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, 16 Sep 2021 02:45:45 -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 18G9X7Tk015850; Thu, 16 Sep 2021 05:34:13 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 18G9X6EQ015847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Thu, 16 Sep 2021 05:33:06 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 18G9X0VF028465 for ; Thu, 16 Sep 2021 05:33:06 -0400 Received: from oc11expo8.exchange.mit.edu (18.9.4.13) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Thu, 16 Sep 2021 05:32:57 -0400 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by oc11expo8.exchange.mit.edu (18.9.4.13) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Thu, 16 Sep 2021 05:32:39 -0400 Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.101) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Thu, 16 Sep 2021 05:32:39 -0400 Received: from BN9PR03CA0939.namprd03.prod.outlook.com (2603:10b6:408:108::14) by CY1PR01MB2124.prod.exchangelabs.com (2a01:111:e400:c614::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4500.19; Thu, 16 Sep 2021 09:32:55 +0000 Received: from BN8NAM11FT023.eop-nam11.prod.protection.outlook.com (2603:10b6:408:108:cafe::6e) by BN9PR03CA0939.outlook.office365.com (2603:10b6:408:108::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4523.16 via Frontend Transport; Thu, 16 Sep 2021 09:32:54 +0000 Received: from mail-yb1-f179.google.com (209.85.219.179) by BN8NAM11FT023.mail.protection.outlook.com (10.13.177.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4523.14 via Frontend Transport; Thu, 16 Sep 2021 09:32:54 +0000 Received: by mail-yb1-f179.google.com with SMTP id c6so11629512ybm.10 for ; Thu, 16 Sep 2021 02:32:54 -0700 (PDT) From: Justin Richards To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Thu, 16 Sep 2021 02:32:51 -0700 Subject: Re: [EE] Oscilloscope help, Siglent, Rigol, etc Thread-Topic: [EE] Oscilloscope help, Siglent, Rigol, etc Thread-Index: Adeq359bq+JGqWnRTh603lzzs+UFwA== Message-ID: References: <613fd508.1c69fb81.ef182.9aff@mx.google.com> <5c94b2ca-2839-40c6-db7c-3c26ba69d4c5@gmail.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5c94b2ca-2839-40c6-db7c-3c26ba69d4c5@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: Pass (protection.outlook.com: domain of gmail.com designates 209.85.219.179 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.219.179; helo=mail-yb1-f179.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=AdJopppoXm/YaPxtwq8dpzo3xqaHCL5TIYlYki+Ims4=; b=M+XTSjPEJd68gy2k+TFopjbjgwXv3IwCPPdNR9hnWmPZoL59C2Zknd5LCrVb8dA+V1 c7hCcXVeJvyu3/hpx21cN3I730S4wWIMCStunaHCGQ8MPUHVLzmo8xSdXJrJLZMRt7ZI JJh8T8aVkFkzof6WoBq68ogKGK77c2gpeonWfknhkRxi0bsyenH37oG+pkFBVASMcIvF m3T9p1kWLV8cLy8VL+AhOVvo20xMU+AznKhTTcxG95vn9qS0bQ5iirBKAhh0/FEbnLhT nlg3Bw9FqBeDuN1NBugSbiuSpriCZo7LnEqSEV9UkmK7TCrmpt3fucfjnaD3IQ1gmcS8 zCuw== authentication-results: spf=pass (sender IP is 209.85.219.179) 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:a05:6902:1547:: with SMTP id r7mr5825626ybu.72.1631784774103; Thu, 16 Sep 2021 02:32:54 -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 I am reasonably happy with my DS1054Z especially after I added the options. It was easy to control via SCPI (via ethernet) to use as a datalogger, basic DSA etc and is generally intuitive to use. It is possible to simply use python to Telnet on port 5555 (removes the need to install VISA) and then status and control, get screen shots etc. I was able to help my daughter do uni stuff from a 1000kms away. She would make circuit changes, then I would take a screen shot etc, advise and/or make control changes. So yes, all very do-able. Clunky but do-able. I was disappointed when attempting to use the math operation, Its a while ago now but I think I wanted to see if it could measure gain as the freq was swept by math-ing input/output and it just lost the plot :). I may have been doing something wrong but I recall successfully doing something similar on another scope. Again, this was solvable using python to get channel values then do the math in python. However, I think the Siglent is a good alternative and I would struggle with the decision. Siglent mentions it comes with decoding options and it seems they have been working hard to make some competitive test equipment. Not sure if it has a telnet feature. No Telnet would almost be a deal breaker for me as it makes it so much easier to quickly do stuff remotely and automated, which I seem to use often. Justin On Tue, Sep 14, 2021 at 8:18 AM DrSkip wrote: > Greetings, > > I need some help to pass on, and also to bring myself out of the Dark > Ages. A friend recently asked me for a scope recommendation. He is > looking at a Rigol or a Siglent. I have a dusty Tek 475A analog scope > that weighs maybe 50 lbs, so I am not qualified to answer, but I do know > folks to ask... ;) > > The models are: > > https://smile.amazon.com/gp/product/B0771N1ZF9 > > or > > https://www.amazon.com/gp/product/B077LSG5P2 with such 'free' addons > as: MSO/DS1000Z AT-DS1000Z - Advanced Triggering Option MEM-DS1000Z - > Memory Depth Upgrade REC-DS1000Z - Real Time Waveform Record and Relay > Option SA-DS1000Z - Serial Bus Analysis... > > This is for personal use, he tinkers with microcontrollers and Arduino, > Pi's, Ham Radio, and all the common popular maker topics I suppose. To > that level he knows how to get around. I know that these have two > different bandwidth specs, but I think that doesn't matter much for > these activities (am I correct? ). I think being able to do bus > analysis, spectral analysis, link to a pc, and so on is really cool - IF > they really do that and it isn't marketing fluff. Is there some > feature(s) that dwarfs overall bandwidth as being important in the > digital world? > > Given that each company uses it's own marketing-speak, I can't even do a > good comparison for him. Also, how do the implementations of similar > functions compare? Which company is better? Which device does basic > scope functions better? I list the Rigol options for example - they > 'say' little on their own. > > I suggested he stick with 4 channel ones. I assume the bus analysis > would need at least that. Beyond that, I can't tell what he gets with > one or loses with the other, OR what is honest versus salesmanship... > > Has anyone compared these? How are they? Reliability? Accuracy? Any > killer function one has that the other doesn't for micro type work? Is > one a true superset of ability over the other, or is it a list of > tradeoffs? If so, what are the tradeoffs, one versus the other? I'm also > going to assume that any upgrade hacks one can find on the net don't > work by now, so it's just going to be as it comes. > > I don't even know if you have to upgrade the firmware on these things or > if that's even a good idea. Ideas on that too? > > Thanks in advance for all long and lengthy educational and opinion > pieces, and/or reliable links. ;) I'm not gonna sell or give him my > 475A (deluxe model with attached DVM) so he has to buy his own. ;) > > > -Dr Skip > > > > -- > 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 .