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.
"The Saleae analyser needs to have an oscilloscope-type continuous trigger, where the view is constantly updated with new data in a rolling-buffer fashion. I wasn't aware that they could not do it, and it has made the usefulness of the analyser lower than anticipated.
The 'recording' mode is very useful to see the history when debugging a certain issue and that feature has been extremely useful, however there are a lot of situations in a professional environment where you need to see plots updated live with continuous trigger. A good example is the Picoscope line up. Their MSO offerings do have this, but not the 'recording' mode.
In my view, the lack of this feature will significantly hurt the analyser's usefulness in a professional R&D environment.
Could you let me know if this feature is planned, if so what timescale is it on?"
"When looping, it would be very helpul if the screen display operated more like an oscilloscope where signals are positioned according to a reference signal and the reference signal is always in the same position on the screen. This helps to see time varying signals such as for example PWM duty change over time."
"Feature Request - Multiple trigger-captures. It would allow me to capture several sequences on random event without having to restart capture by hand each timle event has occured."
"There's a typical oscilloscope mode where the oscilloscope triggers repeatedly, replacing the data onscreen with new data every trigger. This is super helpful for watching an analog waveform event. Logic has a "loop" feature which is similar, but there's no way to time-align it to the trigger. If there was a way to make the "run" button have a "run and then repeat" option, or a way to have the "looping" option keep itself time-aligned to the trigger, that would solve my problem."
Enabling ideas.saleae.com/b/feature-requests/jump-to-trigger-point-after-capture/ would be the first step for this.
I am debugging a SPI connection and my use case is the following. Every ~10.5ms 9 bytes are exchanged between devices and I can externally change the content of these 9 bytes. I would love to have a repeated trigger (either time based, so every 10.5ms or better 72 clock cycles after a falling edge for SPI Clock line), such that the GUI would be frozen on the relevant part of information and I could watch changes in real time. At the moment data is either zipping by too fast in live mode or I have to go back in time to see changes after the fact.
In any case I really love the new GUI!
"Automatic retrigger after capture duration time has finished. Capturing the last event not the first one.
In my use case a cyclic test is running and the test stops if it fails. And every cyclic test logic should automatically capture certain signals. After the test stopped I got the last captured diagram. At the moment we have to implement an instrumented code triggering a debug pin when the issue occurred."
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.
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.
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.
Posting more notes here regarding Triggering and Scope View ideas from the community:
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:
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,
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
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