How can you say there's nothing to trigger on when we can see the nearly 1 division high sine waves are still there, as in Replies #711 and #714. If you've carefully set the trigger level to get a view of the noise, you shouldn't loose that ability for no apparent reason.
I agree with ebastler that being able to trigger on the noise is the normal behavior, we've been doing it for years!
after all, how do you know if it is random noise or a small signal, until you trigger on it.
Normal trigger is usually better than Auto trigger, although it's also a pain to use when the amplitudes are very low.
Quite unlikely random wild guess:
When opening the trig menu it checks it's on the 500uV range, realises an amplitude of 0.8 Div. is likely to be just noise, so doesn't bother triggering on anything less than 1 Div high.
Someone else with a SDS1202X-E ? should try to reproduce it.
You don't get this (initial) behaviour, though. Not on any 'scope I have worked with. What you get is the post-menu triggering behaviour.
You don't get this (initial) behaviour, though. Not on any 'scope I have worked with. What you get is the post-menu triggering behaviour.I certainly get this behavior on my DS1054Z, and consider it to be perfectly normal and expected. And this guy gets it on his DS4024 (but has not understood it either)
I consider the second screen-grab above, to be 'correct'. The only way it could find a genuine trigger point would be if the algorithm found something that looked like a trigger. If you look at the first screen-grab you can see that rectangle where no data points are present to the right of the central graticule (the trigger point). That is an artefact of some kind. It is persistent, and anomalous.
On the SDM3065X, when I enter Frequency measurement mode, and then select Range, what ranges should be present in the UI?
I consider the second screen-grab above, to be 'correct'. The only way it could find a genuine trigger point would be if the algorithm found something that looked like a trigger. If you look at the first screen-grab you can see that rectangle where no data points are present to the right of the central graticule (the trigger point). That is an artefact of some kind. It is persistent, and anomalous.
I'll try one last time; but I think I might just not be able to get my point across to you. (Or I continuously miss your point...)
If you have one sample below the trigger threshold, and the subsequent sample above the trigger threshold, that constitutes "a genuine trigger point". Because you have set the trigger condition to "positive edge", right?!
So, your scope is sitting and waiting, looking at a random sequence of samples which are above, above, below, below, above, below... the trigger threshold. The scope sits and waits until it sees a sequence of "one sample below, followed by one sample above the trigger threshold". Then it triggers. And it displays the sample sequence, centered at the trigger time point.
And guess what: The sample to the right of the trigger time point is always above the trigger threshold!! Which is what your display shows, and what you describe as "that rectangle where no data points are present to the right of the central graticule (the trigger point)." And which is what you explicitly asked the scope to look for and trigger on.
So?!
Do you think it likely that an entire block of sample points would happen to cluster in the manner that you see in the first screen-grab? Statistically highly unlikely, for a single event. For repeatable events -- can't happen.
First -- did you notice there are two behaviours shown? There was no change to triggering involved. So that seems to be some form of bug.
On the SDM3065X, when I enter Frequency measurement mode, and then select Range, what ranges should be present in the UI?Goes something like: Auto, 200mV, 2V, 20V, 200V.
They are essentially sensitivity settings. eg. with open inputs at highest sensitivity you'll probably get ~2x mains frequency.
What is driving me nuts:
Automatic roll mode for long timebase. If I want roll mode, I will turn it on myself, thank you.
On the SDM3065X, when I enter Frequency measurement mode, and then select Range, what ranges should be present in the UI?Goes something like: Auto, 200mV, 2V, 20V, 200V.
They are essentially sensitivity settings. eg. with open inputs at highest sensitivity you'll probably get ~2x mains frequency.Got it. Thank you.
The SDG2000X uses the term "TrigLvl" for this, which seems like a better name than "Range". "Range" in a frequency measurement mode implies a frequency range to me. Maybe "TrigRng" would be a more clear label here?
Turns out I have a much better frequency measurement tool for the frequencies of interest in the SDG2000X. It's built-in frequency counter can handle up to 200MHz.
What is driving me nuts:
Automatic roll mode for long timebase. If I want roll mode, I will turn it on myself, thank you.
If it switches to roll mode for long timebases you can switch of roll mode by pressing the roll button.
Yes, it does seem strange the upper limit for SDM3065X is only 3 MHz.
10 MHz would have been more useful one would think, especially for those with GPS referenced 10 MHz labs.
Let's see if Siglent can squeeze it up some in new FW to come.
Yes, I can. And that is what drives me nuts. Zoom out your time base, and now it rolls... push the button to disable it. Zoom out in few minutes again, and it rolls again... If I want it to roll, I will turn it on... It does something, what I do not want to do, automatically, and as a result I need to keep pushing buttons.... I think this functionality should be user selectable in options.
Has there been any update on the bugs with the Siglent hand held scopes?
Specifically the SHS1062 & SHS806 oscilloscopes.
Has there been any update on the bugs with the Siglent hand held scopes?
Specifically the SHS1062 & SHS806 oscilloscopes.
Hey folks,
I picked up an SDS2204X with MSO option from Saelig a couple weeks ago and had the first opportunity to use it in anger this weekend.
The digital interface worked great. The screen is so much nicer than the old Rigol I had been using.
One thing that's taking some getting used to is switching from the "filter" feature on the Rigol to "Eres" on the Siglent. I live close to the loop in Chicago where all the radio and TV transmitters are located. I can clearly make out every radio station in Chicago on my FFT. So filtering the signal is a must. Otherwise there is 50mV of noise centered at 98MHz. (If you have suggestions for minimizing this problem, I'm open to listeneing.)
One issue I had on the analog side (when using only analog input) was that the trigger indicator would go missing and I could not bring it up on the screen. It would tell me what the trigger level was, and I could see the effect of changing it on the trace, but the dotted bar would not show up. Is this a known issue? I wish I knew how to reproduce it but it "just happened" a couple times. Turning off the scope would make it work again. Is this a known issue?
QuoteOne issue I had on the analog side (when using only analog input) was that the trigger indicator would go missing and I could not bring it up on the screen. It would tell me what the trigger level was, and I could see the effect of changing it on the trace, but the dotted bar would not show up. Is this a known issue? I wish I knew how to reproduce it but it "just happened" a couple times. Turning off the scope would make it work again. Is this a known issue?It might just be user error. If the trigger level is set to ~ 50% of a waveform and the sensitivity increased the trigger will travel upwards and sometimes off the display. In these cases the trigger level indicator will be at the top right of the display and pointing upwards not outwards into the display area.
When you've lost the trigger.......and you have Auto triggering set, press the trigger level control to automatically set the trigger to 50% of the waveform amplitude.
One issue I had on the analog side (when using only analog input) was that the trigger indicator would go missing and I could not bring it up on the screen. It would tell me what the trigger level was, and I could see the effect of changing it on the trace, but the dotted bar would not show up. Is this a known issue? I wish I knew how to reproduce it but it "just happened" a couple times. Turning off the scope would make it work again. Is this a known issue?