Instructions
Table Of Contents
- 1 Preface
- 2 Safety
- 3 Preparation
- 4 About Anybus Communicator
- 5 Installation
- 6 Configuration Quick Guide
- 7 Communicator Configuration
- 7.1 Connecting the Communicator
- 7.2 Access the Built-In Web Interface From HMS IPconfig
- 7.3 Access the Built-In Web Interface From a Web Browser
- 7.4 Communicator Built-In Web Interface Overview
- 7.5 General Subnetwork Settings
- 7.6 About Transaction Templates
- 7.7 Build Transaction Templates
- 7.8 Nodes and Transactions
- 7.9 High Level Network Settings
- 7.10 Naming the Host
- 7.11 Station Name
- 7.12 I/O Data Map
- 7.13 Apply Configuration
- 7.14 Use an Existing Configuration
- 8 PLC Configuration
- 9 Verify Operation
- 10 Use Cases
- 11 Maintenance
- 12 Troubleshooting
- 13 Technical Data
- A Reference Guides
Communicator Configuration 44 (124)
7.6.3 Frame Field Types
Each transaction consists of frame fields which makes up the serial telegram frame.
Each frame field specifies how the Communicator shall interpret or generate a particular part of
the telegram.
The following frame fields are available:
Node address
Frame field representing the Node address of the Node.
A constant byte that holds a copy of the nodes address when the transaction is used by a node.
Constant
Constant frame fields are handled differently depending on the direction of the transaction:
Produce/Request Transactions
The Communicator sends the value as it is without processing it.
Consume/Response Transactions The Communicator checks if the received byte/word/dword matches the specified
value. If the message does not fit, it is discarded.
Limit
Limit is not available for the Transaction Type Produce.
Consume/Response Transactions The Communicator checks if the received byte/word/dword fits inside the specified
boundaries. If the message does not fit, it is discarded.
Data
Data frame fields are used to represent raw data as follows:
Produce/Request Transactions
The specified data block is forwarded from the higher level network to the sub-
network.
Consume/Response Transactions
The specified data block is forwarded from the sub-network to the high level
network.
Variable data
Produce/Request Transactions:
The specified data block will be forwarded from the higher level network to the sub-network.
The control system must supply an End or Length character in order for the Communicator to know the size of the data
block.
The End- or Length-character itself may either be forwarded to the sub-network or discarded.
Consume/Response Transactions:
The specified data block is forwarded from the sub-network to the higher level network.
The End- or Length-character will be generated by the Communicator automatically (if applicable).
The End- or Length-character itself may either be forwarded to the higher level network or discarded.
Anybus
®
Communicator
™
User Manual
SCM-1202-176 1.0 en-US










