Doc.Id. SCM-1200-093
Anybus Communicator for Modbus Plus
Doc.Rev. 3.01
Chapter 8
8. Commands
This information is only valid for master mode and generic mode. For DF1 master mode, please refer
to “Services” on page 54.
8.1 General
As mentioned previously, commands are actually predefined transactions that can be stored and reused.
Just like regular transactions, commands consist of frame objects and are representations of the actual
serial telegrams exchanged on the serial subnetwork.
Adding a command to a node actually results in (a) transaction(s) being added according to the directions
specified in the command. The frame objects in such a transaction may retrieve their values not only
from parameters in the parameter section, but also from other sources such as the ‘SlaveAddress’-pa-
rameter (see “Node Parameters” on page 31). In such case, the parameters in the parameter section will
be greyed out and cannot be edited directly.
In Master Mode, Anybus Configuration Manager comes preloaded with commands for most common
Modbus RTU functions. Additional commands can easily be added using the Command Editor (see
“The Command Editor” on page 47). For DF1 Master Mode, see “Services” on page 54. In Generic
Data Mode, no predefined commands exist, but custom ones may be implemented as desired.
8.2 Adding & Managing Commands
To add a command to a node, right-click on the node in the Navigation Section and select ‘Add Com-
mand’.
A list of commands will appear:
Select the desired command in the list, and select ‘Add Command’
in the ‘Command’-menu. The specified command will be added
to the node.
Just like other transactions, the frame objects of added command
may be edited in the Navigation/Parameter Section or using the
Transaction Editor. Note however that certain frame objects may
be locked for editing.
Summary of Contents for Communicator Modbus plus
Page 83: ......
