Help: My New Rigol DS1054Z Shows a Weird Double Trace - Page 1
Forum section: electronics / testgear

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 29, 2017, 10:51:12 pm
content: I just bought a Rigol DS1054Z and received it today.I've been playing with it a couple hours and can't figure out why it displays double traces. See the attached screenshots to see what I mean.It just looks like noise when the display type is set to vector, but it becomes two separate traces when set to dots. It doesn't matter what the signal source is, and it also does it if the probe is grounded. The behavior is identical on all four channels.I Googled the problem and found a Reddit thread posted by someone with theexactsame problem. They returned their unit and received a replacement with the same problem.https://www.reddit.com/r/AskElectronics/comments/5mi24b/recently_purchased_a_rigol_ds1054z_oscilliscope_i/Mine has firmware version 00.04.04.SP3 (which I think is the latest) and board version 0.1.4.I did a factory reset by pressing the fifth soft button to the left of the screen while booting, but that didn't make a difference. Doing the self calibration didn't help either. I have made no attempt to hack or upgrade the unit.The Reddit poster seems to think it is a firmware bug that causes the peak detect and normal acquisition modes to render simultaneously when in normal acquisition mode. And just like the Reddit poster, I also get a single trace only in high resolution acquisition mode.Does anyone know what's wrong with my oscilloscope and how to fix it?

author: Fungus
author_rank: Super Contributor
timestamp: November 30, 2017, 12:04:09 am
content: Quote from: Porcine Porcupine on November 29, 2017, 10:51:12 pmNope. If that was true then everybody else would be seeing it,Quote from: Porcine Porcupine on November 29, 2017, 10:51:12 pmIf you did a factory reset then I doubt it's the settings.What's your probe set to? 1x or 10x? How are you probing? Do you press the hook on until it clicks into place?What's your grounding like? Does your mains socket have a ground wire?

author: rhb
author_rank: Super Contributor
timestamp: November 30, 2017, 12:05:55 am
content: Connect the probe to the calibrator output. That should be a known good signal.

author: SkyMaster
author_rank: Frequent Contributor
timestamp: November 30, 2017, 12:10:06 am
content: Hi Porcine Porcupine,Do you have this problem only on channel 1, or on all of them?Are you using a probe? Did you try the other probes?

author: StillTrying
author_rank: Super Contributor
timestamp: November 30, 2017, 12:27:43 am
content: It certainly looks like peak detect, is the 2nd sine image triggering on the wrong edge?

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 01:16:37 am
content: Quote from: Fungus on November 30, 2017, 12:04:09 amI've tried a couple of the Rigol probes that came with the unit and another probe I already had. I've tried them on 1x and 10x. I pulled the hook off one of the Rigol probes and put it back. I connected the probe to the calibration output on the oscilloscope with and without the probe's ground clip connected to the ground tab under the signal output. I also connected a function generator to the oscilloscope through a BNC cable. The double trace was always there.Grounding should be good. The house I'm in was built about 30 years ago in compliance with the codes of the time. All the wall sockets have dedicated ground conductors. The ground and neutral wires are bonded only in the main breaker panel as they should be per the NEC, and the ground is connected to a copper ground rod driven into the ground near the main panel.I verified continuity between the oscilloscope's ground and the power cord's ground prong. I tried plugging the oscilloscope into a surge protector that provides filtering and directly into several wall sockets on different circuits, but the double trace persisted.Quote from: rhb on November 30, 2017, 12:05:55 amThe screenshot I posted of the square wave is the oscilloscope's calibration output. The sine wave in the other screenshot is from a function generator connected through a BNC cable.Quote from: SkyMaster on November 30, 2017, 12:10:06 amThe same double trace is displayed on all four channels.I've tried two of the supplied probes and a third one I already had. I also tried connecting the oscilloscope with a BNC cable to a function generator. The double trace is always there.Quote from: StillTrying on November 30, 2017, 12:27:43 amI'm not sure about the triggering. The sine wave looked a bit jittery like maybe it wasn't properly triggering consistently, but I attributed that to the cheap function generator (Sinometer VC2002) I was using.

