linse/sics
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

aktualisierte Hardware(terminal server), kursive bzw. fett gedruckte Schreibweise

Browse Source 
Beispiele
This commit is contained in:
cvs
2002-07-10 11:15:07 +00:00
parent d57cd3af50
commit ee143c691c
12 changed files with 117 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
doc/user/buffer.htm
View File

@ -19,30 +19,30 @@
three commands have been defined:</p> three commands have been defined:</p>
<p> <p>
The <b> Buf </b> object is responsible for creating and deleting R&#252;nbuffers. The syntax is:<ul> The <b> Buf </b> object is responsible for creating and deleting R&#252;nbuffers. The syntax is:<ul>
<li> <b> Buf new name </b> creates a new empty R&#252;nbuffer with the name name. name will be installed as a SICS object afterwards. <li> <b> Buf new <i>name</i> </b> creates a new empty R&#252;nbuffer with the name name. name will be installed as a SICS object afterwards.
<li> <b> Buf copy name1 name2 </b> copies R&#252;nbuffer name1 to buffer name2. <li> <b> Buf copy <i>name1 name2</i> </b> copies R&#252;nbuffer name1 to buffer name2.
<li> <b> Buf del name </b> deletes the R&#252;nbuffer name. <li> <b> Buf del <i>name</i> </b> deletes the R&#252;nbuffer name.
</ul> </ul>
</p> </p>
<p> <p>
After creation, the R&#252;nbuffer is accessible by his name. It After creation, the R&#252;nbuffer is accessible by his name. It
then understands the commands:<ul> 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&#252;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&#252;nbuffer.
<li> <b> NAME print </b> will list the contents of the R&#252;nbuffer. <li> <b> <i>NAME</i> print </b> will list the contents of the R&#252;nbuffer.
<li> <b> NAME del iLine </b> will delete line number iLine from the R&#252;nbuffer. <li> <b> <i>NAME</i> del <i>iLine</i> </b> will delete line number iLine from the R&#252;nbuffer.
<li> <b> NAME ins iLine BimBamBim </b> inserts a new line <b> after </b> line iLine into the R&#252;nbuffer. The line will consist of everything given after the iLine. <li> <b> <i>NAME</i> ins <i>iLine BimBamBim</i> </b> inserts a new line <b> after </b> line iLine into the R&#252;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&#252;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> subst pattern <i>newval</i> </b> replaces all occurences of pattern in the R&#252;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&#252;nbuffer into file filename. <li> <b> <i>NAME</i> save <i>filename</i> </b> saves the contents of the R&#252;nbuffer into file filename.
<li> <b> NAME load filename </b> loads the R&#252;nbuffer with the data in file filename. <li> <b> <i>NAME</i> load <i>filename</i> </b> loads the R&#252;nbuffer with the data in file filename.
<li> <b> NAME run </b> executes the R&#252;nbuffer. <li> <b> <i>NAME</i> run </b> executes the R&#252;nbuffer.
</ul> </ul>
</p> </p>
<p> <p>
The R&#252;nlist is accessible as object <b> stack </b>. Only one R&#252;nlist per server is permitted. The syntax:<ul> The R&#252;nlist is accessible as object <b> stack </b>. Only one R&#252;nlist per server is permitted. The syntax:<ul>
<li> <b> stack add name </b> adds R&#252;nbuffer name to the top of the stack. <li> <b> stack add <i>NAME</i> </b> adds R&#252;nbuffer name to the top of the stack.
<li> <b> stack list </b> lists the current R&#252;nlist. <li> <b> stack list </b> lists the current R&#252;nlist.
<li> <b> stack del iLine </b> deletes the R&#252;nbuffer iLine from the R&#252;nlist. <li> <b> stack del <i>iLine</i> </b> deletes the R&#252;nbuffer iLine from the R&#252;nlist.
<li> <b> stack ins iLine name </b> inserts R&#252;nbuffer name after R&#252;nbuffer number iLine into the R&#252;nlist. <li> <b> stack ins <i>iLine NAME</i> </b> inserts R&#252;nbuffer name after R&#252;nbuffer number iLine into the R&#252;nlist.
<li> <b> stack run </b> executes the R&#252;nlist and returns when all R&#252;nbuffers are done. <li> <b> stack run </b> executes the R&#252;nlist and returns when all R&#252;nbuffers are done.
<li> <b> stack batch </b> executes the R&#252;nlist but does not return when done but waits for further R&#252;nbuffers to be added to the list. This feature allows a sort of background process in the server. <li> <b> stack batch </b> executes the R&#252;nlist but does not return when done but waits for further R&#252;nbuffers to be added to the list. This feature allows a sort of background process in the server.
</ul> </ul>

4
doc/user/commandlog.htm
View File

