Communicator CAN - CANopen gateway
Anybus CAN to CANopen data converter
The gateway works as a CANopen slave for the primary network and as a standard CAN node for the second network
The Communicator performs an intelligent data conversion and presents CAN data to a PLC/Controller in the CANopen network as easy to process I/O data. With convenient configuration software basically every manufacturer-specific CAN data protocol can be exchanged to CANopen, or vice versa.
Features and benefits
- Saves machine builders and device manufacturers of integrating a CANopen interface
- Requires no hardware or software changes to be made to CAN-devices
- Compatible with all PLC's and controllers with CANopen support
- Performs complete CAN protocol conversion, no PLC function blocks required
- Flexible CAN frame building method for both Response/Request or Produce/Consume protocols
- Intelligent I/O data mapping within the Communicator permits even devices with slow CAN communication can be integrated without any restrictions to CANopen
Conversion of I/O-data
The Anybus Communicator maps data byte from CAN messages into I/O data in the CANopen network, and vice versa. This mapping is highly flexible and can contain an arbitrary set of CAN Id’s and data. CAN communication is supported both by both producer /consumer or request/response protocol schemes, who are configured with a flexible CAN frame building method.
All data between CANopen and the CAN network is transferred through an internal memory buffer inside the Communicator. This method of data exchange also permits CAN devices with slow communication to be integrated into high-speed CANopen networks without any restrictions. The Communicator appears as a standard I/O module on the CANopen side.
Easy configuration - No programming required!
The mapping of data between CAN and CANopen is quickly set up in the Anybus Configuration Manager software, included with the Communicator CAN. No programming skills are needed to set up the Communicator.
- 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
- 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
- Handy Save/Load function allows for a completed configuration to be re-used for many other installations
- Password protection prevents unauthorized upload and download of configurations
CANopen interface features
- Complete CANopen slave functionality according to CANopen Version 4.02
- Max 512 bytes of Input and 512 bytes of Output data (PDO + SDO)
- Customizable PDO mapping
- Up to 80 RPDO’s and 80 TPDO’s
- Transmission types: PDO Sync, Change-of-state, Event based and RTR
- Network store/restore functionality
- Heartbeat & Node Guarding support
- Supports CANopen baudrates 10 kbit/s – 1 Mbit/s
- CANopen configuration via .EDS file or DIP switches
|Dimensions||120 x 75 x 27mm|
|Operating temperature||-25 to +55 °C|
|Storage temperature||-40 to +85 °C|
|Power supply||24 VDC|
|Current consumption||Typical 150mA|
|Baudrate||20 kbit/s - 1 Mbit/s|
|Protocol support||CAN 2.0A and 2.0B (11 and 29 bit identifiers)|
|Connector||D-sub 9 Male|
|Connector||1x Sub-D99 male (CiA 303-1)|
|Galvanic isolation||On both CAN and CANopen side|
|Mounting||DIN-rail (EN 50022 standard)|
|Certifications||CE, CULUS, ATEX/Haz.Loc, RoHS|
|Contents of delivery|
|- Anybus Communicator CAN-CANopen|
|- Configuration cable (USB)|
|- D-sub9 connector with screw|
|- Anybus Configuration Manager (Windows™)|
|- Quick Reference Manual|
|- User Manual|