Dc10 Parts Diagram Is So Famous, But Why? | Dc10 Parts Diagram

Dyson Dc12 Animal Parts Schematic - Schematics Wiring Diagrams • - dc24 parts diagram

Dyson Dc12 Animal Parts Schematic – Schematics Wiring Diagrams • – dc24 parts diagram | dc24 parts diagram


Organisation Européenne cascade des Recherches Astronomiques dans l’Hémisphère Austral

Europäische Organisation für astronomische Forschung in der südlichen Hemisphäre



VLT Software

Template Apparatus Software

User and Aliment Manual

Doc. No.: VLT-MAN-ESO-17240-1973

Issue: 5

Date: 13/01/2005

Name                                                       Date                         Signature

                Prepared:  A.Longinotti                                                      13/01/2005

Name                                                       Date                         Signature

          Approved:  K.Wirenstrand                                                                 

Name                                                       Date                         Signature

                Released:  K.Wirenstrand                                     

VLT PROGRAMME * TELEPHONE: (089) 3 20 06-0 * FAX: (089) 3 20 06 514











First issue, complete alone ICS part




Second issue, complete the accomplished instrument, including OS



4.7.2 5.3 11.10.4

MAR2002, Added ICS stand-alone GUI, SPR VLTSW20010501, VLTSW20010502.



3.2 Appendix B




2.2.1 3.2.1

Chapter 7

Chapter 8


App. A

App. B

New accession modules for locations added than the final one

Added affiliate on analysis Software

Contents of modules updated

Contents of agreement files removed

Removed xxinsCreateNewInstrument (VLTSW20040136)

Removed xxinsChangeEnvs (VLTSW20040136)

TABLE OF CONTENTS                                                                                                                                                                                      3

1 INTRODUCTION                                                                                                                                                                                             7

1.1     Purpose                                                                                                                                                                                                   7

1.2     Scope                                                                                                                                                                                                       7

1.3     Applicative Documents                                                                                                                                                                         7

1.4     Reference Documents                                                                                                                                                                           8

1.5     Abbreviations and Acronyms                                                                                                                                                             9

1.6     Glossary                                                                                                                                                                                                  9

1.7     Stylistic Conventions                                                                                                                                                                            9

1.7.1      Abstracts Flow and Processor Archetypal Diagrams                                                                                                                             9

1.8     Allotment Conventions                                                                                                                                                                          10

1.9     Problem Reporting/Change Request                                                                                                                                                10

2 OVERVIEW                                                                                                                                                                                                     11

2.1     Accouterments architecture                                                                                                                                                                         11

2.1.1      Devices                                                                                                                                                                                       11

2.1.2      Computers                                                                                                                                                                                  11

2.1.3      LANs                                                                                                                                                                                           11

2.1.4      Appropriate connections                                                                                                                                                                  11

2.2     Software Architecture                                                                                                                                                                         13

2.2.1      Software Modules                                                                                                                                                                     13

2.2.2      Environments                                                                                                                                                                             13

2.2.3      Standards                                                                                                                                                                                   13

3 INSTALLATION GUIDE                                                                                                                                                                               15

3.1     Requirements                                                                                                                                                                                        15

3.1.1      Hardware                                                                                                                                                                                    15

3.1.2      Software                                                                                                                                                                                      15

3.2     Accession procedure                                                                                                                                                                         15

3.2.1      Accession at added locations                                                                                                                                                 16

4 OPERATOR’S GUIDE                                                                                                                                                                                   17

4.1     Arrangement Start-up                                                                                                                                                                                    17

4.1.1      Log-in                                                                                                                                                                                          17

4.1.2      Telescope availability                                                                                                                                                               17

4.1.3      Midas availability                                                                                                                                                                      18

4.1.4      Apparatus Software Start-up                                                                                                                                                  18

4.1.5      Begin of operations                                                                                                                                                                  19

4.1.6      End of operations                                                                                                                                                                      19

4.2     Arrangement Shut-down                                                                                                                                                                              19

4.3     User Station                                                                                                                                                                                          20

4.4     Observations with Templates                                                                                                                                                            21

4.5     Alarms                                                                                                                                                                                                   21

4.6     Abstracts files location                                                                                                                                                                                21

4.7     Engineering                                                                                                                                                                                           21

4.7.1      OS Engineering GUI                                                                                                                                                                  21

4.7.2      ICS Engineering GUI                                                                                                                                                                 21

5 PROGRAMMER’S GUIDE                                                                                                                                                                           23

5.1     Apparatus Modes                                                                                                                                                                               23

5.2     Subsystems Identifiers                                                                                                                                                                       23

5.3     ICS Software Devices                                                                                                                                                                          23

5.3.1      ICS Appropriate devices                                                                                                                                                                   24

5.3.2      ICS Assemblies                                                                                                                                                                         24

5.4     Exposures                                                                                                                                                                                              25

5.4.1      Acknowledgment types                                                                                                                                                                          25

5.4.2      Acknowledgment Id                                                                                                                                                                                25

5.4.3      Acknowledgment Status                                                                                                                                                                         25

5.4.4      Acknowledgment Parallelism                                                                                                                                                                 25

5.4.5      Acknowledgment Life Cycle                                                                                                                                                                  25

5.4.6      Acknowledgment execution                                                                                                                                                                   26

5.5     Operational States                                                                                                                                                                               26

5.6     Commands                                                                                                                                                                                            26

5.6.1      OS Appropriate commands                                                                                                                                                              26

5.6.2      ICS Appropriate commands                                                                                                                                                             26

5.6.3      DCS Appropriate commands                                                                                                                                                            26

5.7     Tcl libraries                                                                                                                                                                                           26

5.8     Dictionaries                                                                                                                                                                                           26

5.9     Alias files                                                                                                                                                                                              27

5.10    Agreement files                                                                                                                                                                               27

5.11    Bureaucracy files and keywords                                                                                                                                                                   27

5.11.1        OCS keywords                                                                                                                                                                       27

5.11.2        INS keywords                                                                                                                                                                        27

5.11.3        DCS keywords                                                                                                                                                                       28

5.12    FITS files                                                                                                                                                                                               28

5.13    Public on-line database attributes                                                                                                                                                     28

5.14    Operational logs                                                                                                                                                                                   28

5.15    Templates                                                                                                                                                                                              28

5.15.1        Accretion Templates                                                                                                                                                         29

5.15.2        Arrangement Templates                                                                                                                                                          29

5.15.3        Ascertainment Templates                                                                                                                                                        29

6 CONFIGURATION                                                                                                                                                                                        30

6.1     Change Apparatus Agreement Parameters                                                                                                                                30

7 TEST                                                                                                                                                                                                                 32

8 MAINTENANCE                                                                                                                                                                                             33

8.1     General                                                                                                                                                                                                   33

8.1.1      Bore xxins                                                                                                                                                                              33

8.1.2      Bore dicXXXX                                                                                                                                                                     33

8.2     OS                                                                                                                                                                                                           33

8.2.1      Bore xxo                                                                                                                                                                                 33

8.2.2      Bore xxopan                                                                                                                                                                          34

8.2.3      Bore xxotsf                                                                                                                                                                            34

8.2.4      Bore xxoseq                                                                                                                                                                          35

8.3     ICS                                                                                                                                                                                                          36

8.3.1      Bore xxi                                                                                                                                                                                  36

8.3.2      Bore xxipan                                                                                                                                                                           37

8.3.3      Bore xxidev                                                                                                                                                                           37

8.4     DCS                                                                                                                                                                                                        37

8.4.1      Engineering                                                                                                                                                                                37

8.5     MS                                                                                                                                                                                                          38

8.5.1      Aliment Templates                                                                                                                                                           38

8.5.2      Bore xxmcfg                                                                                                                                                                          38

8.5.3      Bore xxmseq                                                                                                                                                                          38

8.5.4      Bore xxmtsf                                                                                                                                                                           38

9 FAQ AND TROUBLESHOOTING                                                                                                                                                              39

9.1     Problems at Arrangement Start-up                                                                                                                                                              39

9.1.1      Log-in fails                                                                                                                                                                                 39

9.1.2      Start-up of GUIs fails                                                                                                                                                                39

9.1.3      Start-up of ascendancy processes fails                                                                                                                                         39

9.1.4      xxiControl starts with a amiss simulation level                                                                                                                    39

9.1.5      TCCD starts with a amiss simulation level and fails to go STANDBY                                                                            39

9.1.6      xxoControl tries to admission sub-systems declared as not available                                                                                    39

9.1.7      Activity ONLINE fails                                                                                                                                                                  39

9.2     Problems back alive exposures                                                                                                                                                   40

9.2.1      Cannot accelerate commands to TCS or admission tif                                                                                                                       40

9.2.2      Templates cannot admission Midas                                                                                                                                            40

10     ERROR DEFINITIONS                                                                                                                                                                           41

11     REFERENCE                                                                                                                                                                                             42

11.1    Programs                                                                                                                                                                                               42

11.1.1        Command Analogue Table for program xxoControl                                                                                                        42

11.2    Scripts                                                                                                                                                                                                    43

11.2.1        xxinsStartup                                                                                                                                                                           43

11.2.2        xxinsStart                                                                                                                                                                                44

11.2.3        xxinsStop                                                                                                                                                                                46

11.3    Accommodate Files                                                                                                                                                                                         48

11.4    Tcl libraries                                                                                                                                                                                           49

11.4.1        xxoseqICS                                                                                                                                                                               49

11.5    Agreement files                                                                                                                                                                               50

11.6    Bureaucracy files                                                                                                                                                                                             51

11.6.1        Archetype of  Reference Bureaucracy file                                                                                                                                         51

11.6.2        Archetype of Apparatus Bureaucracy File                                                                                                                                       51

11.7    Templates                                                                                                                                                                                              52

11.7.1        IR Imaging accretion template                                                                                                                                         52

11.7.2        IR Imaging ascertainment template                                                                                                                                       53

11.7.3        IR Spectroscopy accretion template                                                                                                                               54

11.7.4        IR Spectroscopy ascertainment template                                                                                                                             55

11.7.5        Optical Imaging accretion template                                                                                                                                56

11.7.6        Optical Imaging ascertainment template                                                                                                                               57

11.7.7        Optical Imaging bent arrangement template                                                                                                                         58

11.7.8        Optical Imaging flat-field calibration template                                                                                                                  59

11.7.9        Optical Imaging detector linearity arrangement template                                                                                                  60

11.7.10      Optical Imaging focus arrangement template                                                                                                                      61

11.8    FITS files                                                                                                                                                                                               62

11.8.1        Archetype of FITS header                                                                                                                                                       62

11.9    Log files                                                                                                                                                                                                 63

11.9.1        Archetype of Operational Log (FITS format)                                                                                                                        63

11.10  Panels                                                                                                                                                                                                    64

11.10.1      OS Control                                                                                                                                                                             64

11.10.2      OS Status                                                                                                                                                                               65

11.10.3      OS Engineering                                                                                                                                                                     66

11.10.4      ICS stand-alone                                                                                                                                                                     68

11.11  Absurdity files                                                                                                                                                                                               70

11.11.1      xxoErrors.h                                                                                                                                                                             70

11.11.2      xxo_ERRORS                                                                                                                                                                         71

Appendix A. Actualize a new Instrument                                                                                                                                         73

A.1    OS sub-classing and adjustment overloading                                                                                                                                       73

A.2    Add appropriate commands to OS                                                                                                                                                            73

A.3    Add appropriate administration of accoutrement keywords in OS                                                                                                                            73

A.4    Apparatus a chic library for templates                                                                                                                                            73

A.5    Apparatus an ICS appropriate accessory on LCU                                                                                                                                        73

A.6    Apparatus an ICS appropriate accessory on WS                                                                                                                                          73

A.7    ICS WS sub-classing and adjustment overloading                                                                                                                              74

A.8    ICS WS Assemblies                                                                                                                                                                            74

Appendix B. Accession appliance altered environments                                                                                              75


The software declared in this chiral is advised to be used in the ESO VLT activity by ESO and accustomed alien contractors only.

While every anticipation has been taken in the development of the software and in the alertness of this documentation, ESO assumes no responsibility for errors or omissions, or for accident consistent from the use of the software or of the advice complete herein.

1.1              Purpose

The Arrangement Apparatus (called XXXX) is a fictitious instrument, which incorporates the basal functionality of VLT instruments.

It is declared to advice Chart Software developers, by accouterment them with examples of cipher and accompanying files. It is additionally used internally at ESO to validate, through a complete instrument, the Chart Accustomed Software bales afore a new VLT sw absolution is issued.


This certificate is the User Chiral of the Arrangement Instrument Ascendancy Software.

This amalgamation is absolutely based on VLT Chart Common Software packages, such as icb (base ICS, see [RD 16] and [RD 26]), boss (base OS, see [RD 17]), tpl (library for templates, see [RD 24]).pkgin (installation tool, see [RD 18]), ctoo (configuration tool, see [RD 25]) and stoo (startup tool, see [RD 19]).

This certificate can also be acclimated as arrangement for the User and Aliment Chiral of accession instrument.

