When using a scope you set up one trigger and then everything is plotted relative to that one trigger point across all channels. The trigger point effectively determines where t = 0 seconds, so it wouldn't make sense to have multiple trigger points. If one of the channels has data that is moving relative to another channel then you either need to pick a trigger that is applicable to both channels, use trigger holdoff to ensure you are triggering at the same location (for example for bursted packets), or use a more complex trigger type like a pattern trigger or serial trigger. Check out chapter 10 in the DSOX2014A User's Guide for examples of what is available and how to set them up.

big mistake.. why putting money after a Keysight when you can get a Fnirsi for even less. "Fnirsi" is where you wanna be and where all the cool kids are moving. You can also look at a "Tek" scope, but hanTEK is not always the best in software. Fnirsi is pionering the scope market. it got a ring to it.. being able to tell your clients, "here is my test report that I made on my Fnirsi" (that sounds potent) "Here is my test report I made on my TEK" (yes, that also got a nice ring to it, and why hanTEK also is moving quite a lot of scopes these years. "Here is my test report I made on my KEY" (nahh, just soudns weird and confusing) Fnirsi scopes is where its at in 2022. Cheers and your welcome, you need to understand I do this for a living, guide people on social media.

@@JAKOB1977 Some people go first class others go coach. It clearly costs more but the psychological factor is worth it to me!