About This Document
P-3
Conventions & Terminology
The following conventions are used throughout this document:
• Numbered lists provide sequential steps
• Bulleted lists provide information, not procedural steps
• The term ‘user’ refers to the person or persons responsible for installing the Anybus Communi-
cator in a network.
• The term ‘gateway’ refers to the Anybus Communicator.
• Hexadecimal values are written in the format 0xNNNN, where NNNN is the hexadecimal value.
• Decimal values are represented as NNNN where NNNN is the decimal value
• As in all communication systems, the terms “input” and “output” can be ambiguous, because
their meaning depend on which end of the link is being referenced. The convention in this doc-
ument is that “input” and “output” are always being referenced to the master/scanner end of the
link.
Glossary
Term
Meaning
ABC
Anybus
®
Communicator™
Broadcaster
A protocol-specific node in the configuration that handles transactions destined to all nodes.
RTU
Modbus RTU
Command
A pre-defined transaction.
Configuration
List of configured nodes with transactions on the sub-network.
Fieldbus
The higher level network to which the communicator is connected.
Fieldbus Control System Fieldbus master
Frame Object
Low level entities which are used to describe the different parts of a Transaction.
Monitor
A tool for debugging the gateway and the network connections.
Node
A device in the configuration which defines the communication with a node on the sub-network
Sub-network
The network that is logically located on a subsidiary level with respect to the fieldbus, and to
which the Anybus Communicator acts as a gateway.
Transaction
A generic building block that is used in the sub-network configuration and defines the data that
is sent and received on the sub-network.
User
Person or persons responsible for installing the Anybus Communicator
Higher Level Network
In this case, Modbus RTU
Network
Fieldbus
