User Tools
operations:documentation.dbbcsetupivs_9.10.5
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 Next revision Both sides next revision | ||
|
operations:documentation.dbbcsetupivs_9.10.5 [2012/12/03 22:06] Jim Lovell |
operations:documentation.dbbcsetupivs_9.10.5 [2013/08/01 05:25] Jim Lovell |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| 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 default configuration is kept in ''dbbc_config_file_v102.txt'' and this will be loaded when the server software is started. | + | If you can't connect to the DBBC VNC server, the DBBC may have died. In which case, follow these notes on [[operations:documentation:dbbc_restart|Recovering from a DBBC Failure]] |
| - | Check to see if a program called ''DBBC Control net'' is running. If it's not running, start it. There's a link to it from the desktop. | + | <note important>Note that Yg is now running v104 of the DBBC software but Hb and Ke are currently on v102.</note> |
| - | If the DBBC has had a power cycle or if there have been timing problems, or if you just want to be cautious, say "y" when asked if you want to use the default config. Configurations will take about 2 minutes. | + | |
| + | In ''C:\DBBC_CONF\'' are several configuration files for different experiment types. The default configuration is kept in ''dbbc_config_file_v102.txt'' (or ''dbbc_config_file_104.txt'' for Yg) and this will be loaded when the server software is started. | ||
| + | |||
| + | Check to see if a program called ''DBBC2 ControlDDC v102.exe'' is running (at Yg it should be ''DBBC2 ControlDDC v104.exe''). If it's not running, start it. There's a link to it from the desktop. (Don't have two instances running.) | ||
| + | <note important>Make sure you are running v102 of the DBBC Control software at Hb and Ke, and v104 at Yg.</note> | ||
| + | If the DBBC has had a power cycle or if there have been timing problems, or if you just want to be cautious, say "y" when asked if you want to reconfig with the defaults. Configurations will take about 2 minutes. | ||
| <note important>If you did reconfigure the DBBC, synchronise the DBBC to the station pps with the following command from eRemoteControl | <note important>If you did reconfigure the DBBC, synchronise the DBBC to the station pps with the following command from eRemoteControl | ||
| Line 14: | Line 19: | ||
| The Field system will load the necessary configuration for the experiment later if the default is not correct. | The Field system will load the necessary configuration for the experiment later if the default is not correct. | ||
| - | Lastly, make sure the 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 Control net.exe'' running in a terminal window. If you find it, exit it. | + | 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. | 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. | ||
| Line 20: | Line 25: | ||
| A full list of DBBC commands (requiring a ''dbbc='' prefix if using eRemoteControl)) is given in the {{:hardware:dbbc-command-set-v2.3.pdf| DBBC Command Set V2.3}} document. | A full list of DBBC commands (requiring a ''dbbc='' prefix if using eRemoteControl)) is given in the {{:hardware:dbbc-command-set-v2.3.pdf| DBBC Command Set V2.3}} document. | ||
| + | Target power levels for the CoMos are listed [[operations:documentation.dbbcsetupivs_v2|here ]] | ||
/home/www/auscope/opswiki/data/pages/operations/documentation.dbbcsetupivs_9.10.5.txt · Last modified: 2016/07/27 18:19 by Warren Hankey
Page Tools
