ASC

#   Sending commands to an intelligent device through async comm port
# start_code
#  NONE                    no start signal necessary
#  AT_START                send start signal at start of mode
#  AFTER_STABILITY         send start signal after stabilization
#
# options for success_path and failure_path
# NONE
# MODE_TERMINATE
# RETURN  (to calling procedure)
# a mode number in this test procedure
# the pathname of a test procedure  (example:  /specs/gp/gp_mytest )
# a pathnname and mode number (example: /specs/gp/gp_mytest;23 )
# stop_type 
#
# only 1 command can be used per test mode
#
# Note that the 'stop_path' is only meaningful for the case where
# there is a response from the device

@ASC
   #strt_code success_path  fail_path name_stem command    out_value  return
   AT_START    NONE       NONE      dynloc    "set "     my_var     my_result


The 'out_value' field is evaluated and appended to the command.  The 
'out_value' field may be a constant, variable, or computed expression.

If there is an expected response to this command from the device, the
value in the response will be placed into the 'return' variable.  The
'return' variable may be a real, logical, integer, or string variable.
The device configuration file, 'name_stem.cfg', must contain an appropriate
RESPONSE command structure for the return message.

In the above example, if my_var had a value of 1200, then the command
that would be sent to the device would be "set 1200".