1 INTRODUCTION
The software described in this manual is intended to be used in the ESO VLT project by ESO and authorized external contractors only.
While every precaution has been taken in the development of the software and in the preparation of this documentation, ESO assumes no responsibility for errors or omissions, or for damage resulting from the use of the software or of the information contained herein.
1.1 PURPOSE
This document is the User Manual of the Central Control Software (CCS).
It is intended to provide all the necessary information to use this software to develop application software running on the workstations .
The manual assumes that the reader has a good knowledge of UNIX, C language and is familiar with the RTAP terminology.
In addition to this Introduction section, this manual contains four major sections:
User's Guide, describing the functionality provided by the software, including examples of utilization.
Reference, describing all the functions, commands and tools available to the applications and the application developers.
Installation Guide, describing how to install and make the software ready to be used. This section has been moved into a dedicated manual
[4]covering the full VLT software installation.
Error Messages and Recovery. Provides a list of errors and diagnostic messages and possible recovery actions.
1.2 SCOPE
This manual describes the February 2007 release of the CCS software module.
Changes in modules already described in the pevious issue are highlighted with change bars in the margins. Please be aware that for technical reasons, this was not possible for the Reference section and the Error definition files although there might be differences.
CCS matters is also described in other manuals: Extended CCS User Manual[12] & Event Tool Kit-EVH User Manual[13] document, for C++ programmers, an optional library, and a toolkit to implement event driven applications. Since April 2004 release, the Monitoring tools are described in a dedicated user manual[22] and since the JAN06 release, the engineering interfaces and graphical tools are now described in a dedicated document[23].
1.3 REFERENCE DOCUMENTS
The following documents are referenced in this document and provide additional information:
[1] VLT-PRO-ESO-10000-0228, 1.0 10/03/93 VLT Software Programming Standards
[2] VLT-SPE-ESO-17120-0270, 1.0 VLT LAN's Specification
[3] VLT-MAN-ESO-17200-0888 1.0,VLT Common SW - Overview.
[4] VLT-MAN-ESO-17200-0642 1.6,VLT Common SW - Installation Manual.
[5] VLT-SPE-ESO-17240-0666,2/1 INS Common Software (Design Document)
[6] RTAP/Plus Reference Manual, (vol 1 and vol 2) version 6.7
[7] RTAP/Plus Integration, version 6.7
[8] RTAP/Plus User's Guide, version 6.7
[9] VLT-MAN-SBI-17210-0001 VLT LCC User Manual. Issue 3.4
[10] VLT-SPE-ESO-17210-0711-VLT LCU Software Specification for phase 2 .Issue 1.1
[11] VLT-MAN-ESO-17210-0707-CCS On Line Database Loader User Manual. Issue 1.5
[12] VLT-MAN-ESO-17210-0770 - CCS Extended CCS User Manual. Issue 1.4
[13] VLT-MAN-ESO-17210-0771- CCS Event Tool Kit-EVH User Manual. Issue 1.4
[14] VLT-SPE-ESO-10000-0011-VLT Software Requirements Specification. Issue 2.0
[15] VLT-SPE-ESO-17210-0001-VLT CCS Software Specification. Issue 1.0
[16] VLT-MAN-ESO-17210-0885 - CCS-LITE User Manual. Issue 1.1
[17] VLT-MAN-ESO-17230-1023 - HOS/ACC - User manual. Issue 1.0
[18] VLT-MAN-ESO-17230-1024 - ACC Software User manual. Issue 1.0
[19] GEN-SPE-ESO-19400-794/1.0/8 - Data Interface Control Document
[20] VLT-MAN-ESO-17200-2238 - Combined OS installation manual.
[21] VLT-MAN-ESO-17210-2522-VLT Software - Java Database Monitor - CcseiDb - User Manual 2.0
[22] VLT-MAN-ESO-17210-3053 - VLT Software CCS LITE Monitoring Tools User Manual 1.0
[23] VLT-MAN-ESO-17210-3816 - CCS Engineering Interface And Graphical Tools. 1.0
1.4 ABBREVIATIONS AND ACRONYMS
The following abbreviations and acronyms are used in this document:
ACC Access and Configuration Control
CCS Central Control Software
CCS_Lite Lite version of the CCS software. Not based on RTAP.
DBMS Database Management System
HOS High Level Operations Software
IEEE Institute of Electrical and Electronics Engineers
RTAP/Plus Real Time Application Platform: a product of Hewlett-Packard
1.5 GLOSSARY
Environment
A combination of processes and applications together with other resources like on line database and communication mechanisms. Multiple environments can exist on a single host. The concept of environment is inherited from RTAP and has been extended to CCS_Lite
.
Environment Name
Name by which a given CCS_Lite or RTAP environment is accessible from other environments.
Error Context
The Error Context is the current setup of the error structure returned by the
PLIN (Point List Index Number)
A unique reference number that identifies each point within the database and can be used as a direct address of the point. The PLIN is automatically assigned to each point when the point is created and remains the same until the point is deleted.
A new point can be assigned a PLIN that was used by a deleted point.
Quality Flag
A status 'stamp' which conveys information about the origin or integrity of a data value when this value is resulting from a Calculation Engine definition.
Possible values of the flag are :
a. Error, in case of mathematical errors.
b. Disabled, when the CE has been disabled for that element.
c. Suspect, when the result might be 'corrupted'.
Multithreading
The ability of an operating system to execute different parts of a program, called threads, simultaneously.
Snapshot
An image of the On Line database saved on the disk, to help restore the database in the case of a shutdown or system failure.
1.6 STYLISTIC CONVENTIONS
The following styles are used:
bold in the text, for commands, filenames, pre/suffixes as they have to be typed.
italic in the text, for parts that have to be substituted with the real content before typing.
<name>
in the examples, for parts that have to be substituted with the real content before typing.
bold and italic are also used to highlight words.
1.7 NAMING CONVENTIONS
This implementation follows the naming conventions outlined in the VLT Programming
Standard [1].
1.8 PROBLEM REPORTING / CHANGE REQUEST
In case you don't have access to the ad-hoc WEB based tool, the following form shall be used:
1. to report a problem encountered using the software and/or the documentation,
2. to suggest changes in the software or documentation
Please fill the form, as appropriate to your case, and send it with any other additional material that you think could be helpful, to ESO:
1. by mail or fax for the attention of:
VLT/ELE-SOFTWARE GROUP/Software Configuration Control
2. by e-mail to:
Your request will be checked-in in the Change Request database and processed according to ESO change control procedure. The registration number will be communicated to you for further reference.
===============================================================================
E. S. O. --- VERY LARGE TELESCOPE PROJECT ---
-------------------------------------------------------------------------------
PROBLEM REPORT/CHANGE REQUEST FORM DATE: ../../..
===============================================================================
From:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tel:+. .-. . -. . . . . Fax:+. .-. . -. . . . . e-mail: . . . . . . . . . .
-------------------------------------------------------------------------------
Software/Document identification
Module name / Title : . . . . . . . . . . . . . . . . . . . . . . . . . .
Version/Doc.NR-issue-date: . . . . . . . . . . . . . . . . . . . . . . . . . .
-------------------------------------------------------------------------------
Please mark one of the following categories
_ software error _error in the documentation _change request
_ other: (specify) . . . . . . . . . . . . . . . . . . . . . . . . . . .
and provide the full description and, in case of anomaly, how to reproduce it:
(continue on a separate sheet if necessary)
-------------------------------------------------------------------------------