@ -12,7 +12,7 @@ file or can be
configured by the instrument manager. There exists a special command, configured by the instrument manager. There exists a special command,
commandlog, which allows to control this log file. commandlog, which allows to control this log file.
<DL> <DL>
<DT>commandlog new filename <DT>commandlog new <i>filename</i>
<DD>starts a new commandlog writing to filename. Any prior files will be <DD>starts a new commandlog writing to filename. Any prior files will be
closed. The log file can be found closed. The log file can be found
in the directory specified by the ServerOption LogFileDir. Usually this is 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. <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 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. 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. <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> </DL>
It is now possible to have a script executed whenever a new log file is It is now possible to have a script executed whenever a new log file is

21
doc/user/count.htm
View File

@ -3,19 +3,18 @@
<title>Counting Commands</title> <title>Counting Commands</title>
</head> </head>
<body> <body>
<h1>Counting Commands.</h1> <h1>Counting Commands</h1>
<P> <dl>
<DL> <DT>count <i>[mode preset]</i>
<DT>count mode preset <DD> Does a count operation in mode with a given preset.
<DD> Does a count operation in mode with a preset of preset. <i>Mode</i> can be <i>timer</i> or <i>monitor</i>.
The parameters are optional. If they are not The parameters mode and preset are optional. If they
given the count will be started with the current setting in the histogram are not given the count will be started with the
memory object. After the count, StoreData will be automatically called. current setting in the histogram memory object.
<DT> Repeat num mode preset. <DT> repeat num mode preset.
<DD> Calls count num times. num is a required parameter. The other two are <DD> Calls count num times. num is a required parameter. The other two are
optional and are handled as described above for count. optional and are handled as described above for count.
</DL> </dl>
Both commands make sure, that measured data is written to files. Both commands make sure, that measured data is written to files.
</p>
</body> </body>
</html> </html>

33
doc/user/counter.htm
View File

@ -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 Again, in SICS the counter is an object which understands a set of
commands: commands:
<ul> <ul>
<li> <b> countername SetPreset val </b> sets the counting preset to val. <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 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 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 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. 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. 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 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 getmode </b> prints the current mode.
<li> <b> countername mode val</b> With a parameter sets the 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 without inquires the mode value. This is a duplicate of getmode and
setmode which has been provided for consistency with other setmode which has been provided for consistency with other
commands. Possible values for val are either monitor or timer. 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. preset in monitor mode to val.
<li> <b> countername GetCounts </b> prints the counts gathered in the last run. <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 getmonitor <i>n</i> </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 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 <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 current monitor or time value. Can be used to monitor the progress of
the counting operation. the counting operation.
<li> <b> countername gettime </b> Retrieves the actual time the counter <li> <b> countername gettime </b> Retrieves the actual time the counter
counted for. This excludes time where there was no beam or counting was counted for. This excludes time where there was no beam or counting was
paused. paused.
<li><b>countername getthreshold m</b> retrieves the value of the threshold <li><b>countername getthreshold <i>m</i></b> retrieves the value of the threshold set for the monitor number m.
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
<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
monitor to use as control monitor in monitor mode, it allows to choose 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 the monitor used for pausing the count when the count rate is below the
threshold (Who on earth designed this?) 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 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 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 for the counter box elsewhere. Through this feature it is possible to

17
doc/user/ctrl.htm
View File

@ -5,22 +5,17 @@
<BODY> <BODY>
<H1>Serial Port Direct Access</H1> <H1>Serial Port Direct Access</H1>
<P> <P>
At SINQ serial devices are connected to a Macintosh computer. This Mac runs 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.
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.
</p> </p>
<H2>Invocation</H2> <H2>Invocation</H2>
<P> <P>
The interface to a serial device connected to a Mac is initialised with the The interface to a serial device connected to a UNIX/LINUX computer is initialised with the following command given at the Tcl prompt:<BR>
following command given at the Tcl prompt:<BR>
<EM>Controller name computer port channel</EM><BR> <EM>Controller name computer port channel</EM><BR>
This command opens a connection to the serial port on the Mac and 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:
installs a new command in order to interact with it. The parameters:
<UL> <UL>
<LI>name: is the name of the new command to generate for the connection in Tcl. <LI><b>name</b> is the name of the new command to generate for the connection in Tcl.
<LI> computer: is the computer name of the Macintosh. <LI> <b>computer</b> is the computer name of the UNIX/LINUX machine.
<LI> port: is the TCP/IP port number at which the Macintosh <LI> port: is the TCP/IP port number at which the UNIX/LINUX machine
serial port server is is listening. Usually this is 4000. serial port server is is listening. Usually this is 4000.
<LI>channel: is the number of the RS-232 port to connect to. <LI>channel: is the number of the RS-232 port to connect to.
</UL> </UL>

26
doc/user/histogram.htm
View File

