Recent Changes - Search:

HomePage

LBA

Mt Pleasant 26m

Ceduna 30m

Mt Pleasant 14m

Ceduna-Hobart Interferometer

Schedules

AuScope

PmWiki

edit SideBar

IVS Observing

MtPleasant26m.IVSObserving History

Hide minor edits - Show changes to markup

March 01, 2011, at 01:11 AM by 131.217.6.6 -
Changed lines 1-3 from:

IVS Observing

These pages describe the full procedure for IVS experiments, from setting up through to shipping disks to the correlators.

to:

IVS Observing on the 26m antenna

These pages describe the full procedure for IVS experiments on the 26m antenna only, from setting up through to shipping disks to the correlators. For information on running IVS observations on the AuScope 12m telescopes, go to the AuScope Operations Wiki.

March 01, 2011, at 01:09 AM by 131.217.6.6 -
Deleted line 5:
  • Setting up IVS experiments on the Hobart 12m
December 02, 2010, at 12:08 AM by 131.217.63.235 -
Changed lines 13-14 from:
to:
December 02, 2010, at 12:07 AM by 131.217.63.235 -
Added lines 1-2:

IVS Observing

Added line 10:
Changed lines 13-22 from:

Finishing up IVS experiments on the 26m

 (see; Setting up IVS Experiments )

Processing Logs after an experiment

Which VC’s to drop if one or more die

to:
December 02, 2010, at 12:06 AM by 131.217.63.235 -
Changed lines 13-98 from:

When the experiment has ended (and the schedule has come to an end), you will need to check the cable calibration.

Check the cable measurement system.

In the operator input window issue,

cablen

Add in the test length of cable.
Check the cable measurement system with the longer cable by issuing the command

cablel

Subtract the 2 readings by issuing the command

cablediff

Write the difference in the written log sheet. It should be about 760 usec. Remove the extra cable length!

Once this has been done you can then terminate the field system by typing:

terminate

You then need to close the Field system monitor running on smerd by moving you mouse over the greem window and pressing Ctrl+C. (otherwise the alarm will sound)

Now park the antenna using vdesk if the antennas is not already in the park position.

Alarms or other errors.

With time you’ll be able to fix most problems yourself. The telescope manager will let you know if there are certain problem to lookout for during a given experiment, and may suggest techniques to overcome those problems.

If you encounter a problem which you are unable to solve please contact someone for assistance.

Some tricks.

  • For red alarm light on IF3 on MKIV, enter in the field system (fs) operator window on hobart,
    if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, and rxmon checks out ok, enter in fs operator window,
    check=*,-rx
  • For constant annoying errors that read “Integrator total power overflow on if2″ (or something similar), and you’re sure the power levels on the vco’s and the total power on if2 and if3 are ok, enter in fs operator window,
    check=*,-ifd
  • If the drive pc has been restarted and schedule is still running on Field System use,
    source=disable
    to re-establish communication between fs and antenna drive pc.
  • To repair some kinds of time discrepancies between MK 5 and hobart, (e.g clkoff reports !+0.5s, and monitor also reports time as a few seconds off)
    sy=run setcl offset
  • For MKIV general red alarm light errors, enter in fs operator window,
    valarm
    ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window,
    vc15=200,2
  • Error: v1 frequency does not check with requested value (and you have phase on vc1),
    check=*,-v1
  • See also: Fixing problems such as recovering from power failures
to:
December 02, 2010, at 12:05 AM by 131.217.63.235 -
Changed line 7 from:
to:
Changed lines 10-11 from:
to:

Finishing up IVS experiments on the 26m

When the experiment has ended (and the schedule has come to an end), you will need to check the cable calibration.

Check the cable measurement system.

In the operator input window issue,

cablen

Add in the test length of cable.
Check the cable measurement system with the longer cable by issuing the command

cablel

Subtract the 2 readings by issuing the command

cablediff

Write the difference in the written log sheet. It should be about 760 usec. Remove the extra cable length!

Once this has been done you can then terminate the field system by typing:

terminate

You then need to close the Field system monitor running on smerd by moving you mouse over the greem window and pressing Ctrl+C. (otherwise the alarm will sound)

Now park the antenna using vdesk if the antennas is not already in the park position.

Alarms or other errors.

With time you’ll be able to fix most problems yourself. The telescope manager will let you know if there are certain problem to lookout for during a given experiment, and may suggest techniques to overcome those problems.

If you encounter a problem which you are unable to solve please contact someone for assistance.

Some tricks.

  • For red alarm light on IF3 on MKIV, enter in the field system (fs) operator window on hobart,
    if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, and rxmon checks out ok, enter in fs operator window,
    check=*,-rx
  • For constant annoying errors that read “Integrator total power overflow on if2″ (or something similar), and you’re sure the power levels on the vco’s and the total power on if2 and if3 are ok, enter in fs operator window,
    check=*,-ifd
  • If the drive pc has been restarted and schedule is still running on Field System use,
    source=disable
    to re-establish communication between fs and antenna drive pc.
  • To repair some kinds of time discrepancies between MK 5 and hobart, (e.g clkoff reports !+0.5s, and monitor also reports time as a few seconds off)
    sy=run setcl offset
  • For MKIV general red alarm light errors, enter in fs operator window,
    valarm
    ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window,
    vc15=200,2
  • Error: v1 frequency does not check with requested value (and you have phase on vc1),
    check=*,-v1
  • See also: Fixing problems such as recovering from power failures
    (see; Setting up IVS Experiments )
December 02, 2010, at 12:03 AM by 131.217.63.235 -
Added line 7:
Changed lines 10-100 from:

Finishing up IVS experiments on the 26m

When the experiment has ended (and the schedule has come to an end), you will need to check the cable calibration.

Check the cable measurement system.

In the operator input window issue,

cablen

Add in the test length of cable.
Check the cable measurement system with the longer cable by issuing the command

cablel

Subtract the 2 readings by issuing the command

cablediff

Write the difference in the written log sheet. It should be about 760 usec. Remove the extra cable length!

Once this has been done you can then terminate the field system by typing:

terminate

You then need to close the Field system monitor running on smerd by moving you mouse over the greem window and pressing Ctrl+C. (otherwise the alarm will sound)

Now park the antenna using vdesk if the antennas is not already in the park position.

Alarms or other errors.

With time you’ll be able to fix most problems yourself. The telescope manager will let you know if there are certain problem to lookout for during a given experiment, and may suggest techniques to overcome those problems.

