TCS Test Plan · 2020. 1. 22. · TCS Test Plan CON-0022 Rev A Page 1 of 102 1. INTRODUCTION 1.1...

Project Documentation Document CON-0022

Revision A

TCS Test Plan

Alan Greer & Chris Mayer Observatory Sciences Ltd

27th September 2006

Advanced Technology Solar Telescope 950 N. Cherry Avenue Tucson, AZ 85719 Phone 520-318-8102 [email protected] http://atst.nso.edu Fax 520-318-8500

TCS Test Plan

Version A Page i

Revision Summary:

1. Date: 27th September 2006 Revision: A Changes: Initial version

2. Date: Revision: Changes:

3. Date: Revision: Changes:

TCS Test Plan

CON-0022 Rev A Page ii

Table of Contents

1. Introduction ............................................................................................... 1

1.1 Purpose ..............................................................................................................................1 1.2 Audience............................................................................................................................1 1.3 Scope .................................................................................................................................1 1.4 Overview ...........................................................................................................................1

2. Test Environment ...................................................................................... 2 2.1 Hardware Environment .....................................................................................................2 2.2 Software Environment.......................................................................................................2

3. Test Schedule ............................................................................................ 3 4. REFERENCES........................................................................................ 102

TCS Test Plan

CON-0022 Rev A Page 1 of 102

1. INTRODUCTION 1.1 PURPOSE This document provides the Acceptance Test Plan of the ATST Telescope Control System (TCS). The requirements of the ATST TCS are set out in [1]. Each of the requirements in that document is listed here along with a description of how each one will be verified. The intention is that as many as possible of the tests described here will be automated by the use of scripts but this is to some extent dependant on the availability of suitable ATST Common Services facilities. The baseline scripting language will be python. 1.2 AUDIENCE The intended audiences of this document are:

- The reviewers of the TCS Critical Design - The developers of the TCS Work Package - The acceptors of the TCS Software Work Package

1.3 SCOPE The tests in this document are limited to the TCS software as described in the TCS Software Design Document. Where tests involve the interface between the TCS and other systems the assumption made here is that the other system behaves correctly. The tests are only aimed at uncovering faults with the TCS end of the interface although as a by product they may reveal problems with the other system. 1.4 OVERVIEW The document is divided into two main sections. The first describes the test environment within which the tests will be executed and the second describes the tests themselves. Each of the tests is assigned a number and this is cross referenced to the requirements in [1]. The initial numbering scheme incremented each test by 10. This was to allow new tests to be inserted as the construction of the TCS progressed without requiring a renumbering. A brief description of the test requirement is provided but if full details are needed then refer to the requirements document. The test description describes both the test itself and the expected outcomes.

TCS Test Plan


2. TEST ENVIRONMENT In order to provide a concrete implementation, the environment described here is as at the time of the TCS Critical Design Review. This will be updated as the ATST infrastructure evolves over the construction phase of the TCS. 2.1 HARDWARE ENVIRONMENT For all the tests described here a general purpose PC with the following features is required to run the TCS

1. Pentium class processor with speed of order 2 GHz 2. 512 Mbytes or greater of RAM 3. Network card supporting 100 Mbit/s ethernet or faster 4. A few Gbytes of spare local disk space for logs etc. 5. An interface card for connection to the GIS

It is recommended that the Ice communication server is run on a completely separate machine along with any engineering screens. If the Ice server becomes starved of CPU cycles during rapid screen updates for example then delivery of events can be severely delayed and this will interfere with the operation of some of the tests. This effect can be mitigated by use of a multiprocessor PC. 2.2 SOFTWARE ENVIRONMENT The following software infrastructure is needed on the test machine

1. Centos 4.3 Linux distribution or later 2. The ATST Common Services Panguitch release or later [2]. 3. V1-0 or later of the TCS 4. Access to the ATST Common services Run time database

Note that the Centos or equivalent Linux releases are not real time operating systems. It is possible therefore to starve the TCS and test environment of CPU cycles if other applications are run on the test machine simultaneously. This has already been mentioned in relation to the Ice Server and engineering screens but applies even more so to general purpose programming tools. Whilst the tests are in progress it is important that all web browsers, text editors, e-mail clients etc. are executed on independent workstations.

TCS Test Plan


3. TEST SCHEDULE Test ID TID-TCS-0010 Requirements 4.4-0001 Requirements Description

The TCS shall be one of the four ATST software principal systems. It shall coordinate observations and communicate commands, status and events as a peer with the other principal systems

Test Description 1) Ensure that the OCS, ICS and DHS are running 2) Verify that all attributes within the TCS begin with the prefix atst.tcs. 3) Use the OCS to send an arbitrary configuration to the TCS. Verify that the

TCS responds correctly 4) Use the ICS to send an arbitrary configuration to the TCS. Verify that the

TCS responds correctly 5) Use the DHS to send an arbitrary configuration to the TCS. Verify that the

TCS responds correctly Notes The requirement here is quite general. We need to cross reference to other tests in

this document and/or take one or two explicit configurations rather than using an arbitrary configuration. It may also not be possible to send a configuration from the DHS but we should identify what status and events it needs (WCS info ?)

Test Result

TCS Test Plan


Test ID TID-TCS-0020 Requirements 4.4-0002 Requirements Description

The TCS shall control the ATST telescope and all telescope subsystems. It shall be responsible for coordinating any activities that use the telescope and/or telescope subsystems

Test Description 1) Create a configuration that includes attributes for each of the TCS subsystems. These attributes will have names that are prefixed atst.tcs.mcs, atst.tcs.ecs, atst.tcs.acs etc.

2) Submit the configuration and confirm by inspection of the logs that all the attributes were sent to the top level TCS head controller

3) Confirm by inspection of the logs for each subsystem that the attributes were then passed to the subsystems either as is or after the addition of further attributes

4) Confirm that the TCS configuration stayed busy whilst the subsystem configuration remained active and that the TCS only switched to done when all the subsystem activity had completed.

Notes

Test Result

TCS Test Plan



The TCS shall control the telescope pointing in raw mode

Test Description 1) Select raw pointing mode by setting atst.tcs.pointingmode to raw 2) Verify that all pointing model parameters are zero 3) Verify that refraction corrections have been disabled.

Notes

Test Result

TCS Test Plan


Test ID TID-TCS-0032 Requirements 4.4-0003, 4.4-0022 Requirements Description

The TCS shall control the telescope pointing in open loop mode

Test Description Requirements 4.4-003 and 4.4-0022 are essentially identical. This test case has therefore been removed and is now covered by TID-TCS-0140

Notes

Test Result

TCS Test Plan



The TCS shall control the telescope in closed-loop mode

Test Description 1) Select open loop pointing mode 2) Verify that all open loop models are running (add names of events/attributes

that contain this information) 3) Select active optics mode and verify that correction signals are being