1.2              Scope

This certificate covers alone the ascendancy allotment of the Template Apparatus Software. It does not accord with added genitalia of the Abstracts Flow, such as the pipeline.

It is aimed at operators of the apparatus and software developers, who are amenable for its accession and maintenance.

This certificate is also aimed at software developers, who allegation to advance Chart Software for VLT instruments or in accustomed chart according to VLT standards.

It is additionally meant for ESO engineers, amenable for the affiliation of new VLT Software releases, to validate the VLT Chart Accustomed Software packages.

1.3              Applicative Documents

The afterward documents, of the exact affair shown, anatomy a allotment of this certificate to the admeasurement authentic herein. In the accident of conflict amid the abstracts referenced herein and the capacity of this document, the capacity of this certificate shall be advised as a superseding requirement.



Document Number




[AD 01]



In preparation

DICB – Abstracts Interface Ascendancy Document

[AD 02]



In preparation

VLT Software Requirements Specification

[AD 03]



In preparation

VLT Software Programming Standards

[AD 04]




VLT Requirements for Accurate Instruments

[AD 05]




Guidelines for VLT applications.

[AD 06]




INS Software Specification

[AD 07]




INS Accustomed Software Specification

[AD 08]




ICD amid VCS and Archive

[AD 09]




ICD amid VCS and OH

1.4              Reference Documents

The afterward abstracts are referenced in this document.


Document Number




[RD 01]




VLT Accustomed Software Overview

[RD 02]




VLT Accustomed Software Accession Manual

[RD 03]



In preparation

Paranal Network/Computers Design Description

[RD 04]




LCU Accustomed Software User Manual

[RD 05]




Motor Ascendancy sw User Chiral API/ACI

[RD 06]




Motor Engineering Interface User Manual

[RD 07]




Central Ascendancy Software User Manual

[RD 08]




On Line Database Loader User Manual

[RD 09]




EVH User Manual

[RD 10]




Extended CCS User Manual

[RD 11]




Panel Editor User Manual

[RD 12]




INS Accustomed sw – oslx User Manual

[RD 13]




CCD Detectors Ascendancy Software User Manual

[RD 14]




FIERA Ascendancy Software User Manual

[RD 15]




IRACE-DCS User Manual

[RD 16]




Base ICS User Manual

[RD 17]




Base OS Stub User Manual

[RD 18]




Installation Apparatus for VLT Sw packages

[RD 19]




INS Startup Apparatus User Manual

[RD 20]




HOS – Sequencer User Manual

[RD 21]

P.Ward, S.Mellor, Yourdon Press,


Structured Development for Real-Time Systems

[RD 22]

J. Rumbaugh et. al., Prentice Hall,


Object-Oriented Modeling and Design

[RD 23]




Broker for Ascertainment Blocks User Manual

[RD 24]




INS Accustomed Software for Templates

[RD 25]


Dyson Animal Vacuum Diagram - Wiring Diagram  - dc24 parts diagram

Dyson Animal Vacuum Diagram – Wiring Diagram – dc24 parts diagram | dc24 parts diagram



INS Agreement apparatus User Manual

[RD 26]




Base ICS GUI User Manual

[RD 27]




Acceptance Analysis Plan Arrangement Document

[RD 28]




Tool for Automated Testing User Manual

1.5              Abbreviations and Acronyms

This certificate employs several abbreviations and acronyms to accredit concisely to an item, afterwards it has been introduced. The afterward annual is aimed to advice the clairvoyant in abandoning the continued acceptation of anniversary short expression:


Central Ascendancy Software


Central Processing Unit


Detector Ascendancy Software


European Southern Observatory


Flexible Image Transport Format


Graphical User Interface




Instrument Ascendancy Software


Instrumentation Software Package




Infrared Spectrograph and Array Camera


Instrument Workstation


Local Area Network


LCU Accustomed Software


Local Ascendancy Unit


Maintenance Software


Not Applicable


Object Modeling Technique


Object Oriented


Object Oriented Design


Observation Software


Random Admission Memory




Tool for Automated Testing


To Be Clarified


To Be Defined


Telescope Ascendancy Software


Time Interface Module


Time Reference System


(Portable) User Interface (Toolkit)


UltraViolet Visual Echelle Spectrograph


Very Large Telescope


Versa Bore Eurocard



<!– Accustomed footer –>

1.6              Glossary

No special analogue is alien in this manual

1.7              Stylistic Conventions

The following styles are used:


in the text, for commands, filenames, pre/suffixes as they accept to be typed.


in the text, for genitalia that accept to be commissioned with the complete agreeable before typing.


for examples.


in the examples, for genitalia that accept to be commissioned with the complete content afore typing.

d and italic are additionally acclimated to highlight words.

1.7.1                       Abstracts Flow and Processor Archetypal Diagrams

Data Flow and processor Archetypal Diagrams are based on De Marco/Yourdon characters for real-time systems [RD 21].

1.8              Allotment Conventions

This implementation follows the allotment conventions as categorical in [AD 03].

1.9              Problem Reporting/Change Request

The anatomy described in [RD 02] shall be used.

2         OVERVIEW

This affiliate gives a abbreviate overview of the apparatus and its architecture.

The blow of the chiral is organized as follows:

·  Affiliate 3 is the accession guide.

·  Affiliate 3.2.1 is the operator’s guide, which describes how to accomplish the apparatus at assorted levels.

·  Affiliate 5 is the programmer’s guide, which describes in detail specific items, such as ICS accessories and commands.

·  Affiliate 6 is the agreement guide, which describes in detail the agreement of the instrument.

·  Affiliate 7 contains the Aliment Guide

·  Affiliate 9 contains a FAQ and troubleshooting tips specific to the instrument

·  Affiliate 10 contains the annual of errors authentic by the instrument application

·  Affiliate 11 contains the chiral pages extracted from the source code.

·  Appendix A describes how to actualize from blemish a new instrument starting from the Arrangement Apparatus code

2.1              Accouterments architecture

2.1.1                       Devices

The Instrument consists of:

·         24 devices, controlled by ICS, on 2 LCUs:

q       14 motorized

q       1 arrangement lamp

q       1 bang

q       7 sensors

q       1 appropriate device

·         2 accurate detectors

q       1 bittersweet (IRACE controller)

q       1 optical (FIERA controller)

·         1 abstruse CCD camera (ACE controller)

2.1.2                       Computers

The computers on which the Instrument Software runs are apparent in Figure 1:

·         Apparatus Workstation (wxxxx) with ATM board

·         ICS LCU 1 (lxxics1) with TIM board

·         ICS LCU 2 (lxxics2) with TIM board

·         TCCD LCU (lxxtccd) with TIM board

·         IRACE UltraSparc (wxxirac) with ATM board

·         FIERA UltraSparc (wxxfier) with ATM board

Note: the ATM lath belongs to the accustomed agreement of Instrumentation Workstation and detectors UltraSparc. They are about not bare to run the Arrangement Apparatus Software and are mentioned actuality aloof to admonish that for complete instruments they should be present. The aforementioned appliance applies to the LCU TIM boards, whereby additionally in the case of complete instruments the attendance of the TIM lath is binding alone if the time attention bare on that LCU requires it.

2.1.3                       LANs

The Apparatus LAN follows the lay-out of VLT Ascendancy LANs (see [RD 03]) and is apparent in Figure 1

2.1.4                       Appropriate connections

The Arrangement Apparatus architectonics does not apprehend any appropriate connection.

Figure 1 Accouterments architecture

2.2              Software Architecture

The architectonics of the Ascendancy Software follows the VLT accustomed operational arrangement and is shown in Figure 2

Observation Blocks, created with the P2PP toolkit, are beatific to the Broker for Ascertainment Blocks (BOB), which executes sequentially the templates authentic in them.

In turn, each arrangement consists commonly of a arrangement of commands beatific to the OS Server. This action is amenable to acclimate the commands accustomed and catechumen them into commands for the controlled sub-systems (ICS, DCSs and TCS), demography care of the agnate replies.

At the end of an exposure, the OS Server action is additionally amenable for amalgamation all data/information into one FITS book and annal it, through the dedicated processes VOLAC/VCSOLAC/OLAS.

2.2.1                       Software Modules

The XXXX Apparatus Software consists of the afterward cmm modules (the prefix id xx corresponds to the Apparatus ID):


INS Module






Installation bore for the final ambition configuration




FITS dictionaries




ICS WS front-end and LCU simulator




ICS stand-alone GUI




ICS special device




OS Server








Observation Arrangement scripts



Observation Arrangement Signature Files




Instrument Agreement Files




Maintenance Arrangement scripts




Maintenance Arrangement Signature Files

At locations added than Paranal, the afterward cmm modules are additionally used:






ESO Garching


Installation and agreement bore for targets DEV_ESO and CM_FULL




Installation and agreement bore for targets DEV_MPE and INTEGRATION




Installation and agreement bore for targets DEV_OAT

2.2.2                       Environments

The Apparatus uses the afterward CCS environments:

·         wxxxx. IWS CCS ambiance (see RTAPENV)

·         lxxics1. ICS LCU1 LCC environment.

·         lxxics2. ICS LCU2 LCC environment.

·         lxxtccd. TCCD DCS LCC environment.

·         wxxfier. FIERA DCS CCS environment

·         wxxtcs. TCS simulation CCS ambiance (see TCS_ENVNAME)

2.2.3                       Standards

The Instrument Software is based on the accustomed bales broadcast with VLT Software releases. In particular:

·         TCCD DCS is based on the CCD Software (see [RD 13]).

·         IR DCS is based on the IRACE Software (see [RD 15]).

·         FIERA is based on the FIERA Software (see [RD 14]).

·         ICS is based on the icb amalgamation (see [RD 16] and [RD 26]).

·         OS is based on the BOSS amalgamation (see [RD 17])

·         Templates are based on the tpl amalgamation (see [RD 24]).

·         The Apparatus Software accession is based on the pkgin amalgamation ([RD 18])

·         The Apparatus Agreement is based on the ctoo amalgamation (see [RD 25])

·         The Apparatus Software Start-up/Shutdown is based on the stoo amalgamation (see [RD 19]).

Figure 2 Arrangement Apparatus Architecture


The installation uses the VLT accustomed apparatus pkgin (see [RD 18]).

3.1              Requirements

3.1.1                       Hardware

The following computers allegation be accessible (see area 2.1.2):

·         One Apparatus Workstation (HP, archetypal supported by the VLT sw, see [RD 02]).

Furthermore, a more complete functionality is accomplished if additionally the afterward computers (some or all of them) are available:

·         Two LCUs for ICS

·         One LCU for the TCCD

·         One Sparc LCU for IRACE

·         One Sparc LCU for FIERA

3.1.2                       Software

·         The adaptation of the UNIX Operating System installed on the IWS allegation be accordant with the VLT sw accession (see [RD 02])

·         The VLT sw APR2005 or college allegation be installed, according to [RD 02].

XXXX runs both on fullCCS or CCSLite.

3.2              Accession procedure

The whole accession action allegation be accomplished as user xxxxmgr and will booty at atomic 30 minutes.  It consists of the afterward steps:

1.)      Run the annual vccEnv and verify that the afterward CCS environments are accustomed and correctly configured in the ACC database:

wxxxx for the instrument

lxxics1 for ICS LCU 1

lxxics2 for ICS LCU 2

lxxtccd for TCCD DCS LCU

wxxfier for the FIERA SLCU

2.)      Verify that the ambiance variables INTROOT and INS_ROOT are defined.

% answer $INTROOT

% answer $INS_ROOT

3.)      Verify that the book $HOME/.bobrc exists and is a allegorical articulation to $INTROOT/config/xxins.bobrc. If not, run:

% ln –s $INTROOT/config/xxins.bobrc $HOME/.bobrc

4.)      Actualize an abandoned agenda as basis for the antecedent code, e.g.:

% mkdir $HOME/XXXXSource

5.)      Retrieve the accession module:

% cd $HOME/XXXXSource

% cmmCopy xxins [<version>]

Note: if the <version> constant is omitted, the aftermost adaptation in the cmm annal is retrieved.

Note 2: In the case of the Arrangement Instrument, consortia should retrieve and use the adaptation delivered with the aftermost VLT Software release, which has been  absolutely tested:


% version=`grep “@(#)” examples/insapp/XXXX/xxins/ChangeLog | awk ‘{print $4}’`

% cd $HOME/XXXXSource

% cmmCopy xxins $version

6.)      Alpha logMonitor, to analysis accessible errors during the installation:

% logMonitor &

7.)      Body and install the Apparatus Software

% pkginBuild xxins

During the accession the afterward directories are created:

INSTALL                 It contains logs and absurdity logs of the installation.

ICS                            It contains all ICS modules (see 2.2.1)

OS                             It contains all OS modules (see 2.2.1)

MS                            It contains all MS modules (see 2.2.1), in accurate xxmcfg, with the accomplished set of agreement files.

VLTSW_new           It contains an upgraded adaptation of modules, if any, acceptance to VLT sw releases. If all modules as from VLTROOT are taken, this agenda is missing.

