Sorry for the question. Today is arrived this little baby (1104x-e), and i'm trying to zoom at maximum possible the second rising edge after the trigger of a 1khz signal (jitter analysis). But seem that there is a limit how far the screen can be from the trigger point, limit at 500us. I'm doing something wrong, or there is a better way to do it? Thanks!
Tautech and/or rf-loop, why isn't trigger holdoff available for all trigger types? That seems to be something that should be a general property of the triggering system itself, rather than being something that is type-specific, no? After all, it's just an artificial delay that is introduced prior to the trigger being re-armed.
The nature of how the Siglent does captures is that what you see on the screen is the entire capture. So what you may want to do is to set your timebase such that at least two rising edges are visible, and then zoom in on the second one after you stop the scope. Or you can use zoom mode while the scope is running (see below).
That said, you can actually set the trigger point location to be outside of the capture area. If you rotate the horizontal position knob counterclockwise, you'll be positioning the trigger point earlier in the capture, and you can actually position it to well before the point where the screen begins. So that would make it possible for you to see the second rising edge while triggering on the first rising edge. Note that this would work best when the trigger is set up such that it would trigger on the first rising edge but not the second one, something that you can arrange using the holdoff feature of the edge trigger.
Also, the scope has a "zoom mode". Press the horizontal scale button and it'll switch to zoom mode. This makes it possible for you to capture both rising edges and zoom in on the second one while the scope is running.
Tautech and/or rf-loop, why isn't trigger holdoff available for all trigger types? That seems to be something that should be a general property of the triggering system itself, rather than being something that is type-specific, no? After all, it's just an artificial delay that is introduced prior to the trigger being re-armed.Artificial yes and a necessary tool when dealing with non-repetitive waveforms where you need to have full control of trigger rearming so to be able to reliably trigger on your POI.
Holdoff is just not needed on all trigger types however without detailed analysis of each trigger type they may have their own specific holdoff value.
Arguably in the modern DSO the trigger suite is the most complex feature and certainly the feature that takes the most mastering when we depart from just simple edge triggering.
Tautech and/or rf-loop, why isn't trigger holdoff available for all trigger types? That seems to be something that should be a general property of the triggering system itself, rather than being something that is type-specific, no? After all, it's just an artificial delay that is introduced prior to the trigger being re-armed.Artificial yes and a necessary tool when dealing with non-repetitive waveforms where you need to have full control of trigger rearming so to be able to reliably trigger on your POI.
Holdoff is just not needed on all trigger types however without detailed analysis of each trigger type they may have their own specific holdoff value.
Arguably in the modern DSO the trigger suite is the most complex feature and certainly the feature that takes the most mastering when we depart from just simple edge triggering.
I'm not sure I buy this as an explanation. The trigger conditions, i.e. when it fires, are obviously highly dependent on the trigger type and involve multiple considerations. But that is completely separate from an additional delay that can be imposed. The additional delay is what I'm talking about here, and I see no reason whatsoever that it can't be imposed in all trigger types. After all, all it says is "the trigger shall not fire again until after the specified delay time has passed".
Who's to say whether a delay is needed or not? The answer to that is simple: the user. And only the user. The manufacturer is in no position to make any such claim, because the manufacturer simply cannot know the entirety of circumstances in which the trigger will be used.
Thanks! I've centered the second rising edge, zoomed and worked like a charm!
One more little question: there isn't also a vertical zoom?trying to increase the vertical gain obviously i get a distorted wave due to clipping of the input opamps...
Say for example we need trigger on one bit and as that bit is just one trigger parameter that's user adjustable within that trigger type would be a good example of when trigger holdoff is not required otherwise I broadly agree the user must have the control and not the instrument.
Got another question.
I noticed that in roll mode, the sample memory is cut by a factor of 10. Why is that? A factor of 10 seems excessive. What's the rest of the memory being used for? Certainly not history -- that's disabled in roll mode.
Got another question.
I noticed that in roll mode, the sample memory is cut by a factor of 10. Why is that? A factor of 10 seems excessive. What's the rest of the memory being used for? Certainly not history -- that's disabled in roll mode.IDK for dedicated Roll mode however if max mem depth is what you need in Roll mode you're best to use Auto Roll mode where the full 14 Mpts is available.
You'll get clipping if you increase the vertical gain while the scope is operating, but when the scope is stopped, the vertical zoom just acts as a standard zoom. So try stopping the scope first and then zoom in using the vertical scale knob.
The scope converter only has so much resolution, however, so what you really want to do is to set the vertical settings so that the waveform fills as much of the screen as you can manage. This will ensure that the opamps remain unsaturated while also ensuring that you have maximum use of the ADC resolution. You can then zoom in from there with the scope stopped. There may be limitations in terms of what you can do with respect to zooming in like that, but from what I've seen, you'll easily be able to zoom in vertically to the point where you can make out the individual value transitions within the number of bits per sample recorded.
Got another question.
I noticed that in roll mode, the sample memory is cut by a factor of 10. Why is that? A factor of 10 seems excessive. What's the rest of the memory being used for? Certainly not history -- that's disabled in roll mode.
I see no mention of auto roll mode anywhere in the manual, nor any mention of a setting that would control that. How does one enter it? Merely increasing the time/div doesn't seem to do it on its own. I could swear there's a setting that controls this but I can't for the life of me find it.
AFAIK, Roll mode can use with time scales 50ms/div - 100s/div and in Roll mode max memory is 1.4M (2x1.4M)
No trigger. It just roll like paper roll plotter. Its memory lenghth is 1.4Mpts. with 50ms/div it have its maximum samplerate what is 2MSa/s. Peak detect is available also in roll mode of course. Average and ERES not.
New samples are plotted to display horizontal border and old samples are pushed like FIFO.
It is its limits, like or not. It is made that way. Period.
(Disclaimer, I have not used latest firmwares but I do not believe this thing change, it do not sell any more if it change. )
If need more memory and samplerate using 50ms/div - 100s/div then just do not use ROLL mode. Normal acquisition with Auto trig or Normal or Single shot. Max memory is then 14M with 2 channels on and with 50ms/div max samplerate naturally 20MSa/s. Of course in then can live with less samplerate but need more history then just reduce memory lenght.
With 7k memory 2 channel in 1 group open, 100s/div it have 5 sample/s and it can save up to 3912 these 1400 second acquisitions sequentially. 5476800s data (63 days) plus (sadly too big) time cap between single acquisitions.
Thanks! So i suppose that there isn't a way to zoom with the scope running...
Sigh.
Has anyone managed to get i2c triggering on 7-bit addresses working? Triggering on message start works.
With respect to triggering on 7 bit address + value:
* It works when I set everything to "don't care".
* It works when I set a data value that's present
* It works when I set the read/write attribute to match what's present (and it won't trigger if I get this wrong, which is good)
* It works with combinations of data value and read/write that actually match what's present
* It does *not* work with any combination where I set the address, at least with the signal that I'm using (an Arduino's output to an i2c display), even when the address value I set matches what the decoder consistently shows.
I've already tried things like using the 20 MHz bandwidth filter on the probes. It makes no difference. And frankly, if the decoder can find the address, why can't the triggering mechanism do the same?
What data would you guys like for diagnosis of this?
Here's proof that the address I'm having it search for is present in the signal:
And here's what happens when I set the trigger to use that address and hit "single" or "normal":
I would like to just add: There should be ( on any scope that does decode/trigger from serial protocols ) a button "copy this decoded frame to trigger".
You look around the list, find interesting packet , select and copy it to trigger.... That would be huuge timesaver...
Sorry for the tangent...
With SDS1202X-E firmware revision 1.3.23 (or 7.0.1.3.23 seen on scope 'system' screen), the 'Link to Trigger' button on the DECODE page 2 has been changed to 'Copy Setting.' This adds the ability to not only link the DECODE to the trigger ('Copy To Trig'), but to link the trigger to the DECODE (Copy From Trig). Both options are on a submenu of 'Copy Setting.'
QuoteWith SDS1202X-E firmware revision 1.3.23 (or 7.0.1.3.23 seen on scope 'system' screen), the 'Link to Trigger' button on the DECODE page 2 has been changed to 'Copy Setting.' This adds the ability to not only link the DECODE to the trigger ('Copy To Trig'), but to link the trigger to the DECODE (Copy From Trig). Both options are on a submenu of 'Copy Setting.'
Does this help?