@ -31,7 +31,6 @@ 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 continued until the monitor has reached 25 million. Note, that this scheme with
the exponent is only in operation in Monitor mode. the exponent is only in operation in Monitor mode.
</p> </p>
<h2>Configuration</h2> <h2>Configuration</h2>
<p> <p>
A HM has a plethora of configuration options coming with it which define A HM has a plethora of configuration options coming with it which define
@ -93,10 +92,10 @@ modifying time bins is restricted to instrument managers.
<DL> <DL>
<DT>HM timebin <DT>HM timebin
<DD> Prints the currently active time binning array. <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 <DD>Generates a new equally spaced time binning array. Number n time bins
will be generated starting from start with a stepwidth of step. will be generated starting from start with a stepwidth of step (example: HM genbin 10 1 5).
<DT>HM setbin inum value <DT>HM setbin <i>inum value</i>
<DD>Sometimes unequally spaced time binnings are needed. These can be <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. configured with this command. The time bin iNum is set to the value value.
<DT>HM clearbin <DT>HM clearbin
@ -109,18 +108,15 @@ configured with this command. The time bin iNum is set to the value value.
Besides the configuration commands the HM understands the following Besides the configuration commands the HM understands the following
commands: commands:
<DL> <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 <DD> with a new value sets the preset time or monitor for counting. Without a
value prints the current value. 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 <DD> with a new value sets the exponent to use for the preset time
in Monitor mode. Without a in Monitor mode. Without a
value prints the current value. value prints the current value.
<DT>CountMode <DT>CountMode <i>[mode]</i>
<DD> with a new values sets the count mode. Possible values are Timer for a <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.
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 <DT>HM init
<DD> after giving configuration commands this 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. transfer the configuration from the host computer to the actual HM.
@ -128,14 +124,14 @@ transfer the configuration from the host computer to the actual HM.
<DD> starts counting using the currently active values for CountMode and <DD> starts counting using the currently active values for CountMode and
preset. This command does not block, i.e. in order to inhibit further preset. This command does not block, i.e. in order to inhibit further
commands from the console, you have to give Success afterwards. 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 <DD> initialises the whole histogram memory to the value val. Ususally 0 in
order to clear the HM. 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 <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. 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 <DD>calculates the sum of an area on the detector. For each dimension a
minimum and maximum boundary for summing must be given. minimum and maximum boundary for summing must be given.
</DL> </DL>

7
doc/user/logbook.htm
View File

@ -13,10 +13,9 @@ LogBook understands the following syntax:
<DT> LogBook <DT> LogBook
<DD> alone prints the name of the current logfile and the status of event <DD> alone prints the name of the current logfile and the status of event
logging. logging.
<DT> LogBook file filename <DT> LogBook file <i>filename</i>
<DD> This command sets the filename to which output will be printed. <DD>sets the filename to which output will be printed. Please note
Please note that this new filename will only be in effect after restarting that this new filename will only be in effect after restarting logging.
logging.
<DT> LogBook on <DT> LogBook on
<DD> This command turns logging on. All commands and all answers will be <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, written to the file defined with the command described above. Please note,

10
doc/user/macro.htm
View File

@ -7,7 +7,7 @@
<p> <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> 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> <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: Then there are some special commands which can be used within macro-sripts:
<p> <p>
<b> ClientPut sometext1 ... </b> writes everything after ClientPut to <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> </ul>
</p> </p>
<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> <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 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> 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> <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> <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> </body>
</html> </html>

24
doc/user/motor.htm
View File

@ -6,16 +6,28 @@
<h1>SICS motor handling</h1> <h1>SICS motor handling</h1>
<hr size=4 width="66%"> <hr size=4 width="66%">
<p> <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> In SICS each motor is an object with a name. Motors may take commands which basically come in the form
<li> <b> Motorname list </b> gives a listing of all motor parameters. <p>
<li> <b> Motorname reset </b> resets the motor parameters to default values. <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 This is software zero to 0.0 and software limits are reset to hardware
limits. 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. 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. 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 change of the motor. This command is mainly interesting for implementors of
status display clients. status display clients.
</ul> </ul>

10
doc/user/sicsinvoc.htm
View File

@ -104,15 +104,17 @@ invoke the apropriate command to start the server. These are:
<DT>SANS <DT>SANS
<DD>Computer = lnsa10,User = SANS <DD>Computer = lnsa10,User = SANS
<DT>TRICS <DT>TRICS
<DD>Computer = lnsa13, User = TRICS <DD>Computer = lnsa18, User = TRICS
<DT>HRPT <DT>HRPT
<DD>Computer = lnsa11, User = HRPT <DD>Computer = lnsa11, User = HRPT
<DT>FOCUS <DT>FOCUS
<DD>Computer = lnsa12, User = FOCUS <DD>Computer = lnsa16, User = FOCUS
<DT>AMOR <DT>AMOR
<DD>Computer = lnsa14, User = AMOR <DD>Computer = lnsa14, User = AMOR
<DT>DRUECHAL <DT>TASP
<DD>Computer = lnsa16, User = DRUECHAL <DD>Computer = lnsa12, User = TASP
<DT>POLDI
<DD>Computer = pc2970, User = POLDI
</dl> </dl>
For starting the SICS server type <b>startsics</b>. This is a shell script 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 which will starts all necessary server programs. This script works only on

