null  null
Network Interface Appendix
Anybus -CompactCom DeviceNet
®
Rev. 1.06
HMS Industrial Networks AB
Germany + 49 - 721 - 96472 - 0
Japan
+ 81 - 45 - 478 -5340
Sweden
+ 46 - 35 - 17 29 20
U.S.A
+ 1 - 773 - 404 - 3486
[email protected]
[email protected]
[email protected]
[email protected]
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-3
Support .................................................................................................................................................. P-3
Chapter 1
About the Anybus-CompactCom DeviceNet
General....................................................................................................................................................1-1
Features...................................................................................................................................................1-1
Fieldbus Conformance Notes .............................................................................................................1-1
Front View .............................................................................................................................................1-2
Chapter 2
Basic Operation
General Information.............................................................................................................................2-1
Software Requirements ..................................................................................................................2-1
Electronic Data Sheet (EDS).......................................................................................................2-1
Device Customization ..........................................................................................................................2-2
Communication Settings ......................................................................................................................2-3
Diagnostics .............................................................................................................................................2-3
Data Exchange.......................................................................................................................................2-4
Application Data (ADIs) ............................................................................................................2-4
Process Data.................................................................................................................................2-4
Translation of Data Types ............................................................................................................2-4
Chapter 3
CIP Objects
General Information.............................................................................................................................3-1
Identity Object (01h) ............................................................................................................................3-2
General Information......................................................................................................................3-2
Class Attributes ...........................................................................................................................3-2
Instance #1 Attributes .................................................................................................................3-2
Service Details: Reset Service .........................................................................................................3-3
Message Router (02h) ...........................................................................................................................3-4
General Information......................................................................................................................3-4
Class Attributes ...........................................................................................................................3-4
Instance Attributes........................................................................................................................3-4
DeviceNet Object (03h).......................................................................................................................3-5
General Information......................................................................................................................3-5
Class Attributes ...........................................................................................................................3-5
Instance #1 Attributes .................................................................................................................3-5
Assembly Object (04h) .........................................................................................................................3-6
General Information......................................................................................................................3-6
Class Attributes ...........................................................................................................................3-6
Instance 64h Attributes (Producing Instance) ................................................................................3-6
Instance 96h Attributes (Consuming Instance) ..............................................................................3-6
Connection Object (05h) .....................................................................................................................3-7
General Information......................................................................................................................3-7
Class Attributes ...........................................................................................................................3-7
Instances #1, #10... #14 (Explicit messaging)............................................................................3-7
Instance #2 (Poll or “COS/Cyclic consuming”) ...........................................................................3-8
Instance #3 (Bit-strobe) ................................................................................................................3-9
Instance #4 (COS/Cyclic producing)..........................................................................................3-10
Parameter Object (0Fh)......................................................................................................................3-11
General Information....................................................................................................................3-11
Class Attributes .........................................................................................................................3-11
Instance Attributes......................................................................................................................3-12
Acknowledge Handler Object (2Bh)................................................................................................3-13
General Information....................................................................................................................3-13
Class Attributes .........................................................................................................................3-13
Instances Attributes (01h) ..........................................................................................................3-13
ADI Object (A2h)...............................................................................................................................3-14
General Information....................................................................................................................3-14
Class Attributes .........................................................................................................................3-14
Instances Attributes ....................................................................................................................3-14
Chapter 4
Anybus Module Objects
General Information.............................................................................................................................4-1
Anybus Object (01h).............................................................................................................................4-2
General Information......................................................................................................................4-2
Object Attributes (Instance #0) ....................................................................................................4-2
Instance Attributes (Instance #1) .................................................................................................4-3
Diagnostic Object (02h) .......................................................................................................................4-4
General Information......................................................................................................................4-4
Object Attributes (Instance #0) ....................................................................................................4-4
Instance Attributes (Instance #1) .................................................................................................4-4
Network Object (03h) ..........................................................................................................................4-5
General Information......................................................................................................................4-5
Object Attributes (Instance #0) ....................................................................................................4-5
Instance Attributes (Instance #1) .................................................................................................4-5
Network Configuration Object (04h) ................................................................................................4-6
General Information......................................................................................................................4-6
Object Attributes (Instance #0) ....................................................................................................4-6
Instance Attributes (Instance #1, ‘Device Address’)......................................................................4-7
Instance Attributes (Instance #2, ‘Baud rate’) ..............................................................................4-7
Multilingual Strings......................................................................................................................4-7
Chapter 5
Host Application Objects
General Information.............................................................................................................................5-1
DeviceNet Host Object (FCh)............................................................................................................5-2
General Information......................................................................................................................5-2
Object Attributes (Instance #0) ....................................................................................................5-2
Instance Attributes (Instance #1) .................................................................................................5-3
Command Details: Process_CIP_Request.....................................................................................5-4
Appendix A Implementation Details
DeviceNet Implementation ................................................................................................................ A-1
SUP-Bit Definition...............................................................................................................................A-2
Anybus Statemachine...........................................................................................................................A-2
Appendix B CIP Request Forwarding
Appendix C Technical Specification
Protective Earth (PE) Requirements................................................................................................. C-1
Power Supply ........................................................................................................................................ C-1
Environmental Specification .............................................................................................................. C-1
EMC Compliance................................................................................................................................. C-1
Preface
About This Document
How To Use This Document
This document is intended to provide a good understanding of the functionality offered by the AnybusCompactCom DeviceNet fieldbus communication module. Only the features that are unique to this
product are described in this document, i.e. for general information regarding the Anybus-CompactCom
platform, consult the Anybus-CompactCom Hardware and Software Design Guides.
The reader of this document is expected to be familiar with high level software design, and communication systems in general. The use of advanced DeviceNet-specific functionality may require in-depth
knowledge in DeviceNet/CIP networking internals and/or information from the official DeviceNet/
CIP specification. In such cases, the people responsible for the implementation of this product should
either obtain the DeviceNet/CIP specification to gain sufficient knowledge or limit their implementation is such a way that this is not necessary.
For more information, documentation etc., please visit the HMS website, ‘www.anybus.com’.
Important User Information
Anybus-CompactCom and the technology used in Anybus-CompactCom is protected by patent, pending patents, copyright and trademark laws under the United States of America and international law.
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 application meets all performance and safety requirements including any applicable laws, regulations, codes, and standards.
Anybus® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their respective holders.
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 cannot assume responsibility or liability for actual use based on these examples and illustrations.
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.
About This Document P-2
Related Documents
Document
Anybus-CompactCom Software Design Guide
Anybus-CompactCom Hardware Design Guide
Anybus-CompactCom Software Driver User Guide
DeviceNet Specification
Common Industrial Protocol (CIP) specification
Author
HMS
HMS
HMS
ODVA
ODVA
Document History
Summary of Recent Changes (1.05 - 1.06)
Change
Added instance attribute #18 (‘Connection Timeout Multiplier’) (Connection Object (05h))
Updated object specification (‘Anybus Object (01h)’)
-
Revision List
Revision
1.00
1.01
1.05
1.06
Date
2005-09-15
2005-10-19
2006-05-03
2007-04-26
Author(s)
PeP
PeP
PeP
PeP
Chapter(s)
-
Description
First official release
Misc. minor corrections
Misc. visual and structural updates
Minor update
Page(s)
3-7, 3-8, 3-9, 3-10
4-2
-
About This Document 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, where NNNN is the hexadecimal value.
Support
HMS Sweden (Head Office)
E-mail:
Phone:
Fax:
Online:
[email protected]
+46 (0) 35 - 17 29 20
+46 (0) 35 - 17 29 09
www.anybus.com
HMS America
E-mail:
Phone:
Toll Free:
Fax:
Online:
[email protected]
+1-773-404-2271
888-8-Anybus
+1-773-404-1797
www.anybus.com
HMS Germany
E-mail:
Phone:
Fax:
Online:
[email protected]
+49-721-96472-0
+49-721-964-7210
www.anybus.com
HMS Japan
E-mail:
Phone:
Fax:
Online:
[email protected]
+81-45-478-5340
+81-45-476-0315
www.anybus.com
Chapter 1
About the Anybus-CompactCom DeviceNet
General
The Anybus-CompactCom 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 AnybusCompactCom 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.
Features
•
Galvanically isolated bus electronics
•
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 Baudrate Detection
Fieldbus Conformance Notes
Important: The following information is preliminary/pending:
•
The Anybus-CompactCom DeviceNet has been pre-compliance tested by ODVA’s authorized
Independent Test Lab and found to comply with ODVA Conformance Test Software v. A17.
However, according to ODVA’s conformance test policy, the final product must still be compliance tested to ensure fieldbus conformance. Note that in order to be able to do this, the vendor
information in the DeviceNet Host Object must be customized.
For further information, please contact HMS or ODVA.
•
In order to ensure fieldbus conformance, the recommendations stated in the Anybus-CompactCom Software Design Guide regarding the Network Configuration Object (04h) must be followed.
About the Anybus-CompactCom DeviceNet 1-2
Front View
#
1
2
3
Item
Network Status LED
Module Status LED
DeviceNet Connector
Network Status
State
Off
Green
Flashing Green (1 Hz)
Red
Flashing Red (1 Hz)
Alternating Red/Green
Indication
Not online / No power
On-line, one or more connections are established
On-line, no connections established
Critical link failure
One or more connections timed-out
Self test
Module Status
State
Off
Green
Flashing Green (1 Hz)
Red
Flashing Red (1 Hz)
Alternating Red/Green
Indication
No power
Operating in normal condition
Missing or incomplete configuration, device needs commissioning
Unrecoverable Fault(s)
Recoverable Fault(s)
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 C-1 “Technical Specification”.
Chapter 2
Basic Operation
General Information
Software Requirements
Generally, no additional network support code needs to be written in order to support the Anybus-CompactCom DeviceNet. However, due to the nature of the DeviceNet networking system, certain restrictions must be taken into account:
•
Certain functionality in the module requires that the command ‘Get_Instance_By_Order’ (Application Data Object, FEh) is implemented in the host application.
•
Up to 5 diagnostic instances (See 4-4 “Diagnostic Object (02h)”) 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 Software Design Guide.
See also...
•
4-4 “Diagnostic Object (02h)” (Anybus Module Object)
•
Anybus-CompactCom Software Design Guide, ‘Application Data Object (FEh)’
Electronic Data Sheet (EDS)
Since the module implements the Parameter Object, it is possible for configuration tools such as
RSNetWorx to automatically generate a suitable EDS-file.
Note that this functionality requires that the command ‘Get_Instance_By_Order’ (Application Data
Object, FEh) has been implemented in the host application.
See also...
•
2-2 “Device Customization”
•
3-11 “Parameter Object (0Fh)” (CIP-object)
•
Anybus-CompactCom 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 Product Code which complies to the default Vendor ID, please contact HMS.
Basic Operation 2-2
Device Customization
By default, the module supports the generic CIP-profile with the following identity settings:
•
Vendor ID:
005Ah (HMS Industrial Networks)
•
Device Type:
0000h (Generic Device)
•
Product Code:
0062h (Anybus-CompactCom DeviceNet)
•
Product Name:
‘Anybus-CC DeviceNet’
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...
•
3-2 “Identity Object (01h)” (CIP-object)
•
5-2 “DeviceNet Host Object (FCh)” (Host Application Object)
•
B-1 “CIP Request Forwarding”
IMPORTANT: The default identity information is valid only when using the standard EDS-file supplied by HMS.
To comply with CIP-specification requirements, custom EDS-implementations require a new Vendor ID and/or Product
Code.
To obtain a Product Code which complies to the default Vendor ID, please contact HMS.
Basic Operation 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...
- 4-7 “Instance Attributes (Instance #2, ‘Baud rate’)”
•
Mac ID
See also...
- 4-7 “Instance Attributes (Instance #1, ‘Device Address’)”
The parameters in the Network Configuration Object (04h) are available from the network through the
Identity Object (CIP-object).
See also...
•
3-2 “Identity Object (01h)” (CIP-object)
•
4-6 “Network Configuration Object (04h)” (Anybus Module Object)
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...
•
3-2 “Identity Object (01h)” (CIP-object)
•
4-4 “Diagnostic Object (02h)” (Anybus Module Object)
Basic Operation 2-4
Data Exchange
Application Data (ADIs)
ADIs are represented on DeviceNet through the 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...
•
3-11 “Parameter Object (0Fh)” (CIP-object)
•
3-14 “ADI Object (A2h)” (CIP-object)
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...
•
3-6 “Assembly Object (04h)” (CIP-object)
•
3-7 “Connection Object (05h)” (CIP-object)
Translation of Data Types
The Anybus data types are translated to CIP-standard and vice versa according to the table below.
Anybus Data Type
BOOL
ENUM
SINT8
UINT8
SINT16
UINT16
SINT32
UINT32
FLOAT
CHAR
CIP Data Type
BOOL
USINT
SINT
USINT
INT
UINT
DINT
UDINT
REAL
SHORT_STRING
SINT64
UINT64
LINT
ULINT
Comments
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.
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.
Chapter 3
CIP Objects
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:
•
3-2 “Identity Object (01h)”
•
3-4 “Message Router (02h)”
•
3-5 “DeviceNet Object (03h)”
•
3-6 “Assembly Object (04h)”
•
3-7 “Connection Object (05h)”
•
3-11 “Parameter Object (0Fh)”
•
3-13 “Acknowledge Handler Object (2Bh)”
Vendor Specific Objects:
•
3-14 “ADI Object (A2h)”
It is possible to implement additional CIP-objects in the host application using the CIP forwarding functionality, see 5-2 “DeviceNet Host Object (FCh)” and B-1 “CIP Request Forwarding”.
CIP Objects 3-2
Identity Object (01h)
General Information
Object Description
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Reset
Class Attributes
#
1
Access
Get
Name
Revision
Type
UINT
Comments
0001h
Instance #1 Attributes
#
1
Access
Get
Name
Vendor ID
Type
UINT
005Ah (HMS Industrial Networks ABa)
2
Get
Device Type
UINT
0000h (Generic Devicea)
3
Get
Product Code
UINT
0062h (Anybus-CompactCom DeviceNeta)
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 Set
12 Get
Comments
See 3-3 “Device Status”
Assigned by HMSa
SHORT_STRING “Anybus-CC DeviceNet” (Name of producta)
Active language Struct of:
Requests sent to this instance are forwarded to the Application
{USINT,
Object. The host application is then responsible for updating the lanUSINT,
guage settings accordingly.
USINT}
Supported
Array of struct of: List of languages supported by the host application. This list is read
Language List {USINT,
from the Application Object during the NW_INIT state, and translated
USINT,
to CIP standard.
USINT}
a. Can be customized by implementing the DeviceNet Host Object, see 5-2 “DeviceNet Host Object (FCh)”
CIP Objects 3-3
Device Status
bit(s)
0
1
2
3
4... 7
Name
Module Owned
(reserved)
Configureda
(reserved)
Extended Device Status:
Value: Meaning:
0000b Unknown
0010b Faulted I/O Connection
0011b No I/O connection established
0100b Non-volatile configuration bad
0110b Connection in Run mode
0111b Connection in Idle mode
(other) (reserved)
8
Set for minor recoverable faultsb
9
Set for minor unrecoverable faultsb
10
Set for major recoverable faultsb
11
Set for major unrecoverable faultsb
(reserved)
12... 15
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 is set and/or the module’s NV storage is changed from default.
b. See 4-4 “Diagnostic Object (02h)”.
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 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 cycling). For further information, consult the general Anybus-CompactCom 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 cycling + factory default). For further information, consult the general Anybus-CompactCom Software Design Guide.
CIP Objects 3-4
Message Router (02h)
General Information
Object Description
Supported Services
Class
-
Instance:
-
Class Attributes
-
Instance Attributes
-
CIP Objects 3-5
DeviceNet Object (03h)
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)
Class Attributes
#
1
Name
Revision
Access
Get
Type
UINT
Comments
0002h
Type
USINT
Comments
Currently used MacID
Value: Baud rate:
0
125 kbps
1
250 kbps
2
500 kbps
False
00h
Instance #1 Attributes
#
1
Name
MAC ID
Access
Get/Set
2
Baud Rateab
Get/Set
USINT
3
4
5
BOI
Bus off Counter
Allocation Information
Get/Set
Get/Set
Get
a
6
MAC ID Switch changeda
Get
BOOL
USINT
Struct of:
BYTE
USINT
BOOL
7
Baud rate Switch changeda
Get
BOOL
8
MAC ID Switch valuea
Get
USINT
Allocation choice byte
MAC ID of master
Indicates if the MacID has changed since startup
Value: Meaning
True Changed
False No change
Indicates if the baudrate has changed since startup
Value: Meaning
True Changed
False No change
Actual value of node address switches
Get
USINT
Actual value of baud rate switches
Set
BOOL
Value: Meaning
True Disable auto baud
False Enable auto baud
This setting is stored in NV memory.
9
a
Baud rate Switch value
100 Disable auto baud
a. Implementation of attributes 6 to 9 are conditional as well as access right for attributes 1 and 2. For further information, see 3-1 “Network Communication Settings”.
b. Setting this attribute will also affect attribute #100 (Disable auto baud).
CIP Objects 3-6
Assembly Object (04h)
General Information
Object Description
The Assembly object uses static assemblies and holds the Process Data sent/received by the host application. The default assembly instance IDs used are in the vendor specific range.
See also...
•
2-4 “Process Data”
•
5-2 “DeviceNet Host Object (FCh)”
Supported Services
Class
-
Instance:
Get Attribute Single
Set Attribute Single
Class Attributes
-
Instance 64h Attributes (Producing Instance)
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
Comments
This data corresponds to the Write Process Data
See also...
•
2-4 “Data Exchange”
•
5-2 “DeviceNet Host Object (FCh)”
Instance 96h Attributes (Consuming Instance)
The instance number for this instance can be changed by implementing the corresponding attribute in
the DeviceNet Host Object.
#
3
Name
Consumed Data
Access
Set
Type
Array of BYTE
See also...
•
2-4 “Data Exchange”
•
5-2 “DeviceNet Host Object (FCh)”
Comments
This data corresponds to the Read Process Data
CIP Objects 3-7
Connection Object (05h)
General Information
Object Description
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Class Attributes
#
1
Name
Revision
Access
Get
Type
UINT
Comments
0001h
Instances #1, #10... #14 (Explicit messaging)
#
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
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)
The message group over which the communication
occurs:
Value: Message Group
21
Instance #1
33
Instances #10... #14
262 bytes
262 bytes
2500ms
Value: Action:
0001h Auto delete (default)
0003h Deferred delete
0000h (No connection path)
0000h (No connection path)
0000h
0000h
CIP Objects 3-8
Instance #2 (Poll or “COS/Cyclic consuming”)
#
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
16
17
18
Get
Get
Get
Get/Set
UINT
EPATH
UINT
UINT
Consumed Connection path length
Consumed Connection path
Production Inhibit Time
Connection Timeout Multiplier
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
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)
0007h
20 04 25 nn nn 30 03h
0000h
0000h
CIP Objects 3-9
Instance #3 (Bit-strobe)
#
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
15
16
17
18
Consumed Connection Size
Expected Packet Rate
Watchdog timeout action
Produced Connection path length
Produced Connection path
Consumed Connection path length
Consumed Connection path
Production Inhibit Time
Connection Timeout Multiplier
Get
Get/Set
Get
Get
Get
Get
Get
Get
Get/Set
UINT
UINT
USINT
UINT
EPATH
UINT
EPATH
UINT
UINT
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)
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
0007h
20 04 25 nn nn 30 03h
0000h
0000h
CIP Objects 3-10
Instance #4 (COS/Cyclic producing)
#
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
15
Produced Connection Size
Consumed Connection Size
Expected Packet Rate
Watchdog timeout action
Produced Connection path length
Produced Connection path
Consumed Connection path length
Get
Get
Get/Set
Get
Get
Get
Get
UINT
UINT
UINT
USINT
UINT
EPATH
UINT
16 Consumed Connection path
Get
EPATH
17 Production Inhibit Time
18 Connection Timeout Multiplier
Get/Set
Get/Set
UINT
UINT
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
0000h (No ack.)
0005h (Acknowledged)
No value (No ack.)
20 2B 25 01 00h (Acknowledged)
0000h
0000h
CIP Objects 3-11
Parameter Object (0Fh)
General Information
Object Description
This object allows configuration tools such as RSNetworx to extract information about the Application
Data Instances (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.
Due to limitations imposed by the CIP standard, ADIs containing multiple elements (i.e. arrays etc) cannot be represented through this object. In such cases, default values will be returned, see 3-12 “Default
Values”.
See also...
•
3-12 “Default Values”
•
3-14 “ADI Object (A2h)” (CIP Object)
•
5-2 “DeviceNet Host Object (FCh)” (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
Contents:
Bit:
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 Software Design Guide for further information.
CIP Objects 3-12
Instance Attributes
#
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
Value
Actual value of parameter
This attribute is read-only if bit 4 of Attribute #4 is true
0007h
20 A2 25 nn nn 30 05h
(Path to the object from where this parameter’s value is
retrieved, in this case the ADI Object)
Contents:
Bit:
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)
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
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
CIP Objects 3-13
Acknowledge Handler Object (2Bh)
General Information
Object Description
Supported Services
Class
Get Attribute Single
Instance:
Get Attribute Single
Set Attribute Single
Class Attributes
#
1
Name
Revision
Access
Get
Type
UINT
Value
0001h
Type
UINT
USINT
UINT
Value
16ms
01h
04h
Instances Attributes (01h)
#
1
2
3
Name
Acknowledge Timer
Retry Limit
Producing Connection Instance
Access
Get/Set
Get/Set
Get
CIP Objects 3-14
ADI Object (A2h)
General Information
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.
See also...
•
Application Data Object (see Anybus-CompactCom Software Design Guide)
•
3-11 “Parameter Object (0Fh)” (CIP Object)
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 = 0001h)
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 Software Design Guide for further information.
Instances Attributes
Each instance corresponds to an instance within the Application Data Object (for more information,
consult the general Anybus-CompactCom 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
The minimum permitted parameter value.
8
Default valuea
Get
The default parameter value.
a. Converted to/from CIP standard by the module
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
Meaning:
Bit:
0
Set = Get Access
1
Set = Set Access
Instance value
The maximum permitted parameter value.
Chapter 4
Anybus Module Objects
General Information
This chapter specifies the Anybus Module Object implementation and how they correspond to the functionality in the Anybus-CompactCom DeviceNet.
The following Anybus Module Objects are implemented:
•
4-2 “Anybus Object (01h)”
•
4-4 “Diagnostic Object (02h)”
•
4-5 “Network Object (03h)”
•
4-6 “Network Configuration Object (04h)”
Anybus Module Objects 4-2
Anybus Object (01h)
General Information
Object Description
This object groups common Anybus information, and is described thoroughly in the general AnybusCompactCom 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
Anybus Module Objects 4-3
Instance Attributes (Instance #1)
#
1
2
Name
Module type
Firmware version
Access
Get
Get
3
4
Get
Get/Set
5
6
8
Serial number
Application watchdog
timeout
Setup complete
Exception Code
Error counters
Get/Set
Get
Get
9
10
11
12
Language
Provider ID
Provide specific info
LED colours
Get/Set
Get
Get/Set
Get
13 LED status
14 (reserved)
15 Auxiliary Bit
Get
Get
Get/Set
Type
UINT16
struct of:
UINT8 Major
UINT8 Minor
UINT8 Build
UINT32
UINT16
Value
0401h (Standard Anybus-CompactCom)
(see Anybus-CompactCom Software Design Guide)
BOOL
ENUM
struct of:
UINT16 DC
UINT16 DR
UINT16 SE
ENUM
UINT16
UINT16
Value: Colour:
struct of:
Green
UINT8 (LED1A) 01h
Red
UINT8 (LED1B) 02h
Green
UINT8 (LED2A) 01h
Red
UINT8 (LED2B) 02h
UINT8
(see Anybus-CompactCom Software Design Guide)
UINT8
UINT8
Anybus Module Objects 4-4
Diagnostic Object (02h)
General Information
Object Description
This object provides a standardised way of handling host application events & diagnostics, and is thoroughly described in the general Anybus-CompactCom Software Design Guide.
Supported Commands
Object:
Get_Attribute
Create
Delete
Instance:
Get_Attribute
Object Attributes (Instance #0)
#
1
2
3
4
11
Name
Name
Revision
Number of instances
Highest instance no.
Max no. of instances
Access
Get
Get
Get
Get
Get
Data Type
Array of CHAR
UINT8
UINT16
UINT16
UINT16
Value
‘Diagnostic’
01h
See general Anybus-CompactCom Software Design Guide
5+1
Instance Attributes (Instance #1)
#
1
2
Name
Severity
Event Code
Access
Get
Get
Type
UINT8
UINT8
Value
See general Anybus-CompactCom Software Design Guide
In the Anybus-CompactCom 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...
•
2-3 “Diagnostics”
•
3-2 “Identity Object (01h)” (CIP-object)
Anybus Module Objects 4-5
Network Object (03h)
General Information
Object Description
For more information regarding this object, consult the general Anybus-CompactCom 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”
01h
0001h
0001h
Instance Attributes (Instance #1)
#
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
Type
UINT16
Array of CHAR
ENUM
BOOL
UINT16
UINT16
Value
0025h
‘DeviceNet’
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
a. Consult the general Anybus-CompactCom Software Design Guide for further information.
Anybus Module Objects 4-6
Network Configuration Object (04h)
General Information
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...
•
2-3 “Communication Settings”
•
3-2 “Identity Object (01h)” (CIP-object)
Note: In order to ensure fieldbus conformance, the recommendations stated in the Anybus-CompactCom Software Design Guide regarding this object must be followed.
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.
Access
Get
Get
Get
Get
Data Type
Array of CHAR
UINT8
UINT16
UINT16
Value
‘Network configuration’
01h
0002h
0002h
Anybus Module Objects 4-7
Instance Attributes (Instance #1, ‘Device Address’)
Note: In order to ensure fieldbus conformance, the recommendations stated in the Anybus-CompactCom Software Design Guide regarding this parameter must be followed.
#
1
2
3
4
5
Name
a
Access
Get
Type
Array of CHAR
Description
‘Device address’
Valueb
Get
Get
Get
Get/Set
UINT8
UINT8
UINT8
UINT8
04h (= UINT8)
01h (one element)
07h (read/write/shared access)
MacID, stored in non volatile memory
Name
Data type
Number of elements
Descriptor
a. Multilingual, see 4-7 “Multilingual Strings”.
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 MacID configuration via the network (unless disabled in the DeviceNet Host
Object - in such case, the module will enter communication fault state at start up).
Instance Attributes (Instance #2, ‘Baud rate’)
Note: In order to ensure fieldbus conformance, the recommendations stated in the Anybus-CompactCom Software Design Guide regarding this parameter must be followed.
#
1
2
3
4
5
Name
Namea
Data type
Number of elements
Descriptor
Valueb
Access
Get
Type
Array of CHAR
Description
‘Baud rate’
Get
Get
Get
Get/Set
UINT8
UINT8
UINT8
ENUM
08h (ENUM)
01h (one element)
07h (read/write/shared access)
Meaning:
Value: Enum. String:
00h
‘125kbps’
125kbps
01h
‘250kbps’
250kbps
02h
‘500kbps’
500kbps
03h
‘Autobaud’
Autobaud (default)
a. Multilingual, see 4-7 “Multilingual Strings”.
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 baudrate configuration via the network (unless disabled in the DeviceNet Host
Object - in such case, the module will enter communication fault state at start up).
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
Data rate
German
Geräteadresse
Datenrate
Spanish
Direcc nodo
Veloc transf
Italian
Indirizzo
velocità dati
French
Adresse
Vitesse
Chapter 5
Host Application Objects
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 (see Anybus-CompactCom Software Design Guide)
•
Application Data Object (see Anybus-CompactCom Software Design Guide)
Network Specific Objects:
•
5-2 “DeviceNet Host Object (FCh)”
Host Application Objects 5-2
DeviceNet Host Object (FCh)
General Information
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. In
such case, the module will use it’s default value.
See also...
•
3-2 “Identity Object (01h)”
•
3-6 “Assembly Object (04h)”
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_Object_Request (See B-1 “CIP Request Forwarding”)
Instance:
-
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
Host Application Objects 5-3
Instance Attributes (Instance #1)
#
1
2
3
4
Name
Vendor ID
Device Type
Product Code
Revision
Access
Get
Get
Get
Get
5
6
7
Serial Number
Product Name
Producing
Instance No.
Get
Get
Get
Type
UINT16
UINT16
UINT16
struct of:
UINT8 Major
UINT8 Minor
UINT32
Array of CHAR
UINT16
8
Consuming
Instance No.
Get
UINT16
9
Enable Address Get
from Net
10 Enable Baud
rate from Net
Get
11 Enable CIP for- Get
warding
12 Enable Param- Get
eter Object
BOOL
BOOL
BOOL
BOOL
Default Value
005Ah
0000h
0062h
(software revision)
Comment
These values are forwarded to the DeviceNet Identity Object (CIP).
(set at production)
‘Anybus-CC DeviceNet’
0064h
See also...
- 3-6 “Instance 64h Attributes (Producing
Instance)” (CIP-instance)
0096h
See also...
- 3-6 “Instance 96h Attributes (Consuming
Instance)” (CIP-instance)
True
Value: Meaning:
True Can be set from network
False Cannot be set from network
True
See also...
- 3-2 “Identity Object (01h)” (CIP-object)
Value: Meaning:
True Can be set from network
False Cannot be set from network
False
See also...
- 3-2 “Identity Object (01h)” (CIP-object)
Value: Meaning:
True Enable CIP forwarding
False Disable CIP forwarding
True
See also...
- 5-4 “Command Details:
Process_CIP_Request”
- B-1 “CIP Request Forwarding”.
Value: Meaning:
True Enable CIP Parameter Object
False Disable CIP Parameter Object
See also...
- 3-11 “Parameter Object (0Fh)”
(CIP-object)
Host Application Objects 5-4
Command Details: Process_CIP_Request
Details
Command Code.: 10h
Valid for:
Object Instance
Description
By setting the ‘Enable CIP Request Forwarding’-attribute (#11), all requests to unimplemented CIP-objects 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_Request’-command in the Anybus-CompactCom EtherNet/IP.
See also...
•
2-2 “Device Customization”
•
B-1 “CIP Request Forwarding”
Appendix A
Implementation Details
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 Process Data it changes. An inhibit time can be set to prevent the module from sending too often.
The module supports up to 256 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 256 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. The module only uses the input bit if no other I/O connections have been
configured, and produces up to 8 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 256 bytes in each direction for this type of connection.
•
Explicit Connection
The predefined explicit connection has a buffer of 262 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 A-2 “Anybus Statemachine”.
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.
Implementation Details A-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.
Anybus Statemachine
The table below describes how the Anybus Statemachine relates to the DeviceNet network. status
State
WAIT_PROCESS
ERROR
DeviceNet Specific Meaning
The module will stay in this state until a Class
0 connection is opened.
Class 0 connection error, bus off event
detected or dup-MAC-fail
PROCESS_ACTIVE Error free Class 0 connection active
IDLE
Class 0 connection idle
EXCEPTION
Some kind of unexpected behaviour, e.g.
watchdog timeout.
Notes
(Not set for explicit connections.)
If the error is fatal, such, such as dup-MAC-fail
or bus off, the module will stay in this state until
it’s restarted.
Can only be set for connections consuming
data.
The Module Status LED will turn red to indicate a major fault, and turn the Network Status
LED off.
Appendix B
CIP Request Forwarding
If CIP request forwarding is enabled (DeviceNet Host Object, Instance 1, Attribute 11), all network requests to unknown CIP objects will be forwarded to the host application. For this purpose, the DeviceNet Host Object implements a command called Process_CIP_Object_Request (Command code 10h),
which is used to tunnel CIP requests to the host application.
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
(command/response)
1
This message is a command
10h
Process_CIP_Object_Request
Command number
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)
10h
Command number
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
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)
-
CIP Request Forwarding B-2
•
Host Application Response Message Layout (Unsuccessful)
If the host application did not recognized 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
This message is an error message
(command/error)
1
(command/response)
0
This message is a response
10h
Process_CIP_Object_Request
Command number
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
Appendix C
Technical Specification
Protective Earth (PE) Requirements
In order to ensure proper EMC behaviour, the module must be properly connected to protective earth
via the PE pad / PE mechanism described in the general Anybus-CompactCom Hardware Design
Guide.
HMS Industrial Networks does not guarantee proper EMC behaviour unless these PE requirements are
fulfilled.
Power Supply
Supply Voltage
The module requires a regulated 3.3V power source as specified in the general Anybus-CompactCom
Hardware Design Guide.
Power Consumption
The Anybus-CompactCom DeviceNet is designed to fulfil the requirements of a Class A module. For
more information about the power consumption classification used on the Anybus-CompactCom platform, consult the general Anybus-CompactCom Hardware Design Guide.
The current hardware design consumes up to 65mA1.
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 Hardware Design Guide, and
not on the exact power requirements of a single product.
Environmental Specification
Consult the Anybus-CompactCom Hardware Design Guide for further information.
EMC Compliance
Consult the Anybus-CompactCom Hardware Design Guide for further information.
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 DeviceNet will remain as a Class A module.
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