Implemented Protocols In Unigate Cx C4Map; Implemented Protocols At Canopen Interface; Functionality Of The Individual Transport Protocols; Canopen Mapping - DEUTSCHMANN AUTOMATION UNIGATE CX-CANopen - DeviceNet Manual

Implemented protocols in UNIGATE® CX C4Map
7 Implemented protocols in UNIGATE
The protocols "CANopen (mapping)" and "Delta exchange"are required for communication.
7.1

Implemented protocols at CANopen interface

CANopen Mapping

Note: Data exchange is only possible when the DeviceNet is in "Data
Exchange".
7.1.1

Functionality of the individual transport protocols

7.1.2 CANopen Mapping
Data structure
The mapping in the gateway can be configured using the supplied WINGATE
This gateway module from the UNIGATE series from Deutschmann Automation allows a cou-
pling between fieldbus and CANopen
The gateway behaves on the CANopen
DeviceNet side as a standard-compliant slave.
Data exchange
The data exchange between fieldbus and CANopen
is configured with "WINGATE
Mapping is the mapping of data from a fieldbus to any other fieldbus. All data provided by the
corresponding buses can serve as data here.
The mapping works in both directions, i.e. both from master to slave and vice versa.
Example:
For example, it can be specified that the 2nd byte of the COB-ID201 (CANopen
ferred as the 7th byte in the fieldbus data.
256 mappings are currently possible (128 Tx and 128 Rx mappings). The data is transferred as
PDOs. A maximum of 16 Tx and 16 RX PDOs can be set. Each PDO can have up to 8 bytes (i.e.
8 mappings). 16 PDO * 8 bytes = 128 mappings. SDO access is also supported (see chapter
7.1.2.10).
14
®
.
®
side as a standard-compliant master and on the
®
".
Fieldbus-Gateway UNIGATE
Deutschmann Automation GmbH & Co. KG
CX C4Map
®
®
is carried out by the mapping that
®
CX C4Map - DeviceNet V. 1.0
®
software.
®
node) is trans-
25.9.20