Instructions
Table Of Contents
- Anybus® Communicator™ - PROFIBUS to Modbus RTU/Serial
- Table of Contents
- 1. Preface
- 2. Safety
- 3. Preparation
- 4. About Anybus Communicator
- 5. Installation
- 6. Configuration Quick Guide
- 7. Communicator Configuration
- 7.1. Connect 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 Template
- 7.8. Nodes and Transactions
- 7.9. High Level Network Settings
- 7.10. I/O Data Map
- 7.11. Apply Configuration
- 7.12. To Use an Existing Configuration
- 7.13. To Use an Communicator Classic Configuration
- 8. PLC Configuration
- 9. Verify Operation
- 10. Use Cases
- 11. Maintenance
- 12. Troubleshooting
- 13. Technical Data
- 14. Reference Guides
• Error check type: Specify how the checksum is converted. Select None (Default), One’s complement or Select
None, Two’s complement.
• Representaon: Specify how the checksum is represented. Select Binary (Default) or ASCII.
About Fixed eld*
• Yes, set here: The Value set here is xed and cannot be changed when the transacon is used on a node.
The value must be updated in the transacon template.
• No, set when used: The Default value set here can be edited when the transacon is used on a node.
The allowed range is the min/max values.
Total size including delimiters:
• High Level Network: 1 byte(s)
• Subnetwork: 1 byte(s).
4. Repeat step 1 to 3 unl you have congured all the desired frame objects.
Apply Conguraon
To apply the sengs, click Apply in the web-interface header, and follow the instrucons.
7.7.4. Data Delimiter and Subnet Delimiter Opons
In a variable data object, the length of the data eld may vary depending on the type of data being read in a
specic case.
In order to present the variable data correctly on the corresponding network, the length of the data eld must be
idened.
In a Variable data object, there are three ways to idenfy the data length; by length character, end character or
length of message.
Data delimiter - Data is forwarded From the Communicator to the PLC
The Communicator can be congured to forward data as process data.
Dierent Data delimiter opons can be used for data sent from the subnetwork to the Communicator and for
data forwarded from the Communicator to the high level network, to t the requirements in the PLC.
In most cases, when a stream of data is sent from the Communicator to the PLC the Byte counter (length
character) or End paern (end character) format is used.
Subnet delimiter - Incoming Data From a Serial Node to the Communicator
The Communicator can be congured to expect data from one of the three Subnet delimiter opons; Byte
counter, End paern or None.
If the incoming data match the Subnet delimiter format the data is captured and the data secon is forwarded to
the high level network.
If the incoming data do not match the Subnet delimiter format, the data is ignored and will be matched with the
next consume transacon.
Anybus
®
Communicator
™
- PROFIBUS to Modbus RTU/Serial Build Transacon Template
Page 62 of 134 SCM-1202-177 1.2