Another thing in the manual that does not add up:
Again...
The X2 is whereever you set it up. So it can also be on the left side. The same problem is with the Y1/2.
What you saying is not improvement or bug.
Scope shows sampled, acquired points, not current screen points.
What is purpose of useless metric of current screen?
I don't know about "useless". When showing interpolated traces (as I normally do), I appreciate the hint how many datapoints are actually used to generate the curve I see. Yes, I know I can calculate them by multiplying sample rate * sweep time, but an obvious number is helpful.
But I can also see the value in displaying the total number of acquired points, even if I have zoomed in and see just a fraction of them. Gives me a better idea about what to expect from measurements, for example.
In any case, either the firmware or the manual need to be changed. At the moment they are inconsistent, as the manual claims that the data points indicate the number of points shown on-screen. And that inconsistency is what eTobey had pointed out.
You are dead wrong!
Rude.This is not meant to be rude: but i really get frustrated
It was rude, and your frustration is the result of your lack of understanding (in combination with some errors in the manual 😉). It doesn't matter that he made a typo. You don't need to be a dick about it. Your behavior here is quite abrasive. That's not acceptable, especially when you're seeking help and understanding from people that owe you nothing. Errors in the manual or not, makes no difference. Don't treat people that way.
You are dead wrong!
Rude.This is not meant to be rude: but i really get frustrated
It was rude, and your frustration is the result of your lack of understanding (in combination with some errors in the manual 😉). It doesn't matter that he made a typo. You don't need to be a dick about it. Your behavior here is quite abrasive. That's not acceptable, especially when you're seeking help and understanding from people that owe you nothing. Errors in the manual or not, makes no difference. Don't treat people that way.
Language is a barrier. I translated it using Google and then modified the English. Before sending it, I thought about how others felt when they saw these words and whether they could understand.
People should not deny others first, and spend more time understanding the logic behind other people's discussions.
With note that user manual is reference document. It is not tutorial or introduction to scopes.
Just out of curiosity and because I might be able to learn something: What do people use the "total data points in the acquisition" information for?
Here is my issue:
- Change the manual (red) so it is easier to understand.
- My actual issue (pink):
I would expect that when a condition (an edge happens, a delay has run out, ...) occures, the trigger triggers. But with pattern its inconsistent (again). Whats the point of triggering when a set up condition is not met anymore? Just think of it with a red light at a traffic light: i want to trigger the brake when the red light or yellow light is on. With the patter trigger logic, i would be braking when it is green.
- My actual issue (pink):
I would expect that when a condition (an edge happens, a delay has run out, ...) occures, the trigger triggers. But with pattern its inconsistent (again). Whats the point of triggering when a set up condition is not met anymore? Just think of it with a red light at a traffic light: i want to trigger the brake when the red light or yellow light is on. With the patter trigger logic, i would be braking when it is green.
Terminology true and false belong to Boolean algebra, a mathematical theory. And software engineering, that is based on it.
We are dealing with signals here, so HIGH/LOW.
Inside FPGA VHDL language it is True/False, on physical pin it is electrical quantity HIGH/LOW digital signal.
As far as electrical engineer is concerned any properly measured quantity is true....
We cannot expect a device/instrument to do abstraction/de abstraction of concepts or conceptual thinking for us.
Here is my issue:
- Change the manual (red) so it is easier to understand.
- My actual issue (pink):
I would expect that when a condition (an edge happens, a delay has run out, ...) occures, the trigger triggers. But with pattern its inconsistent (again). Whats the point of triggering when a set up condition is not met anymore? Just think of it with a red light at a traffic light: i want to trigger the brake when the red light or yellow light is on. With the patter trigger logic, i would be braking when it is green.
The image in the manual is an example. When Channel1 is set to High and Channel2 is set to Low, the “Trigger Position“ indications are triggered under different Logic, such as the Logic AND, trigger Position is in the time triggering from True to False.
Have you understand what i was trying to say with the traffic light?
Have you understand what i was trying to say with the traffic light?
Have you read my post #72 in the meantime, where I think I explained why the Pattern trigger strikes at the end of the pattern's existence? It is a bit annoying at times that you hardly ever comment on attempts to answer a question, let alone confirm an answer.
Would you agree, that a better description would be like "Triggers after a pattern existed for the specified amount of time?
I just went to read about the pattern trigger, because the manual made me to! I just wanted to know the delay trigger.
Just out of curiosity and because I might be able to learn something: What do people use the "total data points in the acquisition" information for?
I have thought about removing the "total data points in the acquisition" and found that it doesn't seem to affect anything, I am more concerned about whether the sampling rate meets the requirements. If anyone else has an idea, could you explain it.
It allows me to know at a glance whether the current record can be used for signal analysis without any further (hidden) decimation (which would cause decoders to fail and measurements to give grossly wrong results...
I have indeed not used the mask editor at all yet. Could you describe what seems to be wrong? Ideally in a simple step-by-step sequence which we can try and reproduce.
I have setup a qualified trigger that does not trigger at all on a 100mv/div scale. The edge trigger does trigger on this signal down to 5mv. Signal is from ~0 - 2.7V