Voters 3
-
-
N
-
S
3
Search Digital Channel States / Patterns
- Open
- Subscribe
 |
Tim |
(#73604) Hello, I reckon the software should have the ability to search for a specific edge in the data. For instance: Search for FALLING edge of CH0 where CH1==HIGH and CH2 transitioned to LOW in the preceding 10 ms.
Searching on a recorded long capture is more powerful, because you may not initially know what you're looking for. For instance, you may be looking around and suddenly see something odd. You could say uhm... the weird bug happened 3 times in this capture, let's search for this specific pattern. If it happened other 2 times, it's a strong indication that this is correlated.
Activity Newest / Oldest
Tim
(#82628)
"I have a pattern in few pins that make my device to fail, I have few dma running in parapel and I get some data corrupted, so I have debugging with Saleae (Logic Pro 16) I can trigger in the condition and I see the spi data corrupted, but I am interested to see when the trigger pattern repeat if I have also corrupted data, but it is impossible to see because there are some many signal going on that I can not check one by one, let say something like that but I would like to see all the trigger match cases somehow marked (graphic example)"
Tim
(#80207)
"I'm running a capture but I don't yet know what I'm looking for. The idea is a capture multiple times, I document when my device under test did and did not fail and THEN I would like to go back over the captures to see if certain events did or did not occur (to see if any given behaviour is a symptom or cause of the device failure) For example, I'd like to load a previously saved capture and search for an event where a particular signal was high for more than x ms. Basically, I'd like to do your existing triggering mechanisms on a previously saved capture, like replaying it almost. Does such a feature or similar exist?"
Tim
(#78224)
"Wanted to know if there is a way to 'trigger search' or otherwise mark and jump between multiple trigger matches within a capture?
E.g., using the 'trigger' conditions, look for next/previous time that those conditions are met vs. only marking the FIRST time the 'trigger' is set."