6 devicenet cip object implementation – Baumer GK473 User Manual
Page 10
Manual_GK473_DeviceNet_EN.doc
10/31
Baumer IVO GmbH & Co. KG
04.05.11
Villingen-Schwenningen,
Germany
5.2 Data exchange DeviceNet <-> RS485 sub- bus
The Gateway is enabling communication between the SPA’s RS485 protocol and the DeviceNet fieldbus.
The PLC (DeviceNet Master) output data to the gateway comprise all commands relevant for the addressed
spindle position display. The command is completed by start and stop token as well as by CRC byte (cyclic
redundancy check) and forwarded by the gateway via RS485 interface.
In direction vice-versa, start and stop token as well as CRC byte (cyclic redundancy check) will be taken out
of the RS485 message, but latter is passed with unchanged content to the data block of a DeviceNet
message so that it is available at the PLC as consistent input data.
Furthermore, the gateway provides additional functions to relieve the master PLC and to simplify PLC
programming.
6 DeviceNet CIP Object Implementation
DeviceNet is based on Common Industrial Protocol (CIP)
The following CIP objects are implemented in GK473:
Mandatory objects:
Class Code
Object Name
Number of Instances
0x01 Identity
1
0x03 DeviceNet
1
0x04 Assembly
1
0x05 Connection
3
0x2B Acknowledge
Handler
1
Vendor Specific Objects
Class Code
Object Name
Number of Instances
0x64 GK473
1