aktualisierte Hardware(terminal server), kursive bzw. fett gedruckte Schreibweise
Beispiele
This commit is contained in:
cvs
@ -19,30 +19,30 @@
|
||||
three commands have been defined:</p>
|
||||
<p>
|
||||
The <b> Buf </b> object is responsible for creating and deleting Rünbuffers. The syntax is:<ul>
|
||||
<li> <b> Buf new name </b> creates a new empty Rünbuffer with the name name. name will be installed as a SICS object afterwards.
|
||||
<li> <b> Buf copy name1 name2 </b> copies Rünbuffer name1 to buffer name2.
|
||||
<li> <b> Buf del name </b> deletes the Rünbuffer name.
|
||||
<li> <b> Buf new <i>name</i> </b> creates a new empty Rünbuffer with the name name. name will be installed as a SICS object afterwards.
|
||||
<li> <b> Buf copy <i>name1 name2</i> </b> copies Rünbuffer name1 to buffer name2.
|
||||
<li> <b> Buf del <i>name</i> </b> deletes the Rünbuffer name.
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
After creation, the Rünbuffer is accessible by his name. It
|
||||
then understands the commands:<ul>
|
||||
<li> <b> NAME append what shall we do with a drunken sailor </b> will add all text after append as a new line at the end of the Rünbuffer.
|
||||
<li> <b> NAME print </b> will list the contents of the Rünbuffer.
|
||||
<li> <b> NAME del iLine </b> will delete line number iLine from the Rünbuffer.
|
||||
<li> <b> NAME ins iLine BimBamBim </b> inserts a new line <b> after </b> line iLine into the Rünbuffer. The line will consist of everything given after the iLine.
|
||||
<li> <b> NAME subst pattern newval </b> replaces all occurences of pattern in the Rünbuffer by the text specified as newval. Currently this feature allows only exact match but may be expanded to Unix style regexp or shell like globbing.
|
||||
<li> <b> NAME save filename </b> saves the contents of the Rünbuffer into file filename.
|
||||
<li> <b> NAME load filename </b> loads the Rünbuffer with the data in file filename.
|
||||
<li> <b> NAME run </b> executes the Rünbuffer.
|
||||
<li> <b> <i>NAME</i> append <i>what shall we do with a drunken sailor</i> </b> will add all text after append as a new line at the end of the Rünbuffer.
|
||||
<li> <b> <i>NAME</i> print </b> will list the contents of the Rünbuffer.
|
||||
<li> <b> <i>NAME</i> del <i>iLine</i> </b> will delete line number iLine from the Rünbuffer.
|
||||
<li> <b> <i>NAME</i> ins <i>iLine BimBamBim</i> </b> inserts a new line <b> after </b> line iLine into the Rünbuffer. The line will consist of everything given after the iLine.
|
||||
<li> <b> <i>NAME</i> subst pattern <i>newval</i> </b> replaces all occurences of pattern in the Rünbuffer by the text specified as newval. Currently this feature allows only exact match but may be expanded to Unix style regexp or shell like globbing.
|
||||
<li> <b> <i>NAME</i> save <i>filename</i> </b> saves the contents of the Rünbuffer into file filename.
|
||||
<li> <b> <i>NAME</i> load <i>filename</i> </b> loads the Rünbuffer with the data in file filename.
|
||||
<li> <b> <i>NAME</i> run </b> executes the Rünbuffer.
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
The Rünlist is accessible as object <b> stack </b>. Only one Rünlist per server is permitted. The syntax:<ul>
|
||||
<li> <b> stack add name </b> adds Rünbuffer name to the top of the stack.
|
||||
<li> <b> stack add <i>NAME</i> </b> adds Rünbuffer name to the top of the stack.
|
||||
<li> <b> stack list </b> lists the current Rünlist.
|
||||
<li> <b> stack del iLine </b> deletes the Rünbuffer iLine from the Rünlist.
|
||||
<li> <b> stack ins iLine name </b> inserts Rünbuffer name after Rünbuffer number iLine into the Rünlist.
|
||||
<li> <b> stack del <i>iLine</i> </b> deletes the Rünbuffer iLine from the Rünlist.
|
||||
<li> <b> stack ins <i>iLine NAME</i> </b> inserts Rünbuffer name after Rünbuffer number iLine into the Rünlist.
|
||||
<li> <b> stack run </b> executes the Rünlist and returns when all Rünbuffers are done.
|
||||
<li> <b> stack batch </b> executes the Rünlist but does not return when done but waits for further Rünbuffers to be added to the list. This feature allows a sort of background process in the server.
|
||||
</ul>
|
||||
|
||||
@ -12,7 +12,7 @@ file or can be
|
||||
configured by the instrument manager. There exists a special command,
|
||||
commandlog, which allows to control this log file.
|
||||
<DL>
|
||||
<DT>commandlog new filename
|
||||
<DT>commandlog new <i>filename</i>
|
||||
<DD>starts a new commandlog writing to filename. Any prior files will be
|
||||
closed. The log file can be found
|
||||
in the directory specified by the ServerOption LogFileDir. Usually this is
|
||||
@ -25,7 +25,7 @@ the log directory.
|
||||
<DD>Switches automatic log file creation on. This is normally switched on.
|
||||
Log files are written to the log directory of the instrument account. There
|
||||
are time stamps any hour in that file and there is a new file any 24 hours.
|
||||
<DT>commandlog tail n
|
||||
<DT>commandlog tail <i>[n]</i>
|
||||
<DD>prints the last n entries made into the command log. n is optional and defaults to 20. Up to 1000 lines are held in an internal buffer for this command.
|
||||
</DL>
|
||||
It is now possible to have a script executed whenever a new log file is
|
||||
|
||||
@ -3,19 +3,18 @@
|
||||
<title>Counting Commands</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Counting Commands.</h1>
|
||||
<P>
|
||||
<DL>
|
||||
<DT>count mode preset
|
||||
<DD> Does a count operation in mode with a preset of preset.
|
||||
The parameters are optional. If they are not
|
||||
given the count will be started with the current setting in the histogram
|
||||
memory object. After the count, StoreData will be automatically called.
|
||||
<DT> Repeat num mode preset.
|
||||
<h1>Counting Commands</h1>
|
||||
<dl>
|
||||
<DT>count <i>[mode preset]</i>
|
||||
<DD> Does a count operation in mode with a given preset.
|
||||
<i>Mode</i> can be <i>timer</i> or <i>monitor</i>.
|
||||
The parameters mode and preset are optional. If they
|
||||
are not given the count will be started with the
|
||||
current setting in the histogram memory object.
|
||||
<DT> repeat num mode preset.
|
||||
<DD> Calls count num times. num is a required parameter. The other two are
|
||||
optional and are handled as described above for count.
|
||||
</DL>
|
||||
</dl>
|
||||
Both commands make sure, that measured data is written to files.
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -24,39 +24,36 @@ the exponent is only in operation in Monitor mode.
|
||||
Again, in SICS the counter is an object which understands a set of
|
||||
commands:
|
||||
<ul>
|
||||
<li> <b> countername SetPreset val </b> sets the counting preset to val.
|
||||
<li> <b> countername GetPreset </b> prints the current preset value.
|
||||
<li> <b> countername preset val</b> With a parameter sets the preset, without inquires the preset value. This is a duplicate of getpreset and setpreset which has been provided for consistency with other commands.
|
||||
<li> <b> countername SetExponent val </b> sets the exponent for the counting
|
||||
<li> <b> countername setpreset <i>val</i> </b> sets the counting preset to val.
|
||||
<li> <b> countername getpreset </b> prints the current preset value.
|
||||
<li> <b> countername preset <i>val</i></b> With a parameter sets the preset, without inquires the preset value. This is a duplicate of getpreset and setpreset which has been provided for consistency with other commands.
|
||||
<li> <b> countername setexponent <i>val</i> </b> sets the exponent for the counting
|
||||
preset in monitor mode to val.
|
||||
<li> <b> countername GetExponent </b> prints the current exponent used
|
||||
<li> <b> countername getexponent </b> prints the current exponent used
|
||||
in monitor mode.
|
||||
<li> <b> countername SetMode val </b> sets the counting mode to val. Possible values are Timer for timer mode operation and Monitor for waiting for a monitor to reach a certain value.
|
||||
<li> <b> countername GetMode </b> prints the current mode.
|
||||
<li> <b> countername mode val</b> With a parameter sets the mode,
|
||||
<li> <b> countername setmode <i>val</i> </b> sets the counting mode to val. Possible values are Timer for timer mode operation and Monitor for waiting for a monitor to reach a certain value.
|
||||
<li> <b> countername getmode </b> prints the current mode.
|
||||
<li> <b> countername <i>mode val</i></b> With a parameter sets the mode,
|
||||
without inquires the mode value. This is a duplicate of getmode and
|
||||
setmode which has been provided for consistency with other
|
||||
commands. Possible values for val are either monitor or timer.
|
||||
<li> <b> countername SetExponent val </b> sets the exponent for the counting
|
||||
<li> <b> countername setexponent <i>val</i> </b> sets the exponent for the counting
|
||||
preset in monitor mode to val.
|
||||
<li> <b> countername GetCounts </b> prints the counts gathered in the last run.
|
||||
<li> <b> countername GetMonitor n </b> prints the counts gathered in the monitor number n in the last run.
|
||||
<li> <b> countername Count preset </b> starts counting in the current mode and the the preset preset.
|
||||
<li> <b> countername getcounts </b> prints the counts gathered in the last run.
|
||||
<li> <b> countername getmonitor <i>n</i> </b> prints the counts gathered in the monitor number n in the last run.
|
||||
<li> <b> countername count <i>preset</i> </b> starts counting in the current mode and the given preset.
|
||||
<li> <b> countername status </b> prints a message containing the preset and
|
||||
the current monitor or time value. Can be used to monitor the progress of
|
||||
the counting operation.
|
||||
<li> <b> countername gettime </b> Retrieves the actual time the counter
|
||||
counted for. This excludes time where there was no beam or counting was
|
||||
paused.
|
||||
<li><b>countername getthreshold m</b> retrieves the value of the threshold
|
||||
set for the monitor number m.
|
||||
<li><b>countername setthreshold m val</b> sets the threshold for monitor m
|
||||
to val. WARNING: this also makes monitor m the active monitor for evaluating
|
||||
the threshold. Though the EL7373 counterbox does not allow to select the
|
||||
<li><b>countername getthreshold <i>m</i></b> retrieves the value of the threshold set for the monitor number m.
|
||||
<li><b>countername setthreshold <i>m val</i></b> sets the threshold for monitor m to val. WARNING: this also makes monitor m the active monitor for evaluating the threshold. Though the EL7373 counterbox does not allow to select the
|
||||
monitor to use as control monitor in monitor mode, it allows to choose
|
||||
the monitor used for pausing the count when the count rate is below the
|
||||
threshold (Who on earth designed this?)
|
||||
<li><b>countername send arg1 arg2 arg3 ...</b> sends everything behind
|
||||
<li><b>countername send <i>arg1 arg2 arg3 ...</i></b> sends everything behind
|
||||
send to the counter controller and returns the reply of the counter
|
||||
box. The command set to use after send is the command set documented
|
||||
for the counter box elsewhere. Through this feature it is possible to
|
||||
|
||||
@ -5,22 +5,17 @@
|
||||
<BODY>
|
||||
<H1>Serial Port Direct Access</H1>
|
||||
<P>
|
||||
At SINQ serial devices are connected to a Macintosh computer. This Mac runs
|
||||
a serial port server which allows to read and write data through TCP/IP
|
||||
sockets to a serial port connected to the Mac. This document describes a simple
|
||||
interface for communicating with such serial devices.
|
||||
At SINQ serial devices are connected to a UNIX/LINUX computer. On this machine runs a serial port server which allows to read and write data through TCP/IP sockets to a serial port connected to the machine. This document describes a simple interface for communicating with such serial devices.
|
||||
</p>
|
||||
<H2>Invocation</H2>
|
||||
<P>
|
||||
The interface to a serial device connected to a Mac is initialised with the
|
||||
following command given at the Tcl prompt:<BR>
|
||||
The interface to a serial device connected to a UNIX/LINUX computer is initialised with the following command given at the Tcl prompt:<BR>
|
||||
<EM>Controller name computer port channel</EM><BR>
|
||||
This command opens a connection to the serial port on the Mac and
|
||||
installs a new command in order to interact with it. The parameters:
|
||||
This command opens a connection to the serial port on the UNIX/LINUX machine and installs a new command in order to interact with it. The parameters:
|
||||
<UL>
|
||||
<LI>name: is the name of the new command to generate for the connection in Tcl.
|
||||
<LI> computer: is the computer name of the Macintosh.
|
||||
<LI> port: is the TCP/IP port number at which the Macintosh
|
||||
<LI><b>name</b> is the name of the new command to generate for the connection in Tcl.
|
||||
<LI> <b>computer</b> is the computer name of the UNIX/LINUX machine.
|
||||
<LI> port: is the TCP/IP port number at which the UNIX/LINUX machine
|
||||
serial port server is is listening. Usually this is 4000.
|
||||
<LI>channel: is the number of the RS-232 port to connect to.
|
||||
</UL>
|
||||
|
||||
@ -31,8 +31,7 @@ instance if the preset is 25 and the exponent is 6, then counting will be
|
||||
continued until the monitor has reached 25 million. Note, that this scheme with
|
||||
the exponent is only in operation in Monitor mode.
|
||||
</p>
|
||||
|
||||
<h2> Configuration</h2>
|
||||
<h2>Configuration</h2>
|
||||
<p>
|
||||
A HM has a plethora of configuration options coming with it which define
|
||||
memory layout, modes of operation, handling of bin overflow and the like.
|
||||
@ -93,10 +92,10 @@ modifying time bins is restricted to instrument managers.
|
||||
<DL>
|
||||
<DT>HM timebin
|
||||
<DD> Prints the currently active time binning array.
|
||||
<DT>HM genbin start step n
|
||||
<DT>HM genbin <i>start step n</i>
|
||||
<DD>Generates a new equally spaced time binning array. Number n time bins
|
||||
will be generated starting from start with a stepwidth of step.
|
||||
<DT>HM setbin inum value
|
||||
will be generated starting from start with a stepwidth of step (example: HM genbin 10 1 5).
|
||||
<DT>HM setbin <i>inum value</i>
|
||||
<DD>Sometimes unequally spaced time binnings are needed. These can be
|
||||
configured with this command. The time bin iNum is set to the value value.
|
||||
<DT>HM clearbin
|
||||
@ -104,38 +103,35 @@ configured with this command. The time bin iNum is set to the value value.
|
||||
</DL>
|
||||
</p>
|
||||
|
||||
<h2>Histogram Memory Commands</h2>
|
||||
<h2>Histogram Memory Commands</h2>
|
||||
<p>
|
||||
Besides the configuration commands the HM understands the following
|
||||
commands:
|
||||
<DL>
|
||||
<DT>HM preset
|
||||
<DT>HM preset <i>[newval]</i>
|
||||
<DD> with a new value sets the preset time or monitor for counting. Without a
|
||||
value prints the current value.
|
||||
<DT>HM exponent
|
||||
<DT>HM exponent <i>[newval]</i>
|
||||
<DD> with a new value sets the exponent to use for the preset time
|
||||
in Monitor mode. Without a
|
||||
value prints the current value.
|
||||
<DT>CountMode
|
||||
<DD> with a new values sets the count mode. Possible values are Timer for a
|
||||
fixed counting time and Monitor for a fixed monitor count which has to be
|
||||
reached before counting finishes. Without a value print the currently active
|
||||
value.
|
||||
<DT>CountMode <i>[mode]</i>
|
||||
<DD> with a new values for <i>mode</i> sets the count mode. Possible values are Timer for a fixed counting time and Monitor for a fixed monitor count which has to be reached before counting finishes. Without a value print the currently active value.
|
||||
<DT>HM init
|
||||
<DD> after giving configuration command sthis needs to be called in order to
|
||||
<DD> after giving configuration commands this needs to be called in order to
|
||||
transfer the configuration from the host computer to the actual HM.
|
||||
<DT>HM count
|
||||
<DD> starts counting using the currently active values for CountMode and
|
||||
preset. This command does not block, i.e. in order to inhibit further
|
||||
commands from the console, you have to give Success afterwards.
|
||||
<DT>HM InitVal val
|
||||
<DT>HM initval <i>val</i>
|
||||
<DD> initialises the whole histogram memory to the value val. Ususally 0 in
|
||||
order to clear the HM.
|
||||
<DT> HM get i iStart iEnd
|
||||
<DT> HM get <i>i iStart iEnd</i>
|
||||
<DD> retrieves the histogram number i. A value of -1 for i denotes retrieval
|
||||
of the whole HM. iStart and iEnd are optional amd
|
||||
of the whole HM. iStart and iEnd are optional and
|
||||
allow to retrieve a subset of a histogram between iStart and iEnd.
|
||||
<DT>HM sum d1min d1max d2min d2max .... dnmin dnmax
|
||||
<DT>HM sum <i>d1min d1max d2min d2max .... dnmin dnmax</i>
|
||||
<DD>calculates the sum of an area on the detector. For each dimension a
|
||||
minimum and maximum boundary for summing must be given.
|
||||
</DL>
|
||||
|
||||
@ -13,10 +13,9 @@ LogBook understands the following syntax:
|
||||
<DT> LogBook
|
||||
<DD> alone prints the name of the current logfile and the status of event
|
||||
logging.
|
||||
<DT> LogBook file filename
|
||||
<DD> This command sets the filename to which output will be printed.
|
||||
Please note that this new filename will only be in effect after restarting
|
||||
logging.
|
||||
<DT> LogBook file <i>filename</i>
|
||||
<DD>sets the filename to which output will be printed. Please note
|
||||
that this new filename will only be in effect after restarting logging.
|
||||
<DT> LogBook on
|
||||
<DD> This command turns logging on. All commands and all answers will be
|
||||
written to the file defined with the command described above. Please note,
|
||||
|
||||
@ -7,7 +7,7 @@
|
||||
<p>
|
||||
SICS has a built in macro facility. This macro facility is aimed at instrument managers and users alike. Instrument managers may provide customised measurement procedures in this language, users may write batch files in this language. The macro language is John Ousterhout's Tool Command Language (TCL). Tcl has control constructs, variables of its own, loop constructs, associative arrays and procedures. Tcl is well documented by several books and online tutorials, therefore no details on Tcl will be given here. All SICS commands are available in the macro language. Some potentially harmful Tcl commands have been deleted from the standard Tcl interpreter. These are: exec, source, puts, vwait, exit,gets and socket. A macro or batch file can be executed with the command:</p>
|
||||
<p>
|
||||
<b> FileEval name </b> tries to open the file name and executes the script in this file. </p>
|
||||
<b> fileeval <i>name</i> </b> tries to open the file name and executes the script in this file. </p>
|
||||
Then there are some special commands which can be used within macro-sripts:
|
||||
<p>
|
||||
<b> ClientPut sometext1 ... </b> writes everything after ClientPut to
|
||||
@ -25,15 +25,15 @@ Then there are some special commands which can be used within macro-sripts:
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
<b> SICSbounds var newval </b> checks if the new value newval lies within the limits for varaible var. Returns an error or OK depending on the result of the test.</p>
|
||||
<b> SICSbounds <i>var newval</i> </b> checks if the new value newval lies within the limits for variable var(example: SICSbounds D1HL 10). Returns an error or OK depending on the result of the test.</p>
|
||||
<p>
|
||||
<b> SICSStatus var </b> SICS devices such as counters or motor may be
|
||||
<b> SICSStatus <i>var</i> </b> SICS devices such as counters or motor may be
|
||||
started and left running while the program is free to do something
|
||||
else. This command inquires the status of such a running device. Return values are internal SICS integer codes. This command is only of use for SICS programmers.</p>
|
||||
<p>
|
||||
<b> SetStatus newval </b> sets the SICS status to one of: Eager, UserWait, Count, NoBeam, Driving, Running, Scanning, Batch Hatl or Dead. This command is only available in macros.</p>
|
||||
<b> SetStatus <i>newval</i> </b> sets the SICS status to one of: Eager, UserWait, Count, NoBeam, Driving, Running, Scanning, Batch Hatl or Dead. This command is only available in macros.</p>
|
||||
<p>
|
||||
<b> SetInt newval, GetInt </b> sets SICS interrupts from macro scripts. Not recommended! Possible return values or new values are: continue, abortop, abortscan, abortbatch, halt, free, end. This command is only permitted in macros. Should only be used by SICS programmers.</p>
|
||||
<b> SetInt <i>newval, GetInt</i> </b> sets SICS interrupts from macro scripts. Not recommended! Possible return values or new values are: continue, abortop, abortscan, abortbatch, halt, free, end. This command is only permitted in macros. Should only be used by SICS programmers.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
||||
@ -6,16 +6,28 @@
|
||||
<h1>SICS motor handling</h1>
|
||||
<hr size=4 width="66%">
|
||||
<p>
|
||||
In SICS each motor is an object with a name. Motors may take commands which basically come in the form <i> motorname command </i>. Most of these commands deal with the plethora of parameters which are associated with each motor. The syntax for manipulating variables is, again, simple. <i> Motorname parametername </i> will print the current value of the variable. <i> Motorname parametername newval </i> will set the parameter to the new value specified. A list of all parameters and their meanings is given below. The general principle behind this is that the actual (hardware) motor is kept as stupid as possible and all the intracacies of motor control are dealt with in software. Besides the parameter commands any motor understands these basic commands:<ul>
|
||||
<li> <b> Motorname list </b> gives a listing of all motor parameters.
|
||||
<li> <b> Motorname reset </b> resets the motor parameters to default values.
|
||||
In SICS each motor is an object with a name. Motors may take commands which basically come in the form
|
||||
<p>
|
||||
<i> motorname command </i>; example: D2HR list.
|
||||
<p>
|
||||
Most of these commands deal with the plethora of parameters which are associated with each motor. The syntax for manipulating variables is, again, simple.
|
||||
<p>
|
||||
<i> Motorname parametername </i>
|
||||
<p>
|
||||
will print the current value of the variable.
|
||||
<p>
|
||||
<i> Motorname parametername newval </i>
|
||||
<p>
|
||||
will set the parameter to the new value specified. A list of all parameters and their meanings is given below. The general principle behind this is that the actual (hardware) motor is kept as stupid as possible and all the intracacies of motor control are dealt with in software. Besides the parameter commands any motor understands these basic commands:<ul>
|
||||
<li> <b> <i>Motorname list</i> </b> gives a listing of all motor parameters.
|
||||
<li> <b> <i>Motorname</i> reset </b> resets the motor parameters to default values.
|
||||
This is software zero to 0.0 and software limits are reset to hardware
|
||||
limits.
|
||||
<li> <b> Motorname position</b> prints the current position of the motor.
|
||||
<li> <b> <i>Motorname</i> position</b> prints the current position of the motor.
|
||||
All zero point and sign corrections are applied.
|
||||
<li> <b> Motorname hardposition</b> prints the current position of the motor.
|
||||
<li> <b> <i>Motorname</i> hardposition</b> prints the current position of the motor.
|
||||
No corrections are applied. Should read the same as the controller box.
|
||||
<li><b> Motorname interest</b> initiates automatic printing of any position
|
||||
<li><b> <i>Motorname</i> interest</b> initiates automatic printing of any position
|
||||
change of the motor. This command is mainly interesting for implementors of
|
||||
status display clients.
|
||||
</ul>
|
||||
|
||||
@ -104,15 +104,17 @@ invoke the apropriate command to start the server. These are:
|
||||
<DT>SANS
|
||||
<DD>Computer = lnsa10,User = SANS
|
||||
<DT>TRICS
|
||||
<DD>Computer = lnsa13, User = TRICS
|
||||
<DD>Computer = lnsa18, User = TRICS
|
||||
<DT>HRPT
|
||||
<DD>Computer = lnsa11, User = HRPT
|
||||
<DT>FOCUS
|
||||
<DD>Computer = lnsa12, User = FOCUS
|
||||
<DD>Computer = lnsa16, User = FOCUS
|
||||
<DT>AMOR
|
||||
<DD>Computer = lnsa14, User = AMOR
|
||||
<DT>DRUECHAL
|
||||
<DD>Computer = lnsa16, User = DRUECHAL
|
||||
<DT>TASP
|
||||
<DD>Computer = lnsa12, User = TASP
|
||||
<DT>POLDI
|
||||
<DD>Computer = pc2970, User = POLDI
|
||||
</dl>
|
||||
For starting the SICS server type <b>startsics</b>. This is a shell script
|
||||
which will starts all necessary server programs. This script works only on
|
||||
|
||||
@ -5,13 +5,13 @@
|
||||
<body>
|
||||
<h2>System Commands</h2>
|
||||
<p>
|
||||
<b> Sics_Exitus </b>. A single word commands which shuts the server down. Only Managers may use this command.</p>
|
||||
<b> sics_exitus </b>. A single word commands which shuts the server down. Only managers may use this command.</p>
|
||||
<p>
|
||||
<b> wait time </b> waits time seconds before the next command is executed. This does not stop other clients from issuing commands.</p>
|
||||
<b> wait <i>time</i> </b> waits time seconds before the next command is executed. This does not stop other clients from issuing commands.</p>
|
||||
<p>
|
||||
<b> ResetServer </b> resets the server after an interrupt.</p>
|
||||
<b> resetserver </b> resets the server after an interrupt.</p>
|
||||
<p>
|
||||
<b> Dir </b> a single word command which lists all objects available in the SICS system in its current configuration.</p>
|
||||
<b> dir </b> a single word command which lists all objects available in the SICS system in its current configuration.</p>
|
||||
<p>
|
||||
<b> status </b> A single word command which makes SICS print its current
|
||||
status. Possible return values can be:
|
||||
@ -24,7 +24,7 @@ server. This command is primarily of interest for status display client
|
||||
implementors.
|
||||
</p>
|
||||
<p>
|
||||
<b>backup file</b> saves the current values of SICS variables and selected
|
||||
<b>backup <i>[file]</i></b> saves the current values of SICS variables and selected
|
||||
motor and device parameters to the disk file specified as
|
||||
parameter. If no file parameter is given the data is written to the
|
||||
system default status backup file.
|
||||
@ -34,13 +34,13 @@ implementors.
|
||||
path of the SICS server. This is usually /home/INSTRUMENT/bin.
|
||||
</p>
|
||||
<p>
|
||||
<b>backup motSave</b> toggles a flag which controls saving of motor
|
||||
<b>backup motsave</b> toggles a flag which controls saving of motor
|
||||
positions. If this flag is set, commands for driving motors to the
|
||||
current positions are included in the backup file. This is useful
|
||||
for instruments with slipping motors.
|
||||
</p>
|
||||
<p>
|
||||
<b>restore file</b> reads a file produced by the backup command described
|
||||
<b>restore <i>[file]</i></b> reads a file produced by the backup command described
|
||||
above and restores SICS to the state it was in when the status was saved with
|
||||
backup. If no file argument is given the system default file gets
|
||||
read.
|
||||
|
||||
@ -3,7 +3,6 @@
|
||||
<title>The Scan Command </title>
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<h1>The Scan Command </h1>
|
||||
<hr size=4 width="66%">
|
||||
<p>
|
||||
@ -13,7 +12,7 @@ into equidistant steps. The instrument then proceeds to drive to each
|
||||
of these points and collects data at each of them.
|
||||
</p>
|
||||
<p>
|
||||
The general idea of the scan object for TOPSI is, that you configure the
|
||||
The general idea of the scan object is, that you configure the
|
||||
scan by typing commands at the command line. Once, the configuration is
|
||||
finished the requested scan is started. A data file will be written
|
||||
automatically to the default location. The scan command can not only scan
|
||||
@ -25,24 +24,24 @@ The syntax of the scan command in some detail:
|
||||
<DD> Clears current scan parameters.
|
||||
<DT>scan list
|
||||
<DD> lists current scan parameters.
|
||||
<DT> scan var name start step
|
||||
<DD> Defines a variable (motor) to be scanned. The name of the variable, a
|
||||
start value and a stpe width need to be given. More then one scan variable
|
||||
<DT> scan var <i>name start step</i>
|
||||
<DD> Defines a parameter (motor) to be scanned. The name of the parameter, a
|
||||
start value and a step width need to be given. More then one scan variable
|
||||
can be specified.
|
||||
<DT> scan modvar name start step
|
||||
<DT> scan modvar <i>name start step</i>
|
||||
<DD> Modifies the scan parameters for scan variable name to the new values
|
||||
given.
|
||||
<DT>scan getvars
|
||||
<DD> Returns a list of currently active scan variables terminated with the
|
||||
string -END-.
|
||||
<DT> scan NP num
|
||||
<DT> scan np <i>num</i>
|
||||
<DD> Sets the number of scan points.
|
||||
<DT> scan Preset val
|
||||
<DT> scan preset <i>[val]</i>
|
||||
<DD> Sets the Preset value for the scan. Without a parameter, inquires the
|
||||
current value.
|
||||
<DT> scan Mode val
|
||||
<DT> scan mode <i>[val]</i>
|
||||
<DD> Sets the count mode for the scan. Without a parameter, inquires the
|
||||
current value. Possible values are Timer or Monitor.
|
||||
current value. Possible values are <i>timer</i> or <i>monitor</i>.
|
||||
<DT> scan run
|
||||
<DD> Executes the scan.
|
||||
<DT>scan cinterest
|
||||
@ -55,13 +54,11 @@ ScanVarChange) to you whenever the scan variables get modified. This command
|
||||
is primarily of interest for status display clients.
|
||||
</DL>
|
||||
</p>
|
||||
|
||||
<h2> Center Scan </h2>
|
||||
<h2>Center Scan </h2>
|
||||
<p>
|
||||
Center scan is a convenience command which starts a scan around a specified
|
||||
center value. This mostly used for centering purposes. The syntax is like this:
|
||||
<BLOCKQUOTE>
|
||||
cscan var center delta np preset
|
||||
center value. This mostly used for centering purposes. The syntax is like this:<BLOCKQUOTE>
|
||||
<b>cscan</b> <i>var center delta np preset</i>
|
||||
</BLOCKQUOTE>
|
||||
All parameters must be specified. The parameters and their meanings:
|
||||
<UL>
|
||||
@ -73,14 +70,16 @@ Only one can be specified.
|
||||
<LI><b>preset</b> is the preset to use for the counter. As the counter mode,
|
||||
the mode currently configured active in the scan object is used.
|
||||
</UL>
|
||||
<BLOCKQUOTE>
|
||||
example: <b>cscan</b> <i>d2hr 0.5 0.01 10 10000</i>
|
||||
</BLOCKQUOTE>
|
||||
</p>
|
||||
|
||||
<h2> Simple Scan </h2>
|
||||
<h2>Simple Scan </h2>
|
||||
<p>
|
||||
Simple scan is a convenience command which starts a scan for one to several
|
||||
variables with a simplified syntax. The syntax is like this:
|
||||
<BLOCKQUOTE>
|
||||
sscan var1 start end var2 start end ... np preset
|
||||
sscan <i>var1 start end var2 start end ... np preset</i>
|
||||
</BLOCKQUOTE>
|
||||
All parameters must be specified. The parameters and their meanings:
|
||||
<UL>
|
||||
|
||||
Reference in New Issue
Block a user