jjoonathan,
You can change the FFT size used with FMT triggering by adjusting the RBW. If you change the RBW to 1MHz for example, a 1024pt FFT will be used (round up to the next power of 2).
You might need to adjust your FMT after you increase the RBW since the noise floor will increase.
The min/max FFT sizes that are actually used on the hardware are [512/16384]. Anything below or above those values will be clamped.
Hopefully this help improve the jitter enough to be usable.
You might already be aware, the API is available, and the 250MS/s I/Q captures are can be programmatically controlled through the “Segmented I/Q captures” API. We have several examples of this in the SDK. For your chirped signal, you could setup the video trigger level as you are in Spike, collect the data, and realign the trigger post acquisition. (basically run another video trigger in software). Justin mentions the video trigger limitations in your other thread.
We appreciate your feedback and detailed posts. It’s great to see the wideband captures being pushed to their limits!
https://productbundlesdemo.kinsta.cloud/software/signal-hound-software-development-kit-sdk/
