Thanks for the detailed answer! 512/2 sample trigger resolution is definitely better for this application than 1638/2 sample trigger resolution. I still want to toss in a vote for additional trigger capabilities that might drive that down towards 1 sample 🙂
You’re right that I’m inevitably going to need the API, but for one-off debugging and quick checks it’s nice to stay in the GUI.
Is there a way to control the FMT resolution independently of the spectrogram in Spike since it also uses Zero-Span>FFT Settings>RBW?