I'm programming an application in which RF pulses are manually sent using a PSG. The pulse generator sync output of the PSG is connected to three MXAs trigger input, those are configured in zero span mode.
I'd like to fetch the traces on the MXA after the pulse has been sent. Nevertheless the MXAs change to "wait for trigger" very fast and it seems that they are unresponsive to SCPI commands in that state.
If I set free run triggering in the MXA my software fetches the traces without problems but I need to use external trigger to capture the RF pulses.
What shall I do so the MXAs are responsive to my SCPI commands and I can retrieve the traces?
Regards,
Òscar
Hello Oscar,
The issue could be within the order or the timing of your SCPI commands for the PSG. Setting up the MXA commands first puts the MXA in the “Wait for trigger” state. It’s the PSG command that will “activate” the trigger.
There are several ways to exit the waiting state depending on the type of trigger. Setting the frequency or power is one way, The source settle command works if you’re using the internal firmware. If you are using signal studio, adding a marker in your waveform file also works. The amplitude is what activates the trigger when using a video trigger.
Here is the link to the SCPI command reference document for your reference: http://literature.cdn.keysight.com/litweb/pdf/E8251-90256.pdf