DeviceNetModule 409
DeviceNetModule 409
DeviceNetModule 409
DeviceNet-Module
canAnalyser3 Module
for ODVA™ DeviceNet™ Protocol Interpretation
HMS Technology Center Ravensburg GmbH
Helmut-Vetter-Straße 2
88213 Ravensburg
Germany
Support
In case of unsolvable problems with this product or other HMS products
please contact HMS in written form:
Copyright
Duplication (copying, printing, microfilm or other forms) and the electronic
distribution of this document is only allowed with explicit permission of
HMS Technology Center Ravensburg GmbH. HMS Technology Center
Ravensburg GmbH reserves the right to change technical data without
prior announcement. The general business conditions and the regulations
of the license agreement do apply. All rights are reserved.
Registered trademarks
All trademarks mentioned in this document and where applicable third
party registered are absolutely subject to the conditions of each valid la-
bel right and the rights of particular registered proprietor. The absence of
identification of a trademark does not automatically mean that it is not
protected by trademark law.
Contents
1 Overview 1
DeviceNet Module for canAnalyser3 iii Copyright HMS Technology Center Ravensburg
Contents
A Registers 23
A.1 Definitions, acronyms, abbreviations for DeviceNet . . . . . . . . . . . . . . . . 23
A.2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
A.3 Trademark Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
A.4 Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
A.5 Additional Copyrights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Overview
The DeviceNet-Module (Fig. 1.1) is an add-on module for the canAnalyser3 and provides the
monitoring of the received layer-2 messages in DeviceNet™ notation. The messages are dis-
played in accordance with the DeviceNet standard of the ODVA™ (see Appendix A.2). In addi-
tion, it is possible to show the corresponding layer-2 messages of the protocol-specific interpre-
tations.
2.2 Installation
To install the DeviceNet-Module, insert the provided program CD into the drive of your computer
and run the file "DeviceNetModule32.exe".
Follow the instructions of the installation program.
• Interpretation of layer-2 messages based on the message type and generation of a de-
scription text
• Analysis and monitoring of the fragmentation protocol for Explicit Messages with display
by message or by fragment
• Export and import of the Explicit Connections, the fragmented I/O Messages and the filter
settings
As different instances of the DeviceNet-Module can be started from the Control Panel, it is pos-
sible to adapt each DeviceNet-Module individually to the messages or Message Groups to be
analyzed (only possible with canAnalyser3 standard).
Column Meaning
No Consecutive number of the received DeviceNet messages
Time (rel/abs) Time stamp of the reception, optionally absolute in UTC time format or
relative to the previously received message; the display of hours can
be switched on and off by right-clicking on the column heading
State Reception status
Msg Grp Message Group
Msg ID (hex/dec) Message ID(Message ID)
Src MAC ID (hex/dec) Node number of the message sender (Source MAC-ID)
Dst MAC ID (hex/dec) Node number of the message receiver (Destination MAC-ID)
Msg Usage Message type
XID Transaction ID
RR Displays whether it is a request or a response message
Fragmentation Display of the fragmentation information
Description Interpretation text of the DeviceNet message
Various values can be displayed in hexadecimal or decimal format. The display type for the
individual columns is selected via the menu View or by right mouse click on the corresponding
column header.
A DeviceNet message can be displayed over several lines if the window is not wide enough to
display all information. For this, the menu item View | Word wrap lines is enabled.
To display the corresponding layer-2 message below a DeviceNet message, the menu item View
| Display Layer-2 Messages has to enabled.
Status Meaning
Note: With default settings, the canAnalyser3 is not in Tx-passive mode, i.e. acknowledges
can be actively set and errors signaled. For some DeviceNet™ applications, such as the
analysis of the conformance test, it is necessary to prevent the active bus access. To this end,
the option Tx passive is selected in the controller properties of the Control Panel.
Note: If message interpretation fails, for example because the message has an unexpected
length, the transmitted data are displayed byte-wise.
• Message Group
• Message ID
• Source MAC ID
Note: The signal module can be used to interpret the data of I/O Messages and their meaning
displayed in plaintext.
Note: An entry in the list of fragmented messages is only relevant if no Explicit Connection exists
via this Connection ID.
• Message Group
• Message ID
• XID-bit
• Request/Response bit
• Service Code
• Open Explicit Messaging Connection: For the request, the requested Message For-
mat, the Message Group and the Source Message ID are displayed via which the connec-
tion is to be opened. For the Response, the Message Format used, the Destination and
Source Message ID via which the connection is opened and the Connection Instance ID
are interpreted.
• Close Connection: For the request, the Connection Instance ID is issued. The response
only contains the Service Code.
• Allocate Master/Slave Connection Set: For the request, the Class and Instance IDs
and the individual flags of the Allocation Choice bytes are issued. For the response, the
Message Format used is interpreted.
• Release Master/Slave Connection Set: For the request, the Class and Instance IDs and
the individual flags of the Release Choice bytes are issued. The response only contains
the Service Code.
• Error Response: For this response message, the General Error Code and the Additional
Code are interpreted.
• Device Heartbeat Message: For this response message, the Identity Object Instance
ID, the Device State, the flags Event, System Fault, User Fault, Device-Fault and the Con-
figuration Consistency Value are displayed.
• Device Shutdown Message: For this response message, the Class and Instance IDs
and the Shutdown Code are displayed.
• For all other services, the transferred data are displayed byte-wise.
• Message Group
• Message ID
• XID-bit
• Request/Response bit
• Service Code
• Set Attribute Single: For the request, the Class, Instance and Attribute IDs are analyzed
and the further data are displayed byte-wise. For the response, the transmitted data are
displayed byte-wise.
• Get Attribute Single: For the request, the Class, Instance and Attribute IDs are analyzed.
For the response, the transmitted data are displayed byte-wise.
• Error Response: For these messages, the General Error Code and the Additional Code
are interpreted.
• Allocate and Release Master/Slave Connection Set: These services are interpreted
as described in the section Unconnected Messages.
• For all other services, the Class and Instance IDs are analyzed for the request and the
further data are displayed byte-wise. For the response, the transmitted data are displayed
byte-wise.
In addition, the service and class names defined in DeviceNet™ and the names for the General
Error Codes are displayed with the interpretation.
• Message Group
• Message ID
• Destination MAC ID
• Request/Response bit
• Description text with Physical Port Number, Vendor ID and Serial Number
• Message Group
• Message ID
• Message Group
• Message ID
• Message Group
• Message ID
Attention: As long as the dialog is open, the message reception of the DeviceNet-Module re-
mains stopped.
Via Message Group 2, only the Predefined Master/Slave Connection Set for Explicit Connections
is supported.
When the menu item Functions | Connection Auto Detection is enabled, an Explicit Connec-
tion is added to the list on correct reception of the services Open Explicit Messaging Connection
and Allocate Master/Slave Connection Set. In the event of conflicts with existing entries, these
are removed before a new connection is added to the list.
An Explicit Connection can only be deleted from the list manually. The services Close Con-
nection and Release Master/Slave Connection Set have no influence on the contents of the
connection table.
In addition, time monitoring for the Unconnected Responses and for Acknowledge Fragments
can be set via the connection dialog. The latency time for Unconnected Responses is relevant
for the automatic connection detection on reception of the services Open Explicit Messaging
Connection and Allocate Master/Slave Connection Set. An Explicit Connection is only detected
when the response is transmitted within the latency time. If the latency time is set to 0, no
monitoring is carried out.
Attention: As long as the dialog is open, the message reception of the DeviceNet-Module
remains stopped.
Note: The filter settings have no influence on the automatic connection detection.
Figure 3.4: Display of the three filter views: filtering by Message Group, message usage or MAC ID
All message types are listed in a tree structure (Fig. 3.4). Any message type can be
displayed or filtered out.
• Filtering by MAC ID
All MAC IDs are listed in a tree structure (Fig. 3.4), under each MAC ID a distinction is
made between the individual message types. The specified MAC ID always refers to the
MAC ID in the Connection ID. In this view it is possible to select which messages are to be
received for each node.
Note: A change in filter settings only affects the messages received after the setting change but
not the messages already received before that.
Explanations for exporting and importing solely settings you will find in chapter The term analy-
sis configuration of the canAnalyser3 user manual.
3.10 Toolbar
The main functions of the DeviceNet-Module can also be called via the toolbar (Fig. 3.6).
3.12 Hotkeys
TAB Switch between filter trees and message view
F1 Online-Help
F2 Go to Next Marker
Shift+F2 Go to Previous Marker
Ctrl+F2 Toggle Marker
F5 Start message reception
Shift+F5 Stop message reception
F6 Enable/disable inline logging
F8 Clear View
F11 Show/hide filter trees
Ctrl+C Copy marked lines CSV formatted to clipboard
Ctrl+E Export the received messages to a file
Ctrl+I Show fragmented I/O messages dialog
Ctrl+M Switch fragment- and message-oriented display
Ctrl+N Create a new configuration
Ctrl+O Load application settings from file
Ctrl+S Save application settings from file
Ctrl+T Set/Release Time Reference message
Ctrl+0 Jump to Time Reference message
Ctrl+W Close the application window
Ctrl+X Show explicit connections dialog
PageDown Scroll one page ahead in current View
PageUp Scroll one page backward in current View
Ctrl+PageDown Scroll 1000 messages ahead in current View
Ctrl+PageUp Scroll 1000 messages backward in current View
Ctrl+1..9 Jump to 10%..90% of current View
HKCU\Software\IXXAT\canAnalyser3\Modules\DeviceNet-Module\Settings
(Fig. 3.7):
• ExpReassembling is a DWORD key setting the number of explicit fragments that are
reassembled. Default value is 64.
• IOReassembling is a DWORD key setting the number of I/O fragments that are reassem-
bled. Default value is 64.
• L2FragShown is a DWORD key setting the maximum number of lines to be shown when
layer-2 messages are displayed (see also (View | Show Layer 2 message 3.2)). Default
value is 10.
If a mentioned registry key is not existing, it can be created with the context menu of the registry
editor via command New | DWORD-value (32bit)
Registers
Explicit Message Message type in DeviceNet with which the meaning of the message
is defined by the data field of the CAN message. This message type
is used for configuration and diagnostics. Corresponds to the SDO in
CANopen.
Group-2-Only Server Designation for a device in DeviceNet that only receives messages
in Message Group 2. Uses the Predefined Master/Slave Connection Set
only.
Group-2 Server Designation for a device in DeviceNet that supports the UCMM Port and
also the Predefined Master/Slave Connection Set.
I/O Message Message type in DeviceNet with which the meaning of the message is
defined by the identifier of the CAN message. This message type is used
for the exchange of process data in a DeviceNet system. Corresponds
to the PDO in CANopen.
MAC ID (Media Access Control Identifier) Node number of a DeviceNet device in the
network. For Explicit Messages, DeviceNet distinguishes between
Source MAC ID (source nodes) and Destination MAC ID (destination
nodes). For I/O Messages only the Source MAC ID is used.
Message Format The message format of a connection defines for Explicit Messages with
which format the class and instance are addressed. A DeviceNet node
distinguishes here between 8-bit and 16-bit addressing of class and in-
stance, so that a total of 4 different modes are available: DeviceNet
8/8 to DeviceNet 16/16 (8-bit Class ID/8-bit Instance ID to 16-bit Class
ID/16-bit Instance ID)
Message Group DeviceNet divides the available CAN identifiers into a total of 4 Message
Groups.
Message ID For each DeviceNet node in the network there is a certain number of
message identifiers available in the individual Message Groups.
ODVA (Open DeviceNet Vendor Organization Inc.) User organization of all DeviceNet
users worldwide (see also www.odva.org).
UCMM Port (Unconnected Message Manager Port) One of two ways to set up a con-
nection with a DeviceNet node, the other being the Group-2-Only Un-
connected Port of the Predefined Master/Slave Connection Set.
A.2 Specifications
[1] THE CIP NETWORKS LIBRARY
Volume 1
Common Industrial Protocol
Edition 2.1
January 2005
Open DeviceNet Vendor Association, Inc. (ODVA)
January 2005
Open DeviceNet Vendor Association, Inc. (ODVA)
A.4 Copyright
© 2004-2017 HMS Technology Center Ravensburg GmbH