null  User manual
X-gateway Interface Addendum
DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Connecting DevicesTM
HALMSTAD • CHICAGO • KARLSRUHE • TOKYO • BEIJING • MILANO • MULHOUSE • COVENTRY • PUNE • COPENHAGEN
HMS Industrial Networks
Mailing address: Box 4126, 300 04 Halmstad, Sweden
Visiting address: Stationsgatan 37, Halmstad, Sweden
E-mail: [email protected]
www.hms-networks.com
Important User Information
This document is intended to provide a good understanding of the functionality offered by the Interface described
here.
The reader is expected to be familiar with high level software design, and communication systems in general. The
use of advanced interface-specific functionality may require in-depth knowledge of networking internals and/or
information from the network specifications. In such cases, the persons responsible for the implementation of this
product should either obtain the necessary specifications to gain sufficient knowledge, or alternatively limit the
implementation in such a way that this is not necessary.
Liability
Every care has been taken in the preparation of this manual. 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 US and other countries.
Trademark Acknowledgements
Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their
respective holders.
!
WARNING: This is a class A product. in a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
ESD Note: This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD
control procedures are not followed. Static control precautions are required when handling the
product. Failure to observe this may cause damage to the product.
DeviceNet Adapter X-Gateway Interface Addendum
Copyright© HMS Industrial Networks AB
Doc: HMSI-27-243, Rev: 2.00
May 2014
Table of Contents
Table of Contents
Preface
About This Document
How To Use This Document ............................................................................................................ P-1
Important User Information .............................................................................................................. P-1
Related Documents.............................................................................................................................. P-2
Document History ............................................................................................................................... P-2
Conventions & Terminology......................................................................................................... P-2
Support .................................................................................................................................................. P-2
Chapter 1
About the DeviceNet Adapter Interface
General Description..............................................................................................................................1-1
Features...................................................................................................................................................1-1
External View ........................................................................................................................................1-2
DeviceNet Status LEDs ..............................................................................................................1-2
Connectors and Switches................................................................................................................1-2
Chapter 2
Installation and Configuration
Configuration Switches ........................................................................................................................2-1
Baudrate Configuration.................................................................................................................2-1
Mac ID Configuration ..................................................................................................................2-1
Gateway Config Interface ....................................................................................................................2-2
Network Configuration (RSNetWorx) ..............................................................................................2-3
Step 1: Install the .EDS-file .........................................................................................................2-3
Step 2: Scan the network for new devices........................................................................................2-3
Step 3: Adding the Adapter Interface to the Scanners scanlist........................................................2-4
Step 4: Configuring I/O Sizes ......................................................................................................2-4
Chapter 3
Data exchange
General Information.............................................................................................................................3-1
Input Data (Gateway to DeviceNet) .............................................................................................3-2
Output Data (DeviceNet to Gateway) ..........................................................................................3-2
Table of Contents 4
Chapter 4
CIP Object Implementation
General Information.............................................................................................................................4-1
Identity Object, Class 01h....................................................................................................................4-2
General Information......................................................................................................................4-2
Class Attributes ...........................................................................................................................4-2
Instance Attributes........................................................................................................................4-2
Device Status ................................................................................................................................4-3
Service Details: Reset ....................................................................................................................4-3
Message Router, Class 02h...................................................................................................................4-4
General Information......................................................................................................................4-4
Class Attributes ...........................................................................................................................4-4
Instance Attributes........................................................................................................................4-4
DeviceNet Object, Class 03h ..............................................................................................................4-5
General Information......................................................................................................................4-5
Class Attributes ...........................................................................................................................4-5
Instance #1 Attributes .................................................................................................................4-5
Assembly Object, Class 04h ................................................................................................................4-6
General Information......................................................................................................................4-6
Class Attributes ...........................................................................................................................4-6
Instance Attributes - Instance/Connection Point 64h ....................................................................4-6
Instance Attributes - Instance/Connection Point 96h ....................................................................4-6
Connection Object, Class 05h.............................................................................................................4-7
General Information......................................................................................................................4-7
Class Attributes ...........................................................................................................................4-7
Instance Attributes........................................................................................................................4-8
Instance 1 (Explicit Messaging Connection) Attributes .................................................................4-9
Instance 2 (Polled Connection) Attributes......................................................................................4-9
Instance 3 (Bit-strobe connection) Attributes..................................................................................4-9
Instance 4 (COS/Cyclic connection) Attributes ...........................................................................4-10
Instance 10... 14 (UCMM Explicit Server Instances) Attributes ...............................................4-10
Acknowledge Handler Object, Class 2Bh .......................................................................................4-11
General Information....................................................................................................................4-11
Class Attributes .........................................................................................................................4-11
Instance Attributes......................................................................................................................4-11
I/O Data Input Mapping Object, Class A0h..................................................................................4-12
General Information....................................................................................................................4-12
Class Attributes .........................................................................................................................4-12
Instance Attributes, Instance 01h................................................................................................4-12
I/O Data Output Mapping Object, Class A1h ..............................................................................4-13
General Information....................................................................................................................4-13
Class Attributes .........................................................................................................................4-13
Instance Attributes, Instance 01h................................................................................................4-13
Diagnostic Object, Class AAh...........................................................................................................4-14
General Information....................................................................................................................4-14
Class Attributes .........................................................................................................................4-14
Instance Attributes, Instance 01h................................................................................................4-14
Parameter Data Input Mapping Object, Class B0h .......................................................................4-15
General Information....................................................................................................................4-15
Class Attributes .........................................................................................................................4-15
Instance Attributes, Instance 01h................................................................................................4-15
Parameter Data Output Mapping Object, Class B1h ....................................................................4-16
General Information....................................................................................................................4-16
Table of Contents 5
Class Attributes .........................................................................................................................4-16
Instance Attributes, Instance 01h................................................................................................4-16
Appendix A Technical Specification
DeviceNet Interface Details ...............................................................................................................A-1
DeviceNet Conformance Note.......................................................................................................... A-1
DeviceNet Connector Pinout............................................................................................................. A-1
Preface
P. About This Document
P.1 How To Use This Document
This document describes network specific features and procedures needed when operating the DeviceNet Adapter Interface for the Anybus X-gateway. For general information and operating instructions
for the Anybus X-gateway, consult the Anybus X-gateway User Manual.
The reader of this document is expected to be familiar with DeviceNet networking technology, and
communication systems in general.
For further information, documentation etc., please see www.anybus.com
P.2 Related Documents
Document
Anybus X-gateway User Manual
Anybus-S DeviceNet Fieldbus Appendix
Common Industrial Protocol (CIP) specification
DeviceNet Adaptation of CIP
Author
HMS
HMS
ODVA
ODVA
P.3 Document History
P.3.1 Revision List
Revision
1.00
1.10
1.11
2.00
Date
2004-04-02
2007-11-19
2007-11-21
May 2014
Author
PeP
PeP
PeP
SDa
Chapter
All
All
4
Multiple
Description
First release
Major rewrite
Minor update
New hardware and Anybus Configuration Manager
P.3.2 Conventions & Terminology
The following conventions are used throughout this document:
•
Numbered lists provide sequential steps
•
Bulleted lists provide information, not procedural steps
•
The term ‘X-gateway’ refers to the Anybus X-gateway
•
The term ‘Interface’ refers to the DeviceNet Adapter interface for the Anybus X-gateway.
•
The term ‘user manual’ refers to the Anybus X-gateway User Manual.
•
Hexadecimal values are written in the format NNNNh, where NNNN is the hexadecimal value.
•
16/32 bit values are generally stored in Motorola (big endian) format unless otherwise stated.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
About This Document P-7
P.4 Support
For general contact information and support, please refer to the contact and support pages at
www.anybus.com.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Chapter 1
1. About the DeviceNet Adapter Interface
1.1 General Description
The DeviceNet Adapter Interface for the Anybus X-gateway implements a DeviceNet communications
adapter (profile no. 12). The interface acts as an adapter, which means it can be accessed by a DeviceNet
scanner, but it will not initiate communication by itself.
The interface exchanges data through two buffers as follows:
Input Buffer
This buffer holds data forwarded
from the other network, i.e. data
which can be read by the DeviceNet scanner.
•
Output Buffer
This buffer is forwarded to the
other network, i.e. data which can
be written by the DeviceNet scanner.
Input
Buffer
DeviceNet
•
(from Gateway)
DeviceNet Adapter
Output
Buffer
(to Gateway)
1.2 Features
•
Galvanically isolated bus electronics
•
125kbit, 250kbit and 500kbit operation
•
On-board configuration switches
•
Up to 512 byte of I/O in each direction
•
Explicit Messaging (up to 512 bytes in each direction)
•
Polled I/O
•
Bit-strobed I/O
•
Change-of-state / Cyclic I/O
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
About the DeviceNet Adapter Interface 1-9
1.3 External View
Front View
Top-mounted DeviceNet
interface
1.3.1 DeviceNet Status LEDs
LED
Gateway
Status
NS
MS
Colour
Indication
Consult the Gateway user manual for
further details.
Off
No power or not online
Green
Link OK, online, connected
Green, flash- Online, not connected
ing
Red
Critical link failure
Red, flashing Connection timeout
Off
No power
Green
Operational
Gateway
status
Not used
NS
MS
Not used
USB Gateway
Config Connector
Green, flash- Data size error
ing
Red
Unrecoverable fault
Red, flashing Minor fault
1.3.2 Connectors and Switches
DeviceNet Connector
See A-31 “DeviceNet Connector Pinout”.
Not used
NS
MS
Not used
Gateway
status
Bottom-mounted
DeviceNet interface
Top-mounted Interface
Configuration switches
DeviceNet Connector
Gateway Power
Connector
Configuration Switches
See 2-9 “Configuration Switches”.
Gateway Power Connector
Consult the X-Gateway User Manual for further details.
USB Gateway Config Connector
Bottom-mounted Interface
DeviceNet Connector
Configuration Switches
Consult the X-Gateway User Manual for further details.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Chapter 2
2. Installation and Configuration
2.1 Configuration Switches
2.1.1 Baudrate Configuration
Switches 1 and 2 specifies the operating baudrate for the Adapter Interface as follows:
Switch 1
OFF
OFF
ON
ON
Switch 2
OFF
ON
OFF
ON
Switch 3
-
Switch 4
-
Switch 5
-
Switch 6
-
Switch 7
-
Baudrate
125 kbps
250 kbps
500 kbps
(reserved)
OFF
ON
Example:
Switch 8
-
Baudrate set to 250 kbps.
Note: The orientation of the switches follows that of the Adapter Interface (top or bottom).
2.1.2 Mac ID Configuration
Switches 3 to 8 specifies the MACID for the Adapter Interface in binary format as follows:
Switch 2
...
-
Switch 3
OFF
OFF
OFF
...
ON
ON
ON
Example:
Switch 4
OFF
OFF
OFF
...
ON
ON
ON
Switch 5
OFF
OFF
OFF
...
ON
ON
ON
Switch 6
OFF
OFF
OFF
...
ON
ON
ON
Switch 7
OFF
OFF
ON
...
OFF
ON
ON
Switch 8
OFF
ON
OFF
...
ON
OFF
ON
Mac ID
0
1
2
...
61
62
63
ON
OFF
ON
OFF
ON
OFF
Switch 1
...
-
MACID set to 42.
Note: The orientation of the switches follows that of the Adapter Interface (top or bottom).
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Installation and Configuration 2-11
2.2 Gateway Config Interface
The X-gateway and the DeviceNet slave interface may be configured by using the software tool Anybus
Configuration Manager (ACM), which is available from www.anybus.com/support
When ACM is connected to the gateway via the USB configuration connector, the following settings are
available:
See also:
•
The Anybus X-gateway User Manual, for full details on using ACM.
•
The online help in ACM, for further help on the available settings.
•
4-20 “Assembly Object, Class 04h”
•
4-26 “I/O Data Input Mapping Object, Class A0h”
•
4-27 “I/O Data Output Mapping Object, Class A1h”
•
4-29 “Parameter Data Input Mapping Object, Class B0h”
•
4-30 “Parameter Data Output Mapping Object, Class B1h”
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Installation and Configuration 2-12
2.3 Network Configuration (RSNetWorx)
The following example describes how to include the Adapter Interface in a DeviceNet network using
RSNetWorx.(The procedure used for other network configuration tools is similar, although individual
steps may be slightly different.)
2.3.1 Step 1: Install the .EDS-file
Each device in a DeviceNet network is associated with an .EDS-file1. This file contains information
about the device and is used by the network configuration tool, in this case RSNetWorx.
1. Start RSNetWorx for DeviceNet.
2. To add the .EDS-file for the Adapter interface, select ‘EDS Wizard’ from the ‘Tools’ menu.
3. Click ‘Next’
4. Make sure ‘Register an EDS file(s)’ is selected
5. Click ‘Next’
6. Make sure ‘Register single file’ is selected
7. Type the path and filename of the EDS file, or click ‘Browse’ to select it using the file selector.
8. Click ‘Next’. (RSNetWorx will now parse and test the EDS file and display the result.)
9. Click ‘Next’. (Optionally, an icon to be used with the adapter can be selected now.)
10. Click ‘Next’. (A summary of the EDS process is displayed.)
11. Click ‘Next’. (The Wizard will indicate that the installation process is finished)
12. Click ‘Finish’. The .EDS-file is now included in the DeviceNet configuration tool (RSNetWorx).
2.3.2 Step 2: Scan the network for new devices
In order to be able to add the Adapter Interface to a Scanner’s scanlist, it must first be properly detected
by the network configuration tool (in this case RSNetWorx).
1. From the ‘Network’ menu, select ‘Online’.
This will scan the entire network and find any attached nodes.
2. When done, all devices found on the network will be presented graphically.
The Adapter Interface is now included in the DeviceNet configuration tool (RSNetWorx).
1. The latest version of the .EDS-file for this product can be obtained from www.hms-networks.com or by
contacting HMS.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Installation and Configuration 2-13
2.3.3 Step 3: Adding the Adapter Interface to the Scanners scanlist
To exchange data with the Adapter Interface, it must first be included in the Scanlist of a Scanner.
1. Double-click on the desired Scanner.
This will bring up a window with the configuration of the Scanner.
2. Select the ‘Scanlist-’tab.
You will be prompted whether to download the offline configuration to the Scanner, or upload
the Scanner’s current configuration.
3. Click ‘Upload’.
When done, a window will appear, showing which devices that are included in the Scanner’s
scanlist and which ones that are not.
4. Highlight ‘Anybus-S DeviceNet’ in the list of available devices
5. Click on the right-hand arrow (‘>’).
The Adapter Interface is now included in the Scanner’s scanlist.
2.3.4 Step 4: Configuring I/O Sizes
The I/O sizes for the interface must be configured in the Scanner.
1. From the ‘Scanlist’-window, select ‘Edit I/O Parameters’. A window will appear, containing the
I/O configuration for the Adapter interface.
2. Select ‘Polled’ by checking it’s checkbox.
3. The ‘Input’ and ‘Output’ data sizes must be set to match the values specified via the Gateway
Config interface. Click ‘OK’ when done.
Note: A warning message will appear, indicating that the configured size does not match the settings in the .EDS-file. This is perfectly normal, as the data sizes of the AnyBus-X DeviceNet
Adapter interface can be configured freely. Just click ‘Yes’ to continue.
4. You will now be prompted on whether or not the I/O data should be mapped automatically.
Click ‘Yes’.
5. Click ‘OK’
The configuration will now be downloaded to the Scanner. Once the Scanner is in Run mode, data will
be exchanged.
Note: In case of problems, verify that the I/O configuration specified in RSNetWorx matches that of
the gateway. Also make sure that the baudrate matches that of the DeviceNet network, and that the
MACID of the Adapter Interface doesn’t conflict with another device.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Chapter 3
3. Data exchange
3.1 General Information
The Adapter Interface exchanges up to 512 bytes of data in each direction.
This can be I/O Data and/or Explicit Message data:
•
I/O Data (Up to 512 bytes)
DeviceNet Adapter Interface
This data can be accessed by means of I/O
connections towards the Assembly Object. It
is also represented through the I/O Data Input/Output Mapping Objects.
Status Word
Live List
I/O Data
(from Gateway)
- 4-20 “Assembly Object, Class 04h”
- 4-26 “I/O Data Input Mapping Object,
Class A0h”
DeviceNet
See also...
- 4-27 “I/O Data Output Mapping Object,
Class A1h”
•
Explicit Msg
Control Word
I/O Data
(to Gateway)
Explicit Msg
Explicit Message data (Up to 512 bytes)
This data can be accessed acyclically by means
of Explicit Messaging.
See also...
- 4-29 “Parameter Data Input Mapping Object, Class B0h”
- 4-30 “Parameter Data Output Mapping Object, Class B1h”
The amount of data that is exchanged as I/O Data and Explicit Message data respectively is specified
via the Gateway Config Interface.
See also...
•
2-10 “Gateway Config Interface”
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Data exchange 3-15
3.1.1 Input Data (Gateway to DeviceNet)
Depending on the actual gateway configuration and how it has been set up to operate, parts of the data
produced by the DeviceNet Adapter Interface may be used to represent status information (i.e. Status
Word, Live List etc.).
I/O Data
(16 bytes)
Live List (8 bytes)
Status Word (2 bytes)
I/O Data
(10 bytes)
Status Word (2 bytes)
Live List (8 bytes)
Explicit Msg
(8 bytes)
Data from
gateway (14 bytes)
Example A:
I/O Data Size = 16
Explicit Message Size = 8
Live List = Enabled
Control & Status Word = Enabled
Explicit Msg
(14 bytes)
Data from
gateway (22 bytes)
Example B:
I/O Data Size = 10
Explicit Message Size = 14
Live List = Disabled
Control & Status Word = Enabled
Note: The Live List is only available on master-slave gateway versions.
3.1.2 Output Data (DeviceNet to Gateway)
Depending on the actual gateway configuration and how it has been set up to operate, the first two bytes
consumed by the DeviceNet Adapter Interface may be interpreted as control information (i.e. the Control Word).
Control Word (2 bytes)
Data to
gateway (22 bytes)
Example A:
I/O Data Size = 18
Explicit Message Size = 6
Control Word = Enabled
X-Gateway Interface Addendum: DeviceNet Adapter
I/O Data
(22 bytes)
I/O Data
(24 bytes)
Live List (8 bytes)
Data to
gateway (22 bytes)
Example B:
I/O Data Size = 6
Explicit Message Size = 16
Control Word = Disabled
Doc: HMSI-27-243, Rev: 2.00
Chapter 4
4. CIP Object Implementation
4.1 General Information
The DeviceNet Adapter Interface implements the following standard objects:
•
Identity Object, Class 01h
•
Message Router, Class 02h
•
DeviceNet Object, Class 03h
•
Assembly Object, Class 04h
•
Connection Object, Class 05h
•
Acknowledge Handler Object, Class 2Bh
In addition, the following vendor specific objects are implemented:
•
I/O Data Input Mapping Object, Class A0h
•
I/O Data Output Mapping Object, Class A1h
•
Diagnostic Object, Class AAh
•
Parameter Data Input Mapping Object, Class B0h
•
Parameter Data Output Mapping Object, Class B1h
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-17
4.2 Identity Object, Class 01h
4.2.1 General Information
Object Description
Implemented Services
Class services:
Instance services:
Get Attribute Single
Get Attribute Single
Reset (see 4-17 “Service Details: Reset”)
4.2.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
Type
UINT
UINT
UINT
Struct of:
USINT,
USINT
WORD
UDINT
SHORT_STRING
Value
005Ah (HMS Industrial Networks AB)
000Ch (Communications Adapter)
000Ch (Anybus-S DeviceNet)
4.2.3 Instance Attributes
#
1
2
3
4
5
6
7
Access
Get
Get
Get
Get
Get
Get
Get
Name
Vendor ID
Device Type
Product Code
Revision
Status
Serial Number
Product Name
X-Gateway Interface Addendum: DeviceNet Adapter
(Major fieldbus version)
(Minor fieldbus version)
(see 4-17 “Device Status”)
(assigned at manufacturing)
‘Anybus-S DeviceNet’
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-18
4.2.4 Device Status
bit(s)
0
1
2
3
4... 7
8
9
10
11
12... 15
Name
Module Owned (A master/scanner has allocated the Adapter Interface)
(reserved)
Configured (always set to zero)
(reserved)
Extended Device Status:
Value:Meaning:
0000b Unknown
0010b Faulted I/O Connection (not implemented)
0011b No I/O connection established
0100b Non-volatile configuration bad (not implemented)
0110b Connection in Run mode
0111b Connection in Idle mode
(other) (reserved)
Set for minor recoverable faults
Set for minor unrecoverable faults
Set for major recoverable faults
Set for major unrecoverable faults
(reserved)
4.2.5 Service Details: Reset
There are two types of network reset requests on DeviceNet:
•
Type 0: ‘Power Cycling Reset’
This causes the DeviceNet interface to restart its internal DeviceNet software layer. The overall
operation of the gateway remains unaffected, i.e. the gateway will neither reset itself nor the other
network interface.
•
Type 1: ‘Out of box reset’
This causes the DeviceNet interface to revert to an ‘out of box’ configuration and restart its internal DeviceNet software layer. The overall operation of the gateway remains unaffected, i.e. the
gateway will neither reset itself nor the other network interface.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-19
4.3 Message Router, Class 02h
4.3.1 General Information
Object Description
Supported Services
Class services:
-
Instance services:
-
4.3.2 Class Attributes
-
4.3.3 Instance Attributes
-
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-20
4.4 DeviceNet Object, Class 03h
4.4.1 General Information
Object Description
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Allocate Master/Slave Connection Set (4Bh)
Release Group 2 Identifier Set (4Ch)
4.4.2 Class Attributes
#
1
Name
Revision
Access
Get
Type
UINT
Value
0002h
Type
USINT
USINT
Value
(actual MAC ID)
Value:Meaning:
0 Operating at 125 kbps
1 Operating at 250 kbps
2 Operating at 500 kbps
False
00h
4.4.3 Instance #1 Attributes
#
1
2
Name
MAC ID
Baud Rate
Access
Get
Get
3
4
5
BOI
Bus off Counter
Allocation Information
6
MAC ID Switch changed
Get/Set BOOL
Get/Set USINT
Get
Struct of:
BYTE,
USINT
Get
BOOL
7
Baud rate Switch changed
Get
BOOL
8
9
MAC ID Switch Value
Baud Rate Switch Value
Get
Get
USINT
USINT
X-Gateway Interface Addendum: DeviceNet Adapter
Allocation choice byte
MAC ID of master
Value:Meaning
True MAC ID switches has changed since startup
False MAC ID switches has not changed since startup
Value:Meaning
True Baudrate switches has changed since startup
False Baudrate switches has not changed since startup
(actual value of node address switches)
(actual value of baud rate switches)
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-21
4.5 Assembly Object, Class 04h
4.5.1 General Information
Object Description
This object provides access to the I/O Data in the Input- and Output Buffers. The Assembly Object
uses static assemblies. The instance IDs are in the vendor specific range.
See also...
•
4-26 “I/O Data Input Mapping Object, Class A0h”
•
4-27 “I/O Data Output Mapping Object, Class A1h”
Services
Class services:
Get Attribute Single
Instance services:
Get Attribute Single
Set Attribute Single
4.5.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
4.5.3 Instance Attributes - Instance/Connection Point 64h
This instance is used to access Input I/O Data.
#
3
Access
Get
Name
Data
Type
Array of BYTE
Value
Corresponds to the Input I/O data in the Input Buffer.
4.5.4 Instance Attributes - Instance/Connection Point 96h
This instance is used to access Output I/O Data.
#
3
Access
Get
Name
Data
X-Gateway Interface Addendum: DeviceNet Adapter
Type
Array of BYTE
Value
Corresponds to the Output I/O data in the Output Buffer.
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-22
4.6 Connection Object, Class 05h
4.6.1 General Information
Object Description
Implemented Services
Class services:
Get Attribute Single
Instance services:
Get Attribute Single
Set Attribute Single
4.6.2 Class Attributes
#
1
Access
Get
100a Set
101a Set
102a Set
103a Set
104a Set
Name
Revision
Produced Data for Poll Connection
Type Value
UINT 0002h
USIN Value:Instance no.:
0: 100 (default)
T
1: 101
2: 102
Consumed Data for Poll Connection
USIN Value:Instance no.:
T
0: 150 (default)
1: 151
2: 152
Produced Data for Bit Strobe Connection USIN Value:Instance no.:
0: 100 (default)
T
1: 101
2: 102
Consumed Data for Bit Strobe Connec- USIN Value:Instance no.:
0: 150 (default)
tion
T
1: 151
2: 152
Produced Data for COS/Cyclic Connec- USIN Value:Instance no.:
tion
T
0: 100 (default)
1: 101
2: 102
Value:Instance no.:
3: 103
4: 104
5: 105
Value:Instance no.:
3: 153
4: 154
5: 155
Value:Instance no.:
3: 103
4: 104
5: 105
Value:Instance no.:
3: 153
4: 154
5: 155
Value:Instance no.:
3: 103
4: 104
5: 105
a. Value saved in non-volatile memory.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-23
4.6.3 Instance Attributes
#
1
Access
Get
Name
State
2
Get
Instance type
3
4
5
6
Get
Get
Get
Get
Transport Class trigger
Produced Connection ID
Consumed Connection ID
Initial Comm Characteristics
7
8
9
Get
Get
Produced Connection Size
Consumed Connection Size
a Expected Packet Rate
Get (Set)
12 Get (Set) Watchdog timeout action
Type Value
USIN Value:Meaning:
0: Non existent
T
1: Configuring
3: Established
4: Timeout
5: Deferred delete
USIN Value:Meaning:
0 Explicit messaging connection
T
1 I/O Connection
BYTE (defines the behaviour of the connection)
UINT (CAN ID for transmission)
UINT (CAN ID for reception)
BYTE 0Fh (No ACK)
- Produces over message group
- Does not consume
01h (ACK)
- Produces over message group 1
- Consumes over message group 2
UINT UINT 0
UINT 0
13 Get
USIN Value:Meaning:
0: Transition to the timed out state
T
1: Auto Delete
2: Auto Reset
3: Deferred Delete
UINT 0006h
15 Get
EPAT H
UINT 0004h
Produced Connection path
length
14 Get (Set)b Produced Connection Path
Consumed Connection path
length
16 Get (Set)b Consumed Connection Path
17 Get
18 Get (Set)
Production Inhibit Time
Connection timeout multiplier
EPAT 20 2B 24 01h
H
UINT 0
USIN Default: 0 (x4)
T
a. Only settable for instance #1
b. Saved in non-volatile memory
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-24
4.6.4 Instance 1 (Explicit Messaging Connection) Attributes
#
1
Access
Get
Name
State
2
Get
Instance type
Type Value
USIN Value:Meaning:
0: Non existent
T
1: Configuring
3: Established
4: Timeout
5: Deferred delete
USIN 0 (Explicit messaging connection)
T
4.6.5 Instance 2 (Polled Connection) Attributes
#
1
Access
Get
Name
State
2
Get
Instance type
Type Value
USIN Value:Meaning:
0: Non existent
T
1: Configuring
3: Established
4: Timeout
USIN 1 (I/O Connection)
T
4.6.6 Instance 3 (Bit-strobe connection) Attributes
#
1
Access
Get
Name
State
2
Get
Instance type
X-Gateway Interface Addendum: DeviceNet Adapter
Type Value
USIN Value:Meaning:
0: Non existent
T
1: Configuring
3: Established
4: Timeout
USIN 1 (I/O Connection)
T
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-25
4.6.7 Instance 4 (COS/Cyclic connection) Attributes
#
1
Access
Get
Name
State
2
Get
Instance type
3
4
5
6
Get
Get
Get
Get
Transport Class trigger
Produced Connection ID
Consumed Connection ID
Initial Comm Characteristics
7
8
9
12
Get
Get
Get/Set
Get
Produced Connection Size
Consumed Connection Size
Expected Packet Rate
Watchdog timeout action
13 Get
14 Get
15 Get
16 Get
Produced Connection path
length
Produced Connection Path
Consumed Connection path
length
Consumed Connection Path
Type Value
USIN Value:Meaning:
0: Non existent
T
1: Configuring
3: Established
4: Timeout
USIN 1 (I/O Connection)
T
BYTE (defines the behaviour of the connection)
UINT (CAN ID for transmission)
UINT (CAN ID for reception)
BYTE 0Fh (No ACK)
- Produces over message group
- Does not consume
01h (ACK)
- Produces over message group 1
- Consumes over message group 2
UINT UINT 0
UINT 0
USIN Value:Meaning:
0: Transition to the timed out state
T
1: Auto Delete
2: Auto Reset
3: Deferred Delete
UINT 0006h
EPAT H
UINT 0004h
EPAT 20 2B 24 01h
H
4.6.8 Instance 10... 14 (UCMM Explicit Server Instances) Attributes
#
1
Access
Get
Name
State
2
Get
Instance type
X-Gateway Interface Addendum: DeviceNet Adapter
Type Value
USIN Value:Meaning:
0: Non existent
T
1: Configuring
3: Established
4: Timeout
5: Deferred delete
USIN 0 (Explicit messaging connection)
T
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-26
4.7 Acknowledge Handler Object, Class 2Bh
4.7.1 General Information
Object Description
Implemented Services
Class services:
Get Attribute Single
Instance services:
Get Attribute Single
Set Attribute Single
4.7.2 Class Attributes
#
1
2
Access
Get
Get
Name
Revision
Max Instance
Type
UINT
UINT
Value
0001h
0001h
Type
UINT
USINT
UINT
Byte
Array of
USINT
Byte
Array of
USINT
Value
16
1
4
1
N/A
4.7.3 Instance Attributes
#
1
2
3
4
5
Access
Get/Set
Get/Set
Get/Set
Get
Get
Name
Acknowledge Timer
Retry Limit
Producing Connection Instance
Ack List Size
Ack List
6
7
Get
Get
Data with Ack Path List Size
Data with Ack Path List
1
N/A
Note: Instance 1 is created when initiating an acknowledged COS/Cyclic connection.
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-27
4.8 I/O Data Input Mapping Object, Class A0h
4.8.1 General Information
Object Description
This object can be used to access Input I/O Data.
The data is also available through instance 64h in the Assembly Object.
See also...
•
4-20 “Assembly Object, Class 04h”
•
4-27 “I/O Data Output Mapping Object, Class A1h”
•
4-30 “Parameter Data Output Mapping Object, Class B1h”
Supported Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
4.8.2 Class Attributes
#
1
Access
Get
Name Type
Data UINT
Value
0001h
4.8.3 Instance Attributes, Instance 01h
#
1a
Access
Get
Name Type
Data Array of
USINT
Description
Input I/O data (also available as Assembly Instance 64h)
a. This attribute is only available if the Input I/O Data size is larger than 0 (zero)
See also...
•
4-20 “Instance Attributes - Instance/Connection Point 64h”
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-28
4.9 I/O Data Output Mapping Object, Class A1h
4.9.1 General Information
Object Description
This object can be used to access Output I/O Data.
The data is also available through instance 96h in the Assembly Object.
See also...
•
4-20 “Assembly Object, Class 04h”
•
4-26 “I/O Data Input Mapping Object, Class A0h”
•
4-29 “Parameter Data Input Mapping Object, Class B0h”
Supported Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
Set Attribute Single
4.9.2 Class Attributes
#
1
Access
Get
Name Type
Data UINT
Value
0001h
4.9.3 Instance Attributes, Instance 01h
#
1a
Access Name Type
Get/Set Data Array of
USINT
Description
Output I/O data (also available in Assembly Instance 96h)
a. This attribute is only available if the Output I/O Data size is larger than 0 (zero)
See also...
•
4-20 “Instance Attributes - Instance/Connection Point 96h”
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-29
4.10 Diagnostic Object, Class AAh
4.10.1 General Information
Object Description
This vendor specific object provides access to misc. diagnostic information.
Implemented Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
4.10.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
4.10.3 Instance Attributes, Instance 01h
#
Access
01h Get
Name
Module serial number
Type
UDINT
04h
0Fh
11h
12h
14h
Module Software version
Input I/O Size
Input Total Size
Output I/O Size
Output Total Size
UINT
UINT
UINT
UINT
UINT
Get
Get
Get
Get
Get
X-Gateway Interface Addendum: DeviceNet Adapter
Description
(unique serial number, assigned during manufacturing)
(fieldbus software revision)
(total size of Input I/O Data in bytes)
(total size of Input Buffer in bytes)
(total size of Output I/O Data in bytes)
(total size of Output Buffer in bytes)
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-30
4.11 Parameter Data Input Mapping Object, Class B0h
4.11.1 General Information
Object Description
This object is used to access Input Explicit Message data.
See also...
•
4-20 “Assembly Object, Class 04h”
•
4-26 “I/O Data Input Mapping Object, Class A0h”
•
4-30 “Parameter Data Output Mapping Object, Class B1h”
Supported Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
4.11.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
4.11.3 Instance Attributes, Instance 01h
Each attribute carries up to 255 bytes of data.
#
01h
02h
03h
Access
Get
Get
Get
Name
Data
Data
Data
Type
Array of USINT
Array of USINT
Array of USINT
Description
Input Explicit Message data, bytes 0... 254
Input Explicit Message data, bytes 255... 509
Input Explicit Message data, bytes 510... 511
Note: The interface only creates enough attributes to hold the specified amount of Input Explicit Message data (i.e. if using 400 bytes, the interface creates attributes #1 (255 bytes) and #2 (145 bytes).
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
CIP Object Implementation 4-31
4.12 Parameter Data Output Mapping Object, Class B1h
4.12.1 General Information
Object Description
This object is used to access Output Explicit Message data.
See also...
•
4-20 “Assembly Object, Class 04h”
•
4-27 “I/O Data Output Mapping Object, Class A1h”
•
4-29 “Parameter Data Input Mapping Object, Class B0h”
Supported Services
Class services:
Get Attribute All
Instance services:
Get Attribute Single
Set Attribute Single
4.12.2 Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Value
0001h
4.12.3 Instance Attributes, Instance 01h
Each attribute carries up to 255 bytes of data.
#
01h
02h
03h
Access
Get/Set
Get/Set
Get/Set
Name
Data
Data
Data
Type
Array of USINT
Array of USINT
Array of USINT
Description
Output Explicit Message data, bytes 0... 254
Output Explicit Message data, bytes 255... 509
Output Explicit Message data, bytes 510... 511
Note: The interface only creates enough attributes to hold the specified amount of Output Explicit
Message data (i.e. if using 400 bytes, the interface creates attributes #1 (255 bytes) and #2 (145 bytes).4.9
X-Gateway Interface Addendum: DeviceNet Adapter
Doc: HMSI-27-243, Rev: 2.00
Appendix A
A. Technical Specification
A.1 DeviceNet Interface Details
•
Galvanically isolated bus electronics
•
125kbit, 250kbit and 500kbit operation
•
On-board configuration switches
•
Up to 512 bytes of I/O in each direction
•
Explicit Messaging (up to 512 bytes in each direction)
•
Polled I/O
•
Bit-strobed I/O
•
Change-of-state / Cyclic I/O
A.2 DeviceNet Conformance Note
The DeviceNet Adapter Interface consists of an Anybus-S DeviceNet fieldbus communication module.
The Anybus-S DeviceNet has been pre-compliance tested stand alone by ODVA’s authorized Independent Test Lab, and found to comply with ODVA Conformance Test Software Version A12. However, according to ODVA’s conformance test policy, the final product must still be re-certified as a
complete product even if the Anybus module itself is certified.
For further information, contact HMS or ODVA.
A.3 DeviceNet Connector Pinout
#
1
2
3
4
5
Signal
VCAN_L
SHIELD
CAN_H
V+
X-Gateway Interface Addendum: DeviceNet Adapter
Description
Negative bus power supply
CAN low
Cable shielding
CAN high
Positive bus power supply
1
5
Doc: HMSI-27-243, Rev: 2.00
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