If you encounter a problem which you are unable to solve please contact someone for assistance.

Some tricks.

  • For red alarm light on IF3 on MKIV, enter in the field system (fs) operator window on hobart,
    if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, and rxmon checks out ok, enter in fs operator window,
    check=*,-rx
  • For constant annoying errors that read “Integrator total power overflow on if2″ (or something similar), and you’re sure the power levels on the vco’s and the total power on if2 and if3 are ok, enter in fs operator window,
    check=*,-ifd
  • If the drive pc has been restarted and schedule is still running on Field System use,
    source=disable
    to re-establish communication between fs and antenna drive pc.
  • To repair some kinds of time discrepancies between MK 5 and hobart, (e.g clkoff reports !+0.5s, and monitor also reports time as a few seconds off)
    sy=run setcl offset
  • For MKIV general red alarm light errors, enter in fs operator window,
    valarm
    ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window,
    vc15=200,2
  • Error: v1 frequency does not check with requested value (and you have phase on vc1),
    check=*,-v1
  • See also: Fixing problems such as recovering from power failures
    (see; Setting up IVS Experiments )
to:
December 01, 2010, at 11:59 PM by 131.217.63.235 -
Changed lines 8-112 from:
to:

Finishing up IVS experiments on the 26m

December 01, 2010, at 11:56 PM by 131.217.63.235 -
Changed lines 2-3 from:
to:
Added line 6:
Deleted lines 8-103:

Setting up IVS Experiments

First see… Getting Hobart field system up on NewSmerd

Because there is a need to run the dish for research other than IVS for as many hours as possible even after normal work hours, it may be neccesary for you to set up an IVS experiment prior to observing. The purpose of these notes is to tell you how to do it. Please let us know if anything is missing from these notes.

  • These instructions assume the .skd and .prc files are in place on Hobart. If not, you will need to run drudg. See MtPleasant26.DrudgIVS
  • Move the focus position to −256, +248, +18 (x,y,z) (bottom of rack 2)
  • Ensure 2020 LO Kill switch is off. (bottom of rack 2)
  • Ensure that cables A21 and A22 are each terminated in 50 ohms. Top of rack 5
  • Ensure phasecal cable is in. (Back of rack 10)
  • Ensure alarm cable is connected. (Back of rack 10)
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using the graphic interface on hobart,
    oscillator_control_gui.pl
    or use the command line version, and for explanation of usage, type,
    oscillator_control - - help
  • Check there is space on Hobart for the new log using the command

df -k /usr2/log

Logs are typically less than 2 MB in size. Make sure Mark5A software is running on mkv by typing

ps auxww | grep -i mark

and look for Mark5A -m0. If not then the command on the Mark5 recorder is

Mark5A -m0 &

Check that rs.tcl is not running as FS will give GPIB errors otherwise.(rs.tcl no longer in use??)

If the previous VLBI experiment was not mark5 (ie S2) then run

chooser mk5

in the PCFS log window prior to the next step, type fs to start Field System on Hobart. Watch for errors. Load the experiment procedure library.
eg
proc=rdv58ho

Use the experiment name with “ho” on the end. Run the setup. The command for an R1 experiment is “setupsx”. Look in the experiment procedure library printout to find the correct setup procedure name.

  • Check all the VCs are happy, ie no red lights and no nasty messages appearing in pcfs log window. Command “VC15=200,2″ will load some values to keep VC15 happy which is not normally used. Command “valarm” will turn off any remaining alarm lights on the VCs.
  • Check that if3 is happy with no red lights. You may need if3=alarm
  • Check the formatter error light is off. You may need to do “form”
  • Check that power reading for each VC USB is between 0.1 and 1.0 volt
  • Check that phasecal is visible for each usb out on all VCs
  • Set the cal to be controlled by PCFS.
    smerd:observer:>calu -m pcfs
  • Check that caltsys works. Caltsys results between 50 and 70k
  • Check that weather works. wth
  • Check that cable works. cablen
    Result is 15XXX
  • Check that the formatter PPS coax (instead of hmaser) goes to HP53131A
    counter channel 1.
  • Check that fmout-gps works. clkoff
  • Check that the mark 5 has a blank module big enough for the experiment. Compare the Drudg summary of the schedule with the label on the front of the disk module.
  • Run disk_pos to check the disk module is empty
    Result should be 0/0 otherwise the disk module contains data.
  • Record some data. disk_record=on
  • Observe green disk activity lights on module
  • Stop recording. disk_record=off
  • Check the recording. scan_check
  • Observe the time and details in the PCFS log window for the test recording.
  • Check the record pointer. disk_pos
  • Erase the module. mk5=protect=off; mk5=reset=erase
  • Check the record pointer. disk_pos Should now be zero.
  • Start the schedule. schedule=r1186ho,#1
  • Watch PCFS log for errors.
  • Check the Mark5 is ready with a module loaded.
  • Continue the schedule with the command. mk5relink
  • Check the antenna is on source. onsource
  • Check the cable measurement system. cablen
  • Add in the test length of cable.
  • Check the cable measurement system with the longer cable. cablel
  • Subtract the 2 readings. cablediff
  • Write the difference in the written log sheet. It should be about 760 usec.
  • Remove the extra cable length!
  • Again check the antenna is on the source. onsource.
  • Check everything on the experiment check list.
  • Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these utilities are accessible from Field system menu when you click on the background screen of Hobart.
  • Start FS monitor on Smerd by clicking on the FS Monitor menu button and logging in to hobart as oper in the green window.

Once the schedule starts, watch the log and everything closely for the first scan or so.

Send the start message. Use the template in smerd:/vlbobs/ngs/start You can use observer@ares account and pine email program if you wish.

November 30, 2010, at 11:05 PM by 131.217.63.235 -
Added lines 1-7:

These pages describe the full procedure for IVS experiments, from setting up through to shipping disks to the correlators.

November 08, 2010, at 05:24 PM by Jim Lovell -
Changed lines 285-286 from:
  • See alsohttp://www-ra.phys.utas.edu.au/wiki/index.php?n=MtPleasant26m.FixingProblemsSuchAsRecoveringFromPowerFailures
to:
November 08, 2010, at 05:23 PM by Jim Lovell -
Added lines 285-286:
  • See alsohttp://www-ra.phys.utas.edu.au/wiki/index.php?n=MtPleasant26m.FixingProblemsSuchAsRecoveringFromPowerFailures