14
doc/user/system.htm
View File

@ -5,13 +5,13 @@
<body> <body>
<h2>System Commands</h2> <h2>System Commands</h2>
<p> <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> <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> <p>
<b> ResetServer </b> resets the server after an interrupt.</p> <b> resetserver </b> resets the server after an interrupt.</p>
<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> <p>
<b> status </b> A single word command which makes SICS print its current <b> status </b> A single word command which makes SICS print its current
status. Possible return values can be: status. Possible return values can be:
@ -24,7 +24,7 @@ server. This command is primarily of interest for status display client
implementors. implementors.
</p> </p>
<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 motor and device parameters to the disk file specified as
parameter. If no file parameter is given the data is written to the parameter. If no file parameter is given the data is written to the
system default status backup file. system default status backup file.
@ -34,13 +34,13 @@ implementors.
path of the SICS server. This is usually /home/INSTRUMENT/bin. path of the SICS server. This is usually /home/INSTRUMENT/bin.
</p> </p>
<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 positions. If this flag is set, commands for driving motors to the
current positions are included in the backup file. This is useful current positions are included in the backup file. This is useful
for instruments with slipping motors. for instruments with slipping motors.
</p> </p>
<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 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 backup. If no file argument is given the system default file gets
read. read.

31
doc/user/topscan.htm
View File

@ -3,7 +3,6 @@
<title>The Scan Command </title> <title>The Scan Command </title>
</head> </head>
<body> <body>
<h1>The Scan Command </h1> <h1>The Scan Command </h1>
<hr size=4 width="66%"> <hr size=4 width="66%">
<p> <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. of these points and collects data at each of them.
</p> </p>
<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 scan by typing commands at the command line. Once, the configuration is
finished the requested scan is started. A data file will be written finished the requested scan is started. A data file will be written
automatically to the default location. The scan command can not only scan 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. <DD> Clears current scan parameters.
<DT>scan list <DT>scan list
<DD> lists current scan parameters. <DD> lists current scan parameters.
<DT> scan var name start step <DT> scan var <i>name start step</i>
<DD> Defines a variable (motor) to be scanned. The name of the variable, a <DD> Defines a parameter (motor) to be scanned. The name of the parameter, a
start value and a stpe width need to be given. More then one scan variable start value and a step width need to be given. More then one scan variable
can be specified. 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 <DD> Modifies the scan parameters for scan variable name to the new values
given. given.
<DT>scan getvars <DT>scan getvars
<DD> Returns a list of currently active scan variables terminated with the <DD> Returns a list of currently active scan variables terminated with the
string -END-. string -END-.
<DT> scan NP num <DT> scan np <i>num</i>
<DD> Sets the number of scan points. <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 <DD> Sets the Preset value for the scan. Without a parameter, inquires the
current value. 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 <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 <DT> scan run
<DD> Executes the scan. <DD> Executes the scan.
<DT>scan cinterest <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. is primarily of interest for status display clients.
</DL> </DL>
</p> </p>
<h2>Center Scan </h2> <h2>Center Scan </h2>
<p> <p>
Center scan is a convenience command which starts a scan around a specified 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: center value. This mostly used for centering purposes. The syntax is like this:<BLOCKQUOTE>
<BLOCKQUOTE> <b>cscan</b> <i>var center delta np preset</i>
cscan var center delta np preset
</BLOCKQUOTE> </BLOCKQUOTE>
All parameters must be specified. The parameters and their meanings: All parameters must be specified. The parameters and their meanings:
<UL> <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, <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. the mode currently configured active in the scan object is used.
</UL> </UL>
<BLOCKQUOTE>
example: <b>cscan</b> <i>d2hr 0.5 0.01 10 10000</i>
</BLOCKQUOTE>
</p> </p>
<h2>Simple Scan </h2> <h2>Simple Scan </h2>
<p> <p>
Simple scan is a convenience command which starts a scan for one to several Simple scan is a convenience command which starts a scan for one to several
variables with a simplified syntax. The syntax is like this: variables with a simplified syntax. The syntax is like this:
<BLOCKQUOTE> <BLOCKQUOTE>
sscan var1 start end var2 start end ... np preset sscan <i>var1 start end var2 start end ... np preset</i>
</BLOCKQUOTE> </BLOCKQUOTE>
All parameters must be specified. The parameters and their meanings: All parameters must be specified. The parameters and their meanings:
<UL> <UL>