8.)      At the end of the installation, analysis for absurdity logs in book $HOME/XXXXSource/INSTALL/pkginBuild.err.

3.2.1                       Accession at added locations

Normally an Apparatus Software User Chiral should call alone the accession procedure bare in the operational configuration, i.e. at the Observatory, area all computers acclimated by that apparatus are available. However, due to the attributes of the Arrangement Apparatus (example for all apparatus developers, alive at altered places beneath altered hw configurations), we accommodate additionally this section, which describes the action to be followed at added locations, e.g. a development site, area not necessarily the accomplished hw is available.

·         At development armpit MPE (example), whose agreement is:

o        All LCUs are available, but no hw is affiliated to them

o        The FIERA Sparc is not available

o        The TCS simulation amalgamation is used

The accession bore to be acclimated is xxmmpe. The action appropriately is:

% mkdir $HOME/XXXXSource

% cd $HOME/XXXXSource

% cmmCopy xxmmpe

% consign TARGET=DEV_MPE

% pkginBuild xxmmpe

·         At the Affiliation armpit (here MPE, as example), whose agreement is:

o        All LCUs are available, but no hw is affiliated to them

o        The FIERA Sparc is available

o        The TCS simulation amalgamation is used

The accession bore to be acclimated is xxmmpe. The action appropriately is:

% mkdir $HOME/XXXXSource

% cd $HOME/XXXXSource

% cmmCopy xxmmpe


% pkginBuild xxmmpe

·         At ESO Garching in the VLT Ascendancy Model, whose agreement is:

o        All LCUs are available, but no hw is affiliated to them

o        The FIERA Sparc is available

o        The VCM TCS is available

The accession bore to be acclimated is xxmgar. The action appropriately is:

% mkdir $HOME/XXXXSource

% cd $HOME/XXXXSource

% cmmCopy xxmgar

% consign TARGET=CM_FULL

% pkginBuild xxmgar


This affiliate is advised to accord instrument operators all advice they allegation to assignment with the Apparatus Software through its Graphical User Interface.

Note: For Instruments operational at Paranal, afterwards able log-in on the User Station, the CDE card is customized to the specific Apparatus to be operated, such that committed options to start-up/shutdown ascendancy processes or alone panels are provided. An archetype of such functionality is not accessible for the Arrangement Apparatus yet.

4.1              Arrangement Start-up

In the afterward it is affected that the accession (see affiliate 3) has been auspiciously completed and environments are active.

4.1.1                       Log-in

In adjustment to operate the apparatus properly, the user has to log-in on all terminals in the User Station as user xxxx.

Unless otherwise specified, all UNIX carapace commands, declared in the aing sections, accept to be typed on a xterm window alive on the Apparatus Workstation.

After log-in, check that the ambiance variables bare to run appropriately the Apparatus software are defined. To annual the ambiance variables that should be authentic type:

% osbEnvSet XXXX

The ambience of these variables is done aural the book $INTROOT/config/xxins-misc-all.env. This book is automatically sourced whenever you login or any new xterm is opened. Accomplish abiding that this is the case.

4.1.2                       Telescope availability

If TCS is supposed to be used, analysis with the telescope abettor that it is alive and ONLINE, afore starting the Chart Software.

In a development environment, area no real telescope is available, the TCS simulation amalgamation is used. Run:

% xxinsStart –panel OS_ENGINEERING

Figure 3  OS Engineering panel

The OS engineering console (see Figure 3) pops-up.

·         If the accompaniment of TCS Simulator is not ONLINE, columnist the on STARTUP: afterwards a while the accompaniment should change to ONLINE (if not, check, e.g. with scanei, that the browse arrangement amid wxxxx and wxxtcs works properly).

·         Alpha the TCS Sim. GUI

·         From the TCS Simulation GUI, alpha the TCS Ascendancy and TCS User Panel

·         In the TCS User Panel, columnist Preset Name acme and delay till the aphotic gray background blush of the RA and DEC fields in the TCS Ascendancy Console disappears.

·         Close TCS Simulation GUI, TCS Ascendancy and TCS User Panel.

·         Simulate TCS auto-guiding running, by selecting in the OS engineering console the menu item

Simulation à TCS à Auto-guider à Stop and afresh Start

·         Simulate TCS alive eyes running, by selecting in the OS engineering console the menu item

Simulation à TCS à Alive Eyes à Stop and afresh Start

·         Close the OS engineering console (File à quit).

4.1.3                       Midas availability

Normally the Chart Software does not allegation any abstracts abridgement amalgamation installed and alive on the Instrument Workstation. The alone barring is back such a amalgamation is bare to perform on-line abstracts abridgement operations, whose after-effects are afresh acclimated by the Chart Software. Alike in this case, commonly no ascendancy process accesses the on-line abstracts abridgement package, because this should be done at templates level.

Some XXXX templates allegation a abstracts abridgement amalgamation and Midas is acclimated for this purpose. Midas APR2005 allegation appropriately be installed.

If this is not accessible to run Midas, for whatever reason, afresh templates can still be accomplished (e.g. for analysis purposes) by ambience the ambiance capricious DEBUG_MIDAS (access to Midas from templates is disabled):

%export DEBUG_MIDAS=1

4.1.4                       Apparatus Software Start-up

The arrangement start-up is based on the accustomed startup apparatus stoo (see [RD 19]).

After a new installation, or whenever some start-up agreement constant needs to be changed, blazon on an xterm window:

% xxinsStartup

The Start-up GUI (Figure 4) pops-up. This console allows defining which sub-systems are accessible and at which akin of simulation they should start, in accurate if they accept to admission the LCUs or they should simulate the LCU functionality at WS level. It additionally allows allegorical which GUIs will be automatically started.

Figure 4 Startup panel

Finally, by acute the on Start, all authentic GUIs and sub-systems ascendancy processes are started. A log window shows the assorted phases of the startup procedure.

When successfully completed, the log window disappears and all sub-systems should be in accompaniment STANDBY.

If any error occurs, the log window charcoal alive and shows the acumen of the failure.

Once the start-up agreement is defined, the apparatus can be started, or re-started, by directly accounting on an xterm window:

% xxinsStart

This command has the aforementioned aftereffect of acute the Start on in the start-up GUI.

4.1.5                       Begin of operations

Before actuality able to accomplish the apparatus and booty exposures, it has to be ONLINE.

On the OS Ascendancy panel (see Figure 5), analysis the all-around State. If it is not ONLINE, select the card option

Instrument à ONLINE.

Please delay till the all-around Accompaniment turns to ONLINE.

Figure 5 OS Ascendancy panel

4.1.6                       End of operations

After operating the instrument, whenever it is advancing to leave it abandoned for continued time (e.g. during daytime), the apparatus has to be brought to a safe state, additionally called STANDBY.

On the OS Ascendancy panel (see Figure 5), baddest the card option

Instrument à STANDBY.

Please delay till the all-around Accompaniment turns to STANDBY.

4.2              Arrangement Shut-down

Type on a xterm window:

% xxinsStop

All control processes and panels are terminated.

4.3              User Station

Figure 6 User Station awning #1

Figure 7 User Station awning #2

4.4              Observations with Templates

This is the usual way to do observations at the VLT.

In this area we allegorize a simple archetype of celebratory run. We run the Ascertainment Block (OB) authentic in the book XXXX_gen_tec_SelfTest.obd. This OB executes sequentially all templates defined for XXXX. It is declared to be used as self-test action to verify that the apparatus is alive appropriately (see additionally [RD 24]).

Normally Ascertainment Blocks (OBs) exercise all apparatus sub-systems, as able-bodied as the telescope (if declared available).

It is appropriately VERY IMPORTANT to verify the cachet of apparatus and telescope afore starting this OB, to abstain damages.

OBs are prepared through the P2PP apparatus on a abstracted Workstation (wxxdhs).

In adjustment to run OBs:

1.)      Baddest the OB to be accomplished in the P2PP GUI

2.)      Amount this OB in the BOB GUI (File à Amount Obs à 1).

See sections 5.15 and 8.2.3 for a added abundant description of the available templates.

4.5              Alarms

No alarms are at present authentic for the instrument.



Operator’s Action

4.6              Abstracts files location

All abstracts files used and/or generated by the Apparatus Software are amid beneath $INS_ROOT as follows:

·         Agreement files:


·         Image FITS files, after-effects of exposures:


·         Bureaucracy files:

Dyson Dc12 Parts Diagram Dyson Dc12 All Floors Parts – Meze Blog ..

Dyson Dc12 Parts Diagram Dyson Dc12 All Floors Parts – Meze Blog .. | dc24 parts diagram


<type> is one of the following: REF, INS, DET, TARG

·         Arrangement Signature File:


·         Ascertainment Block Description files:


4.7              Engineering

4.7.1                       OS Engineering GUI

The OS Engineering GUI (see Figure 3) allows to startup/shutdown, change accompaniment and startup the stand-alone GUI of distinct sub-systems, e.g. whenever there are problems with specific sub-systems. To alpha it up:

%xxinsStart –panel OS_ENGINEERING

4.7.2                       ICS Engineering GUI

While the detectors and the telescope stand-alone GUIs are provided by the associated standard software packages, the ICS GUI is necessarily specific to the apparatus (see Figure 8). It is based on icbpan (see [RD 26]). To alpha it up:

Figure 8 ICS Engineering GUI


This allotment of the certificate provides a description of the programmatic interface of the Instrument Software.

For bodies accepting no acquaintance with Chart software yet, it is recommended, although not necessary, before starting to apprehend this section, aboriginal to accept a attending at the alternate acceptance of the apparatus at affiliate 4 and possibly try it out. It can advice to get a bigger abstraction of how Instrumentation software works.

5.1              Apparatus Modes

XXXX defines the afterward modes:

·         IR_IMAGING. Its purpose is to take images in the infrared.

Subsystems complex are IRACE, ICS and TCS.

·         GUIDING. Its purpose is to perform allegorical operations.

Subsystems complex are TCCD, ICS and TCS.

·         IR_SPECTROSCOPY. Its purpose is to booty spectra in the infrared.

Subsystems complex are IRACE, TCCD, ICS and TCS.

In this approach two complete exposure, one for anniversary detector (IR and TCCD), can be accomplished in a semi-parallel way, i.e. the exposures on the two detectors are started at altered credibility in time, about there is a time interval, during which both exposures are running. For added advice see [RD 17].

·         OPT_IMAGING. Its purpose is to take images in the optical range.

Subsystems complex are FIERA, ICS and TCS.

5.2              Subsystems Identifiers

OS allegation be able to accessory one or more sub-systems to anniversary short-FITS keyword associated to a SETUP command. The clarification belief are authentic in the agreement file $INS_ROOT/SYSTEM/COMMON/CONFIGFILES/xxmcfgINS.cfg.

The table beneath provides a summary.


FITS Prefix













5.3              ICS Software Devices

The ICS Software accessories are authentic in the agreement book $INS_ROOT/SYSTEM/COMMON/CONFIGFILES/xxmcfgINS.cfg:







FITS Prefix

ICB Class




Sample lamp








Sample shutter








Sample ADC device








Sample depolarizer








Sample derotator








Sample filter wheel








Sample grating wheel








Sample mirror caster /slide








Sample slide








Sample wheel







Sample slide








Sample wheel








Sample dekker (two jaws)








Sample aperture (two jaws)








Sample slit wheel/slide








Sample tilt device








Cryostat sensor








Pressure sensor








Cryostat temp. sensor








Cooling control sensor








Digital sensors








Humidity sensor








Temperature sensor








Sample special device




Special device


Some remarks:

·         All automated accessories use ESO accustomed motion ascendancy (Maccon) and amplifier boards.

·         All motors with affiliated accession do so with a two footfall complete motion to affected accessible backfire problems (see [RD 16]).

·         Accessories focu and rot use a beeline blueprint for user units against encoder units conversion.

·         Accessories dekk and aperture accept two motors each

·         Accessory dpor rotates continuously back asked to move.

·         Accessory adc1 uses ADC tracking approach (see [RD 16]).

·         Accessory drot uses assorted tracking modes  (see [RD 16]).

·         Accessory fcs is affiliated to the hw accessory ADAM 4017 (RS-485)

·         Accessory baro is affiliated to the hw accessory VAISALA PTB220B (RS-485)

·         Accessory fctc is affiliated to the hw accessory OMEGA CN77000 (RS-485)

·         Accessory ccc1 is affiliated to the ESO accustomed chiffonier cooling hw accessory (RS-232)

·         Accessory dis1 is affiliated to the ESO accustomed Acromag agenda I/O board

·         Accessory temp is affiliated to the ESO accustomed temperature accretion assemblage Esters DC24 (RS-232).

5.3.1                       ICS Appropriate devices

The alone special accessory is yyyy. It is a simple sample software accessory that has two bifold attributes in its OLDB point. These two bifold attributes can be set with the SETUP command (with FITS keywords INS.MIRR2.DATA1 and INS.MIRR2.DATA2).  These ethics can be retrieved with the STATUS command.

5.3.2                       ICS Assemblies

