Jump to trigger point after capture

Voters 24

P
R
D
S
R
J
+ 18 voters
H
J
A
M
E
J
J
D
J
F
D
P
Z
J
K
J
A

Held for moderation

Live

Eule

I would like to have a selection to automatically jump to the trigger point after capture. Like manually by pressing the yellow arrow.

19-07-2020 -

Activity Newest / Oldest

Considering that I capture a certain time after a trigger, it would be nice to navigate back and forth from rising edges.
A capture mode where it would automatically capture when a new trigger condition is met would be super interesting, as we can do in an oscilloscope.

Tim

Navigating to the next or previous edge offscreen (whether rising or falling) is possible via a button or keyboard shortcut. More information on this can be found in the link below. However, navigating to the next specific edge (i.e. just rising, or just falling) is not possible.
support.saleae.com/user-guide/using-logic/navigating-your-data

We're also tracking a feature request for repeated trigger captures via the post below:
ideas.saleae.com/b/feature-requests/repeated-trigger-capture/

Having said that, we do have an Automation API via Python (link below to the documentation) that would allow you to automatically start repeated triggered captures and save each capture to disk.
saleae.github.io/logic2-automation/

Helge

I think it is great that stops the trigger point at the center of the screen but it could be improved a lot more by being able to select the position of the trigger. Why not have a selection of 0 - 100% of the display? In that what you could Select if you wanted to see as much as possible of the beginning of a captured frame or as much as possible before the trigger point.

A radio button for auto zoom to the trigger point and a value field for the position on the screen.

Even better would be an extra field for delayed trigger. A value field for how long time before/after a trigger point the display should auto zoom to.

I use this frequently when looking at SPI and I2C data. You get a trigger from the MCU and then you want to look at what happened before or after the trigger. Usually it is close to the trigger point but often it is a fixed time befor the trigger or after the trigger.

Doing the above manually is time-consuming and sometimes irritating. This function is available on many other logic analyzers out there.

Tim

Status changed to: Live

Also, please preserve the scale and the horizontal location of the trigger from the previous capture, if one exists. That way, repeated triggers will produce the same image in the same place, only with different data

Tim

(#63441)
"Feature Request - view the captured trace at the beginning of the trigger point. I'm always having to click on the yellow 'T' to view the relevant data trace. If there's an option that after a trigger capture, the window shows the captured data right at the trigger without having to scroll or click the 'T' everytime."

Tim

(#63294)
"Currently, after a capture, I have to manually hit to position the trigger line at the center of the screen. Sometimes the center is fine, other times I need to scroll it just to the left margin. This is used often when I am looking to see the start of a sequence (ie. I2C, SPI, etc.)

The ideas is to have some sort of toggle option to do this automatically, a 3-state “switch” that will remember this setting.
1) Normal
2) Align automatically to center of screen
3) Align automatically to left of screen

Currently, I am debugging a DMA issue on a STM32 MCU. The first data transfer after RESET is okay, but the second one sometimes gets corrupted. To catch this, I press and hold RESET on the MCU, start LOGIC16, and release the RESET button.

LOGIC16 captures a few DMA frames and aligns to the end of the captured data. I then manually have to type each time to get to the first frame, and then manually scroll it to the left to compare the first and subsequent frames.

Because the DMA error is sporadic, I have to do this RESET and capture sequence multiple times to catch a bad frame. While not the end of the world, it does break the “flow” of debugging. Having the toggle option would streamline this kind of operation."

Tim

