Connecting devices with a CAN interface
Connect your CAN devices to any major fieldbus or industrial Ethernet networks with the Anybus Communicator. The Communicator performs an intelligent conversion between the CAN protocol of the automation device and the chosen industrial network.
For industral devices with a CAN 2.0A or 2.0B port, HMS makes it possible to configure almost any Produce/Consume, Request/Response protocols with its flexible CAN frame building method. No proprietary configuration software is needed. All necessary configuration is performed using the Anybus Configuration Manager that accompanies the gateway.
- How it works
Anybus Communicator CAN is designed to exchange data between a subnetwork, running CAN, and a higher level network ( Fieldbus/Ethernet).
Through the configuration of the CAN frames, the Communicator will adapt to a predefined CAN network. It will be possible to send and receive data from the subnetwork, but also to act as a relay for data on the CAN subnetwork.
Dual port Ethernet switch technology
Any device with a CAN 2.0 A- or B-based protocol can be connected. Typical applications are variable frequency drives, sensors, actuators, human machine interfaces, barcode readers, RFID readers,weighscales and many types of industrial machinery.
The Communicators flexibility and high industrial standards and certifications, enables it to be used with many different types of industrial applications. Factory automation, Building and HVAC, Waste water management, Marine, Mining, Medical and with Infrastructure projects are some of the industries where the Communicator is connecting devices today.
Flexible CAN configuration
The Anybus Configuration Manager CAN provides you with a flexible and easy-to-use CAN frame building environment with several readymade CAN functions. It allows for a mixture of both Query/Response and/or Produce/Consume protocols to be configured.
Query/Response (master mode)
Any device on the CAN network , including the Communicator, can spontaneously produce or consume a message; It does not have to reply to a message, nor does it have to wait for a query to send one. This is very common transmission method use with with bar code scanners, for example.
If you require assistance implementing your CAN protocol then contact HMS, or your local Anybus Distributor or approved HMS System Partner.
The uplink fieldbus or Ethernet slave interface to the PLC is configured with a standard device description file (GSD/EDS) in the PLC engineering tool. (Step7, RSNetworx etc)
|KEY FEATURES - ANYBUS CONFIGURATION MANAGER - COMMUNICATOR CAN|
|Graphical CAN frame building support using several ready-made CAN functions.|
|Can configure any CAN 2.0A or 2.0B based protocol (11 and 29 bit identifiers).|
|Configures upto 128 transactions containing a total of 256 CAN frames.|
|Handy Save/Load function means a completed configuration can be re-used for many other installations.|
|Password protection prevents unauthorized upload and download of configurations.|
|Monitor/Modify function of process I/O data informing of CAN transaction status.|
|Diagnostic transaction Live List in the network I/O informing of CAN transaction status.|
|Configuration via Ethernet or USB.|
Intelligent Data Mapping
All data between the fieldbus and the CAN network is stored in an internal memory buffer inside the Communicator.
The data exchange between the PLC on the fieldbus/Ethernet and the automation device is then made using the input and output areas of the internal memory within the Communicator.
The internal storage of I/O data inside the Communicator de-couples the two networks.
This allows automation devices, even those with slow CAN communication, to be integrated into high-speed fieldbus/Ethernet networks without any restrictions to the upper network.