Upgrade to PRO & Simultaneous Measurements

markvaughan

Hi.

I was running version 9.19 on standard license with Siglent SVA1032X, where scanning both sets worked bringing the traces for both onto teh screen as it moved between each segment.

I've just upgraded to the Pro licence, the new license file placed into the main directory, I've done install license, and About now shows PRO, so I believe that's correct. (I have not played with or implemented real time scanning yet)

My problem is that the scanning for both sets doesn't appear to be working.

I have 'Enable simultaneous measurement of 2 traces' ticked in options, which puts a '2' on the Play Arrow.

I have 'Show checkboxes for consecutive measurements of both sets' ticked in options.

On the main screen, I have the box 'Run Both sets', which I can click, or unclick but it doesn't run traces consecutively

When I click Play, if 'Run Both Sets' is set it turns it off, and just does the measurement set 1 or 2, as selected, and I have to manually select to do the next one.

If I unset Enable simultaneous, and set Run Both sets, then it runs one set after the other as expected.

I must have something set wrong, but not sure where.

robert

The “Enable simultaneous measurement of 2 traces” option and the “Run Both sets” checkbox are mutually exclusive. In total, they have the same effect on a scan in which Set1 and Set2 have the same frequency information. With the first method, two detectors are read out simultaneously from the spectrum analyzer during the measurement; with the second method, the sets are measured one after the other. Therefore, the first method is faster as only one measurement is required for 2 detectors. However, not all devices have this function. If both methods are activated at the same time, “Run Both Sets” is automatically deactivated. This is also displayed in red in the message window

Info: play 16
Warning: and is not possible
Info: ignoring

markvaughan

Thanks for a response Robert, what you've said is exactly how I'd thought/remembered it worked before upgrading.

It turns out one of my segment files for the scan was corrupt, with additional characters in the detector area between Q and Peak, each call for the detector being exactly the same, but wrong.

Refreshed the install just in case

Rewrote a fresh version of my QP segment file, and it's all been running fine last week.

Might be of use to someone else though, if they get issues, try testing another standard, then come back and look at the segment file in the ones that were failing

Thanks Mark