VST Project. Test Procedure in Europe. Tracking. Doc.no. : VST-PRO-OAC-TRK-001. Date: Issue: 1.0 DRAFT VERSION

(1)

VST Project

Test Procedure in Europe

Tracking

Doc.no. : VST-PRO-OAC-TRK-001

Date: 2006-10-05

Issue: 1.0

DRAFT VERSION

Name Date Signature

Written by M. Brescia, P. Schipani 2006-10-05

Checked by Released by

(2)

Change Record

Issue/Rev. Date Section/Page affected Reason/Remarks

(3)

Index

1 Introduction ... 4

2 Scope of the tests ... 4

3 Applicable Documents... 4

4 Test Conditions... 5

5 Definition of tests ... 6

5.1 Large tracking map ... 6

5.1.1 Test principle ... 6

5.1.2 Collected data ... 6

5.1.3 Analysis ... 6

5.1.4 Step by step procedure ... 9

6 Test results ... 16

Reference Documents

id. Document code Title Source Date Issue

(4)

1 Introduction

This document contains procedures to test the quality of the VST tracking system in Europe. Generally speaking, the test procedure should describe in detail all basic operations needed to perform a verification by plan. Therefore, the test procedure reports all the following information:

• Scope of the test: a theoretical description of the test, its scope e purpose, identifying also all the verification items involved;

• All the applicable documentation list (i.e. relevant documents to verify or referred for the test procedure);

• Test procedure: detailed list of all operations required to perform the functional tests;

• Test conditions: conditions of the system to perform tests, operation tools, environmental conditions, special requirements on tested items, calibration requirements;

• Test results: all the procedures to process row data for the final presentation of the results;

2 Scope of the tests

Scope of the tests is to measure and verify telescope preliminary tracking performance in Europe of the tracking axes: Azimuth, Altitude, Rotator.

Just blind tracking capabilities of the telescope are measured as the autoguider cannot be used in real mode in the Italy integration facility.

3 Applicable Documents

The following documents are considered relevant to tracking system test procedure:

CODE TITLE SOURCE DATE ISSUE

VST-SPE-OAC-25000-1177 VSTALAZ module description VST 28/09/05 1.0 VST-SPE-OAC-25000-1178 VSTAXEI module description VST 28/09/05 1.0 VST-SPE-OAC-25000-1184 VSTAXIS module description VST 28/09/05 1.0 VST-SPE-OAC-25000-1182 VSTHB module description VST 28/09/05 1.0 VST-SPE-OAC-25000-1185 VSTIKLIDA module description VST 28/09/05 1.0 VST-SPE-OAC-25000-1176 VSTIO module description VST 28/09/05 1.0 VST-SPE-OAC-25000-1181 VSTROT module description VST 28/09/05 1.0 VST-SPE-OAC-25000-11xx VSTTRK module description VST 28/09/05 1.0 VLT-MAN-ESO-17130-1211 LCU axis control module acm/axis ESO 29/12/97 1.0 VLT-SPE-ESO-17130-1210 Axis control module design descr. ESO 21/09/01 2.0 VLT-SPE-ESO-17230-0755 TCS tracking design description ESO 16/05/00 1.1

(5)

4 Test Conditions

In order to perform tracking functional tests on VST, no particular equipment is needed. Just WS engineering GUIs controlling axes are necessary, listed below. The only HW requirement is that the telescope should be completely mechanically assembled in order to guarantee perfect balancing between near (AZ/ROT assembly) and far (ALT assembly) masses.

From the control point of view, the following equipment is directly involved, and their functionality required:

• AZ axis LCU (environment ltvaz)

• AZ HBS LCU (environment ltvhb)

• ALT axis LCU (environment ltvalt)

• ROT axis LCU (environment ltvadc)

• TCS control WS (environment wtvst)

From the SW point of view, the following applications are usually employed, depending on the specific level of test/verification. They are partially derived/modified from VLT TCS SW package, so for most of them, their use can be considered the same:

Control tools:

• vstguiStatus: TCS mode switching control interface

• vstaxei: tracking axis control engineering user interface (AZ/ALT/ROT)

• vsthbCabinStatus: AZ HBS control engineering user interface

• vstcogui: Corotator control/diagnostic engineering interface

• vstguiTCS: main TCS control user interface (high level) Diagnostic tools:

• VLTSW engineering applications (logMonitor, ccseiDb, sampCtrl, etc.)

• vsthbPadStatus: AZ HBS baseplate pads monitoring interface

• vsthbLog: AZ HBS signal monitoring interface

• vstalazAzStatus: AZ axis control diagnostic interface

• vstalazAzEncStatus: AZ axis encoder system diagnostic interface

• vstalazAltStatus: ALT axis control diagnostic interface

• vstalazAltEncStatus: ALT axis encoder system diagnostic interface

• vstaxeiRotStatus: ROT axis control diagnostic interface

All these engineering tools can be launched from WS console in order to execute preset/tracking commands for all or single tracking axis and/or to receive control and diagnostic information during test operations.

