user_ctrl_specs
Purpose:
-
Process and configure user control loop specifications from a file, handling keywords to set up control tasks.
Enter:
-
user_ctrl_specs [specification_file] [loop_name]
Where:
-
specification_file
Optional unless a loop_name is specified. Specify the specification filename to configure the user control task. The default is user_ctrl_specs.NNN.
loop_name
Optional. Specify a single loop to configure. The first 28 characters must be unique as it affects the registered name.
Example:
-
user_ctrl_specs
The above command configures the user control task with the default user_ctrl_specs file. Assuming that the command is executed at test cell NNN, the default file is: /specs/user_ctrl_specs.NNN is used.A separate instance of the user_ctrl_task will be launched for each user loop. The loops are configured one at a time. If the file is being re-processed, all instances of user_ctrl_task will continue to run using the arguments they were originally launched with. If an argument for the user_ctrl_task needs to be changed, such as “critical”, then that instance must be slayed before reprocessing the specification file.
user_ctrl_specs /specs/my_user_ctrl_specs
The above command results in the file /specs/my_user_ctrl_specs being processed.user_ctrl_specs /specs/my_user_ctrl_specs desired_loop_name
The above command is a special case. If the second argument to user_ctrl_specs is specified, then only the loop specified will be configured.
Notes:
-
Use the errs command to check for errors after using this command.