Linking Device
Linking Device
EtherNet/IP™ to PROFIBUS® DP
USER MANUAL
SCM-1202-026 1.0
ENGLISH
Important User Information
Liability
Every care has been taken in the preparation of this document. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commitment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements including any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot assume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product described in this document. These intellectual property rights may include patents and pending patent applications in
the USA and other countries.
Linking Device User Manual
SCM-1202-026 1.0
Table of Contents
1
2
3
4
5
About This Document .................................................................................................... 3
1.1
About This Document.....................................................................................................3
1.2
Related Documents .......................................................................................................3
1.3
Document history...........................................................................................................3
1.4
Trademark Information ...................................................................................................3
1.5
Conventions ..................................................................................................................4
EtherNet/IP to PROFIBUS DP Linking Device.......................................................... 5
2.1
Introduction ...................................................................................................................5
2.2
Features .......................................................................................................................5
2.3
Unique Integration into Studio 5000.................................................................................6
2.4
Data Mapping ................................................................................................................6
2.5
Configuring the EtherNet/IP Network ...............................................................................7
2.6
Control Word .................................................................................................................7
2.7
Status Word ..................................................................................................................7
2.8
PROFIBUS Slave Live List .............................................................................................7
About the Linking Device.............................................................................................. 8
3.1
External View ................................................................................................................8
3.2
Mounting the Linking Device ...........................................................................................9
3.3
Status LEDs ................................................................................................................ 11
3.4
EtherNet/IP Connectors................................................................................................ 11
3.5
PROFIBUS Connector .................................................................................................12
3.6
USB Connector............................................................................................................12
3.7
Power Connector .........................................................................................................12
The Linking Device Web Interface ............................................................................ 13
4.1
Overview.....................................................................................................................13
4.2
Firmware Update .........................................................................................................13
4.3
Diagnostics .................................................................................................................13
Studio 5000 Implementation Example ..................................................................... 14
5.1
6
Page
Step by Step Guide ......................................................................................................14
Tag Editor ........................................................................................................................ 21
6.1
Tag Editor Overview .....................................................................................................21
6.2
Tag Editor Basics .........................................................................................................22
6.3
Tag Rule Definitions .....................................................................................................23
Linking Device User Manual
SCM-1202-026 1.0
Table of Contents
7
CIP Objects ..................................................................................................................... 24
7.1
General Information .....................................................................................................24
7.2
Translation of Status Codes ..........................................................................................24
7.3
Identity Object (01h).....................................................................................................26
7.4
Message Router (02h)..................................................................................................28
7.5
Assembly Object (04h) .................................................................................................29
7.6
Connection Manager (06h) ...........................................................................................31
7.7
DLR Object (47h) .........................................................................................................34
7.8
QoS Object (48h) .........................................................................................................35
7.9
TCP/IP Interface Object (F5h) .......................................................................................36
7.10
Ethernet Link Object (F6h) ............................................................................................39
7.11
PROFIBUS Master Object (301h)..................................................................................43
7.12
PROFIBUS Slave Object (302h)....................................................................................43
7.13
EN2PBR Object (303h) ................................................................................................50
A Technical Specification ............................................................................................... 53
A.1
Functional Earth (FE) Requirements..............................................................................53
A.2
Power Supply ..............................................................................................................53
A.3
Environmental Specification..........................................................................................53
A.4
EMC (CE) Compliance .................................................................................................53
B Copyright Notices ......................................................................................................... 54
Linking Device User Manual
SCM-1202-026 1.0
About This Document
3 (56)
1
About This Document
1.1
About This Document
This manual describes how to install and configure EtherNet/IP to PROFIBUS DP Linking
Device.
For additional related documentation and file downloads, please visit the support website at
www.anybus.com/support.
1.2
1.3
1.4
Related Documents
Document
EtherNet/IP to Modbus-TCP Linking Device User Manual
Author
HMS
Copyright Notices for the HMS-EN2PB-R
HMS
Document ID
SCM-1202-008
Document history
Version
Date
Description
1.0
2017-04-21
First version
Trademark Information
Anybus® is a registered trademark of HMS Industrial Networks AB.
All other trademarks are the property of their respective holders.
Linking Device User Manual
SCM-1202-026 1.0
About This Document
1.5
4 (56)
Conventions
Ordered lists are used for instructions that must be carried out in sequence:
1.
First do this
2.
Then do this
Unordered (bulleted) lists are used for:
•
Itemized information
•
Instructions that can be carried out in any order
...and for action-result type instructions:
►
This action...
➨
leads to this result
Bold typeface indicates interactive parts such as connectors and switches on the hardware, or
menus and buttons in a graphical user interface.
Monospaced text is used to indicate program code and other
kinds of data input/output such as configuration scripts.
This is a cross-reference within this document: Conventions, p. 4
This is an external link (URL): www.hms-networks.com
This is additional information which may facilitate installation and/or operation.
This instruction must be followed to avoid a risk of reduced functionality and/or
damage to the equipment, or to avoid a network security risk.
Caution
This instruction must be followed to avoid a risk of personal injury.
WARNING
This instruction must be followed to avoid a risk of death or serious injury.
Linking Device User Manual
SCM-1202-026 1.0
EtherNet/IP to PROFIBUS DP Linking Device
5 (56)
2
EtherNet/IP to PROFIBUS DP Linking Device
2.1
Introduction
The EtherNet/IP to PROFIBUS DP Linking Device is used to provide a seamless connection between a PROFIBUS network and an EtherNet/IP network. The linking device enables the master of the EtherNet/IP network to control the PROFIBUS network, and data can be transmitted
transparently between the two networks.
2.2
Features
2.2.1
The EtherNet/IP to PROFIBUS DP Linking Device
•
Up to 7000 bytes IO data
3500 bytes in each direction over multiple IO connections on EtherNet/IP.
•
Routing of acyclic data
Predefined CIP objects available for specific PROFIBUS DPV1 Class 1 and Class 2 read
and write requests. These are accessed either by the PLC through CIP Message Instructions from Studio 5000 Logix Designer or from within the Custom Add-On Profile network
configuration software by the system integrator
2.2.2
2.2.3
2.2.4
•
Control/Status information added to the I/O data for diagnostic purposes
•
Live List of the active status of the connected slaves
•
Configuration through Customer Add-On Profile for Studio 5000 Logix Designer for Device
and Network configuration of the PROFIBUS network and data structures for Studio 5000
EtherNet/IP Adapter Class Product Specifics
•
Beacon Based DLR (Device Level Ring) and linear network topology supported
•
10/100 Mbit, full/half duplex operation
•
Dual port cut-through switch
•
ODVA Conformance tested
PROFIBUS DP Master Specifics
•
Complete PROFIBUS DP Master functionality according to IEC 61158
•
Controls up to 125 slaves
•
Acyclic Communication (DP-V1, Class 1 & 2)
•
Supports all common baudrates up to 12Mbps
•
Galvanically isolated PROFIBUS interface
Custom Add-On Profile for Studio 5000
•
Contains a unique tag editor for uplink PLC data structuring
•
Contains the PROFIBUS DP Master configuration tool
•
Contains IP Config utility
•
Backup of configuration data into Studio 5000 project and stored in the Controller memory
•
Dynamically generates data structures based on the configuration
Linking Device User Manual
SCM-1202-026 1.0
EtherNet/IP to PROFIBUS DP Linking Device
2.2.5
2.3
6 (56)
•
Automatic generation of named and structured Studio 5000 Controller Tags. Possible to
manually edit generated tag names if desired
•
Possible to Group tags by Slave which creates substructures per slave in Studio 5000
•
Possible to exclude defined tags to minimize the amount of tags in PLC
•
Possible to pack selected tags into arrays of tags to minimize the amount of tags in PLC
•
All network and device level configuration is done within Studio 5000
•
No need for any separately installed software or additional licenses
Other
•
USB for firmware download
•
ODVA, CE, UL, ATEX and Haz.Loc. certifications available
Unique Integration into Studio 5000
The EtherNet/IP to PROFIBUS DP Linking Device features a custom add-on profile (AOP) for
easy integration with Studio 5000. Within this add-on profile (AOP), the HMS configuration tool
can be launched. When the configuration is ready, it can automatically be translated to structured Studio 5000 controller tags.
All network and device level configuration is done within Studio 5000.
The add-on profile is supported by RSLogix 5000, v20 and later.
2.4
Data Mapping
PROFIBUS slots are assembled in multiple Class 1 Exclusive Owner (IO) Connections, on the
EtherNet/IP side. There are a maximum of 10 available connections (with an associated input
and output connection parameter per each) available. Each connection can manage up to a
maximum of 500 bytes input data and 496 bytes output data. In total, all 10 connections can
manage 3500 bytes input data and 3500 bytes output data.
Linking Device User Manual
SCM-1202-026 1.0
EtherNet/IP to PROFIBUS DP Linking Device
7 (56)
Connections will be made as needed. If a PROFIBUS slot does not fit into the remaining parts
of a connection, it will be moved to the next connection. Every slot will always be checked
against already existing connections. If it fits in the unused space of an earlier connection, it will
be put there.
2.5
Configuring the EtherNet/IP Network
The Linking Device is an EtherNet/IP adapter (slave) on the EtherNet/IP network. The general
settings for the adapter interface are configured using the configuration pages. All data transfers
must be configured in Studio 5000. Please note that the size of the I/O data that can be read
from and written to the module is defined when configuring the linking device using the configuration pages.
2.6
Control Word
16 bit control word sent to the linking device from the PLC or EtherNet/IP scanner.
2.7
Bit(s)
Name
Description
0-1
Run mode
2-15
-
0 - PROFIBUS is set to IDLE
1 - PROFIBUS is set to OPERATE
2 - PROFIBUS is set to STOP
Bits are unused
Status Word
16 bit status word sent from the linking device to the EtherNet/IP scanner or PLC.
2.8
Bit(s)
Name
Description
0-1
Run mode
2
CFG error
0 - PROFIBUS in IDLE (or not initialized)
1 - PROFIBUS is set in OPERATE
2 - PROFIBUS is set in STOP
0 - Configuration is valid and in use.
1 - Configuration is either missing or invalid.
3-15
-
-
PROFIBUS Slave Live List
The PROFIBUS slave live list consists of a 16 byte bit-field, where each bit corresponds to one
slave on the PROFIBUS network. Each bit is linked to one specific PROFIBUS node address,
according to the table below.
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
0
1
2-14
15
Slave 7
Slave 15
...
Slave 6
Slave 14
...
Slave 5
Slave 13
...
Slave 4
Slave 12
...
Slave 3
Slave 11
...
Slave 2
Slave 10
...
Slave 1
Slave 9
...
Slave 0
Slave 8
...
Slave
127
Slave
126
Slave
125
Slave
124
Slave
123
Slave
122
Slave
121
Slave
120
Linking Device User Manual
SCM-1202-026 1.0
About the Linking Device
3
About the Linking Device
3.1
External View
8 (56)
A: Power Connector
This connector is used to apply power to the
linking device. It is also possible to connect
protective earth (PE) to the power connector.
B: SD Card Slot
Currently not in use.
C: USB Port
This port adds the possibility to connect a PC
to the linking device to perform firmware
upgrades.
D: Status LEDs
E: DIN Rail Connector
The DIN-rail mechanism fastens the linking
device to a DIN-rail and connects the module
to protective earth (PE).
F: EtherNet/IP Connectors
G: PROFIBUS Connector
Linking Device User Manual
SCM-1202-026 1.0
About the Linking Device
3.2
9 (56)
Mounting the Linking Device
The EtherNet/IP to PROFIBUS DP Linking Device can be physically installed either by mounting it onto a DIN-rail or, if installed in areas exposed to vibration, by mounting it on a wall for
more stability.
3.2.1
DIN-rail Mounting
Make sure the DIN-rail fastening mechanism on the
back of the module is in a fixed and closed position, i.
e. pushed all the way up.
To mount the module, first hook it on to the DIN-rail
(1), then push it against the DIN-rail to make it snap
on (2).
To unmount the module, a screwdriver is needed.
Use the screwdriver to push the DIN-rail fastening
mechanism on the back of the module down until it
locks in a fixed and open position (1). Then unhook
the module from the DIN-rail (2).
Do not leave the module with the DIN-rail fastening
mechanism in a fixed and open position. This may
eventually wear the fastening mechanism out so it
cannot be used efficiently. Be sure to push the DINrail fastening mechanism back into the fixed and
closed position after demounting the module.
Linking Device User Manual
SCM-1202-026 1.0
About the Linking Device
3.2.2
10 (56)
Wall Mounting
Use the wall mounting option if there is a need to place the linking device in an environment exposed to vibration. This way of mounting the module offers more stability than the traditional
DIN-rail mounting.
: The device should be fastened in a standing-up position, to ensure a constant air flow.
When mounting the device to a wall using the wall mount option, do not forget to connect the
module to protective earth (PE) via the power connector.
Step
Description
Visual Description
Open up the package containing the
wall mounting accessories.
- One metal frame
- Industrial velcro
- Four plastic vibration dampers
Remove the plastic protection from
one side of the velcro.
Attach the velcro to the metal frame.
Attach the four plastic vibration
dampers to the linking device, on the
side that will face the wall.
Remove the plastic protection from
the other side of the velcro.
Turn the device around, so that the
plastic vibration dampers face
downwards.
Fasten the metal frame to the device
by pressing the frame firmly against
the device, making the two velcro
parts attach to each other.
Attach the metal frame and the device to a wall using screws and washers (not enclosed).
Linking Device User Manual
SCM-1202-026 1.0
About the Linking Device
3.3
11 (56)
Status LEDs
Name
Indication
Meaning
(MS EN)
Module Status
Off
Flashing green
Power off
Not configured, or scanner in
idle state
Controlled by a scanner in
run state
Boot up
Recoverable error
Fatal error
Green
(NS)
Network Status
Orange
Flashing red
Red
Off
Flashing green
Green
Orange
Flashing red
Red
(Link 1, Link 2)
Ethernet Link 1 & 2
Off
Flashing green
Yellow
Flashing yellow
(MS PB)
Master Status
(DB)
Database Status
(CS)
Communication
Status
Off
Red
Flashing green
Green
Off
Green
Flashing green
Red
Off
Green
Flashing green
(TH)
Token Hold
Red
Off
Green
No IP address
Online, no connection
Online, connection
established
Boot up
Timeout
Duplicate IP address, fatal
error
No link
Receiving/transmitting Ethernet packets at 100 Mbit
Boot up
Receiving/transmitting Ethernet packets at 10 Mbit
Master is offline
Master in STOP mode
Master in CLEAR mode
Master in OPERATE mode
No database
Database OK
Database download in
progress
Database invalid
No data exchange
Data exchange with all
slaves
Data exchange with at least
one slave
Bus control error
Another station holds the
Token
Master interface holds the
Token
At power-up, LED 1 - 2 will indicate solid orange and LED 3 - 4 will indicate solid yellow for 15 30 seconds. This will be followed by a LED test sequence, performed on the (MS EN) Module
Status and (NS) Network Status LEDs.
3.4
EtherNet/IP Connectors
Pin no
Description
1
2
3
6
4, 5, 7, 8
TX+
TXRX+
RXNot connected
Housing
Shield
Linking Device User Manual
Connector
SCM-1202-026 1.0
About the Linking Device
3.5
3.6
3.7
12 (56)
PROFIBUS Connector
Pin no
Description
3
4
5
B-Line
RTS
6
8
1, 2, 7, 9
GND Bus
+5 V Bus Out
A-Line
Not connected
Housing
FE (Functional Earth)
Connector
USB Connector
Pin no
Description
1
+5 V Input
2
USBDM (USB communication
signals)
3
USBDP (USB communication
signals)
4
Signal GND
Housing
Cable shield
Connector
Power Connector
Pin no
Description
1
2
3
+24 V DC
GND
FE (Functional Earth)
Linking Device User Manual
Connector
SCM-1202-026 1.0
The Linking Device Web Interface
4
13 (56)
The Linking Device Web Interface
The web page interface for the linking device is accessible via the USB port.
4.1
1.
Connect a PC to the USB port on the linking device.
2.
Open a web browser.
3.
Open the linking device overview web page via IP 192.168.10.1.
Overview
This page provides general information about the linking device.
4.2
Firmware Update
Via the firmware page, it is possible to update the firmware in the linking device. The Firmware
Update Log presents information about the latest firmware update.
To update the firmware, find the firmware file (.swu) on the computer, and press install. The linking device will restart two times during the process.
4.3
Diagnostics
The diagnostic web page provides information about the system and, if available, logs of fatal
events.
Linking Device User Manual
SCM-1202-026 1.0
Studio 5000 Implementation Example
5
14 (56)
Studio 5000 Implementation Example
This section will be a guide through all steps necessary to create a basic configuration for the
EtherNet/IP to PROFIBUS DP Linking Device.
5.1
Step by Step Guide
1.
Start the Studio 5000 software. Expand the “I/O Configuration” folder in the tree view.
Right-click “Ethernet” and select “New Module”.
2.
Select the HMS-EN2PB-R linking device and click “Create”.
3.
In the “New Module” window, assign a name to the module. The IP address should be set
via the BOOTP-DHCP server and entered in the IP address field. Click “Change” in the
“Module Definition” section.
Linking Device User Manual
SCM-1202-026 1.0
Studio 5000 Implementation Example
15 (56)
4.
In the “Module Definition” window, launch the configuration manager for the
HMS-EN2PB-R linking device.
5.
This part of the configuration manager is called the tag editor. Since this is a new configuration, the editor is empty. To proceed, open the HMS-EN2PB-R configuration tool by clicking
the left-most icon in the tool bar.
Linking Device User Manual
SCM-1202-026 1.0
Studio 5000 Implementation Example
6.
7.
16 (56)
The bus view window consists of three parts.
–
1. A tree view of all connected devices
–
2. A graphical view of the connected devices in the network
–
3. A list view for input/output data and slave properties
Add a slave by right-clicking on the “General” folder in the tree view. Choose “Install
new .GS* file”. In this case, an Anybus-S DPV1 is used.
Linking Device User Manual
SCM-1202-026 1.0
Studio 5000 Implementation Example
8.
Right-click the slave to bring up the slave properties window.
9.
Set the name of the slave and set the PROFIBUS slave address
Linking Device User Manual
17 (56)
SCM-1202-026 1.0
Studio 5000 Implementation Example
18 (56)
10. Right-click in the list view, and choose “Module selection”.
11. Add input/output data to the slave. In this case, there are three transactions.
12. When the configuration is finished, close the bus view window. Click “Yes” to apply the new
configuration and transfer it to the tag editor.
Linking Device User Manual
SCM-1202-026 1.0
Studio 5000 Implementation Example
19 (56)
13. The tag editor is now updated with Studio 5000 tags. All transactions are visible under the
“Input Data” and “Output data” tabs.
14. Download the configuration to the linking device by clicking the download icon in the tool
bar. The progress bar will indicate the progress.
15. Close the tag editor.
16. Close the “Module Definition” window. Click “Yes” in the RSLogix 5000 information window,
to change the module definition in the Studio 5000 environment.
Linking Device User Manual
SCM-1202-026 1.0
Studio 5000 Implementation Example
20 (56)
17. The tags for the configuration are now imported into Studio 5000.
18. Download the configuration to the Studio 5000 project by right-clicking the computer icon
and then choosing “Download”.
19. To run the application, set the least significant bit in the control word to “y”.
Linking Device User Manual
SCM-1202-026 1.0
Tag Editor
6
21 (56)
Tag Editor
The tag editor is supported by Windows 7 and later.
6.1
Tag Editor Overview
Initially, the tag editor looks like this.
The pen symbol in the lower right corner tells if the PLC is online or offline. No configuration is
possible while the PLC is online.
6.1.1
Menu Choices
File
•
Import
Import a configuration from the hard drive.
•
Export
Export a configuration from the hard drive.
•
Exit
Edit
•
Select All
•
Deselect All
Tools
•
Edit PROFIBUS Configuration
This option will launch the PROFIBUS configuration manager.
Linking Device User Manual
SCM-1202-026 1.0
Tag Editor
22 (56)
•
Download Configuration to EN2PB-R
Download the configuration to the linking device.
•
Launch IPConfig
With the IPConfig tool, it is possible to scan for devices and alter IP settings for the linking
device.
•
Reboot
•
Factory Reset
Resets the linking device to default values.
•
Restore
Loads the latest stored configuration from Studio 5000.
•
Options
–
Hide report on retrieve of PROFIBUS configuration.
–
Group tags on PLC (by PROFIBUS slave)
Help
•
6.2
About
Tag Editor Basics
When the PROFIBUS configuration tool is closed after configuration, the tag editor will be filled
with resulting Studio 5000 tags.
Tags that are new or altered since last time, will be presented in magenta color.
In the left most column, check boxes makes it possible to choose which tags should be exported
to the Studio 5000 environment. Only tags that are checked will be exported.
Linking Device User Manual
SCM-1202-026 1.0
Tag Editor
6.3
23 (56)
Tag Rule Definitions
The default and automatically generated tags will follow and adhere to the rules
below. This list is only informative.
When adding process tags (controller tags) to the configuration the following rules must apply:
•
The designated memory address of the process tag must be inside the process data area
boundaries.
•
The memory address of the process tag must be divisible by four, for data types DINT or
REAL or a tag whose dimension is above zero.
•
The memory address of the process tag must be dividable by two for data type INT.
•
Two process tags can not occupy the same memory address area on the EtherNet/IP side.
•
Two process tags can address the same memory address on the PROFIBUS side.
•
The designated memory address of the process tag must smaller than or equal to the corresponding designated memory address in the configuration.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
24 (56)
7
CIP Objects
7.1
General Information
This chapter specifies the CIP-object implementation in the module. These objects can be accessed from the network, but not directly by the host application.
Mandatory objects
•
Identity Object (01h), p. 26
•
Message Router (02h), p. 28
•
Assembly Object (04h), p. 29
•
Connection Manager (06h), p. 31
•
DLR Object (47h), p. 34
•
QoS Object (48h), p. 35
•
TCP/IP Interface Object (F5h), p. 36
•
Ethernet Link Object (F6h), p. 39
It is possible to implement additional CIP-objects in the host application using the CIP forwarding functionality.
Unconnected CIP routing is supported, which means that a message can be sent to a device
without first setting up a connection.
7.2
Translation of Status Codes
If an error occurs when an object is requested from the application, an error code is returned.
These HMS-EN2PB-R error codes are translated to CIP status codes according to the table
below.
Linking Device Error Code
CIP Status Code
Value
00h
01h
02h
Value
1Eh
1Eh
1Eh
Error
Reserved
Reserved
Invalid message format
Status
Embedded service error
Embedded service error
Embedded service error
03h
Unsupported object
05h
Path destination unknown
04h
Unsupported instance
05h
Path destination unknown
05h
Unsupported Command
08h
Service not supported
06h
Invalid CmdExt(0)
14h
Depending on Anybus CompactCom Service returning this reply, e.g. attribute not supported
07h
Invalid CmdExt(1)
-
Depending on Anybus CompactCom Service returning this reply
08h
09h
Attribute not settable
Attribute not gettable
0Eh
2Ch
Attribute not settable
Attribute not gettable
0Ah
0Bh
Too Much Data
Not Enough Data
15h
13h
Too much data
Not enough data
0Ch
Out of range
09h
Invalid attribute value
0Dh
Invalid state
0Ch
Object state conflict
0Eh
0Fh
Out of resources
Segmentation failure
02h
1Eh
Resource unavailable
Embedded service error
10h
Segmentation buffer overflow
23h
Buffer overflow
11h
Value too high
09h
Invalid attribute value
12h
Value too low
09h
Invalid attribute value
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
25 (56)
Linking Device Error Code
CIP Status Code
Value
13h
Value
0Fh
Error
Attribute controlled
Status
A permission/privilege check failed
14h
Message channel too small
11h
Reply data too large
FFh
Object Specific Error
1Fh
Other
-
1Eh
Vendor specific error. No additional error codes will
be sent on EtherNet/IP
Embedded service error
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
7.3
26 (56)
Identity Object (01h)
Category
Extended
Object Description
The Identity Object provides identification of and general information about the module.
Supported Services
Class:
Get_Attribute_Single
Get_Attributes_All
Instance:
Get_Attribute_Single
Set_Attribute_Single
Get_Attributes_All
Reset
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0001h (Object revision)
2
Max
instance
Number of
instances
Get
UINT
Maximum instance number
Get
UINT
Number of instances
3
Instance Attributes
#
Name
Access
Type
1
Vendor ID
Get
UINT
005Ah (HMS Industrial Networks AB)
2
Device Type
Get
UINT
000Ch (Communications Adapter)
3
Product
Code
Revision
Get
UINT
0056h (HMS-EN2PB-R)
Get
Major and minor firmware revision
Status
Serial
Number
Product
Name
Active
language
Get
Get
Struct of:
USINT
USINT
WORD
UDINT
4
5
6
7
11
12
Supported
Language
List
Get
Set
Get
Linking Device User Manual
SHORT_
STRING
Struct of:
USINT
USINT
USINT
Array of:
Struct of:
USINT
USINT
USINT
Value/Description
See Device Status table below
Unique serial number (assigned by HMS)
“HMS-EN2PB-R”
Only English supported.
Only English supported.
SCM-1202-026 1.0
CIP Objects
27 (56)
Device Status
bit(s)
Name
0
1
Module Owned
(reserved)
2
Configured
This bit shows if the product has other settings than "out-of-box". The value is set to true if the configured attribute
in the Application Object is set and/or the module’s NV storage is changed from default.
3
(reserved)
4... 7
Extended Device Status:
Value:
Meaning:
8
9
10
0000b
0010b
0011b
0100b
Unknown
Faulted I/O Connection
No I/O connection established
Non volatile configuration bad
0101b
Major fault
0110b
0111b
Connection in Run mode
Connection in Idle mode
(other)
(reserved)
Set for minor recoverable faults.
Set for minor unrecoverable faults.
Set for major recoverable faults.
11
Set for major unrecoverable faults.
12... 15
(reserved)
Service Details: Reset
There are two types of network reset requests on EtherNet/IP:
Type 0: Power Cycling
Reset
This service power cycles the module.
Type 1: Out of box reset
This service sets an “out of box” configuration (all configuration data will be erased) and
performs a reset.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
7.4
28 (56)
Message Router (02h)
Category
Extended
Object Description
The Message Router Object provides a messaging connection point through which a client may address a
service to any object class or instance residing in the physical module.
In the HMS-EN2PB-R module it is used internally to direct object requests.
Supported Services
Class:
-
Instance:
-
Class Attributes
-
Instance Attributes
-
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
7.5
29 (56)
Assembly Object (04h)
Category
Extended
Object Description
The Assembly object uses static assemblies and holds the Process Data sent/received by the host application. It allows data to and from each object to be sent or received over a single connection. The default assembly instance IDs used are 100-109 and 150-159.
It is possible for the application to create and support up to ten consuming and ten producing instances.
The terms “input” and “output” are defined from the network’s point of view. An input will produce data on the
network and an output will consume data from the network.
See also ....
•
Assembly Mapping Object (see Anybus CompactCom 40 Software Design Guide)
Supported Services
Class:
Get_Attribute_Single
Instance:
Get_Attribute_Single
Set_Attribute_Single
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0002h (Object revision)
2
Max
instance
Get
UINT
Maximum instance number
Instance 03h Attributes (Heartbeat, Input-Only)
This instance is used as heartbeat for Input-Only connections. The data size of the Heartbeat instance in the
Forward_Open-request should be 0 bytes, however other values are also permitted.
#
Name
Access
Type
Value/Description
3
Data
Set
N/A
- (The data size of this attribute is zero)
4
Size
Get
UINT
0 (Number of bytes in attribute 3)
Instance 04h Attributes (Heartbeat, Listen-Only)
This instance is used as heartbeat for listen-only connections. The data size of the Heartbeat instance in the
Forward_Open-request should be 0 bytes, however other values are also permitted.
#
Name
Access
Type
Value/Description
3
Data
Set
N/A
- (The data size of this attribute is zero)
4
Size
Get
UINT
0 (Number of bytes in attribute 3)
Instance 05h Attributes (Configuration Data)
Configuration Data that is sent through the service Forward_Open will be written to this instance.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
30 (56)
#
Name
Access
Type
Value/Description
3
Data
Set
N/A
- (Configuration data written to the application when the forward open
command has the configuration data included)- (The data size of this attribute is zero)
4
Size
Get
UINT
0 (Number of bytes in attribute 3)
Instance 06h Attributes (Heartbeat, Input-Only Extended)
This instance is used as heartbeat for input-only extended connections, and does not carry any attributes.
The state of connections made to this instance does not affect the state of the HMS-EN2PB-R module, i.e. if
the connection times out, the module does not switch to the Error state. The data size of the Heartbeat instance in the Forward_Open-request should be 0 bytes, however other values are also permitted.
#
Name
Access
Type
Value/Description
3
Data
Set
N/A
- (The data size of this attribute is zero)
4
Size
Get
UINT
0 (Number of bytes in attribute 3)
Instance 07h Attributes (Heartbeat, Listen-Only Extended)
This instance is used as heartbeat for listen-only extended connections, and does not carry any attributes.
The state of connections made to this instance does not affect the state of the Anybus CompactCom 40 module, i.e. if the connection times out, the module does not switch to the Error state. The data size of the Heartbeat instance in the Forward_Open-request should be 0 bytes, however other values are also permitted.
#
Name
Access
Type
Value/Description
3
Data
Set
N/A
- (The data size of this attribute is zero)
4
Size
Get
UINT
0 (Number of bytes in attribute 3)
Instance 64h Attributes (Producing Instance)
#
Name
Access
Type
Value/Description
3
Produced
Data
Size
Get
Array of BYTE
This data corresponds to the Write Process Data.
Get
UINT
Number of bytes in attribute 3
4
Instance 96h Attributes (Consuming Instance)
#
Name
Access
Type
Value/Description
3
Produced
Data
Size
Get
Array of BYTE
This data corresponds to the Read Process Data.
Get
UINT
Number of bytes in attribute 3
4
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
7.6
31 (56)
Connection Manager (06h)
Category
Extended
Object Description
This object is used for connection and connectionless communications, including establishing connections
across multiple subnets.
Supported Services
Class:
-
Instance:
Get Attribute All
Get Attribute Single
Set Attribute Single
Large_Forward_Open
Forward_Open
Forward_Close
Unconnected Send (when unconnected routing is enabled)
Class Attributes
(No supported class attributes)
Instance Attributes
#
Name
Access
Type
Value/Description
1
Open
Requests
Set
UINT
Number of Forward Open service requests received.
2
Open Format
Rejects
Set
UINT
Number of Forward Open service requests which were rejected due to
bad format.
3
Open Resource
Rejects
Set
UINT
Number of Forward Open service requests which were rejected due to
lack of resources.
4
Open Other
Rejects
Set
UINT
Number of Forward Open service requests which were rejected for reasons other than bad format or lack of resources.
5
Close
Requests
Set
UINT
Number of Forward Close service requests received.
6
Close Format Rejects
Set
UINT
Number of Forward Close service requests which were rejected due to
bad format.
7
Close Other
Rejects
Set
UINT
Number of Forward Close service requests which were rejected for reasons other than bad format.
8
Connection
Timeouts
Set
UINT
Total number of connection timeouts that have occurred in connections
controlled by this Connection Manager.
Class 0 Connection Details
Not supported.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
32 (56)
Class 1 Connection Details
General
Class 1 connections are used to transfer I/O data, and can be established to instances in the Assembly Object. Each Class 1 connection will establish two data transports; one consuming and one producing. The
heartbeat instances can be used for connections that shall only access inputs. Class 1 connections use UDP
transport. Null forward open is supported.
Total number of supported
class 1 connections:
10
Max input connection size:
500 bytes with Forward_Open
Max output connection
size:
496 bytes with Forward_Open
Supported RPI (Requested
Packet Interval):
5... 3200 ms
T→O Connection type:
Point-to-point, Multicast, Null
O→-T Connection type:
Point-to-point, Null
Supported trigger types:
Cyclic, CoS (Change of State)
Supported priorities:
Low, High, Scheduled, Urgent
T
Target, in this case the module
O
Origin, in this case the master
Connection Types
•
Exclusive-Owner connection
This type of connection controls the outputs of the HMS-EN2PB-R and does not depend on other
connections.
•
Max. no. of Exclusive-Owner
connections:
10
Connection point O →T:
Assembly Object, instance 96h (Default)
Connection point T →O:
Assembly Object, instance 64h (Default)
Input-Only connection
Not supported.
•
Input-Only Extended connection
Not supported.
•
Listen-Only connection
Not supported.
•
Listen-Only Extended connection
Not supported.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
33 (56)
Class 3 Connection Details
General
Class 3 connections are used to establish connections towards the message router. Thereafter, the connection is used for explicit messaging. Class 3 connections use TCP transport.
No. of simultaneous Class 3
connections:
6
Supported RPI (Requested Packet
Interval):
100... 10000 ms
T→O Connection type:
Point-to-point
O→-T Connection type:
Point-to-point
Supported trigger type:
Application
Supported connection size:
1448 bytes with Large Forward Open
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
7.7
34 (56)
DLR Object (47h)
Category
Extended
Object Description
The Device Level Ring (DLR) Object provides the status information interface for the DLR protocol. This protocol enables the use of an Ethernet ring topology, and the DLR Object provides the CIP application-level interface to the protocol.
Supported Services
Class:
Get_Attribute_Single
Get_Attributes_All
Instance:
Get_Attribute_Single
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0003h (Object revision)
Instance Attributes
Attributes #1–4 and #6–7 an be customized by implementing the EtherNet/IP Host Object.
#
Name
Access
Type
Value/Description
1
Network
Topology
Get
USINT
Bit:
0
1
Contents:
“Linear”
“Ring”
2
Network
Status
Get
USINT
Bit:
0
1
2
3
4
Contents:
“Normal” (N/A)
“Ring Fault”
“Unexpected Loop Detected”
“Partial Network Fault”
“Rapid Fault/Restore Cycle”
10
Active
Supervisor
Address
Get
This attribute holds the IP address (IPv4) and/or the Ethernet Mac address of the active ring supervisor.
12
Capability
Flags
Get
Struct of:
UDINT
Array of:
6 USINTs
DWORD
Linking Device User Manual
82h (Beacon-based ring node, Flush_Table frame capable)
SCM-1202-026 1.0
CIP Objects
7.8
35 (56)
QoS Object (48h)
Category
Extended
Object Description
Quality of Service (QoS) is a general term that is applied to mechanisms used to treat traffic streams with different relative priorities or other delivery characteristics. Standard QoS mechanisms include IEEE 802.1D/Q
(Ethernet frame priority) and Differentiated Services (DiffServ) in the TCP/IP protocol suite.
The QoS Object provides a means to configure certain QoS related behaviors in EtherNet/IP devices.
The object is required for devices that support sending EtherNet/IP messages with nonzero DiffServ code
points (DSCP), or sending EtherNet/IP messages in 802.1Q tagged frames.
Supported Services
Class:
Get_Attribute_Single
Instance:
Get_Attribute_Single
Set_Attribute_Single
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0001h (Object revision)
Instance Attributes
#
Name
Access
Type
Value/Description
1
802.1Q Tag
Enable
Set
USINT
Enables or disables sending 802.1Q frames.
4
DSCP
Urgent
Set
USINT
5
DSCP
Scheduled
Set
USINT
6
DSCP High
Set
USINT
7
DSCP Low
Set
USINT
8
DSCP
Explicit
Set
USINT
Bit:
0
1
Linking Device User Manual
Contents:
Disabled (Default)
Enabled
CIP transport class 1 messages with priority Urgent
Default: 55
CIP transport class 1 messages with priority Scheduled
Default: 47
CIP transport class 1 messages with priority High
Default: 43
CIP transport class 1 messages with priority Low
Default: 31
CIP UCMM and CIP class 3
Default: 27
SCM-1202-026 1.0
CIP Objects
7.9
36 (56)
TCP/IP Interface Object (F5h)
Category
Extended
Object Description
This object provides the mechanism to configure the TCP/IP network interface of the module. It groups the
TCP/IP-related settings in one instance for each TCP/IP capable communications interface.
Supported Services
Class:
Get_Attribute_All
Get_Attribute_Single
Instance:
Get_Attribute_All
Get_Attribute_Single
Set_Attribute_Single
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0004h (Object revision)
2
Max
instance
Number of
instances
Maximum ID
Number
Class
Attributes
Maximum ID
Number Instance
Attributes
Get
UINT
1 (Maximum instance number)
Get
UINT
1 (Number of instances)
Get
UINT
7 (The attribute number of the last implemented class attribute)
Get
UINT
13 (The attribute number of the last implemented instance attribute)
3
6
7
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
37 (56)
Instance Attributes
#
Name
Access
Type
Value
Comments
1
Status
Get
DWORD
-
Bit:
Meaning:
(reserved, set to 0)
0–3
When set to h, attribute #5 contains valid
configuration from DHCP or non-volatile storage. When set to 2h, attribute #5 contains
valid configuration from hardware settings.
Remaining values are reserved for future
use.
Multicast pending if set to 1.
4
5
7
8–31
Interface configuration pending if set to 1. A
new configuration will be loaded at the next
reset.
AcdStatus. Set to 1 if an address conflict is
detected. Address conflict detection is enabled/disabled in attribute #10.
AcdFault
(reserved, set to 0)
Bit:
Meaning:
0-3:
Always 4. For more information, consult the
CIP specifications.
4:
The ‘Configuration Settable’-bit reflects the
value of instance attribute #9 in the "EtherNet/IP Host Object (F8h)".
5:
The module is hardware configurable when
this bit is set to 1. The bit will be set if any of
the address attributes is set in the Network
Configuration Object (04h) during setup or if
attribute #6 (Hardware configurable address)
in the Application Object (FFh) is set.
6:
Always 0. For more information, consult the
CIP specifications.
7:
If set to 1, the device is capable of detecting
address conflicts. The bit is set to 0 if address conflict detection is disabled in the
Ethernet Host Object.
8 - 31:
(reserved, set to 0)
Value:
Meaning
0:
Configuration from non-volatile memory
2:
Configuration from DHCP
6
2
3
4
5
6
8
9
Configuration
Capability
Get
Configuration Control
Get/Set
Physical Link
Object
Get
Interface
Configuration
Get/Set
Host Name
TTL Value
Get/Set
Get/Set
Mcast Config
Set
Alloc Control
Linking Device User Manual
DWORD
DWORD
-
-
Struct of:
UINT (Path
size)
-
Padded EPATH
20 F6 24 03h
0002h
Path to Ethernet Link Object, Instance #3
-
Struct of:
UDINT (IP)
IP address
UDINT (Mask)
Subnet mask
UDINT (GW)
Default gateway
UDINT
(DNS1)
Primary DNS
UDINT
(DNS2)
Secondary DNS
STRING
(Domain)
Default domain
STRING
USINT
1
Struct of:
USINT
Host name of the HMS-EN2PB-R
TTL value for EtherNet/IP multicast packets
IP multicast configuration
0
Value:
Meaning:
SCM-1202-026 1.0
CIP Objects
#
Name
38 (56)
Access
Type
Value
Comments
0:
10
(reserved)
USINT
0
Num Mcast
UINT
-1
Mcast Start
Addr
SelectAcd
UDINT
-
Bool
1
Set
Use default allocation algorithm to generate
multicast addresses
1:
Allocate multicast addresses according to
the values in the “Num Mcast”- and “Mcast
Start Addr”-fields.
Set to zero. Do not change.
Number of multicast addresses to allocate for EtherNet/IP
Starting multicast address from which to begin
allocation
Value:
Meaning:
0:
1:
11
LastConflictDetected
AcdActiviity
Set
RemoteMAC
ArpPdu
13
Encapsulation inactivity
timeout
Set
Linking Device User Manual
Struct of:
USINT
-
ARRAY of 6
USINT
ARRAY of 28
USINT
UINT
0 - 3600
Disable ACD
Enable ACD (Default).
If ACD (address conflict detection) is enabled, bit 6 in attribute #1 will be set if an
ACD conflict is detected. The Network Status
LED will also indicate a detected conflict.
ACD Diagnostic parameters Related to the last conflict
detected.
State of ACD activity when last conflict
detected.
MAC address of remote node form the ARP
PDU in which a conflict was detected.
Copy of the raw ARP PDU in which a conflict
was detected.
Number of seconds of inactivity before a TCP connection is closed.
0: Disabled
SCM-1202-026 1.0
CIP Objects
7.10
39 (56)
Ethernet Link Object (F6h)
Category
Extended
Object Description
This object maintains link specific counters and status information for an IEEE 802.3 communications interface. Exactly one instance for each communications interface on the module is supported. Instances for internally accessible interfaces can also be supported.
Supported Services
Class:
Get_Attributes_All
Get_Attribute_Single
Instance:
Get_Attributes_All
Get_Attribute_Single
Set_Attribute_Single
Get_And_Clear
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0004h (Object revision)
2
Max
Instance
Number of
Instances
Maximum ID
Number
Class
Attributes
Maximum ID
Number Instance
Attributes
Get
UINT
1 or 3 (Maximum instance number)
Get
UINT
1 or 3 (Number of instances)
Get
UINT
7 (The attribute number of the last implemented class attribute.)
Get
UINT
11 (The attribute number of the last implemented instance attribute.)
3
6
7
Instance Attributes
#
Name
Access
Type
Value
Comments
1
Interface
Speed
Get
UDINT
10 or 100
Actual Ethernet interface speed.
2
Interface
Flags
Get
DWORD
-
See table “Interface Flags” below.
3
Physical
Address
Interface
Counters
In Octets
In Ucast
Packets
In NUcast
Packets
In Discards
Get
Array of 6
USINTs
Struct of:
(MAC ID)
Physical network address, i.e. assigned MAC address.
UDINT
UDINT
N/A
N/A
Octets received on the interface
Unicast packets received on the interface
UDINT
N/A
Nonunicast packets received on the interface
UDINT
N/A
Inbound packets with unknown protocol
UDINT
N/A
Inbound packets that contain errors (does not include
In discards)
4
Get
In Errors
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
#
5
Name
In Unknown
Protos
Out Octets
Out Ucast
Packets
Out NUcast
Packets
Out Discards
Out Errors
Media
Counters
Alignment
Errors
40 (56)
Access
Get
Type
Value
Comments
UDINT
N/A
Inbound packets with unknown protocol
UDINT
UDINT
N/A
N/A
Octets sent on the interface
Unicast packets sent on the interface
UDINT
N/A
Nonunicast packets sent on the interface
UDINT
N/A
Outbound packets with unknown protocol
UDINT
N/A
Outbound packets that contain errors (does not include Out discards)
Struct of:
Media specific counters
UDINT
N/A
Frames received that are not an integral number of octets in length
FCS Errors
UDINT
N/A
Frames received that do not pass the FCS check
Single
Collisions
UDINT
N/A
Successfully transmitted frames that have experienced exactly one collision
Multiple
Collisions
UDINT
N/A
SQE Test
Errors
UDINT
0
Successfully transmitted frames that have experienced more than one collision
The number of times the SQE test error message is
generated(Counter not provided with current PHY
interface)
Deferred
Transmissions
Late
Collisions
UDINT
N/A
Frames for which the first transmission attempt is delayed because the medium is busy
UDINT
N/A
The number of times a collision is detected later than
512 bit-times into the transmission of a packet
Excessive
Collisions
UDINT
N/A
MAC Transmit Errors
UDINT
N/A
Frames for which a transmission fails due to excessive
collisions
Frames for which a transmission fails due to an internal MAC sublayer receive error
Carrier
Sense Errors
UDINT
N/A
Frame Too
Long
UDINT
N/A
MAC Receive Errors
UDINT
N/A
Linking Device User Manual
The number of times that the carrier sense condition
was lost or never asserted when attempting to transmit
a frame
Frames received that exceed the maximum permitted
frame size
Frames for which reception on an interface fails due to
an internal MAC sublayer receive error
SCM-1202-026 1.0
CIP Objects
41 (56)
#
Name
Access
Type
6
Interface
Control
Control Bits
Forced Interface Speed
Get/Set
Struct of:
7
Interface
Type
8
Interface
State
Admin State
Interface
Label
Interface
Capability
9
10
11
Value
Comments
WORD
UINT
-
Get
USINT
-
Interface control bits
Speed at which the interface shall be forced to operate.
Returns ‘Object state Conflict’ if auto-negotiation is
enabled
See table “Interface State” below.
Get
USINT
-
See table “Interface Type” below.
Get/Set
USINT
Get
SHORT_
STRING
Struct of:
—
See table “Admin State” below.
See table “Interface Label” below.
-
Indication of the capabilities of the interface
Capability
Bits
DWORD
-
Interface capabilities, other than speed/duplex
See table “Interface Capability” below.
Speed/Duplex Options
Struct of:
-
USINT
-
Indicates speed/duplex pairs supported in the Interface Control Attribute
Speed/duplex array count
Array of Struct
of:
UINT
-
Speed/duplex array
-
Interface speed
USINT
-
Interface Duplex Mode
0 = half duplex
1 = full duplex
2 - 255 = Reserved
Get
Interface Flags
Bit
Name
Description
0
Link status
Indicates whether or not the Ethernet 802.3 communications interface is connected to
an active network.
Value:
Meaning:
1
Half/full duplex
0
Inactive link
1
Active link
Indicates the duplex mode currently in use.
Value:
0
1
2-4
5
6
7-31
Negotiation Status
Manual Setting requires
Reset
Meaning:
Half duplex
Full duplex
Indicates the status of link auto-negotiation.
Value:
Meaning:
0
Auto-negotiation in progress.
1
Auto-negotiation and speed detection failed (using default values)
(Recommended default values are 10 Mbps, half duplex)
2
Auto negotiation failed but detected speed (using default duplex value)
3
Successfully negotiated speed and duplex.
4
Auto-negotiation not attempted. Forced speed and duplex.
Value:
Meaning:
0
Interface can activate changes to link parameters during runtime
1
Reset is required in order for changes to have effect
Local Hardware Fault
Value:
Meaning:
(reserved)
0
No local hardware fault detected
1
Local hardware fault detected
Set to 0.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
42 (56)
Interface State
This attribute indicates the current operational state of the interface.
Value
0
1
Description
2
3
The interface is disabled.
The interface is testing.
Unknown interface state.
The interface is enabled and is ready to send and receive data.
Admin State
This attribute controls the administrative setting of the interface state.
Value
0
Description
1
2
3-255
Enable the interface.
Disable the interface.
(reserved)
(reserved)
Interface Label
Instance
1
2
3
Value
Port 1
Port 2
Internal
Interface Type
Value
Description
Instance
1
2
Twisted-pair
2
2
Twisted-pair
3
1
Internal interface
Interface Capability
Bit
0
Name
Description
Implementation
Manual setting requires
reset
Indicates that the device automatically applies changes
made to the Interface Control attribute (#6) and, therefore,
does not require a reset in order for changes to take effect.
This bit shall have this value when the Interface Control attribute (#6) is not implemented.
Return 0
1
Autonegotiate
0
Indicates that the interface does not support link autonegotiation
0 for internal interface, 1 for external
interfaces
1
Indicates that the interface supports link autonegotiation
0
Indicates that the interface does not support auto
MDIX operation
1
Indicates that the interface supports auto MDIX
operation
0
Indicates that the interface does not support manual
setting of speed/duplex. The Interface Control attribute (#6) shall not be supported.
1
Indicates that the interface supports manual setting of
speed/duplex via the Interface Control attribute (#6)
2
3
4 - 31
Auto-MDIX
Manual
speed/duplex
Reserved
Shall be set to 0
Linking Device User Manual
0 for internal interface, 1 for external
interfaces
0 for internal interface, 1 for external
interfaces
Return 0
SCM-1202-026 1.0
CIP Objects
7.11
43 (56)
PROFIBUS Master Object (301h)
Category
Extended
Object Description
-
Supported Services
Class:
Get_Attribute_Single
Instance:
Get_Attribute_Single
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0001h (Object revision)
2
Max
instance
Number of
instances
Get
UINT
0001h (Maximum instance number)
Get
UINT
0001h (Only 1 instance)
3
Instance Attributes
#
Name
Access
Type
Value/Description
1
Operation
Mode
Get
USINT
The operation mode of the PROFIBUS master can be read here.
0x00 - OFFLINE (master is not initialized) (cannot be Set)
0x40 - STOP (master is not active on the network)
0x80 - CLEAR (master sends no valid data to slaves, but reads data)
0xC0 - OPERATE (master in normal mode)
2
Slave Configured List
Get
Array of 16 *
USINT
Array of 16 bytes where each bit correspond to one slave.
0 - Slave is not part of PROFIBUS configuration.
1 - Slave is present in database.
3
Data Transfer List
Get
Array of 16 *
USINT
Array of 16 bytes where each bit correspond to one slave.
0 - Slave is not in data exchange with master.
1 - Slave is in data exchange with master.
4
Slave Diagnostic List
Get
Array of 16 *
USINT
Array of 16 bytes where each bit correspond to one slave.
0 - Slave does not have any diagnostic data.
1 - Slave has got diagnostics.
7.12
PROFIBUS Slave Object (302h)
Category
Extended
Object Description
Through this object it is possible to access acyclic PROFIBUS DP-V1 services from the EtherNet/IP-side.
The instance number corresponds to the PROFIBUS slave address.
It is not possible to address a PROFIBUS slave with node address 0.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
44 (56)
Supported Services
Class:
Get_Attribute_Single
Instance:
Get_Attribute_Single
Set_Attribute_Single
Class2_Initiate
Class2_Abort
Class2_Read
Class2_Write
Set_Slave_Address
Class1_Read
Class1_Write
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0001h (Object revision)
2
Max
instance
Number of
instances
Class 2 Connection Live
List
Get
UINT
-
Get
UINT
007Eh (126 instances)
Get
Array of 16 *
USINT
Array of 16 bytes where each bit correspond to one Class 2 connection.
0 - Connection not open.
1 - Connection established.
3
100
Instance Attributes
#
Name
Access
Type
Value/Description
1
Is
Configured
Get
BOOL
False – Slave is not part of PROFIBUS configuration.
True – Slave is present in database.
2
In Data
Transfer
Get
BOOL
False – Slave is not in data exchange with master.
True – Slave is in data exchange with master.
3
Diagnostics
Available
Get
BOOL
False – Slave does not have any diagnostic data currently.
True – Slave has got diagnostics.
4
Diagnostics
Data
Get
Byte array with diagnostic data for the slave. Length of data is 6-244.
5
Start
Set
Array of
USINT
BOOL
6
Output Data
Get
Array of
USINT
Output data for the selected slave. Data which is sent from the master to
the slave.
Array of bytes, from 0 - 244.
7
Input Data
Get
Array of
USINT
Input data for the selected slave. Data which is sent from the slave to the
master.
Array of bytes, from 0 - 244.
False – Disable (Stop) slave
True – Enable (Start) slave
Enable or disable the data exchange for one particular slave. As default
the data exchange is enabled.
Service Details: Class2 Initiate
Details
Service Code:
Valid for:
Linking Device User Manual
0x4B
Object Instance
SCM-1202-026 1.0
CIP Objects
45 (56)
Description
This service opens up a Class 2 communication channel.
Request
Name
Value
Description
Class
Instance
Attribute
0x0302
1-125
0
Slave node address
-
Successful Response
If a successful response is received, the following data will be returned:
Offset
Type
Description
0
1
SINT
SINT
Slave address
Max data length
2-3
4
INT
SINT
Send timeout
Features supported 1
5
SINT
Features supported 2
6
SINT
Profile features supported 1
7
SINT
Profile features supported 2
8-9
10
INT
SINT
Profile ident number
S_Type
11
SINT
S_Length
12
SINT
D_Type
13
SINT
D_Length
16-M
Array of SINT
S_Address
(M+1)-N
Array of SINT
D_Address
Error Response
If the service returns an error, General Status is set to error and the different error codes are
passed.
Name
Value
Description
General Status
0x1F: Vendor specific Error
CIP general status code (object specific)
Size of Additional Status
Additional Status
4
0-1: Error decode
-
2-3: Error code 1/ Error code 2
4-5: Extended Fault Information
See the PROFIBUS specification for
details.
Only returned for certain error messages.
6-7: Fault Information
-
See the PROFIBUS specification for details. Only the lower byte is used.
Service Details: Class2 Abort
Details
Service Code:
Valid for:
Linking Device User Manual
0x4C
Object Instance
SCM-1202-026 1.0
CIP Objects
46 (56)
Description
With this service a Class 2 connection can be aborted. Before this service can be used, a connection needs to be opened (using the Class2 Initiate service).
Request
Name
Value
Description
Class
Instance
Attribute
0x0302
1-125
0
Slave node address
-
Successful Response
If a successful response is received, no data will be returned.
Error Response
If the service returns an error, General Status is set to error and the different error codes are
passed.
Name
Value
Description
General Status
0x1F: Vendor specific Error
CIP general status code (object specific)
Size of Additional Status
4
0-1: Extended Fault Information
-
2-3: Fault Information
-
Only returned for certain error messages.
Service Details: Class2 Read
Details
Service Code:
Valid for:
0x4D
Object Instance
Description
This service initiates a PROFIBUS DP-V1 Class 2 Read. Before this service can be used, a
connection needs to be opened (using the Class2 Initiate service).
Request
Name
Value
Description
Class
Instance
Attribute
Data[0]: Slot
0x0302
1-125
0
0-255
-
Data[1]: Index
0-255
Index number to address
Data[2]: Length
1-240
Number of data bytes to request. Response can contain fewer bytes
than requested
Slave node address
Slot number to address
Successful Response
Offset
Type
Description
0-N
Array of SINT
Data
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
47 (56)
Error Response
If the service returns an error, General Status is set to error and the different error codes are
passed.
Name
Value
Description
General Status
0x1F: Vendor specific Error
CIP general status code (object specific)
Size of Additional Status
Additional Status
4
0-1: Error decode
-
2-3: Error code 1/ Error code 2
4-5: Extended Fault Information
See the PROFIBUS specification for
details
Only returned for certain error messages
6-7: Fault Information
-
See the PROFIBUS specification for details. Only the lower byte is used
Service Details: Class2 Write
Details
Service Code:
Valid for:
0x4E
Object Instance
Description
This service initiates a PROFIBUS DP-V1 Class 2 Write. Before this service can be used, a connection needs to be opened (using the Class2 Initiate service).
Request
Name
Value
Description
Class
Instance
Attribute
Data[0]: Slot
0x0302
1-125
0
0-255
-
Data[1]: Index
0-255
Index number to address
Data[2-N]: Data
-
The data to write. 1-240 bytes
Slave node address
Slot number to address
Successful Response
If a successful response is received, no data will be returned.
Error Response
If the service returns an error, General Status is set to error and the different error codes are
passed.
Name
Value
Description
General Status
0x1F: Vendor specific Error
CIP general status code (object specific)
Size of Additional Status
Additional Status
4
0-1: Error decode
-
2-3: Error code 1/ Error code 2
4-5: Extended Fault Information
See the PROFIBUS specification for
details
Only returned for certain error messages
6-7: Fault Information
-
Linking Device User Manual
See the PROFIBUS specification for details. Only the lower byte is used
SCM-1202-026 1.0
CIP Objects
48 (56)
Service Details: SetSlaveAddress
Details
Service Code:
Valid for:
0x4F
Object Instance
Description
With this service, the PROFIBUS master can assign a node address to a PROFIBUS slave.
Request
Name
Value
Description
Class
Instance
Attribute
Data[0]: New slave
address
Data[1-2]: Slave ident
number
Data[3]: No address
change lock
0x0302
1-126
0
0-126
-
00xFFFF
0-255
PROFIBUS ident number for the slave that shall receive a new
address
0 – address can be changed again
1 – address can only be changed if the address is reset to 126 (using
factory reset or similar)
-
Array of bytes with vendor specific data. 0-240 bytes
Data[4-N]: Vendor specific data
Slave node address
New slave address
Successful Response
If a successful response is received, optional data will be returned.
Offset
Type
Description
0-N
Array of SINT
Data
Error Response
If the service returns an error, General Status is set to error and the different error codes are
passed.
Name
Value
Description
General Status
0x1F: Vendor specific Error
CIP general status code (object specific)
Size of Additional Status
Additional Status
4
0-1: Error decode
-
2-3: Error code 1/ Error code 2
4-5: Extended Fault Information
See the PROFIBUS specification for
details.
Only returned for certain error messages.
6-7: Fault Information
-
See the PROFIBUS specification for details. Only the lower byte is used.
Service Details: Class1 Read
Details
Service Code:
Valid for:
0x50
Object Instance
Description
This service initiates a PROFIBUS DP-V1 Class 1 Read.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
49 (56)
Request
Name
Value
Description
Class
Instance
Attribute
Data[0]: Slot
0x0302
1-125
0
0-255
-
Data[1]: Index
0-255
Index number to address
Data[2]: Length
1-240
Number of data bytes to request. Response can contain fewer bytes
than requested
Offset
Type
Description
0-N
Array of SINT
Data
Slave node address
Slot number to address
Successful Response
Error Response
If the service returns an error, General Status is set to error and the different error codes are
passed.
Name
Value
Description
General Status
0x1F: Vendor specific Error
CIP general status code (object specific)
Size of Additional Status
Additional Status
4
0-1: Error decode
-
2-3: Error code 1/ Error code 2
4-5: Extended Fault Information
See the PROFIBUS specification for
details
Only returned for certain error messages
6-7: Fault Information
-
See the PROFIBUS specification for details. Only the lower byte is used
Service Details: Class1 Write
Details
Service Code:
Valid for:
0x51
Object Instance
Description
This service initiates a PROFIBUS DP-V1 Class1 Write.
Request
Name
Value
Description
Class
Instance
Attribute
Data[0]: Slot
0x0302
1-125
0
0-255
-
Data[1]: Index
0-255
Index number to address
Data[2-N]: Data
-
The data to write. 1-240 bytes
Slave node address
Slot number to address
Successful Response
If a successful response is received, no data will be returned.
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
50 (56)
Error Response
If the service returns an error, General Status is set to error and the different error codes are
passed.
7.13
Name
Value
Description
General Status
0x1F: Vendor specific Error
CIP general status code (object specific)
Size of Additional Status
Additional Status
4
0-1: Error decode
-
2-3: Error code 1/ Error code 2
4-5: Extended Fault Information
See the PROFIBUS specification for
details
Only returned for certain error messages
6-7: Fault Information
-
See the PROFIBUS specification for details. Only the lower byte is used
EN2PBR Object (303h)
Category
Extended
Object Description
...
Supported Services
Class:
Get_Attribute_Single
Instance:
Get_Attribute_Single
Class Attributes
#
Name
Access
Type
Value
1
Revision
Get
UINT
0001h (Object revision)
2
Max
instance
Number of
instances
Get
UINT
0001h (Maximum instance number)
Get
UINT
0001h (Only 1 instance)
3
Instance Attributes
#
Name
Access
Type
Value/Description
1
Control word
Get
INT
Current control word (most recent received from the EtherNet/IP
scanner)
2
3
Status word
Product
version
Get
INT
Current status word
Get
Array of 2 *
UINT
BCD-coded version number for the product
First UINT
High byte: Major version (0x01 == 1)
Low byte: Minor version (0x02 == 2)
Second UINT
Build number (0x0009 == 9)
4
EtherNet/IP
version
Get
Array of 2 *
UINT
BCD-coded version number of the CompactCom device
First UINT
High byte: Major version (0x01 == 1)
Low byte: Minor version (0x02 == 2)
Second UINT
Build number (0x0009 == 9)
Linking Device User Manual
SCM-1202-026 1.0
CIP Objects
51 (56)
#
Name
Access
Type
Value/Description
5
PROFIBUS
master
version
Get
UINT
BCD-coded version number of the PROFIBUS master
High byte: Major version (0x01 == 1)
Low byte: Minor version (0x02 == 2)
6
GUID
Get
16 bytes GUID of the configuration
7
Configuration version
supported
Get
Array of 16 *
USINT
UINT
Linking Device User Manual
1: This is the version of the configuration that the EN2PBR supports
SCM-1202-026 1.0
This page intentionally left blank
Appendix A: Technical Specification
A
Technical Specification
A.1
Functional Earth (FE) Requirements
53 (56)
In order to achieve proper EMC behavior, the product must be connected to functional earth
(FE) via the DIN-rail connector. If the DIN-rail cannot be used, FE must be connected to the
power connector.
HMS Industrial Networks does not guarantee proper EMC behavior unless these FE requirements are fulfilled.
Note: Make sure the DIN-rail is properly connected to FE.
A.2
Power Supply
A.2.1
Supply Voltage
The HMS-EN2PB-R linking device requires a regulated 24 V (20.4 V to 28.8 V) DC power
source.
A.2.2
Power Consumption
The typical power consumption is 220 mA at 24 V
The maximum power consumption is 300 mA at 24 V
A.3
Environmental Specification
A.3.1
Temperature
Operating
-25º to +60º Celsius, -13º to +140º F
Nonoperating
-40º to +85º Celsius, -40º to +185º F
A.3.2
Relative Humidity
The product is designed for a relative humidity of 5% to 95% noncondensing.
A.4
EMC (CE) Compliance
EMC compliance testing has been conducted according to the Electromagnetic Compatibility
Directive 2004/108/EC. For more information please consult the EMC compliance document,
see product/support pages for EtherNet/IP to PROFIBUS DP Linking Device at www.anybus.
com.
Linking Device User Manual
SCM-1202-026 1.0
Appendix B: Copyright Notices
B
54 (56)
Copyright Notices
For a document with a complete list of all copyright notices, see the referenced documents section in the beginning of this user manual.
Linking Device User Manual
SCM-1202-026 1.0
This page intentionally left blank
last page
© 2017 HMS Industrial Networks AB
Box 4126
300 04 Halmstad, Sweden
[email protected]
SCM-1202-026 1.0.3846 / 2017-04-21 09:26
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement