User Manual Gateway component for DeviceNetTM PR100071 • 1/7/2016
Table of Contents KUNBUS GmbH Table of Contents 1 General Information ........................................................................................................................ 3 1.1 Disclaimer.................................................................................................................................. 3 1.2 Notes Regarding this User Manual............................................................................................ 4 1.3 Validity ..........................
1.1 Disclaimer © 2015 KUNBUS GmbH, Denkendorf (Germany) The contents of this user manual have been prepared by KUNBUS GmbH with the utmost care. Due to technical development, KUNBUS GmbH reserves the right to change or replace the contents of this user manual without prior notice. You can always obtain the latest version of the user manual at our homepage: www.kunbus.de KUNBUS GmbH shall be liable exclusively to the extent specified in General Terms and Conditions (www.kunbus.de/agb.html).
This user manual provides important technical information that can enable you as a user to integrate the Gateways into your applications and systems efficiently, safely and conveniently. It is intended for trained, qualified personnel, whose sound knowledge in the field of electronic circuits and expertise in DeviceNet TM is assumed. As an integral part of the module, the information provided here should be kept and made available to the user. 1.
Safe Use 2 Safe Use 2.1 User The Gateway may only be assembled, installed and put into operation by trained, qualified personnel. Before assembly, it is absolutely essential that this documentation has been read carefully and understood. Expertise in the following fields is assumed: – electronic circuits, – basic knowledge of DeviceNet, – work in electrostatic protected areas, – locally applicable rules and regulations for occupational safety. 2.
Overview 3 Overview 3.1 Functionality The KUNBUS Gateway is a protocol converter. It allows communication between networks with different protocols. Illustration 1: Functionality A Gateway consists of 2 gateway components that master one specific protocol each. You can combine these gateway components as you wish. This design offers you a high degree of flexibility, since you can exchange the individual gateway components at any time.
Overview 3.
Overview Top 1 1 2 Illustration 3: Top 1 2 Gateway component for DeviceNetTM Interconnect ports for interconnecting the gateway components. Locking clamps for securely attaching the gateway component to the DIN rail.
Overview Bottom 1 2 Illustration 4: Bottom 1 2 Gateway component for DeviceNetTM Mains connection with 24 V power supply Locking clamps for securely attaching the gateway component to the DIN rail.
Overview 3.3 Status LEDs The signals of the status LEDs for DeviceNet have the following meaning: LED designation Power Signal Meaning off blinks, green on, green Gateway not running Initialization phase not yet completed All system components are functioning perfectly Correctable error (e.g. second gateway component missing) Serious error/defect in the gateway Device is offline flashes, red NS on, red off Possible causes: – The Dup_MAC_ID-Test has not yet been completed – No voltage present (s.
Signal Meaning off green, flashes The gateway component is not in operation. Check the power supply. Start-up green, on At least one system component has not yet finished its initialization. This also includes the automatic bitrate detection. Normal operation red, flashes red, on flashes green and red Gateway component for DeviceNetTM All system components are running perfectly. The partner gateway component is connected correctly.
Installation 4 Installation 4.1 Preparations for Trouble-free Operation In the following section we have compiled some general information for you that is important for trouble-free operation. If you are already acquainted with this topic, you can skip to the next section. There, you will learn about which conditions are necessary for installing the gateway. Cable routing Route your cables separately in cable groups. This will protect your gateway from any unintended electromagnetic interferences.
Shield your cables. This will reduce any unintended electromagnetic interferences. Potential equalization Potential differences occur when devices are connected to different earths. These potential differences cause malfunctions. To prevent malfunctions, you have to route an equipotential equalization conductor. When doing so, bear in mind the following points: – Select an equipotential equalization conductor with low impedance.
The Gateway was designed for use in a control cabinet. ü The protection class of the control cabinet must be equivalent to at least IP54. ü For installation in the control cabinet you need a DIN rail 35 x 7.5 mm (EN50022). ◦ Install the DIN rail horizontally in the control cabinet according to the manufacturers' specifications. When doing so, make sure that the Gateway is at a sufficient distance from other devices. NOTICE Your gateway could be damaged if temperatures are too high.
In order to attain a fully functional gateway, you have to interconnect both gateway components. ◦ Connect an interconnect port to each gateway component using the plug-in jumper provided. Illustration 6: Connecting gateway components ð You can now install the gateway in the control cabinet. NOTICE Only ever interconnect 2 gateway components. If you connect additional components, severe defects could result on all devices. Gateway component for DeviceNetTM 15 / 38 Installation 4.
◦ Hold the raster element of the gateway on the DIN rail. ◦ Press down the locking elements towards the gateway. ◦ Make sure that the gateway is firmly attached to the DIN rail. Gateway component for DeviceNetTM 16 / 38 Installation 4.
To connect the gateway component to the power supply, you need a spring-loaded terminal (e.g. Metz-Connect SP995xxVBNC). You have to connect each gateway component separately to a power supply. Never interconnect functional earth and GND, otherwise the galvanic isolation between gateway GND and fieldbus ground will be removed. Instead, connect the functional earth with low impedance to the potential equalization.
To connect the gateway component to DeviceNet, you need One 5pin Combicon connector. The pin assignment complies with the specifications of the ODVA. Cable color White Blue Not isolated Black Red Gateway component for DeviceNetTM Signal CAN_H CAN_L drain VV+ 18 / 38 Installation 4.
Configuration 5 Configuration 5.1 Supported Size of the Process Data The gateway component for DeviceNet supports process data of a length up to 64 bytes. An additional 448 bytes are available for the asynchronous data traffic. NOTICE Bear in mind that the maximum length of the process data is always determined by the fieldbus with the shorter data length. 5.2 Setting MAC-ID and bitrate The MAC-ID and bitrate are assigned in binary format.
To configure the gateway component, you have to make the appropriate settings in the DeviceNet objects with the configuration software of your Device master. Object structure DeviceNetTM uses the application layer CIPTM (Common Industrial Protocol) that was specified by the ODVA (Open DeviceNet Vendor Association - http://www.odva.org). Physically based DeviceNet on CAN (Controller Area Network). CIP is a connection oriented protocol.
This class contains information about the identification of the module. The gateway component supports the following functions in this class: – Get Attribute Single (0x0e): This function returns the content of certain attributes. – Reset Service (0x05) – Type 0: The module restarts the DeviceNet software. – Type 1: The module is reset to the original settings.
Name These is a connection to the master/scanner Reserved (set to 0) Configured (always set to 0) Reserved (set to 0) Extended Device Status 0000b Unknown 0010b Timeout 0011b No IO connection established 0100b Not implemented 0110b Connection in Run mode 0111b Connection in idle mode Others 8 9 10 11 12-15 Reserved A recoverable error has occurred An unrecoverable error has occurred A serious recoverable error has occurred A serious unrecoverable error has occurred Reserved (set to 0) Configu
Configuration Class Code 0x03 Hex In this class you will find information about the configuration and status of a DeviceNet port.
USINT MAC ID Switch Get Changed BOOL Value range 0–63, 255 MAC ID from the master Change is only possible by allocation from the master. This value indicates whether the node ID has been changed since the last restart. 0 = No change 7 Bit Rate Switch Get Changed BOOL 1 = Change since the last start This value indicates whether the bitrate has been changed since the last restart.
Configuration Class Code 0x04 Hex This object enables you to access the input and output data.
Configuration Class Code 0x05 Hex The gateway component supports the following functions in this class: Class Services – Get Attribute Single (0x0e) Instance Services – Get Attribute Single (0x0e) – Set Attribute Single (0x10) The gateway component supports the following data in this class: Instance 0 # 1 Gateway component for DeviceNetTM Name Version Access Get Type UINT Value 0x0002 26 / 38
# 1 Name State Access Get Type USINT Description State of the object 3: Established 2 Instance type Get USINT 3 TransportGet Class trigger DeviceNet Get produced connection id BYTE DeviceNet consumed connection id DeviceNet initial comm characteristics Produced connection size Consumed connection size Expected packet rate Watchdog timeout action Get UINT Get BYTE Get UINT Get UINT Get/Set UINT Get/Set USINT 4 5 6 7 8 9 12 13 14 15 16 UINT Produced connection path length Pr
# 1 Name State Access Get Type USINT Description State of the object 3: Established 2 Instance type Get USINT 3 TransportGet Class trigger DeviceNet Get produced connection id BYTE DeviceNet consumed connection id DeviceNet initial comm characteristics Produced connection size Consumed connection size Expected packet rate Watchdog timeout action Get UINT Get BYTE Get UINT Get UINT Get/Set UINT Get/Set USINT 4 5 6 7 8 9 12 13 14 15 16 Gateway component for DeviceNetTM UINT
# 1 Name State Access Get Type USINT Description State of the object 3: Established 2 Instance type Get USINT 3 TransportGet Class trigger DeviceNet Get produced connection id BYTE DeviceNet consumed connection id DeviceNet initial comm characteristics Produced connection size Consumed connection size Expected packet rate Watchdog timeout action Get UINT Get BYTE Get UINT Get UINT Get/Set UINT Get/Set USINT 4 5 6 7 8 9 12 13 14 15 16 UINT Produced connection path length Pr
# 1 Name State Access Get Type USINT Description State of the object 3: Established 2 Instance type Get USINT 3 TransportGet Class trigger DeviceNet Get produced connection id BYTE DeviceNet consumed connection id DeviceNet initial comm characteristics Produced connection size Consumed connection size Expected packet rate Watchdog timeout action Get UINT Get BYTE Get UINT Get UINT Get/Set UINT Get/Set USINT 4 5 6 7 8 9 12 13 14 15 16 Gateway component for DeviceNetTM UINT
Instance 10…12 Production inhibit time # 1 Name State UINT Access Get Type USINT Defines the minimum time between the data productions. This attribute is necessary for all I/O client connections. Excluded from this are connections with cyclical production triggers.
The gateway component supports the following functions in this class: Class Services – Get Attribute Single (0x0e): This function resets the content of certain attributes. Instance Services – Get Attribute Single (0x0e): This function resets the content of certain attributes.
Data with Ack Get Path List Size 7 Data with Ack Get Path List Gateway component for DeviceNetTM Configuration 6 BYTE Maximum number 1 of participants from the attribute "Data with Ack Path List" Array of List of all connec- N/A USINT tion participants.
In this object you have the option to access the I/O data. The process data input area is distributed here to the various attributes in instance 1 of this class. You can also access these values via class 3, instance 0x96-0x9a. The gateway component supports the following functions in this class: Class Services – Get Attribute Single (0x0e): This function resets the content of certain attributes. Instance Services – Get Attribute Single (0x0e): This function resets the content of certain attributes.
In this object you have the option to access the I/O data. The process data output area is distributed here to the various attributes in instance 1 of this class. You can also access these values via the assembly object. The gateway component supports the following functions in this class: Class Services – Get Attribute Single (0x0e): This function resets the content of certain attributes. Instance Services – Get Attribute Single (0x0e): This function resets the content of certain attributes.
Configuration Class 0xa2 - I/O Data Output Mapping With this object you can poll data via the partner gateway component.
Technical Data 6 Technical Data 6.1 Technical Data Dimensions Width Height Depth Weight 22.5 mm 96 mm 110.4 mm 90 g Electrical data Power supply 24 V DC Power consumption during operation 100 mA (cyclical data exchange) Status display LED Environmental conditions Ambient temperature Storage temperature Humidity Condensing Protection class 0 – 60 °C - 25 – 60 °C 93 % (at 40 °C) Not allowed Control cabinet IP54 Housing IP20 Terminal area IP20 Assembly data DIN rail Height Depth 35 x 7.
Technical Data Illustration 7: Side dimensions Illustration 8: Front dimensions Gateway component for DeviceNetTM 38 / 38