The ICS assemblies are authentic in the agreement file $INS_ROOT/SYSTEM/COMMON/CONFIGFILES/xxmcfgINS.cfg:








All pre-slit devices





All accessories used in the bittersweet arm





All accessories used in the optical arm





Instrument mode



See 5.1



Light path








5.4              Exposures

5.4.1                       Acknowledgment types

The Acknowledgment types accustomed are those authentic by the accustomed IRACE, FIERA and TCCD Software bales (see corresponding manuals).

5.4.2                       Acknowledgment Id

The OS acknowledgment Id is a complete accumulation amount abnormally anecdotic an acknowledgment from the OS point of view.

The aboriginal SETUP command allegation be issued with the –expoId 0 parameter, and the Exposure Id alternate by the acknowledged achievement of this command allegation be acclimated for every added SETUP command, as able-bodied any added command (START, END, PAUSE, CONTINUE, ABORT, WAIT, STATUS) apropos to the aforementioned exposure.

5.4.3                       Acknowledgment Status

OS keeps clue of the all-around acknowledgment status, demography into annual the accustomed cachet of each detector and accessible alongside exposures. It is stored in the OLDB aspect <alias>xxo:exposure.expStatus and its ethics are those authentic by the BOSS amalgamation (see [RD 17]).

5.4.4                       Acknowledgment Parallelism

In mode IR_SPECTROSCOPY, area two detectors are complex (IRDCS and TCCD), the apparatus has the aforementioned akin of exposures accompaniment accurate by BOSS (see [RD 17]).

5.4.5                       Acknowledgment Life Cycle

1.        An acknowledgment is initially authentic with a SETUP command with

·         -expoId 0

·         INS.MODE keyword present (as allotment of the –function constant or aural a bureaucracy book authentic with the –file parameter)

2.        A new Acknowledgment Id is generated and alternate in the reply. Every Additional SETUP command shall accommodate this Id.

5.4.6                       Acknowledgment execution

The afterward is an archetype of arrangement of commands bare to ascertain and assassinate exposures:

14   ß alternate acknowledgment Id



5.5              Operational States

The instrument all-around accompaniment is the everyman accompaniment of its sub-systems and is recorded in the OLDB aspect <alias>xxo:status.state

The table below gives the annual of accessible states and the commands (uppercase) and/or scripts (italics) bare to change the accustomed state.



















5.6              Commands

According to the accustomed VLT Chart Software architecture, all commands to the apparatus allegation be beatific to the OS Server action xxoControl. The commands available are listed in the Command Analogue Table book $INTROOT/CDT/xxoControl.cdt

5.6.1                       OS Appropriate commands

In accession to the accustomed commands authentic by BOSS, OS accouterments the appropriate command TESTCMD (not in the present release).

The sole purpose of TESTCMD is to appearance an archetype how to add a command to an OS based on BOSS. See additionally Appendix AA.2.

5.6.2                       ICS Appropriate commands


5.6.3                       DCS Appropriate commands


5.7              Tcl libraries

The tcl class library for templates xxoseq uses the abject classes provided by the accustomed VLT library for templates tpl (see [RD 24]). See additionally Appendix AA.4.

This library is registered in the BOB agreement book ($INTROOT/config/xxins.bobrc)

5.8              Dictionaries

The Instrument Software uses several dictionaries to handle bureaucracy keywords and to actualize FITS files with able header:

·         ESO-VLT-DIC.CCDDCS for the keywords acceptance to the TCCD sub-system

·         ESO-VLT-DIC.FCDDCS for the keywords acceptance to the FIERA sub-system

·         ESO-VLT-DIC.IRACE for the keywords acceptance to the IRDCS sub-system

·         ESO-VLT-DIC.TCS for the keywords acceptance to the TCS sub-system

·         ESO-VLT-DIC.XXXX_ICS for the keywords belonging to the ICS sub-system

·         ESO-VLT-DIC.OSB for the accustomed keywords acceptance to the OS sub-system

·         ESO-VLT-DIC.XXXX_OS for the appropriate keywords acceptance to the XXXX OS sub-system

·         ESO-VLT-DIC.DPR for the keywords acceptance to templates

·         ESO-VLT-DIC.TPL for the keywords acceptance to templates

·         ESO-VLT-DIC.OBS for the keywords acceptance to templates

The following dictionaries are instead not acclimated at runtime, but for accession and/or startup purposes:

·         ESO-VLT-DIC.ICB_CFG for the accustomed keywords acceptance to the ICS configuration

·         ESO-VLT-DIC.XXXX_CFG for the appropriate keywords acceptance to the apparatus specific configuration

·         ESO-VLT-DIC.STOO_CFG for the keywords acclimated by the startup apparatus stoo

All instrument specific dictionaries are complete in bore dicXXXX.




5.9              Alias files

No alias book is used.

5.10          Agreement files

After installation, all agreement files acclimated by the Apparatus Software are amid in the directory $INS_ROOT/SYSTEM/COMMON/CONFIGFILES.

See affiliate 6 for added abundant advice on the capacity of the alone files.

5.11          Bureaucracy files and keywords

5.11.1                   OCS keywords

OS treats these keywords. The apparatus does not apparatus any appropriate OCS keyword: it uses alone accustomed keywords authentic by the BOSS amalgamation (see [RD 17]) and declared in the concordance ESO-VLT-DIC.OSB.

5.11.2                   INS keywords

OS and ICS treat these keywords.

The table below shows the keywords used:

Setup keyword







Instrument mode

See 5.1













ADC mode





Start/Stop affiliated rotation













Right Ascension


Start position angle

Derotator mode

Offset basis for STAT mode



See xxmcfgINS.cfg




Filter name

See xxmcfgINS.cfg


Dyson parts dc 12 dc 12 motor assembly schematic vert wonderful here ..

Dyson parts dc 12 dc 12 motor assembly schematic vert wonderful here .. | dc24 parts diagram





Grating name

Central wavelength

See xxmcfgINS.cfg




Mirror name

See xxmcfgINS.cfg




Slide position name

See xxmcfgINS.cfg




Slide position name

See xxmcfgINS.cfg




Focus position

See xxmcfgINS.cfg




Position angle

See xxmcfgINS.cfg




Decker length

See xxmcfgINS.cfg




Slit width

See xxmcfgINS.cfg




Position name

See xxmcfgINS.cfg




Tilt position

See xxmcfgINS.cfg






Sample special accessory bureaucracy keyw.

Sample special accessory bureaucracy keyw.

any float number

any float number


·         All automated accessories with encoder can additionally be addressed to a specific complete or about encoder amount appliance the keywords .ENC and .ENCREL (e.g. INS.FILT1.ENC 15000 or  INS.FILT1.ENCREL 1000). The acceptance of these keywords is about limited to engineering/maintenance operations.

5.11.3                   DCS keywords

OS and DCS treat these keywords.

The apparatus does not apparatus any appropriate DCS keyword: it uses alone keywords authentic by the accustomed DCS bales IRACE (see [RD 15]), FIERA (see [RD 14]) and CCD (see [RD 13]).

5.12          FITS files

Images, as result of exposures, are accounting on WS deejay in FITS architectonics (see [AD 01]).

An archetype of complete FITS attack is accustomed in 11.8.1

The VLT on-line Annal is a of anniversary new complete book accessible for archiving, according to the accustomed agreement authentic in [AD 08].

5.13          Public on-line database attributes

This area is applicative alone to those instruments, which are declared to assignment in affiliation with added instruments (e.g. through Super-OS).

No OLDB attribute is about available.

5.14          Operational logs

An archetype of operational log in FITS architectonics is accustomed in 11.9.1.

5.15          Templates

This section describes briefly the templates implemented for the instrument.

5.15.1                   Accretion Templates

·         XXXX_irimg_acq. It is the accretion arrangement for the IR_IMAGING Mode.

·         XXXX_irspec_acq. It is the accretion arrangement for the IR_SPECTROSCOPY Mode.

·         XXXX_optimg_acq. It is the accretion arrangement for the OPT_IMAGING Mode.

5.15.2                   Arrangement Templates

·         XXXX_optimg_cal_bias. It executes bent exposures with the FIERA DCS in OPT_IMAGING Mode

·         XXXX_optimg_cal_flatfield. It accomplished collapsed acreage exposures with the FIERA DCS in OPT_IMAGING Mode

·         XXXX_optimg_cal_focus. It checks the FIERA camera focus in OPT_IMAGING Mode

·         XXXX_optimg_cal_linearity. It does a CCD dent breadth analysis with the FIERA DCS in OPT_IMAGING Mode

5.15.3                   Ascertainment Templates

·         XXXX_irimg_obs_exp. It performs accustomed exposures in IR_IMAGING Mode

·         XXXX_irspec_obs_exp. It performs accustomed exposures in IR_SPECTROSCOPY Mode

·         XXXX_optimg_obs_exp. It performs accustomed exposures in OPT_IMAGING Mode


This area is aloof to engineers amenable of the apparatus maintenance.

It describes where apparatus agreement ambit are stored and the way, in which they can be changed, adored and kept beneath agreement control.

The instrument agreement is based on the Agreement Apparatus (ctoo, see User Chiral [RD 25]).

In adjustment to be able to accomplish the apparatus appropriately and reliably, the apparatus configuration ambit allegation be kept beneath agreement control. For this reason, all files complete configuration constant ethics for the final ambition are put in one distinct committed cmm module, alleged xxmcfg (directory config).

After installation, all agreement files are amid in $INS_ROOT/SYSTEM/COMMON/CONFIGFILES, except IRACE agreement and alarm files, amid under $INS_ROOT/SYSTEM/MISC/IRACE.

The files complete advice accompanying to the apparatus agreement are:

·         xxmcfgCONFIG.cfg. It is the master book for the ctoo apparatus and contains basal advice about which added files are complex and for what purpose.

·         xxmcfgINS.cfg. It contains most of the Apparatus agreement information.

·         xxmcfgSTART.cfg. It contains only the startup advice (e.g. which subsystems are accessible and at which level of simulation they should work) and is acclimated by xxinsStartup, xxinsStart and xxinsStop, all based on the Startup Apparatus stoo (see [RD 19]).

·         xxmcfgTARGET.cfg. It contains the agreement advice for a specific ambition (e.g. for the VLT Control Model).

·         xxmcfgTEST.cfg. It contains the agreement advice for alive cocky analysis scripts (see chiral folio of inscSelfTest)

·         xxmcfg*M.dbcfg. Anniversary of these files contains the agreement of one motor controlled by ICS. They accept been created appliance the VLT Motor Engineering Interface Apparatus (motei, see [RD 06]).

·         Added *.cfg and *.dbcfg files are created and acclimated by the accustomed DCS and Real-Time Affectation (rtd/irtd) packages.

6.1              Change Apparatus Agreement Parameters

For agreement changes to booty effect, they accept to be activated to the files stored in the $INS_ROOT. 

Once a new abiding agreement has been found, this agreement has to be stored in the xxmcfg module, as this is the alone way to save assuredly any change to the apparatus configuration.

The accustomed arrangement of operations, which acquiesce befitting ascendancy over changes to the apparatus configuration, is:

1.        Edit the files in the $INS_ROOT, that accommodate the ambit to be modified:

·         use motei for the xxmcfg*M.dbcfg files

·         use a accustomed argument editor for the *.cfg files (they are ASCII files in PAF format).

2.        If the changes done affect ICS LCU devices, run:

% icbConfigSet XXXX

3.        Analysis the Apparatus in the new configuration

4.        Repeat the accomplish aloft as abounding times as needed.

5.        At the end of the agreement change, one of the afterward accomplish MUST be performed to accumulate able agreement control:

a)       The agreement changes are rejected.

Re-install the latest well-known agreement stored in the xxmcfg module:

% cmmCopy xxmcfg

% cd xxmcfg/src

% accomplish apple-pie all man install

% icbConfigSet XXXX

b)       The agreement changes are accepted:

Archive the new agreement in the xxmcfg module:

% ctooConfigArchive XXXX

ctooConfigArchive (should be accessible additionally from a GUI menu) executes the afterward steps:

·         cmmModify xxmcfg

·         archetype the agreement files from $INS_ROOT to the xxmcfg bore (as authentic by the CONFIG.ARCHIVE.* keywords, see [RD 25]).

·         cmmArchive xxmcfg

When a complete software (re-)installation on the IWS is activity to be done, a snapshot of the accustomed instrument agreement (as declared aloft in point 5b) MUST be archived afore starting the new installation.

7         TEST

As authentic in [AD 06], an Instrument Software amalgamation allegation accommodate analysis procedures and scripts to exercise the Apparatus functionality and accomplish automated corruption tests.

The set of procedures and scripts acclimated is declared in detail in [RD 27]. They are based on the accustomed analysis arrangement accurate by the Chart Common Software (see [AD 07]).

The automated corruption tests are based on the accustomed Apparatus for Automated Testing (tat, see [RD 28]).


8.1              General

8.1.1                       Bore xxins

This bore is committed to the accession of the apparatus software on the final target.

·         src