supplied to M1 and M2 4) Select Adaptive optics mode and verify that correction signals are now

coming from the WCS adaptive optics controller Notes

Test Result

TCS Test Plan



The TCS shall log pertinent data to the ATST facility log system

Test Description 1) Set atst.tcs.debugCategory to default 2) In turn set atst.tcs.debugLevel to 0 to 5(?) 3) Examine the log database for the TCS to confirm that debug messages are

being saved 4) Repeat the above for each of the valid debug categories permitted by

atst.tcs.debugCategory Notes

Test Result

TCS Test Plan



The TCS shall use the ATST Common Services in its operation

Test Description 1) Examine the code for the TCS and confirm that all components of the TCS are loaded into an ATST common services container.

2) Use the IcePack administration service to confirm that all TCS components are registered with IcePack after loading

3) Use the IceStorm administration interface to verify that the TCS registers suitable topics with IceStorm for the dissemination of status

4) Use one of the generic common services tools e.g. adminCLUI to load/unload, init/uninit the TCS components.

Notes

Test Result

TCS Test Plan



The TCS shall be designed and built using the programmatical model defined in the ATST Operational Concepts [3]

Test Description 1) Examine the code for the TCS and confirm that all components of the TCS are loaded into an ATST common services container.

2) Use the IcePack administration service to confirm that all TCS components are registered with IcePack after loading

3) Use the IceStorm administration interface to verify that the TCS registers suitable topics with IceStorm for the dissemination of status

4) Use one of the generic common services tools e.g. adminCLUI to load/unload, init/uninit the TCS components.

5) Confirm that the TCS components and containers are registered with the ATST run time database

6) Confirm that the TCS uses the ATST logging service by examining the entries in the messages table of the database.

Notes

Test Result

TCS Test Plan



The TCS shall be connected to the Global Interlock System (GIS) and follow the protocols defined by the GIS

Test Description 1) Generate a global interlock from the GIS (a global interlock is currently the only interlock the TCS responds to)

2) Confirm that the interlock was received by attempting to send a configuration to the TCS. The configuration should be rejected.

3) Clear the interlock and confirm that the TCS now starts acting on valid configurations without any other special commands

4) Set the atst.tcs.globalInterlock attribute to On 5) Confirm that the GIS receives a global interlock demand 6) Set atst.tcs.globalInterlock to Off 7) Confirm that the GIS no longer sees an interlock from the TCS.

Notes

Test Result

TCS Test Plan



The TCS shall always be available to accept or reject commands. It shall not block any command request while processing another command request

Test Description 1) Issue a configuration to the TCS that will cause an action that will take a long time to complete e.g. slew the telescope a long distance in azimuth and elevation

2) In the middle of the slew send a new configuration to slew to a new target 3) Confirm that the telescope immediately starts moving to the new target and does

not slew first to the original target 4) Once on target, again slew the telescope 5) Whilst slewing, send a stop command 6) Confirm that the TCS responds immediately and the axes come to a halt.

Notes

Test Result

TCS Test Plan



The TCS shall provide a tool for creating pointing maps. This tool shall include features for target acquisition, data collection, pointing map calculation, pointing map storage and retrieval. The pointing map shall contain error information for altitude, azimuth and rotators

Test Description 1) Start the pointingUpdate tool 2) Select a standard sequence of targets or manually select each target from a

selected catalogue 3) Start the sequence and tweak each target onto the reference on the acquisition

system 4) Run tpoint on the results of the sequence and fit a model to the data 5) Update the pointing model parameters in the database 6) Slew to a new sequence of targets and confirm that the rms errors of the model

are in agreement with the rms errors of the new sequence. Notes

Test Result

TCS Test Plan



Static information required by the TCS to operate shall be recoverable after a restart or reboot

Test Description 1) Boot the TCS and check the values of the pointing model parameters i.e. those configuration parameters starting atst.tcs.pointingmodel

2) Confirm that the values in the running TCS agree with those in the database 3) Update the values of the pointing model parameters and then shutdown the TCS 4) Reboot the TCS and verify that the check boxes for the pointing model

parameters are all cleared 5) Init and startup the TCS and confirm that the pointing model parameters have

been reset back to the default values 6) Update the values of the pointing model parameters and then shutdown the TCS 7) Reboot the TCS and verify that the check boxes for the pointing model

parameters are selected 8) Init and startup the TCS and confirm that the pointing model parameters are those

that were updated and are not set to the default values Notes

Test Result

TCS Test Plan



The TCS shall perform scanning motions either autonomously or in coordination with the ICS. Scanning motions shall be either one or two-dimensional motions. They shall be either stepped or continuous motions

Test Description 1) Set atst.tcs.scantype to random 2) Set atst.tcs.scanparams with duration 60s, box size 300” and speed 100”/s 3) Submit the configuration and log the achieved positions and velocities 4) Confirm that the scan stopped after 60s, that the telescope was confined to a box

of side approximately 300” and that the mean speed achieved was 100”/s 5) Set atst.tcs.scantype to grid 6) Set atst.tcs.scanparams with frame HP, dwell 10s, nx 5, ny 5, dx 10”, dy 10” and

orientation 0° 7) Submit the configuration and log the achieved positions and times. 8) Confirm that the telescope stepped to a total of 25 points, that the points were 10”

apart in x and y and that it stayed at each point for 10s 9) Set the atst.tcs.scantype to scan 10) Set atst.tcs.scanparams with frame HP, duration 10s, dx 200”, dy 10”, ny 5,

orientation 0° and reverse set to true. 11) Submit the configuration and log the achieved positions and velocities 12) Confirm that the telescope performed a raster scan of 5 rows with alternate rows

being traversed in opposite directions each separated by 10”. Along each row confirm that the speed was 20”/s and that this lasted for 10s

Notes

Test Result

TCS Test Plan



The TCS shall use International Atomic Time (TAI) in all calculations. It shall use TAI in all data distributed to its subsystems

Test Description 1) Prepare a configuration for the TCS with a start time in the future given as a UTC. The configuration should be such that the telescope will be required to slew.

2) Log the data streams to the TCS subsystems and note the discontinuity in the demands

3) Compare the demand time at the time of the discontinuity with the start time and verify that there is a 33s offset between the two with the demand time leading the start time.

Notes

Test Result

TCS Test Plan



The TCS shall calculate the current solar ephemeris, including but not limited to, local apparent sidereal time, position and rate of motion of the solar disk, the solar rotational axis and the differential rotation rates for solar latitudes. The ephemeris data shall have better accuracy and precision than that required for pointing and tracking the telescope mount.

Test Description 1) Track the center of the solar disk 2) Log the apparent topocentric demands from the TCS along with the heliographic

