BNMR: CAMP

• BNMR overview
• Getting started
• Troubleshooting
• All BNMR pages
• Midas

Links

• BNMR
• Experimental Modes
• Getting Started

Introduction

The software package CAMP is used for the slow controls for the bnmr and bnqr experiments.

The CAMP server runs on a MVME162 located in the VME crate. The name of the MVME162 is

The CAMP system itself is accessed using the CAMP User Interface (CUI). Using the CUI, the user can add instruments to be accessed by the DAQ system during the experiment.

CAMP Hostname

The CAMP Hostname is

• bnmrvw for the bnmr experiment or
• polvw for bnqr experiment

The CAMP hostname is set in two places in the DAQ system :

1. environment variable CAMP_HOST

[bnmr@isdaq01 ~]$ printenv CAMP_HOST
bnmrvw.triumf.ca

2. in the ODB

 [local:bnmr:Stopped]/>ls "/Equipment/FIFO_acq/mdarc/camp/camp hostname"
 camp hostname                   bnmrvw.triumf.ca

CAMP User Interface

To access the CUI, in an xterm type "camp".

[bnmr@isdaq01 ~]camp

A display similar to Figure 1 will appear.

Figure 1 Example of CAMP User Interface

The camp command will use the default camp hostname (bnmrvw in Figure 1). The camp hostname is contained in the environment variable CAMP_HOST, defined at login (in ~/.cshrc). The camp hostname is also defined in the ODB at path /Equipment/FIFO_acq/mdarc/camp/camp hostname for the use of the DAQ system. The name should be the same as CAMP_HOST.

To access the Camp User Interface using a different camp host, specify the camp hostname, e.g.

[bnmr@isdaq01 ~]camp -node polvw

CAMP in BNMR/BNQR

The CAMP system is used for two purposes in the BNMR/BNQR experiments:

• for logging of CAMP data to the saved file
• for the CAMP scan experiment(s) Experimental Modes 1c and 1j

CAMP Logging

Logging of CAMP data to the saved file is handled differently for

• Type 1 (I-MUSR) runs
• Type 2 (TD-MUSR) runs

In both cases, #Automatic CAMP variables are saved.

Automatic CAMP variables

File:Review run params.png

Figure 1 Review Run Parameters Links on Custom Status Page

Automatic CAMP variables are listed in ODB at path /Equipment/FIFO_acq/mdarc/camp/ and can be easily accessed by clicking on the alias link "AutoHeaders" in the section "Review Run Parameters" on the Custom Status Page (Figure 1). This will result in a page displayed similar to Figure 2.

File:Autoheaders bnmr.png

Figure 2 Autoheaders ODB page for bnmr

The user enters the required CAMP path for "temperature variable" and "field variable", or blank if not used. The CAMP paths must be written exactly as they appear in the #CAMP User Interface. Automatic CAMP variables (if defined) are saved for both Type 1 and Type 2.

ODB Keys in the Automatic Headers subtree

The Automatic Headers subtree can be found at ODB path /Equipment/FIFO_acq/mdarc/camp. It contains the #Automatic CAMP variables for logging. Also see above for access to this directory via alias-link, and an example.

The ODB Keys found in this directory are explained below.

camp hostname

• Type: STRING
• Default:

This key in the Automatic headers subtree contains the name of the MVME host running CAMP. See examples at #CAMP Hostname. If the CAMP hostname is NOT blank, the CAMP host must be booted up and available for use.

The CAMP host is "pinged" before attempting access, to try to avoid a complete hangup of mdarc if the CAMP host is powered down. If the CAMP host is not responding or logging is turned off, the run start may fail, or a warning message will be displayed each time a file is saved.

---

temperature variable

• Type: STRING
• Default:

This key in the Automatic headers subtree contains the camp path of the automatic temperature variable used to fill the temperature field in the run header. The CAMP paths must be written exactly as they appear in the #CAMP User Interface. The path must start with a slash (/) or the string will be ignored. The average value is used. All failures are silently ignored. To disable logging of this variable, leave it blank.

---

field variable

• Type: STRING
• Default:

This key in the Automatic headers subtree contains the camp path of a the field variable used to fill the appropriate area in the run header. The CAMP paths must be written exactly as they appear in the #CAMP User Interface. The path must start with a slash (/) or the string will be ignored. The average value is used. All failures are silently ignored. To disable logging of this variable, leave it blank.

---

RF power variable

• Type: STRING
• Default:

This key in the Automatic headers subtree contains the camp path of a the RF power variable used to fill the appropriate area in the run header. The CAMP paths must be written exactly as they appear in the #CAMP User Interface. The path must start with a slash (/) or the string will be ignored. The average value is used. All failures are silently ignored. To disable logging of this variable, leave it blank.

---

enable weighted averaging

• Type: BOOL
• Default: y

This key in the Automatic headers subtree enables/disables weighted averaging of the values of all the CAMP devices listed as Automatic variables.

---

record temperature error

• Type: BOOL
• Default: y

If the value of this key in the Automatic headers subtree is TRUE, the error in temperature (standard deviation) is recorded.

---

record field error

• Type: BOOL
• Default: y

If the value of this key in the Automatic headers subtree is TRUE, the error in field (standard deviation) is recorded.

Type 1 (I-MUSR)

The CAMP variables to be logged in a Type 1 (I-MUSR) experiment must be listed in the ODB tree /Equipment/Camp/Settings.

Type 2 (TD-MUSR)

In this case, the CAMP variables to be logged are