540-6779-Anybus_CompactCom_40_DeviceNet_network guide

540-6779-Anybus_CompactCom_40_DeviceNet_network guide
Network Guide
Anybus CompactCom 40 DeviceNet™
®
Doc.Id. HMSI-27-264
Rev. 1.20
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.anybus.com
Important User Information
This document is intended to provide a good understanding of the functionality offered by DeviceNet™. The document only describes the features that are specific to the Anybus CompactCom 40 DeviceNet. For general information regarding the Anybus CompactCom, consult the Anybus CompactCom design guides.
The reader of this document is expected to be familiar with high level software design, and communication systems in general. The information in this manual should normally be sufficient for implementing a design. However,
if advanced DeviceNet specific functionality is to be used, in-depth knowledge of DeviceNet networking internals
and/or information from the official DeviceNet specifications, may be required. In such cases, the people responsible for the implementation of this product should either obtain the DeviceNet specification to gain sufficient
knowledge or limit their 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.
Anybus CompactCom 40 DeviceNet Network Guide
Rev 1.20
Copyright© HMS Industrial Networks AB
Oct 2015 Doc Id HMSI-27-264
Table of Contents
Table of Contents
Preface
About This Document
Related Documents.................................................................................................................................. 5
Document History ................................................................................................................................... 5
Conventions & Terminology .................................................................................................................. 6
Support....................................................................................................................................................... 6
Chapter 1
About the Anybus CompactCom 40 DeviceNet
General....................................................................................................................................................... 7
Features ...................................................................................................................................................... 7
Chapter 2
Basic Operation
General Information ................................................................................................................................ 8
Software Requirements ..................................................................................................................... 8
Electronic Data Sheet (EDS) .......................................................................................................... 8
Device Customization.............................................................................................................................. 9
Modular Device Functionality .......................................................................................................... 9
Quick Connect ............................................................................................................................... 10
Communication Settings ....................................................................................................................... 11
Setting Baud Rate.......................................................................................................................... 12
Setting Node Address .................................................................................................................... 12
Diagnostics .............................................................................................................................................. 13
Data Exchange........................................................................................................................................ 14
Application Data (ADIs) ............................................................................................................. 14
Process Data .................................................................................................................................. 14
Translation of Data Types ............................................................................................................. 15
Chapter 3
CIP Objects
General Information .............................................................................................................................. 16
Identity Object (01h).............................................................................................................................. 17
Message Router (02h) ............................................................................................................................ 20
DeviceNet Object (03h) ........................................................................................................................ 21
Assembly Object (04h) .......................................................................................................................... 23
Connection Object (05h)....................................................................................................................... 25
Parameter Object (0Fh)......................................................................................................................... 30
Acknowledge Handler Object (2Bh) ................................................................................................... 33
Base Energy Object (4Eh) .................................................................................................................... 34
Power Management Object (53h) ........................................................................................................ 36
ABCC ADI Object (A2h) ..................................................................................................................... 38
4
Chapter 4
Anybus Module Objects
General Information .............................................................................................................................. 40
Anybus Object (01h).............................................................................................................................. 41
Diagnostic Object (02h) ........................................................................................................................ 43
Network Object (03h)............................................................................................................................ 44
Network Configuration Object (04h).................................................................................................. 45
Anybus File System Interface Object (0Ah) ...................................................................................... 48
Chapter 5
Host Application Objects
General Information .............................................................................................................................. 49
CIP Identity Host Object (EDh) ......................................................................................................... 50
SYNC Object (EEh) .............................................................................................................................. 51
DeviceNet Host Object (FCh) ............................................................................................................. 52
Appendix A Categorization of Functionality
Basic.......................................................................................................................................................... 56
Extended.................................................................................................................................................. 56
Appendix B Implementation Details
DeviceNet Implementation .................................................................................................................. 57
SUP-Bit Definition................................................................................................................................. 58
Anybus State Machine ........................................................................................................................... 58
Appendix C CIP Request Forwarding
Appendix D Technical Specification
Front View............................................................................................................................................... 61
Protective Earth (PE) Requirements................................................................................................... 62
Power Supplies........................................................................................................................................ 62
Power Consumption .............................................................................................................................. 62
Environmental Specification ................................................................................................................ 63
EMC Compliance ................................................................................................................................... 63
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Preface
P. About This Document
For more information, documentation etc., please visit the HMS website, ‘www.anybus.com’.
P.1 Related Documents
Document
Anybus CompactCom 40 Software Design Guide
Anybus CompactCom M40 Hardware Design Guide
Anybus CompactCom B40 Design Guide
Anybus CompactCom Driver User Manual
DeviceNet Specification
Common Industrial Protocol (CIP) specification
Author
HMS
HMS
HMS
HMS
ODVA
ODVA
P.2 Document History
Summary of Recent Changes (1.11... 1.20)
Change
Removed section 1.3 (information already in Technical Specification appendix)
Extended and advanced categories joined to one, extended
Updated description on how to assign a node address
Changed device address to node address
Added description on how to set baud rate
Page(s)
12
12
Revision List
Revision
1.00
1.10
1.11
1.20
Date
2014-09-15
2014-10-02
2015-01-30
2015-10-23
Author(s)
KeL
KeL
KaD
KeL
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Chapter(s)
All
1, 4, D
2
Description
First official version
Misc. updates
Minor update
Minor update
Doc.Id. HMSI-27-264
About This Document 6
P.3 Conventions & Terminology
The following conventions are used throughout this manual:
•
Numbered lists provide sequential steps
•
Bulleted lists provide information, not procedural steps
•
The terms ‘Anybus’ or ‘module’ refers to the Anybus CompactCom module.
•
The terms ‘host’ or ‘host application’ refers to the device that hosts the Anybus module.
•
Hexadecimal values are written in the format NNNNh or 0xNNNN, where NNNN is the hexadecimal value.
•
A byte always consists of 8 bits.
•
The terms ‘basic’ and ‘extended’ are used to classify objects, instances and attributes. Please refer
to “Categorization of Functionality” on page 56 for more information.
P.4 Support
For general contact information and support, please refer to the contact and support pages at
www.anybus.com.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Chapter 1
1. About the Anybus CompactCom 40 DeviceNet
1.1 General
The Anybus CompactCom 40 DeviceNet communication module provides instant DeviceNet connectivity via the patented Anybus CompactCom host interface. Any device that supports this standard can
take advantage of the features offered by the module, allowing seamless network integration regardless
of network type.
The modular approach of the Anybus CompactCom platform allows the CIP-object implementation to
be extended to fit specific application requirements. Furthermore, the Identity Object can be customized, allowing the end product to appear as a vendor-specific implementation rather than a generic Anybus module.
This product conforms to all aspects of the host interface for Active modules defined in the Anybus
CompactCom 40 Hardware- and Software Design Guides, making it fully interchangeable with any other device following that specification. Generally, no additional network related software support is needed, however in order to be able to take full advantage of advanced network specific functionality, a
certain degree of dedicated software support may be necessary.
1.2 Features
•
Pluggable 5.08 DeviceNet connector
•
Brick version
•
CIP Parameter Object Support
•
Explicit messaging
•
UCMM Capable
•
Bit-strobed I/O
•
Change-of-state / Cyclic I/O
•
Polled I/O
•
Expansion possibilities via CIP forwarding
•
Customizable Identity object
•
Automatic Baud Rate Detection
•
Modular Device functionality
•
Quick Connect supported
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Chapter 2
2. Basic Operation
2.1 General Information
2.1.1 Software Requirements
Generally, no additional network support code needs to be written in order to support the Anybus CompactCom 40 DeviceNet. However, due to the nature of the DeviceNet networking system, certain requirements and facts must be taken into account:
•
Certain functionality in the module requires that the command ‘Get_Instance_Number_By_Order’ (Application Data Object, FEh) is implemented in the host application.
•
Up to 5 diagnostic instances (See “Diagnostic Object (02h)” on page 43) can be created by the
host application during normal conditions. An additional 6th instance may be created in event of
a major fault.
For in-depth information regarding the Anybus CompactCom software interface, consult the general
Anybus CompactCom 40 Software Design Guide.
See also...
•
“Diagnostic Object (02h)” on page 43 (Anybus Module Object)
•
Anybus CompactCom 40 Software Design Guide, ‘Application Data Object (FEh)’
2.1.2 Electronic Data Sheet (EDS)
Since the module implements the Parameter Object, it is possible for configuration tools such as RSNetWorx from Rockwell, to automatically generate a suitable EDS-file.
Note that this functionality requires that the command ‘Get_Instance_Number_By_Order’ (Application Data Object, FEh) has been implemented in the host application.
See also...
•
“Device Customization” on page 9
•
“Parameter Object (0Fh)” on page 30 (CIP-object)
•
Anybus CompactCom 40 Software Design Guide, ‘Application Data Object (FEh)’
IMPORTANT: To comply with CIP-specification requirements, custom EDS-implementations require a new Vendor
ID and/or Product Code.¨
To obtain a Vendor ID, contact the ODVA.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Basic Operation 9
2.2 Device Customization
By default, the module supports the generic CIP-profile with the following identity settings:
•
Vendor ID:
005Ah (HMS Industrial Networks AB)
•
Device Type:
002Bh (Generic Device)
•
Product Code:
003Fh (Anybus CompactCom 40 DeviceNet(TM))
•
Product Name:
‘CompactCom 40 DeviceNet(TM)’
It is possible to customize the identity of the module by implementing the DeviceNet Host Object. Furthermore, it is possible to re-route requests to unimplemented CIP-objects to the host application, thus
enabling support for other profiles etc.
To support a specific profile, perform the following steps:
•
Set up the identity settings in the DeviceNet Host Object according to profile requirements.
•
Set up the Assembly Instance Numbers according to profile requirements.
•
Enable routing of CIP-messages to the host application in the DeviceNet Host Object.
•
Implement the required CIP-objects in the host application.
See also...
•
“Identity Object (01h)” on page 17 (CIP-object)
•
“DeviceNet Host Object (FCh)” on page 52 (Host Application Object)
•
“CIP Request Forwarding” on page 59
IMPORTANT: According to the CIP specification, the combination of Vendor ID and serial number must be unique.
It is not permitted to use a custom serial number in combination with the HMS Vendor ID (005Ah), nor is it permitted
to choose Vendor ID arbitrarily. Failure to comply to this requirement will induce interoperability problems and/or other
unwanted side effects. HMS approves use of the HMS Vendor ID (005Ah), in combination with the default serial number, under the condition that the implementation requires no deviations from the standard EDS-file.
To obtain a Vendor ID, contact the ODVA.
2.2.1 Modular Device Functionality
Modular devices consist of a backplane with a certain number of “slots”. The first slot is occupied by
the “coupler” which contains the Anybus CompactCom module. All other slots may be empty or occupied by modules. The Anybus CompactCom 40 DeviceNet module is configurable as a modular slave.
When mapping ADIs to process data, the application shall map the process data of each module in slot
order.
A list of modules in a Modular Device is available to the DeviceNet network master by a request to the
CIP Identity object.
See also ...
•
“Modular device Object (ECh)” (see Anybus CompactCom 40 Software Design Guide)
•
“Identity Object (01h)” on page 17 (CIP object)
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Basic Operation 10
2.2.2 Quick Connect
The module supports the Quick Connect functionality. The functionality is disabled by default and can
be enabled in the DeviceNet Host Object. Enabling the functionality in the DeviceNet Host Object, will
make it possible to enable/disable the use of it in the DeviceNet object (CIP) or the Network Configuration Object.
The module itself has a connection time down to 100 ms when Quick Connect is enabled. The actual
connection time to the network will depend on the performance of the application, response time, and
amount of process data to be mapped.
See also ...
•
“DeviceNet Host Object (FCh)” on page 52
•
“DeviceNet Object (03h)” on page 21 (CIP object)
•
“Network Configuration Object (04h)” on page 45
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Basic Operation 11
2.3 Communication Settings
As with other Anybus CompactCom products, network related communication settings are grouped in
the Network Configuration Object (04h)
In this case, this includes...
•
Baud rate
See also...
- “Setting Baud Rate” on page 12
•
Node Address (MAC ID)
See also...
- “Setting Node Address” on page 12
•
QuickConnect
See also...
- “Instance Attributes (Instance #3, ‘QuickConnect’)” on page 47
The parameters in the Network Configuration Object (04h) are available from the network through the
Identity Object (CIP-object). If the parameters are set through switches from the application during setup, the parameters cannot be changed from the network, but still be read.
See also...
•
“Identity Object (01h)” on page 17 (CIP-object)
•
“DeviceNet Object (03h)” on page 21 (CIP-object)
•
“Network Configuration Object (04h)” on page 45 (Anybus Module Object)
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Basic Operation 12
2.3.1 Setting Baud Rate
If automatic baud rate detection is disabled, the baud rate can be set according to the methods in the
table below.
Method
Baud rate set only
from network
Baud rate set only
from application
Node address set from
network or from application
Actions Required to be Performed by Host
Application
• Set attribute #5 in the Network Configuration Object (04h), Instance #2 to 04h or
larger.
• Set attribute #10 in the DeviceNet Host
Object (FCh) to TRUE.
• Set attribute #10 in the DeviceNet Host
Object (FCh) to FALSE.
• Set attribute #5 in the Network Configuration Object (04h), Instance #2 to any value
between 00h - 03h
• Each time the host application changes the
value, the new value shall be written to attribute #5 in the Network Configuration Object
(04h), Instance #2.
• Set attribute #5 in the Network Configuration Object (04h), Instance #2.
• Each time the host application changes the
value, the new value shall be written to attribute #5 in the Network Configuration Object
(04h), Instance #2.
• Set attribute #10 in the DeviceNet Object
(FCh) to TRUE.
Comments
An invalid value (04h or larger) is set by the
host application. The module will go online
using the latest configured baud rate. When a
value is set from the network, the value will be
set in attribute #5 in the Network Configuration
Object (04h), Instance #2. The new baud rate
will valid after the next reset.
If an invalid value is set by the host application
(04h or larger), the module will enter the “Communication faulted state” at network initialization.
If, after network initialization, the configured and
the last value set by the host application differ, a
minor fault will be indicated. Attributes #7 and
#9 in the CIP DeviceNet Object (03h) will be
updated, see page 21.
If an invalid value is set by the host application,
the module will return to the latest used.
When a value is set from the network, the value
will be set in attribute #5 in the Network Configuration Object (04h), Instance #2. The new
baud rate will valid after the next reset.
If, after network initialization, the configured and
the last value set by the host application differ, a
minor fault will be indicated. Attributes #7 and
#9 in the CIP DeviceNet Object (03h) will be
updated, see page 21.
2.3.2 Setting Node Address
There are three different methods to set the node address (the MAC ID) of the module.
Actions Required to be Performed by Host
Application
Node address set only • Set attribute #5 in the Network Configurafrom network
tion Object (04h), Instance #1 to 64 or
larger.
• Set attribute #9 in the DeviceNet Host
Object (FCh) to TRUE.
Method
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Comments
An invalid node address (64 - 255) is set by the
host application. The module will go online
using the latest configured address. When a
node address is set from the network, the
address will be set in attribute #5 in the Network
Configuration Object (04h), Instance #1. The
module deletes all Connection objects and
restarts the network access process.
Doc.Id. HMSI-27-264
Basic Operation 13
Actions Required to be Performed by Host
Application
Node address set only • Set attribute #9 in the DeviceNet Host
from application
Object (FCh) to FALSE.
• Set attribute #5 in the Network Configuration Object (04h), Instance #1 to any value
between 0 - 63.
• Each time the host application changes the
value, the new value shall be written to attribute #5 in the Network Configuration Object
(04h), Instance #1.
Node address set from • Set attribute #5 in the Network Configuranetwork or from applition Object (04h), Instance #1.
cation
• Each time the host application changes the
value, the new value shall be written to attribute #5 in the Network Configuration Object
(04h), Instance #1.
• Set attribute #9 in the DeviceNet Object
(FCh) to TRUE.
Method
Comments
If an invalid value is set by the host application
(64 - 255), the module will enter the “Communication faulted state” at network initialization.
If, after network initialization, the configured and
the last value set by the host application differ, a
minor fault will be indicated. Attributes #6 and
#8 in the CIP DeviceNet Object (03h) will be
updated, see page 21.
If an invalid value is set by the host application,
the module will return to the latest used.
When a node address is set from the network,
the address will be set in attribute #5 in the Network Configuration Object (04h), Instance #1.
The module deletes all Connection objects and
restarts the network access process.
If, after network initialization, the configured and
the last value set by the host application differ, a
minor fault will be indicated. Attributes #6 and
#8 in the CIP DeviceNet Object (03h) will be
updated, see page 21.
See also ...
•
“DeviceNet Host Object (FCh)” on page 52 (Host Application Object)
•
“Network Configuration Object (04h)” on page 45 (Anybus Module Object)
2.4 Diagnostics
The severity value of all pending events are combined (using logical OR) and copied to the corresponding bits in the ‘Status’-attribute of the CIP Identity Object.
See also...
•
“Identity Object (01h)” on page 17 (CIP-object)
•
“Diagnostic Object (02h)” on page 43 (Anybus Module Object)
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Basic Operation 14
2.5 Data Exchange
2.5.1 Application Data (ADIs)
ADIs are represented on DeviceNet through the ABCC ADI Object (CIP-object). Each instance within
this objects corresponds directly to an instance in the Application Data Object on the host application
side.
See also...
•
“Parameter Object (0Fh)” on page 30 (CIP-object)
•
“ABCC ADI Object (A2h)” on page 38 (CIP-object)
2.5.2 Process Data
Process Data is represented on DeviceNet through dedicated instances in the Assembly Object. Note
that each ADI element is mapped on a byte-boundary, i.e. each BOOL occupies one byte.
See also...
•
“Assembly Object (04h)” on page 23 (CIP-object)
•
“Connection Object (05h)” on page 25 (CIP-object)
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Basic Operation 15
2.5.3 Translation of Data Types
The Anybus data types are translated to CIP-standard and vice versa according to the table below.
Anybus Data Typea
BOOL
ENUM
SINT8
UINT8
SINT16
UINT16
SINT32
UINT32
FLOAT
CHAR
CIP Data Type
Comments
BOOL
USINT
SINT
USINT
INT
UINT
DINT
UDINT
REAL
SHORT_STRING
Each ADI element of this type occupies one byte.
SINT64
UINT64
BITS8
BITS16
BITS32
OCTET
BITS1-7
PAD0-8
PAD9-16
LINT
ULINT
BYTE
WORD
DWORD
USINT
BYTE
BYTE
BYTE
Each ADI element of this type occupies two bytes.
Each ADI element of this type occupies four bytes.
SHORT_STRING consists of a single-byte length field (which in this case
represents the number of ADI elements) followed by the actual character data
(in this case the actual ADI elements). This means that a 10-character string
occupies 11 bytes.
Each ADI element of this type occupies eight bytes.
Each ADI element of this type occupies one byte.
Each ADI element of this type occupies two bytes.
Each ADI element of this type occupies four bytes.
Each ADI element of this type occupies one byte.
BIt fields of size 1 - 7
BIt fields of size 0 - 8 used for padding
BIt fields of size 9 - 16 used for padding
a. For more information about the Anybus data types, please consult the Anybus CompactCom 40 Software Design
Guide.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Chapter 3
3. CIP Objects
3.1 General Information
This chapter specifies the CIP-objects implementation in the module. The objects described herein can
be accessed from the network, but not by the host application.
Mandatory Objects:
•
“Identity Object (01h)” on page 17
•
“Message Router (02h)” on page 20
•
“DeviceNet Object (03h)” on page 21
•
“Assembly Object (04h)” on page 23
•
“Connection Object (05h)” on page 25
•
“Parameter Object (0Fh)” on page 30
•
“Acknowledge Handler Object (2Bh)” on page 33
CIP Energy Objects:
•
“Base Energy Object (4Eh)” on page 34
•
“Power Management Object (53h)” on page 36
Vendor Specific Objects:
•
“ABCC ADI Object (A2h)” on page 38
It is possible to implement additional CIP-objects in the host application using the CIP forwarding functionality, see “DeviceNet Host Object (FCh)” on page 52 and “CIP Request Forwarding” on page 59.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 17
3.2 Identity Object (01h)
Category
Extended
Object Description
The Identity Object provides identification of and general information about the module.
The object supports multiple instances. Instance 1, which is the only mandatory instance, describes the
whole product. It is used by applications to determine what nodes are on the network and to match an
EDS file with a product on the network. The other (optional) instances describe different parts of the
product e.g. the software.
If modular device functionality is enabled, a list of the modules in the slots can be retrieved and made
available to the network master by sending a get request to class attribute 100.
Instance attributes 1 - 4 and 6 - 7 can be customized by implementing the DeviceNet Host Object.
Additional identity instances can be registered by implementing the CIP Identity Host Object (host application object).
See also ....
•
“DeviceNet Host Object (FCh)” on page 52
•
“CIP Identity Host Object (EDh)” on page 50
Supported Services
Class
Get Attribute Single
Get Attribute All
Instance:
Get Attribute Single
Get Attribute All
Set Attribute Single
Reset
Class Attributes
#
1
2
3
100
Access
Get
Get
Get
Get
Name
Revision
Max instance
Number of instances
Module ID List
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Type
UINT
UINT
UINT
Array of UINT32
Comments
0001h
Maximum instance number
Number of instances
List of Module IDs supported in the application if Modular Device functionality is enabled.
See “Modular Device Functionality” on page 9 for
more information,
Doc.Id. HMSI-27-264
CIP Objects 18
Instance #1 Attributes
Extended
#
1
Access
Get
Name
Vendor ID
Type
UINT
005Ah (HMS Industrial Networks ABa)
2
Get
Device Type
UINT
002Bh (Generic Devicea)
3
Get
Product Code
UINT
003Fh (Anybus CompactCom 40 DeviceNet(TM)a)
4
Get
Revision
Major and minor firmware revisiona
5
6
Get
Get
Status
Serial Number
Struct of:
{USINT, USINT}
WORD
UDINT
7
Get
Product Name
11 Get/Set
12 Get
Comments
See “Device Status” on page 19
Assigned by HMSa
SHORT_STRING “CompactCom 40 DeviceNet(TM)” (Name of producta)
Active language Struct of:
Set requests sent to this instance are forwarded to the application
{USINT,
using the Set_Lang_Request service of the Anybus Application
USINT,
Object. The host application shall acknowledge or not acknowledge
USINT}
the set request. The module is then responsible for updating the language settings in the Anybus Object accordingly.
Supported
Array of struct of: List of languages supported by the host application. This list is read
Language List {USINT,
from the Application Object and translated to CIP standard.
USINT,
USINT}
a. Can be customized by implementing the DeviceNet Host Object, see “DeviceNet Host Object (FCh)” on page 52
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 19
Device Status
bit(s)
0
1
2
3
4... 7
8
9
Name
Module Owned
(reserved, set to 0)
Configureda
(reserved, set to 0)
Extended Device Status:
Value: Meaning:
0010b Faulted I/O Connection
0011b No I/O connection established
0101b Major fault
0110b Connection in Run mode
0111b Connection in Idle mode
(other) (reserved)
Set for minor recoverable faults
Set for minor unrecoverable faults
10
Set for major recoverable faults
11
Set for major unrecoverable faults
(reserved, set to 0)
12... 15
Priority (higher number means higher priority):
3
0
4
1
2
These bits represent a combination of network specific
faults (see CIP specifications) and faults generated by the
module (see “Diagnostic Object (02h)” on page 43)
a. 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 (FFh) is set.
Service Details: Reset Service
The module forwards reset requests from the network to the host application. For more information
about network reset handling, consult the general Anybus CompactCom 40 Design Guide.
There are two types of network reset requests on DeviceNet:
•
Type 0: ‘Power Cycling Reset’
This service emulates a power cycling of the module, and corresponds to Anybus reset type 0
(Power-on reset). For further information, consult the general Anybus CompactCom 40 Software Design Guide.
•
Type 1: ‘Out of box reset’
This service sets a “out of box” configuration and performs a reset, and corresponds to Anybus
reset type 2 (Power-on reset + factory default). For further information, consult the general Anybus CompactCom 40 Software Design Guide.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 20
3.3 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 Anybus CompactCom 40 module it is issued internally to direct object requests.
Supported Services
Class
-
Instance:
-
Class Attributes
-
Instance Attributes
-
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 21
3.4 DeviceNet Object (03h)
Category
Extended
Object Description
This object provides means for configuring the DeviceNet interface of the module.
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Allocate Master/Slave Connection Set (4Bh)
Release Master/Slave Connection Set (4Ch)
Class Attributes
#
1
Name
Revision
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Access
Get
Type
UINT
Comments
0002h
Doc.Id. HMSI-27-264
CIP Objects 22
Instance #1 Attributes
Extended
#
1
Name
MAC ID
Access
Get/Set
Type
USINT
Comments
Currently used node address (0 - 63)
2
Baud Ratea b
Get/Set
USINT
3
BOIc
Get/Set
BOOL
4
5
Bus-Off Counter
Allocation Information
Get/Set
Get
Value:Baud rate:
0 125 kbps
1 250 kbps
2 500 kbps
Defines CAN controller action in case of a Bus-Off interrupt
Value: Meaning
False The CAN controller is reset, but will not try to
restart the communication on the bus
True The CAN controller is reset and will try to restart
communication on the bus
00h
a
6
MAC ID Switch changedd
Get
USINT
Struct of:
BYTE
USINT
BOOL
7
Baud rate Switch changede
Get
BOOL
8
MAC ID Switch valued
Get
USINT
Allocation choice byte
MAC ID (node address) of master
Indicates if the MAC ID (node address) has changed since
startup
Value: Meaning
True Changed
False No change
Indicates if the baud rate has changed since startup
Value:Meaning
True Changed
False No change
Actual value of node address switches
9
Baud rate Switch value
Get
USINT
Actual value of baud rate switches
10
Quick Connectf
Get/Set
Bool
Get/Set
BOOL
Enables/Disables the Quick Connect feature. Disabled by
default
Value: Meaning
True Enable
False Disable
Value: Meaning
True Disable auto baud
False Enable auto baud
This setting is stored in NV memory.
e
100 Disable auto baud
a. Set access right for attributes 1 and 2 are conditional. For further information, see “Communication Settings” on
page 11.
b. Setting this attribute will also affect attribute #100 (Disable auto baud).
c. A Bus-Off Interrupt is generated from the underlying CAN layer. It indicates that no communication is possible on
the bus, e.g. due to a short circuit between lines.
d. Implementation of attributes 6 and 8 is conditional. The attributes are implemented if the node address (MAC ID)
is set from the Network Configuration Object at startup.
e.Implementation of attributes 7 and 9 is conditional. The attributes are implemnented if the baud rate is set from the
Network Configuration Object at startup.
f. Enabled if attribute #13 (‘Enable Quick Connect”) in the DeviceNet Host Object (FCh) is set to true, see “DeviceNet Host Object (FCh)” on page 52.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 23
3.5 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 in the vendor specific range.
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...
•
“Process Data” on page 14
•
“DeviceNet Host Object (FCh)” on page 52
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Class Attributes
#
1
2
Name
Revision
Max Instance
Access
Get
Get
Type
UINT
UINT
Comments
0002h
Highest instance number
Instance 64h Attributes (Producing Instance)
Extended
The instance number for this instance can be changed by implementing the corresponding attribute in
the DeviceNet Host Object.
#
3
Name
Produced Data
Access
Get
Type
Array of BYTE
4
Size
Get
UINT
Comments
Process data, written from the application and sent to the
CIP network. Corresponds to the Write Process data.
Number of bytes in attribute #3
See also...
•
“Data Exchange” on page 14
•
“DeviceNet Host Object (FCh)” on page 52
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 24
Instance 96h Attributes (Consuming Instance)
Extended
The instance number for this instance can be changed by implementing the corresponding attribute in
the DeviceNet Host Object.
#
3
Name
Consumed Data
Access
Get/Set
Type
Array of BYTE
4
Size
Get
UINT
Comments
Process data, received from the CIP network master and
read by the application. Corresponds to the Read Process
data.
Number of bytes in attribute #3
See also...
•
“Data Exchange” on page 14
•
“DeviceNet Host Object (FCh)” on page 52
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 25
3.6 Connection Object (05h)
Category
Extended
Object Description
This object allocates and manages the internal resources associated with both I/O and Explicit Messaging Connections. It is used to model the communication specific characteristics of an application-to-application(s) relationship.
A specific Connection Object Instance manages the communication specific aspects related to an endpoint.
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Class Attributes
#
1
Name
Revision
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Access
Get
Type
UINT
Comments
0001h
Doc.Id. HMSI-27-264
CIP Objects 26
Instances #1, #10... #14 (Explicit messaging)
Extended
#
1
Name
State
Access
Get
Type
USINT
2
3
4
5
6
Instance type
Transport Class trigger
Produced connection ID
Consumed connection ID
Initial Comm Characteristics
Get
Get
Get
Get
Get
USINT
BYTE
UINT
UINT
BYTE
7
8
9
12
Produced Connection Size
Consumed Connection Size
Expected Packet Rate
Watchdog timeout action
Get
Get
Get/Set
Get/Set
UINT
UINT
UINT
USINT
13
14
15
16
17
18
Produced Connection path length
Produced Connection path
Consumed Connection path length
Consumed Connection path
Production Inhibit Time
Connection Timeout Multiplier
Get
Get
Get
Get
Get
Get/Set
UINT
EPATH
UINT
EPATH
UINT
UINT
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Comments
Value:State:
0 Non existent
1 Configuring
2 Waiting for connection ID
3 Established
4 Time out
5 Deferred Delete
0000h (Explicit messaging connection)
83h (Server, Transport class 3)
CAN ID for transmission
CAN ID for reception
The message group over which the communication
occurs:
Value:Message Group
21 Instance #1
33 Instances #10... #14
512 bytes
512 bytes
2500ms (timing associated with this connection)
Value:Action:
0001h Auto delete (default)
0003h Deferred delete
0000h (No connection path)
0000h (No connection path)
0000h
Specifies the multiplier applied to the expected
packet rate value to derive the value for the Inactivity/Watchdog Timer.
Value:Meaning:
0: x4 (default)
1: x8
2: x16
3: x32
4: x64
5 x128
6: x256
7: x512
8-255: (reserved)
Doc.Id. HMSI-27-264
CIP Objects 27
Instance #2 (Poll or “COS/Cyclic consuming”)
Extended
#
1
Name
State
Access
Get
Type
USINT
2
3
Instance type
Transport Class trigger
Get
Get
USINT
BYTE
4
Produced connection ID
Get
UINT
5
6
Consumed connection ID
Initial Comm Characteristics
Get
Get
UINT
BYTE
7
Produced Connection Size
Get
UINT
8
9
12
13
Consumed Connection Size
Expected Packet Rate
Watchdog timeout action
Produced Connection path length
Get
Get/Set
Get
Get
UINT
UINT
USINT
UINT
14 Produced Connection path
Get
EPATH
15 Consumed Connection path length
16 Consumed Connection path
Get
Get
UINT
EPATH
17 Production Inhibit Time
18 Connection Timeout Multiplier
Get
Get/Set
UINT
UINT
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Comments
Value:State:
0 Non existent
1 Configuring
2 Waiting for connection ID
3 Established
4 Time out
0001h (I/O Connection)
Value:Meaning:
82h Server, Polled, Class 2
80h Server, COS/Cyclic, Class 0, No Ack.
82h Server, COS/Cyclic, Class 2, Ack.
Value:Meaning:
FFFFh Not consuming (COS/Cyclic)
Other CAN ID for transmission
CAN ID for reception (Polled)
Value:Meaning:
01h Polled
- Produces over message group 1
- Consumes over message group 2
F1h COS/Cyclic, No Ack
- Consumes only over message group 2
01h COS/Cyclic, Ack
- Produces over message group 1 (Ack)
- Consumes over message group 2
Value:Meaning:
0000h COS/Cyclic
Other Size of Write Process Data (Polled)
Size of Read Process Data
0000h (Transition to the timed out state)
0000h (COS/Cyclic)
0007h (Polled)
No value (COS/Cyclic)
20 04 25 nn nn 30 03h (Polled, nn = producing
instance number in assembly object)
0007h
20 04 25 nn nn 30 03h (nn = consuming instance
number in assembly object)
0000h
Specifies the multiplier applied to the expected
packet rate value to derive the value for the Inactivity/
Watchdog Timer.
Value:Meaning:
0: x4 (default)
1: x8
2: x16
3: x32
4: x64
5 x128
6: x256
7: x512
8-255: (reserved)
Doc.Id. HMSI-27-264
CIP Objects 28
Instance #3 (Bit-strobe)
Extended
#
1
Name
State
Access
Get
Type
USINT
2
3
Instance type
Transport Class trigger
Get
Get
USINT
BYTE
4
5
6
Produced connection ID
Consumed connection ID
Initial Comm Characteristics
Get
Get
Get
UINT
UINT
BYTE
7
Produced Connection Size
Get
UINT
8
9
12
13
14
Consumed Connection Size
Expected Packet Rate
Watchdog timeout action
Produced Connection path length
Produced Connection path
Get
Get/Set
Get
Get
Get
UINT
UINT
USINT
UINT
EPATH
15 Consumed Connection path length Get
16 Consumed Connection path
Get
UINT
EPATH
17 Production Inhibit Time
18 Connection Timeout Multiplier
UINT
UINT
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Get
Get/Set
Comments
Value:State:
0 Non existent
1 Configuring
2 Waiting for connection ID
3 Established
4 Time out
0001h (I/O Connection)
82h (Transport class & Trigger Server,
Cyclic, Class 2)
CAN ID for transmission
CAN ID for reception
Produces over message group 1
Consumes over message group 2
Size of produced data on this connection.
Max of: 8 bytes, Mapped Process data
0008h
0000h (Transition to the timed out state)
0007h
20 04 25 nn nn 30 03h (nn = producing instance number
in assembly object)
0007h
20 04 25 nn nn 30 03h (nn = consuming instance number
in assembly object)
0000h
Specifies the multiplier applied to the expected packet
rate value to derive the value for the Inactivity/Watchdog
Timer.
Value:Meaning:
0: x4 (default)
1: x8
2: x16
3: x32
4: x64
5 x128
6: x256
7: x512
8-255: (reserved)
Doc.Id. HMSI-27-264
CIP Objects 29
Instance #4 (COS/Cyclic producing)
Extended
#
1
Name
State
Access
Get
Type
USINT
2
3
Instance type
Transport Class trigger
Get
Get
USINT
BYTE
4
5
Produced connection ID
Consumed connection ID
Get
Get
UINT
UINT
6
Initial Comm Characteristics
Get
BYTE
7
8
9
12
13
14
Produced Connection Size
Consumed Connection Size
Expected Packet Rate
Watchdog timeout action
Produced Connection path length
Produced Connection path
Get
Get
Get/Set
Get
Get
Get
UINT
UINT
UINT
USINT
UINT
EPATH
15 Consumed Connection path length
Get
UINT
16 Consumed Connection path
Get
EPATH
17 Production Inhibit Time
18 Connection Timeout Multiplier
Get/Set
Get/Set
UINT
UINT
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Value
Value:State:
0 Non existent
1 Configuring
2 Waiting for connection ID
3 Established
4 Time out
0001h (I/O Connection)
Value:Meaning:
00h Client, Cyclic, Class 0 (No Ack.)
10h Client, COS, Class 0 (No Ack.)
02h Client, Cyclic, Class 2 (Ack.)
12h Client, COS, Class 2 (Ack.)
CAN ID for transmission
Value:Meaning:
FFFFh Not acknowledged
Other CAN ID for reception (Ack.)
Value:Meaning:
0Fh Producing only over message group 1
(No Ack.)
01h Produces over message group 1
Consumes over message group 2
(Ack.)
Size of produced data on this connection.
0000h (Consumes 0 bytes on this connection)
Timing associated with this connection.
0000h (Transition to the timed out state)
0007h
20 04 25 nn nn 30 03h (nn = producing instance
number in assembly object)
0000h (No ack.)
0005h (Acknowledged)
No value (No ack.)
20 2B 25 01 00h (Acknowledged)
0000h
Specifies the multiplier applied to the expected
packet rate value to derive the value for the Inactivity/Watchdog Timer.
Value:Meaning:
0: x4 (default)
1: x8
2: x16
3: x32
4: x64
5 x128
6: x256
7: x512
8-255: (reserved)
Doc.Id. HMSI-27-264
CIP Objects 30
3.7 Parameter Object (0Fh)
Category
Extended
Object Description
The Parameter Object provides an interface to the Application Data Instances (ADIs) of the module. It
can provide a full description of each parameter, including minimum and maximum values and a text
string describing the parameter.
Each parameter is represented by one instance. Instance numbers start at 1, and are incremented by one,
with no gaps in the list. Due to limitations imposed by the CIP standard, ADIs containing multiple elements (i.e. arrays and structures) cannot be represented through this object. In such cases, default values
will be returned, see “Default Values” on page 32.
Configuration tools, such as RSNetworx, can extract information about the ADIs and present them with
their actual name and range to the user.
Since this process may be somewhat time consuming, especially when using the serial host interface, it
is possible to disable support for this functionality in the DeviceNet Host Object.
See also...
•
“ABCC ADI Object (A2h)” on page 38 (CIP Object)
•
“DeviceNet Host Object (FCh)” on page 52 (Host Application Object)
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Get Attributes All
Get Enum String
Class Attributes
#
1
2
Name
Revision
Max instance
Access
Get
Get
Type
UINT
UINT
8
Parameter class
descriptor
Get
WORD
9
Configuration Assembly Get
instance
UINT
Value
0001h (Revision of the object)
Maximum created instance number = class attribute 3 in
the Application Data Objecta
Default: 0000 0000 0000 01011b
Bit:Contents:
0 Supports parameter instances
1 Supports full attributes
2 Must do non-volatile storage save command
3 Parameters are stored in non-volatile storage
0000h (Configuration assembly not supported)
a. Consult the general Anybus CompactCom 40 Software Design Guide for further information.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 31
Instance Attributes
Extended
#
1
Name
Parameter Value
Access
Get/Set
2
3
Link Path Size
Link Path
Get
Get
Type
Specified in attributes 4, 5 & 6.
USINT
Packed EPATH
4
Descriptor
Get
WORD
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Data type
Data size
Parameter Name String
Units String
Help String
Minimum value
Maximum value
Default value
Scaling Multiplier
Scaling Divisor
Scaling Base
Scaling Offset
Multiplier link
Divisor Link
Base Link
Offset Link
Decimal precision
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
EPATH
USINT
SHORT_STRING
SHORT_STRING
SHORT_STRING
(Data Type)
(Data Type)
(Data Type)
UINT
UINT
UINT
INT
UINT
UINT
UINT
UINT
USINT
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Value
Actual value of parameter
This attribute is read-only if bit 4 of Attribute #4 is true
0007h
21 mm mm 25 nn nn 30 05h
(Path to the object from where this parameter’s value is
retrieved, in this case the ADI Object. “mm mm” is A2 00h
by default, but can be customized using the Anybus DeviceNet Host Object to change the ABCC ADI Class Object
number)
Bit:Contents:
0 Supports Settable Path (N/A)
1 Supports Enumerated Strings
2 Supports Scaling (N/A)
3 Supports Scaling Links (N/A)
4 Read only Parameter
5 Monitor Parameter (N/A)
6 Supports Extended Precision Scaling (N/A)
Data type code
Number of bytes in parameter value
Name of the parameter, truncated to 16 chars
(not supported)
Minimum value of parameter
Maximum value of parameter
Default value of parameter
0001h (not supported)
0000h (not supported)
Doc.Id. HMSI-27-264
CIP Objects 32
Default Values
#
1
2
3
4
5
6
7
8
9
10
11
12
Name
Parameter Value
Link Path Size
Link Path
Descriptor
Data type
Data size
Parameter Name String
Units String
Help String
Minimum value
Maximum value
Default value
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Value
0
0
0010h
C6h
1
(reserved)
“”
“”
N/A
N/A
N/A
Description
Size of link path in bytes.
NULL Path
Read only Parameter
USINT
0
0
0
Doc.Id. HMSI-27-264
CIP Objects 33
3.8 Acknowledge Handler Object (2Bh)
Category
Extended
Object Description
This object notifies the producing application of acknowledge reception, acknowledge timeouts, and
production retry limit.
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Class Attributes
#
1
Name
Revision
Access
Get
Type
UINT
Value
0001h
Instances Attributes (01h)
Extended
#
1
Name
Acknowledge Timer
Access
Get/Set
Type
UINT
2
Retry Limit
Get/Set
USINT
3
Producing Connection Instance
Get
UINT
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Value
16 ms (Time to wait for acknowledge, in ms, before
resending)
01h (number of ack timeouts before retry limit reached
event)
04h (Connection instance, which contains the path of the
producing I/O application object, which will be notified of
Ack Handler events)
Doc.Id. HMSI-27-264
CIP Objects 34
3.9 Base Energy Object (4Eh)
Category
Extended
Object Description
The Base Energy Object acts as an “Energy Supervisor” for CIP Energy implementations. It is responsible for providing a time base for energy values, provides energy mode services, and can provide aggregation services for aggregating energy values up through the various levels of an industrial facility. It also
provides a standard format for reporting energy metering results. The object is energy type independent
and allows energy type specific data and functionality to be integrated into an energy system in a standard
way. The Anybus CompactCom 40 DeviceNet module supports one instance of the Base Energy Object. For instance, an electric power monitor may count metering pulse output transitions of a separate
metering device. The count of such transitions, represented by a Base Energy Object instance, would
reflect the energy consumption measured by the separate metering device. An instance of the Base Energy Object may exist as a stand-alone instance, or it may exist in conjunction with an Electrical and/or
Non-Electrical Energy Object instance1. If an instance of any of these objects is implemented in a device, it must be associated with a Base Energy Object instance in the device.
For this object to be able to access the network, the Energy Reporting Object (E7h) must be implemented in the host application, see the Anybus CompactCom 40 Software Design Guide for more information.
Supported Services
Class:
Get_Attribute_Single
Instance:
Get_Attribute_Single
Class Attributes
#
1
Name
Revision
Access
Get
Type
UINT
Value
0002h (Object revision)
1. These objects are not implemented in the Anybus CompactCom 40 DeviceNet
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 35
Instance Attributes
Extended
#
1
Access
Get
Type
UINT
Get
UINT
Get
UINT
Energy Accu- Get
racy Basis
Get
7a Consumed
Energy Odometer
UINT
ODOMETERb
(Struct of :
UINT,
UINT,
UINT,
UINT,
UINT)
The value of the consumed energy.
Get
8a Generated
Energy Odometer
ODOMETERb
(Struct of :
UINT,
UINT,
UINT,
UINT,
UINT)
Struct of:
UINT (Path size)
padded EPATH
(Path)
The value of the generated energy.
2
3
Name
Energy/
Resource Type
Base Energy
Object Capabilities
Energy Accuracy
4
12 Energy Type
Get
Specific Object
Path
Value/Description
Type of energy managed by this instance
Always 0 (Generic)
Always 0 (Energy measured)
Specifies the accuracy of power and energy metering results, either
in 0.01 percent of reading (default) or 0.01 of other units specified in
attribute #4. If 0, unknown.
Always 0 (Percent of reading)
NULL path
a. Depending on whether the instance reports consumed or generated energy, either attribute #7 or attribute #8 is
required.
b. This struct data type makes it possible to represent very large values, in the range from 0 to 999 999 999 999 999.
It’s defined as a STRUCT of UINTs where each position holds a three-digit value, that, multiplied according to
[x10n, x10n+3, x10n+6, x10n+9, x10n+12], and added to each other will givet the total result.
E.g. if n=0 and the contents in the struct are [123, 234, 345, 456, 567] the resulting value will be 567 456 345 456
567.
The data type is not translated to any Anybus data type, but the value can be read and interpreted from the attributes above.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 36
3.10 Power Management Object (53h)
Category
Extended
Object Description
The Power Management Object provides standardized attributes and services to support the control of
devices into and out of paused or sleep states. The Energy Control Object (F0h) has to be implemented
for this object to gain access to the network.
See also ..
•
Energy Control Object (F0h) (Anybus CompactCom 40 Software Design Guide)
Supported Services
Class:
Get_Attribute_Single
Instance:
Get_Attribute_Single
Power_Management
Set_Pass_Code
Clear_Pass_Code
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 37
Class Attributes
#
1
Name
Revision
Access
Get
Type
UINT
Value
0002h (Object revision)
Instance Attributes
Extended
#
1
2
3
4
5
Name
Power Management Command
Power Management Status
Client Path
Access
Get
Get
Get
Number of
Get
Power Management Modes
Power Manage- Get
ment Nodes
Type
DWORD
Value/Description
Collection of bit fields comprising the most recent power management request.
DWORD
Collection of bit fields providing Power Management status information.
Struct of:
Specifies the EPATH from this instance (server) to its current owner
(client).
UINT (Path Size) Size of path (in words
Padded EPATH
(Path)
UINT
Number of Power Management Mode array entries in attribute 5.
Array of:
Struct of:
USINT
UINT
USINT
UINT
REAL
BOOL
6
Sleeping State Get
Support
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
BOOL
Array of low power modes
Modes (Array of mode structures)
Minimum Pause Units (Specifies the unit of Minimum Pause Time)
Minimum Pause Time
Resume Units (Specifies the unit of Resume Time)
Resume Time (Required time to transition from the paused stated to
the owned state.
Power Level (Power in kW for this mode)
Availability (Specifies whether this mode can be entered given the
current device state)
0 (Sleeping state not supported)
Doc.Id. HMSI-27-264
CIP Objects 38
3.11 ABCC ADI Object (A2h)
Category
Extended
Object Description
This object maps instances in the Application Data Object to DeviceNet. All requests to this object will
be translated into explicit object requests towards the Application Data Object in the host application;
the response is then translated back to CIP-format and sent to the originator of the request.
The object number can be customized using the DeviceNet Host Object (FCh)
See also...
•
Application Data Object (see Anybus CompactCom 40 Software Design Guide)
•
“Parameter Object (0Fh)” on page 30 (CIP Object)
•
“DeviceNet Host Object (FCh)” on page 52
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Class Attributes
#
1
2
Name
Revision
Max Instance
Access
Get
Get
Type
UINT
UINT
Value
Object revision (Current value = 0002h)
3
Number of instances
Get
UINT
Equals attribute #3 in the Application Data Objecta
Equals attribute #4 in the Application Data Objecta
a. Consult the general Anybus CompactCom 40 Software Design Guide for further information.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
CIP Objects 39
Instances Attributes
Extended
Each instance corresponds to an instance within the Application Data Object (for more information,
consult the general Anybus CompactCom 40 Software Design Guide).
#
1
2
3
4
Name
Name
ABCC Data type
No. of elements
Descriptor
Access
Get
Get
Get
Get
Type
SHORT_STRING
USINT
USINT
USINT
5
Valuea
Get/Set
6
Max valuea
Get
Determined by
attribute #2
7
Min valuea
Get
8
Get
Default valuea
Number of subelements Array of
UINT
9
Description
Parameter name (Including length)
Data type of instance value
Number of elements of the specified data type
Bit field describing the access rights for this instance
Bit:Meaning:
0: Set = Read access
1: Set = Write access
2: Not set (reserved)
3: Set = Write process data mapping possible
4: Set = Read process data mapping possible
Instance value
The maximum permitted parameter value.
The minimum permitted parameter value.
The default parameter value.
N/A
Each element defines the number of subelements of the
corresponding element of the instance value for structures and variables.
The number of subelements may only differ from 1 if the
corresponding element is of ABCC data type CHAR or
OCTET:
a. Converted to/from CIP standard by the module
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Chapter 4
4. Anybus Module Objects
4.1 General Information
This chapter specifies the Anybus Module Object implementation and how they correspond to the functionality in the Anybus CompactCom 40 DeviceNet.
The following Anybus Module Objects are implemented:
•
“Anybus Object (01h)” on page 41
•
“Diagnostic Object (02h)” on page 43
•
“Network Object (03h)” on page 44
•
“Network Configuration Object (04h)” on page 45
•
“Anybus File System Interface Object (0Ah)” on page 48
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Anybus Module Objects 41
4.2 Anybus Object (01h)
Category
Basic
Object Description
This object groups common Anybus information, and is described thoroughly in the general Anybus
CompactCom 40 Software Design Guide.
Supported Commands
Object:
Get_Attribute
Instance:
Get_Attribute
Set_Attribute
Get_Enum_String
Object Attributes (Instance #0)
#
1
2
3
4
Name
Name
Revision
Number of instances
Highest instance no.
Access
Get
Get
Get
Get
Data Type
Array of CHAR
UINT8
UINT16
UINT16
Value
“Anybus”
04h
0001h
0001h
Instance Attributes (Instance #1)
Basic
#
1
2
Name
Module type
Firmware version
Access
Get
Get
3
4
Serial number
Application watchdog
timeout
Setup complete
Exception Code
(reserved)
Error counters
Get
Get/Set
Type
UINT16
struct of:
UINT8 Major
UINT8 Minor
UINT8 Build
UINT32
UINT16
Get/Set
Get
BOOL
ENUM
Get
struct of:
UINT16 DC
UINT16 DR
UINT16 SE
ENUM
UINT16
UINT16
5
6
7
8
9 Language
10 Provider ID
11 Provide specific info
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Get/Set
Get
Get/Set
Value
0403h (Anybus CompactCom 40)
(see Anybus CompactCom 40 Software Design Guide)
Doc.Id. HMSI-27-264
Anybus Module Objects 42
# Name
12 LED colors
Access
Get
13
14
15
16
17
18
LED status
(reserved)
Get
Virtual attributes
Black list/White list
Get/Set
Get/Set
19 Network Time
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Get
Type
struct of:
UINT8(LED1A)
UINT8(LED1B)
UINT8(LED2A)
UINT8(LED2B)
UINT8
Value
Value:Color:
01h Green
02h Red
01h Green
02h Red
(see Anybus CompactCom 40 Software Design Guide)
Array of UINT
struct of
UINT8 Infobits
UINT8 ListLen
UINT16 Prot#1
UINT16 Prot#2
...
UINT16 Prot#n
UINT64
0 (The network does not support network time)
Doc.Id. HMSI-27-264
Anybus Module Objects 43
4.3 Diagnostic Object (02h)
Category
Basic
Object Description
This object provides a standardized way of handling host application events & diagnostics, and is thoroughly described in the general Anybus CompactCom 40 Software Design Guide.
Supported Commands
Object:
Get_Attribute
Create
Delete
Instance:
Get_Attribute
Object Attributes (Instance #0)
#
1
2
3
4
11
12
Name
Name
Revision
Number of instances
Highest instance no.
Max no. of instances
Supported functionality
Access
Get
Get
Get
Get
Get
Get
Data Type
Array of CHAR
UINT8
UINT16
UINT16
UINT16
BITS32
Value
‘Diagnostic’
01h
See general Anybus CompactCom 40 Software Design Guide
5+1 (One instance is reserved for major events)
0 (Latching events are not supported)
Instance Attributes (Instance #1)
Basic
#
1
2
Name
Severity
Event Code
Access
Get
Get
Type
UINT8
UINT8
Value
See general Anybus CompactCom 40 Software Design Guide
In the Anybus CompactCom 40 DeviceNet, the severity level of all instances are logically OR:ed together and represented on the network through the CIP Identity Object. The Event Code cannot be represented on the network and is thus ignored by the module.
See also...
•
“Diagnostics” on page 13
•
“Identity Object (01h)” on page 17 (CIP-object)
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Anybus Module Objects 44
4.4 Network Object (03h)
Category
Basic
Object Description
For more information regarding this object, consult the general Anybus CompactCom 40 Software Design Guide.
Supported Commands
Object:
Get_Attribute
Instance:
Get_Attribute
Set_Attribute
Get_Enum_String
Map_ADI_Write_Area
Map_ADI_Read_Area
Object Attributes (Instance #0)
#
1
2
3
4
Name
Name
Revision
Number of instances
Highest instance no.
Access
Get
Get
Get
Get
Data Type
Array of CHAR
UINT8
UINT16
UINT16
Value
“Network”
02h
0001h
0001h
Instance Attributes (Instance #1)
Basic
#
1
2
3
4
5
Name
Network type
Network type string
Data format
Parameter data support
Write process data size
Access
Get
Get
Get
Get
Get
6
Read process data size Get
UINT16
7
Exception information
UINT8
Get
Type
UINT16
Array of CHAR
ENUM
BOOL
UINT16
Value
0025h
‘DeviceNet(TM)’
00h (LSB first)
True
Current write process data size (in bytes)
Updated on every successful Map_ADI_Write_Areaa
Current read process data size (in bytes)
Updated on every successful Map_ADI_Read_Areaa
Holds exception information:
Value: Meaning:
00h: No information
01h: Invalid assembly instance mapping, i.e. an
assembly instance number is equal to 0, or the
assembly instance numbers (consume/produce) are
equal.
a. Consult the general Anybus CompactCom 40 Software Design Guide for further information.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Anybus Module Objects 45
4.5 Network Configuration Object (04h)
Category
Basic
Object Description
This object holds network specific configuration parameters that may be set by the end user. A reset
command (factory default) issued towards this object will result in all instances being set to their default
values.
See also...
•
“Communication Settings” on page 11
•
“Identity Object (01h)” on page 17 (CIP-object)
Supported Commands
Object:
Get_Attribute
Reset
Instance:
Get_Attribute
Set_Attribute
Get_Enum_String
Object Attributes (Instance #0)
#
1
2
3
4
Name
Name
Revision
Number of instances
Highest instance no.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Access
Get
Get
Get
Get
Data Type
Array of CHAR
UINT8
UINT16
UINT16
Value
‘Network configuration’
01h
0002h
0002h
Doc.Id. HMSI-27-264
Anybus Module Objects 46
Instance Attributes (Instance #1, ‘Node Address’)
Basic
#
1
Name
Namea
Data type
Number of elements
Descriptor
Access
Get
Type
Array of CHAR
Description
‘Node address’
UINT8
UINT8
UINT8
UINT8
UINT8
04h (= UINT8)
01h (one element)
07h (read/write/shared access)
Node address
range: 0-63
default: 63
Holds the configured value, which will be written to
attribute #5.
Node address
range: 0-63
default: 64 (invalid value)
2
3
4
5
Valueb
Get
Get
Get
Get/Set
6
Configured Value
Get
a. Multilingual, see “Multilingual Strings” on page 47.
b. A ‘Get’ command always returns the actual value. If an invalid value is assigned to this attribute (i.e. using a ‘Set’
command), the module will accept node address configuration via the network (unless disabled in the DeviceNet
Host Object - in such case, the module will enter communication fault state at start up). If an invalid value is set
from switches, the latest valid value will be used when going online.
Instance Attributes (Instance #2, ‘Baud rate’)
Basic
#
1
Name
a
Access
Get
Type
Array of CHAR
Description
‘Baud rate’
2
3
4
5
Valueb
Get
Get
Get
Get/Set
UINT8
UINT8
UINT8
ENUM
6
Configured Value
Get
ENUM
08h (ENUM)
01h (one element)
07h (read/write/shared access)
Value:Enum. String:Meaning:
00h ‘125kbps’ 125kbps
01h ‘250kbps’ 250kbps
02h ‘500kbps’ 500kbps
03h ‘Autobaud’ Autobaud (default)
Holds the configured value, which will be written to
attribute #5.
Value:Enum. String:Meaning:
00h ‘125kbps’ 125kbps
01h ‘250kbps’ 250kbps
02h ‘500kbps’ 500kbps
03h ‘Autobaud’ Autobaud
default: 04h (invalid value)
Name
Data type
Number of elements
Descriptor
a. Multilingual, see “Multilingual Strings” on page 47.
b. A ‘Get’ command always returns the actual value. If an invalid value is assigned to this attribute (i.e. using a ‘Set’
command), the module will accept baud rate configuration via the network (unless disabled in the DeviceNet Host
Object - in such case, the module will enter communication fault state at start up). If an invalid value is set from
switches, the latest valid value will be used when going online.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Anybus Module Objects 47
Instance Attributes (Instance #3, ‘QuickConnect’)
Please note that this instance will only be implemented if Quick Connect functionality has been enabled
in the DeviceNet Host object during startup. It will be activated the first time the module enters Anybus
state WAIT_PROCESS.
See also ...
•
“DeviceNet Host Object (FCh)” on page 52
•
“Anybus State Machine” on page 58
Basic
#
1
2
3
4
5
Name
Name
Data type
Number of elements
Descriptor
Value
Access
Get
Get
Get
Get
Get/Set
Type
Array of CHAR
UINT8
UINT8
UINT8
BOOL
6
Configured Value
Get
BOOL
Description
‘QuickConnect’
00h (BOOL)
01h (one element)
07h (read/write/shared access)
Value:Meaning:
00h ‘Disable’ (Default)
01h ‘Enable’
Holds the configured value, which will be written to
attribute #5 when the module is reset.
Value:Meaning:
00h ‘Disable’
01h ‘Enable’
Multilingual Strings
The instance names in this object are multi-lingual, and are translated based on the current language settings as follows:
Instance
1
2
English
Node address
Baud rate
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
German
Geräteadresse
Datenrate
Spanish
Direcc nodo
Veloc transf
Italian
Indirizzo
Velocità dati
French
Adresse
Vitesse
Doc.Id. HMSI-27-264
Anybus Module Objects 48
4.6 Anybus File System Interface Object (0Ah)
Category
Extended
Object Description
This object provides an interface to the built-in file system. In an Anybus CompactCom 40 Devicenet
module, the file system consist of one folder, called “Firmware”. This folder is used to save a firmware
file to upgrade the module. After a reset, the firmware in the module will be upgraded and the file erased.
Please consult the Anybus CompactCom 40 Software Design Guide for more information.
Supported Commands
(Consult the general Anybus CompactCom 40 Software Design Guide for further information)
Object Attributes (Instance #0)
(Consult the general Anybus CompactCom 40 Software Design Guide for further information)
Instance Attributes
(Consult the general Anybus CompactCom 40 Software Design Guide for further information)
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Chapter 5
5. Host Application Objects
5.1 General Information
This chapter specifies the host application object implementation in the module. The objects listed here
may optionally be implemented within the host application firmware to expand the DeviceNet implementation.
Standard Objects:
•
Application Object (FFh, see Anybus CompactCom 40 Software Design Guide)
•
Application Data Object (FEh, see Anybus CompactCom 40 Software Design Guide)
•
Modular Device Object (ECh, see Anybus CompactCom 40 Software Design Guide)
•
Energy Control Object (F0h, see Anybus CompactCom 40 Software Design Guide)
•
Energy Reporting Object (E7h, see Anybus CompactCom 40 Software Design Guide)
•
“SYNC Object (EEh)” on page 51
Network Specific Objects:
•
“CIP Identity Host Object (EDh)” on page 50
•
“DeviceNet Host Object (FCh)” on page 52
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Host Application Objects 50
5.2 CIP Identity Host Object (EDh)
Category
Extended
Object Description
This object allows for applications to support additional CIP identity instances. It is used to provide additional product identity information, e.g. concerning the software installed.
The first instance in the CIP identity object will not change its behavior. When implementing instances
in the CIP identity host object, they will be mapped to the CIP identity object starting at instance 2. Instance no. 1 in the CIP identity host object will be mapped to instance no. 2 in the CIP identity object,
and so on.
Supported Commands
Object:
Get_Attribute
Instance:
Get_Attribute
Get_Attribute_All
Object Attributes (Instance #0)
#
1
2
3
4
Name
Name
Revision
Number of instances
Highest instance no.
Access
Get
Get
Get
Get
Type
STRING
UINT8
UINT16
UINT16
Value
“CIP Identity”
01h
Depends on application
Depends on application
Comment
Object name
Object revision
Supported number of instances
Highest implemented instance
Instance Attributes (Instance #1)
Extended
#
1
2
3
4
5
6
7
Name
Vendor ID
Device Type
Product Code
Revision
Status
Serial Number
Product Name
Access
Get
Get
Get
Get
Get
Get
Get
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Type
UINT16
UINT16
UINT16
Struct of
UINT8,
UINT8
UINT16
UINT32
Array of CHAR
Value
-
Comment
These values replace the default values for
the CIP Identity object.
(Major Revision,
Minor Revision)
-
Doc.Id. HMSI-27-264
Host Application Objects 51
5.3 SYNC Object (EEh)
Category
Extended
Object Description
This object implements the host application SYNC settings.
See also...
•
Anybus CompactCom 40 Software Design Guide, “Sync”
•
Anybus CompactCom 40 Software Design Guide, “Sync Object”
Supported Commands
Object:
Get_Attribute
Instance:
Get_Attribute
Set_Attribute
Object Attributes (Instance #0)
(Consult the general Anybus CompactCom 40 Software Design Guide for further information)
Instance Attributes (Instance #1)
Extended
#
1
Name
Cycle time
2-8
(not implemented)
Access
Get/Set
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Type
UINT32
Default Value
Comment
When a connection is active, the value of
attribute #9 (Expected Package Rate) of the
Connection Object, instance #2 (CIP object)
should be written to this attribute.
See “Connection Object (05h)” on page 25.
Doc.Id. HMSI-27-264
Host Application Objects 52
5.4 DeviceNet Host Object (FCh)
Category
Basic, extended
Object Description
This object implements DeviceNet specific settings in the host application. It is also used when implementing DeviceNet classes in the host application, e.g. when creating profile implementations etc.
The implementation of this object is optional; the host application can support none, some, or all of the
attributes specified below. The module will attempt to retrieve the values of these attributes during startup; if an attribute is not implemented in the host application, simply respond with an error message (06h,
“Invalid CmdExt[0]”). In such case, the module will use its default value.
If the module attempts to retrieve a value of an attribute not listed below, respond with an error message
(06h, “Invalid CmdExt[0]”).
See also...
•
“Identity Object (01h)” on page 17
•
Anybus CompactCom 40 Software Design Guide, “Error Codes”
IMPORTANT: To comply with CIP-specification requirements, the combination of Vendor ID (instance attribute
#1) and serial number (instance attribute #5) must be unique. The default Vendor ID, serial number, and Product Code
combination is valid only if using the standard ESD-file supplied by HMS.
Supported Commands
Object:
Process_CIP_Message_Request (See “CIP Request Forwarding” on page 59)
Instance:
-
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Host Application Objects 53
Object Attributes (Instance #0)
#
1
2
3
4
Name
Name
Revision
Number of instances
Highest instance no.
Access
Get
Get
Get
Get
Data Type
Array of CHAR
UINT8
UINT16
UINT16
Value
‘DeviceNet’
01h
0001h
0001h
Instance Attributes (Instance #1)
Basic
#
1
2
3
4
Name
Vendor ID
Device Type
Product Code
Revision
Access
Get
Get
Get
Get
5
6
Serial Number
Product Name
Get
Get
Type
UINT16
UINT16
UINT16
struct of:
UINT8 Major
UINT8 Minor
UINT32
Array of CHAR
Default Value
005Ah
002Bh
003Fh
(software revision)
Comment
These values are forwarded to the DeviceNet Identity Object (CIP).
(set at production)
‘CompactCom 40 DeviceNet(TM)’
Extended
#
7
Name
Producing
Instance No.
Access
Get
Type
UINT16
Default Value
0064h
8
Consuming
Instance No.
Get
UINT16
0096h
9
Enable Address Get
from Net
BOOL
True
10 Enable Baud
rate from Net
Get
11 Enable CIP for- Get
warding
BOOL
BOOL
True
False
Comment
See also...
- “Instance 64h Attributes (Producing
Instance)” on page 23 (CIP-instance)
See also...
- “Instance 96h Attributes (Consuming
Instance)” on page 24 (CIP-instance)
Value:Meaning:
True Can be set from network
False Cannot be set from network
See also...
- “Identity Object (01h)” on page 17 (CIPobject)
Value:Meaning:
True Can be set from network
False Cannot be set from network
See also...
- “Identity Object (01h)” on page 17 (CIPobject)
Value:Meaning:
True Enable CIP forwarding
False Disable CIP forwarding
See also...
- “Command Details: Process_CIP_Message_Request” on page 55
- “CIP Request Forwarding” on page 59.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Host Application Objects 54
# Name
Access
12 Enable Param- Get
eter Object
13 Enable Quick
Connect
Get
20 Anybus Com- Get
pactCom ADI
Object Number
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Type
BOOL
Default Value
True
BOOL
False
UINT16
00A2h
Comment
Value:Meaning:
True Enable CIP Parameter Object
False Disable CIP Parameter Object
See also...
- “Parameter Object (0Fh)” on page 30
(CIP-object)
Value:Meaning:
True Enable Quick Connect
False Disable Quick Connect
See also...
- “DeviceNet Object (03h)” on page 21
This attribute is used either to change the
object number of the Anybus CompactCom
ADI Object or to disable the object.
Valid ranges: 0064h-00C7h and 0300h04FFh (within the Vendor Specific ranges).
Any value outside these ranges will disable
the ADI Object.
Doc.Id. HMSI-27-264
Host Application Objects 55
Command Details: Process_CIP_Message_Request
Category
Extended
Details
Command Code.: 10h
Valid for:
Object Instance
Description
By setting the ‘Enable CIP Request Forwarding’-attribute (#11), all requests to unimplemented CIP-objects or unimplemented assembly object instances will be forwarded to the host application. The application then has to evaluate the request and return a proper response.
The module supports up to 6 pending CIP-requests; additional requests will be rejected by the module.
Note: This command is similar - but not identical - to the ‘Process_CIP_Message_Request’-command
in the Anybus CompactCom 40 EtherNet/IP.
See also...
•
“Device Customization” on page 9
•
“CIP Request Forwarding” on page 59
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Appendix A
A. Categorization of Functionality
The objects, including attributes and services, of the Anybus CompactCom and the application are divided into two categories: basic and extended.
A.1 Basic
This category includes objects, attributes and services that are mandatory to implement or to use. They
will be enough for starting up the Anybus CompactCom and sending/receiving data with the chosen
network protocol. The basic functions of the industrial network are used.
Additional objects etc, that will make it possible to certify the product also belong to this category.
A.2 Extended
Use of the objects in this category extends the functionality of the application. Access is given to the
more specific characteristics of the industrial network, not only the basic moving of data to and from
the network. Extra value is given to the application.
Some of the functionality offered may be specialized and/or seldom used. As most of the available network functionality is enabled and accessible, access to the specification of the industrial network may be
required.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Appendix B
B. Implementation Details
B.1 DeviceNet Implementation
Predefined Connection Set
The module acts as a Group 2 server and supports the Predefined Master/Slave Connection Set.
•
COS Connection
When the master allocates this connection type, the module transmits the all Process Data at a
change of state. An inhibit time can be set to prevent the module from sending too often.
The module supports up to 512 bytes in each direction for this type of connection. The size of
the connection is checked against the number of bytes mapped as Process Data.
•
Cyclic Connection
When the master allocates this connection type, the module cyclically transmits the Process Data
at the configured interval.
The module supports up to 512 bytes in each direction for this type of connection.
•
Bit Strobe Connection
When the master allocates this connection type, the module transmits data when the bit strobe
message is received, and produces up to 512 bytes.
•
Polled Connection
When the master allocates this connection type, the module transmits the Process Data data
when a poll command is received.
The module supports up to 512 bytes in each direction for this type of connection.
•
Explicit Connection
The predefined explicit connection has a buffer of 512 bytes.
•
Idle/Running
The module is considered to be in Idle mode when not receiving any DeviceNet telegrams, or
when receiving DeviceNet telegrams with no data. In other cases, the module is considered to
be in Run mode.
This affects the Anybus State machine as describe in B-58 “Anybus State Machine”.
Unconnected Message Server (UCMM)
The module is a UCMM capable device, and supports the Unconnected Explicit Message Request port,
Group3, Message ID=6.
•
Explicit Message Server
The module supports up to 5 simultaneous explicit message connections.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Implementation Details 58
B.2 SUP-Bit Definition
The supervised bit (SUP) indicates that the network participation is supervised by another network device. For DeviceNet this bit is set when the connection object has a connection.
B.3 Anybus State Machine
The table below describes how the Anybus State Machine relates to the DeviceNet network. status
State
WAIT_PROCESS
DeviceNet Specific Meaning
Notes
The module will stay in this state until a Class (Not set for explicit connections.)
0 connection is opened.
If the error is fatal, such, such as dup-MAC-fail
ERROR
Class 0 connection error, Bus-Offa event
or Bus-Off, the module will stay in this state
detected or dup-MAC-fail
until a HW reset is done.
PROCESS_ACTIVE Error free Class 0 connection active
IDLE
Class 0 connection idle
Can only be set for connections consuming
data.
EXCEPTION
Some kind of unexpected behavior, e.g.
The Module Status LED will turn red to indiwatchdog timeout.
cate a major fault, and turn the Network Status
LED off.
a. A Bus-Off occurs when it is impossible to communicate on the underlying CAN layer, e.g. if the lines are short
circuited.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Appendix C
C. CIP Request Forwarding
If CIP request forwarding is enabled (DeviceNet Host Object, Instance 1, Attribute 11), all network requests to unknown CIP objects or unknown assembly object instances will be forwarded to the host
application. For this purpose, the DeviceNet Host Object implements a command called Process_CIP_Message_Request (Command code 10h), which is used to tunnel CIP requests to the host application.
Note: CIP request forwarding is only relevant for explicit messages. It is not applicable to the messages
that carry the cyclic/process data.
Since the telegram length on the host interface is limited, the request data size must not exceed 255 bytes.
If it does, a the module will send a ‘resource unavailable’ response to the originator of the request and
the message will not be forwarded to the host application.
•
Command Message Layout
This message will be sent by the module to the host application upon receiving an unknown CIP
request from the network.
Contents
Notes
b7 b6 b5 b4 b3 b2 b1 b0
Source ID
(Source ID)
Selected by the module
Dest. Object
FCh
Destination Object = DeviceNet Host Object
Dest. Instance (lsb)
00h
Destination Instance = Object Instance
Dest. Instance (msb) 00h
This message is not an error message
(command/error)
0
1
This message is a command
(command/response)
Command number
10h
Process_CIP_Object_Request
Message Data Size
Length of CIP request
CmdExt[0]
CIP Service Code
CIP service code from original CIP request
(reserved, ignore)
CmdExt[1]
MsgData[0]
Requested CIP Class no.
(Low byte)
MsgData[1]
(High byte)
MsgData[2]
Requested CIP Instance no.
(Low byte)
MsgData[3]
(High byte)
MsgData[4...n]
CIP Data
Data associated with the CIP request
Field
•
Host Application Response Message Layout (Successful)
If the host application recognized the CIP request, i.e. if the CIP object in question is implemented in the host application, the following response shall be sent to the module.
Contents
b7 b6 b5 b4 b3 b2 b1 b0
Source ID
(Source ID)
Dest. Object
FCh
Dest. Instance (lsb)
00h
Dest. Instance (msb) 00h
(command/error)
0
0
(command/response)
Command number
10h
Message Data Size
Length of response data
CmdExt[0]
CIP Service Code (with reply bit set)
CmdExt[1]
00h
MsgData[0...n]
Response data
Field
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Notes
(Selected by the module)
Object = DeviceNet Host Object
Instance = Object
This message is not an error message
This message is a response
Process_CIP_Object_Request
(not used, set to zero)
-
Doc.Id. HMSI-27-264
CIP Request Forwarding 60
•
Host Application Response Message Layout (Unsuccessful)
If the host application did not recognize the CIP request, i.e. the CIP object in question is not
implemented in the host application, the following response shall be sent to the module.
Contents
Notes
b7 b6 b5 b4 b3 b2 b1 b0
Source ID
(Source ID)
(Selected by the module)
Dest. Object
FCh
Object = DeviceNet Host Object
Dest. Instance (lsb)
00h
Instance = Object
Dest. Instance (msb) 00h
(command/error)
0
This message is not an ABCC error messagea
(command/response)
0
This message is a response
Command number
10h
Process_CIP_Object_Request
Message Data Size
02h
2 bytes of message data
CmdExt[0]
94h
CIP error service code with reply bit set
CmdExt[1]
00h
(not used, set to zero)
MsgData[0]
CIP General status code
MsgData[1]
Optional additional status
(FFh if no additional status)
Field
a.If this bit is set (1), an Anybus CompactCom error has occurred and an ABCC error code is returned.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Appendix D
D. Technical Specification
D.1 Front View
#
1
Item
Network Status LED
2
Module status LED
3
DeviceNet Connector
1
2
3
1
5
Network Status
State
Off
Green
Flashing Green (1 Hz)
Red
Flashing Red (1 Hz)
Alternating Red/Green
Indication
Not online / No network power
On-line, one or more connections are established
On-line, no connections established
Critical link failure, fatal event
One or more connections timed-out
Executing self test
Module Status
State
Off
Green
Flashing Green (1 Hz)
Red
Flashing Red (1 Hz)
Alternating Red/Green
Indication
Not operating
Operating in normal condition
Missing, incorrect or incomplete configuration, device needs commissioning.
Unrecoverable Fault(s)
Recoverable Fault(s)
Executing self test
DeviceNet Connector
This connector provides DeviceNet connectivity.
Pin
1
Signal
V-
2
3
4
5
CAN_L
SHIELD
CAN_H
V+
Description
Negative bus supply voltagea
CAN low bus line
Cable shield
CAN high bus line
Positive bus supply voltagea
a. DeviceNet bus power. For more information, see D-61 “Technical Specification”.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Technical Specification 62
D.2 Protective Earth (PE) Requirements
In order to ensure proper EMC behavior, the module must be properly connected to protective earth
via the PE pad / PE mechanism described in the general Anybus CompactCom 40 Hardware Design
Guide.
HMS Industrial Networks does not guarantee proper EMC behavior unless these PE requirements are
fulfilled.
D.3 Power Supplies
Supply Voltage
The module/brick requires a regulated 3.3 V power source as specified in the general Anybus CompactCom M40 Hardware Design Guide.
DeviceNet Power Supply
The total number of units that can be connected to the DeviceNet bus is limited by the maximum current that the power supply can deliver to the bus. Maximum current consumption per unit is specified
in the DeviceNet specification to 750 mA. If e.g. the supply can deliver 9 A and all units consume maximum current, the maximum numbers of units allowed on the bus are 12 (12x750 mA = 9A).
The Anybus CompactCom 40 DeviceNet module accepts 11 - 25 V on the industrial network side of
the module.
D.4 Power Consumption
Note: It is strongly advised to design the power supply in the host application based on the power consumption classifications described in the general Anybus CompactCom 40 Hardware Design Guide, and
not on the exact power requirements of a single product.
Anybus CompactCom M40 DeviceNet
The Anybus CompactCom M40 DeviceNet is designed to fulfil the requirements of a Class B module.
For more information about the power consumption classification used on the Anybus CompactCom
platform, consult the general Anybus CompactCom M40 Hardware Design Guide.
The current hardware design consumes up to 280 mA1.
Maximum current consumption on the network side at 11 - 25 V is 16 mA/module.
Anybus CompactCom B40-1 DeviceNet
The brick alone consumes up to 115 mA. The connector board will add up to 3.5 mA to the power consumption. A complete solution, including a brick, a connector board and LEDs with maximum allowed
current consumption, will consume up to 147 mA.
Maximum current consumption on the network side at 11 - 25 V is 39 mA/brick.
1. Note that in line with HMS policy of continuous product development, we reserve the right to change the
exact power requirements of this product without prior notification. Note however that in any case, the
Anybus CompactCom 40 DeviceNet will remain as a Class B module.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
Technical Specification 63
D.5 Environmental Specification
Consult the Anybus CompactCom 40 Hardware Design Guide for further information.
D.6 EMC Compliance
Consult the Anybus CompactCom 40 Hardware Design Guide for further information.
Anybus CompactCom 40 DeviceNet
Doc.Rev. 1.20
Doc.Id. HMSI-27-264
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