November 04, 2010, at 12:55 PM by Jim Lovell -
Changed lines 281-284 from:
  • Error: v1 frequency does not check with requested value (and you have phase on vc1)

check=*,-v1

to:
  • Error: v1 frequency does not check with requested value (and you have phase on vc1),
    check=*,-v1
November 04, 2010, at 12:54 PM by Jim Lovell -
Added lines 281-284:
  • Error: v1 frequency does not check with requested value (and you have phase on vc1)

check=*,-v1

October 18, 2010, at 12:32 AM by 131.217.6.7 -
Changed lines 24-28 from:

Logs are typically less than 2 MB in size. Make sure Mark5A software is running on mkv. If not then the command on

to:

Logs are typically less than 2 MB in size. Make sure Mark5A software is running on mkv by typing

ps auxww | grep -i mark

and look for Mark5A -m0. If not then the command on

October 18, 2010, at 12:26 AM by 131.217.6.8 -
Changed lines 22-24 from:

df -k

Make sure Mark5A software is running on mkv. If not then the command on

to:

df -k /usr2/log

Logs are typically less than 2 MB in size. Make sure Mark5A software is running on mkv. If not then the command on

October 13, 2010, at 12:26 AM by JMc -
Changed line 9 from:
  • These instructions assume the .skd and .prc files are in place on Hobart.
to:
  • These instructions assume the .skd and .prc files are in place on Hobart. If not, you will need to run drudg. See MtPleasant26.DrudgIVS
October 04, 2010, at 01:27 PM by 131.217.6.9 -
Changed lines 263-264 from:
  • To repair some kinds of time discrepancies between MK 5 and hobart,
to:
  • To repair some kinds of time discrepancies between MK 5 and hobart, (e.g clkoff reports !+0.5s, and monitor also reports time as a few seconds off)
August 19, 2010, at 01:58 PM by JMc -
Changed lines 4-6 from:
to:
August 19, 2010, at 01:58 PM by JMc -
Added line 3:

First see…

Added lines 5-6:
August 19, 2010, at 01:38 PM by JMc -
Changed lines 2-3 from:
to:
July 31, 2009, at 02:27 AM by 131.217.6.8 -
July 24, 2009, at 12:23 AM by 202.168.118.145 -
Changed lines 244-245 from:
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window,
to:
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, and rxmon checks out ok, enter in fs operator window,
Added lines 248-252:
  • For constant annoying errors that read “Integrator total power overflow on if2″ (or something similar), and you’re sure the power levels on the vco’s and the total power on if2 and if3 are ok, enter in fs operator window,
    check=*,-ifd
September 04, 2008, at 12:33 AM by 131.217.60.165 -
September 04, 2008, at 12:32 AM by 131.217.60.165 -
Changed lines 271-273 from:
to:
September 04, 2008, at 12:30 AM by 131.217.60.165 -
Changed line 271 from:
to:
September 02, 2008, at 01:13 PM by Warren -
Changed lines 25-26 from:

Check that rs.tcl is not running as FS will give GPIB errors otherwise.

to:

Check that rs.tcl is not running as FS will give GPIB errors otherwise.(rs.tcl no longer in use??)

September 02, 2008, at 01:11 PM by Warren -
Changed lines 11-13 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using, on hobart,
    oscillator_control
    for explanation of usage, type,\\
to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using the graphic interface on hobart,
    oscillator_control_gui.pl
    or use the command line version, and for explanation of usage, type,\\
September 02, 2008, at 12:55 PM by 131.217.6.6 -
Changed lines 14-15 from:

oscillator_control - - help

to:

oscillator_control - - help

September 02, 2008, at 12:54 PM by 131.217.6.6 -
Changed lines 11-14 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using
    oscillator_control on hobart. See,
    oscillator_control - - help
    for explanation of usage.
to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using, on hobart,
    oscillator_control
    for explanation of usage, type,
    oscillator_control - - help
September 02, 2008, at 12:53 PM by 131.217.6.6 -
Changed lines 11-13 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using

oscillator_control on hobart. See, oscillator_control - - help

to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using
    oscillator_control on hobart. See,
    oscillator_control - - help\\
September 02, 2008, at 12:52 PM by 131.217.6.8 -
Changed lines 11-14 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using oscillator_control on hobart. See oscillator_control - - help for explanation of usage.
to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using

oscillator_control on hobart. See, oscillator_control - - help for explanation of usage.

September 02, 2008, at 12:52 PM by 131.217.6.8 -
Changed line 11 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using oscillator_control on hobart. See oscillator_control - - help for explanation of usage.
to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using oscillator_control on hobart. See oscillator_control - - help for explanation of usage.
September 02, 2008, at 12:51 PM by 131.217.6.8 -
Changed line 11 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using oscillator_control on hobart. See oscillator_control —help for explanation of usage.
to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using oscillator_control on hobart. See oscillator_control - - help for explanation of usage.
September 02, 2008, at 12:51 PM by 131.217.6.8 -
Changed line 11 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using rs.tcl on hobart.
to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using oscillator_control on hobart. See oscillator_control —help for explanation of usage.
August 29, 2008, at 06:32 PM by 131.217.6.7 -
Changed lines 196-197 from:

cable

to:

cablen

Changed lines 202-203 from:

cablelong

to:

cablel

August 29, 2008, at 09:49 AM by 131.217.6.8 -
Changed lines 252-253 from:

sy=run setcl offset

to:
 sy=run setcl offset
August 29, 2008, at 09:47 AM by 131.217.6.8 -
Changed lines 252-253 from:

sy=run setcl offset

to:

sy=run setcl offset

August 29, 2008, at 09:47 AM by 131.217.6.6 -
Added lines 250-253:
  • To repair some kinds of time discrepancies between MK 5 and hobart,

sy=run setcl offset

June 16, 2008, at 05:01 PM by Warren -
Changed line 47 from:
  • Check that cable works. cable \\
to:
  • Check that cable works. cablen \\
Changed line 68 from:
  • Check the cable measurement system. cable
to:
  • Check the cable measurement system. cablen
Changed line 70 from:
  • Check the cable measurement system with the longer cable. cablelong
to:
  • Check the cable measurement system with the longer cable. cablel
Changed lines 90-91 from:

Periodically check all the items on the checklist each hour, and complete the check list once ever four hours.

to:

