RMODE:
set readout mode
This page is part of the ING document
INS-DAS-24:
client-server interface for control of cameras
Purpose: to select a mode of readout for subsequent observations.
Actors: udas_rmode client; udas_run client; udas_camera
server.
Outline: udas_rmode invokes the RMODE action; the server
stores the mode choices such that the udas_run can retrive them
later.
Normal course of events:
-
Server is between observations.
-
udas_rmode invokes the RMODE action on server with these arguments:L
-
Argument1 is the name of the mode, set to "mndr".
-
Argument2 is a repeat count, set to 4..
-
Server stores these data.
-
Server returns good status to udas_rmode.
-
udas_run starts a run sequence.
-
udas_run retrieves the mode name and repeat count from the parameters
RMODE_NAME and RMODE_COUNT.
-
udas_run implements the mode as a set of 4 readouts after a clear,
then a single integration, then another set of 4 readouts.
Variations:
-
The repeat count may be any number between 1 and 20 inclusive.
-
The mode name is "simple" and the repeat count is one. Udas_run does
a single readout after a single integration: this is the normal setting
for CCDs.
-
The mode name is "ramp" sets the camera for read-up-the-ramp mode.
-
The mode name is "simple" and the repeat count is greater than 1.
Udas_run
does
an integrate-readout pair for each repeat. This is profoundly wierd, but
still valid.
-
The mode name is something other than "simple", "mndr", or "ramp", or the
repeat count isn't in the range 1..20. Server stops at step 2 and does
not store the mode data. Server sends and error message to udas_rmode
and returns status UDAS__BADRMODE.
-
Udas_rmode has not been invoked before udas_run is invoked.
Udas_run
finds the parameter defaulted like this:
-
RMODE_NAME = "simple".
-
RMODE_COUNT = 1.