Offload your PLC from additional calculations

I/O data exchange between the serial/CAN device to the PLC is mapped within the internal memory buffer inside Anybus Communicator. This offloads your PLC from from additional complex calculations. 

  • The PLC exchanges data via the fieldbus/Ethernet network
  • The converted serial data from the Communicator can be accessed by the PLC
  • The Communicator collects data from the devices on the serial sub-network
  • The data is stored in its memory buffer before an intelligent conversion takes place
  • The Communicator reads and writes the serial telegram to the serial device via Modbus-RTU, ASCII/DF1/CAN or other custom based protocols
  • All data between the fieldbus and the serial network is stored in an internal memory buffer inside the Anybus Communicator.

 

The Results

The internal storage of I/O data inside the Communicator de-couples the two networks.

This permits the that even automation devices with slow serial communication can be integrated into high-speed fieldbus/Ethernet networks without any restrictions to the upper network.

I/O mapping within the Communicator

Serial/CAN protocol mapping examples

 

Request/Response protocol  

In this example one can either use pre-defined commands (Modbus) or create customized frames

  • The Communicator is a Master on the sub-network and a Slave on the PLC network
  • It sends a request and waits for the serial device to respond 



serial-master-mode

Produce/consume protocol  

In this example frames have to be built according to the protocol defined by the serial application

  • No Master/Slave relationship between the Communicator and connected serial device
  • Any device on the serial network (including the Communicator) can spontaneously produce or consume a message
  • The node does not have to reply to a message, nor does it have to wait for a query to send one

 

serial-generic-mode

CAN 2.0A / 2.0B -  Request/response or produce/consume protocols 

The example below shows Request/Response scenario but can also be Produce/Consume as shown above

  • With Request/Response the Communicator is a Master on the CAN network and a Slave on the PLC network
  • It sends a request and waits for the CAN device to respond 
  • With Produce/Consume no Master/Slave relationship exists between the Communicator and connected CAN device
  • Any device on the CAN network (including the Communicator) can spontaneously produce or consume a message
  • Support for 11 or 29 bit CAN Identifier


can-master-mode

Anybus communicator configs

Verified devices

The Communicator connects thousands of industrial devices worldwide.
How data is mapped

How data is mapped

Offload your PLC from additional calculations
Case Studies

Anybus Communicator Case Studies

Anybus Communicator Case studies

Contact us!

Need more information about the product or a quote? We are at your disposal...