We have discovered the reason behind the false trigger. It is because while the longest period of zero level signaling without stopping transmissions is 180 ns, all the triggers we have tried so far trigger on either a high or low level and since the signaling could be all -1 and 0 (or all 1 and 0) ...

We have discussed in-house in the past that if Window Dropout had a way to select only Entering or only Exiting (instead of the way it currently works where it is both entering or exiting) that this might help our use case.

I wanted to update that we have seen the Level Dropout triggers on both start and end of transmissions rather than on only the end of transmissions as desired.

The signal is not always the same length. To clarify I specifically do not want to trigger on both start and stop at the same time, these are two different asks for two different use cases we have. The largest space in the signaling that we would not want to consider a start or stop of transmitting ...

We have attemted to use Pulse Width for start of transmissions, the issue we find is that it has a ton of false triggers. From the description of the trigger it seems it shouldn't so maybe this is a bug in the software. We have assumed this is a likely case as it is not consistent. Sometimes we get ...

Yes, you may publish them here. The signaling is PAM3 and in theory, the longest period of 0's in normal signaling could be up to 120 ns plus a small tolerance. So anything greater than that we would consider stopping transmitting for that trigger. The starting transmitting trigger is obviously just...

Please send an FTP login.

I have two files one with the start of transmissions example and one with the end of transmissions example. I would like the trigger to be based on Channel B starting transmissions in the one and on Channel B stopping transmissions in the other. However, they are too large to attach here and zipping...

Yes as I said in my post I used our hardware that we can control a logical signal on channel A to go high at the same time that we stop transmissions (or start them) in order to show what we need to be able to trigger on. However, we need to be able to trigger on the Channel B type event in the scre...

This would trigger on every edge though, which would have a bunch of triggers we don't want and can't have happening for our use case. I need it to only trigger on the types of events shown in the images. A rising or falling edge trigger would trigger millions of times before that as well as the sig...

I didn't get a notification of this response for some reason. I am attaching a pssettings file for this. The screenshot is here:

Our team has been attempting to setup triggers that reliably trigger when transmissions either start or stop on a channel. We need one trigger to fire only if transmissions start. We need a second trigger to fire only if transmissions stop. We have looked at the Trigger resources in the User Guide, ...

I am trying to find a way to trigger when a channel's transmissions stop. But I do not want it to trigger when the channel's transmissions start again. I had thought this would be a level dropout trigger, however, this does not work as I would expect. This image was taken with the following level dr...

This would be useful for our team as well.

I am curious if there will be an update to allow this feature again. My organization would greatly benefit from this feature.