TCS Test List for Y2000 Compliance Tests on Control Model
* Last update: PSI/COU 28/02/02


Preconditions for the following tests:

1) 	Login as tcs user

2)	Shutdown the environments wt0tcs, wa0tcs
	vccEnvStop -e wt0tcs
	vccEnvStop -e wa0tcs

3)	a) reboot of lcu's pushing the reset button: 
	in the control model room 72 reset the following LCUs:
	la0agc, la0iac, lt0alt, lt0az, lt0hb, lt0adc, lt0enc, lt0m2,
        and  lt0m1m3
	in the optical lab room 38 reset the following LCUs:
	la0aga, la0iaa, lt0ada

	b) check that all the LCUs have rebooted successfully:
	open the file $VLTDATA/ENVIRONMENTS//lcubootLogFile
	this file should contain at the end:
	"LCC INITIALISATION SUCCESSFULL."

Remark: the environments of the LCUS are generated on two different
        machines:
	on wa0tcs: la0aga, la0agc, la0iaa, la0iac
	on wt0tcs: lt0ada, lt0adc, lt0alt, lt0az, lt0enc, lt0hb, 
                   lt0m1m3, lt0m2

4)	start the environments wt0tcs, wa0tcs
	vccEnvStart -e wt0tcs
	vccEnvStart -e wa0tcs

	check with RtapPerfMon, in particular logManager


5)	Start on wt0tcs screens:
	vltguiTCS
	vltguiStatus


	- vltguiStatus
	Focus must be Cassegrain, i.e., only "CA" subsystems 
	are enabled (NA and NB are of grey colour)

	If not in Cassegrain: "Focus change" from menu bar, 
        and select Cassegrain.

	Due to simulation, Encl and Hb must be ignored (set the ignore 
	box to red).

	Bring all the TCS subsystems to ONLINE state

	For each system use the following sequence:

	 click "change state", select INIT, status remains in LOADED 
	 click "change state", select STANDBY, status should change 
         to STANDBY 
	 click "change state", select ONLINE, status should change 
         to ONLINE   
	 (* the transition STANDBY--> ONLINE may take several seconds!)

Remark: after each change state wait for the REPLY in the 
	Command Feedback Window

	Set systems on the following order 
	altAxis
	azAxis 
	adapt (CA)
	trkalt 
	trkaz 
	trkrot (CA)

	m1cell 
	m3 
	m2 
	m2tc Online (it should be in standby status after m2 online)

	ag (CA) 
	(agccd already online after a reboot)
	act (CA) 
	ladc (CA) 

If any of these subsystems is in a grey box, it means that the scan 
system is not working for the environment corresponding to that 
subsystem. In this case, open the scanei panel.
Select the corresponding environment (who should be in FAILED status).
After the select operation, a window with the detailed status of the 
environment should pop up.
In this window first disable the environment, then enable it.

At the end of these operations,  on the vltguiStatus panel 
the status should be :
	
		ONLINE	IDLE	IDLE

The first is the Main State of the Telescope, the second the Substate 
(it is related to the subsystem as they appear in the vltguiStatus 
panel) , the third is the tracking status.
If this one is in ERROR, from the vltguiTCS panel press the "PRESET" 
button. The tracking status should change (after a while) in TRACKING.
After that, the tests can be started.



6)	Start on wa0tcs screens:
	ccdStartAgc
	perform Shutdown and Startup
	check the status : it should be online

	rtdStartAgc
	From the TCS menu choose:
	Attach camera 

7)	rlogin to wt0tcs from wa0tcs
	start in a wt0tcs shell on wa0tcs: 
	vltguiGA
	chopwsgui

Remark: From the Telescope Control System panel, check that the 
	Instrument Selection is "defCA". If not, select defCA. 

8) 	check with scanei that the scan system is working for all the 
	LCUs.All the environments have to be in ENABLE/DISABLE status,
	no FAILED status should appear in the panel.
	If an environment is in FAILED status, select it;
	a window should pop-up. In this new window before disable the 
	scan link for that LCU, then enable it.
   




TestId  Action                                                               
==============================================================================

In all the tests: alpha=RA, delta=DEC, Hour Angle=HA, alt=Altitude, 
rem trk: remaining tracking time.
Remark: after each preset operation, before starting another test, 
wait for the subsystem "Tracking" reaching the tracking status 
on the vltguiTCS panel.