·         xxinsStartup. Calligraphy acclimated to startup the apparatus software afterwards a clean or some above modifications to the hw agreement (panel pops-up acceptance to configure the simulation levels).

·         xxinsStart. Calligraphy commonly acclimated to startup the accomplished apparatus software or sub-systems. Simulation levels are kept as defined in the agreement files xxmcfgSTART.cfg.

·         xxinsStop. Calligraphy commonly acclimated to stop the whole apparatus software or sub-systems.


·         lxxics1. Arrangement agenda to be taken by pkginBuild back architecture ambiance lxxics1

·         lxxics2. Arrangement agenda to be taken by pkginBuild back architecture ambiance lxxics2

·         lxxtccd. Arrangement agenda to be taken by pkginBuild back architecture ambiance lxxtccd

·         wxxxx. Arrangement agenda to be taken by pkginBuild back architecture ambiance wxxxx

·         wxxtcs. Arrangement agenda to be taken by pkginBuild back architecture ambiance wxxtcs

·         config

·         xxins.bobrc. Agreement book for BOB

·         xxins-misc-all.env. Book complete environment capricious definitions, sourced automatically at login (if CDE used)

·         xxinsINSTALL.cfg. Capital agreement book for pkginBuild. It includes:

·         xxinsINSTALL_TCSSIM.cfg. It contains definitions to be acclimated alone for targets area the TCS simulation amalgamation is used.

·         xxinsINSTALL_VLTSW.$VLTSW_RELEASE cfg. It contains definitions accompanying to versions of modules altered to those delivered with the VLT Software absolution authentic in $VLTSW_RELEASE

8.1.2                       Bore dicXXXX

This bore contains the apparatus specific dictionaries.

·         src

·         dicXXXX_CFG.txt. It contains configuration keywords acclimated in xxmcfgINS.cfg for the appropriate accessory yyyy.

·         dicXXXX_ICS.txt. It contains run-time keywords acclimated by ICS

·         dicXXXX_OS.txt. It contains run-time keywords acclimated by OS

8.2              OS

8.2.1                       Bore xxo

This bore contains the cipher for the OS processes.

·         src

·         xxoControl.C It contains the capital of the OS front-end action xxoControl.

·         xxoSERVER.C. It contains the cipher for class xxoSERVER, sub-class of bossSERVER. In particular, adjustment SubsystemInterfaces creates instances of the able interface chic for anniversary sub-system acclimated by OS.

·         xxoExpoCtrl.C. It contains the overloading of bossSERVER methods StartPostProc and StartPostProc. They are aloof examples of bossSERVER adjustment overloading.

·         include

·         xxoErrors.h. It defines macros for the module errors

·         xxoPrivate.h. It contains definitions acclimated by xxoControl

·         xxoSERVER.h. It contains definitions for the chic xxoSERVER

·         CDT

·         xxoControl.cdt Command Analogue Table for the action xxoControl

·         ERRORS

·         xxo_ERRORS Analogue of errors for this module

·         config

·         xxoTccd.det Detector Bureaucracy Book acclimated for apparatus approach GUIDING

·         dbl

·         xxoSERVER.class. dbl chic defining the branches for the sub-systems used.

·         xxo.db. dbl accommodate book defining the accomplished OS annex of the OLDB. This book allegation be included in wxxxx/dbl/DATABASE.db

8.2.2                       Bore xxopan

This bore contains the cipher for the OS GUIs.

·         src

·         xxopanControl.pan Book created with the VLT console editor for the OS Ascendancy GUI (see Figure 5)

·         xxopanControl.doc. Antecedent book for the panel xxopanControl chiral page

·         xxopanStatus.pan Book created with the VLT panel editor for the OS Cachet GUI. Dummy.

·         xxopanStatus.pan. Antecedent book for the panel xxopanStatus chiral page

·         xxopanEngineering.pan. Book created with the VLT console editor for the OS Engineering GUI (see Figure 3)

·         xxopanEngineering.pan. Antecedent book for the panel xxopanEngineering chiral page

·         library xxopanPrivate

·         xxopanMisc.tcl. It contains miscellaneous action acclimated aural OS GUI panels.

·         xxopanStateSubSystems_uifClass.tcl. VLT panel editor chic acclimated aural xxopanEngineering. It contains:

·         xxopanStateIcs_uifClass.tcl. VLT console editor chic acclimated to act on ICS

·         xxopanStateIrDcs_uifClass.tcl VLT console editor chic used  to act on IRDCS

·         xxopanStateOs_uifClass.tcl VLT console editor chic acclimated to act on xxoControl

·         xxopanStateTccd_uifClass.tcl VLT console editor chic acclimated to act on TCCD

·         xxopanStateFiera_uifClass.tcl VLT console editor chic acclimated to act on FIERA

·         xxopanStateTcs_uifClass.tcl VLT console editor chic acclimated to act on VLTISIM

8.2.3                       Bore xxotsf

This bore contains the files accidental to the Apparatus Package, bare by the DFS, and in accurate P2PP.

·         src

The VLT annual oslxCompileTsf is acclimated by make to accomplish the .tsf files (directory config) from the tsfx files.

·         XXXX_irimg_acq.tsfx. TSF antecedent book for Target Accretion in IR_IMAGING mode

·         XXXX_irimg_obs_exp.tsfx. TSF antecedent book for accustomed observations in IR_IMAGING mode

·         XXXX_irspec_acq.tsfx. TSF antecedent book for Target Accretion in IR_SPECTROSCOPY mode

·         XXXX_irspec_obs_exp.tsfx. TSF antecedent book for accustomed observations in IR_SPECTROSCOPY mode

·         XXXX_optimg_acq.tsfx. TSF antecedent book for Target Accretion in OPT_IMAGING mode

·         XXXX_optimg_cal_bias.tsfx. TSF antecedent book for bent exposures in OPT_IMAGING mode

·         XXXX_optimg_cal_flatfield.tsfx. TSF antecedent file for collapsed acreage exposures in OPT_IMAGING mode

·         XXXX_optimg_cal_focus.tsfx. TSF antecedent book for focus analysis in OPT_IMAGING mode

·         XXXX_optimg_cal_linearity.tsfx. TSF antecedent file for breadth analysis in OPT_IMAGING mode

·         XXXX_optimg_obs_exp.tsfx. TSF antecedent book for accustomed observations in OPT_IMAGING mode

·         config

·         XXXX.isf Apparatus Arbitrary File, to be included in the Apparatus Amalgamation for P2PP

·         include

·         xxotsfDET_EXPLEVEL.tsfx. TSF accommodate file. It contains the afterward keywords:


·         xxotsfINS_FILT.tsfx. TSF accommodate file. It contains the afterward keywords:


·         xxotsfINS_MODE.tsfx. TSF accommodate file. It contains the afterward keywords:


·         xxotsfIRDET.tsfx. TSF accommodate file. It contains DET1 keywords for IRDCS and includes:

·         xxotsfIRDET_DIT.tsfx. TSF accommodate file. It contains the afterward keywords:



·         xxotsfSCCD.tsfx. TSF accommodate file. It contains DET3 keywords for FIERA and includes:






·         xxotsfISCCD_BIN.tsfx. TSF accommodate file. It contains the afterward keywords:



·         xxotsfISCCD_DIT.tsfx. TSF accommodate file. It contains the afterward keywords:


·         xxotsfISCCD_DIT_LIST.tsfx. TSF accommodate file. It contains the afterward keywords:


·         xxotsfISEQ.tsfx. TSF accommodate file. It contains the afterward keywords:


·         xxotsfITCCD_DIT.tsfx. TSF accommodate file. It contains the afterward keywords:


·         xxotsfITEL.tsfx. TSF accommodate file. It contains the afterward keywords:













8.2.4                       Bore xxoseq

This bore contains the Arrangement Calligraphy files, as able-bodied as the Reference Bureaucracy files acclimated by Templates and analysis OBs.

·         src

·         XXXX_acq.seq. Arrangement Calligraphy book acclimated by accretion templates in IR_IMAGING and OPT_IMAGING mode

·         XXXX_irimg_obs_exp.seq. Arrangement Calligraphy file acclimated by accustomed ascertainment templates in IR_IMAGING mode

·         XXXX_irspec_acq.seq. Arrangement Calligraphy book used by accretion templates in IR_SPECTROSCOPY mode

·         XXXX_irspec_obs_exp.seq. Arrangement Calligraphy file acclimated by accustomed ascertainment templates in IR_SPECTROSCOPY  mode

·         XXXX_optimg_cal_bias.seq. Arrangement Calligraphy file acclimated by bent arrangement in OPT_IMAGING mode

·         XXXX_optimg_cal_flatfield.seq. Arrangement Script book acclimated by collapsed acreage arrangement in OPT_IMAGING mode

·         XXXX_optimg_cal_focus.seq. Arrangement Calligraphy file acclimated by focus analysis arrangement in OPT_IMAGING mode

·         XXXX_optimg_cal_linearity.seq. Arrangement Script book acclimated by breadth analysis arrangement in OPT_IMAGING mode

·         XXXX_optimg_obs_exp.seq. Arrangement Calligraphy file acclimated by accustomed ascertainment templates in OPT_IMAGING mode

·         xxoseqGenTecSelfTest.txt. Acclimated in the Makefile to body the cocky analysis obd XXXX_gen_tec_SelfTest.obd and abundance it in the agenda config.

·         xxoseqTsfList.txt. Acclimated in the Makefile to build the analysis OBs for anniversary alone arrangement and abundance them in the directory config.

·         library xxoseq

·         xxoseqICS.tcl. Defines methods for the itcl chic xxoseqICS, sub-class of tplICS

·         config

·         XXXX_acq.ref Reference Bureaucracy Book acclimated in accretion templates in IR_IMAGING and OPT_IMAGING mode

·         XXXX_irimg_obs_exp.ref. Reference Bureaucracy File acclimated by accustomed ascertainment templates in IR_IMAGING mode

·         XXXX_irspec_acq.ref. Reference Bureaucracy Book used by accretion templates in IR_SPECTROSCOPY mode

·         XXXX_irspec_obs_exp.ref. Reference Bureaucracy File acclimated by accustomed ascertainment templates in IR_SPECTROSCOPY  mode

·         XXXX_optimg_cal_bias.ref. Reference Bureaucracy File acclimated by bent arrangement in OPT_IMAGING mode

·         XXXX_optimg_cal_flatfield.ref. Reference Setup Book acclimated by collapsed acreage arrangement in OPT_IMAGING mode

·         XXXX_optimg_cal_focus.ref. Reference Bureaucracy File acclimated by focus analysis arrangement in OPT_IMAGING mode

·         XXXX_optimg_cal_linearity.ref. Reference Setup Book acclimated by breadth analysis arrangement in OPT_IMAGING mode

·         XXXX_optimg_obs_exp.ref. Reference Bureaucracy File acclimated by accustomed ascertainment templates in OPT_IMAGING mode

·         XXXX_gen_tec_SelfTest.obd. OB Description File to analysis all templates

·         XXXX_irimg_acq.obd OB Description Book to test arrangement XXXX_irimg_acq

·         XXXX_irimg_obs_exp.obd OB Description Book to analysis arrangement XXXX_irimg_obs_exp

·         XXXX_irspec_acq.obd OB Description Book to test arrangement XXXX_irspec_acq

·         XXXX_irspec_obs_exp.obd OB Description Book to analysis arrangement XXXX_irspec_obs_exp

·         XXXX_optimg_acq.obd OB Description Book to test arrangement XXXX_optimg_acq

·         XXXX_optimg_cal_bias.obd OB Description Book to analysis arrangement XXXX_optimg_cal_bias

·         XXXX_optimg_cal_flatfield.obd OB Description Book to analysis arrangement XXXX_optimg_cal_flatfield

·         XXXX_optimg_cal_focus.obd OB Description Book to analysis arrangement XXXX_optimg_cal_focus

·         XXXX_optimg_cal_linearity.obd OB Description Book to analysis arrangement XXXX_optimg_cal_linearity

·         XXXX_optimg_obs_exp.obd OB Description Book to analysis arrangement XXXX_optimg_obs_exp

8.3              ICS

8.3.1                       Bore xxi

It contains the cipher and files for ICS WS part.

·         src

·         xxiConfigSet.tcl. Tcl calligraphy alleged by icbConfigSet to set the yyyy appropriate accessory agreement values in the ICS LCU 2 OLDB (file $VLTDATA/config/lxxics2.dbcfg)

·         xxiControl.C It contains the capital for the ICS WS front-end action xxiControl

·         xxiCtrlMAIN_HANDLER.C It contains the cipher for the chic xxiCtrlMAIN_HANDLER, sub-class of ic0CtrlMAIN_HANDLER. It overloads the adjustment NewServer, bare in adjustment to actualize an instance of chic xxiSERVER

·         xxiSERVER.C. It contains the cipher for the class xxiSERVER, sub-class of ic0SERVER. It overloads, aloof as as example, the method StatusCB, callback for the command STATUS, and additionally the methods accompanying to OLDB contest (AttachDbEvents, DbEvtCB) and timers (AddTimers, TimerCB). The code overloading ic0 methods is actuality alone to accommodate examples to developers. They should be removed back architecture a new apparatus from the Arrangement Instrument code.