(6)

5 Definition of tests

5.1 Large tracking map

The procedure generates a tracking map recording axes position and position errors for the three axes. It uses 37 standard positions, mostly derived from RD1.

5.1.1 Test principle

Telescope points and tracks in predefined positions and the data are recorded using sampCtrl sampling tool.

5.1.2 Collected data

The following data are collected:

• AZ actual position

• AZ position error

• ALT actual position

• ALT position error

• ROT actual position

• ROT position error 5.1.3 Analysis

Data can be processed using VLTSW cfp module, but it is our intention to use an alternative tool based on a Matlab analysis dedicated program called paetrackgui:

For each tracking position the program provides:

• One plot showing encoder position error vs. time per each axes

• One plot showing encoder position error vs. position per each axes

• Additionally, one plot showing azimuth encoder position error corrected with cos(ALT) factor

• One plot showing main axes combined error ALT+AZ (AZ corrected with cos(ALT) factor) Each plot shows:

• encoder position error RMS

• the average axis speed

• file name

(7)

(8)

(9)

5.1.4 Step by step procedure

(10)

Step no. Action Actual Status / Value

1 Record date and time Date =

Time =

2 Record software modules version vstaxis:

vstiklida: vstalaz: vstrot: vstco: trk: trkws: vstBUILD: vstIO: vsthb:

3 Record position servo constants for az, alt, rot Az Kp =

Az Ki = Az maxacc = Az maxvel = Az maxjerk = Az Kb = Az alg switch 1 = Az alg switch 2 = Alt Kp = Alt Ki = Alt maxacc = Alt maxvel = Alt maxjerk = Alt Kb =

Alt alg switch 1 = Alt alg switch 2 = Rot Kp =

(11)

Rot Ki = Rot maxacc = Rot maxvel = Rot maxjerk = Rot Kb =

Rot alg switch 1 = Rot alg switch 2 =

5 Record encoder calibration status Az enc calibrated (Y/N):

Alt enc calibrated (Y/N): Rot enc calibrated (Y/N):

6 Preset to coordinates of the next object in Tab. 1

7 •Start sampling of data to files

•Collect data for 10 minutes

•Stop sampling of data to files

•Write file name to Tab. 1

•Move file to /vltuser/PAE/trkTests:

mv filename /vltuser/PAE/trkTests

8 If Tab. 1 entries are not finished, go to step no.6

9 Produce plots with the analysis program paeTrackGui

Add plots to this report

(12)

(13)

(14)

Νο. α δ AZ Pos ALT Pos AZ Vel ALT Vel File AZ RMS AZ_SKY RMS ALT RMS AZ+ALT RMS ROT RMS Remarks Executer 1 <HA~+1h> -150000 238 73 29.5 -11.6 2 <HA~+2h> -150000 257 60 11.7 -13.3 3 <HA~+3h> 000000 247 40 10 -12 4 <HA~+4h> 000000 256 27 7.8 -13 5 <HA~+2h> -250000 277 63 2.9 -13.5 6 <HA~+3h> -250000 280 49 3.4 -13.4 7 <HA~+5h> -400000 304 27 2 -11 8 <HA~+2h> -400000 309 61 -8.9 -10.6 9 <HA~+0.5h> -300000 311 81 -53 -10 10 <HA~+3h> -600000 331 43 4.9 -6.6 11 <HA~+5h> -600000 327 29 0.05 -7 12 <HA~+1h> -600000 348 53 -11.5 -2.9

13 <HA~-5min> -600000 0 55 -13 0 Meridian crossing

16 <HA~-1h> -600000 12 53 -11.5 2.9 17 <HA~-2h> -800000 6 33 -2.6 1.4 18 <HA~-3h> -600000 29 43 -4.9 6.6 19 <HA~-1h> -400000 36 70 -24 8 20 <HA~-30min> -300000 49 81 -53 10 21 <HA~-3h> -400000 56 49 -2.5 11 22 <HA~-5h> -400000 56 27 2.4 11 23 <HA~-1h> -250000 85 76 1.5 14 24 <HA~-5h> -250000 72 23 4.5 13 25 <HA~-3h> -150000 94 47 7.3 13.6 26 <HA~-2h> -150000 103 60 12 13 27 <HA~-1h> -150000 122 73 29 11.6 28 <HA~-2h> 000000 126 52 16 11

(15)

30 <HA~-1h> +300000 164 33 15 3.7

31 <HA~-5min> +150000 180 50 23 0 Meridian crossing

32 <HA~-5min> 000000 180 65 36 0 Meridian crossing

33 <HA~-5min> -220000 180 87 300 0 Meridian crossing

34 <HA~+30min> -220000 251 83 41 -12

35 <HA~+1h> 000000 213 61 27 -7

36 <HA~+2h> +300000 209 28 13 -6.7

37 <HA~-10min> -240000 180 89 1000 0 Meridian crossing

(16)

6 Test results

(17)