Open a VNC session to the DBBC you want to configure from the Applications menu on Ops2:

If you can't connect to the DBBC VNC server, the DBBC may have died. In which case, follow these notes on Recovering from a DBBC Failure

In C:\DBBC_CONF\ are several configuration files for different experiment types. The default configuration is kept in dbbc_config_file_104.txt and this will be loaded when the server software is started.

Check to see if a program called DBBC2 Control DDC v104_2.exe is running. If it's not running, start it. There's a link to it from the desktop. (Don't have two instances running.)

dbbc=pps_sync

Lastly, make sure the DBBC Client software is NOT running on the DBBC. The Field System can't connect to the server if another client is running. Look for DBBC client.exe running in a terminal window. If you find it, exit it.

Now all DBBC commands can be issued from the field system software or eRemoteControl. Any native DBBC command can be sent via these interfaces with a dbbc= prefix (such as the pps_sync command above). Many commonly used DBBC commands have been set up in the Field System so that they look like old Mark4 rack commands to make compatibility between different hardware systems easier. For example, the bbcNN commands in the dbbcsx8 procedure and the ifX commands in the ifdsx procedure.

A full list of DBBC commands (requiring a dbbc= prefix if using eRemoteControl)) is given in the DBBC Command Set V2.3 document.

Target power levels for the CoMos are listed here

Just for reference, the configurations used for IVS are:

• dbbc_config_file_104_rapid.txt for R1 and R4 geodesy
• dbbc_config_file_104_aust.txt for AUSTRAL sessions
• dbbc_config_file_104_apsg_crf.txt for APSG, CRDS and CRF geodesy
• dbbc_config_file_104_T2_OHIG.txt for T2 and OHIG
• dbbc_config_file_104_point.txt for pointing observations