Recent Changes - Search:

HomePage

LBA

Mt Pleasant 26m

Ceduna 30m

Mt Pleasant 14m

Ceduna-Hobart Interferometer

Schedules

AuScope

PmWiki

edit SideBar

Oscillator Control

MtPleasant26m.OscillatorControl History

Show minor edits - Show changes to markup

February 18, 2013, at 11:14 PM by JMc -
Changed lines 3-6 from:

The preferred way of controlling the Mt. Pleasant oscillators is now through the oscillator_gui.sh script. This is in ~oper on hobart but there is a desktop shortcut on newsmerd to easily start this (labeled “OSCILLATOR GUI”). It lists the current status of the known oscillators, and can set the frequencies and levels. The script provides instructions on its use.

There are two caveats - the script currently returns zero frequencies and power levels if the device is uncontactable (off at the power switch of not connected to the GPIB network). It also returns an output power level of 0.000 dBm when the RF output is off.

to:

The preferred way of controlling the Mt. Pleasant and Ceduna oscillators is now through the oscillator_gui.sh script. This is in ~oper on hobart and pcfscd but there is a desktop shortcut on newsmerd to easily start this (labeled “OSCILLATOR GUI”). It lists the current status of the known oscillators, and can set the frequencies and levels.

The image below shows the script in operation

http://fourier.phys.utas.edu.au/wiki_images/oscillator_gui.png

Each of the listed oscillators can be selected either by entering the full name as listed, or by the index number. The script will then prompt you for the desired frequency and level. It will then set the oscillator and refresh the display.

There are some caveats - the script requires the Field System to handle the GPIB communications correctly. It currently returns zero frequencies and power levels if the device is uncontactable (off at the power switch of not connected to the GPIB network). It also occasionally misreads a line but this can be corrected by refreshing the display.

Added lines 16-18:
Changed lines 24-27 from:

Control of the Agilent (first LO) and remote control of the second LOs (SML01, SMY01) is currently handled by some shell scripts on hobart. The current settings can be checked with ./oscillator_query.sh and set with ./oscillator_control.sh . Both programs should be run from ~oper on hobart.

From an oper@hobart terminal, use ./oscillator_query.sh Agilent to check the current frequency and power level of the Agilent. The script returns a string like Agilent is set to 12.200 GHz and 16.000 dBm. ./oscillator_query.sh SML01 and ./oscillator_query.sh SMY01 return the settings for the SML01 & SMY01 respectively. If the returned frequency is given as 0.000, try re-running the script - this is usually a misreading of the data. If the power is given as 0.000 dBm, this may indicate that the oscillator is off. Again, try re-running the script first before changing anything.

to:

Control of the Agilent (first LO) and remote control of the second LOs (SML01, SMY01) is currently handled by some shell scripts on hobart and pcfscd. The current settings can be checked with ./oscillator_query.sh and set with ./oscillator_control.sh . Both programs should be run from ~oper on hobart/pcsfcd.

From an oper@hobart terminal, use ./oscillator_query.sh Agilent to check the current frequency and power level of the Agilent. The script returns a string like Agilent is set to 12.200 GHz and 16.000 dBm. The frequency reference is EXT and the output in ON.. ./oscillator_query.sh SML01 and ./oscillator_query.sh SMY01 return the settings for the SML01 & SMY01 respectively. If the returned frequency is given as 0.000, try re-running the script - this is usually a misreading of the data. If the power is given as 0.000 dBm, this may indicate that the oscillator is off. Again, try re-running the script first before changing anything.

Changed line 32 from:

N.B. For single frequency (dual pol) experiments, SML01 is run through a splitter (to provide the two pols) and SMY01 is not used.

to:

N.B. For single frequency (dual pol) experiments, SML01 and SML02 should be set to the same frequencies

August 03, 2012, at 02:00 AM by 10.100.249.33 -
Deleted lines 0-1:

Oscillator Control

Changed lines 9-13 from:

Command-line control

to:

Command-line control

August 03, 2012, at 02:00 AM by 10.100.249.33 -
Added lines 3-15:

Using the GUI

The preferred way of controlling the Mt. Pleasant oscillators is now through the oscillator_gui.sh script. This is in ~oper on hobart but there is a desktop shortcut on newsmerd to easily start this (labeled “OSCILLATOR GUI”). It lists the current status of the known oscillators, and can set the frequencies and levels. The script provides instructions on its use.

There are two caveats - the script currently returns zero frequencies and power levels if the device is uncontactable (off at the power switch of not connected to the GPIB network). It also returns an output power level of 0.000 dBm when the RF output is off.

If you wish to turn off the RF output, you can do this by sending “off” as the level. Similarly, you can turn the output back on by sending “on”

Command-line control

Changed lines 20-21 from:

To change the oscillator’s settings use ./oscillator_control.sh Agilent 12.2 16 (to set the Agilent to 12.2 GHz, 16 dBm), or ./oscillator_conrtol.sh SML01 878 10 (to set SML01 to 878 MHz, 10 dBm). The script assumes that you’re specifying the Agilent frequency in GHz and all others in MHz, and that all levels are specified in dBm. The script returns the same output string as ./oscillator_query.sh - check that the settings are correct.

