User Tools

Site Tools


operations:documentation.dbbcsetupivs_v2

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.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
operations:documentation.dbbcsetupivs_v2 [2014/04/08 04:09]
Lucia McCallum
operations:documentation.dbbcsetupivs_v2 [2016/10/08 16:08] (current)
Jesse Swan
Line 1: Line 1:
-====== DBBC Setup for IVS at Katherine======+====== DBBC Setup for IVS======
 Open a VNC session to the DBBC you want to configure from the Applications menu on Ops2: Open a VNC session to the DBBC you want to configure from the Applications menu on Ops2:
  
 In ''​C:​\DBBC_CONF\''​ are several configuration files for different experiment types. The configurations used for IVS are: In ''​C:​\DBBC_CONF\''​ are several configuration files for different experiment types. The configurations used for IVS are:
  
-  * ''​dbbc_config_file_102_rapid.txt''​ for R1 and R4 geodesy +  * ''​dbbc_config_file_104_rapid.txt''​ for R1 and R4 geodesy 
-  * ''​dbbc_config_file_102_aust.txt''​ for AUSTRAL sessions +  * ''​dbbc_config_file_104_aust.txt''​ for AUSTRAL sessions 
-  * ''​dbbc_config_file_102_APSG_CRF.txt''​ for APSG, CRDS and CRF geodesy +  * ''​dbbc_config_file_104_APSG_CRF.txt''​ for APSG, CRDS and CRF geodesy 
-  * ''​dbbc_config_file_102_T2_OHIG.txt''​ for T2 and OHIG+  * ''​dbbc_config_file_104_T2_OHIG.txt''​ for T2 and OHIG
  
-The default configuration is kept in ''​dbbc_config_file_102.txt''​ and this will be loaded when the server software is started.+The default configuration is kept in ''​dbbc_config_file_104.txt''​ and this will be loaded when the server software is started.
 (If you want to change the default, //​**Copy**//​ (i.e. Do NOT rename) the appropriate file to ''​dbbc_config_file.txt''​) (If you want to change the default, //​**Copy**//​ (i.e. Do NOT rename) the appropriate file to ''​dbbc_config_file.txt''​)
  
Line 16: Line 16:
 Start ''​DBBC Control net.exe''​ which can be found on the Desktop. If you didn't accept the default config, load the file you want now with the LOAD command. e.g.: Start ''​DBBC Control net.exe''​ which can be found on the Desktop. If you didn't accept the default config, load the file you want now with the LOAD command. e.g.:
 <​code>​ <​code>​
-load=dbbc_config_file_102_rapid.txt+load=dbbc_config_file_104_rapid.txt
 </​code>​ </​code>​
 Then configure the DBBC with a Then configure the DBBC with a
 <​code>​ <​code>​
-reconf+dbbc=reconf
 </​code>​ </​code>​
- 
-Note: It's probably "​reconf"​ but needs checking. If not, try "​config"​ or "​reconfig"​. 
  
 Configurations will take about 2 minutes. ​ Configurations will take about 2 minutes. ​
Line 33: Line 31:
 </​code>​ </​code>​
  
-===== Setting the IFs - all stations ​=====+During observations,​ the log monitor will ring an alarm if the internal delay in the dbbc has changed. This is automatically tested every scan. To trigger the command yourself, use 
 +''​dbbc=pps_delay=1''​. 
 + 
 +===== Setting the IFs =====
  
  
 You now need to set up the IF system. The commands to do this depend on the IVS observation. You now need to set up the IF system. The commands to do this depend on the IVS observation.
  
-For R1, R4, AUSTRAL, CRF, CRDS and RDV experiments they should be:+For R1, R4, AUSTRAL, CRF, CRDS, AUG, AUA and RDV experiments they should be:
 <​code>​ <​code>​
-dbbcifa=1,agc,1 +ifa=1,agc,1 
-dbbcifb=4,agc,4 +ifb=4,agc,4 
-dbbcifc=2,agc,2 +ifc=2,agc,2 
-dbbcifd=2,agc,2+ifd=2,agc,2
 dbbcform=geo dbbcform=geo
 </​code>​ </​code>​
Line 49: Line 50:
  
  
-For APSG, OHIG and T2 experiments they should be:+For APSG, OHIG, AOV and T2 experiments they should be:
 <​code>​ <​code>​
-dbbcifa=1,agc,1 +ifa=1,agc,1 
-dbbcifb=4,agc,1 +ifb=4,agc,1 
-dbbcifc=2,agc,2 +ifc=2,agc,2 
-dbbcifd=2,agc,2+ifd=2,agc,2
 dbbcform=geo dbbcform=geo
 </​code>​ </​code>​
  
-The target values for the total power readings vary by station and CoMo. The targets are listed in the table below. The current ​power level (and target) can be checked by the command dbbcif[abcd]. If the levels ​are too high or low, then adjust the attenuation on the IF box.  +The target values for the total power readings vary by station and CoMo. The syntax for setting ​the IFs and power levels ​is:
- +
-| CoMo | Target power level | +
-| **Hb** | +
-| A | 40000 | +
-| B | 48000 | +
-| C | 32500 | +
-| D | 35000 | +
-| **Ke** | +
-| A | 38000 | +
-| B | 33000 | +
-| C | 36000 | +
-| D | 33000 | +
-| **Yg** | +
-| A | 25000 | +
-| B | 25000 | +
-| C | 35000 | +
-| D | 35000 |+
  
 +<​code>​
 +if[abcd]=[1,​2,​4],​agc,​[1,​2,​4],​[power level]
 +</​code>​
 +eg,
  
 +<​code>​
 +ifa=1,​agc,​1,​25000
 +ifb=4,​agc,​4,​25000
 +ifc=2,​agc,​2,​35000
 +ifd=2,​agc,​2,​35000
 +</​code>​
  
 +The target power levels are listed on the [[hardware:​dbbc.targetifpower|Recommended DBBC IF Power Levels]] page. The current power level (and target) can be checked by the command if[abcd]. If the levels are too high or low, then adjust the attenuation on the IF box. 
  
 +**Chris: I don't think the following has been an issue for some time. Candidate for removal?**
  
 There is a known issue where the target levels loaded by the DBBC through load=dbcc... are incorrect. For now, the workaround is to specify the target power levels in the ifdsx section of the proc file. There is a known issue where the target levels loaded by the DBBC through load=dbcc... are incorrect. For now, the workaround is to specify the target power levels in the ifdsx section of the proc file.
/home/www/auscope/opswiki/data/attic/operations/documentation.dbbcsetupivs_v2.1396930168.txt.gz · Last modified: 2014/04/08 04:09 by Lucia McCallum