·         xxi_LAMP.C. It contains the cipher for the chic xxi_LAMP, sub-class of ic0INS_LAMP, to accommodate an archetype of accustomed accessory class overloading. It should be deleted back architecture a new apparatus from the Arrangement Apparatus code.

·         xxiINS_ANALOG.C It contains the cipher for the chic xxiINS_ANALOG, sub-class of ic0INS_DEVICE, for the appropriate accessory yyyy. In particular, it overloads method DevTrigger. It should be deleted back architecture a new apparatus from the Arrangement Apparatus code.

·         xxins_TRAK.C. It contains the cipher for the class xxins_TRAK, sub-class of ic0INS_ASSEMBLY, to accommodate an archetype of assembly chic overloading. It should be deleted back architecture a new apparatus from the Arrangement Apparatus code.

·         include

·         xxiControl.h. Analogue of classes to be used for the ICS accessories on the WS.

·         xxiCtrMAIN_HANDLER.h Declaration of the class xxiMAIN_HANDLER

·         xxiSERVER.h Declaration of the chic xxiSERVER

·         xxins_LAMP.h Declaration of the class xxins_LAMP.

·         xxiINS_ANALOG.h Declaration of the class xxiINS_ANALOG

·         xxiINS_TRAK.h Declaration of the class xxiINS_TRAK

·         CDT

·         xxiControl.cdt Command Analogue Table for the WS ICS front-end action xxiControl

·         xxiSimControl.cdt. Command Analogue Table for the ICS LCU simulation action xxiSimControl

·         config

·         lxxics1.scan. Browse agreement book for the ICS LCU 1

·         lxxics2.scan. Browse agreement book for the ICS LCU 2

·         dbl

·         xxiSIM_CONTROL.class. dbl chic complete the OLDB annex acclimated by xxiSimControl

·         xxiEnv1.db. dbl accommodate book for the ICS LCU 1 and WS

·         xxiEnv2.db. dbl accommodate book for the ICS LCU 2 and WS

·         xxiHISTORIAN.db. dbl accommodate book which defines the CCS historian tables acclimated by ICS

·         xxiEnv.db. dbl accommodate book which creates the accomplished ICS annex on WS and LCU

8.3.2                       Bore xxipan

This bore contains the cipher for the ICS GUIs.

·         src

·         xxipanControl.pan ICS stand-alone panel, created with the CCS console editor

·         xxipanControl.doc Chiral folio for the xxipanControl panel

8.3.3                       Bore xxidev

It contains the cipher and files for ICS LCU part, in accurate the yyyy appropriate device.

·         src

·         xxidev.boot Cossack book for the xxidev module, as requested by LCC

·         xxidevDeviceCmds.c. It contains the callbacks for all implemented commands, as requested by icb

·         xxidevDeviceDummies.c. It contains the dummy callbacks for commands not implemented.

·         xxidevDeviceNewObj.c It contains architect and destructor of a appropriate accessory object

·         xxidevServer.c It contains the cipher of the yyyy server task, as requested by icb

·         xxidevServerInterface.c It contains the interface functions authentic in the Command Interpreter Table file xxidevServer.cit

·         xxidevVersion.c. It contains the action which allotment the adaptation of the module

·         xxidevFocuInitSw.c. It contains an archetype of cipher for the sw init bend action provided by ic0. It should be deleted when architecture a new apparatus from the Arrangement Apparatus code.

·         xxidevFocuPreInit.c. It contains an archetype of cipher for the pre hw init bend action provided by ic0. It should be deleted back architecture a new apparatus from the Arrangement Apparatus code.

·         xxidevFocuPostInit.c. It contains an archetype of cipher for the column hw init bend action provided by ic0. It should be deleted back architecture a new apparatus from the Arrangement Apparatus code.

·         xxidevFocuPreMove.c. It contains an archetype of cipher for the pre move bend action provided by ic0. It should be deleted when architecture a new apparatus from the Arrangement Apparatus code.

·         xxidevFocuPostMove.c. It contains an archetype of cipher for the column move bend action provided by ic0. It should be deleted when architecture a new apparatus from the Arrangement Apparatus code.

·         xxidevFocuUsr2Enc.c. It contains an archetype of cipher for the user units about-face bend action provided by ic0. It should be deleted back architecture a new apparatus from the Arrangement Apparatus code.

·         CDT

·         xxidevServer.cdt Command Analogue Table for the action xxidevServer

·         CIT

·         xxidevServer.cit Command Interpreter Table for the action xxidevServer

·         ERRORS

·         xxidev_ERRORS. It contains absurdity definitions acclimated in this module

·         dbl

·         xxidevYYYY.db dbl accommodate book abacus the OLDB point for the accessory yyyy. It is included in xxiEnv2.db

·         include

·         xxidevErrors.h It contains macros for errors acclimated in this module

·         vnidevDevice.h. It contains definitions acclimated by the accessory yyyy

·         xxidevServer.h It contains action declarations acclimated in the xxidevServer process

8.4              DCS

8.4.1                       Engineering

Engineering/Maintenance Operations on DCS sub-systems can be performed through the accustomed stand-alone GUIs:

·         TCCD

·         FIERA

·         IRDCS

8.5              MS

8.5.1                       Aliment Templates

·         XXXX_optimg_tec_parasitic. It is the acclimated to ascertain ablaze leaks axial the instrument.

8.5.2                       Bore xxmcfg

This bore accommodate the files anecdotic the accustomed agreement of the instrument

·         config

·         xxmcfgCONFIG.cfg. Capital agreement book used by the VLT apparatus ctoo

·         xxmcfgINS.cfg It contains best of the instrument configuration, except the startup/simulation part

·         xxmcfgSTART.cfg It contains the startup/simulation allotment of the apparatus configuration

·         xxmcfgTARGET.cfg. It  is an abandoned book to accommodate a bend for target specific definitions

·         xxmcfgTEST.cfg. It contains all definitions bare to run analysis scripts (see inscSelfTest)

·         xxmcfgIRDCS.cfg. It contains the IRDCS allotment of the apparatus configuration

·         xxmcfgADC1M.dbcfg. OLDB advancement file, created by motei, complete the agreement of the ADC1 motor

·         xxmcfgDEKK1M.dbcfg. OLDB advancement file, created by motei, complete the agreement of the DEKK1 motor

·         xxmcfgDEKK2M.dbcfg. OLDB advancement file, created by motei, complete the agreement of the DEKK2 motor

·         xxmcfgDPORM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the DPOR motor

·         xxmcfgDROTM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the DROT motor

·         xxmcfgFILTM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the FILT motor

·         xxmcfgFOCUM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the FOCU motor

·         xxmcfgGRATM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the GRAT motor

·         xxmcfgGRISM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the GRIS motor

·         xxmcfgIODSM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the IODS motor

·         xxmcfgMIRRM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the MIRR motor

·         xxmcfgROTM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the ROT motor

·         xxmcfgSLIT1M.dbcfg. OLDB advancement file, created by motei, complete the agreement of the SLIT1 motor

·         xxmcfgSLIT2M.dbcfg. OLDB advancement file, created by motei, complete the agreement of the SLIT2 motor

·         xxmcfgSLITSM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the SLITS motor

·         xxmcfgTILTM.dbcfg. OLDB advancement file, created by motei, complete the agreement of the TILT motor

·         xxmcfgIcsSelfTest_*.ins. Apparatus bureaucracy files acclimated by inscSelfTest as the ICS self-test procedure

8.5.3                       Bore xxmseq

This bore contains the aliment Arrangement Calligraphy files, as able-bodied as the Reference Bureaucracy files acclimated by Templates and analysis OBs.

·         src

·         xxmseqGenTecMSSelfTest.txt. Acclimated in the Makefile to body the cocky analysis obd XXXX_gen_tec_MSTest.obd and abundance it in the agenda config.

·         xxmseqTsfList.txt. Acclimated in the Makefile to build the analysis OBs for anniversary alone arrangement and abundance them in the directory config.

·         config

·         XXXX_optimg_tec_parasitic.ref Reference Setup Book acclimated in the abject allegation abstracts template

8.5.4                       Bore xxmtsf

This bore contains the files accidental to the Apparatus Package, bare by the DFS, and in accurate P2PP.

·         src

The VLT annual oslxCompileTsf is acclimated by make to accomplish the .tsf files (directory config) from the tsfx files.

·         XXXX_optimg_tec_parasitic.tsfx. TSF antecedent file for abject allegation altitude template

·         config

·         XXXX_tec.isf Aliment Apparatus Summary File, to be included in the Aliment Apparatus Amalgamation for P2PP


All suggestions presented in this chapter aim to acquiesce the user to break themselves the best accustomed problems they may encounter.

In all cases, it is recommended to use the annual logMonitor to attending for abundant affidavit of the failure.

9.1              Problems at Arrangement Start-up

9.1.1                       Log-in fails

1.        Accomplish abiding that the terminal is booting from the right host (wxxxx)

2.        Accomplish abiding you accept entered the appropriate user name (xxxx) and password.

9.1.2                       Start-up of GUIs fails

1.        Accomplish abiding you issued the command from a xterm running on the Apparatus Workstation (wxxx) as user xxxx. Type:


2.        Analysis the Start-up agreement (file xxmcfgSTART.cfg).

9.1.3                       Start-up of ascendancy processes fails

1.        Alpha the OS Engineering GUI:

%xxinsStart –panel OS_ENGINEERING

2.        Accomplish abiding that the sub-system associated to the failing action is declared to run at a simulation akin accordant with the hw accessible (cross-check additionally with the capacity of the book xxmcfgSTART.cfg).

3.        If the abortion is accompanying to the LCU sw (e.g. LCU not responding), a reboot of the LCU may help.

9.1.4                       xxiControl starts with a amiss simulation level

1.        The simulation akin at which xxiControl is declared to alpha is authentic by the keyword INS.CON.OPMODE, authentic in xxmcfgSTART.cfg (NOT in xxmcfgINS.cfg !!).

9.1.5                       TCCD starts with a amiss simulation akin and fails to go STANDBY

1.        If the TCCD LCU is available, but no TCCD arrangement is affiliated to it, xxmcfgSTART.cfg should contain:


9.1.6                       xxoControl tries to admission sub-systems declared as not available

1.        Advice about availability of sub-systems is provided through the keywords OCS.*.ACCESS in the book xxmcfgSTART.cfg.

9.1.7                       Activity ONLINE fails

1.        Alpha the OS Engineering GUI:

%xxinsStart –panel OS_ENGINEERING

2.        Analysis which sub-system bootless to go online

3.        Alpha the accompanying stand-alone panel

4.        If the declining sub-system is ICS, the best accustomed case is that one of its accessories has been broken (e.g. one motor) or set to handset/manual approach (e.g. one lamp or shutter). The declining accessory can be anon accustomed because its accompaniment is NOT online.

·         Analysis the accouterments connections/hardware switches

Dyson Dc12 Attachments Dyson dc12 parts diagram dyson | Built-in ..

Dyson Dc12 Attachments Dyson dc12 parts diagram dyson | Built-in .. | dc24 parts diagram

·         Try to re-initialize the device.

5.        If the declining sub-system is TCCD, the best accustomed case is that the affiliation to the ACE box is down

·         Analysis all cables in accurate the cilia optics cable.

6.        If the declining sub-system is FIERA, the best common case is that the ambassador is powered off (e.g. because of overheating protections).

7.        If the declining sub-system is IRACE, the best common case is that the WS allotment tries to admission the Sparc, whereby this computer is not available. Analysis the analogue of ambiance variables, in particular SDMA_HOST (it allegation be the host name of the IWS, back the Sparc is not available).

9.2              Problems back alive exposures

9.2.1                       Cannot accelerate commands to TCS or admission tif

1.        Accomplish abiding that TCS is alive and ONLINE.

2.        Accomplish abiding that TCS RA and DEC are OK. If the RA and DEC accomplishments blush in the OS Ascendancy Console is gray, afresh apparently TCS is not operational. See additionally 4.1.2.

9.2.2                       Templates cannot admission Midas

1.        Accomplish abiding that MIDAS NOV99 or college is installed on the IWS. If not, attenuate MIDAS admission from templates (see 4.1.3)


The Apparatus Software uses the standard apparatus authentic and provided by the CCS absurdity arrangement to log and acknowledgment error information, both at anatomic and command level, on LCU and WS.

Errors are authentic in the afterward files:

·         xxoErrors.h OS absurdity codes

·         xxo_ERRORS OS absurdity messages

See additionally area 11.11


11.1          Programs

11.1.1                   Command Analogue Table for affairs xxoControl


// E.S.O. – VLT project


// “@(#) $Id: xxoControl.cdt,v 1.47 2003/03/21 16:18:07 vltsccm Exp $”


// who        when      what

// ———- ——–  ———————————————-

// gzins      28/11/99  Created

// epozna               adopted fpr boss

// epozna               use accustomed interface (osb)

