|
Tim |
Add the ability to filter / isolate measurements. Our measurement extensions do a great job of providing statistical measurements across a time range for your capture, but doesn't help you find specific areas of interest, such as pulses > 10ms.
One way of solving this is to add the ability to highlight regions as the capture is parsed for measurements.
A fully-featured measurement search system could also be cool, then it highlights what it finds. Kind of like a ctrl+F, but for waveforms.
For example:
- search… pos pulse… > … 28ms
- search… pos pulse… max
- search… HLA… value… =… 0x00 (technically already possible)
- search… voltage… >… 1.8V
Activity Newest / Oldest
Tim
(#87135)
"the only reason I clicked on the value was because I expected that I could jump to the peak by doing that. I was very disappointed – and hope you agree! 😉 I’ll start searching for another way to find it"
Tim
(#74276)
"I re-test from time to time to ensure my system still meets its timing requirements. Often times, the measurements will show that the software sometimes does not meet its timing requirements. This can be observed by watching for to have a longer than normal crest when compared to its usually consistent runs (the "glitches" I mentioned previously).
What I want to automate is the process of finding these glitches, measuring them, and measuring the time between them."
Tim
(#63852)
"We can isolate the required pulse from the recorded pulse based on filter categories/condition. Now we need to search manually which is difficult if we have to search with more pulse. Like if we need to find the pulse from 100/500/1000 pulses then its time consuming thing.
Example,
The pulse from GPIO used to measure the execution time of function, GPIO pin HIGH before calling that function and making LOW after calling that function, and the time is varying depends on certain condition. Expected execution time is 28us but sometimes it consumes more time, like 34us, 43us and 48us. Now there is a need to isolate the data which are high, like HIGH duration is greater than 28us to analyze and check how frequently it occurs.
Solution(Suggestion):
We can provide a filter option (May be only on captured data bcz with real time data we may introduce complexity) with pulse HIGH/LOW duration, color code, after/before recorded time.
In the output, we can also provide filter pulse count - total number of pulse met the filter condition.
Color code can be used to draw only the filter pulse. For example, if channel 0 uses by default white color, we can use filter color code to draw only for pulse which meets the filter condition.")
Tim
discuss.saleae.com/t/option-to-isolate-maximum-minimum-duration-in-digital-channel/1189
"For example,
I am measuring the execution time of specific function by making GPIO pin HIGH before calling that function and making LOW after calling that function, and the time is varying depends on certain condition. Expected execution time is 28us but sometimes it consumes more time, like 34us, 43us and 48us. Now I want to isolate the data which are high, like HIGH duration is greater than 28us to analyze and check how frequently it occurs."