| Products > Test Equipment |
| Why is the trigger rate of my scope (SDS814X HD) changing in an unexpected way? |
| << < (4/5) > >> |
| Someone:
--- Quote from: eTobey on September 29, 2024, 12:17:06 pm ---i believe there will be a lot of people who would not like that either --- End quote --- Perhaps if you make a thread it should explain its self and stand alone with all the information needed? This topic expects us to watch videos and take the information out of them. Many members (such as myself) will just ignore that, just as we ignored the previous threads where it was not explained what you were talking about. |
| eTobey:
--- Quote from: 2N3055 on September 29, 2024, 08:46:07 pm --- --- Quote from: eTobey on September 29, 2024, 08:32:41 pm --- --- Quote ---In sequence mode, the oscilloscope only acquires and stores data without processing and displaying, until the specified segments are acquired. --- End quote --- --- End quote --- In sequence mode scope will not process display and measurements. --- End quote --- Why are you repeating things, i already quoted? --- Quote from: 2N3055 on September 29, 2024, 08:46:07 pm ---Why do you ask questions when all the time you simply discard answers and keep repeating your opinion, based on complete lack of understanding how things really work? --- End quote --- Which answer? Your so called "answer" did not explicitly answer any of my question from that one post. So yes, i discard that answer too! (Seems like nowadays, asking explicit questions and instisting of an explicit answer is like spitting in someones face :palm:) --- Quote from: 2N3055 on September 29, 2024, 08:46:07 pm ---I think you should start a company and start making your own scopes. --- End quote --- No thanks! The hassle of communication and discussing with people is not worth the effort. And good people are hard to find, or already sit at Keysight and the like. I am good with how it is now ;-) So in summary: Its not possible very hard to investigate glitches / debug circuits on that scope (on other too?), because sequence mode may fail to trigger on those occurences, if you set the sample rate to low, which is something that you would do, to get a higher frame count and a longer acquire duration. (Gosh... does anyone understand this sentence? ;D) |
| tautech:
--- Quote from: eTobey on September 30, 2024, 09:45:49 am ---So in summary: Its not possible very hard to investigate glitches / debug circuits on that scope (on other too?), because sequence mode may fail to trigger on those occurences, if you set the sample rate to low, which is something that you would do, to get a higher frame count and a longer acquire duration. (Gosh... does anyone understand this sentence? ;D) --- End quote --- Yep, and the lack of understanding of how to use an analytical DSO to best advantage. Persist is your first friend/tool, just to see if you might have a problem. With Sample rate at max, the powerful trigger suite allows for triggering on most anything. Persist indicates what trigger you should/might use then Search allows you to find the incidences. |
| eTobey:
--- Quote from: tautech on September 30, 2024, 10:06:49 am ---With Sample rate at max, the powerful trigger suite allows for triggering on most anything. --- End quote --- Yes, but only for one time every n cycles on something you know, but i am looking for glitches and misalignments. But that seems to be to hard to understand for some. Its not s simple kind of steady signal! :palm: |
| tszaboo:
I really don't understand why you have vendetta against all the testing equipment that you purchased. Can you please list one testing equipment that you bought and it works the way you want it? |
| Navigation |
| Message Index |
| Next page |
| Previous page |