NONIUS CAD4/MACH3 User manual

Introduction
Installation of the programs
    Linux PC
    Irix SGI
Configuration of the programs and data

Introduction

Common to all of the computers used as hosts in CAD4 systems is their ability to exploit the many capabilities of the operating system. This disk-oriented system permits multiple users each to execute multiple tasks which may have different and variable priorities. It provides many invisible but highly important attributes which enhance the systems reliability and throughput. In addition its repertoire of commands allows the operator all of the flexibility and user friendliness expected of modern computing systems.

It is neither possible nor appropriate in this manual to describe all of the system commands and this will not be attempted. It is assumed that the user is reasonably familiar with the UNIX operating system.

Installation of the programs

Below details on the installation for LINUX and IRIX operating systems are given. For other UNIX systems the installation will be done in an analogous way. Only the names of the devices, important for the connection with the RS232, may be different.

LINUX

First a top directory has to be created, in which the .tar file should be extracted, for instance /home/cad4. This directory should be linked to /cad4_root by the system manager:

ln -s /home/cad4 /cad4_root

The RS232 port should be read/write enabled; i.e. if this is "cua1" do:

chmod 666 /dev/cua1

The stty settings which are seen by the UNIX command:

stty < /dev/cua1

are set during program startup. If the baudrate is not 9600 it should be set so by:

stty 9600 < /dev/cua1

Copy the file c4_lin_vvvv.tar to the top directory (vvvv is the linux version; the version number can be seen by /bin/uname -r). Extract the .tar file in this directory by: tar -xvf c4_lin_vvv.tar so that the subdirectories and files will be created now.

IRIX (SGI)

First a top directory has to be created, in which the .tar file should be extracted, for instance /usr/people/cad4. This directory should be linked to /cad4_root by the system manager:

ln -s /usr/people/cad4 /cad4_root

The RS232 port should be read/write enabled; i.e. if this is "ttyd2" do:

chmod 666 /dev/ttyd2

The stty settings, which are seen by the UNIX command:

stty < /dev/ttyd2

are set during program startup. If the baudrate is not 9600 it should be set so by:

stty 9600 < /dev/ttyd2

In /etc/inittab the line for the cad4 device should be (also in case of ttyd2):

t2:23:off:/sbin/getty -N ttyd2 co_9600 #port 2

Copy the file c4_sgi_vvv.tar to the top directory. (vvvv is the irix version; the version number can be seen by /bin/uname -r). Extract the .tar file in this directory by: tar -xvf c4_sgi.tar so that the subdirectories and files will be created now.

Configuration of the programs and data

The work_directory is the system subdirectory, i.e. the subdirectory of /cad4_root named system. In this directory the links are also made during the extraction of the .tar file. Optionally the file make_links in the top directory can be used.

In the work_directory are all programs used by the CAD4 system and the handlers (.tsk) files for the interfaces ( falcon, falcon+ and lsi).

Data will come in subdirectories of the root, for example in data0/ for your first CAD4, in data1/ for your second CAD4. In that case the other data directories (until data7) will not change or can be used for simulation. In the work_directory these data directories are linked to ca0_data, ca1_data etc.

Other directories of the root are jobs/ (linked in the work directory to cad4_jobs), used by the CAD4 command 'NEWCMP' to create the .cat files for the automatic procedure (see Automatic Measurement Procedure) and global (linked to cad4_global in the work_directory), which contains files with general CAD4 values and parameters important for the automatic procedure.

Values and parameters important for a specific CAD4 are in files of the data subdirectories config (linked in the work_directory to ca0_config, ca1_config etc.). Some files in ca"n"_config have to be mentioned here:
 
 

The file rs232_port.xxxx	If xxxx = "simula" (in the distribution version for "n" = 1 to 7) the simulation version of the program will run. Otherwise the program assumes that xxxx is the device name of the serial(RS232) line. For instance cua1 for linux, ttyd2 for sgi, tty00 for ultrix.
The file lambda.xx	In the distribution xx is mo (Molybdenum radiation). For copper radiation rename this file to lambda.cu. This is important for the  automatic measurement procedure (see also auto.doc).
The file temperature.xxx	In the distribution version xxx is lnt, which means that low (liquid nitrogen) temperature is assumed. In that case during the automatic procedure data collection is not always done at psi = 0. If you rename the file so that xxx is something else (max. 3 characters) room temperature is assumed and reflections are normally measured at psi = 0 in bisecting mode.
The file kv.xxx	In the distribution version xxx is 60, which means that for the generator 60 kV is assumed. This will come in text of the data-collection file, also if using the automatic procedure. If you use for instance 40 kV, rename this file to kv.40.
The file ma.xxx	In the distribution version xxx is 50, which means that for the generator 50 mA is assumed. This will come in the text of the data-collection file, also if using the automatic procedure. If you use for instance 40mA, rename this file to ma.40.
The file filter.xxx	In the distribution version xxx is mon, which means that a monochromator is assumed. This will come in the text of the data-collection file, also if using the automatic procedure. You can rename filter.mon so  that xxx is something else.
The file profile.x	In the distribution version x is 3, which means that during a measurement the last three profiles in argus (Argus, Display of the CAD4 process) are displayed. If you want for instance only the last two profiles, rename profiles.3 to profile.2

Files necessary for the X-window version of the argus program are in the data subdirectories master (linked in the work_directory to ca0_master, ca1_master etc.). For a good working program system it is important that the files and links in all directories mentioned above are not changed, deleted or renamed, except for the files mentioned.