Periodically check all the items on the checklist each hour, and complete the check list once every four hours.

June 16, 2008, at 12:36 PM by 131.217.6.8 -
Changed lines 236-237 from:
  • For red alarm light on IF3 on MKIV, enter in fs operator window,
to:
  • For red alarm light on IF3 on MKIV, enter in the field system (fs) operator window on hobart,
June 16, 2008, at 12:32 PM by 131.217.6.6 -
Changed lines 250-251 from:
  • For MK IV red alarm light errors, enter in fs operator window,
to:
  • For MKIV general red alarm light errors, enter in fs operator window,
June 16, 2008, at 12:29 PM by 131.217.6.9 -
Changed lines 248-249 from:
 to re-establish communication between fs to antenna drive pc.
to:
 to re-establish communication between fs and antenna drive pc.
June 16, 2008, at 12:28 PM by 131.217.6.9 -
Added line 249:
June 16, 2008, at 12:28 PM by 131.217.6.9 -
Changed lines 246-248 from:

source=disable

to re-establish communication between fs to antenna drive pc.

to:
 source=disable 

 to re-establish communication between fs to antenna drive pc.
Changed lines 251-254 from:

valarm

( see; Setting up IVS Experiments).

to:
 valarm

 ( see; Setting up IVS Experiments).
Changed lines 257-260 from:

vc15=200,2

(see; Setting up IVS Experiments )

to:
 vc15=200,2 

 (see; Setting up IVS Experiments )
June 16, 2008, at 12:27 PM by 131.217.6.9 -
Changed lines 242-243 from:

check=*,-rx

to:
 check=*,-rx
Added line 247:
Added line 252:
Added line 254:
Added line 258:
June 16, 2008, at 12:26 PM by 131.217.6.9 -
Deleted line 242:
Changed lines 245-246 from:
 source=disable 
to:

source=disable

Changed lines 249-251 from:
 valarm

 ( see; Setting up IVS Experiments).
to:

valarm ( see; Setting up IVS Experiments).

Changed lines 253-254 from:
 vc15=200,2 
to:

vc15=200,2

June 16, 2008, at 12:25 PM by 131.217.6.9 -
Changed lines 236-241 from:
  • For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx
  • If the drive pc has been restarted and schedule is still running on Field System use source=disable to re-establish communication between fs to antenna drive pc.
  • For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )
to:
  • For red alarm light on IF3 on MKIV, enter in fs operator window,
    if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window,

check=*,-rx

  • If the drive pc has been restarted and schedule is still running on Field System use,
    source=disable

to re-establish communication between fs to antenna drive pc.

  • For MK IV red alarm light errors, enter in fs operator window,
    valarm
    ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window,
    vc15=200,2

(see; Setting up IVS Experiments )

June 16, 2008, at 12:24 PM by 131.217.6.8 -
Changed lines 236-241 from:
  • For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx
  • If the drive pc has been restarted and schedule is still running on Field System use source=disable to re-establish communication between fs to antenna drive pc.
  • For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )
to:
  • For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx
  • If the drive pc has been restarted and schedule is still running on Field System use source=disable to re-establish communication between fs to antenna drive pc.
  • For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )
June 16, 2008, at 12:22 PM by 131.217.6.8 -
Changed lines 236-240 from:
  • For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx
  • For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )
to:
  • For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx
  • If the drive pc has been restarted and schedule is still running on Field System use source=disable to re-establish communication between fs to antenna drive pc.
  • For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )
June 05, 2008, at 06:45 AM by 131.217.6.8 -
Changed lines 236-240 from:

For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments). To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )

to:
  • For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm
  • For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx
  • For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments).
  • To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )
June 05, 2008, at 06:44 AM by 131.217.6.8 -
June 05, 2008, at 06:43 AM by 131.217.6.8 -
Added lines 234-236:

Some tricks.

For red alarm light on IF3 on MKIV, enter in fs operator window, if3=alarm

Changed lines 238-240 from:
to:

For MK IV red alarm light errors, enter in fs operator window, valarm ( see; Setting up IVS Experiments). To keep MKIV happy enter in fs operator window, vc15=200,2 (see; Setting up IVS Experiments )

June 04, 2008, at 09:23 PM by 131.217.6.8 -
Changed lines 234-235 from:

For spurious errors that read “70K stage hotter than 85K”, enter in fs operator window, check=*,-rx

to:

For spurious errors that read “The Receiver 70K stage hotter than 85K”, enter in fs operator window, check=*,-rx

May 28, 2008, at 10:07 PM by warren -
Added lines 234-235:

For spurious errors that read “70K stage hotter than 85K”, enter in fs operator window, check=*,-rx

May 20, 2008, at 12:52 AM by JMc -
Changed lines 234-235 from:
to:
May 20, 2008, at 12:52 AM by JMc -
Added lines 234-235:
December 14, 2007, at 04:54 AM by 131.217.6.9 -
Changed lines 232-234 from:

If you encounter a problem which you are unable to solve please contact someone for assistance.

to:

If you encounter a problem which you are unable to solve please contact someone for assistance.

Selene Observations and Setup

July 19, 2007, at 07:28 AM by Brett Reid -
Changed lines 27-28 from:

in the PCFS log window prior to the next step Start Field System on hobart watching for errors. fs

to:

in the PCFS log window prior to the next step, type fs to start Field System on Hobart. Watch for errors.

July 09, 2007, at 02:09 PM by JMc -
Changed line 54 from:
  • Run disk_pos to cherck the disk module is empty\\
to:
  • Run disk_pos to check the disk module is empty\\
July 09, 2007, at 02:09 PM by JMc -
Changed lines 53-54 from:
  • Check that the mark 5 has a blank module. disk_pos \\
to:
  • Check that the mark 5 has a blank module big enough for the experiment. Compare the Drudg summary of the schedule with the label on the front of the disk module.
  • Run disk_pos to cherck the disk module is empty\\
July 04, 2007, at 10:33 AM by Brett Reid and Cliff Senkbeil -
Changed lines 85-87 from:

Maintaining IVS Experiments

to:

Monitoring IVS Experiments

July 04, 2007, at 10:33 AM by Brett Reid and Cliff Senkbeil -
Deleted lines 0-1:

Setting up, monitoring and terminating IVS Experiments

July 04, 2007, at 10:32 AM by Brett Reid and Cliff Senkbeil -
Changed lines 1-4 from:

Setting up, monitoring and terminating IVS Experiments

