Right, actually batronix offer them without a bundle for free- therefore the sig gen only license will cost 568€ incl. VAT, the all in bundle 1496€
568€ for a one channel AWG....
Apart from this I would like to have the discussion about sense or nonsense of inbuilt awgs separated from here, because it´s a general thing...
But it still needs the zoom crutch. Everyone can walk faster without a crutch.
Also decoding only what is on screen gives you the problem that it is nearly impossible to correlate messages which may be in different parts of the acquisition memory. Get a Keysight or R&S scope on your bench and see how easy it is to be able to go through the entire record with timestamps relative to each packet.
Same for the automatic memory length. For the millionth time: limiting the memory size to the visible screen only is a serious productivity limitation. There is no arguing around that other than using yet another crutch (going back & forth between time/div settings). Everyone can walk faster without a crutch.
Remember I used to own an SDS2000 and the automatic memory selection annoyed the hell out of me.
Reasoning that none of the customers has asked for it is more indicative of the kind of customers Siglent has than automatic memory selection should be standard. Power users like me that need to have an oscilloscope which works efficiently will ask for it (or silently just don't buy the oscilloscopes from Siglent). Siglent has come a long way in the past few years and now they really have to start addressing the productivity issues (at least on the higher end models) in order to really compete with the A-brands.
I'm obviously responding to something that is rather old, but I can't help myself.But it still needs the zoom crutch. Everyone can walk faster without a crutch.What you call a "crutch", others clearly consider to be an advantage.
The scope decodes everything in the capture (subject to the limitations that were mentioned).
One capability that the Siglent approach has which other scopes might not have (and I can't say whether they have it or not. The Rigol DS-1054Z certainly doesn't) is to make it possible to place the trigger point outside of the captured area. From what I can tell, you can place the trigger point an arbitrary amount of time prior to the capture, and up to the right edge of the screen, which is the end of the capture buffer.
and look at Dave's 'zoom out' video.
If your reference point is a DS-1054Z then you have a boat load of catching up to do.
None of the features on Siglent scopes are special in any way compared to their mainstream competitors.
The rest has already been debated so I urge you to just read some other threads and look at Dave's 'zoom out' video.
If your reference point is a DS-1054Z then you have a boat load of catching up to do.It's not my "reference point", it's just a scope that I happen to have access to. It's why I worded things the way I did.QuoteNone of the features on Siglent scopes are special in any way compared to their mainstream competitors.Not even the "always on" history?
QuoteThe rest has already been debated so I urge you to just read some other threads and look at Dave's 'zoom out' video.Dave has quite a few videos. Can you provide a link to the video you're referring to?
Not even the "always on" history?Yup. Standard on Yokogawa oscilloscopes for ages.
QuoteDave has quite a few videos. Can you provide a link to the video you're referring to?
One example: a while ago I had to debug a SoC design and wanted to check the CPU's core voltage because every now and then it would crash. For that I wanted to see what happened to the core voltage when it is switched. One channel on the signal to the regulator and one on the core voltage. Trigger set to the control signal and go. No idea on what timescale the event is taking place. Turned out that I choose the time/div too short so I couldn't see the entire event where the supply voltage dropped for a while. Since the oscilloscope I used (RTM3004) was on maximum memory depth I could simply turn the time/div / horizontal position knobs to get more signal. From that single capture I had all the information needed to see what the exact problem was even though I had no idea about what I was going to look for. Recapturing the event on a different time/div setting would have meant waiting for another crash to happen.
Another example: every now and then there is a problem with an I2C message. In order to see whether a message is correct or not you need to see the part which goes wrong. Once the message is captured turning the time/div / horizontal position knobs can be used to check what happened leading up to the event. Again, it is unknown on what timescale the event is taking place so more memory is better because recapturing the event isn't easy.
Admittedly, the screen can get really busy if you're tracking multiple signals with it. Zoom mode should be configurable in terms of how much real estate the full capture portion occupies, for exactly that reason. But that's not an indictment of the capture approach Siglent is taking here, but rather of the lack of flexibility in their zoom mode.
So while Siglent's "always on" history isn't unique, if Yokogawa is the only other manufacturer that has it, then Siglent is in a league of its own with respect to offering this feature in the market segment it plays in.
History function: looking back in time
Where does the interference pulse in the signal come
from? What caused the loss of a data bit? Finding the real
cause of a problem is often only possible by looking at the
history of a signal sequence.
The R&S®RTO history function provides access to previously
acquired waveforms at the press of a button. This allows
users to analyze the measurement data stored in memory.
They can scroll through the individual acquisitions with the
history player or use the persistence mode to display them
superimposed. This powerful function facilitates searches
for signal faults over all acquisitions. One timestamp per
waveform clearly identifies when events took place. Various
analysis tools such as automatic measurements, FFT,
mask tests and a search function are available for analyzing
past acquisitions.
I haven't seen anyone else address this, so ...One example: a while ago I had to debug a SoC design and wanted to check the CPU's core voltage because every now and then it would crash. For that I wanted to see what happened to the core voltage when it is switched. One channel on the signal to the regulator and one on the core voltage. Trigger set to the control signal and go. No idea on what timescale the event is taking place. Turned out that I choose the time/div too short so I couldn't see the entire event where the supply voltage dropped for a while. Since the oscilloscope I used (RTM3004) was on maximum memory depth I could simply turn the time/div / horizontal position knobs to get more signal. From that single capture I had all the information needed to see what the exact problem was even though I had no idea about what I was going to look for. Recapturing the event on a different time/div setting would have meant waiting for another crash to happen.
Then you got lucky. You got lucky because it just happened that the supply voltage drop happened within the time window that your scope was able to record with its memory.
With the Siglent, you would know whether or not you've got the scope configured in such a way as to capture both the core voltage event and the control signal trigger event, assuming that the scope would be capable of doing it at all, because as long as you know the characteristics of the core
I haven't seen anyone else address this, so ...One example: a while ago I had to debug a SoC design and wanted to check the CPU's core voltage because every now and then it would crash. For that I wanted to see what happened to the core voltage when it is switched. One channel on the signal to the regulator and one on the core voltage. Trigger set to the control signal and go. No idea on what timescale the event is taking place. Turned out that I choose the time/div too short so I couldn't see the entire event where the supply voltage dropped for a while. Since the oscilloscope I used (RTM3004) was on maximum memory depth I could simply turn the time/div / horizontal position knobs to get more signal. From that single capture I had all the information needed to see what the exact problem was even though I had no idea about what I was going to look for. Recapturing the event on a different time/div setting would have meant waiting for another crash to happen.
Then you got lucky. You got lucky because it just happened that the supply voltage drop happened within the time window that your scope was able to record with its memory.
With the Siglent, you would know whether or not you've got the scope configured in such a way as to capture both the core voltage event and the control signal trigger event, assuming that the scope would be capable of doing it at all, because as long as you know the characteristics of the coreThere is no guessing involved! At some point you have enough experience to just know if the memory depth is enough or not. Just like you know how far your car will go when the fuel indicator says the tank is half full. And at some point you also acquire the experience to know which tools work with you and which tools work against you.
How and why it helps when part of acquisition is hidden outside of screen.
There is no guessing involved! At some point you have enough experience to just know if the memory depth is enough or not. Just like you know how far your car will go when the fuel indicator says the tank is half full. And at some point you also acquire the experience to know which tools work with you and which tools work against you.
Hm.. I am really surprised that Siglent does not have it. Even my old Rigol DS1102E has the "zoom-out" feature. And I use it quite often - I just set up the horizontal system so I can clearly see what I want, but I know that I have a couple of "screens" on the left and on the right if I need them. And I often go there. At least scroll left/right for about one screen. It's obvious that I can capture at more us/div, stop and then zoom in, but it's not that convenient for me.
Hi, fast question, it's possible view %THD factor from FFT screen? Tek MDO4104C have this option.