2 OVERVIEW
2.1 GENERAL
The VLT Common Software currently includes:
· VLT development utilities
· Central Common Software (CCS)
· Instrumentation Common Software (INS)
· Telescope Control Software (simulation)
· WS-LCU communication software (Qserver)
· LCU Common Software (LCC)
· CCD Control Software (formerly disstributed as a separate tape)
· Infrared Detector Control Software (IRD)
· installation and installation verification procedures
and all the relevant documentation in both printed and PostScript file format.
The present version of the VLT Common Software replaces entirely any previous ESO distribution of VLT Software. No support will be given to previous versions.
The distribution kit contains all the sources needed to regenerate the software on both HP and SUN systems. Distributing the sources also provides developers with:
· examples of applications (e.g., test programs)
· skeletons for the development of similar modules (e.g., drivers)
For a complete description of each module mentioned, please refer to the appropriate user manual, included in the shipment.
The major differences with the previous version as well as currently knows problems and work around are summarized in the RELEASE NOTES, that are published together with the documentation and also available on WEB.
Even if you are interested in only one part of the VLT Software, please read ALL of the following sections.
2.1.1 Copyright
The VLT Common Software is distributed outside ESO for the development of applications related to the VLT Project and ruled by the "General Conditions of ESO Contracts". Any other use is not allowed without prior authorization from ESO.
The rights of Third Parties (Free Software Foundation, VxWorks, etc.), whose software is for convenience copied on the VLT Common Software tape, are ruled by their copyright notice included in their software.
The file COPYING, included in the distribution kit, contains the full copyright notice.
2.2 SUPPORTED CONFIGURATION
2.2.1 Hardware
· Motorola MVME 167 CPU board - any version
· Motorola MVME 2604 CPU board - any version
· VMIVME-3111 Analog I/O board - version ID 0x0d
· ACROMAG AVME948X Digital I/O board - any version
· ESO Time Reference Board - ESO internal version
· VME4SA-X1 4-channel DC Servo Amplifier - any version
· VME4ST 4-channel STP Servo Amplifier - any version
· MACCON - MAC4- INC motion controller incremental encoder - version 4.1A or 4.2
· MACCON - MAC4- SSI motion controller SSI encoder - version 4.1A or 4.2
· MACCON - MAC4- STP motion controller STP encoder - version 2.0A or 2.1
· VMIVME-5576 Reflective Memory Board
· ESD ISER8 - 8 port RS232 serial interface
· NAT NET01 - Ethernet board
· BI016 - transputer interface
· Heidenhain IK320 Encoder, firmware: "246 118 06"
2.2.2 Software
SUN: Solaris 2.6 for CCSlite and NOCCS. No CCS(RTAP) version for Solaris.
HP: HP-UX B.10.20 for Full CCS (+ RTAP)
HP-UX B.11.00 for CCSlite and NOCCS. No CCS(RTAP) version for HP11.
Remark: we do not distribute by default both the HP-UX operative systems. By default HP10.20
will be delivered unless the consortium makes explicitly request for HP11 instead, or both.
Graphical Libraries: X11R5 and Motif1.2.
For both SUN and HP, these libraries are an add-on to the basic OS. You are required to install the appropriate extensions in order to be able to compile and link graphical applications:
HP: "C-Development bundle" (includes c89-compiler, X11, Motif, etc.)
RTAP: (required only if you intend to install Full CCS on HP10.20)
· TORNADO 1.0.1 (VxWorks 5.3) on HP-UX 10.20 and 11
· TORNADO 2.0 (VxWorks 5.4) on SunOS
MIDAS (only if INS/pco installation is done):
2.3 CONTENTS
The VLT Common Software is distributed as:
a. the software. (For convenience, the CD also contains some public domain software used in the generation of the VLT Software)
· an additional CD containing VxWorks (5.3 or 5.4) is distributed on request
2.3.1 Software
1. PUBLIC DOMAIN SOFTWARE
a. GNU C-compiler (2.95.2)
2. VLT SOFTWARE
(the version number of each module is listed in <VLTSW>/INSTALL/buildFromArchive)
installation scripts: (vltsw)
Kit/VLT Makefile and Man-page browser (vlt)
document development support toolkit (doc)
software module handling utilities (mod)
utilities to check files for potential compatibility problems (compat)
code and document templates (templates)
standard environment (stdEnv)
compatibility checker (compat)
emacs customization kit (emacs)
code management module (cmm)
tool for automatic test (tat)
workpage time account (wp) (FOR ESO INSTALLATION ONLY)
b. Queue Server Emulator (qsemu)
c. Central Common Software:
d. HOS (High-level Operaton Software)
brooker for observing blocks (bob)
access configuration and control (acc)
e. INS Common Software - File handling
SLX/miscellaneous utilities (misc)
SLX/setup file handling (slx)
SLX/setup file handling - C++ version (oslx)
SLX/setup file handling - tcl interface (slxtcl)
SLX/file handling tool - user interface (fht)
INS/data transfer module. (dxf)
INS/ins system tools (ist)
INS/protocol converter. (pco)
INS/common templates (insc)
INS/VLT OnLine Archive interface (volac)
f. ICB INS Common Base ICS (auto, ctoo, egen, ic0, ic0dev, ic0dig, ic0lcu, ic0mot, ic0sen, icb, lccdev, lcctoo)
h. OSB (boss, ibac, ixac, osb)
i. FIERA CCD Detector ontrol Software
j. IRD Infrared Detector Control Software - NEW -
k. TCS (Telescope Control Software)
TCS/Star Catalogue interface (catif)
TCS simulation kit (agws, catif, m2com, msw, prs, tcs, tcssim, tif, trkws)
TPOINT Telescope pointing model
l. Real-Time Display (DMD/rtd) and catalog lirary (DMD/catlib)
m. DICB FITS keyword Dictionaries (dicDPR, dicOBS, dicPAF, dicTPL) - NEW -
n. an example of a WS application (examples/wsapp)
LCC engineering interface (lccei)
Command Interpreter templates (citmp)
Command Interpreter tools (too)
driver log utility (lculog)
driver common utilities (lcudrv)
empty driver skeleton (xxx)
ACROMAG Digital I/O driver (acro)
Servo Amplifier driver (ampl)
NET01 Ethernet I/F Board driver (net01)
Heidenhein IK320 Encoder driver (ikon)
LCU configuration tool (lcuboot)
LCU status monitoring tool (lcustat, lcuwd)
driver engineering interface basic tool (inducer)
acro engineering interface (acrox)
aio engineering interface (aiox)
ikon engineering interface (ikonx)
Time Board engineering interface (timx)
Motion Controller wrapper (mcm)
Motion Controller SDL (mac4)
Motor Control Module API (mot)
Motor Command Interface (motci)
Motor Engineering Interface (motei)
SDL Common Interface (sdl)
Servo Amplifier SDL (vme4sa)
s. an example of an LCU application (lexamples/cuapp)
2.3.2 Documentation
The documentation is organized in the following volumes
1a&b: CCS - workstation part
2a: LCU Common Software and Motor Library
See the table of contents, delivered as part of the kit in a file called TOC, for the actual list of documents.
Documents are provided:
· as paper copy
only on motivated request
To people who have already received the previous versions, only new or changed documents are shipped as well as instructions on how to merge the new set into the existing one.
· as a tar compressed file DOC.tar.Z in the VLTSW CD that contains all the documents in ps format (most of them are also in pdf format)
· on the web:
http://www.eso.org/projects/vlt/sw-dev/wwwdoc/MAR2001/dockit.html
2.4 BACKWARD COMPATIBILITY
The software included in the present delivery is backward compatible with the previous versions that have been already declared as baseline. For what is concerning software that appear for the first time with this release, please refere to the appropriate User Manual to see whether is released as a baseline version (i.e., backward compatible in future versions) or still in a preliminary form (i.e., it may change in future versions)
In any case, after the installation of the current release, any existing software must be regenerated.
The "Release notes" points out the differences between the current version and the previous one. In addition the "compat" utilities is provided to help in locating the lines of code to be changed (see 3.10 for more), if any.
2.5 NEW DEFAULT SHELL
Starting with the MAR2001 release, the default shell is bash. We changed to bash from tcsh for different technical reasons, the main one being that tcsh is not supported any longer on HP11.
We re-wrote also the standard environment, now called PECS (see section 3.6 and 6) in order to use bash. The general organisation of the environment, the installation procedure and setting the environment for a user have changed. The implications of this are:
· a new account is needed (called pecsmgr) that is the owner of some core PECS files;
· the users vltmgr and vlt must have the default shell set to /bin/bash;
· vx will remain to /bin/csh
· any other user must be defined with default shell /bin/bash
· the syntax in the bash shell is different (see
6 ).
2.6 PROBLEM REPORTING/CHANGE REQUEST
Please use the procedure explained in [6].