// epozna     10/10/00  aish colons afterwards PUBLIC_COMMANDS


//  NAME

//    xxoServer.cdt – command analogue table



//    This book describes the accustomed commands authentic in a process

//    xxoServer (Supervisory Ascertainment Software server).







//  BOSS Accustomed Commands




#include “osbControl.cdt”

11.2          Scripts

11.2.1                   xxinsStartup





    xxinsStartup – configure and alpha XXXX capital application




    This calligraphy starts the XXXX startup agreement panel

    and afresh starts XXXX if the START on is pressed.

    The user can set several options in the startup panel

    afore starting XXXX:

    Telescope (TCS):

     – Available: baddest if the telescope can be accessed or not.

    Apparatus (ICS):

     – Available:      commonly true.

     – WS Simulation:  commonly false, unless the instrument

                       is not available.

     – User Interface: alpha the ICS stand-alone panel.

    Detectors (DCS):

     – Available:      commonly true; set to false, if the

                       detector should not be used.

     – WS Simulation:  commonly false; set to true, if the

                       detector accouterments is not available.

     – User Interface: alpha the detector stand-alone panel.

     – Alpha RTD:      alpha the detector RTD.


     – Alpha BOB:        alpha the BOB panel, commonly true.

     – Alpha OS Control: alpha the OS control panel.

     – Alpha Alarm Display: alpha the alarm display.


    xxmcfgSTART.cfg alpha agreement file

    xxmcfgINS.cfg   apparatus agreement file

                    Both are in $INS_ROOT/SYSTEM/COMMON/CONFIGFILES




    xxinsStart xxinsStop

### generated by docDeroff ###

11.2.2                   xxinsStart





    xxinsStart – alpha XXXX application


    xxinsStart [-log] [-proc <appl>] [-panel <panel>]

               [-restart] [-loglevel <n>]


    This calligraphy starts the XXXX application.

    – Absence panels are stopped.

    – All subsystems are started.

    – The Ascertainment Software is started.

    – Absence panels are started.


    no option:      Analysis that OS and its subsystems are running,

                    alpha them if necessary.

                    Restart absence panels.

    -proc <name>    Alpha the appliance <name>.

                    <name> may be the name of a subsystem

                    (e.g. ICS) or OS.

                    To admission a annual of known panels, use e.g.:

                    ‘xxinsStart -proc show’

    -panel <name>   Alpha the console <name>.

                    To admission a annual of known panels, use e.g.:

                    ‘xxinsStart -panel show’

    Advantage modifiers:

    -restart        Restart the application.

                    OS and subsystems are stopped, afresh restarted.

                    Alone absence panels are chock-full and restarted.

    -log            Open a log window

                    (-log MUST consistently be the aboriginal option).

                    To aish the log window, pass any other

                    advantage to xxinsStart, e.g. ‘-loglevel 1’.

    -loglevel <n>   Increase logging for debugging. n = 0..3.


    xxmcfgSTART.cfg alpha agreement file

    xxmcfgINS.cfg   apparatus agreement file

                    Both are in $INS_ROOT/SYSTEM/COMMON/CONFIGFILES


    xxinsStart -panel OS_CONTROL



### generated by docDeroff ###

11.2.3                   xxinsStop





    xxinsStop – stop XXXX application


    xxinsStop [-log] [-proc <appl>] [-panel <panel>]

              [-standby] [-loglevel <n>]


    This calligraphy stops the XXXX application.

    – OS is placed in accompaniment STANDBY.

    – All panels are stopped.

    – OS and all subsystems are stopped.


    no option:      Abode OS in accompaniment STANDBY, stop all panels

                    and stop OS and all subsystems.

    -proc <name>    Stop the appliance <name>.

                    <name> may be the name of a subsystem

                    (e.g. ICS) or OS.

                    To admission a annual of known panels, use e.g.:

                    ‘xxinsStop -proc show’

    -panel <name>   Stop the console <name>.

                    To admission a annual of known panels, use e.g.:

                    ‘xxinsStop -panel show’

    -standby        Alone abode OS in accompaniment STANDBY.

                    Leave all panels and processes running.

    Advantage modifiers:

    -log            Open a log window

                    (-log MUST consistently be the aboriginal option).

                    To aish the log window, canyon any other

                    advantage to xxinsStop, e.g. ‘-loglevel 1’.

    -loglevel <n>   Increase logging for debugging. n = 0..3.


    xxmcfgSTART.cfg alpha agreement file

    xxmcfgINS.cfg   apparatus agreement file

                    Both are in $INS_ROOT/SYSTEM/COMMON/CONFIGFILES


    xxinsStop -panel OS_CONTROL



### generated by docDeroff ###

11.3          Accommodate Files

All accommodate files are clandestine to the instrument.

11.4          Tcl libraries

The library xxoseq provides classes acclimated for the development of XXXX Templates. The man-pages presented in this area accredit to classes acceptance to that library.

11.4.1                   xxoseqICS





    xxoseqICS – XXXX ICS interface for templates.


    xxoseqICS ics


    XXXX ICS interface for BOB templates.




    see tplICS man page.



### generated by docDeroff ###

11.5          Agreement files

The configuration files (see Affiliate 6), due to their size, are not apparent here.

11.6          Bureaucracy files

11.6.1                   Archetype of  Reference Bureaucracy file


11.6.2                   Archetype of Apparatus Bureaucracy File


# E.S.O. – VLT project


# “@(#) $Id: xxmcfgIcsSelfTest_1.ins,v 1.64 2003/02/25 12:03:27 vltsccm Exp $”


# who         when      what

# ———-  ——–  ———————————————-

# rschmutz    13/05/02  SLIT1 param. adapted (were aloof out of range).

# alongino    04/01/01  created



PAF.HDR.START;                 # Alpha of PAF Header

PAF.TYPE         “Instrument Setup”; # Type of PAF

PAF.ID           ”        “;   # ID for PAF

PAF.NAME         ”        “;   # Name of PAF

PAF.DESC         ”        “;   # Abbreviate description of PAF

PAF.CRTE.NAME    ”        “;   # Name of creator

PAF.CRTE.DAYTIM  ”        “;   # Civil Time for creation

PAF.LCHG.NAME    ”        “;   # Name of person/appl. changing

PAF.LCHG.DAYTIM  ”        “;   # Timestamp of last change

PAF.CHCK.NAME    ”        “;   # Name of appl. checking

PAF.HDR.END;                   # End of PAF Header

INS.LAMP1.ST              “T”; # lamp on/off

INS.SHUT1.ST              “T”; # bang on/off

INS.ADC1.MODE           “OFF”; # adc off/auto

INS.DPOR.ST               “T”; # dpor on/off

INS.DROT.MODE          “STAT”; # drot mode

INS.DROT.POSANG          0.00; # drot alpha bend (deg)

INS.FILT1.NAME            “U”; # accessory named position

INS.GRAT1.NAME         “CD#1”; # accessory named position

INS.GRAT1.WLEN           0.00; # axial wavelength

INS.MIRR1.NAME         “IRED”; # accessory named position

INS.OPTI1.NAME          “OUT”; # accessory called position

INS.GRIS1.NAME        “GRIS1”; # accessory named position

INS.FOCU1.POS          -153.4; # accessory affiliated position

INS.ROT1.POS           -90.00; # accessory affiliated position

INS.SLIT1.LEN            0.14; # accessory affiliated position

INS.SLIT1.WID            0.15; # accessory affiliated position

INS.SLIT2.NAME         “FREE”; # accessory named position

INS.TILT1.POS          -153.4; # accessory affiliated position

INS.MIRR2.DATA1        -10.00; # appropriate accessory data

INS.MIRR2.DATA2        -20.00; # appropriate accessory data

# — oOo —

11.7          Templates

11.7.1                   IR Imaging accretion template





XXXX_irimg_acq – XXXX Accretion Arrangement signature file


Target accretion : presetting to coordinates

### generated by docDeroff ###

11.7.2                   IR Imaging ascertainment template





XXXX_irimg_obs_exp.tsf – XXXX Ascertainment Arrangement signature file


    accustomed exposure

### generated by docDeroff ###

11.7.3                   IR Spectroscopy accretion template





XXXX_irspec_acq.tsf – XXXX Accretion Arrangement signature file


Target accretion : alternate presetting to pixel position

### generated by docDeroff ###

11.7.4                   IR Spectroscopy ascertainment template





XXXX_irspec_obs_exp.tsf – XXXX Ascertainment Arrangement signature file


    accustomed exposure

### generated by docDeroff ###

11.7.5                   Optical Imaging accretion template





XXXX_optimg_acq – XXXX Accretion Arrangement signature file


Target accretion : presetting to coordinates

### generated by docDeroff ###

11.7.6                   Optical Imaging ascertainment template





XXXX_optimg_obs_exp.tsf – XXXX Ascertainment Arrangement signature file


    accustomed exposure

### generated by docDeroff ###

11.7.7                   Optical Imaging bent arrangement template





XXXX_optimg_cal_bias.tsf – XXXX Arrangement Arrangement signature file


    SEQ.NEXPO XXXX Biases or Darks

### generated by docDeroff ###

11.7.8                   Optical Imaging flat-field arrangement template





XXXX_optimg_cal_calunitflat.tsf – XXXX Collapsed Acreage Arrangement Arrangement signature file


      Flats         :   afterwards 1 bent and a 1 sec. flat, calculate

                    :   acknowledgment time to ability DET.EXPLEVEL

                    :   and accomplish SEQ.NEXPO arch flats.

### generated by docDeroff ###

11.7.9                   Optical Imaging detector breadth arrangement template

Dyson DC12 Vacuum Parts – Vacuum Direct - dc24 parts diagram

Dyson DC12 Vacuum Parts – Vacuum Direct – dc24 parts diagram | dc24 parts diagram





XXXX_optimg_cal_linearity.tsf – XXXX Arrangement Arrangement signature file


Linearity sequence

### generated by docDeroff ###

11.7.10                Optical Imaging focus arrangement template





XXXX_optimg_cal_focus.tsf – XXXX Arrangement Arrangement THRU FOCUS signature file


Thu focus sequence

### generated by docDeroff ###

11.8          FITS files

11.8.1                   Archetype of FITS header


11.9          Log files

11.9.1                   Archetype of Operational Log (FITS format)


11.10      Panels

11.10.1                OS Control





xxopanControl – Ascendancy console for XXXX OS


“File” menu


        avenue the application

“Options” menu


        Refresh all achievement fields as from the IWS OLDB.

“Engineering” menu


        Alpha the XXXX OS Engineering GUI

“Telescope” menu


        If not set, TCS is abandoned (not implemented yet)

“Instrument” menu


        Alpha all XXXX ascendancy processes


        Bring the XXXX Apparatus to STANDBY state


        Bring the XXXX Apparatus to ONLINE state


        Terminate all XXXX ascendancy processes

“Help” menu

    Continued Help. Not implemented yet



    Abort the alive acknowledgment with the related DCS

### generated by docDeroff ###

11.10.2                OS Status





xxopanStatus – Cachet console for XXXX OS


“File” menu


        avenue the application

“Std. Options” menu

    “Refresh Database values”

        Refresh all achievement fields as from the IWS OLDB.

    “Re-Start Database Events”

        Re-Start all OLDB Contest associated to achievement widgets

“Help” menu

    Continued Help. Not implemented yet

### generated by docDeroff ###

11.10.3                OS Engineering





xxopanEngineering – Engineering console for XXXX OS


“File” menu


        avenue the application

“Std. Options” menu

    “Refresh Database values”

        Refresh all achievement fields as from the IWS OLDB.

    “Re-Start Database Events”

        Re-Start all OLDB Contest associated to achievement widgets

“Simulation” menu

    “IR DCS”

        “No simulation”

              IRACE Slcu accessible and affiliated to IRACE controller

        “Slcu simulated”

              IRACE Slcu NOT available (simulated on the IWS)

        “Irace simulated”

              IRACE Slcu accessible and NOT affiliated to IRACE controller

    “TCCD DCS”

        “No simulation”

              TCCD lcu accessible and connected to ACE controller

        “Lcu simulated”

              TCCD lcu NOT accessible (simulated on the IWS)

        “Ace simulated”

              TCCD lcu accessible and NOT affiliated to ACE controller


        “No simulation”

              FIERA Slcu accessible and affiliated to FIERA controller

        “Slcu simulated”

              FIERA Slcu NOT available (simulated on the IWS)

        “Head simulated”

              FIERA Slcu accessible and NOT affiliated to FIERA controller


        “Simulate accessory hw on LCU”

              ICS LCUs accessible but NO device accouterments affiliated to them


        “Active Optics”


                     Simulate starting active optics


                     Simulate endlessly active optics



                     Simulate starting auto-guiding


                     Simulate stopping auto-guiding

“Help” menu

    Continued Help. Not implemented yet



    Alpha the ascendancy processes for the related sub-system


    Bring the accompanying sub-system to STANDBY state


    Bring the accompanying sub-system to ONLINE state


    Terminate the ascendancy processes for the accompanying sub-system


    Alpha the stand-alone GUI for the related sub-system

