MAMBO Backends: BOGLE and ABBA


Now there are two MAMBO backends, BOGLE,  for the 37-channel MAMBO, and ABBA,  a new backend that will be used with the new 117-channel array. Here you find some basic instruction on how to use ABBA in test mode. In the following we give basic instructions of relevance for MAMBO users using the old backend BOGLE.
 

Starting BOGLE

If you need o start, restart, or monitor BOGLE, open three windows (if not already existent!) on the mrt-lx8 console to the right of the obs console:


1. On window 1, telnet to mrt-vis2 (the pc standing in the back computer room probably next to the new file server mrt-lx1), 
login as rlemke. Inquire about the status of BOGLE_control: 

/sbin/init.d/bogle  status

If it is not running, and you want to start it, make sure that the backend process mrt_be was stopped on the VAX.
now start BOGLE_control:

/sbin/init.d/bogle start

and let the operator restart the backend process (through @befast, e.g.). In case you wish to restart the BOGLE_control
stop it first with

/sbin/init.d/bogle stop

and then start it again. Always make sure that the backend process on the VAX was stopped before that, 
else the VAX may crash!


2. On window 2, login to mrt-lx3 as "hello". Then type

kermit
connect

which opens a kermit connection to the BOGLE serial port so you can see what's happening there. When a scan starts, you should get some line there saying which sbs parameter it picks (2 for wobbler, 3 for skydip, 1 for internal generator), such as:

    You selected 2 Blank/Sync CombinationThe Integrationszyklus is: 1 

You can set this also by hand if you need (by typing e.g., sbs 2) to switch between wobbler mode or skydip or the internal generator for the blank and sync. Type ? for help.


3. On window 3  (optional) you may login again to mrt-vis2, where bogle runs, and open a remote shell to BOGLE:

rsh bogle

You should get a response prompt:  BOGLE -> 
If needed you can reboot bogle here (after stopping the backend process on IRAMEA!) by typing

BogleRestart

Then the rsh will be lost after about 20sec (wait a while) and you can re-enter with rsh bogle.
During data taking, you will see messages appear on the screen of the sort:

6192.780273 3.118489 259290 63652
6207.853027 3.118507 259292 63501
6222.925781 3.118497 259295 63353
Selected BS 2
6242.156738 7.276470 259291 62725 
etc
 


On window 1 you can also start:

tail -f   /var/tmp/dataSynchronizer.log

which shows you the error log that BOGLE writes, and which looks like:

Bogle: 6507.748047 3.638300
6509.307100 5.717200
Bogle: 6522.820312 3.118400
6524.379800 5.717200
Bogle: 6537.893066 3.118500
6539.452500 5.197500 

There should be a line appearing after every subscan in point, focus, mapping or onof, and about every second during skydip. Stop the tail again with <crtl>C. The last number in each line is the time difference between two data transfers from bogle to the VAX.


Problems may arise due to a nonfunctional network connection with mrt-vis2. If some connection hangs, go to its console and enter, provided you are loged in as root (same pw as usual):

init 1
init 2

which will restart the network connection. If the machine is frozen or so,  reboot it (reboot, or halt, or push the reset next to the floppy) and login again as root.

After this it is necessary to restart BOGLE_control (window 1). Before this you may also want to reboot Bogle (BogleRestart in window 3).
Window 2 should not be affected.

If it is necessary to hard boot BOGLE, go up to the receiver cabin and push the ABORT and then the RESET button. BOGLE is located in a VME crate, the CPU-board is the first on the left. At the bottom of the crate there is a little box which creates the blank/sync signal for BOGLE and ABBA from the wobbler status signal - just for your information. 


For serious unsolvable problems, contact Albrecht Sievers, Roland Lemke, or Frank Bertoldi.
 

(f.bertoldi  & a.sievers 19.2.01)