1. Setting up IVS Experiments

to:

Setting up, monitoring and terminating IVS Experiments

Setting up IVS Experiments

Changed lines 87-89 from:

2. Maintaining IVS Experiments

to:

Maintaining IVS Experiments

Changed lines 94-95 from:

Checking Clocks:

to:

Checking Clocks

Changed lines 113-114 from:

Checking the VC power levels:

to:

Checking the VC power levels

Changed lines 119-120 from:

Checking the VC phase stability:

to:

Checking the VC phase stability

Changed lines 123-124 from:

Disk position:

to:

Disk position

Changed lines 134-135 from:

Checking the system temperature:

to:

Checking the system temperature

Changed lines 139-140 from:

Checking the logging procedure:

to:

Checking the logging procedure

Changed lines 154-155 from:

The wth command outputs a list of numbers, Temperature, pressure and humidity.

to:

The wth command outputs a list of numbers, Temperature, pressure and humidity.

Changed lines 159-161 from:

Logging the weather:

to:

Logging the weather

Changed lines 174-175 from:

Checking Stalm:

to:

Checking Stalm

Changed lines 179-180 from:

Checking the Field System Monitor:

to:

Checking the Field System Monitor

Changed lines 188-190 from:

3. End of schedule

to:

End of schedule

Changed lines 194-195 from:

Check the cable measurement system.

to:

Check the cable measurement system.

Changed lines 229-230 from:

4. Alarms or other errors.

to:

Alarms or other errors.

July 04, 2007, at 10:28 AM by Brett Reid and Cliff Senkbeil -
Changed line 13 from:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using rs.tcl on hobart.
to:
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using rs.tcl on hobart.
July 04, 2007, at 10:28 AM by Brett Reid and Cliff Senkbeil -
Changed lines 7-17 from:

These instructions assume the .skd and .prc files are in place on Hobart.
Move the focus position to −256, +248, +18 (x,y,z) (bottom of rack 2)
Ensure 2020 LO Kill switch is off. (bottom of rack 2)
Ensure that cables A21 and A22 are each terminated in 50 ohms. Top of rack 5
Ensure phasecal cable is in. (Back of rack 10)
Ensure alarm cable is connected. (Back of rack 10)
Ensure the previous receiver to be used is not using Agilent LO
frequency that interferes with S or X band signal, if so change the frequency/level using rs.tcl on hobart.
Check there is space on Hobart for the new log using the command

to:
  • These instructions assume the .skd and .prc files are in place on Hobart.
  • Move the focus position to −256, +248, +18 (x,y,z) (bottom of rack 2)
  • Ensure 2020 LO Kill switch is off. (bottom of rack 2)
  • Ensure that cables A21 and A22 are each terminated in 50 ohms. Top of rack 5
  • Ensure phasecal cable is in. (Back of rack 10)
  • Ensure alarm cable is connected. (Back of rack 10)
  • Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using rs.tcl on hobart.
  • Check there is space on Hobart for the new log using the command
July 04, 2007, at 10:26 AM by Brett Reid and Cliff Senkbeil -
Changed line 52 from:
  • Check that cable works. cable
to:
  • Check that cable works. cable \\
July 04, 2007, at 10:25 AM by Brett Reid and Cliff Senkbeil -
Changed lines 42-46 from:
  • Check all the VCs are happy, ie no red lights and no nasty messages

appearing in pcfs log window. Command “VC15=200,2″ will load some values to keep VC15 happy which is not normally used. Command “valarm” will turn off any remaining alarm lights on the VCs.

to:
  • Check all the VCs are happy, ie no red lights and no nasty messages appearing in pcfs log window. Command “VC15=200,2″ will load some values to keep VC15 happy which is not normally used. Command “valarm” will turn off any remaining alarm lights on the VCs.
Changed line 52 from:
  • Check that cable works. cable \\
to:
  • Check that cable works. cable
July 04, 2007, at 10:24 AM by Brett Reid and Cliff Senkbeil -
Changed lines 83-88 from:
  • Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these

utilities are accessible from Field system menu when you click on the background screen of Hobart.

  • Start FS monitor on Smerd by clicking on the FS Monitor menu button and

logging in to hobart as oper in the green window.

to:
  • Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these utilities are accessible from Field system menu when you click on the background screen of Hobart.
  • Start FS monitor on Smerd by clicking on the FS Monitor menu button and logging in to hobart as oper in the green window.
July 04, 2007, at 10:23 AM by Brett Reid and Cliff Senkbeil -
Changed line 55 from:
  • Check that cable works. cable\\
to:
  • Check that cable works. cable \\
Changed line 60 from:
  • Check that the mark 5 has a blank module. disk_pos
to:
  • Check that the mark 5 has a blank module. disk_pos \\
July 04, 2007, at 10:22 AM by Brett Reid and Cliff Senkbeil -
Changed line 55 from:
  • Check that cable works. cable
to:
  • Check that cable works. cable\\
Changed line 57 from:
  • Check that the formatter PPS coax (instead of hmaser) goes to HP53131A
to:
  • Check that the formatter PPS coax (instead of hmaser) goes to HP53131A\\
July 04, 2007, at 10:21 AM by Brett Reid and Cliff Senkbeil -
Changed lines 51-52 from:
  • Set the cal to be controlled by PCFS.

smerd:observer:>calu -m pcfs\\

to:
  • Set the cal to be controlled by PCFS.
    smerd:observer:>calu -m pcfs
July 04, 2007, at 10:20 AM by Brett Reid and Cliff Senkbeil -
Changed lines 47-51 from:
  • Check that if3 is happy with no red lights. You may need if3=alarm
    * Check the formatter error light is off. You may need to do “form”
    * Check that power reading for each VC USB is between 0.1 and 1.0 volt
    * Check that phasecal is visible for each usb out on all VCs
    * Set the cal to be controlled by PCFS. \\
to:
  • Check that if3 is happy with no red lights. You may need if3=alarm
  • Check the formatter error light is off. You may need to do “form”
  • Check that power reading for each VC USB is between 0.1 and 1.0 volt
  • Check that phasecal is visible for each usb out on all VCs
  • Set the cal to be controlled by PCFS.
Changed lines 53-55 from:
  • Check that caltsys works. Caltsys results between 50 and 70k
    * Check that weather works. wth
    * Check that cable works. cable \\
to:
  • Check that caltsys works. Caltsys results between 50 and 70k
  • Check that weather works. wth
  • Check that cable works. cable