longitude and latitude of the disk center, the differential track rates and the position angle of the pole.

3) Compare the above demands with the values from the JPL Horizons system and/or the Astronomical Almanac.

4) Confirm that the demand values are identical with the tabulated data from the other sources

Notes

Test Result

TCS Test Plan



The TCS shall provide an open loop pointing model that utilizes only the mount position and pointing map

Test Description 1) Ensure that the WCCS is not active or is not loaded. If it is loaded issue the uninit command.

2) Set the target for the TCS to 1.0, 0.0 in Helioprojective coordinates. 3) Monitor a context viewer to confirm that the telescope tracks the solar limb

without guide corrections from the WCCS Notes

Test Result

TCS Test Plan



The TCS shall provide a closed loop pointing mode that utilizes information from the guider and the adaptive/active optics

Test Description Requirement 4.4-0023 is the same a part of requirement 4.4-0003. The requirements here are therefore already covered by TID-TCS-0034

Notes

Test Result

TCS Test Plan



The TCS shall utilize a pointing map that covers the useful sky. This pointing map shall contain errors for the altitude, azimuth and Nasmyth and coudé rotator. The map shall be sufficiently dense to provide the required open loop pointing accuracy

Test Description 1) Use the pointingUpdate tool to perform a night time pointing test 2) Analyze the data from that test with TPOINT 3) Compare the rms pointing accuracy of the test with the required open loop

pointing accuracy. 4) Re-run a new pointing test and check that the achieved pointing accuracy with the

new map is equal or better than the required open loop pointing accuracy 5) If the pointing accuracy is not met, repeat the pointing test with a larger number

of targets in order to improve the accuracy of the pointing terms or uncover extra terms.

Notes

Test Result

TCS Test Plan



The TCS shall be able to point to all areas of the sky that are accessible to the mount

Test Description 1) Generate a grid of azimuth and elevation positions 2) Set atst.tcs.mode to move 3) Send a sequence of configurations consisting of atst.tcs.az.pos and atst.tcs.el.pos

with the values generated from the azimuth/elevation grid 4) Confirm that the telescope slews to each of the specified positions and that the

difference between demand and achieved position is zero in both axes. Notes

Test Result

TCS Test Plan



The TCS shall be able to track through the zenith blind spot. Some degradation of pointing performance is allowed but the performance shall be immediately restored upon exiting the zenith blind spot.

Test Description 1) Generate a target position with a declination equal to the latitude of the observatory and an RA 5 minutes after the current sidereal time

2) Let the telescope track through the zenith and log or observe the error signals from the drives

3) Note that he error signals are essentially zero until a minute or so prior to transit and recover quickly after transit

Notes It will be necessary to tweak the declination if it is required to go exactly through the zenith depending on the size of the pointing model terms.

Test Result

TCS Test Plan



The TCS shall track a position in the coordinate frames None, Sidereal, Heliocentric or Heliographic

Test Description 1) Set atst.tcs.mode to move 2) Set atst.tcs.az.pos and atst.tcs.el.pos to arbitrary values 3) Confirm that the telescope slews to the designated azimuth and elevation 4) Set atst.tcs.mode to follow 5) Set atst.tcs.ra and atst.tcs.dec to values that guarantee a target above the horizon 6) Confirm that the telescope slews to the target and tracks there. 7) Set atst.tcs.refsys to heliocentric. 8) Set the desired target position to 1.0, 0.0 and confirm the telescope slews and then

tracks the solar limb 9) Set atst.tcs.refsys to heliographic and then the latitude and longitude to the

coordinates of a known sunspot. Leave the system tracking and confirm that over a long period of time the spot remains centered in the field of view.

Notes

Test Result

TCS Test Plan



The TCS shall accept input and display current positions in any of the following coordinate systems: Raw, Alt-Az, RA/HA/declination, Heliocentric, Heliographic

Test Description 1) Open the TCS engineering display for the mount, coude and nasmyth rotators and note the azimuths, elevations and rotation angles displayed

2) On the top level TCS engineering screen note the displays for RA and Declination

3) On the ACS screens when viewing the solar disk / corona note the readouts of heliographic and heliocentric positions as the cursor is moved across the image. (These coordinates are generated from information supplied by the TCS)

4) Set atst.tcs.mode to move 5) Set atst.tcs.az.pos and atst.tcs.el.pos to arbitrary values 6) Confirm that the telescope slews to the designated azimuth and elevation 7) Set atst.tcs.mode to follow 8) Set atst.tcs.ra and atst.tcs.dec to values that guarantee a target above the horizon 9) Confirm that the telescope slews to the target and tracks there. 10) Set atst.tcs.refsys to heliocentric. 11) Set the desired target position to 1.0, 0.0 and confirm the telescope slews and then

tracks the solar limb 12) Set atst.tcs.refsys to heliographic and then the latitude and longitude to the

coordinates of a known sunspot. Leave the system tracking and confirm that over a long period of time the spot remains centered in the field of view.

Notes

Test Result

TCS Test Plan



The TCS shall accept a target position in any of the above coordinate systems. The TCS shall point the telescope to the target position and track it in the requested coordinate system. Additionally the TCS shall have fixed positions for various engineering positions including the parked position and the service position. These fixed positions shall be reconfigurable

Test Description 1) Set atst.tcs.mode to park and submit the configuration 2) Confirm that the TCS and its subsystems go their park positions 3) Set atst.tcs.mode to service and submit the configuration 4) Confirm that the TCS and its subsystems go to their service positions 5) Set one or more of the following attributes (all prefixed atst.tcs.) mcsparkazpos,

mcsparkelpos, ecsparkazpos, ecsparkelpos, mcsparkcouderotpos, mcsparknasmythrotpos

6) Set atst.tcs.mode to park and confirm that the new park positions are used. 7) Set one or more of the following attributes (all prefixed atst.tcs.)

mcsserviceazpos, mcsserviceelpos, ecsserviceazpos, ecsserviceelpos, mcsservicecouderotpos, mcsservicenasmythrotpos

8) Set atst.tcs.mode to service and confirm that the new service positions are used Notes The first part of this requirement is the same as 4.4-0027 and 4.4-0028 so won’t be

repeated as part of this test.

Test Result

TCS Test Plan



The TCS shall accept and display offsets from the nominal input target position in any of the above coordinate systems

Test Description 1) For each supported target coordinate systems, set the attribute atst.tcs.offsetrefsys 2) Set the attribute atst.tcs.targetoffset 3) Submit the configuration and confirm that the offset was accepted.

Notes

Test Result

TCS Test Plan



The TCS shall be responsible for controlling the flow of wavefront information between the subsystems. The TCS shall also be responsible for enabling and disabling wavefront information

