500ms/div ... 100mV/div vertical.
That's in ROLL mode so NO triggering until the display is filled then it should trigger no prob and maybe even get into Zoom mode where you can examine the trace in further detail.
Anyways, would love to see a screenshot if you can.
It's not in roll mode. Objectively I placed the trigger 1 div into the left side of the screen and waited. It is supposed to trigger there, then fill the remainder of the sample memory and chuck it on the screen instantly after the trigger. But it was doing full captures which were slowly sliding left by half a div per capture (auto mode) and no trigger indicator was happening. In single mode, bugger all.
My purpose here was to grab a monostable trigger event and then measure the delay.
Alas doing a self cal seems to have fixed it now (or power cycling it - who knows?!?!) but that's just shit. Can't screenshot it now because the damn problem has gone away. I was going to video it this morning. Grr.
Edit: I validated trigger level, trigger mode, trigger channel several times thinking it was me but it appears it wasn't this time. It usually is me!
![Laughing :-DD](https://www.eevblog.com/forum/Smileys/default/smiley_laughing.gif.pagespeed.ce._hfWAz_QHO.gif)
500ms/div ... 100mV/div vertical.
Self cal has passed and it actually triggers now on 1/2
. Looks like something analogue had drifted off ffs. Literally only did self cal on Sunday. piece of crap.
Looking at Keysights again now ![Laughing :-DD](https://www.eevblog.com/forum/Smileys/default/smiley_laughing.gif.pagespeed.ce._hfWAz_QHO.gif)
This should fit your use cases. Perhaps. ![Grin ;D](https://www.eevblog.com/forum/Smileys/default/xgrin.gif.pagespeed.ic.QVVz6XIT20.png)
https://www.ebay.com/itm/253848130391
I don't think even both my kidneys are worth that
![Laughing :-DD](https://www.eevblog.com/forum/Smileys/default/smiley_laughing.gif.pagespeed.ce._hfWAz_QHO.gif)