Changed line 58 from:

counter channel 1.\\

to:

counter channel 1.

Changed lines 60-73 from:
  • Check that the mark 5 has a blank module. disk_pos
    Result should be 0/0 otherwise the disk module contains data.
    * Record some data. disk_record=on
    * Observe green disk activity lights on module
    * Stop recording. disk_record=off
    * Check the recording. scan_check
    * Observe the time and details in the PCFS log window for the test recording.
    * Check the record pointer. disk_pos
    * Erase the module. mk5=protect=off; mk5=reset=erase
    * Check the record pointer. disk_pos Should now be zero.
    * Start the schedule. schedule=r1186ho,#1
    * Watch PCFS log for errors.
    * Check the Mark5 is ready with a module loaded.
    * Continue the schedule with the command. mk5relink\\
to:
  • Check that the mark 5 has a blank module. disk_pos

Result should be 0/0 otherwise the disk module contains data.

  • Record some data. disk_record=on
  • Observe green disk activity lights on module
  • Stop recording. disk_record=off
  • Check the recording. scan_check
  • Observe the time and details in the PCFS log window for the test recording.
  • Check the record pointer. disk_pos
  • Erase the module. mk5=protect=off; mk5=reset=erase
  • Check the record pointer. disk_pos Should now be zero.
  • Start the schedule. schedule=r1186ho,#1
  • Watch PCFS log for errors.
  • Check the Mark5 is ready with a module loaded.
  • Continue the schedule with the command. mk5relink
Changed lines 75-82 from:
  • Check the cable measurement system. cable
    * Add in the test length of cable.
    * Check the cable measurement system with the longer cable. cablelong
    * Subtract the 2 readings. cablediff
    * Write the difference in the written log sheet. It should be about 760 usec.
    * Remove the extra cable length!
    * Again check the antenna is on the source. onsource.
    * Check everything on the experiment check list.\\
to:
  • Check the cable measurement system. cable
  • Add in the test length of cable.
  • Check the cable measurement system with the longer cable. cablelong
  • Subtract the 2 readings. cablediff
  • Write the difference in the written log sheet. It should be about 760 usec.
  • Remove the extra cable length!
  • Again check the antenna is on the source. onsource.
  • Check everything on the experiment check list.
Changed line 85 from:

background screen of Hobart.\\

to:

background screen of Hobart.

Changed lines 90-92 from:

first scan or so.
Send the start message. Use the template in smerd:/vlbobs/ngs/start\\

to:

first scan or so.

Send the start message. Use the template in smerd:/vlbobs/ngs/start

July 04, 2007, at 10:17 AM by Brett Reid and Cliff Senkbeil -
Changed lines 42-44 from:

Check all the VCs are happy, ie no red lights and no nasty messages appearring in pcfs log window. Command “VC15=200,2″ will load some values to keep VC15 happy which is not normally used. Command “valarm”

to:
  • Check all the VCs are happy, ie no red lights and no nasty messages

appearing in pcfs log window. Command “VC15=200,2″ will load some values to keep VC15 happy which is not normally used. Command “valarm

Changed lines 47-51 from:

Check that if3 is happy with no red lights. You may need if3=alarm
Check the formatter error light is off. You may need to do “form”
Check that power reading for each VC USB is between 0.1 and 1.0 volt
Check that phasecal is visible for each usb out on all VCs
Set the cal to be controlled by PCFS. \\

to:
  • Check that if3 is happy with no red lights. You may need if3=alarm
    * Check the formatter error light is off. You may need to do “form”
    * Check that power reading for each VC USB is between 0.1 and 1.0 volt
    * Check that phasecal is visible for each usb out on all VCs
    * Set the cal to be controlled by PCFS. \\
Changed lines 53-55 from:

Check that caltsys works. Caltsys results between 50 and 70k
Check that weather works. wth
Check that cable works. cable \\

to:
  • Check that caltsys works. Caltsys results between 50 and 70k
    * Check that weather works. wth
    * Check that cable works. cable \\
Changed line 57 from:

Check that the formatter PPS coax (instead of hmaser) goes to HP53131A

to:
  • Check that the formatter PPS coax (instead of hmaser) goes to HP53131A
Changed lines 59-60 from:

Check that fmout-gps works. clkoff Check that the mark 5 has a blank module. disk_pos\\

to:
  • Check that fmout-gps works. clkoff
  • Check that the mark 5 has a blank module. disk_pos\\
Changed lines 62-83 from:

Record some data. disk_record=on
Observe green disk activity lights on module
Stop recording. disk_record=off
Check the recording. scan_check
Observe the time and details in the PCFS log window for the test recording.
Check the record pointer. disk_pos
Erase the module. mk5=protect=off; mk5=reset=erase
Check the record pointer. disk_pos Should now be zero.
Start the schedule. schedule=r1186ho,#1
Watch PCFS log for errors.
Check the Mark5 is ready with a module loaded.
Continue the schedule with the command. mk5relink
Check the antenna is on source. onsource Check the cable measurement system. cable
Add in the test length of cable.
Check the cable measurement system with the longer cable. cablelong
Subtract the 2 readings. cablediff
Write the difference in the written log sheet. It should be about 760 usec.
Remove the extra cable length!
Again check the antenna is on the source. onsource.
Check everything on the experiment check list.
Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these

to:
  • Record some data. disk_record=on
    * Observe green disk activity lights on module
    * Stop recording. disk_record=off
    * Check the recording. scan_check
    * Observe the time and details in the PCFS log window for the test recording.
    * Check the record pointer. disk_pos
    * Erase the module. mk5=protect=off; mk5=reset=erase
    * Check the record pointer. disk_pos Should now be zero.
    * Start the schedule. schedule=r1186ho,#1
    * Watch PCFS log for errors.
    * Check the Mark5 is ready with a module loaded.
    * Continue the schedule with the command. mk5relink
    * Check the antenna is on source. onsource
  • Check the cable measurement system. cable
    * Add in the test length of cable.
    * Check the cable measurement system with the longer cable. cablelong
    * Subtract the 2 readings. cablediff
    * Write the difference in the written log sheet. It should be about 760 usec.
    * Remove the extra cable length!
    * Again check the antenna is on the source. onsource.
    * Check everything on the experiment check list.
    * Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these
Changed lines 86-87 from:

Start FS monitor on Smerd by clicking on the FS Monitor menu button and logging in to hobart as oper in the green window.\\