Test Description 1) Set atst.tcs.activeoptics first to openloop and then closedloop 2) Set atst.tcs.fieldstab to on when atst.tcs.activeoptics is closedloop 3) Set atst.tcs.adaptiveoptics to on and then off

Notes

Test Result

TCS Test Plan



The TCS shall control the transmission of wavefront data between the WCCS and M1CS

Test Description 1) With the entrance aperture and the M1 cover open, set atst.tcs.activeoptics to closedloop

2) Confirm that the M1CS is now receiving and acting on the data from the WCCS Notes

Test Result

TCS Test Plan



The TCS shall control the transmission of wavefront data between the WCS and M2CS

Test Description 1) Set atst.tcs.fieldstab to on 2) Confirm that the M2CS is now receiving and acting on the data from the WCCS

Notes

Test Result

TCS Test Plan



The TCS shall control the transmission of wavefront data between the WCS and MCS

Test Description 1) Set atst.tcs.fieldstab to on 2) Confirm that the MCS is now receiving wavefront data generated by the WCCS

Notes

Test Result

TCS Test Plan



The TCS shall control the transmission of wavefront data between the WCS and the FOCS

Test Description 1) Set atst.tcs.activeoptics to closedloop 2) Confirm that the FOCS is now receiving wavefront data from the WCS

Notes

Test Result

TCS Test Plan



The TCS shall control the transfer of a daily temperature profile to the M1CS

Test Description 1) Confirm that atst.tcs.m1cs.thermalmodel is set to On 2) Set atst.tcs.m1cs.thermalprofile to be an array with a single element [0.0] 3) Confirm that atst.tcs.m1cs.thermalState shows that the model is “Reactive” 4) Wait 24 hours (this probably needs to be configurable !) and confirm that after

23.5 hours a warning is issued that the model is about to expire and that after 24 hours an error alarm is raised.

5) Repeat the above but after some hours send a new thermalprofile. Confirm that the original timer is cancelled and that a new one is started.

6) Set the atst.tcs.m1cs.thermalprofile to be an array as specified in the TCS/M1 ICD [5]

7) Confirm that atst.tcs.m1cs.thermalState shows the model as “Predictive” 8) Confirm that a warning is raised 30 mins before the last time given in the

thermalprofile array. 9) Confirm that an error alarm is raised when the current time reaches the latest time

in the thermalprofile array 10) Repeat step 6 but before the alarms can be raised, issue a new profile and confirm

that the old timer is cancelled and a new timer is started. 11) Repeat step 6 but make the profile extend over a period of more than 24 hours.

Confirm that the warnings and alarms are raised after 23.5 and 24 hours and not when the latest time in the profile is reached.

Notes

Test Result

TCS Test Plan



The TCS shall control the temperature set points for all thermal systems within the ATST telescope structure and surrounding environment.

Test Description 1) Change the M1CS thermal set point by setting atst.tcs.m1cs.thermal.offset. This is the offset from ambient

2) Change the M2CS thermal set point by setting atst.tcs.m2cs.thermal.setpoint. 3) Need to check how to access the set points of the FOCS 4) Are there any set points for the WCCS – none are specified? 5) Are there any set points for the ACS e.g. the camera temperature? 6) Set the ECS coolmode to “set” and the coolpos to the temperature required.

Confirm that the enclosure temperature converges on coolpos. 7) Set the ECS coolmode to “Ambient” and the cooldpos to say -2. Confirm that the

enclosure temperature converges on the ambient temperature minus 2 8) For the HSA, set atst.tcs.hsa.thermal.reflector.setpoint and

atst.tcs.hsa.thermal.beamdump.setpoint to specific values. Turn on the cooling systems and verify the temperatures converge to the set points.

Notes

Test Result

TCS Test Plan



The TCS shall monitor the status of all thermal systems within the ATST telescope structure and surrounding environment

Test Description 1) From the top level TCS engineering screen launch the thermal summary screen 2) Confirm that the screen displays the temperatures, flow rates and states of each of

the TCS subsystems and of their sub components. It may be necessary to click on the symbol representing the subsystem or pass the cursor over it to get all the information required.

3) Either simulate or trigger a thermal alarm by switching off the cooling to a system, changing the temperature tolerance etc.

4) Confirm that the mechanism in question goes in to an alarm state by either turning yellow or red depending on the severity of the alarm

5) Remove the trigger for the thermal alarm and confirm that the mechanism symbol goes back to its normal neutral state

Notes

Test Result

TCS Test Plan



The TCS shall respond to a thermal overload from any of the thermal systems within the ATST telescope structure and surrounding environment

Test Description 1) With enclosure aperture, mirror cover and dark slide opened, in turn switch of the cooling to mirrors 1 to 13 and confirm that in each case the three mechanisms were closed

2) Attempt to open each of the mechanisms and confirm that the configurations are rejected

3) Turn on mirror cooling to a random set of mirrors and confirm that the configurations are still rejected

4) Simulate a temperature overload on any of the mirrors, the HSA or the telescope structure and confirm that in each case the dark slide, mirror cover and entrance aperture are closed.


6) Remove the thermal overloads on a number (but not all) of the mirrors, TMA or HSA and confirm that configurations to open any of the mechanisms are still rejected.

Notes See also TID-TCS-590

Test Result

TCS Test Plan



The TCS shall recover from a thermal overload condition when the condition has been removed. The recovery should be initiated by the operator

Test Description 1) With enclosure aperture, mirror cover and dark slide opened, in turn switch of the cooling to mirrors 1 to 13 and confirm that in each case the three mechanisms were closed


3) Turn on mirror cooling to all the mirrors and confirm that commands to open the three mechanisms are once again accepted

4) Simulate a temperature overload on any of the mirrors, the HSA or the telescope structure and confirm that in each case the dark slide, mirror cover and entrance aperture are closed.


6) Remove all the temperature overloads and confirm that the three mechanisms can again be opened.

Notes

Test Result

TCS Test Plan



The TCS shall control the state of the enclosure ventilation gates and fans. The state shall be selected by the operator with a goal of automatically determining the state

Test Description 1) Set atst.tcs.ecs.fanpos to a value in the range 0 to 100 2) Set atst.tcs.ecs.ventpattern to one of the available pattern numbers 3) Submit the configuration and confirm that the fans and vents opened or set to the

correct values Notes

Test Result

TCS Test Plan



The TCS shall control the ATST weather reporting station and provide data from this station.

Test Description 1) Ensure that the ATST weather reporting station and the TCS are both shut down 2) Start the TCS via the container manager and confirm that the weather station

software is restarted Notes

Test Result

TCS Test Plan



The TCS shall control the sequencing of commands sent to the subsystems

Test Description 1) Set the atst.tcs.tracking attribute to off 2) Confirm that simultaneously the dark slide, enclosure aperture and M1 cover are

