Startwin "do not set conditions" behaviour

[Karsten Goemann]

I've been using Startwin a bit recently for performance testing, dead time measurements etc on our new JEOL 8530F Plus.

It is nice that it does have a "do not set conditions" option if for example I just want to check something quickly at a higher beam current / higher count rate. But currently the "do not set conditions" flag only seems to apply to counting, not to peaking and PHA acquisitions.  Is this by design? If not, could it be changed to also apply to operations like peaking and PHA/bias scans?

[John Donovan]

I've been using Startwin a bit recently for performance testing, dead time measurements etc on our new JEOL 8530F Plus.

It is nice that it does have a "do not set conditions" option if for example I just want to check something quickly at a higher beam current / higher count rate. But currently the "do not set conditions" flag only seems to apply to counting, not to peaking and PHA acquisitions.  Is this by design? If not, could it be changed to also apply to operations like peaking and PHA/bias scans?

Hi Karsten,
We should be able to do that for you.  I'll let you know.
john

[John Donovan]

I've been using Startwin a bit recently for performance testing, dead time measurements etc on our new JEOL 8530F Plus.

It is nice that it does have a "do not set conditions" option if for example I just want to check something quickly at a higher beam current / higher count rate. But currently the "do not set conditions" flag only seems to apply to counting, not to peaking and PHA acquisitions.  Is this by design? If not, could it be changed to also apply to operations like peaking and PHA/bias scans?

Hi Karsten,
The latest update of PFE has Startwin now respecting the "do not send conditions" menu for PHA and peaking scans.
john