to:

To change the oscillator’s settings use ./oscillator_control.sh Agilent 12.2 16 (to set the Agilent to 12.2 GHz, 16 dBm), or ./oscillator_control.sh SML01 878 10 (to set SML01 to 878 MHz, 10 dBm). The script assumes that you’re specifying the Agilent frequency in GHz and all others in MHz, and that all levels are specified in dBm. The script returns the same output string as ./oscillator_query.sh - check that the settings are correct.

April 24, 2012, at 05:55 AM by 131.217.6.6 -
Changed lines 3-4 from:

Control of the Agilent (first LO) remote control of the second LOs (SML01, SMY01) is currently handled by some shell scripts on hobart. The current settings can be checked with ./oscillator_query.sh and set with ./oscillator_control.sh . Both programs should be run from ~oper on hobart.

to:

Control of the Agilent (first LO) and remote control of the second LOs (SML01, SMY01) is currently handled by some shell scripts on hobart. The current settings can be checked with ./oscillator_query.sh and set with ./oscillator_control.sh . Both programs should be run from ~oper on hobart.

Changed lines 9-11 from:

For the second LOs (SML01, SMY01, etc), if you’re present at Mt Pleasasnt you can adjust them manually. They’re located in rack 5. To adjust the frequency, press the FREQ button (to the right of the screen), type in the frequency in MHz and finally press the MHZ button to activate the new setting. For level adjustment, select LEVEL, enter the level in dBm & press the dBm button to activate the new setting.

to:

If you’re present at Mt Pleasant it is also possible to adjust the second LOs (SML01, SMY01) manually. They are located in rack 5. To adjust the frequency, press the FREQ button (to the right of the screen), type in the frequency in MHz and finally press the MHZ button to activate the new setting. For level adjustment, select LEVEL, enter the level in dBm & press the dBm button to activate the new setting.

N.B. For single frequency (dual pol) experiments, SML01 is run through a splitter (to provide the two pols) and SMY01 is not used.

April 23, 2012, at 01:26 PM by JMc -
Changed lines 7-9 from:

To change the oscillator’s settings use ./oscillator_control.sh Agilent 12.2 16 (to set the Agilent to 12.2 GHz, 16 dBm), or ./oscillator_conrtol.sh SML01 878 10 (to set SML01 to 878 MHz, 10 dBm). The script assumes that you’re specifying the Agilent frequency in GHz and all others in MHz, and that all levels are specified in dBm. The script returns the same output string as ./oscillator_query.sh - check that the settings are correct.

to:

To change the oscillator’s settings use ./oscillator_control.sh Agilent 12.2 16 (to set the Agilent to 12.2 GHz, 16 dBm), or ./oscillator_conrtol.sh SML01 878 10 (to set SML01 to 878 MHz, 10 dBm). The script assumes that you’re specifying the Agilent frequency in GHz and all others in MHz, and that all levels are specified in dBm. The script returns the same output string as ./oscillator_query.sh - check that the settings are correct.

For the second LOs (SML01, SMY01, etc), if you’re present at Mt Pleasasnt you can adjust them manually. They’re located in rack 5. To adjust the frequency, press the FREQ button (to the right of the screen), type in the frequency in MHz and finally press the MHZ button to activate the new setting. For level adjustment, select LEVEL, enter the level in dBm & press the dBm button to activate the new setting.

April 23, 2012, at 01:19 PM by JMc -
Added lines 1-7:

Oscillator Control

Control of the Agilent (first LO) remote control of the second LOs (SML01, SMY01) is currently handled by some shell scripts on hobart. The current settings can be checked with ./oscillator_query.sh and set with ./oscillator_control.sh . Both programs should be run from ~oper on hobart.

From an oper@hobart terminal, use ./oscillator_query.sh Agilent to check the current frequency and power level of the Agilent. The script returns a string like Agilent is set to 12.200 GHz and 16.000 dBm. ./oscillator_query.sh SML01 and ./oscillator_query.sh SMY01 return the settings for the SML01 & SMY01 respectively. If the returned frequency is given as 0.000, try re-running the script - this is usually a misreading of the data. If the power is given as 0.000 dBm, this may indicate that the oscillator is off. Again, try re-running the script first before changing anything.

To change the oscillator’s settings use ./oscillator_control.sh Agilent 12.2 16 (to set the Agilent to 12.2 GHz, 16 dBm), or ./oscillator_conrtol.sh SML01 878 10 (to set SML01 to 878 MHz, 10 dBm). The script assumes that you’re specifying the Agilent frequency in GHz and all others in MHz, and that all levels are specified in dBm. The script returns the same output string as ./oscillator_query.sh - check that the settings are correct.

Edit - History - Print - Recent Changes - Search
Page last modified on February 18, 2013, at 11:14 PM