We now have some gif files available which demostate the timings of the operations. These gifs print best on A3 paper. See for the axes mode timings and See for the non-axes mode timings. These files have a fair bit of technical information available but should still be useful to most people trying to get an understanding of the timing relationships.We have fixed the problem where by shuffle files are not downloaded if the file name does not change, even through the file itself has changed. The file is now always downloaded. All the prompts to the NS now remember and use as defaults the previous values entered. As a result, you can repeat a shuffle by just hitting return at all the prompts.
Three connections are required to the instrument sequencer. First, the instrument sequencer console RS232 port S1 must be connected to the AAOD2Q terminal server port 4, via the cable marked "ISconsole" at both ends. This connection is used to to command the instrument sequencer.
The second connection from from the Instrument Sequencer S3 serial line to the AAOD2A teminal server port 8, via the cable marked "ISapplic" at both ends. This is used by the instrument sequencer to send commands to the telescope via the VAX.
The third connection is for the CCD sync pulse. This involves a connection normally used in the TAURUS charge shuffline mode. There is a 55 way connection which normally plugs into the instrument sequencer I1 lemo connector and the S2 connector. In the cass cage, the Lemo connector on the other end of this plugs in to the "sync out" port of the CCD controller to be used. The other connections are not used (they are for TAURUS).
Note that Nod and Shuffling is fully compatible with TAURUS and a future version of TAURUS will use this scheme as well. The cabling is the same,but with the addition TAURUS connections plugged in in the cass cage.
define instseq_sif IRISTEST_SIF: TEL_CONTROLThe TEL_CONTROL program continues to run from this terminal. To exit it at the end of the night, type Control-Y and then logout.
(Note, we may remove the requirement for the define command at some stage soon).
Telescope commands sent by the instrument sequencer will be logged whilst the program runs.
For example, assuming you want to run CCD 1 from X-terminal AATXTK. Login into the VAX OBSERVER account and type the following commands.
version 6oct xon aatxtk rvnod ccd_1Observer will now start up (in a separate window), as will the instrument sequencer program. You will receive the ICL> prompt.
You can do all normal CCD operations, either from the Observer window or the ICL> prompt.
To run a nod and shuffle operation, you use the "NS" command at the ICL> prompt. This will prompt you for various values, being
Before running this command, you need to determine the following
The program writes to STDOUT the charge shuffling file. It writes to STDERR the timer resolution index value and the external device delay value. For example, assume an axes mode operation, exposure time of 10 seconds in both positions, offset time of 2 seconds and shift of 300 rows. The command is as follows
nodshuffle -axes -exptime 10 -offtime 2 -shift 300This produces
The timer resolution value is "3" The external device delay is "2000" PI PR 0,65535,10000,12100,1,300,0,0,1 PR 0,65535,10000,12100,65535,300,0,0,2 PE 0,65535,1,2100,0,65535,0,0,1 PE 0,65535,1,100,0,65535,0,0,0 PTIf I want to catch the charge shuffling file in a disk file, then I need to redirect STDOUT. E.g
define/user_mode sys$output myfile.csx nodshuffle -axes -exptime 10 -offtime 2 -shift 300Produces
The timer resolution value is "3" The external device delay is "2000"And the file myfile.csx which contains
PI PR 0,65535,10000,12100,1,300,0,0,1 PR 0,65535,10000,12100,65535,300,0,0,2 PE 0,65535,1,2100,0,65535,0,0,1 PE 0,65535,1,100,0,65535,0,0,0 PT
The Telescope control software also supports telescope FOCUS control, so it should be possible to write charge shuffling scripts to do FOCUS runs.
If the instrument sequencer task is not powered up or not communicating with the VAX, then you should expect the following just after entering the RVNOD command
Loading INSTSEQ_DIR:INSTSEQ into INSTSEQ INSTSEQ initialising !! No error to report (improper use of EMS) !! OBEYW error from task INSTSEQ - action INITIALISE TAURUS_CCD ADAMERR %SYSTEM, device timeout In Procedure: NS_LOAD At Statement: obeyw INSTSEQ INITIALISE TAURUS_CCD Called by: NS_MODULEINIT_G Called by: NS_MODULEINITIf you get this error, physically check the instrument sequencer micro. Ensure there are three lights down the left hand side (+5V, +12V and -12V). Ensure is is cabled correctly (see "Hardware Prepration" section). Hit the reset button.
Exit ICL and then start it again (you need only type ICL this time, although doing the full "RVNOD ccd_1" command does no harm)
You can log communications with the instrument sequencer micro by entering the following command at the ICL> prompt.
obeyw instseq log_level inst-sThis will log all information to the ICL window as well as the Observer log file. For example, consider issuing the command "SS 0".
ICL> obeyw instseq MICRO "SS 0" Output to INSTSEQ -> aa. Input from INSTSEQ -> aa. Input from INSTSEQ -> ? - Unknown Command. Output to INSTSEQ -> SS 0. Input from INSTSEQ -> SS 0.You can see SS command output and the echo of it returned. But what is the "aa" command about. This is just the way the instrument sequencer task checks if the micro is listening. If a run was aborted incorrectly, the micro may not be listening, in which case, the task needs to send a Ctrl-E character to grab it's attention. But, if it is listening, the Ctrl-E character causes a crash, so the software has to check first. The "? - Unknown Command." string is the expected response from "aa".
So just what is sent during a run. This varies a touch based on the type of run. There are two stages, one prefixed by "Down-loading commands to instrument sequencer" and the other prefix by "Down-loading phase table to instrument sequencer"
The commands send during the first stage are something like these
SS 0 IM 2 DC 256 AC 1 "THAW" AC 2 "FREEZE" AC 3 "OFFSET 10 20" AC 4 "OFFSET 0 0"The SS command selects serial port for the Telescope. The IM command specifies that we are running the telescope (as against running TAURUS). When the IM command is send, the system tries to talk to the Telescope by issuing a "WHERE" command to the telescope interface. You should see this echoed on the Night account terminal running TEL_CONTROL.
The AC commands specify the Telescope commands for each phase. The last number in each phase table line indicates which of these commands is selected. The command is sent to the telescope at the begining of the phase and you should see it echoed on the Night account terminal
The command sent during the second stage are something like these
PI PR 0,65535,5000,8100,1,341,0,0,1 PR 0,65535,1,3100,0,65535,0,0,2 PR 0,65535,5000,8100,65535,341,0,0,3 PR 0,65535,1,3100,0,65535,0,0,4 PE 0,65535,1,3100,0,65535,0,0,1 PE 0,65535,1,100,0,65535,0,0,0 PT cs 3Where the phase table was downloaded verbatim, and then followed by the "cs" command which causes the run to start and specifies the number of cycles.