to:
  • Start FS monitor on Smerd by clicking on the FS Monitor menu button and

logging in to hobart as oper in the green window.

Added line 91:
Changed lines 193-195 from:

password: (standard password)

to:

password:

July 04, 2007, at 10:11 AM by Brett Reid and Cliff Senkbeil -
Deleted lines 59-60:
Changed lines 75-76 from:
to:

Check the cable measurement system. cable
Add in the test length of cable.
Check the cable measurement system with the longer cable. cablelong
Subtract the 2 readings. cablediff
Write the difference in the written log sheet. It should be about 760 usec.
Remove the extra cable length!
Again check the antenna is on the source. onsource.
Check everything on the experiment check list.
Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these utilities are accessible from Field system menu when you click on the background screen of Hobart.
Start FS monitor on Smerd by clicking on the FS Monitor menu button and logging in to hobart as oper in the green window.
Once the schedule starts, watch the log and everything closely for the first scan or so.
Send the start message. Use the template in smerd:/vlbobs/ngs/start
You can use observer@ares account and pine email program if you wish.

Changed lines 152-158 from:

wth

clkoff

cable

to:

wth
clkoff
cable

Changed lines 165-167 from:

Logging the weather:

to:

Logging the weather:

Changed lines 171-173 from:
to:
Changed lines 180-181 from:

Checking Stalm:

to:

Checking Stalm:

Changed lines 185-186 from:

Checking the Field System Monitor:

to:

Checking the Field System Monitor:

Changed lines 190-200 from:

Username: oper

password: (standard password)

Section 3.

End of schedule

to:

Username: oper
password: (standard password)

3. End of schedule

Changed lines 200-202 from:

Check the cable measurement system.

to:

Check the cable measurement system.

Changed lines 204-210 from:

cable

Add in the test length of cable.

to:

cable

Add in the test length of cable.\\

Changed lines 210-212 from:

cablelong

to:

cablelong

Changed lines 215-217 from:

cablediff

to:

cablediff

Changed lines 225-227 from:

terminate

to:

terminate

Changed lines 233-237 from:

Section 4.

Alarms or other errors.

to:

4. Alarms or other errors.

Changed lines 240-285 from:

If you encounter a problem which you are unable to solve please contact someone for assistance.

You can contact the following people for this experiment:

Check the cable measurement system. cable Add in the test length of cable. Check the cable measurement system with the longer cable. cablelong Subtract the 2 readings. cablediff Write the difference in the written log sheet. It should be about 760 usec. Remove the extra cable length! Again check the antenna is on the source. onsource. Check everything on the experiment check list. Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these utilities are accessible from Field system menu when you click on the background screen of Hobart. Start FS monitor on Smerd by clicking on the FS Monitor menu button and logging in to hobart as oper in the green window. Once the schedule starts, watch the log and everything closely for the first scan or so. Send the start message. Use the template in smerd:/vlbobs/ngs/start You can use observer@ares account and pine email program if you wish.

to:

If you encounter a problem which you are unable to solve please contact someone for assistance.

July 04, 2007, at 08:15 AM by Brett Reid and Cliff Senkbeil -
Changed lines 3-4 from:

Setting up IVS Experiments

to:

1. Setting up IVS Experiments

Changed line 15 from:

frequency/level using rs.tcl on hobart.

to:

frequency/level using rs.tcl on hobart.\\

Changed lines 77-79 from:

Maintaining IVS Experiments

to:

2. Maintaining IVS Experiments

Deleted line 83:
Changed lines 86-88 from:

Checking Clocks:

to:

Checking Clocks:

Changed lines 90-97 from:

Drive PC,

Formatter,

Decoder and

AT Maser

to:
  • Drive PC,
  • Formatter,
  • Decoder and
  • the AT Maser
Changed lines 98-103 from:

Check that the clkoff procedure is being correctly logged in the field system, this can be done by looking at the most recent output in the Field System Log window, or by issuing the command

clkoff

to:

Check that the clkoff procedure is being correctly logged in the field system, this can be done by looking at the most recent output in the Field System Log window, or by issuing the command

clkoff

Changed lines 105-106 from:

Checking the VC power levels:

to:

Checking the VC power levels:

Deleted line 108:
Changed lines 111-113 from:

Checking the VC phase stability:

to:

Checking the VC phase stability:

Changed lines 115-118 from:

Disk position:

to:

Disk position:

Changed lines 120-122 from:

disk_pos

to:

disk_pos

Changed lines 126-127 from:

Checking the system temperature:

to:

Checking the system temperature:

July 04, 2007, at 07:55 AM by Brett Reid and Cliff Senkbeil -
Changed lines 7-13 from:

These instructions assume the .skd and .prc files are in place on Hobart. Move the focus position to −256, +248, +18 (x,y,z) (bottom of rack 2) Ensure 2020 LO Kill switch is off. (bottom of rack 2) Ensure that cables A21 and A22 are each terminated in 50 ohms. Top of rack 5 Ensure phasecal cable is in. (Back of rack 10) Ensure alarm cable is connected. (Back of rack 10) Ensure the previous receiver to be used is not using Agilent LO

to:

These instructions assume the .skd and .prc files are in place on Hobart.
Move the focus position to −256, +248, +18 (x,y,z) (bottom of rack 2)
Ensure 2020 LO Kill switch is off. (bottom of rack 2)
Ensure that cables A21 and A22 are each terminated in 50 ohms. Top of rack 5
Ensure phasecal cable is in. (Back of rack 10)
Ensure alarm cable is connected. (Back of rack 10)
Ensure the previous receiver to be used is not using Agilent LO\\

Changed lines 27-31 from:

If the previous VLBI experiment was not mark5 (ie S2) then run “chooser mk5″ in the PCFS log window prior to the next step Start Field System on hobart watching for errors. fs Load the experiment procedure library. eg proc=rdv58ho Use the experiment name with “ho” on the end.

to:

If the previous VLBI experiment was not mark5 (ie S2) then run

chooser mk5

in the PCFS log window prior to the next step Start Field System on hobart watching for errors. fs Load the experiment procedure library.
eg
proc=rdv58ho

Use the experiment name with “ho” on the end.

Added line 41:
Changed lines 46-53 from:

