Manual
Table Of Contents
- Anybus® Communicator™ - Modbus TCP Server to EtherCAT Slave
- Table of Contents
- 1. Preface
- 2. Safety
- 3. Preparation
- 4. About Anybus Communicator
- 5. Installation
- 6. Communicator Configuration
- 6.1. Connect the Communicator
- 6.2. Access the Built-In Web Interface From HMS IPconfig
- 6.3. Access the Built-In Web Interface From a Web Browser
- 6.4. Communicator Built-In Web Interface Overview
- 6.5. Modbus TCP Settings
- 6.6. EtherCAT Settings
- 6.7. I/O Configuration
- 6.8. Apply Configuration
- 6.9. Configuration Notes
- 7. PLC Configuration
- 8. Verify Operation
- 9. Maintenance
- 10. Troubleshooting
- 11. Technical Data
4.2. How the Data Exchange Works
Figure 2. The Communicator internal memory areas
The data exchanged between the Communicator and the Modbus TCP and the EtherCAT resides in the
Communicator internal memory buer.
The Communicator internal memory buer is divided into two areas: Input data and Output data.
Input Data
This Input data area is read by the EtherCAT.
The Communicator can handle up to 1486 bytes input data.
Output Data
The Output data area is read/wrien by the Modbus TCP.
The Communicator can handle up to 1500 bytes output data.
4.3. Data Integrity
A snapshot of the process data buer between the Modbus TCP/EtherCAT Client and the server interface is used
during the operaon of execung all the transacons within one cycle.
When the cycle is completed, the process data available on the server interface is updated and a new snapshot is
created for the next cycle.
How the Data Exchange Works Anybus
®
Communicator
™
- Modbus TCP Server to EtherCAT Slave
SCM-1202-192 Version 1.0 Page 7 of 56