Remark: if HA="Sideral time"=0, preset the telescope before starting 
        the tests

1       vltguiTCS:
        enter: alpha=sidereal time, delta=-400000
        push preset button
 Expected Result:  HA=0, alt moves to 75deg

2       vltguiTCS:
	note the alt value
        in the "Telescope OFFSET" box, enter as ra/dec offsets 1800"
        push offset button north    
Expected Result: alt changes by 0.5deg
        push offset button south 
Expected Result: alt changes back by 0.5


3       vltguiTCS:
        enter alpha = sidereal time + 15min 
        delta = -243700
        push preset button                                                     
	when the telescope is tracking:
	- check that altitude = 86.6
	- HA value should become : -15min
        keep tracking for 10 min.
Expected Result: after 15 min. alt = 89.5

4       enter alpha = sidereal time - 5h30m, delta = -400000 
	push preset button
	=> HA = +5h30m
        keep tracking 
Expected Result:  alt = 21deg at start, at HA=5h36min alt=20deg
Remark: the same should happen with other values, for example:
	if HA=+5h20m and alt=31deg, when HA=+5h26m alt=30deg

5       enter alpha = sidereal time, delta = -150000 
	push preset button
	=> HA=0
        set additional velocities to 5 and 0
Expected Result: RA should increase by 5 arcsec/sec, 
		 no motion in alt
        set additional velocities to 0 and 5    
Expected Result: dec should decrease by 5 arcsec/sec, 
		 motion in alt ~dec motion
	set additional velocities to 0

6       enter alpha = sidereal time, delta = -450000 
        push preset button
	=> HA=0
Expected Result: rem trk time > 6hrs

7       wait 1hour  
Expected Result: rem trk ~ 5hrs
Remark: the success of this test depend on which subsystem has been 
	taking as reference for the remaining tracking time: rot and 
	az don't change the rem trk time, only alt does.
       

8       enter alpha = sidereal time + 1h, dec = -243700   
        push preset button
	=> HA = -1h
Expected Result:  rem trk time ~ 60min

9       enter alpha = sideral time + 0.25h, dec = -243700     
        push preset button
	=> HA = -0.25h
Expected Result: rem trk time ~ 15min


10      enter alpha = sideral time, delta = -450000
        push preset button
	=> HA=0

11      vltguiag:
        In the "Autoguider Control" box, configure :
	- loop freq = 0, Int time = 0.01
	- select Guide Mode: Autoguide
	- set disp on (Display enable ?)
	In the Guide Acquisition Panel:
	the CCD is not in the Control Model any longer, so we have 
        to work in simulation
	- Preliminary condition: we must have in the tcs' $INS_ROOT 
          the following file: 
		  $INS_ROOT/SYSTEM/DETDATA/atguiAgSim.fits
	  If the file is not there, one can copy it from 
		  te13:/home/vltmgr/www/sw-dev/control-model
	- "stop exposure"
	- send the following command as tcs:
 
    msgSend "" agwsControl SETUP ",,DET.READ.SIMIMG atguiAgSim.fits"

	  and wait for the OK answer
        - "start exposure" (start ccd integration)

	In the Telescope R.T.D. panel":
        - from the TCS menu, choose
  	  pick reference star ...
Remark: click the button "Auto Set Cut Levels" to get the image more 
	visible, then on the "pick reference star" window choose:
	- Sample size (in image pixels):20
	- pick object coords enabled
	- press the "pick object" button and click on object on the 
          Telescope R.T.D. panel

        On the vltguiag panel, push "Start guiding"   
Expected Result:  Autoguiding (Guiding in the Autoguider Status?)
	let it guide for at least 5 min.


12      Autoguiding
	vltguiag:
        push "stop guiding"
        in the "Autoguider Control" box, 
            select Guide Mode: field stabilisation
        and push "Start guiding"
Expected Result:  Autoguiding (Guiding in the Autoguider Status?)
	let it guide for at least 5 min.
                   							
13      Field stabilisation
	chopwsgui:
        set chop freq to 0.2
        throw: 20
        Sky orientation 67deg
        push "send setup"
        push "start chop"                                                    
Expected Result:   2 windows on rtd
        let it guide/chop as long as you can
        push "stop chop"<\PRE>