For those that've had DSO experience the bugs aren't so bad that they can't be worked around but for a smart scope novice they are apparent and disconcerting.
@exe While you have every right to decide to send yours back, I think you are being a bit hasty with your decision. I may be wrong but I believe that Siglent will fix the trigger issue within a month, probably less.Seeing is believing. I already have made the mistake to wait for Siglent to fix firmware but that ended up with having to buy a different scope + dumping the Siglent one into the bin.
Of course this was 'work in progress' and shouldn't be put aside as owners of other equipment are waiting for FW tweaks too.
I nag the factory every week for X-E FW but as a SW engineer you know damn well that with a # of bugs the risk is that you create more bugs with the ones you fix. You also know the process of beta testing takes good time with further tweaks and further tests adding to delays.
That you couldn't wait is fine but in your profession I do find your lack of understanding ...........
Of course this was 'work in progress' and shouldn't be put aside as owners of other equipment are waiting for FW tweaks too.
I nag the factory every week for X-E FW but as a SW engineer you know damn well that with a # of bugs the risk is that you create more bugs with the ones you fix. You also know the process of beta testing takes good time with further tweaks and further tests adding to delays.
That you couldn't wait is fine but in your profession I do find your lack of understanding ...........
The process of testing and so forth wouldn't be as visible an issue with the proper pipelining setup. It's entirely possible to set things up such that firmware releases with bug fixes are done on a schedule. Yes, the amount of time between discovery of a bug and a fix for it would not change with such an approach, but at least the bug fixes would come in a steady stream.
There is always risk of introducing new bugs whenever alterations are made. What matters is the rate of bug production versus the rate of fixes. As long as the latter outpaces the former, all is good. It's when the former outpaces the latter that it's time to stop development altogether and do a ground-up rewrite (since those conditions usually arise as a result of the complexity of the software growing to an unmanageable state).
the MSO7104B cost me around $9,000 and it's 'only' 4 Gsps.
It's interesting to watch the double standard unfolding in this thread after all the mean things that were said by certain people about the DS1054Z's minor/obscure bugs.
The DS1054Z never had any bugs in basic things like triggering.
Why is Siglent being given so much love?
Recall that your principal excuse for the performance issues and bugs in the Rigol was cost: that you shouldn't expect a US$400 'scope to operate as well as a much more expensive one. That isn't unreasonable, provided basic functionality is available.
This Siglent has more processing power, so should be capable of doing better than the Rigol -- but there are obvious bugs that need to be corrected.
I don't see any significant difference in reaction.
a) The people who bashed the Rigol to death for sport are mysteriously absent here
b) There's now other choices for the same money (which wasn't true for much of the Rigol's existence).
I'm not sure what your complaint is here.
There are always going to be some people for whom a lesser quality instrument is considered beneath them. Gear snobs, essentially. However there are also people who will -- correctly -- point out the significant flaws that some cheap products have, and note that you can't really consider a product with a lot of limitations as being equivalent to a much more expensive but more capable product.
A 200 MHz scope has more bandwidth than a 100 MHz scope and bandwidth is everything! Except channels...
A 200 MHz scope has more bandwidth than a 100 MHz scope and bandwidth is everything! Except channels...AND samplerate.
I like 200 MHz but i think it will be more harm than good if you probe fast signals... such as MCU pins
my 1054z wobbles a lot when probing PIC32MZ pins
you have to wonder what would happen if Siglent (or Rigol) made the software open-source!!
it worked well for routers and phones.
I can't seem to recreate the triggering issue.
most router makers provide the source - you have to dig a bit to find it.
it's a legal requirement because it's usually based on open-source stuff to begin with.
similar with chinese fones - the korean company's dont give a damn (yet)
nothing wrong with xiaomi - my main and favourite fone is a Mi4
and there is bucketloads of custom firmware for it.
The new scope arrived and first impressions are very good, the fan is a little noisy but the UI is very responsive and I can't seem to recreate the triggering issue. I've included a couple of pictures, the first of which shows the software and FPGA versions.
I have a quick question about the PP215 probes; how do you get the hook tip off? I pulled at mine but it doesn't come off and I'm worried that I'll break it if I pull too hard.
make sure you buy an access point/router that's in their (extensive) list.
I seem to remember that someone said that the SDS1202X-E didn't have 50 Ohm terminations built in but I can't find where; I haven't tested it yet but it's there in the UI so I assume it does