Check that if3 is happy with no red lights. You may need if3=alarm Check the formatter error light is off. You may need to do “form” Check that power reading for each VC USB is between 0.1 and 1.0 volt Check that phasecal is visible for each usb out on all VCs Set the cal to be controlled by PCFS. smerd:observer:>calu -m pcfs Check that caltsys works. Caltsys results between 50 and 70k Check that weather works. wth Check that cable works. cable Result is 15XXX

to:

Check that if3 is happy with no red lights. You may need if3=alarm
Check the formatter error light is off. You may need to do “form”
Check that power reading for each VC USB is between 0.1 and 1.0 volt
Check that phasecal is visible for each usb out on all VCs
Set the cal to be controlled by PCFS.
smerd:observer:>calu -m pcfs
Check that caltsys works. Caltsys results between 50 and 70k
Check that weather works. wth
Check that cable works. cable
Result is 15XXX

Changed lines 58-79 from:

counter channel 1. Check that fmout-gps works. clkoff

Check that the mark 5 has a blank module. disk_pos Result should be 0/0 otherwise the disk module contains data. Record some data. disk_record=on Observe green disk activity lights on module Stop recording. disk_record=off Check the recording. scan_check Observe the time and details in the PCFS log window for the test recording. Check the record pointer. disk_pos Erase the module. mk5=protect=off; mk5=reset=erase Check the record pointer. disk_pos Should now be zero. Start the schedule. schedule=r1186ho,#1 Watch PCFS log for errors. Check the Mark5 is ready with a module loaded. Continue the schedule with the command. mk5relink Check the antenna is on source. onsource

Check the cable measurement system. cable

to:
Changed lines 211-212 from:

Check the cable measurement system with the longer cable. cablelong Subtract the 2 readings. cablediff

to:

Check the cable measurement system with the longer cable by issuing the command

cablelong

Subtract the 2 readings by issuing the command

cablediff

Added lines 227-278:

Once this has been done you can then terminate the field system by typing:

terminate

You then need to close the Field system monitor running on smerd by moving you mouse over the greem window and pressing Ctrl+C. (otherwise the alarm will sound)

Now park the antenna using vdesk if the antennas is not already in the park position.

Section 4.

Alarms or other errors.

With time you’ll be able to fix most problems yourself. The telescope manager will let you know if there are certain problem to lookout for during a given experiment, and may suggest techniques to overcome those problems.

If you encounter a problem which you are unable to solve please contact someone for assistance.

You can contact the following people for this experiment:

Check the cable measurement system. cable Add in the test length of cable. Check the cable measurement system with the longer cable. cablelong Subtract the 2 readings. cablediff Write the difference in the written log sheet. It should be about 760 usec. Remove the extra cable length!

July 04, 2007, at 07:49 AM by Brett Reid and Cliff Senkbeil -
Added lines 1-89:

Setting up, monitoring and terminating IVS Experiments

Setting up IVS Experiments

Because there is a need to run the dish for research other than IVS for as many hours as possible even after normal work hours, it may be neccesary for you to set up an IVS experiment prior to observing. The purpose of these notes is to tell you how to do it. Please let us know if anything is missing from these notes.

These instructions assume the .skd and .prc files are in place on Hobart. Move the focus position to −256, +248, +18 (x,y,z) (bottom of rack 2) Ensure 2020 LO Kill switch is off. (bottom of rack 2) Ensure that cables A21 and A22 are each terminated in 50 ohms. Top of rack 5 Ensure phasecal cable is in. (Back of rack 10) Ensure alarm cable is connected. (Back of rack 10) Ensure the previous receiver to be used is not using Agilent LO frequency that interferes with S or X band signal, if so change the frequency/level using rs.tcl on hobart. Check there is space on Hobart for the new log using the command

df -k

Make sure Mark5A software is running on mkv. If not then the command on the Mark5 recorder is

Mark5A -m0 &

Check that rs.tcl is not running as FS will give GPIB errors otherwise.

If the previous VLBI experiment was not mark5 (ie S2) then run “chooser mk5″ in the PCFS log window prior to the next step Start Field System on hobart watching for errors. fs Load the experiment procedure library. eg proc=rdv58ho Use the experiment name with “ho” on the end. Run the setup. The command for an R1 experiment is “setupsx”. Look in the experiment procedure library printout to find the correct setup procedure name. Check all the VCs are happy, ie no red lights and no nasty messages appearring in pcfs log window. Command “VC15=200,2″ will load some values to keep VC15 happy which is not normally used. Command “valarm” will turn off any remaining alarm lights on the VCs. Check that if3 is happy with no red lights. You may need if3=alarm Check the formatter error light is off. You may need to do “form” Check that power reading for each VC USB is between 0.1 and 1.0 volt Check that phasecal is visible for each usb out on all VCs Set the cal to be controlled by PCFS. smerd:observer:>calu -m pcfs Check that caltsys works. Caltsys results between 50 and 70k Check that weather works. wth Check that cable works. cable Result is 15XXX Check that the formatter PPS coax (instead of hmaser) goes to HP53131A counter channel 1. Check that fmout-gps works. clkoff

Check that the mark 5 has a blank module. disk_pos Result should be 0/0 otherwise the disk module contains data. Record some data. disk_record=on Observe green disk activity lights on module Stop recording. disk_record=off Check the recording. scan_check Observe the time and details in the PCFS log window for the test recording. Check the record pointer. disk_pos Erase the module. mk5=protect=off; mk5=reset=erase Check the record pointer. disk_pos Should now be zero. Start the schedule. schedule=r1186ho,#1 Watch PCFS log for errors. Check the Mark5 is ready with a module loaded. Continue the schedule with the command. mk5relink Check the antenna is on source. onsource

Check the cable measurement system. cable Add in the test length of cable. Check the cable measurement system with the longer cable. cablelong Subtract the 2 readings. cablediff Write the difference in the written log sheet. It should be about 760 usec. Remove the extra cable length! Again check the antenna is on the source. onsource. Check everything on the experiment check list. Start Stalm, Status monitor, monitor Tsys and monitor Mark 5. All these utilities are accessible from Field system menu when you click on the background screen of Hobart. Start FS monitor on Smerd by clicking on the FS Monitor menu button and logging in to hobart as oper in the green window. Once the schedule starts, watch the log and everything closely for the first scan or so. Send the start message. Use the template in smerd:/vlbobs/ngs/start You can use observer@ares account and pine email program if you wish.

Edit - History - Print - Recent Changes - Search
Page last modified on March 01, 2011, at 01:11 AM