diff --git a/doc/user/poldi.htm b/doc/user/poldi.htm new file mode 100644 index 00000000..bd7814be --- /dev/null +++ b/doc/user/poldi.htm @@ -0,0 +1,59 @@ + + +POLDI Reference Manual + + + +

POLDI Reference Manual

+ +

+Welcome to the Strain Scaning diffractometer POLDI at SINQ! This manual +describes how to operate POLDI through the means of the instrument +control software system SICS. SICS means: Sinq Instrument Control +System. SICS is a client server system. This means there is a magic server +program running somewhere which does all the work. The user interacts +only with client applications which communicate with the server +through the network. Most instument hardware (motor controllers, +counter boxes etc.) is connected to the system through RS-232 serial +connections. These RS-232 ports are connected to a terminal server +(name: PSTS240) by means of a special program running on it. The SICS server +communicates with this terminal server and other devices through the network. +

+ +

General User Commands

+

+

+

+

Advanced Topics

+

+

+

+

Download Manual

+ + + + diff --git a/doc/user/poldicho.htm b/doc/user/poldicho.htm new file mode 100644 index 00000000..050e6e38 --- /dev/null +++ b/doc/user/poldicho.htm @@ -0,0 +1,46 @@ + + +Chopper Control + + +

Chopper Control

+

+POLDI is equipped with a Dornier Disk Chopper. The SICS program handling +RS-232 requests at the chopper control computer +is rather slow. This would slow the SICS server to unacceptable +levels, if any request would be handled through the RS-232 interface. In order +to cope with the problem, the SICS server buffers chopper +information. This information is updated any minute if not set otherwise. +

+

+The chopper system control is divided into several distinct objects: There +is the actual chopper controller which mainly serves for answering +status requests. One virtual motor (chopperspeed) is available which +represent the modifiable parameter of the disk chopper. The parameter can +be driven through the normal drive command. The commands understood by the +chopper controller object are: +

+
choco list +
prints a listing of all known chopper parameters. Parameters phase and ratio are not used. +
choco name +
print only the value of parameter name. Possible values for name +can be extracted from the list printed with choco list (example choco speed). +
+The following virtual motor variable exists. +
+
chopperspeed +
disk chopper speed +
+The variable chopperspeed kindly prints its current value when given as a command. Modifying the value happens through the normal drive +command. For instance the command: +
+drive chopperspeed 10000
+
+will drive the disk chopper to 10000 RPM eventually and if no problem occurs. +Please check your input carefully for all chopper commands. +Dornier has provided no way to stop an erraneous command in its software. So, if you intend to run the chopper to 1000 RPM and mistyped it as 10000 then +you'll wait for 20 minutes until the chopper is at speed! +

+ + diff --git a/doc/user/poldimo.htm b/doc/user/poldimo.htm new file mode 100644 index 00000000..50db386b --- /dev/null +++ b/doc/user/poldimo.htm @@ -0,0 +1,86 @@ + + +POLDI motors + + +

POLDI motors

+

+

Physical Motors

+
+
D1HL +
2-axis diaphragm - horizontal translation (left) +
D1HR +
2-axis diaphragm - horizontal translation (right) +
D2HL +
4-axis diaphragma - horizontal translation (left) +
D2HR +
4-axis diaphragma - horizontal translation (right) +
D2VU +
4-axis diaphragma - vertical translation (upper side) +
D2VL +
4-axis diaphragma - vertical translation (lower side) +
SHU +
sample table x-translation +
SHL +
sample table y-translation +
SV +
sample table z-translation +
SA +
sample table rotation +
SGU +
sample goniometer rotation (alpha) +
SGL +
sample goniometer rotation (beta) +
RSU +
sample table overlay for radioactive samples (x-translation) +
RSL +
sample table overlay for radioactive samples (y-translation) +
RSA +
sample table overlay for radioactive samples (rotation) +
+

+

Virtual motors

+

+Virtual motors are instrument parameters which can be driven with the +drive and run commands, though they are not physical motors. Mostly +this encompasses coordinated movements of motors around several axis +or other lengthy and error prone hardware operations. +

+
flightpathlength +
distance between chopper and detector [in mm] +
chopper_sample +
distance between chopper and sample [in mm] +
chopper_dia +
distance between chopper and 2-axis diaphragma [in mm] +
dia1_dia2 +
distance between 2-axis diaphragma and 4-axis diaphragma [in mm] +
dia2_sample +
distance between 4-axis diaphragma and sample position [in mm] +
detectordist +
distance between sample position and detector [in mm] +
chopperspeed +
disk chopper speed +
twotheta +
scattering angle to the middle of the detector +
x0_det +
centre of the detector circle (x-coordinate) +
y0_det +
centre of the detector circle (y-coordinate) +
nodet +
number of detector cells (400 really cells exist) +
det_size +
size of a single detector cell [in mm] +
det400 +
automatic configuration of the histogram memory to 400 detectors with +a cell size of 2.5 mm +
det800 +
automatic configuration of the histogram memory to 800 detectors +(including 400 virtual detectors) with a cell size of 1.25 mm +
+Note: The adjustments of det400 and det800 will be activated after giving a +HM init command! +

+ + + + diff --git a/doc/user/poldiscan.htm b/doc/user/poldiscan.htm new file mode 100644 index 00000000..abab2355 --- /dev/null +++ b/doc/user/poldiscan.htm @@ -0,0 +1,32 @@ + + +
+

Special POLDI scan command

+

+Additionally a special POLDI scan command was programmed which offers the +possibility to scan variables (motor) against detector count rate. For this +purpose the 400 detector cells are divided into 4 groups (5-100, 101-200, +201-300, 301-395) where the count rates (stored in the histogram memory) +are added. +

+

+The command syntax for the POLDI specific scanning is like this: +

+scanhm var start delta np preset +
+All parameters must be specified. The parameters and their meanings: + +

+

+The scan data are saved in ASC-format in the directory /home/POLDI/scan. +Additionally the typical NeXus-files are available for each step of the scan. +The NeXus files are saved in the directory /home/POLDI/data/2002. +

+ + diff --git a/doc/user/poldiwrite.htm b/doc/user/poldiwrite.htm new file mode 100644 index 00000000..36525a99 --- /dev/null +++ b/doc/user/poldiwrite.htm @@ -0,0 +1,30 @@ + + +POLDI Data Storage + + +

POLDI Data Storage

+

+POLDI writes data into portable binary NeXus files. The scheme implemented +involves opening a new file for any run and updating this file at +predefined intervalls during counting operations. All this is commonly +handled automatically by the count +command. However, data file writing can be initiated and configured +manually from the command line through the following commands: +

+
storedata start +
Write a new data file +
storedata update +
Updates the current data file. +
storedata intervall +
prints the current update intervall to use during counting. Units +is minutes. Default is 20 minutes. +
storedata intervall newval +
Sets the update intervall to newval minutes. +
killfile +
This command will overwrite the last data file written and thus + effectively erase it. Therefore this command requires manager privilege. +
+

+ +