closed 3) Confirm that when and only when the mechanisms above have closed, the mount

and enclosure tracking modes are set to halt Notes

Test Result

TCS Test Plan



The TCS shall control the Enclosure Control System

Test Description 1) Track a solar or sidereal target 2) Monitor the atst.tcs.ecs.trajectory event 3) Set atst.tcs.ecs.ventpattern to 0 and confirm that the vents all moved to the correct

positions 4) Set atst.tcs.ecs.coolmode to ambient and confirm that the ECS tracks the ambient

temperature at the appropriate offset value 5) Monitor the events atst.tcs.ecs.cpos, atst.tcs.ecs.thermal.cpos and verify that the

data displayed by the TCS is the same. Notes

Test Result

TCS Test Plan



The TCS shall control the Mount Control System

Test Description 1) Track a solar or sidereal target 2) Monitor the atst.tcs.mcs.trajectory event 3) Confirm that the mount axes and rotator are following the stream of demands 4) Monitor the events atst.tcs.mcs.mountcpos, atst.tcs.mcs.thermal.temps,

atst.tcs.mcs,coude.cpos, atst.tcs.mcs.nasmyth.cpos and confirm that the TCS is displaying identical data.

Notes

Test Result

TCS Test Plan



The TCS shall control the M1 Mirror Control System

Test Description 1) Start up the TCS via the container manager 2) Confirm from the logs that the M1CS is loaded and receives the commands init

and startup from the TCS 3) Issue a thermal profile to the M1CS from the TCS and, over a period of time

record both the demand set point temperature and the achieved temperature. Confirm that the achieved temperature tracks the demand temperature

4) Now set atst.tcs.m1cs.thermalmodel to Off. Again record the demand set point temperature and the achieved temperature. Confirm that the demand and achieved temperatures are now uncorrelated.

5) Notes

Test Result

TCS Test Plan



The TCS shall control the M2 Mirror Control System

Test Description 1) Start up the TCS via the container manager 2) Confirm from the logs that the M2CS is loaded and receives the commands init

and startup from the TCS 3) Issue configurations to translate and tilt M2 4) Confirm that the image shifts by the expected amount for the demanded M2

offsets. 5) Set atst.tcs.m2cs.thermalcontrol to off 6) Confirm that an alarm is raised in the TCS and that M2’s temperatures starts to

rise Notes

Test Result

TCS Test Plan



The TCS shall control the Feed Optics Control System

Test Description 1) Start up the TCS via the container manager 2) Confirm from the logs that the FOCS is loaded and receives the commands init

and startup from the TCS 3) Set atst.tcs.focus to nasmyth 4) Confirm that the beam is directed to Nasmyth 5) Set atst.tcs.focus to coude 6) Confirm that the beam is now directed to Coudé

Notes

Test Result

TCS Test Plan



The TCS shall control the Wavefront Control System

Test Description 1) Start up the TCS via the container manager 2) Confirm from the logs that the WCCS is loaded and receives the commands init

and startup from the TCS 3) Set atst.tcs.wccs.fieldstab to closed and confirm that dependent on configuration

the image is now stabilized 4) Set atst.tcs.wccs.activeoptics to closed and confirm that M1 is now receiving a

stream of zernike corrections from the WCCS Notes

Test Result

TCS Test Plan



The TCS shall control the Acquisition and Guiding Control System.

Test Description 1) Start up the TCS via the container manager 2) Confirm from the logs that the ACS is loaded and receives the commands init and

startup from the TCS 3) Set atst.tcs.acs.filter to an allowed filter name and confirm that the correct filter is

inserted 4) Set atst.tcs.acs.exposure to continuous and confirm from the image display that a

continuous series of exposures are taken. Notes

Test Result

TCS Test Plan



The TCS shall accept or reject a command given on its public interface within 0.1s

Test Description 1) Send a command to the TCS and log its arrival time 2) Compare the arrival time with the logged timestamp of the response

Notes

Test Result

TCS Test Plan



The TCS shall be operational and ready to receive and act upon commands within 5 minutes of a cold power off start of its hardware

Test Description 1) Switch off the TCS PC 2) Restart the PC and note the current time 3) Note the time at which the PC is fully rebooted and the TCS is up and running.

Notes

Test Result

TCS Test Plan



The TCS shall apply any external offsets or adjustments within 0.1 seconds.

Test Description 1) Send a configuration consisting of the attributes atst.tcs.targetoffset and offsetrefsys

2) Log the time of arrival of the command at the TCS 3) Inspect the trajectory stream to the mount and locate the sample at which the

demands showed a discontinuity 4) Compare the time stamp of this sample with the time stamp of the configuration

arrival time and confirm the difference is less than 0.1s Notes

Test Result

TCS Test Plan



The TCS shall have no appreciable contribution to the optical error budget

Test Description 1) Notes Not sure yet how to test this. It seems you need to measure the optical image quality

both with and without the TCS running.

Test Result

TCS Test Plan



The TCS shall not consume more than 50% of its processing capability. The TCS and the operating system shall not consume more than 50% of the hard disk capacity

Test Description 1) Load the TCS application 2) Configure the TCS so that it is tracking the Sun and then start a continuous scan

with as many of the control loops closed as possible. The aim is to set a configuration that puts the maximum load on the TCS

3) Use top or some other system monitoring tool to confirm that the CPU is on average less than 50% utilized.

4) Use du or some system tool to confirm that less than 50% of the local disk capacity is unused.

Notes

Test Result

TCS Test Plan



The TCS shall perform open loop pointing while tracking to within 3 arc-seconds with a goal of 1 arcsec.

Test Description 1) Perform a full pointing test and update all the derived pointing parameters in the TCS

2) Perform a second pointing test and verify that the rms pointing error with no fitting is less than 3 arcsec.

Notes

Test Result

TCS Test Plan



The TCS shall perform closed loop pointing while tracking to within 0.1 arsecs.

Test Description 1) Set the telescope to track a sidereal or solar target 2) Turn the field stabilization on 3) Log the residual errors between the target demand position and the target location 4) Confirm that the residual error is less than 0.1” when the track rate is less than

150”/sec Notes

Test Result

TCS Test Plan



The TCS shall provide accurate pointing, for both open-loop and closed-loop, for all azimuth angles and for all altitude angles between +10° and +89.5°.

Test Description 1) Perform a full pointing map and then update the pointing parameters in the TCS 2) Repeat the pointing map for a new set of targets that fully cover the azimuth and

elevation range of the telescope 3) Confirm that the rms error on the new pointing map is less than 3 arcsec.

Notes

Test Result

TCS Test Plan



The TCS shall track through the zenith blind spot, defined as the area within 0.5 degrees of the zenith.

