start_cont
Purpose:
-
Start continuous channels.
Enter:
-
start_cont <arg1> <option>
Where:
-
arg1
Specify the input specification filename to process. If not specified, the default name of inpt_specs.NNN is processed. This argument may also be the letter ‘d’. If this special character is entered, then the default file will be processed in addition to setting an internal ‘debug’ flag. Doing this allows the debugging of the InputManger task.
option
Optional. Specify channels to ‘add’ to the existing continuous channels that are currently active. This option is not recommended. Any additional input specification should be handled via setting a logical PNP variable prior to the initial execution of start_cont.
Example:
-
start_cont
The above command, which is normally in the go script, results in start_cont processing the file ‘inpt_specs.NNN’, where NNN is the test cell number.start_cont inpt_specs.314
The above command results in start_cont processing the file ‘inpt_specs.314’.start_cont /specs/inpt_specs.extra add
The above command results in start_cont processing the file ‘inpt_specs.extra’. The ‘add’ argument is required when using the ‘add’ argument with ai_specs or di_specs.start_cont d
The above command, which is normally in the go script, results in start_cont processing the file ‘inpt_specs.NNN’, where NNN is the test cell number and sets the internal debug flag to ‘TRUE’. When the internal debug flag is set TRUE, exercise the following steps to allow debugging of the InputManager.1. start_cont will wait on the ASSET_INIT_SEM to be set by the “startup” process which is usually run later in the go.scp. So, it will probably not do anything unless the “asset_init” variable is TRUE
2. start_cont should be started under the debugger so that sending the request event to the input manager can be controlled.
3. start_cont will not attach to any input manager response timeout events in order to allow debugging of the input manager.
4. When the input manager is spawned with debug==TRUE, then it immediately exits so that it may be manually respawned.
5. Since the calling arguments to the input manager are determined by start_cont, when the input manager is manually spawned it must have the same calling arguments that were used by start_cont. Manually start the input manager via the debugger as follows:
InputManager MngrRspn-PID InptRqst-PID
where:
PID = the task pid of start_cont that spawned the original input manager.