fesa-fg-dump, fesa-fg-load, fesa-fg-arm
Both tools are using Python cmwrda, so don't forget to specify production environment by option
--pro
or by setting environment variable
RDAPY_SYSTEM_ENVIRONMENT=pro
fesa-fg-dump
Extracts ramp data from function generators (FESA class PowerSupply and ists subsets), displays and writes to file.
Data are dumped for a range of beam processes. By default, all available ramps (voltage, current, frequency, phase, resonance frequency, detune-phase) are dumped.
Either polynominal data (property
Setting
) or raw data (function generator coefficients, property
RawRampData) can be dumped.
usage: fesa-fg-dump --pro|--dev <device> [options]
device: nomenclature
options:
--pro, --dev select production or development (default)
environment var. 'RDAPY_SYSTEM_ENVIRONMENT=pro' may be used
-f <filename> default: <device>.rmp / <device>.raw
-nf don't write to file, display only
-l <bp min> lower limit of beam process range
-u <bp max> upper limit of beam process range
-p <beam-process> read only specified beam process
-r read raw data
-t <ramp-type> ramps to be read, default: all ramps
c: current, f: frequency, v: voltage,
p: phase, d: detune-phase, r: resonance frequ.
fesa-fg-load
Loads ramp data which are dumped by
fesa-fg-dump to device.
usage: fesa-fg-load --dev|--pro <filename> [<device>]
file: text file, containing JSON ramp data
device: nomenclature
options:
--pro, --dev select production or development (default)
environment var. 'RDAPY_SYSTEM_ENVIRONMENT=pro' may be used
-s <server-name> set name of RDA front-end server (e.g. PowerSupplyRf_DU.scuxl0060)
will not look-up in data base for device name
-v verbose, dispose data values
If not given, device name is used as stored in the data file.
fesa-fg-arm
Sets the armFg-flag in the property Setting of ramped devices (values true or false).
usage:
fesa-fg-arm [--pro|--dev] <nomenclature> t|f <beam-process nr>
don't forget option --pro for devices in production environment
example:
fesa-fg-arm --pro XGS00BE_F t 99