Rockwell Automation 8520-9API 9/Series OCI API Developer's Guide - Manual (Page 113)

5–2 OCI Data Server CNC Commands
Publication 8520-6.6 - August 1999
For applications where it is critical that the command is executed
successfully before continuing on with processing, make certain your
code monitors the return code for confirmation before continuing.
Return code values are given in a table with each command.
The Basic Display Set checks some return codes and translates them
into error messages. See chapter 3 for details on the Basic Display
Set.
For dual process systems, follow the command name with a .1 or .2
to indicate the process number. No process number by default makes
a request for process 1. Single process systems can also use .1 as a
valid command request. Use the table in appendix B to determine if
a command is available as dual process. For example:
[STOP_QUICK_CHECK.1]
would attempt to stop quick check on process 1.
Important: Dual process does not apply to Release 1 of the 9/PC
CNC.
Most development tools accept DDE commands in a standard
format. You must specify to the server:
•
Service or Application name – ABOCISERVER
•
Topic Name – CNC1 (or your alias for the CNC)
•
Link Type – (commands use manual link type)
After the above connection has been made the command can be
issued. The standard format for the command syntax of a DDE
request is:
[command ( argument, argument, ...)]
Where:
command – is the command string which identifies the operation.
For example “INSERT_AXISCAL_POINT” is an example
command string.
argument – is the data to pass to the CNC with the command. For
example axis_num is an argument which is used to pass the number
of the axis back to the control with the command string. If multiple
arguments are used with the command, they are separated by a
comma.
Selecting the Process
OCI Command Syntax