Test Description 1) Set the TCS reference system to ICRS 2) Set the demand declination to the latitude of the observatory 3) Set the RA to 16 minutes later than the current LST 4) Confirm that a warning is raised after about a minute when the target is about to

enter the zenith blind spot (the exact time will depend on how close the target will go to the true zenith which in turn will depend on the current point model)

5) Confirm that a further warning is raised when the telescope enters the actual blind spot

6) Confirm that the warning is cleared when the target leaves the zenith blind spot. Notes

Test Result

TCS Test Plan



The TCS shall position the Nasmyth rotator to within 3 arc-seconds of the calculated position

Test Description 1) Set atst.tcs.focus to nasmyth 2) Track a sidereal or solar target 3) Examine the trajectory stream atst.tcs.mcs.nasmythtrajectory 4) Confirm that the demand position (in degrees) has at least 4 decimal places of

precision and that a smooth track is being supplied Notes

Test Result

TCS Test Plan



The TCS shall position the coudé rotator to within 3 arc seconds of the calculated position.

Test Description 1) Set atst.tcs.focus to coudé. 2) Track a sidereal or solar target 3) Examine the trajectory stream atst.tcs.mcs.coudetrajectory 4) Confirm that the demand rotator position in degrees is given to a least 4 decimal

places and that the track is smooth. Notes

Test Result

TCS Test Plan



The TCS shall calculate the position of all mount and enclosure drives at a rate of at least 20Hz

Test Description 1) For a short time log the events atst.tcs.mcs.mounttrajectory and atst.tcs.ecs.trajectory

2) Note the time stamps of successive samples and see that they are separated by 50ms

3) Examine the TCS pointing code and see that the fast pointing loop is running at a rate of at least 20hz.

Notes

Test Result

TCS Test Plan



The TCS shall send pointing values to the ECS and MCS with timestamps for the correct time the data should be applied. The data should never arrive more than 10 milliseconds after the time listed in the timestamp.

Test Description 4) For a short time log the events atst.tcs.mcs.mounttrajectory and atst.tcs.ecs.trajectory

1) Note the time stamps of successive samples and see that they are separated by 50ms

2) Turn on diagnostics in the MCS and ECS and log the time of arrival of the samples. Confirm that the data always arrives no later than 10ms after the time stamp

Notes

Test Result

TCS Test Plan



The TCS shall not cause additional delay in the transfer of wavefront data from the WCS to the other subsystems.

Test Description 1) Notes

Test Result

TCS Test Plan



The TCS shall provide the forecasted temperature profile for the M1 mirror at least 2 hours into the future.

Test Description 1) Generate an M1 temperature profile and pass to the TCS for onward transmission to the M1CS

2) Verify that a timer is started to expire in the sooner of 24 hours or at the last time specified in the profile

3) Confirm that a warning is raised 2 hours prior to the expiration of the timer 4) Confirm that an alarm is raised if the timer expires

Notes The TCS does not provide the temperature profiles and so can’t guarantee that one will be available for at least 2 hours into the future. What it can do is raise alarms if one isn’t provided so this is what is tested here. See [4]

Test Result

TCS Test Plan



The TCS shall respond to thermal overload signals from the subsystems within 0.25 seconds.

Test Description 1) Generate a thermal overload or alarm by switching off the cooling to a mirror 2) Log the time at which the cooling is switched off 3) Log the warning generated by the TCS in response to the loss of cooling 4) Confirm that the warning is generated within 0.25s of the cooling being lost

Notes See also TID-TCS-0310

Test Result

TCS Test Plan



The TCS shall never block a subsystem from operating

Test Description 1) Send a configuration to the TCS that results in a time consuming action being started in a subsystem e.g. slew to a new target that is a considerable distance from the current position

2) Whilst slewing issue a configuration that brings he mount to a halt 3) Confirm that the axes stop very shortly after the command is executed and that in

particular the mount does not slew all the way to the new position and then stop. Notes

Test Result

TCS Test Plan



The TCS shall command the subsystems in a fashion whereby an incomplete command or set of commands, or a transmission error, will not cause the subsystem to execute an improper command or perform an improper action.

Test Description 1) Notes This requirement is not within the control of the TCS. The response to incomplete or

corrupted commands can only be dealt with by the subsystems

Test Result

TCS Test Plan



The TCS shall provide and operate a time master for the ATST.

Test Description 1) Notes Is the time master going to be a separate standalone system?

Test Result

TCS Test Plan



The TCS shall use the defined interface to the Global Interlock System

Test Description 1) Notes Has the defined interface been specified? The baseline the TCS has adopted until

advised otherwise is to use a 48 channel digital i/o card the PCI-7348 from Adlink.

Test Result

TCS Test Plan



The TCS shall use TCP/IP for all communications on the Control LAN

Test Description None Notes This requirement is contained within requirement 4.4-0210 provided the ATST

Common Services use TCP/IP for all communications over the control LAN.

Test Result

TCS Test Plan



The TCS shall use the ATST Common Services for all communications on the Control LAN

Test Description 1) Examine the TCS source code 2) Verify that all communications with the OCS or TCS subsystems goes through

the connection or event service 3) Verify that no private sockets or other communication methods are used within

the code. Notes

Test Result

TCS Test Plan



The TCS shall use containers and components as defined by the Operational Concepts Document [3]

Test Description 1) Use AdminCLUI or the Testharness to load the TCS into a container 2) Use the same application to load the TCS components and controllers into the

TCS container 3) Verify that this is possible

Notes

Test Result

TCS Test Plan



The TCS shall use the proper configuration identifier in all communications.

Test Description 1) Use the OCS to send a configuration to the TCS 2) Log the configuration identifier received by the TCS. 3) If the configuration involves generating additional configurations for the TCS

subsystems confirm that each such configuration is given a new unique configuration identifier

Notes

Test Result

TCS Test Plan



The TCS shall obey the ATST Common Services command interface when issuing all commands to the TCS subsystems

Test Description 1) Load each TCS subsystem into its container 2) Enable logging on these subsystems 3) Load the TCS into its container and issue init and startup to it. 4) Verify from the logs that each TCS subsystem was sent an init and startup

command 5) Issue a range of configurations to the TCS. 6) Confirm that each subsystem that is involved in the configuration receives a

submit command with a suitably constructed configuration Notes

Test Result

TCS Test Plan



The TCS shall use the ATST Common Services event interface to send and receive asynchronous information between itself and the subsystems.

Test Description 1) Using the TCS ICDs, note the names of events that transit data asynchronously between itself and the other systems

2) Use a generic ATST Common Services tool to verify that each of these events can be subscribed to.

Notes

Test Result

TCS Test Plan



The TCS shall define a directory stream to transmit pointing and tracking data from the TCS to the MCS.

Test Description 1) Log the event atst.tcs.mcs.mounttrajectory 2) Confirm that the trajectory stream contains the demand positions and velocities of

