Filter
Top Products
Command Language 6-3
Data Field
The Data Field defines the data transfer requirements of the
application layer message. This field describes the data using
the ‘data type’ defined in Section 2.l. Commas separate
individual elements of data.
As previously discussed in Section 3, there are two types of
application layer packets–. Command and Response.
Command packets ALWAYS contain a transaction number
(USINT). Response packets ALWAYS contain a transaction
number (USINT) and a status (USINT). The transaction
specification is only concerned with the data field portion of these
messages. The transaction number and status are assumed to
be present, and are not shown in the specification.
In transactions that fit the basic Set, Get, and Set/Get definitions,
only a single data field is described in the specification. In these
cases it is assumed that a ‘Set’ transaction has only Command
packet data. A ‘Get’ has only Response packet data. And a
‘Set/Get’ has the same data in the Command and Response
packet, unless it is being used to ‘Get’ only, in which case there
is no Command data.
Transactions are not required to conform to these basic rules.
When such exceptions exist, both their Command and Response
data fields will be described in detail. The command data field is
preceded by a C:, the response data field is preceded by a R: for
identification purposes only.
In some cases variable names are given in the data field
specification. These names are used to describe multiple
elements of a common data type. These names are not required
for use, but may be included in present and future software
drivers and libraries provided by Baldor. (When used with tools
provided by Baldor, variable names are case sensitive.)