- Updated the managers documentation a little
- The crystal settings calculation in hkl now tried to put omega into the limts by calculating a delta omega. - TRICS data files now include HKL and the UB - The scan module has been expanded to support user defined scans which run a script at any scan point. - A small fix to the PSD code in SinqHM_srv_filler
This commit is contained in:
cvs
@ -34,7 +34,8 @@ The following commands are available to install motors into the system:
|
||||
<DD> This command creates a simulated
|
||||
motor with the lower limits lowlim, the upper limit uplim, an ratio of
|
||||
randomly generated errors err and a driving speed of speed. Use this for
|
||||
testing and instrument simulation.
|
||||
testing and instrument simulation. If err is less then 0, the motor will
|
||||
not create failures and thus can be used in a instrument simulation server.
|
||||
<DT>Motor name EL734 host port chan no
|
||||
<DD>This command creates a stepper motor named name which is controlled through a
|
||||
El734 motor controller. The
|
||||
@ -46,20 +47,54 @@ El734DC motor controller. The
|
||||
parameters host, port, chan have the meanings defined above. no is the
|
||||
number of the motor in the EL734DC motor controller.
|
||||
</DL>
|
||||
<DT>MakePIMotor name c804 pararray
|
||||
<DD>Creates a motr name connected to a C804 motor controller from the
|
||||
manufacturer Physik Instrumente. Pararray is a Tcl array holding the
|
||||
initialization information. The follwoing elements are required in this
|
||||
array:
|
||||
<dl>
|
||||
<dt>Computer, port, channel
|
||||
<dd>The standard connection parameters.
|
||||
<dt>upperlimit, lowerlimit
|
||||
<dd>The limits for this motor.
|
||||
<dt>motor
|
||||
<dd>The number of the motor in the motor controller.
|
||||
</dl>
|
||||
<dt>Motor name pipiezo pararray
|
||||
<dd>Creates a piezo electric positioning device. Again the controller is a
|
||||
Physik Instrumente controller. pararray has the same meaning as for the
|
||||
C804 controller given above.
|
||||
</p>
|
||||
|
||||
<h3>Counting Devices</h3>
|
||||
<p>
|
||||
<DL>
|
||||
<DT>MakeCounter name SIM
|
||||
<DT>MakeCounter name SIM failrate
|
||||
<DD>This command creates a simulated single counter
|
||||
accessible as object name.
|
||||
accessible as object name. Failrate is the per centage of invocations
|
||||
at which the counter will generate a random failure for testing error
|
||||
treatment code. If failrate is less then 0, there are no
|
||||
failures. This can be used in a instrument simulation server.
|
||||
<DT>MakeCounter name EL737 host port chan
|
||||
<DD>This command creates a single
|
||||
counter name, using an EL737 driver. The counter is at host host, listening
|
||||
at port port and sits at serial port chan.
|
||||
</DL>
|
||||
<DT>MakeHMControl name counter hm1 hm2 hm3
|
||||
<dd>At some instruments (for instance TRICS) multiple counters or
|
||||
histogram memories are controlled by a master counter which watches
|
||||
over presets and the like. This command installs a virtual counter
|
||||
which does exactly that. The parameters are:
|
||||
<dl>
|
||||
<dt>name
|
||||
<dd>The name of the virtual counter in SICS
|
||||
<dt>counter The name of the master counter
|
||||
<dt>hm1, hm2, hm3
|
||||
<dd>Up to three slave counting devices.
|
||||
</dl>
|
||||
</dl>
|
||||
</p>
|
||||
|
||||
<h4>Histogram Memory</h4>
|
||||
<p>
|
||||
Due to the large amount of parameters, histogram memories are configured
|
||||
|
||||
@ -34,6 +34,24 @@ file) may use special commands for the installation of:
|
||||
<LI>Hardware
|
||||
</ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Actually the SICS servers configuration is rarely stored in one file
|
||||
but in several files which are included by the main configuration
|
||||
file. In general the following files are present:
|
||||
<DL>
|
||||
<dt>inst.tcl
|
||||
<DD>Replace inst with the name of the instrument in lowercase. This is
|
||||
the main initialization file. It should contain all the hardware
|
||||
initialization.
|
||||
<dt>instcom.tcl
|
||||
<DD>Again replace inst with name of the instrument in
|
||||
lowercase. This file holds instrument specific commands defined in the
|
||||
Tcl macro language. This file is automatically included by inst.tcl.
|
||||
<dt>scancommand.tcl, tecs.tcl, log.tcl
|
||||
<DD>Some macro definitions which are used by so many instruments that
|
||||
it was deemed appropraite to hold them in separate files. Such files
|
||||
are included from instcom.tcl.
|
||||
</dl>
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -35,7 +35,6 @@ which is described elsewhere.
|
||||
<ul>
|
||||
<li> To the general <a href =setup.htm> setup</a> section.
|
||||
<Li> To the <a href = inifile.htm> server initialision</a> section.
|
||||
<li> To the <a href = client.htm>client </a> configuration section.
|
||||
<li> To the section describing <a href=special.htm>special commands</a> for
|
||||
SICS administrators or programmers.
|
||||
<li> Commands for <a href=status.htm>status display</a> support.
|
||||
|
||||
@ -44,7 +44,7 @@ SICSINT followed by an interrupt number. For interrupt numbers see file
|
||||
interrupt.h.
|
||||
<li> <b> DefaultTclDirectory </b> specifies where Tcl defined commands are
|
||||
stored. When this is properly defined Tcl will autoload commands.
|
||||
<li> <b> StatusFile </b> defines the file to which he current state will be
|
||||
<li> <b> statusfile </b> defines the file to which he current state will be
|
||||
saved on close down of the server and restored from at startup time.
|
||||
<li><b>TelnetPort</b> The port number where the SICS server will be
|
||||
listening for telnet connections. If this option is missing login via telent
|
||||
@ -54,6 +54,11 @@ needed. The login word, This option defines this word. If this option is
|
||||
missing telnet login to SICS is disabled.
|
||||
<li><b>LogFileDir</b> This server option defines the directory where
|
||||
commandlog log files are kept.
|
||||
<li><b>RedirectFile</b> This defines a filename to which all output to
|
||||
stdout and stderr is logged by the SICS server. This is mainly a
|
||||
debugging feature.
|
||||
<li><b>TecsPort</b> The port number at which the Tecs temperature
|
||||
control server is listening.
|
||||
</ul>
|
||||
</p>
|
||||
</body>
|
||||
|
||||
@ -1,8 +1,78 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>General SICS Setup</TITLE>
|
||||
<TITLE>SICS Setup</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<H1>SICS programs, Scripts and Prerequisites<h1>
|
||||
<p>
|
||||
<h2>Hardware</h2>
|
||||
The following hardware is usually present for any SICs instrument:
|
||||
<ul>
|
||||
<li>An instrument computer
|
||||
<li>A Lantronix terminal server with 8-16 serial ports for connecting:
|
||||
<li>Motor controllers
|
||||
<li>Counter boxes
|
||||
<li>Temperature controllers.
|
||||
<li>Optionally 1-n histogram memory computers are present.
|
||||
</ul>
|
||||
The terminal server software is provided by Lantronix, see the
|
||||
appropriate manuals for the device for a description. The histogram
|
||||
memories are 6800 VME onboard computers running the VXworks realtime
|
||||
operating system and some home grown histogramming software documented
|
||||
elsewhere.
|
||||
</p>
|
||||
<h2>Server programs</h2>
|
||||
<p>
|
||||
On the instrument computer the following software must run:
|
||||
<dl>
|
||||
<dt>SerPortServer
|
||||
<dd>This is a TCP/IP server which implements a special protocoll for
|
||||
communicating with serial ports. The actual communication with the
|
||||
serial ports is done through the Lantronix terminal server. Both the
|
||||
serial port protocoll and the SerPortServer are only documented in the
|
||||
source code.
|
||||
<dt>TecsServer
|
||||
<dd>This is a TCP/IP server which watches over temperature
|
||||
controllers. The only knwon source of documentation about this
|
||||
software is Markus Zolliker.
|
||||
<dt>FileSync
|
||||
<dd>This is a little UDP server which waits for UDP messages from the
|
||||
instrument control program. Then the server starts a script which
|
||||
synchronizes the local data directory with the central data storage on
|
||||
the labarotory server. FileSync is configured through an
|
||||
initilaization file usually called fs.ini. See the comments therein
|
||||
for more information.
|
||||
<dt>SICServer
|
||||
<dd>This is the actual instrument control server. The configuration of
|
||||
this program is documented in this manual.
|
||||
</dl>
|
||||
Additionally a client program is needed which connects to the
|
||||
instrument control server and provides a user interface to it.
|
||||
</p>
|
||||
|
||||
<h2>Scripts</h2>
|
||||
<p>
|
||||
To get all this software up and running a couple of shell scripts have
|
||||
been provided:
|
||||
<dl>
|
||||
<dt>startsics
|
||||
<dd> This script starts all the necessary server programs for driving
|
||||
the instrument.
|
||||
<dt>killsics
|
||||
<dd>This script shuts down all instrument control servers properly.
|
||||
<dt>keepalice, keepaliveserp
|
||||
<dd>The server programs are automatically restarted when they
|
||||
die. This is done through these scripts. keepaliveserp is a special
|
||||
script for the serial port server.
|
||||
<dt>instsync
|
||||
<dd>replace inst by the name of the instrument in lower case. This
|
||||
script is invoked by the FileSync server and is responsible for
|
||||
synchronizing the local data store with the one on the labaratory
|
||||
server. This is usally done by calling the unix program rsync with
|
||||
appropriate parameters.
|
||||
</dl>
|
||||
</p>
|
||||
|
||||
<H1>General SICS Setup</H1>
|
||||
<P>
|
||||
SICS is a client server system. This implies that there is a server program
|
||||
@ -24,10 +94,16 @@ server is kept along with local copies of all necessary clients, the server
|
||||
initialisation files and special macro files defined for the instrument.
|
||||
<DT>data
|
||||
<DD>The data directory is the central place where all data files collected
|
||||
at the instrument are stored. Additionally this directory holds a file named
|
||||
at the instrument are stored. This directory contains subdirectories
|
||||
for each year. These directories hold the data collected at the
|
||||
instrument in this year plus a file named
|
||||
DataNumber which keeps the current serial number of the data files. This
|
||||
file should never be edited. However, on the first of january an instrument
|
||||
manager should reset the serial number in this file to 0.
|
||||
file should never be edited. At the start of each year the instruement manager
|
||||
must create a new directory with an empty DataNumber
|
||||
file. Additionally the
|
||||
path variables both for the data file directory and the DataNumber
|
||||
file have to be set to the new directory in the instrument
|
||||
initialization file.
|
||||
<DT>log
|
||||
<DD> The log directory contains the server log files and the automatically
|
||||
generated client log files. Any now and then, and especially when disk space
|
||||
@ -41,6 +117,12 @@ as lynx or netscape.
|
||||
<DD> The sim directory is meant to hold all files necessary for a SICServer
|
||||
initialised for the instrument but configured with simulated hardware. This
|
||||
facility is meant for testing of command files.
|
||||
<DT>motor
|
||||
<DD>This directory holds a script for reading and restoring the motor
|
||||
parameter from the EL734 motor controllers. And the motor parameters
|
||||
stored in parameter files. It is the instrument scientists
|
||||
responsability to save the motor parameters after changes to the
|
||||
configuration of the instrument.
|
||||
</DL>
|
||||
Besides these directories there should be nothing on the instrument account.
|
||||
All evaluated data, personal command files etc. should be held on the normal
|
||||
@ -55,7 +137,8 @@ source /data/lnslib/bin/lns.login</b> into her .login file.
|
||||
<h2> SICS Installation</h2>
|
||||
<p>
|
||||
All executables and files necessary to run SICS for each instrument is
|
||||
avaialable under the /data/lnslib/src/sics hierarchy. The bin directory
|
||||
avaialable under the /data/lnslib/distribution/sics hierarchy.
|
||||
The bin directory
|
||||
holds general executable files and a directory for each instrument which
|
||||
holds instrument specific files. SICS installation on a unix system is
|
||||
greatly simplified by using the <b>sicsinstall</b> korn shell script. This
|
||||
@ -74,6 +157,23 @@ directory. This command is meant to be used by computing staff only.
|
||||
<DD>copies all files necessary for the instrument TOPSI.
|
||||
<DT>sans
|
||||
<DD>copies all files necessary for the instrument SANS.
|
||||
<DT>hrpt
|
||||
<DD>copies all files necessary for the instrument HRPT.
|
||||
<DT>amor
|
||||
<DD>copies all files necessary for the instrument AMOR
|
||||
<DT>focus
|
||||
<DD>copies all files necessary for the instrument FOCUS
|
||||
<DT>tasp
|
||||
<DD>copies all files necessary for the instrument TASP
|
||||
<DT>druechal
|
||||
<DD>copies all files necessary for the instrument DRUECHAL
|
||||
<DT>trics
|
||||
<DD>copies all files necessary for the instrument TRICS
|
||||
<DT>save inst
|
||||
<DD>copies all the instrument configuration files from the instrument
|
||||
account back to to the distribution area. Replace inst with the name
|
||||
of the instrument in lower case. This call is necessary to save
|
||||
modified instrument configurations.
|
||||
<DT>doc
|
||||
<DD>updates only the documentation on your disk.
|
||||
<DT>exe
|
||||
|
||||
Reference in New Issue
Block a user