18

Repeated trigger capture


Uriel Klieger

Similar to the "normal" trigger mode of an oscilloscope, it would be useful if Logic could be set capture an amount of time around a trigger event, and then re-arm the trigger and do it continually. Logic could save each trigger to a file automatically or only display the most recent capture.

This could be useful for capturing certain events which are far apart in time, without having to sift through all the data in between.

It would be most helpful for capturing the final occurrence of a trigger -- that is, something should happen regularly when things are running normally and then it stops happening. This way, we could see what happened around the time of the failure and not miss the event.

A

Activity Newest / Oldest

S

Sergey

Looping with trigger synchronization or continuous trigger allows you to track the change in synchronization of multiple devices in real time.

I have several transceivers and I need to monitor in real time how many microseconds their mutual synchronization diverges.

Such a mode is available in any oscilloscope, and also in the analyzer from Kingst: Click the @ button in the toolbar to start automatic repeat acquisition.When the collection time is reached, the software will automatically starts the next collection, it is not necessary to click the > button manually until the sampling needs to be stopped.


A

Andy

In repetitive debug tasks, the steps are often:
1 arm the Trigger in Logic 2
2 Run some code
3 look at the Logic2 output
4 repeat at step 1

It would be very helpful to have a flag in the trigger settings, which would automatically re-arm the trigger after the capture duration has elapsed.

Extended option:
In addition to the "capture duration" there could be an additional waiting time "hold-off time" without data capturing, before the trigger is re-armed. However, this is probably not required and would just make the settings more complex.


Tim R

Posting more notes here regarding Triggering and Scope View ideas from the community:
discuss.saleae.com/t/triggering-and-scope-view-share-your-ideas-with-us/563/43


N

Neel

Status changed to: Open

R

Rani Horev

Hey all, we'll start working on this feature soon and we'd love to learn more about your use cases. Please share with us your experience here:
discuss.saleae.com/t/triggering-and-scope-view-share-your-ideas-with-us/563


R

Rani Horev

Merged Post: First of all - I love it, really. And it helps me so much everyday coding DSP Firmware.

For the new Live View Feature - would it be possible to set a trigger that fixes maybe rising/falling edge to a defined starting point at the view, like Oscilloscopes do ?
I actually Play with HiRes PWM and if i can fix the rising edge somewhere to the left of the window, i can see jitter and change in on-time changes more easily.
In the current release, it starts somewhere in the window.

So much thanks for your support & kind regards from Germany,
Marja


R

Rani Horev

Merged with: Trigger Point for live view

R

Rani Horev

Merged post: I would be good to have possibility to re capture each time the trigger occurs.
And save only a certain amount of time before and after.
This could be use to monitor the last action of an heartbeat without saving GB of data


R

Rani Horev

Merged with: Continuous Trigger

R

Rani Horev

Status changed to: Planned

R

Rani Horev

Thanks!
Yes, we are planning on integrating the live view and triggers (of all kinds - digital, analog and protocol results). You'd be able to select if the live view updates only on a new trigger or with any new data