### generated by docDeroff ###

11.10.4                ICS stand-alone





xxipanControl – XXXX ICS stand-alone GUI


“File” menu


        avenue the application

“Selection” menu

    “Select all functions”

        Set the analysis on associated to each device

    “Deselect all functions”

        Reset the analysis on associated to anniversary device

“Setup” menu


        Save the accustomed bureaucracy in bureaucracy file xxipan.ins

    “Save As …”

        Save the accustomed bureaucracy in the specified bureaucracy file

    “Load …”

        Amount in the console the capacity of the authentic bureaucracy file

“Maintenance” menu

    “Edit cfg. book …”

        Alpha the absence argument editor and open the xxmcfgINS.cfg file

    “Set LCU cfg.”

        Assassinate icbConfigSet XXXX

    “Reboot LCUi”

        Reboot the authentic LCU

“Tools” menu


        Alpha the CCS annual logMonitor



            Alpha the motor engineering interface



            Alpha the acromag agenda I/O board engineering interface



            Alpha the acromag agenda I/O board engineering interface

“Std. Options” menu

    “Refresh Database values”

        Refresh all OLDB ethics in the panel.

    “Re-Start Database events”

        Configure afresh all contest absorbed to OLDB values.

        Useful e.g. afterwards one LCU has rebooted.

“Help” menu

    Continued Help. Not implemented.


“Global Control”


        Alpha the ICS WS processes

    “State control”

        Bring ICS to the authentic state

        The command is issued as anon the advantage on is released


        Terminate the ICS WS processes


        Baddest the command to be sent


        Set the command ambit to be sent


        Accelerate the authentic command and ambit to xxiControl

“Functions control”


        Accelerate a SETUP command to xxiControl for all called devices


        Emergency stop. All accessories are stopped.

    “Change State”

        Bring the called accessories to the authentic state


        Bring the called accessories to the called simulation mode.

    Anniversary accessory uifClass has the following widgets

        Analysis on to baddest the accessory for the aing operation (e.g. SETUP)

        Accessory name

        Short-FITS accessory prefix

        Simulation flag


        Handset banderole (not for sensors)

        Cachet value(s)

        Encoder position (only for motors)

        Bureaucracy advantage on

        Bureaucracy ascribe field(s) for numerical values

“Command Feedback Window”

    It shows the aftermost commands and replies to/from xxiControl as

    able-bodied as the capital advancing accomplishments (e.g. LCU rebooting).

### generated by docDeroff ###

11.11       Error files

11.11.1                xxoErrors.h


# “@(#) $Id$”


# Error Accommodate File    Created on  Mar 24 12:53:33 2003


# This book has been generated by a utility


#  !!!!!!!!!!!  DO NOT MANUALLY EDIT THIS FILE  !!!!!!!!!!!



#ifndef xxoERRORS_H

#define xxoERRORS_H

#ifndef CCS_H

#include “ccs.h”


#define xxoErrOffset 0


#define xxoERR_DB_READ                 ((vltINT16) ( xxoErrOffset 1 ))

#define xxoERR_DB_WRITE                ((vltINT16) ( xxoErrOffset 2 ))

#define xxoERR_LOAD_DICTIONARY         ((vltINT16) ( xxoErrOffset 3 ))

#define xxoERR_LOAD_ALIAS_TABLE        ((vltINT16) ( xxoErrOffset 4 ))

#define xxoERR_INVALID_STATE           ((vltINT16) ( xxoErrOffset 5 ))

#define xxoERR_CMD_ABORTED             ((vltINT16) ( xxoErrOffset 6 ))

#define xxoERR_CACHE_FILE_EXISTS       ((vltINT16) ( xxoErrOffset 7 ))

#define xxoERR_NO_KEYW_TO_SAVE         ((vltINT16) ( xxoErrOffset 8 ))

#define xxoERR_KEYW_NOT_SAVED          ((vltINT16) ( xxoErrOffset 9 ))

#define xxoERR_NO_FILE_SPECIFIED       ((vltINT16) ( xxoErrOffset 10 ))

#define xxoERR_CONFLICT_OFFSET         ((vltINT16) ( xxoErrOffset 11 ))

#define xxoERR_OPTION_CONFLICT         ((vltINT16) ( xxoErrOffset 12 ))

#define xxoERR_EXPO_FILE_MISSING       ((vltINT16) ( xxoErrOffset 13 ))

#define xxoERR_SEQ_EXPO                ((vltINT16) ( xxoErrOffset 14 ))

#define xxoERR_INVALID_NAMING_TYPE     ((vltINT16) ( xxoErrOffset 15 ))

#define xxoERR_INVALIDE_EXP_MODE       ((vltINT16) ( xxoErrOffset 16 ))


11.11.2                xxo_ERRORS


# Adaptation Id. is authentic at the end of the book


# Error Analogue File    Created on  Jun 15 14:11:41 2000


# This book has been generated by a utility


#  !!!!!!!!!!!  DO NOT MANUALLY EDIT THIS FILE  !!!!!!!!!!!




define xxoErrOffset 0


1 S xxoErrOffset

xxoERR_DB_READ : Could not apprehend database aspect ‘%.80s’


2 S xxoErrOffset

xxoERR_DB_WRITE : Could not address database aspect ‘%.80s’


3 W xxoErrOffset

xxoERR_LOAD_DICTIONARY : Could not amount concordance %.80s


4 W xxoErrOffset

xxoERR_LOAD_ALIAS_TABLE : Could not amount alias table %.80s


5 W xxoErrOffset

xxoERR_INVALID_STATE : Command %.80s cannot be accomplished in the accustomed state: %.80s/%.80s


6 W xxoErrOffset

xxoERR_CMD_ABORTED : Command %.80s beheading aborted


7 W xxoErrOffset

xxoERR_CACHE_FILE_EXISTS : The book ‘%.80s’ already exists in accumulation directory


8 W xxoErrOffset

xxoERR_NO_KEYW_TO_SAVE : No keywords were accustomed to save into book ‘%.80s’


9 W xxoErrOffset

xxoERR_KEYW_NOT_SAVED : The keyword ‘%.80s’ was not adored in this file


10 W xxoErrOffset

xxoERR_NO_FILE_SPECIFIED : No filename has been authentic in command ‘%.80s’


11 W xxoErrOffset

xxoERR_CONFLICT_OFFSET : Conflict in appropriate offsets in command OFFSET: RA/DEC=%.2f/%.2f arcsec, X/Y=%.2f/%.2f pixels, rotator=%.2f deg, focus=%.2f mm


12 W xxoErrOffset

xxoERR_OPTION_CONFLICT : Conflict in options %.80s and %.80s


13 W xxoErrOffset

xxoERR_EXPO_FILE_MISSING : Acknowledgment FITS filename missing. Allegation be set afore starting exposure.


14 W xxoErrOffset

xxoERR_SEQ_EXPO : Amiss acknowledgment ascendancy sequence. Call aboriginal %.20s.


15 W xxoErrOffset

xxoERR_INVALID_NAMING_TYPE : Invalid book allotment blazon ‘%.80s’


16 F xxoErrOffset

xxoERR_INVALIDE_EXP_MODE : Approach ‘%.80s’ accustomed in the SETUP is invalid.



# “@(#) $Id: xxo_ERRORS,v 1.47 2003/03/21 16:18:12 vltsccm Exp $”

Appendix A. Create a new Instrument

It is recommended to use the arrangement apparatus as the starting point of the development of a new instrument. There is a script accessible (module insc, name inscCreateNewInstrument, see [AD 07]), which creates a twin archetype of the Arrangement Instrument, by artlessly renaming modules and files and modifying the capacity accordingly, befitting of advance the aforementioned functionality. Such a archetype already provides the accustomed anatomy (modules and files) of an apparatus and should appropriately be taken as starting point for the development of the apparatus specific code.

The calligraphy assumes that the XXXX apparatus has already been auspiciously installed and activated and allegation be accomplished from the aforementioned directory area pkginBuild xxins has been executed.

After alive the script, a agenda structure, alongside to XXXX and called with the new apparatus ID, will be available.

The new apparatus allegation be now tested, afterward the same action as declared in affiliate 3.2.1.

Once the tests accept completed successfully, it is probably time to annal the new modules created by inscCreateNewInstrument: they still don’t do what your Apparatus is declared to do, but at atomic they attending like modules acceptance to your Instrument. Since apparently they are not alike registered in the VLT Agreement Ascendancy Management Arrangement (cmm) there is some preliminary authoritative assignment to be done in adjustment you to get admission to the cmm functionality and your new modules to be registered in the system. Please acquaintance the ESO software amenable for your activity in adjustment to get this done.

At this point, you can alpha adapting the absolute modules to the absolute needs and characteristics of your Instrument.

XXXX provides several examples to advice in this process. They are listed below.

An archetype of BOSS chic bossSERVER adjustment (StartPreProc) overloading is available in the book xxo/src/xxoExpCtrl.C.


An archetype of chic for arrangement is accessible in book xxoseq/src/xxoseqICS.tcl.

Module xxidev contains the LCU cipher for the appropriate accessory yyyy. The appropriate accessory yyyy is a simple sample software accessory that has two bifold attributes in its OLDB point. These two bifold attributes can be set with the SETUP command (with FITS keywords INS.MIRR2.DATA1 and INS.MIRR2.DATA2).  These ethics can be retrieved with the STATUS command.

File xxidevDeviceCmds.c contains the software accessory specific cipher for the CCS commands that the device is able of receiving.

·         Action xxidevDeviceSetup

This action receives the two FITS keywords DATA1 and DATA2, and food them in the OLDB attributes data1 and data2.

·         Action xxidevDeviceStatus

This action returns the ethics of the OLDB attributes data1 and data2, according to the received ambit DATA1 and DATA2.

See additionally [RD 16].

Module xxi contains some examples for ICS WS sw. In particular, book xxiINS_ANALOG.C accouterments the WS allotment accessory yyyy.

Please agenda that a LCU appropriate accessory does not necessarily allegation to accept a appropriate adverse allotment on the WS: it ability able-bodied appear that the absence behavior provided by the chic ic0INS_DEVICE altogether fits the needs for that accessory at WS level.

The aforementioned applies additionally the added way around. There ability be a device, which allegation some appropriate analysis on WS, but altogether avalanche into one of the accustomed ICS LCU accessory categories; in this case, it is acceptable to apparatus the appropriate functionality on WS.

In the case of XXXX, we accept that yyyy needs a appropriate analysis both on WS and LCU, aloof to provide a complete example.

Please agenda that the appropriate accessory and accompanying chic (xxiINS_ANALOG) has to be registered in the xxiControl action (see book xxiControl.C).

See additionally [RD 16].

File xxiSERVER.C shows an archetype of sub-classing (xxiSERVER sub-class of ic0SERVER) and method overloading (StatusCB, callback for the STATUS command).

In adjustment to let xxiControl use the xxiSERVER chic in abode of the ic0SERVER (default), additionally the adjustment NewServer in ic0CtrlMAIN_HANDLER has to be active (see book xxiCtrlMAIN_SERVER.C).

See additionally [RD 16].

See 5.3.2. and [RD 16].

Appendix B. Installation appliance altered environments

It is recommended to use the ambiance names authentic in xxins/config/xxinsINSTALL.cfg and again in 2.2.2. About in some cases, for development or test purposes, it ability be all-important to use altered ambiance names. The action to acclimate the XXXX cipher to this case is declared here.

Let’s accept that the ambiance names to be acclimated are:

wyyxx (instead of wxxxx)

wyytcs (instead of wxxtcs)

lyyics1 (instead of lxxics1)

lyyics2 (instead of lxxics2)

lyytccd (instead of lxxtccd)

1.       Retrieve modules from annal and add address permission to files

% cd $HOME/XXXXSource

% cmmCopy xxins $XXXX_VERSION

% pkginBuild xxins -step RETRIEVE

% chmod –R w .

2.       Run inscChangeEnvs annual (see [AD 07]):

% inscChangeEnvs xx yy

3.       Body and install the XXXX Software

See 3.2 for the actual allotment of the installation, according to the hw availability.

Dyson Ball Dc12 Parts List | Viewmotorjdi

Dyson Ball Dc12 Parts List | Viewmotorjdi | dc24 parts diagram


Dc10 Parts Diagram Is So Famous, But Why? | Dc10 Parts Diagram – dc24 parts diagram
| Welcome to my own blog, on this time I’ll explain to you regarding dc24 parts diagram

Dyson model DC12 vacuum, upright genuine parts - dc24 parts diagram

Dyson model DC12 vacuum, upright genuine parts – dc24 parts diagram | dc24 parts diagram

Dyson Wiring Diagram - Enthusiast Wiring Diagrams • - dc24 parts diagram

Dyson Wiring Diagram – Enthusiast Wiring Diagrams • – dc24 parts diagram | dc24 parts diagram

Dyson Dc12 Parts | Wiring Diagram Collection - dc24 parts diagram

Dyson Dc12 Parts | Wiring Diagram Collection – dc24 parts diagram | dc24 parts diagram

Mariana Lisa Aretina