(#63337)
"Feature Request - Post capture auto-focus. At the end of the capture, the window view is empty because it shows the last capture interval after the signal. To go back to the trigger instant, it requires to zoom out, scroll to the trigger and zoom in again. This is a very annoying operation if you have to repeat it continuously for debug purposes. It would make so much sense to have an automatic action after the capture, which allows to choose for instance between "zoom fit" to fit the entire acquired waveform in the window, or "zoom trigger" to automatically zoom on the trigger."

Tim

(#61672)
"Feature Request - Scroll to trigger marker
After a triggered capture automaticaly scroll to trigger marker"

Tim

(#61452)
"Currently I'm bothered by the fact that the trigger point is not visible at the completion of a capture.
You'll agree that the trigger point is of special interest to the user (why else choose it as a trigger ?). Why then show data that's 200ms farther out ?
In my setup I'm interested in the data before and after the trigger, but I always want to start looking from the trigger point on.
I know that there's a short cut to get there, but I really would welcome the option to have the trigger shown on completion (selectable in the preferences ?) - and be able to specify where it is on the screen (not just the middle)"

Tim

discuss.saleae.com/t/improper-zoom-on-2-3-30/1069/5
"After a capture and trigger, I find that:
A) It does not automatically center the trigger rising edge after capture is finished"

Tim

#61051
"Feature Request - Configuration option to "jump to trigger' automatically after a capture. Eliminate repetition of after each capture"

Tim

(#59890)
"When using I2C, after the trigger occurs, the display always goes to the end of the buffer.

For instance, my current screen with the trigger point on the display has a resolution of 100px = 199us and my buffer depth is set to 100ms. I have my whole transfer framed in the screen. When I re-run my experiment, and after I re-trigger the display goes to the end of the buffer. So I then have to hit Cntl-J to go to the trigger point and THEN I have to move the image to the left to see the end of my packet.

Why can't Logic 2 just remember where in the buffer where I had my view set to an just go back to that location with respect to the trigger after I re-trigger? I am using the same settings every time. The Logic 2 software should be able to calculate where is this. I understand, that if I change something that decreasing the buffer depth then it may need to just default to end of buffer, but in normal usage, it should be able to just go back to the same point."

Tim

discuss.saleae.com/t/auto-zoom-to-trigger-point/915
"Trying to get the screen to always jump to the trigger point when stopped recording. Is this possible?
Still need the data recorded before and after the trigger. Just get the trigger to always center on the screen when done."

Ken

Its not just to the center of screen, its to the same point. So if the trigger location is 100 pix from the left of the screen, after the next trigger occurs and once the capture is complete, then the new capture trigger would also be 100pix from the edge of the screen. The same would be if I was displaying data from a 500msec capture and I was looking at data 200msec from the trigger. In this case the new trigger would also display the portion of the capture 200msec from the trigger. This is the way every low end and high end analyzer logic analyzer I have used in the past 20 years work. Even external triggers work the same way on all of the analyzers. This is the only analyzer I have used that doesn't follow this method. This allows the user to just look at the data they are interested in and not have to fiddle with the knobs after every capture. This is the way every Tek, Agilent, HP and LeCroy setups I have ever used.

Where this gets more difficult is with your long capture buffer setups. I think right now you display the data as it comes in after the trigger has occurred. So if I do a 10 second trigger and I have my view set at the "trigger" point, what do you do? Today you show the data as it comes it and then stop at the end of the buffer and display the data at the end of the buffer(the easy way). So the question here, is what do you do on these long captures. In this case, I have chosen my point of interest with respect to the trigger and that's not going to change unless I change it. So once a trigger occurs and once the data gets to the point of interest, the screen freezes at the point but continue to collect the data until the buffer is full and then it stops but the data displayed is still the point of interest.

Tim

Thanks for clarifying all of this Ken! These are very valid points you make:
"This allows the user to just look at the data they are interested in and not have to fiddle with the knobs after every capture."

Right now, you're absolutely right about the way we handle the viewpoint after a trigger occurs. When we get to improving trigger behavior, we'll certainly take all of this into account.

Tim

(#57967)
"When in trigger mode, display does not automatically jump to triggered event. This one is especially annoying since sometimes both hands are busy holding probes and having to let go of probes to view the event graphs just detracts from the smoothness of the process."

Tim

(#57634)
"Feature Request - move to trig point
a feature that can be easly and quickly to move to trig line (T0), especialy after capture completed."

Daniel

It would be nice to have a check-box option that causes the analyzer to automatically jump to the trigger after a capture to eliminate the manual ctrl-j I need to do each time. Ideally, there would be three options : align left of screen, align middle, align right. Also, a zoom parameter to apply after the alignment relative the trigger position. Currently, I have to do this manually after each capture. This option would streamline my measurement process. Cheers!

Tim

Merged with: Enable automatic jumping to trigger point after capture

Jiří

Thinking more about my original idea to jump to the trigger start (T0). I would like to slightly modify this request to "Jump to T0 +- time shift where I was before new sample" When I'm tracking the end of the communication packet I'm not interested in T0 (trigger start) but T0 + 10ms.
Shortly - the same behavior as was in 1.x version.
The same Jim suggested.

Tim

discuss.saleae.com/t/logic-2-3-17/872/7?
"Hi. How or where to set up to automatically jump to trigger start after measurement? It’s annoying on every measure to jump to start (CTRL+J). In 1.x version the position remained always on the same place between measurements. This is for me desired behavior."

Jim

Yes - like an automatic ctrl-J.
Traditional o'scope functionality allows the user to position the trigger location on the screen or even off-screen by allowing for a fixed delay.