*** empty log message ***
This commit is contained in:
cvs
59
doc/user/poldi.htm
Normal file
59
doc/user/poldi.htm
Normal file
@ -0,0 +1,59 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>POLDI Reference Manual</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<!latex-off>
|
||||
<H1>POLDI Reference Manual</H1>
|
||||
<!latex-on>
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
<!latex-off>
|
||||
<h1>General User Commands</h1>
|
||||
<p>
|
||||
<ul>
|
||||
<li><a href="sicsinvoc.htm">logging</a> in to SICS.
|
||||
<li><a href="drive.htm">Driving</a> motors.
|
||||
<li><a href="poldimo.htm">List</a> of POLDI motors.
|
||||
<li>Controlling the <a href="chopper.htm">chopper system</a>.
|
||||
<li><a href="count.htm">Counting</a>.
|
||||
<li><a href="logging.htm">logging</a> actions.
|
||||
<li><a href="logbook.htm">logbook</a>.
|
||||
<li><a href="commandlog.htm">commandlog</a>.
|
||||
<li><a href="batch.htm">Batch</a> processing.
|
||||
<li><a href="token.htm">Grabbing control</a>.
|
||||
</UL>
|
||||
</p>
|
||||
<h1>Advanced Topics</h1>
|
||||
<p>
|
||||
<UL>
|
||||
<li>Handling <a href="samenv.htm">sample environment</a> devices in SICS.
|
||||
<li>Configuring <a href="histogram.htm">histogram memory</a>
|
||||
<li>Configuring <a href="poldiwrite.htm">data storage.</a>
|
||||
<li><a href="motor.htm">Motor Parameters</a>.
|
||||
<li>Dealing with the <a href="counter.htm">counter box</a>.
|
||||
<li>Directly access a <a href="ctrl.htm">serial device.</a>
|
||||
<li>SICS <a href="system.htm">system commands</a>.
|
||||
<li>Doing a <a href="topscan.htm">scan</a>.
|
||||
<li>Configuring a <a href="config.htm">client connection</a> manually.
|
||||
<li><a href="trouble.htm">Trouble</a> shooting.
|
||||
</UL>
|
||||
</p>
|
||||
<h1>Download Manual</h1>
|
||||
<ul>
|
||||
<li><a href="poldiman.ps">Postscript Format</a>,246KB
|
||||
</ul>
|
||||
<!latex-on>
|
||||
</BODY>
|
||||
</HTML>
|
||||
46
doc/user/poldicho.htm
Normal file
46
doc/user/poldicho.htm
Normal file
@ -0,0 +1,46 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Chopper Control</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<H1>Chopper Control</H1>
|
||||
<P>
|
||||
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.
|
||||
</p>
|
||||
<p>
|
||||
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 <a
|
||||
href="drive.htm">drive</a> command. The commands understood by the
|
||||
chopper controller object are:
|
||||
<dl>
|
||||
<DT>choco list
|
||||
<DD>prints a listing of all known chopper parameters. Parameters phase and ratio are not used.
|
||||
<DT>choco <i>name</i>
|
||||
<DD>print only the value of parameter name. Possible values for name
|
||||
can be extracted from the list printed with choco list (example choco <i>speed</i>).
|
||||
</dl>
|
||||
The following virtual motor variable exists.
|
||||
<dL>
|
||||
<DT>chopperspeed
|
||||
<DD>disk chopper speed
|
||||
</DL>
|
||||
The variable <i>chopperspeed</i> kindly prints its current value when given as a command. Modifying the value happens through the normal drive
|
||||
command. For instance the command:
|
||||
<pre>
|
||||
drive chopperspeed 10000
|
||||
</pre>
|
||||
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!
|
||||
</p>
|
||||
</BODY>
|
||||
</HTML>
|
||||
86
doc/user/poldimo.htm
Normal file
86
doc/user/poldimo.htm
Normal file
@ -0,0 +1,86 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>POLDI motors</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<H1>POLDI motors</H1>
|
||||
<P>
|
||||
<h2>Physical Motors</h2>
|
||||
<DL>
|
||||
<DT>D1HL
|
||||
<DD>2-axis diaphragm - horizontal translation (left)
|
||||
<DT>D1HR
|
||||
<DD>2-axis diaphragm - horizontal translation (right)
|
||||
<DT>D2HL
|
||||
<DD>4-axis diaphragma - horizontal translation (left)
|
||||
<DT>D2HR
|
||||
<DD>4-axis diaphragma - horizontal translation (right)
|
||||
<DT>D2VU
|
||||
<DD>4-axis diaphragma - vertical translation (upper side)
|
||||
<DT>D2VL
|
||||
<DD>4-axis diaphragma - vertical translation (lower side)
|
||||
<DT>SHU
|
||||
<DD>sample table x-translation
|
||||
<DT>SHL
|
||||
<DD>sample table y-translation
|
||||
<DT>SV
|
||||
<DD>sample table z-translation
|
||||
<DT>SA
|
||||
<DD>sample table rotation
|
||||
<DT>SGU
|
||||
<DD>sample goniometer rotation (alpha)
|
||||
<DT>SGL
|
||||
<DD>sample goniometer rotation (beta)
|
||||
<DT>RSU
|
||||
<DD>sample table overlay for radioactive samples (x-translation)
|
||||
<DT>RSL
|
||||
<DD>sample table overlay for radioactive samples (y-translation)
|
||||
<DT>RSA
|
||||
<DD>sample table overlay for radioactive samples (rotation)
|
||||
</DL>
|
||||
</P>
|
||||
<h2>Virtual motors</h2>
|
||||
<p>
|
||||
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.
|
||||
<dl>
|
||||
<DT>flightpathlength
|
||||
<DD>distance between chopper and detector [in mm]
|
||||
<DT>chopper_sample
|
||||
<DD>distance between chopper and sample [in mm]
|
||||
<DT>chopper_dia
|
||||
<DD>distance between chopper and 2-axis diaphragma [in mm]
|
||||
<DT>dia1_dia2
|
||||
<DD>distance between 2-axis diaphragma and 4-axis diaphragma [in mm]
|
||||
<DT>dia2_sample
|
||||
<DD>distance between 4-axis diaphragma and sample position [in mm]
|
||||
<DT>detectordist
|
||||
<DD>distance between sample position and detector [in mm]
|
||||
<DT>chopperspeed
|
||||
<DD>disk chopper speed
|
||||
<DT>twotheta
|
||||
<DD>scattering angle to the middle of the detector
|
||||
<DT>x0_det
|
||||
<DD>centre of the detector circle (x-coordinate)
|
||||
<DT>y0_det
|
||||
<DD>centre of the detector circle (y-coordinate)
|
||||
<DT>nodet
|
||||
<DD>number of detector cells (400 really cells exist)
|
||||
<DT>det_size
|
||||
<DD>size of a single detector cell [in mm]
|
||||
<DT>det400
|
||||
<DD>automatic configuration of the histogram memory to 400 detectors with
|
||||
a cell size of 2.5 mm
|
||||
<DT>det800
|
||||
<DD>automatic configuration of the histogram memory to 800 detectors
|
||||
(including 400 virtual detectors) with a cell size of 1.25 mm
|
||||
</dl>
|
||||
Note: The adjustments of det400 and det800 will be activated after giving a
|
||||
HM init command!
|
||||
</p>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
||||
32
doc/user/poldiscan.htm
Normal file
32
doc/user/poldiscan.htm
Normal file
@ -0,0 +1,32 @@
|
||||
<html>
|
||||
<body>
|
||||
<hr size=4 width="66%">
|
||||
<h2>Special POLDI scan command</h2>
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
<p>
|
||||
The command syntax for the POLDI specific scanning is like this:
|
||||
<BLOCKQUOTE>
|
||||
scanhm <i>var start delta np preset</i>
|
||||
</BLOCKQUOTE>
|
||||
All parameters must be specified. The parameters and their meanings:
|
||||
<UL>
|
||||
<LI><b>var start delta</b> This is how the variables to scan are specified. For
|
||||
each variable scanned the name of the variable, the start value and the step wide must be given.
|
||||
<LI><b>np</b> is the number of points to scan.
|
||||
<LI><b>preset</b> is the preset to use for the counter. As the counter mode,
|
||||
the mode <i>timer</i> is predefined.
|
||||
</UL>
|
||||
</p>
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
30
doc/user/poldiwrite.htm
Normal file
30
doc/user/poldiwrite.htm
Normal file
@ -0,0 +1,30 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>POLDI Data Storage</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<H1>POLDI Data Storage</H1>
|
||||
<P>
|
||||
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 <a href="count.htm">count</a>
|
||||
command. However, data file writing can be initiated and configured
|
||||
manually from the command line through the following commands:
|
||||
<dl>
|
||||
<DT>storedata start
|
||||
<DD>Write a new data file
|
||||
<DT>storedata update
|
||||
<DD>Updates the current data file.
|
||||
<DT>storedata intervall
|
||||
<DD>prints the current update intervall to use during counting. Units
|
||||
is minutes. Default is 20 minutes.
|
||||
<DT>storedata intervall <i>newval</i>
|
||||
<DD>Sets the update intervall to newval minutes.
|
||||
<DT>killfile
|
||||
<DD>This command will overwrite the last data file written and thus
|
||||
effectively erase it. Therefore this command requires manager privilege.
|
||||
</DL>
|
||||
</P>
|
||||
</BODY>
|
||||
</HTML>
|
||||
Reference in New Issue
Block a user