the mount axes. Notes

Test Result

TCS Test Plan



The TCS shall define a trajectory stream to transmit pointing and tracking data from the TCS to the ECS.

Test Description 1) Monitor the event stream atst.tcs.ecs.trajectory 2) Verify that it contains a time stamp and demand positions for the enclosure and

shutter Notes

Test Result

TCS Test Plan



The TCS shall define a wavefront data stream to transmit wavefront errors from the WCCS to the M1CS, M2CS and MCS.


Test Result

TCS Test Plan



The TCS shall accept and operate on configurations sent by the other principal systems. All TCS commands shall be based upon configurations

Test Description 1) Examine the TCS/OCS ICD [6] and confirm that the public interface of the TCS operates entirely via configurations

2) Submit an arbitrary number of configurations to the TCS and verify that id the configuration is valid it is acted on and matched.

Notes

Test Result

TCS Test Plan



The TCS shall be responsible for any sequence or order of command execution for commands sent by the principal systems


Test Result

TCS Test Plan



The TCS shall obey the ATST Common Services command interface when receiving all commands from the principal systems

Test Description 1) Use a generic common services tool such as AdminCLUI or Testharness 2) Load the TCS and its components into a container and verify that this is possible 3) For each of the loaded components issue the init and startup commands and

verify that these are accepted 4) Now submit one or more configurations and verify that these are accepted and

acted upon if they are valid 5) For each of the components in the TCS issue the shutdown, uninit and remove

commands and verify that the components are unloaded Notes

Test Result

TCS Test Plan



The TCS shall use the ATST Common Services event interface to send and receive asynchronous information between itself and the OCS and ICS

Test Description 1) Start up the TCS engineering screens 2) For all updating text fields etc. leave the cursor over the widget and note the

names of the common services events that are being monitored 3) Examine the OCS and ICS and confirm that they are monitoring these same

events Notes

Test Result

TCS Test Plan



The TCS shall provide an interface to allow the other principal systems to adjust the position of the telescope.

Test Description 1) Submit a configuration to the TCS consisting of the attributes atst.tcs.offsetrefsys and atst.tcs.targetoffset

2) Confirm that the telescope offsets to the new demand position 3) Submit a configuration with atst.tcs.refsys set to ICRS and atst.tcs.target set to a

suitable RA and Dec. i.e. one currently above the elevation lower limit 4) Now set atst.tcs.trackrate to non zero values and confirm that the TCs no longer

tracks at the sidereal rate 5) Send a configuration consisting of either a random, grid or scan type scan 6) Confirm that the telescope offsets as specified and then reverts to its previous

tracking target once the scan is complete Notes

Test Result

TCS Test Plan



The TCS shall provide an interface to publish all appropriate telescope status information (i.e. position, rate, time, state etc.)

Test Description 1) Start up an OCS client to monitor each of the event streams defined in the OCS/TCS ICD [6] using the common services event service

2) Start up another client and monitor the same event streams 3) Verify that each client receives the same data and that any number of clients can

subscribe to the same data streams Notes

Test Result

TCS Test Plan



The TCS shall obey the OCS-to-TCS interface defined by both principal systems. The interface is to be written by the ATST project with input from the TCS contractor

Test Description 1) Examine the TCS/OCS ICD [6] 2) Using the TCS engineering screens submit configurations based on the attributes

that are contained in that ICD 3) Monitor the event streams generated by the TCS 4) Confirm that attributes specified in the ICD exist within the TCS

Notes

Test Result

TCS Test Plan



The TCS shall obey the GIS to TCS interface. This interface is to be written by the ATST project with input from the TCS contractor.

Test Description 1) Generate a global interlock via the GIS interface ( a global interlock is currently the only interlock the TCS must respond to)

2) Verify that an interlock status is set within the TCS 3) Clear the interlock from the GIS and verify that the interlock status is cleared

within the TCS 4) Set atst.tcs.globalInterlock to On and submit this configuration 5) Verify via the GIS interface that it has received a global interlock demand from

the TCS 6) Set atst.tcs.globalInterlock to Off and verify that the GIS is no longer seeing an

interlock demand from the TCS Notes

Test Result

TCS Test Plan



The TCS shall provide a compliance matrix noting the TCS requirements in this document, the compliance or non-compliance of the requirement, additional comments on the requirement, the test used to show the compliance and any additional test results

Test Description 1) Obtain a copy of the TCS Software Design Description [4] and refer to Section 6. Verify that the table in that section lists each requirement in the TCS requirements document [1] along with a cross reference to where compliance is provided. Also note the comments column providing qualification or expansion of the requirement

2) Use this document to verify that each requirement in [4] has a Test Identifier that can be used to show compliance along with sections for notes on the performance of the test as well as the test results.

Notes

Test Result

TCS Test Plan



The TCS shall supply test software (source and executable) for all TCS requirements

Test Description 1) Notes Test software is likely to be supplied as a set of python scripts by this is TBD

depending on the state of ATST Common services scripting support

Test Result

TCS Test Plan



The TCS shall supply a test plan to describe the number and types of tests for the TCS requirements. Additional software, hardware, resources and test equipment shall be included.

Test Description 1) Verify using this document that a test is provided for each requirement in the ATST TCS Requirements Document [1]

2) Verify that section 2 of this document contains the details of the software, hardware, resources and test equipment that are needed to execute the tests

Notes

Test Result

TCS Test Plan



The TCS shall supply an engineering display for the TCS operating software.

Test Description 1) Launch the JES screens for the TCS 2) Confirm that all configuration parameters listed in the TCS/OCS ICD can be set

from these screens 3) Execute a number of configurations from these screens and confirm that the

responses are as expected. 4) Confirm that all the status events listed in the TCS/OCS ICD can be monitored

through the screens 5) If any configuration item or event can not be monitored, place the screens into

edit mode and add extra text entry or text update fields linked to the desired parameters.

6) Switch the screens to execute mode and confirm that the new fields are now displaying or setting the desired parameters.

Notes

Test Result

TCS Test Plan



The TCS shall provide a final design document. This document shall include all details necessary to construct the TCS.

Test Description 1) Verify by inspection that the document called the TCS Software Design Document contains a detailed description of the structure and operation of the ATST TCS

Notes

Test Result

TCS Test Plan



The TCS shall document all public software interfaces. Public software interfaces are used by the principal systems, communications systems and the TCS subsystems

Test Description 1) Verify the existence and content of each of the following Interface Control Documents

