The backend to be used can be manually selected as follows:
where bckname is the name of the backend. At present, the only available choice is:
Total Power - focus selector¶
The TotalPower backend works as a “focus selector”, sending
the signal from the wanted receiver to any other backend. For this reason,
it must be set up even when acquisitions take place using another
backend. This is accomplished simply using the overall setup commands
Bandwidth and sampling rate can be changed using:
- [sect] is an integer specifying the section number
- [startFreq] is the initial frequency for the section (not applicable for TPB)
- [bw] is a double for the bandwidth (MHz)
- [feed] is the number of the feed connected to the section (not applicable for TPB)
- [mode] is the polarisation mode (not applicable for TPB)
- [sampleRate] is also given in MHz
- [bins] is the number of frequency bins for the given section (not applicable for TPB)
To leave a parameter at its previously set value, or equivalently skip it when it is not applicable, use an asterisk. For the TPB, in particular, always use:
where bw can be chosen between two options (MHz):
Larger bandwidths (1250, 2000) are technically possible, but make no sense as long as the receivers’ IF bandwidth is restricted to 500 MHz.
Consider that the above-listed bandwidths do not correspond to the true observed ones, for the reason discussed in Initial Setup. When accumulations of the data “dumps” are required before integrating them to the output file, it is possible to set the integration time as follows:
where N is given in milliseconds.
Each section is provided with an attenuator, to manage the signal intensity. To set the desired attenuation:
where sect is the section number and att can vary, for the TPB, form 0 dB to 15 dB, with a 1 dB step.
If a backend re-initialization is needed, use:
code can be
This command resets the backend only, setting it to the default values foreseen for the specified focus/receiver. After the frontend/backend configuration is changed, it is necessary to update the value for the beamsize (HPBW), which is computed as a function of the actually observed band and is used – during the observations – to evaluate the pointing accuracy. This is accomplished using the command:
which uploads to the system the parameters relative to section number [sect] (you can generally use 0, which exists for all the receivers, unless you need to observe only with a different feed).
Calmux - calibration diode multiplexer¶
The Calmux is a multiplexer that allows to choose which backend is entitled to control the calibration diode on the frontend. This device is required when more than one backend has the capability to exploit the fast switching. This is the case for DBBC (VLBI) and TotalPower backends in Noto. When observing with DISCOS, the proper calmux configuration is set transparently during the setup phase. In case a specific configuration is required, use:
code can be
- Since then calmux control port is single-client, it is mandatory for DISCOS to properly configure it to make sure that no other clients are connected at the time of the telescope setup.