author: alsetalokin4017
author_rank: Super Contributor
timestamp: November 30, 2017, 01:36:39 am
content: Well, isn't that strange. I can reproduce the issue exactly as described here and in the reddit thread.Even to the point of seeing the double trace when using the probe > FG but not when using a direct BNC patch cable connection from FG to scope.However I can also state that I have never seen any problem like this when actually using the scope with realistic settings to display actual signals from a DUT.My scope is running 00.04.04.03.02 ( aka 00.04.04.SP3) Board ver. 0.1.1Some example scopeshots from my actual usage of the scope: no such problem is evident.... So I'm going to fall back on the old joke:"Doctor, it only hurts when I do this!""Well, so don't do that!"(Or the ultimate Rigol comeback: It's only a 400 dollar scope, what did you expect?)

author: StillTrying
author_rank: Super Contributor
timestamp: November 30, 2017, 01:45:15 am
content: Quote from: Porcine Porcupine on November 30, 2017, 01:16:37 amI don't think there's any excuse for the wrong edge to be at the trigger position.Try to produce a 1 or 2 Vpp mains waveform by touching the probe tip to see if it's mains related.https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg1178338/#msg1178338https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg1178420/#msg1178420

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 02:02:43 am
content: Quote from: Fungus on November 30, 2017, 12:04:09 amI agree, but I wonder if maybe the firmware could be corrupt or something. I'm tempted to try reloading the firmware, but I'm not sure if it will allow that if it already has the latest version.Quote from: alsetalokin4017 on November 30, 2017, 01:36:39 amThat's interesting.All I had to do was connect the probe to the calibration output and hit the auto button to notice it. At first I thought it was a noisy calibration signal, but then I changed the display type to dots and saw the double trace. I found the Reddit thread immediately when I Googled it.I've hardly used an oscilloscope in the last 10 years, much less a modern digital one. I wasn't sure at first if it was just something stupid I was doing, but this seems to have others confused as well.

author: alsetalokin4017
author_rank: Super Contributor
timestamp: November 30, 2017, 02:10:07 am
content: I'd recommend just filing it as a bug report with Rigol, and then ignore it and use the scope normally. As I've shown it doesn't seem to affect (my) normal use of the scope.YMMV of course. Do you often find the need to use Dots display mode and very sensitive V/div settings?(As I have found when discussing this particular model scope, we will get answers and speculation from people who don't actually have this model scope, or who seldom use many of its features even if they do have it. If the problem can be resolved or worked around by using Peak Detect acquisition mode, that's good, right?)

author: alsetalokin4017
author_rank: Super Contributor
timestamp: November 30, 2017, 02:18:06 am
content: Except I do _not_ see the double trace when making the direct connection from FG to scope using a BNC patch cord. If I probe the FG output directly using the scope probe I do see the double trace, also when I use the probe on the end of the BNC cable from the FG.

author: tablatronix
author_rank: Regular Contributor
timestamp: November 30, 2017, 02:36:47 am
content: I was trying to post but this dumb forum keeps just going to a blank add new topic when i post.Forum has issues with ios 11 it now saves images as heifnor jpeg both which are not allowed to upload.Mine did this, it was fun.

author: jjoonathan
author_rank: Frequent Contributor
timestamp: November 30, 2017, 02:51:49 am
content: Have you checked continuity on the ground lead of the scope probe? EDIT: nevermind, you've tested multiple probes and a BNC to a FG.If you capture a single trace and zoom in using dots mode, do you see a regular pattern (e.g. every 4th dot is high)?If you use auto triggering with source = ac and zoom out to 10ms/div or in to the fastest timebase, do you see a regular pattern?

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 03:21:20 am
content: Quote from: StillTrying on November 30, 2017, 01:45:15 amI noticed with that signal it will swap edges as I adjust the triggering above and below zero. I think it might just be triggering on some noise or something.I attached some screenshots I took while touching the probe tip with my finger. I can't really tell if the double trace is there or not because the high frequency noise on the waveform might be hiding it.

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 03:36:30 am
content: Quote from: alsetalokin4017 on November 30, 2017, 02:10:07 amI doubt I'll often use the dots display. I only switched to dots to try to see what was going on here.As long as this isn't a physical defect with my oscilloscope, it isn't a big deal for me. It mostly concerns me because I would like to quickly (i.e. before I get around to doing anything that might void the warranty) resolve it with either Rigol or the vendor if this is a warranty issue.

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 03:40:00 am
content: Quote from: alsetalokin4017 on November 30, 2017, 02:18:06 amMaybe it is somehow caused by noise that's being picked up, and your BNC cable is shielded better than mine.

author: K5HJ
author_rank: Regular Contributor
timestamp: November 30, 2017, 04:20:53 am
content: The top of the trace is off of the screen. Looks like the ADC is in severe clipping.

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 04:59:28 am
content: Quote from: jjoonathan on November 30, 2017, 02:51:49 amIf I zoom in on a captured trace (screenshots 1-5), it becomes clear that what looked like two lines is actually two groups of three lines. Maybe it's just noise and looks this way because of quantization, but that doesn't explain why everyone doesn't see this on their DS1054Z.The 6th screenshot is 10 ms/div. Screenshots 7-9 show zooming in on a captured trace at 10 ms/div. The double traces go away at 200 µs and faster. Screenshots 10-13 are with it running, but the double trace doesn't go away until 20 µs or faster.

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 05:11:03 am
content: Quote from: K5HJ on November 30, 2017, 04:20:53 amIt's off the screen because I adjusted the vertical position and scale. You can still see the double traces in the attached screenshot showing the full vertical extent of the waveform.

author: technogeeky
author_rank: Frequent Contributor
timestamp: November 30, 2017, 05:15:14 am
content: Quote from: Porcine Porcupine on November 30, 2017, 05:11:03 amYeah. There's something wrong with that scope. I would request a replacement.

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 05:36:23 am
content: Quote from: technogeeky on November 30, 2017, 05:15:14 amI'm afraid that's what I'm going to have to do. I'm a little reluctant because the Reddit poster who had the same problem received a replacement that had the same problem. I've sent the Reddit person a message to ask how he finally solved the problem if he ever did.I'm also tempted to take the scope to a different location and try it to completely rule out local interference.

author: JPortici
author_rank: Super Contributor
timestamp: November 30, 2017, 06:17:11 am
content: single shot. are the multiple traces still in the display?and do an FFT of the signal, make it use you can see the frequencies up to...what are the AM and FM frequency bands in your area?

author: Fungus
author_rank: Super Contributor
timestamp: November 30, 2017, 12:48:23 pm
content: Quote from: alsetalokin4017 on November 30, 2017, 01:36:39 amMe too!Quote from: alsetalokin4017 on November 30, 2017, 01:36:39 amNor me. I've had my DS1054Z for three years and never seen it.Quote from: Porcine Porcupine on November 30, 2017, 03:36:30 amYep. I don't think I've ever used dots in all the time I've owned mine, so.No big deal.And all the Rigol haters would have posted endlessly if they'd seen it so I'm guessing none of them has ever seen it before either.Quote from: K5HJ on November 30, 2017, 04:20:53 amYes, you have to zoom in vertically and squish the signal against the top of the screen to see the separation properly. Normally it just looks like a thick line.Quote from: Porcine Porcupine on November 30, 2017, 05:36:23 amSeems like everybody else has it, too so you won't gain anything. Take comfort from the fact that nobody here even knew about it. Whatever the cause of the problem it has zero impact in real life.

author: Fungus
author_rank: Super Contributor
timestamp: November 30, 2017, 01:16:08 pm
content: It seems to be something to do with aliasing in 'dots' display mode. You can see it best in zoom mode (push horizontal timebase knob):When you're zoomed out you see two lines.When you zoom in a bit you see a single thick line but with most dots concentrated in two bands at top/bottom (is this where the two 'lines' come from?)Zoom a bit more, looks like noise but if you squint your eyes you can still see the 'lines' at top and bottom:On maximum zoom you see a sine wave:(Radio interference? It changes if I put my hand around the probe...)It might be that what we're seeing is a combination of quantization artifacts (concentrating the dots of the sine wave at top/bottom) plus display aliasing when you zoom out (ie. it can't average every single point in the pixel).So the question is: What do other 'scopes do?

author: Fungus
author_rank: Super Contributor
timestamp: November 30, 2017, 01:54:20 pm
content: Just for reference, this is dots vs. lines display:Dots:Lines:

author: frozenfrogz
author_rank: Frequent Contributor
timestamp: November 30, 2017, 02:13:29 pm
content: Software: 00.04.04.03.02Board: 0.1.4Boot: 0.0.1.4Firmware: 0.2.3.11CPLD: 1.1I can not reproduce the double trace via the steps posted on reddit.

author: JohnPen
author_rank: Regular Contributor
timestamp: November 30, 2017, 02:17:45 pm
content: These are the results following checks on my upgraded Rigol 1054Z. Pre conditions: No input signal, a 500usec TB for best visibilty and 1mV range ( X1 sensitivity).AC/DC input selected. Vector Display - Visual amplitude of noise ~1mV (filled in noise) Dots amplitude of noise ~1mV (2 noisy traces ~1mV apartChannel GND selected. Vector Display - Visual amplitude of noise ~500uV (filled in noise) Dots amplitude of noise ~500uV ( 2 noisy traces ~500uV apart)In both cases this is the basic noise level of the scope but the Dots mode displays it in a somewhat more confusing way. In either case Vector or Dots with a low level signal in mV you are unlikely to see anything useful unless it is is several mV above the scopes basic noise level. Having an external low noise amplifier could be useful in some applications to raise the signal level and improve the signal to noise ratio on the scope.Edit_ It is worth noting that this noise level also impacts on the trace triggering unless your input signal is quite a lot higher than the noise level.

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 07:44:17 pm
content: I have to say this forum is fantastic. All the great responses I've gotten here have been very helpful.Quote from: JPortici on November 30, 2017, 06:17:11 amYes, they're still there with single shot. I don't really see anything notable in the FFT corresponding to the AM band (535-1605 kHz), but there is some obvious stuff in the FM (88 to 108 MHz) band.Quote from: Fungus on November 30, 2017, 12:48:23 pmI think you've got me nearly convinced to forget about it. One concern I still have is whether I'm seeing a normal amount of noise for this scope. The whole reason I switched to dots and found the double trace is because the calibration signal trace looked too fat to me. You can see in the image below I'm seeing about around 100 mVpp with the vertical scale set to 500 mV/div. I'm assuming the signal itself is relatively noise free of course, but does 20% of the vertical setting seem reasonable here for this scope? If it does, I think I'm finished worrying about it.Quote from: frozenfrogz on November 30, 2017, 02:13:29 pmI just found out how to get the extended system information. It looks like we have an identical combination of hardware and software.BTW, here's a forum post about getting the extended information if anyone is wondering.https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg1101808/#msg1101808

author: cybermaus
author_rank: Frequent Contributor
timestamp: November 30, 2017, 08:03:32 pm
content: Quote from: Porcine Porcupine on November 30, 2017, 01:16:37 amSilly suggestion, but did you check continuity between power cord ground and actual grounding pin and/or said neutral bonding?When I bought my house actually had the screw linking to the ground pin loose. Not just a little due to thermal expansion cycling, but like several turns loose. Like the code inspector never did his job. But it can be in other wiring places as well.

author: Fungus
author_rank: Super Contributor
timestamp: November 30, 2017, 08:09:36 pm
content: Quote from: Porcine Porcupine on November 30, 2017, 07:44:17 pmIt looks identical to mine.Quote from: Porcine Porcupine on November 30, 2017, 07:44:17 pmFWIW you can turn on averaging mode. Averaging mode can get rid of noise on repetitive signals by finding complete waves in the incoming signal and averaging them together (see manual for details).This is the same signal with averaging turned on - the line is 1 pixel wide:I also tried averaging in dots mode and it cures the "double line" problem!This is dots mode with averaging turned on - no double lines:Conclusion: Your hardware is fine, IMHO. It's all about the way the 'scope copies noisy data to the screen.We need to learn all the display options and when to use each one.

author: JPortici
author_rank: Super Contributor
timestamp: November 30, 2017, 08:20:43 pm
content: Quote from: Porcine Porcupine on November 30, 2017, 07:44:17 pmand it shouldn't be there.i still have this scope among other equipment. at home if i'm not extra careful the signal is swamped in FM picked up by the scope (not by the probe) so that 10 mV/div is the best i can do at full bandwidth.at the work lab instead the scope is very quiet.i think cybermaus is onto something

author: Porcine Porcupine
author_rank: Contributor
timestamp: November 30, 2017, 08:46:42 pm
content: Quote from: cybermaus on November 30, 2017, 08:03:32 pmI didn't check that, but I'll check it out when I get a chance since you mentioned it.Quote from: Fungus on November 30, 2017, 08:09:36 pmCool, I think I'm satisfied now that my scope isn't defective.Quote from: JPortici on November 30, 2017, 08:20:43 pmThat's interesting. The stuff I see in the FM band goes away when I set the channel's input coupling to ground. I'm not sure if that means what I'm seeing is getting in through the probe or not.

author: Old Printer
author_rank: Frequent Contributor
timestamp: November 30, 2017, 10:21:54 pm
content: When the discussion comes as to which scope to buy, some will offer the opinion that the large number of 1054Z users, particularly on this forum, is a major plus. It is instances like this that give those statements credence. Imagine trying to sort out something like this with a more obscure scope. You might well wind up sending it off to the factory concerned it is part of a larger fault. All of these low end scopes are going to have some issues, the question is what to do about it. In this case, probably nothing, but how to come to that conclusion on your own. Dave

author: IAmBack
author_rank: Regular Contributor
timestamp: November 30, 2017, 10:35:22 pm
content: In my scope I can replicate this even with "coupling" set to GND. I simply see two yellow lines, 4mV one from other (10x probe set in menu).When I set time base to 200ms and press run/stop (it lit in red), then go to 1ms, those lines are getting close one to each other making "noisy line". but with two thin black lines...When I turn on rest of the channels, I see it in each of them. Channel 1 and 3 shows little more distance between lined. It looks like 8-channel scope...The distance between lines is changing with the "mem depth" setting - increasing mem depth increases distance between "doubled" lines. Non-GND coupling also makes the distance wider...Maybe it is some kind of pattern noise being "uncovered" by the decimation before displaying them?

author: Fungus
author_rank: Super Contributor
timestamp: November 30, 2017, 10:43:23 pm
content: Quote from: IAmBack on November 30, 2017, 10:35:22 pmYes, definitely this. You can see it happening if you go into zoom mode (see myscreenshots).

author: IAmBack
author_rank: Regular Contributor
timestamp: November 30, 2017, 10:44:37 pm
content: I like this thread.It explains why I need new Siglent 4ch scope

author: Fungus
author_rank: Super Contributor
timestamp: November 30, 2017, 10:48:05 pm
content: Quote from: IAmBack on November 30, 2017, 10:44:37 pmYeah, because that one will be perfect.Better the devil you know...

author: IAmBack
author_rank: Regular Contributor
timestamp: November 30, 2017, 11:10:03 pm
content: Quote from: Fungus on November 30, 2017, 10:48:05 pmI guess, that when all such "features" of the new scope will be discovered, then a newer one will apear in the market. This makes GAS fresh and vivid. As John Cleese said - there is no illness that can't be prolonged with an expensive cure.

author: IAmBack
author_rank: Regular Contributor
timestamp: November 30, 2017, 11:19:13 pm
content: Quote from: Fungus on November 30, 2017, 08:09:36 pmMine has BY-AY less than 60 mV.

author: JPortici
author_rank: Super Contributor
timestamp: November 30, 2017, 11:49:19 pm
content: Quote from: Porcine Porcupine on November 30, 2017, 08:46:42 pmjust so you know-1054Z always do everything from screen data, which is not the acquired data. there are countless topics on that-1054Z doesn't a true GND mode. In the 1054Z when you choose GND coupling what it actually does is draw a line at zero on screen data so every function returns zero. Or maybe somebody can explain how it can do GND mode without phisically shorting the input to ground, as every other scope i've ever seen do.-if you terminate the input with a terminator you may see no added noise, just the front end noise which is adequate

author: StillTrying
author_rank: Super Contributor
timestamp: December 01, 2017, 12:38:16 am
content: Does anyone want to see what the bottom of the Siglent CML+'s 1kHz looks like at 100mv/div.edit: I'll take that as a no, so here it is anyway! It looks much better, the probe is on X10, there's no control over the cml+'s much lower 5MSa/s sampling rate.

author: IAmBack
author_rank: Regular Contributor
timestamp: December 01, 2017, 11:20:36 am
content: Quote from: JPortici on November 30, 2017, 11:49:19 pmI can see "double line" in "GND mode"... So no zero.

author: Fungus
author_rank: Super Contributor
timestamp: December 01, 2017, 12:47:39 pm
content: Quote from: JPortici on November 30, 2017, 11:49:19 pmWhy would it need one? GND mode is a throwback to analog 'scopes where you often lost the trace and needed a way to get it back on screen so you could figure out how to reset the horizontal/vertical controls or refocus the beam (remember when oscilloscopes had a "focus" knob? That's where the GND button comes from...)These days we can just push the vertical position knob instead(!)I guess the fact that the haters always target the DS1054Z really just shows how good/popular it really is.Quote from: IAmBack on December 01, 2017, 11:20:36 amRight. Just something that's close enough.

author: Fungus
author_rank: Super Contributor
timestamp: December 01, 2017, 02:07:01 pm
content: Quote from: IAmBack on November 30, 2017, 11:19:13 pmThe base noise will be from radio transmitters in the area, etc., not from inside the 'scope.

author: IAmBack
author_rank: Regular Contributor
timestamp: December 01, 2017, 03:11:01 pm
content: Quote from: Fungus on December 01, 2017, 02:07:01 pmProbably, but I'm not sure if my scope is in "quiet" place. Anyway, not a big difference.

author: jsantoro
author_rank: Regular Contributor
timestamp: December 01, 2017, 04:20:20 pm
content: I've retired and got back into electronics as a hobby a while ago. I keep thinking I need to update some of my old equipment but after seeing posts like this I'm hesitant to replace my Tek 2247 with something new. Been looking at all these new DSO's and it seems they all have some sort of quirk. I want one but don't know why. Is it a case of I don't know what I'm missing? They do take up a whole lot less bench space.

author: tggzzz
author_rank: Super Contributor
timestamp: December 01, 2017, 04:32:10 pm
content: Quote from: jsantoro on December 01, 2017, 04:20:20 pmAll equipment has its quirks.Don't replace your Tek, but do augment it with a DSO. They have complementary advantages.Do consider what you need from new equipment. If you can tolerate 10MHz bandwidth, then consider a Digilent Analog Discovery. It is a 14 bit scope (good for its spectrum analyser) with built-in AWG (so you can do bode plots of filters etc), digital pattern generator and logic analyser.

author: Porcine Porcupine
author_rank: Contributor
timestamp: March 04, 2018, 06:35:03 am
content: After having this oscilloscope awhile, I've become convinced the problem is a firmware bug causing it to be stuck inpeak detectmode. I've posted it as a bug in the DS1000Z bug thread. Here's a link for future reference:https://www.eevblog.com/forum/testgear/rigol-ds1000z-series-buglist-continued-(from-fw-00-04-04-03-02)/msg1442914/#msg1442914

author: emocabras
author_rank: Contributor
timestamp: March 06, 2018, 12:24:55 am
content: Quote from: Porcine Porcupine on March 04, 2018, 06:35:03 amI tested different frequencies and waveforms with the signal generator in my rigol ds1054z I can not see double line.check you have power line problems, try to raise oscilloscope from the earth to do the test, to diagnose your local earth reference send strange frequencies.5.00ns Dots

author: Fungus
author_rank: Super Contributor
timestamp: March 06, 2018, 08:07:21 am
content: Quote from: StillTrying on December 01, 2017, 12:38:16 amYes!Quote from: StillTrying on December 01, 2017, 12:38:16 am"Much better" is relative, the point is it has the exact same problem. Thanks for confirming it!

author: Porcine Porcupine
author_rank: Contributor
timestamp: March 06, 2018, 09:47:10 am
content: Quote from: Fungus on March 06, 2018, 08:07:21 amAre you sure you're looking at that picture right? He's cropped the Siglent's traces from two screenshots and pasted them onto a screenshot from a Rigol. The Siglent's traces look normal to me.

author: Fungus
author_rank: Super Contributor
timestamp: March 06, 2018, 10:18:06 am
content: Quote from: Porcine Porcupine on March 06, 2018, 09:47:10 amIn that case, no I'm not.