User Tools
hardware:dbbc.reprogram
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hardware:dbbc.reprogram [2010/11/22 04:25] Jim Lovell |
hardware:dbbc.reprogram [2016/09/16 16:38] (current) Jesse Swan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Reprogramming the DBBC ====== | ====== Reprogramming the DBBC ====== | ||
| Sometimes the DBBC needs reprogramming because channels have been dropped or spectra look strange. To do this, preferable in a gap between scans, follow the following steps: | Sometimes the DBBC needs reprogramming because channels have been dropped or spectra look strange. To do this, preferable in a gap between scans, follow the following steps: | ||
| - | - Open a VNC connection to the DBBC. At Hobart, connect to 131.217.63.248:0 <code>vncviewer -shared 131.217.63.248:0</code> | + | - Open a VNC connection to the DBBC. At Hobart, connect to 131.217.63.248:0 <code>Applications --> Auscope Hobar --> VNC -->dbbchb </code> |
| - | - You should see a console window named ''DBBC Control.exe''. At the ''Enter Command:'' prompt, type<code>Enter Command: reconfig</code> The DBBC will be reprogrammed, which takes about 2 minutes. | + | - You should see a window named ''DBBC2 Control DDC v104_2.exe''. Close it and then restart it from the desktop. When prompted to reconfigure press "y", it takes about 2 minutes. |
| - | - It is then necessary to make sure the DBBC is synchronised with the station PPS:<code>Enter Command: pps_sync</code> You should then see a row of LEDs on the DBBC flash in sync, once a second. | + | - It is then necessary to make sure the DBBC is synchronised with the station PPS. After some time, in eremotectrl type:<code>dbbc=pps_sync</code> You should then see a row of LEDs on the DBBC flash in sync, once a second. |
| - | - Lastly, the Mark5 time needs synchronising. To do this, open a terminal on pcfsya and type <code>fmset</code> In the interface, type ''S'' followed by ''y'', then press the **ESC** key. | + | - Lastly, the Mark5 time needs synchronising. To do this, open a terminal on pcfshb and type <code>fmset</code> In the interface, type ''S'' followed by ''y'', then press the **ESC** key. |
| - | - In the oprin window on pcfsya, type <code>mk5=dot?</code> and check that you see ''syncerr_eq_0'' and ''FHG_on'' (or ''FHG_off''). If you see something like ''syncerr_gt_3'' then ''fmset'' may need to be run again. | + | - In the oprin window on pcfshb, type <code>mk5=dot?</code> and check that you see ''syncerr_eq_0'' and ''FHG_on'' (or ''FHG_off''). If you see something like ''syncerr_gt_3'' then ''fmset'' may need to be run again. |
| + | - Also check that the maser-GPS and delay through the DBBC are the same (to within a microsec) with the ''maserdelay'' and ''clkoff'' commands which read the Agilent counters. | ||
| + | - If one or both counters are not responding to these commands, you will see an error message like this <code>ERROR sp -4 GPIB Device time-out on response c2</code> To fix this, try re-setting the counters. In the ''oprin'' window, type <code>counter</code> and try the ''clkoff'' and ''maserdelay'' commands again. | ||
/home/www/auscope/opswiki/data/attic/hardware/dbbc.reprogram.1290399904.txt.gz · Last modified: 2011/10/26 06:37 (external edit)
Page Tools