2) ICD 4.2/4.4 The OCS to TCS interface 3) ICD 3.1.6/4.4 The ICS to TCS interface 4) ICD 4.3.4.4 The DHS to TCS interface 5) ICD x.x/4.4 The GIS to TCS interface 6) ICD 1.1/4.4 The TCS to MCS interface 7) ICD 1.1.4.4 The TCS to M1CS interface 8) ICD 1.4.4.4 The TCS to M2CS interface 9) ICD 1.5/4.4 The TCS to FOCS interface 10) ICD 2.3/4.4 The TCS to WCCS interface 11) ICD 1.8/4.4 The TCS to ACS interface 12) ICD 4.4/5.0 The TCS to ECS interface 13) ICD 4.4/6.3.2 The TCS to EMS interface 14) ICD 1.3/4.4 The TCS to HSA interface 15) ICD 3.1.1/4.4 The TCS to PAC interface

Notes

Test Result

TCS Test Plan



The TCS shall provide an operators Manual describing the use of the TCS by an ATST engineer

Test Description 1) Refer to the ATST User Manual Notes

Test Result

TCS Test Plan



The TCS shall presume all communications to it are secure

Test Description 1) Start up the TCS engineering screens from any account on any machine on the ATST control LAN

2) Submit an arbitrary configuration from that engineering interface 3) Confirm that the configuration (if valid) is accepted and acted on.

Notes

Test Result

TCS Test Plan



The TCS shall not be designed or constructed in a way to preclude porting the software to another operating system.

Test Description 1) Checkout the TCS into a clean directory 2) Examine the source code and note it is written in a mixture of Java, C++ and C

(scripts may be written in python) 3) Note that any os specific features are confined to a few well defined source files

maintained under separate directory headings Notes

Test Result

TCS Test Plan



The TCS shall not be designed or constructed in a way to preclude porting the software to another CPU architecture

Test Description 1) Checkout the TCS source code into a clean directory 2) Examine the source code and note that any CPU specific features are extracted

into well defined separate modules Notes

Test Result

TCS Test Plan



The TCS shall not consume resources without eventually returning equivalent resources to the operating system. Resources include network ports, TCP/IP buffers, physical memory and disk space.

Test Description 1) Monitor the memory usage of the TCS PC prior to starting the TCS 2) Whilst the TCS is operating monitor the memory usage of the PC 3) Shutdown the TCS and confirm that he memory usage has dropped back to what

it was originally Notes Not sure what to do about locally written log files – it probably not a good idea just

to delete them though this would meet the requirement!

Test Result

TCS Test Plan



The TCS shall not fail if a subsystem unexpectedly changes state, does not respond, or otherwise fails to operate as required. The TCS shall protect other subsystems from such failure.

Test Description 1) Whilst the TCS is running, shutdown, uninit or remove one or more of the TCS subsystems

2) Note that although alarms may be raised and some configurations requirements will fail, the TCS will otherwise operate normally, continuing to raise events for other subsystems

Notes

Test Result

TCS Test Plan



The TCS should never need to be rebooted or restarted during normal operations

Test Description 1) Start the TCS application in the early morning 2) Use the TCS to support general observing. 3) Confirm that there are no reboots or restarts that can be attributed to the TCS

application 4) At the end of the day and particularly at sun set confirm that the TCS behaves

normally and can be slewed back to the park position 5) The next day slew the telescope to acquire the Sun following the standard

procedures 6) Confirm that this is possible and that the TCS has not been restarted over night.

Notes

Test Result

TCS Test Plan



The TCS shall provide all source code written for the TCS

Test Description 1) Checkout all source code for the TCS from CVS into a clean directory 2) Build the application 3) Start the application and confirm that it loads and that the full functionality of the

TCS as described in the User Manual is available Notes

Test Result

TCS Test Plan



The TCS shall document all source code in a manner consistent with good software practices.

Test Description 1) Checkout the TCS application from CVS 2) Inspect the coding and commenting style 3) For those modules written in Java run Javadoc and confirm that classes, methods

and parameters are fully described. Notes

Test Result

TCS Test Plan



The TCS shall use a revision repository (such as CVS) during construction. The repository shall be accessible by the ATST during construction.

Test Description 1) Set CVSROOT to :pserver:@sirius.observatorysciences.co.uk:/usr/local/cvs

2) cvs login 3) cvs checkout atst

Notes The TCS code and supporting libraries are not publicly available. You must first acquire a valid user name and provide the IP address of the machine you will use to access the code so that a hole can be opened in the server firewall.

Test Result

TCS Test Plan



The TCS shall respond to a global interlock signal by placing itself and its subsystems in a safe state. The safe state shall prevent the TCS from moving any mechanisms or equipment while the interlock condition exists.

Test Description 1) Generate a global interlock via the GIS 2) Submit a configuration that would result in mechanism movement 3) Confirm that when the configuration is submitted it is rejected with a message

that an interlock is present 4) Submit a configuration that would result in a stop being sent to moving

mechanism 5) Confirm that the configuration is accepted and that the mechanism halts 6) Remove the global interlock. 7) Confirm that configurations are again accepted without requiring any special

extra attributes being sent Notes

Test Result

TCS Test Plan



The TCS shall generate a global interlock signal if it detects an unsafe condition where personnel or equipment may be harmed.

Test Description 1) Send a configuration with tcs.globalInterlock set to On 2) Confirm that all configurations that would result in mechanism movement are

now rejected. 3) Confirm that the GIS receives an interlock demand signal from the TCS 4) Send a configuration with tcs.globalInterlock set to Off 5) Confirm that the GIS interlock demand signal is cleared 6) Confirm that configurations causing mechanism movement are once again

accepted. Notes The test here makes assumptions about how the GIS responds to an interlock demand

from the TCS. If on receiving an interlock demand it raises an interlock request back to the TCS then simply removing the TCS demand may not necessarily clear the interlock request.

Test Result

TCS Test Plan


4. REFERENCES

[1] Goodrich, B., ATST Telescope Control System Design Requirements, SPEC-0019, Rev. A [2] Wampler, S., Goodrich, B. and Tvedt, J., The ATST Common Services Design Document, SPEC-

0022, Rev. A [3] Wampler, S., The ATST Operational Concepts Design Document, SPEC-0013, Rev. A [4] Mayer, C., Terrett, D., and Wallace, P.T., The TCS Software Design Description, SPEC-0021,

Rev. C [5] Mayer, C.J., The M1 Assembly to Telescope Control system Interface, ICD 1.2/4.4, Rev. B [6] Mayer, C.J, Terrett, D. & Wampler, S., The Observatory Control System to Telescope Control

System Interface, ICD 4.2/4.4, Rev. B

TCS Test Plan · 2020. 1. 22. · TCS Test Plan CON-0022 Rev A Page 1 of 102 1. INTRODUCTION 1.1...

Documents

Transcript of TCS Test Plan · 2020. 1. 22. · TCS Test Plan CON-0022 Rev A Page 1 of 102 1. INTRODUCTION 1.1...