cbcd98c10c
This directory was accidentally omitted from the merge-release branch during the PSI code merge.
958 lines
50 KiB
XML
958 lines
50 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
||
<?oxygen RNGSchema="http://www.oasis-open.org/docbook/xml/5.0/rng/docbook.rng" type="xml"?>
|
||
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink"
|
||
version="5.0">
|
||
<info><title>Taipan User Guide - deprecated to db5SICSUserGuideTaipan.xml</title><author>
|
||
<personname>Kirrily Rule</personname>
|
||
</author>
|
||
<date>2013-04-09 16:47</date>
|
||
</info>
|
||
<sect1>
|
||
<title>Quick start guide</title>
|
||
<para>To start running Gumtree, double click on the icon on the desktop. Two windows will
|
||
automatically open and you will be logged in as “Manager”. (Why manager, why not
|
||
user???)</para>
|
||
<para>This quick start guide assume SICS is configured for your experiment, and that it is
|
||
running. If it is not, go to the section <xref linkend="status"/></para>
|
||
<sect2>
|
||
<title>To edit and run a batch file</title>
|
||
<figure>
|
||
<title>Script Perspective </title>
|
||
<mediaobject>
|
||
<imageobject><imagedata align="center" width="160mm" fileref="taipanGumtree.jpg"
|
||
/></imageobject>
|
||
</mediaobject>
|
||
</figure>
|
||
<para>Open one of the previous batch files by double clicking on a .tcl file in the
|
||
Project Explorer window. This will appear in the Tree View panel above. You can edit
|
||
this and save it with a new file name (File -> Save as). </para>
|
||
<para>To run this file, drag it into the Buffer Queue. You can either press Play, or
|
||
Validate to check the file. </para>
|
||
<para>All commands listed with <emphasis>>
|
||
</emphasis> should be typed into the SICS command line in Gumtree, or in the black
|
||
sicsclient window opened via PuTTy (Taipan ICS profile). Either of these will drive
|
||
the instrument. Only those commands executed from Gumtree will be printed into the
|
||
Log file. </para>
|
||
</sect2>
|
||
<sect2>
|
||
<title> Live visualisation of data</title>
|
||
<figure>
|
||
<title>Analysis Perspective </title>
|
||
<mediaobject>
|
||
<imageobject><imagedata align="center" width="160mm"
|
||
fileref="taipanGumtree1.jpg"/></imageobject>
|
||
</mediaobject>
|
||
</figure>
|
||
<para>In the Scripting control window, choose </para>
|
||
<para><command>Load Script -> analysis -> live data</command> to show a live plot as the
|
||
counts are taken. </para>
|
||
<para>In this window, you can tick (or untick) autofit (for a Gaussian fit), and
|
||
normalise (which normalises to time) You can also change which detector you wish to
|
||
see the counts in:</para>
|
||
<para>bm1_counts = monitor </para>
|
||
<para>bm2_counts = detector </para>
|
||
<para>You can also control the fitting range in this window </para>
|
||
<para>You can add past data sets to the Plot 2 window (beneath the liveplot window).
|
||
Highlight the plots you wish to add, be sure you have the correct detector choice
|
||
and x-axis parameter selected, then click on the button “Import Data Files to
|
||
Plot2”. These can also be removed for the plot. There is currently no fitting
|
||
procedure for Plot2. </para>
|
||
<note>
|
||
<para>At any time, to interrupt SICS you can click on the red button, or type
|
||
>>INT1712 3</para>
|
||
</note>
|
||
</sect2>
|
||
</sect1>
|
||
<sect1 xml:id="status">
|
||
<title>SICS status and login</title>
|
||
<para>Before you can control the instrument, there are 2 programs that need to be running,
|
||
SICS and Gumtree. SICS should already be configured and running by the local contact.
|
||
This procedure allows you to check this.</para>
|
||
<sect2>
|
||
<title>Login to the SICS computer from a PuTTy terminal</title>
|
||
<orderedlist>
|
||
<listitem>
|
||
<para>On the Microsoft Windows computer in the instrument cabin, find the putty
|
||
program. <figure>
|
||
<title>PuTTy icon on the Microsoft Windows desktop </title>
|
||
<mediaobject>
|
||
<imageobject><imagedata align="left" width="30mm"
|
||
fileref="putty.jpg"/></imageobject>
|
||
</mediaobject>
|
||
</figure></para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Choose the ICS computer from the list of Saved Sessions</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Load and open</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Use your NBI username and password, supplied by the Bragg Institute User
|
||
Office</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>You will now have a command prompt to a Linux operating system</para>
|
||
</listitem>
|
||
</orderedlist>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Check SICS status</title>
|
||
<para>Normally SICS will be running. You can check if SICS is running by using the PuTTy
|
||
window and at the Linux operating system command prompt type</para>
|
||
<para><command>> runsics status</command>
|
||
</para>
|
||
<para>If the status shows that SICS is not running, or if there is a change in the SICS
|
||
configuration files e.g. a piece of sample environment has been added, you should
|
||
contact your local contact. </para>
|
||
<para>If the local contact has confirmed it is OK to restart SICS, then in the PuTTy
|
||
window type </para>
|
||
<para><command>> runsics stop</command>
|
||
</para>
|
||
<para><command>> runsics start</command>
|
||
</para>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Login to SICS using the putty session</title>
|
||
<para>In the previous section, you logged into the ICS (instrument control server)
|
||
computer using putty. At the Linux operating system command prompt, you will run a
|
||
program that will give you a sics command prompt. </para>
|
||
<para>For most cases, you won't have to do this. A SICS command prompt is available in
|
||
Gumtree. </para>
|
||
<para>At the Linux operating system command prompt type </para>
|
||
<para><command>> sicsclient</command></para>
|
||
<para>You should see <computeroutput>OK</computeroutput> on the screen.</para>
|
||
<para>You now have a SICS command prompt. It may look strange since the cursor will be
|
||
on a blank line. You will not have access to the Linux operating system command
|
||
prompt until you log off.</para>
|
||
<para>Next step is to login to sics by typing</para>
|
||
<para><command>> user password</command> where user is literally the word "user" and
|
||
the password will be supplied by the local contact</para>
|
||
<para>You can replace user with spy. The spy login provides read-only access to SICS.
|
||
</para>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Login to SICS from Gumtree</title>
|
||
<figure>
|
||
<title>Gumtree connected to SICS </title>
|
||
<mediaobject>
|
||
<imageobject><imagedata align="center" width="160mm"
|
||
fileref="taipanGumtree2.jpg"/></imageobject>
|
||
</mediaobject>
|
||
</figure>
|
||
<para>Normally, Gumtree will be connected to SICS, as in the figure above. </para>
|
||
<para>In Gumtree you reconnect to SICS if you restart SICS. This is done by clicking on
|
||
the little man at the bottom of the Gumtree screen and log in to SICS. He will be
|
||
standing still, and you will see the word Disconnected when not connected. He will
|
||
be running when connected as in the figure. You will then need to start a new Sics
|
||
terminal in Gumtree. From the left screen, in the project explorer window, Right
|
||
click on SICS and choose the option to start a new “SICS telnet terminal”. </para>
|
||
<note>
|
||
<para>Reconnection won't work properly if SICS has changed configuration e.g. you've
|
||
added a piece of sample environment. In this case, when you restart SICS you
|
||
should also restart Gumtree </para>
|
||
<para/>
|
||
</note>
|
||
</sect2>
|
||
</sect1>
|
||
<sect1>
|
||
<title>Preparing the spectrometer</title>
|
||
<sect2>
|
||
<title>Aligning the spectrometer</title>
|
||
<warning>
|
||
<title>12T magnet</title>
|
||
<para> When using the 12T magnet on TAIPAN, you must work in fixed Ki mode, as the
|
||
magnet is too heavy to move M2. Consider the energy transfer range required to
|
||
determine the appropriate Ei for these experiments. </para>
|
||
</warning>
|
||
<para>After discussing your instrument preferences with your local contact, they will
|
||
align the spectrometer in the following way:</para>
|
||
<itemizedlist>
|
||
<listitem>
|
||
<para>Drive the spectrometer to the required incident energy (for elastic mode)
|
||
= e.g. 14.87meV</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Drive the analyser arm to the straight-through position (s2=0, a1=0, a2=0,
|
||
atrans=19)</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Visually check the straight-through arm and change any motors
|
||
accordingly</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Place the Ni sample on the sample stage, and Borated Al sheets over the
|
||
analyser collimator. (the detector saturates at ~35,000 counts/sec)</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Check M1 alignment with a rocking scan</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Check S2=0 alignment with a rocking scan</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Check A2=0 alignment with a rocking scan</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Remove the Al attenuator and insert collimators if they need
|
||
changing</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Perform the Ni powder calibration, using 5 peaks</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>From the least squares fitting of these peaks, update the new M1 offset,
|
||
M2 offset and S2 offset.</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>With the spectrometer at S2=-50, and atrans=0 (to view the Vanadium
|
||
incoherent peak from the Ni sample can), perform an A1 scan and an A1/A2
|
||
scan around the elastic position.</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Perform an En scan (where Ei will move if Ef is fixed). Here the FWHM of
|
||
the peak will give you the resolution of your instrument.</para>
|
||
<para/>
|
||
</listitem>
|
||
</itemizedlist>
|
||
<warning>
|
||
<title/>
|
||
<para>When driving Ei or Ef in this stage of the setup, the software calculates a
|
||
constant-Q instrument position based on the current UB matrix (usually from the
|
||
previous experiment). This will often drive S1, S2, sgu and sgl to unexpected
|
||
positions. To constrain these so that they don’t move unexpectedly, fix the
|
||
motors so they don't move. </para>
|
||
<para>Motors can be fixed (1) or unfixed (-1) and their status checked by typing the
|
||
motor name </para>
|
||
<para><command>> S1 fixed 1 (fixes S1) </command></para>
|
||
<para><command>> S1 fixed -1 (unfixes S1)</command></para>
|
||
<para>Alternatively you can drive vei which drives only the M1 and M2 motors – this
|
||
cannot be used in a scan command. </para>
|
||
<para><command>> drive vei 14.87 </command></para>
|
||
<para><command>> tasub update </command></para>
|
||
<para><command>> ei </command></para>
|
||
<para/>
|
||
</warning>
|
||
<warning>
|
||
<title/>
|
||
<para>You will often need to “home” the slits if they have been unplugged or removed
|
||
during the setup. The pa_left and pa_right slits can vary between -27 (open) and
|
||
0 (closed), while the pa_top and pa_bottom slits can vary between -200 (open)
|
||
and 0 (closed). The same limits apply for the ps_slits. </para>
|
||
<para><command>> pa_left homerun 1 </command> (this will do all of the slits)
|
||
(??? really)</para>
|
||
</warning>
|
||
<para/>
|
||
<para>Confirm the following setups for your experiment. This can be done by typing
|
||
everything except the red values below: </para>
|
||
<para><command>> tasub ss -1 </command> (Scattering sense = M+1, S-1, A+1) </para>
|
||
<para><command>> tasub ana ss 1</command> (Scattering sense = M+1, S-1, A+1) </para>
|
||
<para><command>> tasub outofplane 0</command> (Confines the scattering sense to be in
|
||
the plane) </para>
|
||
<para><command>> tasub const ki / kf / elastic</command> (Defines whether Ei or Ef
|
||
are fixed, or if both are fixed) </para>
|
||
<para/>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Aligning your sample</title>
|
||
<para> At the beginning of an experiment load the “Experimental setup” script (in the
|
||
scripts window, right screen) to list the most important configuration identifiers
|
||
for the experiment. These should appear in the header lines in your data files. For
|
||
instance, these include: </para>
|
||
<itemizedlist>
|
||
<listitem>
|
||
<para>Proposal number and title</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>User’s name, and research team present</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Local contact’s name</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Sample information including number of samples and sample environment
|
||
requirements</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Particular instrument setup features (scattering sense, collimation,
|
||
filters, slits etc)</para>
|
||
</listitem>
|
||
</itemizedlist>
|
||
<para>Next the UB matrix needs to be set. To do this, you need to input the cell
|
||
parameters and at least 2 reflections which will define your scattering plane. These
|
||
can be calculated for your system using the file
|
||
“/home/taipan/calculatedDspaceTAIPAN.xls” or something similar, such as the ICSD
|
||
website. </para>
|
||
<variablelist>
|
||
<varlistentry>
|
||
<term><command>> tasub listub</command></term>
|
||
<listitem>
|
||
<para>shows the current UB matrix, cell parameters and reference
|
||
peaks</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub cell a b c alpha beta gamma</command>
|
||
</term>
|
||
<listitem>
|
||
<para> input new lattice parameters</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub addref qh qk ql</command></term>
|
||
<listitem>
|
||
<para> adds a new reflection to the list when Taipan is at the
|
||
reflection</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub addref qh qk ql a3 a4 sgu sgl ei ef</command></term>
|
||
<listitem>
|
||
<para> adds a new reflection from a calculation</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub addauxref qh qk ql</command></term>
|
||
<listitem>
|
||
<para> adds a new reflection where S2 is calculated from the lattice
|
||
parameters only. This will also calculate the relative S1
|
||
positions</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub del num</command></term>
|
||
<listitem>
|
||
<para> deletes one of the previously stored reflections</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub listref</command></term>
|
||
<listitem>
|
||
<para> lists the reflections that have been input</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub makeub 1 2</command></term>
|
||
<listitem>
|
||
<para> calculates new UB matrix from reflections 1 and 2</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> tasub calcang qh qk ql ei ef</command></term>
|
||
<listitem>
|
||
<para> calculates reflection from UB matrix – be careful when changing
|
||
lattice parameters, as this command won’t use them! Output: M2 S1 S2 sgu
|
||
sgl A2</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
</variablelist>
|
||
<example>
|
||
<title>Sample alignment</title>
|
||
<para> For Ei = Ef = 14.87 meV</para>
|
||
<para><command>> tasub cell 5.011 5.85 10.353 90 92.4 90</command>
|
||
</para>
|
||
<para><command>> tasub calcang 1 0 0 14.87 14.87 (calculated S2 = 27.1)
|
||
</command></para>
|
||
<para><command>> tasub calcang 1 1 0 14.87 14.87 (calculated S2 = 35.9)
|
||
</command></para>
|
||
<para><command>> tasub calcang 0 2 0 14.87 14.87 (calculated S2 = 47.3)
|
||
</command></para>
|
||
<para>Drive the instrument to the calculated S2 value of a particular peak. The
|
||
other motor positions are not correctly set at this point. This will also give
|
||
you a relative s1 position between the peaks.</para>
|
||
<para>Scan S1 until you find the peak. </para>
|
||
<para><command>> bmonscan clear</command></para>
|
||
<para><command>> bmonscan add S1 -10 0.2 </command> (motor name, starting point,
|
||
step size)</para>
|
||
<para><command>> bmonscan run 60 timer 5 </command> (scans 60 points, for a time
|
||
of 5 seconds per point)</para>
|
||
<para>OR</para>
|
||
<para><command>> runscan s1 -10 0 101 time 5 </command> (motor, start, stop, #
|
||
pts, time (the mode in secs))</para>
|
||
<para>(this does not work for multiple motors yet)</para>
|
||
<para> (This step should hopefully be replaced by the differential scan, or the
|
||
rate-meter) </para>
|
||
<para>Once the peak position (S1) has been optimised, scan sgu and sgl </para>
|
||
<para><command>> runscan sgl -10 10 21 time 1 </command></para>
|
||
<para><command>> runscan sgu -10 10 21 time 1 </command></para>
|
||
<para>Once the peak has been optimised with SGU and SGL (and you are sitting at the
|
||
peak position!!) you can set this as one of your reference peaks, where the
|
||
current motor values define the peak position. </para>
|
||
<para><command>> tasub addref 1 0 0 </command></para>
|
||
<para>Calculate the values of S1 and S2 for the next peak – use the </para>
|
||
<para><command>> tasub calcang qh qk ql ei ef </command></para>
|
||
<para>command to see the relative values of S1 and S2 as calculated from the lattice
|
||
parameters!</para>
|
||
<para>
|
||
</para>
|
||
<para>Repeat for at least one other peak, preferably one orthogonal to the first. </para>
|
||
<para><command>> tasub addref 0 0 1 </command></para>
|
||
<para><command>> tasub listref </command> (to see the observed peaks in your list
|
||
(e.g. number 4 and 5)) </para>
|
||
<para><command>> tasub makeub 4 5 </command>(this used peaks 4 and 5 to calculate
|
||
the UB matrix) </para>
|
||
<para><command>> tasub update </command></para>
|
||
<para><command>> tasub listub </command></para>
|
||
<para>Once this has been set, then you should be able to drive your spectrometer to
|
||
any accessible qh, qk, ql and en.</para>
|
||
<warning>
|
||
<title>
|
||
</title>
|
||
<para>At the end of each change, be sure to type <command>> tasub
|
||
update</command></para>
|
||
</warning>
|
||
</example>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Reducing background with a slit scan</title>
|
||
<para>Once your sample has been aligned, add the PG filter to the instrument. You could
|
||
test the effectiveness of the filter by scanning a peak that will display higher
|
||
order scattering – e.g. (½ 0 0) which does not exist except from higher order
|
||
scattering from the (1 0 0 ). Sometimes you might want to add an additional filter.
|
||
Finally you can scan your slits to reduce the background scattering. </para>
|
||
<para><command>> runscan pa_left -15 -2 27 time 1 </command>(scans 27 points, for a
|
||
time of 1 seconds per point)</para>
|
||
<para> After this, consider if you need to add more shielding to the detector drum or
|
||
any other part of the instrument (e.g. manual slits on analyser arm, additional PG
|
||
filters).</para>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Setting the (new) lattice parameters</title>
|
||
<para>When the sample temperature has stabilized at the required temperature, the low
|
||
temperature lattice parameters can be checked. For example, a tetragonal system in
|
||
the ab-scattering plane can be optimized as follows: </para>
|
||
<para><command>> drive qh 5 qk 0 ql 0 en 0 </command></para>
|
||
<para><command>> runscan qh 4.985 5.015 31 time 5 </command></para>
|
||
<para>The centre of this scan should be close to 5, but could be shifted. This will be
|
||
the fit value from the scan. Then you can <emphasis role="underline">change the
|
||
<emphasis role="bold">a</emphasis> lattice parameter</emphasis> accordingly
|
||
in tasub </para>
|
||
<para>
|
||
a<subscript>new</subscript>=a<subscript>old</subscript>(peak<subscript>calculated</subscript>/peak<subscript>centre
|
||
from scan</subscript>) replace with jpg of equation??? MathML doesn't transform
|
||
to pdf using oxygen xslt. </para>
|
||
<para><command>> tasub cell a b c alpha beta gamma </command></para>
|
||
<para>The next peak can be aligned in the same way </para>
|
||
<para><command>> drive qh 0 qk 3 ql 0 en 0 </command></para>
|
||
<para><command>> runscan qk 2.985 3.015 31 time 5 </command></para>
|
||
<para>Find the centre of this scan then you can <emphasis role="underline">change the
|
||
<emphasis role="bold">b</emphasis> lattice parameter</emphasis> accordingly
|
||
in tasub. Also, while sitting on the peak, perform the </para>
|
||
<para><command>> tasub addref 0 3 0 </command></para>
|
||
<para>If your sample is cubic (and remains cubic at low temperatures) and you are in the
|
||
HK0 scattering plane, then the lattice parameters are best set with a peak that
|
||
involved both H and K – for instance the 110 peak.</para>
|
||
<para>Make sure after you have changed your lattice parameters, and both peaks have been
|
||
added to the reference list that you remake your ub matrix! </para>
|
||
</sect2>
|
||
</sect1>
|
||
<sect1>
|
||
<title>Running an experiment</title>
|
||
<sect2>
|
||
<title> Creating and running batch files</title>
|
||
<para>Batch files are stored in /usr/local/nbi/sics/taipan/batch and are just text files
|
||
with the extension .tcl. You can edit these in a text editor, or the editing panel
|
||
of the left window. Your file, filename.tcl can be run by dragging and dropping into
|
||
the Buffer Queue and then run by pressing the “Play” button. </para>
|
||
<para>You can also queue additional files to run by dragging and dropping them into
|
||
Batch Queue window. These will then be run sequentially. Files can be removed and
|
||
edited or replaced as desired from the Batch Queue window. Once the file has been
|
||
read into the buffer, it can no longer be edited. For this reason it is recommended
|
||
that multiple short files are created. These can be run multiple times if necessary.
|
||
</para>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Validation of scans</title>
|
||
<para>To check your script, you can validate it using the Validation tab in the Buffer
|
||
Queue. Drag your file into the Validate window and click on Validate. Information
|
||
about your file will scroll through the log screen. Use this to see if any errors or
|
||
motor limits have been reached. </para>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Example experiment script</title>
|
||
<para>
|
||
<literallayout>
|
||
# This is a comment and will not be executed
|
||
drive qh 2.5 qk 0 ql 3.5 en 32
|
||
bmonscan clear
|
||
bmonscan add qh 2.5 0.1
|
||
bmonscan run 31 monitor 1000000
|
||
|
||
# This is another comment with important information
|
||
drive qh -2.5 qk 0 ql 3.5 en 32
|
||
bmonscan clear
|
||
bmonscan add s2 -55 -0.1
|
||
bmonscan run 31 monitor 1000000
|
||
clientput [m2 absenc] # (prints out the m2 absolute encoder value)
|
||
</literallayout>
|
||
</para>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Motor errors</title>
|
||
<warning>
|
||
<title/>
|
||
<para>If you ever see the following error message:</para>
|
||
<para><command>> ERROR: THREAD ZERO NOT RUNNING ON CONTROLLER on m1</command></para>
|
||
<para> Type the following (this is case sensitive)</para>
|
||
<para><command>> m1 send RS </command></para>
|
||
<para> If you ever see the following error message:</para>
|
||
<para><command>> ERROR: MOTOR CONTROLLER RUN ERROR: -102 on m2 </command></para>
|
||
<para>Type the following (this is case sensitive)</para>
|
||
<para><command>> m2 send MG RUNF</command> and if this is a number not 0 or 1,
|
||
then:</para>
|
||
<para><command>> m2 send RUNF=0</command></para>
|
||
</warning>
|
||
</sect2>
|
||
<sect2>
|
||
<title>Creating and accessing log files</title>
|
||
<para>There are new log files written for each experiment. These are located in:
|
||
<computeroutput>J:\data\current\reports\exp#\LogFile.txt</computeroutput> on the
|
||
Microsoft Windows DAV computer. These will be updated as the experiment progresses
|
||
and should include both commands from the command line window and the batch file. </para>
|
||
<para>Use a program such as WinSCP to transfer files to your computer. The files will be
|
||
in
|
||
<computeroutput>/experiments/taipan/data/current/reports/exp#/LogFile.txt</computeroutput>.
|
||
These files are archived to a proposal directory at the end of each cycle e.g.
|
||
<computeroutput>/experiments/taipan/data/proposal/proposal#/reports/exp#/LogFile.txt</computeroutput>
|
||
</para>
|
||
</sect2>
|
||
</sect1>
|
||
<sect1>
|
||
<title>Sample environment control</title>
|
||
<sect2>
|
||
<title>Cryo-furnace with Lakeshore 340 controller</title>
|
||
<para>The typical closed cycle cryo-furnace used on Taipan is cryo-furnace #1 (CF1).
|
||
This uses a Lakeshore 340 controller. SICS is capable of reading and driving the
|
||
temperature on this device. The Moxa box must be installed, and connected to the
|
||
Lakeshore hardware. In the future, the Lakeshores will have a dedicated Moxa box. </para>
|
||
<variablelist>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> tc1_driveable2</command></term>
|
||
<listitem>
|
||
<para>shows the sample temperature from channel A </para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> run tc1_driveable 200 </command></term>
|
||
<listitem>
|
||
<para>drives the regulation temperature (B) to 200K </para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> wait 600 </command></term>
|
||
<listitem>
|
||
<para>shows wait in seconds </para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>> drive tc1_driveable 200 </command></term>
|
||
<listitem>
|
||
<para>drives the regulation temperature (B) to 200K and waits for it to be
|
||
within 1K of this value before continuing to the next command </para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>>sct_ls340_tc1 send "RANGE?" </command></term>
|
||
<listitem>
|
||
<para>this will query the heater power range – 0 = off, 5 = 100W </para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>>sct_ls340_tc1 send "RANGE 1" </command></term>
|
||
<listitem>
|
||
<para>this will set the heater power range. Set to a value between 0-5
|
||
</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
</variablelist>
|
||
<para>The fine control of the temperature parameters, such as tolerance, heater power
|
||
range, etc, can be adjusted by clicking on the SIC Server tree view. Alternatively
|
||
you can use certain commands listed below in a batch file: </para>
|
||
<para>Check the heater power range of the closed cycle. To heat the sample relatively
|
||
quickly you need to have the heater range to 5. To reach base temperature (10K or
|
||
less), the heater range should be set to 4 or lower. </para>
|
||
<figure>
|
||
<title>Setting temperature</title>
|
||
<mediaobject>
|
||
<imageobject><imagedata align="center" width="160mm"
|
||
fileref="taipanGumtree3.jpg"/></imageobject>
|
||
</mediaobject>
|
||
</figure>
|
||
<para> These detailed commands can be used (also in batch files) to control the
|
||
temperature parameters:</para>
|
||
<variablelist>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> hlist –val /sics/tc1/sensor </command></term>
|
||
<listitem>
|
||
<para>shows set points and sensors etc</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> hget /sics/tc1/sensor/setpoint1</command></term>
|
||
<listitem>
|
||
<para>to show the temperature</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> hset /sics/tc1/sensor/setpoint1 200</command></term>
|
||
<listitem>
|
||
<para>to set the temperature to 200K – there is no blockage of the drive
|
||
functions when this command is used</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> > hset /sample/tc9/Loop1/setpoint 200</command></term>
|
||
<listitem>
|
||
<para>to set the temperature of the 12T magnet to 200K</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> hget /sample/tc9/Loop3/sensor</command></term>
|
||
<listitem>
|
||
<para>to read the temperature of the 12T magnet</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> hset /sics/tc1/heater/heaterRange 5</command></term>
|
||
<listitem>
|
||
<para>for 100W power, or 4 for 10W power</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> hset /sics/tc1/control/tolerance 1 5</command></term>
|
||
<listitem>
|
||
<para>to set the tolerance of 5K to reach desired temperature</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
</variablelist>
|
||
<para> Sics and gumtree can also control the high voltage rig which is also set up on
|
||
CF1. The following commands will be useful</para>
|
||
<variablelist>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> pulseron</command></term>
|
||
<listitem>
|
||
<para>turn on HV</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> pulseroff</command></term>
|
||
<listitem>
|
||
<para>turn off HV</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> getvolt</command></term>
|
||
<listitem>
|
||
<para/>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>
|
||
<command>> setvolt 100</command></term>
|
||
<listitem>
|
||
<para>sets the voltage to 100V</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
</variablelist>
|
||
</sect2>
|
||
<sect2>
|
||
<title>12T magnet control. Important procedures before ramping the field. </title>
|
||
<warning>
|
||
<title>Protect the slits</title>
|
||
<para>Once you have set your slits, turn the motion control <emphasis role="bold"
|
||
>OFF</emphasis> (on the same box as the shutter control) and <emphasis
|
||
role="bold">unplug</emphasis> the 4 cables. Turn the motion control ON
|
||
again. The slits are now in a safe mode for driving the field.</para>
|
||
</warning>
|
||
<warning>
|
||
<title>Stop magnet quenching</title>
|
||
<para>To perform field ramps safely (without risk of quenching), you should put the
|
||
beam stop down. To do this, turn the motion control OFF (on the same box as the
|
||
shutter control), ramp the field into persistent mode and then turn the motion
|
||
control ON again. Once you have reached your new field, drive to a new Q-E
|
||
position to ensure that all the motors still behave correctly after the motion
|
||
OFF. If not, you might have to reset particular motors: </para>
|
||
<para><command>> m1 send RS</command> (this will reset the m1 motor controller)</para>
|
||
<para>To keep the beam stop down</para>
|
||
<orderedlist>
|
||
<listitem>
|
||
<para> Turn off motion control</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Close valve located at the base of the beam stop</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Turn on motion control</para>
|
||
</listitem>
|
||
</orderedlist>
|
||
</warning>
|
||
</sect2>
|
||
<sect2>
|
||
<title>12T magnet control. Driving s1</title>
|
||
<para>There are two parameters you will need for driving the <command>s1</command> via
|
||
the sample stick. <command>vs1</command> drives the motor from the command line,
|
||
while <command>dummy_s1</command> is in the UB matrix and scan parameters. So use
|
||
these in the following way: </para>
|
||
<para><command>> drive vs1 30</command> (in the command line – this drives the motor
|
||
to a value) </para>
|
||
<para><command>> runscan dummy_s1 25 35 101 time 1</command>
|
||
</para>
|
||
<para><command>> runscan qh</command>
|
||
</para>
|
||
<para>When running a powder sample in the magnet, fix <command>dummy_s1</command>
|
||
</para>
|
||
<para><command>> dummy_s1 fix 1</command> (> dummy_s1 fix 0 to unfix)</para>
|
||
</sect2>
|
||
</sect1>
|
||
<sect1>
|
||
<title>Sample environment configuration (Local contact only)</title>
|
||
<para>On ics1-taipan, you'll be editing SICS configuration files so that SICS will load the
|
||
driver for a device. The editor is <command>vim</command>. This process will be done
|
||
through a graphical interface in the future. </para>
|
||
<variablelist>
|
||
<title><command>vim</command> commands</title>
|
||
<varlistentry>
|
||
<term><command>:colorscheme ron </command></term>
|
||
<listitem>
|
||
<para>Change the color scheme. This make editing easier</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term><command>/tasub</command></term>
|
||
<listitem>
|
||
<para> This searches for the string “tasub” </para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>i</term>
|
||
<listitem>
|
||
<para>insert mode. Add text.</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>r</term>
|
||
<listitem>
|
||
<para>replace. Replace a character.</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>x</term>
|
||
<listitem>
|
||
<para> delete</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
<varlistentry>
|
||
<term>ESC key</term>
|
||
<listitem>
|
||
<para> escape out of the current mode</para>
|
||
</listitem>
|
||
</varlistentry>
|
||
</variablelist>
|
||
<sect2>
|
||
<title>Lakeshore 340 configuration</title>
|
||
<para>When using the Lakeshore 340, various things need to be changed in the
|
||
configuration files. This should only be done by the local contact.</para>
|
||
<orderedlist>
|
||
<listitem>
|
||
<para>> cd /usr/local/nbi/sics/taipan/</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> vim extraconfig.tcl</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para> Remove both the # in the following four lines </para>
|
||
<para>#catch </para>
|
||
<para>#add_sct_… </para>
|
||
<para># hsetprop </para>
|
||
<para>#}msg </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Save and quit by typing <command>:wq</command>
|
||
</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics stop</command></para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics start</command></para>
|
||
</listitem>
|
||
</orderedlist>
|
||
</sect2>
|
||
<sect2>
|
||
<title>High voltage configuration</title>
|
||
<para>When using the High voltage setup, various things need to be changed in the
|
||
configuration files. This should only be done by the local contact.</para>
|
||
<orderedlist>
|
||
<listitem>
|
||
<para>> cd /usr/local/nbi/sics/taipan/</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> vim extraconfig.tcl</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para> Remove both the # in the four lines </para>
|
||
<para># Make AsyncP… </para>
|
||
<para># Make AsyncP… </para>
|
||
<para># pulser delay </para>
|
||
<para># pulser timeout </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Save and quit by typing <command>:wq</command>
|
||
</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Make sure that the IP on the function generator is set to the following:
|
||
137.157.203.149 </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Get an electrician such as Dan Bartlett to confirm the setup is safe!
|
||
</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics stop</command></para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics start</command></para>
|
||
</listitem>
|
||
</orderedlist>
|
||
</sect2>
|
||
<sect2>
|
||
<title>12T magnet configuration</title>
|
||
<para>When using the 12T magnet, various things need to be changed in the configuration
|
||
files. This should only be done by the local contact. </para>
|
||
<orderedlist>
|
||
<listitem>
|
||
<para>Turn on the magnet laptop – check that the Ethernet cable and grey cable
|
||
are connected. </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Click on “SICS oxford instruments” to bring up the front panel. </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Click on ITC503 Front Panel </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>open a Putty terminal</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> cd /usr/local/nbi/sics/taipan/server </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> sudo vim taipan_configuration.tcl </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>On line 59, remove the # from # fileeval ../aerotech.tcl </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>On line 61 is s1 in the TASUB command. Change this to vs1. </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Save and quit by typing <command>:wq</command>
|
||
</para>
|
||
<para>If you made a mistake, quit without changing by typing
|
||
<command>:q!</command> and start again.</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> cd config/motors/ </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> sudo vim motor_configuration.tcl </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>/magnet</command>
|
||
</para>
|
||
<para>Search for the string “magnet” </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>The following {0} should change to {1} for the magnet: </para>
|
||
<para>If {0}{</para>
|
||
<para> # Convert magnet angle to s1 angle </para>
|
||
<para> VarMake vs1speed float user </para>
|
||
<para> vs1speed 1 </para>
|
||
<para> … </para>
|
||
<para> } } </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Save and quit by typing <command>:wq</command>
|
||
</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> cd /usr/local/nbi/sics/taipan/</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> vim extraconfig.tcl</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>#--------------- </para>
|
||
<para># 12T magnet </para>
|
||
<para>#--------------- </para>
|
||
<para>Remove the # in the following lines (choose which temp controller method
|
||
you require – running with the Mercury, or as Legacy mode) </para>
|
||
<para>#add_oxford_magnet "magnetic" 137.157.203.153 </para>
|
||
<para>#add_oxford_mercury "tc9" 137.157.203.151 7020 2.0 "\r" </para>
|
||
<para>#add_itc500 tc1 137.157.203.151 7020 2.0 "@8" This is for running in
|
||
Legacy Mode (to look like ITC500) </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Save and quit by typing <command>:wq</command>
|
||
</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics stop</command></para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics start</command></para>
|
||
</listitem>
|
||
</orderedlist>
|
||
</sect2>
|
||
<sect2>
|
||
<title><superscript>3</superscript>He configuration</title>
|
||
<para>When using the <superscript>3</superscript>He setup, various things need to be
|
||
changed in the configuration files. This should only be done by the local contact.</para>
|
||
<para>When using the <superscript>3</superscript>He setup, you need to switch to the
|
||
appropriate speeds and accelerations for the elongated instrument. To do this, in
|
||
the PuTTy window, go to </para>
|
||
<orderedlist>
|
||
<listitem>
|
||
<para>> cd /usr/local/nbi/sics/taipan/</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>> vim taipan_setup.txt</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Change the 0 to 1 to turn on this file </para>
|
||
</listitem>
|
||
<listitem>
|
||
<para>Save and quit by typing <command>:wq</command>
|
||
</para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics stop</command></para>
|
||
</listitem>
|
||
<listitem>
|
||
<para><command>> runsics start</command></para>
|
||
</listitem>
|
||
</orderedlist>
|
||
</sect2>
|
||
</sect1>
|
||
<sect1>
|
||
<title>Known Issues</title>
|
||
<para>Alerts the user to known operational problems</para>
|
||
</sect1>
|
||
<sect1>
|
||
<title>Troubleshooting</title>
|
||
<para>What to do if things go wrong</para>
|
||
</sect1>
|
||
</chapter>
|